Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual page 90

FC Services
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m .
Solution
Consider the following solutions:
•
•
•
•
•
•
Specific VSAN traffic is not being routed through SAN fabric
Each configured VSAN needs to support a separate set of fabric services. One such service is the FSPF
routing protocol, which can be independently configured per VSAN. You may see that specific VSAN
traffic is not being routed if inappropriate traffic engineering capabilities are used.
Possible Cause
The FSPF hello interval is misconfigured.
The following example shows possible log messages from the show logging command log.
Example:
FSPF-3-HELLO_MISMATCH: %$VSAN <vsan-id>%$ Mismatch in Hello timer in the Hello packet on
interface san-port-channel <channel-id>
%FSPF-3-FC2_PROC_ERR: %$VSAN <vsan-id>%$ Error in processing HELLO
san-port-channel <channel-id>, Error
Solution
To resolve a wrong hello interval on an ISL using the NX-OS CLI, perform the following steps.
Cisco Nexus 5000 Series Troubleshooting Guide
5-18
Use the show hardware internal fc-mac <slot-number> port <port-number> statistics command
to check for Class-3 packet counters.
Analyze the output of the show flogi internal all interface fc <slot/port> command for a possible
drop of FLOGI packets somewhere in the path.
Check the Fport server fault-injection table for any Invalid, Drop FLOGI packets.
Use the shut CLI command followed by the no shut command to disable and enable the FC slot/port.
If this does not clear the problem, try moving the connection to a different port on the same or
another FC module.
If the problem continues to persist, use the following commands to collect information to aid in
further analysis:
show tech-support flogi
show logging log | grep
show port internal info interface fc <slot/port>
show port internal event-history interface fc <slot/port>
show tech-support detail > bootflash:showtechdet
show platform fwm info pif fc <slot/port> {find the gatos instance for the port}
show platform fwm info gatos-errors 13 {check for the non-zero counters for drops}
Capture debug Flogi with the following:
switch# debug logfile flogi_debug
switch# debug flogi all
switch(config)# int fc <slot/port>
switch(config-if)# shut
switch(config-if)# no shut
switch(config-if)# undebug all
switch# dir log: {check if you have the file in log: directory}
31 Aug 03 13:45:13 2010
34941 Aug 06 07:21:15 2010
switch# copy log:flogi_debug ftp://x.y.z.w {or use tftp/scp/sftp}
fc <slot/port>
dmesg
flogi_debug
= Bad packet received
Chapter 5 Troubleshooting SAN Switching Issues
packet on interface
OL-25300-01