Site icon

ACI: Configuring Out-of-Band (OOB) access for your Fabric

Screen Shot 2018-04-13 at 1.21.38 PM.png

Configuring Out-of-Band connectivity to your ACI Fabric devices is a critical component to successfully maintaining and operating your datacenter. When it comes to configuring OOB connectivity to your devices (Leafs, Spines, and APIC Controllers), you’ll have need to do two things to get things going:

  1. All devices will need static OOB addresses (APIC Controllers, Leafs, and Spines) that associates the IP address, NodeID, Default GW, and Management type (OOB, in our case)
  2. Configure a Contract which will be consumed and provided to your OOB devices. The Contract will allow the system know what traffic is allowed (for our use case, we will use the default/common contract to permit any traffic).

Notables and Caveats

Provide OOB Address for your APICs and Switches

Add the APIC(s) to the Static OOB Address List

Tenant > Tenant mgmt > Node Management Addresses > Static Node Management Addresses

Tenant > Tenant mgmt > Node Management Addresses > Static Node Management Addresses

 

Add your ACI Fabric Switches to the Static OOB Address List

Tenant > Tenant mgmt > Node Management Addresses > Static Node Management Addresses

Tenant > Tenant mgmt > Node Management Addresses > Static Node Management Addresses

 

Provide and Consume Contracts for your OOB devices using default/common contract (permit any/any)

Step 1 – Providing the contract

Tenant > Tenant mgmt > Node Management EPGs > Out-of-Band EPG default

Tenant > Tenant mgmt > Node Management EPGs > Out-of-Band EPG default

Step 2 – Consuming the contract

Tenant > Tenant mgmt > External Management Network Instance Profiles > YourInstanceProfile

Tenant > Tenant mgmt > External Management Network Instance Profiles > YourInstanceProfile

 

 

 

Exit mobile version