Out-Of-Band EPG - default

[conf-t]

Hi,

Under "Out-Of-Band EPG - default", we can configure static routes but without nexthop (or gateway).. What is the purpose of this option? And why I couldn't find the route when typing "route -n" on the apic cli?

[M02@rt37]

Hello @conf-t,

The "route -n" command on the APIC CLI typically shows the routes that are relevant to the internal fabric routing, not necessarily the routes associated with the out-of-band management. Routes for out-of-band management might not be displayed using this command.

https://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/aci-guide-configuring-out-of-band-access-for-your-fabric.pdf

[conf-t]

Thank you for your response

Can you answer me about the purpose of this option called "static routes" under the OOB EPG? 

[M02@rt37]

@conf-t 

All devices will need static OOB addresses (APIC controllers, leafs, and spines) that associate the IP address, NodeID, default GW, and management type (OOB, in this case). You'll need to configure a contract that will be consumed and provided to your OOB devices. The contract will allow the system to know what traffic is allowed. (In this use case, you will use the default/common contract to permit any traffic.)

[conf-t]

M02@rt37 

Yes you talk about how to configure OOB, I know that.

I'm asking about the "static  routes" option on the Out-Of-Band EPG.

[M02@rt37]

 @conf-t 

When you configure static routes under the "Out-of-Band EPG - default" in Cisco ACI, the routes are intended for communication within the fabric's out-of-band management network. These routes are used for managing and accessing the components of the ACI fabric, including the APIC controllers, spine switches, and leaf switches.

When you configure a static route without specifying a next hop or gateway under the "Out-of-Band EPG - default," it signifies that the route is local to the fabric, and the destination is reachable within the fabric itself. This is typical for the out-of-band management network where communication between fabric components occurs within the fabric infrastructure.

Now, regarding the visibility of these routes using the "route -n" command on the APIC CLI, the routes configured under the "Out-of-Band EPG - default" might not be displayed by default. This is because the APIC CLI may not provide visibility into routes associated specifically with out-of-band management trafic.

[conf-t]

Thank you M02@rt37 

Have you a use case? an example for using this static route? Thanx