I/O Data Traffic Issues; Driver Installation Fails And System Cannot Be Booted - Brocade Communications Systems CNA 1010 Troubleshooting Manual

I/O data traffic issues

I/O data traffic issues are occurring, such as an application is not receiving data, FTP problems on
an Ethernet network, data is not reaching a target on a Fibre Channel network, or ping failures.
1. Possible Cause: Ethernet traffic problem (CNAs only).
2. Possible Cause: Fibre Channel or FCoE I/O problems.

Driver installation fails and system cannot be booted

Installation of a new Windows 2008 driver package fails in systems where an adapter is used for
booting over SAN and the operating system becomes unbootable.
Possible Cause: Existing driver package that was accessing the remote boot LUN was removed and
system was rebooted.
Action: Install the new adapter driver without uninstalling the existing driver. This is the
recommended procedure for updating adapter drivers.
Brocade Adapters Troubleshooting Guide
53-1001582-01
Action: Run the Ethernet loopback serdes test on the suspected Ethernet port using the BCU
ethdiag --loopback <port_id> -t serdes command. This tests internal adapter hardware
components. If the test passes, suspect the following external problems:
•
Faulty fiber
•
Faulty software
•
Destination host problem
Action: Run the BCU Ethernet external loopback test using the BCU command ethdiag
--loopback <port_id> -t ext (stand-up adapters only). Be sure that a loopback connector is
installed in the port. If the serdes or internal loopback test passes, but the external test fails,
suspect the following problems:
•
Loopback connector not inserted in transceiver
•
Faulty SFP or loopback connector.
Action: Run the loopback serdes test on the suspected Fibre Channel port (HBAs only) or FCoE
port (CNAs only) using the BCU diag --loopback <port_id> -t serdes command. If the test
passes, suspect the following external problems:
•
Faulty fiber
•
Faulty software
•
Target problem
Action: Run the BCU external loopback test (stand-up adapters only) using the BCU command
diag --loopback <port_id> -text. Be sure that a loopback connector is installed in the port. If the
serdes or internal loopback test passes, but the external test fails, suspect the following
problems:
•
Loopback connector not inserted in transceiver
•
Faulty SFP or loopback connector.
General HBA and CNA problems
2
13