Cisco MDS-9124 Troubleshooting Guide - Page 245

Chapter 11 Troubleshooting VSANs, Domains, and FSPF FSPF Issues Send documentation comments to [email protected] Troubleshooting FSPF Using Device Manager To troubleshoot FSPF using Device Manager, follow these steps: Step 1 Step 2 Step 3 Step 4 Choose FC > Advanced > FSPF and select the LSDB LSRs tab to verify the link state records (LSRs) in the FSPF database. • The VSANId/ DomainId column shows the domain's view of the fabric topology. • The AdvDomainId column shows which domain is the owner of the LSR. • The Age value is a 16-bit counter starting at 0x0000, incremented by one for each switch during flooding and by one for each second held in the database. This field is used as a tie-breaker if incarnation numbers are the same. • The IncarnationNumber is a 32-bit value between 0x80000001 and 0x7FFFFFFF that is incremented by one each time the originating switch transmits an LSR. This is used before the Age value. Choose FC > Advanced > FSPF and select the LSDB Links tab to verify that each path is in the FSPF database. Choose FC > Advanced > FSPF and select the Interfaces tab to verify that the FSPF parameters are correct for each interface and verify that the AdminStatus is up. • The Cost column shows the cost of the path out of the interface. • The Intervals column shows the configured FSPF timers for this interface, which must match on both sides. • The State column shows the full or adjacent state if the interface has sent and received all database exchanges and required Acks. The port is now ready to route frames. • The Neighbors column shows FSPF neighbor information. Choose FC > Advanced > FSPF and select the Statistics or InterfaceStats tab to verify that there are no excessive errors present. Troubleshooting FSPF Using the CLI To troubleshoot FSPF using the CLI, follow these steps: Step 1 Use the show fspf database vsan command to verify that each path is in the FSPF database. switch1# show fspf database FSPF Link State Database for VSAN 2 Domain 1