Configuring Cisco ACI OOB Management

Summary of the configuration steps

  • have in mind the subnet you are going to use for out of band, and its gateway IP address.
  • assign the OOB subnet to selected nodes
  • define an OOB contract, with a subject and a default filter. This contract will be used in both directions: provide and consume.
  • set the OOB contract as a provided contract by the default OOB EPG
  • create an External Network Instance Profile
  • set the OOB contract as a consumed contract by the external management network instance profile.

Detailed configuration steps

  • position yourself on tenant mgmt
  • Create a Node Management Address:
  • give it a name next to Policy Name
  • Select Nodes by: choose specific then select the nodes that will receive IP addresses
  • under Config select “out-of-band addresses”
  • select the default EPG as the Out-of-band Management EPG
  • define the out-of-band gateway.
  • define the subnet range of OOB IP addresses that will be assigned to the previously selected nodes.
  • confirm
  • Position your self under Out-of-Band Contracts. Prior to ACI v4 you click on Security Policies. In ACI v4 you find the OOB Contracts menu under Contracts directly.
  • define a new contract name
  • expand the Subjects by clicking on the plus sign:
  • name the subject:
  • Expand the Filters
  • select the filter default from the drop down list:
  • select the default out-of-band EPG under Node Management EPGs
  • click on it and expand the Provided Out-of-Band Contracts. Select the previously created contract:
  • Create a External Management Network Instance Profile

Give it a name:

  • expand Consumed Out-of-Band Contracts and select the same OOB contract created before:

Additional Ressources on Configuring OOB Management on ACI

  • Configure the OOB for ACI Fabric, prior to v4: https://community.cisco.com/legacyfs/online/attachments/discussion/aci-oob-part1_tdeleon.pdf

Click here to read the rest of my Cisco ACI study notes.

Comments

Post a Comment

Popular posts from this blog

The Thing With CUCM Device Packs

Image
To add a new phone on CUCM, whether it is a Cisco phone or one of the free softphones on the Internet, you go to Device –> phone. Sometimes the phone you want to add does not exist in the drop box, because the device model is new or the CUCM version is a bit old. What you can do here is to download a Device Pack of the new phone and install it. A Device Pack is a set of firmwares contained in a single file. Generally, it has the extension “sgn”. A Device Pack for phone X not only contains a load for it, but also loads for many other phone models. This is important to know because, once you install a Device Pack in CUCM, your existing phones by default will install the new version of their respective loads. I encountered a case where, after installing a Device Pack, some phones no longer worked. So I had to note down the “Active Load” and put it in the Device Defaults page. CUCM Device Pack download To download a Device Pack, you need to have a valid Cis...
Read more

En Bloc Dialing vs Digit-By-Digit Dialing

Image
Digit Signaling, aka Digit Addressing, is the method by which digits are sent from a dialing endpoint (e.g. phone) to a CUCM server, or by a voice gateway or trunk. There are three known digit signaling methods: En Bloc dialing SIP Dial Rules Digit-by-digit dialing 1. En Bloc digit dialing In the En Bloc digit signaling method, digits are sent as a whole block. Think of it like a brick that you send to UCM. This is the digit addressing method used on Type A Cisco phones, whether the endpoint signaling protocol is SIP or SCCP. En Bloc dialing is the default method used with the famous gateway protocols -MGCP, H323 and SIP- and also on H323 trunks and SIP trunks. Besides, the resulting pattern of a Translation Pattern operation is sent as En bloc to the call control system. 2. SIP Dial Rules It is important to know that all SIP phones support SIP dial rules, whether they are Type A or Type B. SIP dial rules are created on CUCM and downloaded by...
Read more

Call Forward And Call Hunt on CUCM

Image
Call forwarding is one of the features of the call coverage in Cisco CUCM. Call Hunting is when CUCM distributes a call on more than one Directory Number (DN), whether consecutively or simultaneously, depending on the algorithm. Hunt Pilot A Hunt Pilot is the entry point for the whole call hunting process. It is hit by a Call. The Hunt Pilot number is a dialable entity and has many similarities with Route Patterns : We can configure Route Filters with Hunt Pilots, Hunt Pilots can Provide Outside Dial Tone , We can set Hunt Pilots with the Urgent Priority flag, They can route or block calls, They can apply Calling and Called Party Transformations. Hunt Lists After hitting the Hunt Pilot, the call is presented by CUCM to the Hunt List. Each Hunt List contains one or more ordered Line Groups. A Hunt List can be pointed by one or more Hunt Pilots. Line Groups Each Line Group contains one or more member (we’ll refer to them as Hunt members, hunt parties or Line Group members). A Line Grou...
Read more