Static routing table does not match across cluster members for Cisco

Vendor

Cisco

Description

Indeni will identify when two devices are part of a cluster and alert if their static routing tables are different.

Remediation Steps

Ensure the static routing table matches across devices in a cluster.

1. Execute the "show ip route static" command to display the current contents of the static routes installed to the routing table.

2. Compare the static route config between the peer switches with the show run | i "ip route" command

NOTE: The static routes configured between the peer switches may be different in case of orphan devices without need of redundancy between the vPC peer switches

3. For more information please review the next Cisco configuration guide:

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_cli_nxos/l3_route.html

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show ip route static" command. The output includes a table with the device's configured static routes.

Why is this important?

This script logs into the Cisco Nexus switch using SSH and retrieves the output of the "show ip route static" command. The output includes a table with the device's configured static routes.

Without Indeni how would you find this?

It is possible to poll this data through SNMP but additional external logic would be required to correlate the static routes table across vPC domain (cluster) members.


View Source Code