Cisco MDS-9124 Troubleshooting Guide - Page 251

Chapter 11 Troubleshooting VSANs, Domains, and FSPF FSPF Issues Send documentation comments to [email protected] Step 2 Step 3 Repeat Step 1 to determine the value of the retransmit interval on the adjacent switch. switch2# show fspf v 1 interface fc2/16 FSPF interface fc2/16 in VSAN 1 FSPF routing administrative state is active Interface cost is 500 Timer intervals configured, Hello 20 s, Dead 80 s, Retransmit 5 s FSPF and select the Interfaces tab to verify that the FSPF parameters are correct for each interface and check the Dead interval column and the State column. • 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. Repeat Step 1 to determine the value of the dead interval on the adjacent switch. Fill in the Dead field to change the dead interval and click Apply. Resolving a Mismatch in Dead Intervals on an ISL Using the CLI To identify a mismatch in dead intervals on an ISL, follow these steps: Step 1 Use the debug fspf all command and look for wrong dead interval messages. switch1# debug fspf all Jan 5 00:28:14 fspf: Wrong dead interval for packet on interface 100f000 in VSAN 1 Jan 5 00:28:14 fspf: Error in processing hello packet , error code = 4 Tip We recommend that you open a second Telnet or SSH session before entering any debug commands. If the debug output overwhelms the current session, you can use the second session to enter the undebug all command to stop the debug message output. Step 2 Use the undebug all command to turn off debugging. OL-9285-05 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x 11-31