3–Fibre Channel ConfigurationRunning Diagnostics—Fibre Channel Ping and Trace Route79 BK3254601-00 CRunning a Fibre Channel CT Ping from QConvergeConsole CLITo run a Fibre Channel CT ping test from QConvergeConsole CLI:1. From the QConvergeConsole CLI FC Diagnostics menu, select 7: CT PingTest.2. From the HBA Model list, select the port that you want to ping.3. From the CT Ping Test menu, select 4: Start Diagnostic Test.The following shows example output from the CT ping test.----------------------------------------------Diagnostics Test Configuration----------------------------------------------Diagnostic Mode : CT PingNumber of tests (1-10000) : 10Number of Pass : 1Test Increment (1-10000) : 1Abort On Error : IgnoreTest Continuous : OFF---------------------------------------------------ID Data Link Sync Signal Invalid DiagnosticPort/Loop Miscompare Failure Loss Loss CRC Status--------- ---------- ------- -------- --------- --------- ----------01-0B-01 0 0 0 0 0 SuccessRunning a Fibre Channel CT Ping from QConvergeConsole VMware Plug-insFor information about running Fibre Channel CT ping from theQConvergeConsole VMware vCenter Server Plug-in or QConvergeConsoleVMware vSphere Web Client Plug-in, see the section “Diagnostic Tests—FibreChannel Port” in the User’s Guide—QConvergeConsole Plug-ins for VMwarevSphere (part number SN0054677-00).Fibre Channel Trace RouteTo run a Fibre Channel trace route from QConvergeConsole GUI:1. In the system tree pane on the left, click the Host tab.2. In the content pane on the right, click the Topology tab.3. Next to Topology, select the Physical option.4. In the topology map, right-click the applicable adapter.5. Select the FC Trace Route option.NOTEThe default setting will repeat 10 times with output similar to the precedingfor each pass of the test.
