Troubleshooting Multipod and Multi-Site Issues

This chapter contains the following sections:

Troubleshooting Multi-Site and Multi-Pod

This section describes how to troubleshoot Multi-Site and Multi-Pod.

Error:400

If you receive the following error: 

Error:400 - Invalid Configuration Following Intersite Spines are not configured as Mpod Spines: 1202

You must enable the fabric external connectivity for all the existing spines and if you are trying to add new spines use the Setup Multipod GUI wizard.

There are two ways to resolve this issue.

  • Enable all the spines under the external routed network:

    • In the APIC GUI, on the menu bar, click Tenant > infra.

    • In the Navigation pane, expand Networking > External Routed Networks, right-click on the external routed network and choose Enable Fabric External Connectivity.

  • Add new spines under the external routed network:

    • In the APIC GUI, on the menu bar, click Fabric.

    • In the Navigation pane, expand Quick Start > Node or Pod Setup > Setup Multipod and complete the Multipod setup.

Verifying Remote Leaf Configuration

After you enable direct communication for Remote Leaf switches, you can verify the configuration using the following steps.

Procedure

Step 1

SSH in to the switch.
Step 2

Verify that direct communication is enabled.

In the following output, verify that rldirectMode is set to yes: 

remote-leaf-switch# cat /mit/sys/summary
# System
[...]
remoteNetworkId          : 0
remoteNode               : no
rlOperPodId              : 1
rlRoutableMode           : yes
rldirectMode             : yes
[...]
Step 3

Verify that the remote leaf switches are in complete routable mode and are talking to Cisco APIC's public IP address.

  1. Verify that rlRoutableMode is set to yes. 

    remote-leaf-switch# moquery -c topSystem | grep rlRoutableMode
rlRoutableMode           : yes

  2. Verify that you can ping the Cisco APIC routable IP address from the remote leaf switch. 

    remote-leaf-switch# iping -V overlay-1 110.0.0.225

PING 110.0.0.225 (110.0.0.225) from 193.0.3.20: 56 data bytes

64 bytes from 110.0.0.225: icmp_seq=0 ttl=61 time=0.401 ms

  3. Verify that dhcpRespMo in the remote leaf switch is set to the APIC's routable IP address. 

    remote-leaf-switch# moquery -c dhcpResp

serverId     : 110.0.0.225
siAddr       : 110.0.0.225
status       :
subnetMask   : 255.255.255.255
yiAddr       : 191.2.0.72