Brsocade Adapters Troubleshooting Guide 23
53-1001253-01
Ethernet network interface problems (CNA only)
2
To disable NetworkManager for SLES systems, perform the following steps.
a. Open YaST.
b. Select the Network Devices Network Card.
c. On the first screen set the Network Setup Method option to Traditional Method with ifup.
Loss of adapter hardware address in Linux
The ifconfig command displays HW Addr as 00:00:00:00:00:00.
Possible Cause: The CNA failed to initialize for some reason.
Action: Disable the Ethernet I/O controller by entering the BCU ethioc --disable command, then
enable the I/O controller by entering the BCU ethioc --enable command.
Loss of adapter IP address in Linux
The IP address for the adapter disappears when the adapter goes down or system reboots.
Symptom: The IP address set in Linux with the ifconfig command disappears when the adapter
goes down or host system reboots.
1. Possible Cause: The IP address was set with the ifconfig command and the adapter is enabled
in DHCP (Dynamic Hardware Configuration Protocol) mode.
Action: Configure IP address using system GUI-based networking tools.
2. Possible Cause: The IP address is not configured in the ifcfg-ethX script.
Action: Manually configure IP address in ifcfg-ethX script.
Ethernet loopback test problems
Errors occur during BCU Ethernet loopback tests.
1. Symptom: Loopback test returns “Check link/cable or SFP” error when executed with -t cable
option.
Possible Cause: Loopback cable not inserted in tested port.
Action: Verify that loopback cable is securely inserted in the port that you are testing.
2. Symptom: Loopback test returns a “port not disabled” error.
Possible Cause: Port is enabled.
Action: Disable the port using the BCU port --disable command before running loopback test.
3. Symptom: Loopback test returns a “port not disabled” error.displays even after disabling the
port.
Possible Cause: Network load balancing service is enabled. This will cause the adapter to
disable and enable, and the previously configured state (port disable) is lost.
Action: Disable network load balancing and retest.
4. Symptom: The loopback test returns “Device busy - Retry operation” or “diag busy.”
Possible Cause: Other users or sessions are running another instance of loopback tests.
Comentarios a estos manuales