3–Fibre Channel ConfigurationRunning Diagnostics—Fibre Channel Ping and Trace Route79 CU0354604-00 PRunning Diagnostics—Fibre Channel Ping andTrace RouteThis section provides the following information on how to run Fibre Channel pingand trace route diagnostics: Pinging and Viewing Trace of Routing Using Topology Map Running a Fibre Channel CT Ping Test Fibre Channel Trace RoutePinging and Viewing Trace of Routing Using Topology MapThe QConvergeConsole GUI topology map uses the common transport (CT) layerto enable the adapter’s initiator port to ping or run a trace route that will navigateacross the environment through multiple ports of the switch or switches and to thetarget.Table 3-8 compares the differences between the Ping Test, CT Ping Test, and theCT FTR Tests.Supported configurations for Fibre Channel ping and trace route include: QLogic 2600 Series Adapters and 8200 Series Adapters Brocade Switches with Based Fabric OS ® (FOS) v6.0.0a Cisco ® Switches with NX-OS v8.3.1 (FC Trace Route not supported)Table 3-8. Ping Test, CT Ping Test, and CT FTR TestPing Test CT Ping Test CT FTR TestSCSI layer ping CT or Fibre Channel ping CT or Fibre Channel trace routeUses SCSI inquiry command Uses echo through an externallinkRequires scan of physical topologyCan operate on any SCSIdeviceCan operate with all Fibre Chan-nel devices that support CT or anexternal linkCan operate with all devices thatare connected through a port thatsupports CT or an external linkNOTEThe switch and the Fibre Channel end device must both support the FibreChannel ping and trace route feature. See Table 3-11 on page 96 for thesupported Fibre Channel software version.
