Send documentation comments to mdsfeedback-doc@cisco.com
11-29
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 11 Troubleshooting VSANs, Domains, and FSPF
FSPF Issues
Resolving a Wrong Hello Interval on an ISL Using the CLI
To resolve a wrong hello interval on an ISL using the CLI, follow these steps:
Step 1 Use the debug fspf all command and look for wrong hello interval messages.
switch1# debug fspf all
Jan 5 00:28:14 fspf: Wrong hello 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.
Step 3 Use the show fspf internal route vsan command to show FSPF information.
Note To issue commands with the internal keyword, you must have an account that is a member of
the network-admin group.
switch1# show fspf internal route vsan 1
FSPF Unicast Routes
---------------------------
VSAN Number Dest Domain Route Cost Next hops
----------------------------------------------------------------------
1 0xEF(239) 1000 fc1/1 <-----1
1 0xED(238) 2000 fc1/1
1 0x01(1) 3000 fc1/1 <-----2
1. There is no second path to domain 238, through domain 1 switch 2.
2. There is no direct path to domain 1 switch 2; traffic must travel through three ISLs. This is based on
the route cost column.
Step 4 Use the show fspf vsan vsan-id interface command to view the FSFP configuration.
switch1# show fspf vsan 1 interface fc1/16
FSPF interface fc1/16 in VSAN 1
FSPF routing administrative state is active
Interface cost is 500
Timer intervals configured, Hello 5 s, Dead 80 s, Retransmit 5 s <-----1
FSPF State is INIT <-----2
Statistics counters :
Number of packets received : LSU 0 LSA 0 Hello 2 Error packets 1
Number of packets transmitted : LSU 0 LSA 0 Hello 4 Retransmitted LSU 0
Number of times inactivity timer expired for the interface = 0
1. The Hello timer is not set to the default, so you should check the neighbor configuration to make
sure it matches.
2. FSPF is not in FULL state, indicating a problem.
Step 5 Repeat Step 4 to determine the value of the Hello timer 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