Remote LEAF Control Plane

[waschminator]

hello, if a pod fails where a remote leaf is connected then it will connect to a spine in anither pod (as long as the option for that is anbbled (in the system settings)). but how am i able to check under the hood to whcih spine the control plane of the remote leaf is connected?

br +thc

[dexterhale398]

Hi there,
To check which spine the control plane of the remote leaf is connected to, you can use the following methods:

1. Check the Leaf's OSPF/EVPN Neighbors:
   Use the command show lldp neighbors or show evpn to see the spine the remote leaf is connected to. This will provide details on the neighbor relationships.

2. Check the Control Plane Data Path:
   Use show ip route or show bgp to inspect the routing and BGP sessions, which will indicate the spine that is handling the remote leaf's traffic.

3. Use the Fabric Health Dashboard:
   In Cisco ACI, you can view the fabric’s health dashboard to identify path failover and where the control plane is currently being handled.

These commands will help you identify the spine currently in control of the remote leaf's traffic and control plane.

[waschminator]

hmm...i am not sure if that really helps

ad 1. the remote leaf has only the ipn as ospf neigbor. and there is also no evpn neighbor within a pod afaik

ad 2. the routing does not say something about the association of the leaf. mroeover there is not really a go sesison with a pod.

ad 3. where is that?

[AshSe]

Hello @waschminator , I would like to give a little clarity before addressing your question:

A remote leaf is always connected to a spine located in different DC in different geographical location. Further, 

To check under which spine the control plane of a remote leaf is connected in a Cisco ACI environment, you can use the Cisco Application Policy Infrastructure Controller (APIC) to gather this information. The APIC provides various tools and interfaces to monitor and manage the ACI fabric, including the relationships between leaf and spine switches.

Here are the steps to check the control plane connection of a remote leaf:

Using the APIC GUI:

1. Log in to the APIC GUI: Access the APIC web interface using your credentials.
2. Navigate to Fabric Inventory:
   1. Go to the "Fabric" tab.
   2. Select "Inventory" from the left-hand menu.
3. Locate the Remote Leaf:
   1. Find the remote leaf switch in the inventory list. You can use the search function to quickly locate it by its name or ID.
4. View Leaf Details:
   1. Click on the remote leaf switch to view its details.
   2. Navigate to the "Operational" tab or section, where you can see various operational parameters and status information.
5. Check Spine Connectivity:
   1. Look for information related to spine connectivity. This may be under sections like "Fabric Membership", "Control Plane", or similar.
   2. The GUI should display the spine switches to which the remote leaf is currently connected for control plane communication.

Using the APIC CLI:

1. Access the APIC CLI: Use SSH to log in to the APIC controller.
2. Run Commands to Check Spine Connectivity:
   1. Use the following commands to gather information about the control plane connections:
      # show fabric membership 
   2. For more detailed information, you can use:
      # show fabric node <node-id>

Hope This Helps!

AshSe

If you found this post helpful, please consider rating it.

[waschminator]

unfortunately your tips do not work

spine# show fabric membership
Incorrect command "show fabric membership"
spine# show fabric node 1101
Incorrect command "show fabric node 1101"
LABCSRV-AB1BU1133-0402-S01P02#

also in the GUI we do not find it in this way.

only way i was able yet to find it is in the GUI under fabric/inventory/pod-x/remore-leaf/protocols/coop --->oracle adjacency

and in the CLI with  "show coop internal info global" 

[Wassim Aouadi · Accepted solution]

To add to the good reply from @waschminator , the command "show coop internal info global" must be entered from the CLI shell of the Remote Leaf.

@waschminator kindly mark the post as solved.

Regards

Wassim

[Wassim Aouadi]

Hello @AshSe ,

Can you post the link to your source please? The command you've mentioned does not exist in the Cisco APIC CLI reference.

Regards

Wassim