Brocade Fabric OS Troubleshooting and Diagnostics Guide (Supporting Fabric OS v7.3.0) - Manual (Page 36)

20 Fabric OS Troubleshooting and Diagnostics Guide
53-1003141-01
FC-FC routing connectivity
2
Consider the following example in which a few errors are recorded on ISLs 3/205-->2/25,
3/204-->2/27, 2/42-->101/3, and 2/1-->101/8. The potential faulty link is internal port 0/284 on
domain 2 with the maximum of 100 percent failure.
ISL COVERAGE
-------------
SNO ISL STATUS
-----------------------------------------------------------------------------
1 3/123[128]--> 165/96[128] SUCCESS(5/5)
2 3/205[128]--> 2/25[128] FAILURE(7/50)
3 3/204[128--> 2/27[128] FAILURE(11/50)
4 165/99[128]--> 101/16[128] SUCCESS(5/5)
6 2/42[128]--> 101/3[128] FAILURE(10/67)
7 2/1[128]--> 101/8[128] FAILURE(8/33)
INTERNAL PORT COVERAGE
-----------------------
SNO DOMAIN INTRNL_PORT STATUS
-----------------------------------------------------------------------------
1 2[128] 0/272 SUCCESS(40/40)
2 2[128] 0/276 SUCCESS(44/44)
3 2[128] 0/280 SUCCESS(30/30)
4 2[128] 0/284 FAILURE(20/20) <== 100% failure
When an ECHO frame is dropped, all the ISLs in the path are marked as failed. It is not possible to
determine the exact ISL link that dropped the frame. Because of this, all the ISLs in the path record
some failures. The ISL with the actual error has the maximum percentage of failures, as this ISL,
when selected in any possible path, causes the ECHO frame to be dropped and accumulates a
higher failure percentage.
Restrictions
• Fabric reconfiguration cannot occur while using the Superping feature. It is assumed that the
fabric is stable before the fcPing --allpaths command is executed.
• The control path for interswitch communication should be available, even if the data path for
device-to-device communication may have resource starvation.
• When executed in a fabric with trunk ports, only the trunk master index is output to the user
(for example, individual coverage statistics for each trunk-member are not available).
• All switches must have Fabric OS v6.3.0 or later.
• Superping requires that the FC ECHO ELS frame is supported by end-devices.
• In TI Zones, when failover is disabled and Superping is executed on a destination device
included in the TI Zone, then Superping displays failures on all ISLs that are not part of the TI
Zone. Also, when Superping is executed on a device that is not present in a TI Zone, failures are
shown on all ISLs that are part of any TI Zone.
• This feature is not supported in interopMode 2 or 3.
• In frame redirection configurations, where there is a physical host, physical target, virtual
initiator, and virtual target; Superping only identifies the path from the physical host to the
physical target regardless of whether the data path consists of the path from the physical
target to the virtual target through the virtual initiator.