Users Guide

3–Fibre Channel Configuration
Running Diagnostics—Fibre Channel Ping and Trace Route
79 BK3254601-00 J
Running Diagnostics—Fibre Channel Ping and
Trace Route
This section provides the following information on how to run Fibre Channel ping
and trace route diagnostics:
 Pinging and Viewing Trace of Routing Using Topology Map
 Running a Fibre Channel CT Ping Test
 Fibre Channel Trace Route
Pinging and Viewing Trace of Routing Using Topology Map
The QConvergeConsole GUI topology map uses the common transport (CT) layer
to enable the adapter’s initiator port to ping or run a trace route that will navigate
across the environment through multiple ports of the switch or switches and to the
target.
Table 3-8 compares the differences between the Ping Test, CT Ping Test, and the
CT FTR Tests.
Supported configurations for Fibre Channel ping and trace route include:
 QLogic 2700 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 Test
Ping Test CT Ping Test CT FTR Test
SCSI layer ping CT or Fibre Channel ping CT or Fibre Channel trace route
Uses SCSI inquiry command Uses echo through an external
link
Requires scan of physical topology
Can operate on any SCSI
device
Can operate with all Fibre Chan-
nel devices that support CT or an
external link
Can operate with all devices that
are connected through a port that
supports CT or an external link
NOTE
The switch and the Fibre Channel end device must both support the Fibre
Channel ping and trace route feature. See Table 3-11 on page 96 for the
supported Fibre Channel software version.