26
Brocade Adapters Troubleshooting Guide
53-1001582-01
Ethernet network interface problems (CNAs only)
2
Action: To determine link state, run the ifconfig command for Linux or VMware systems. For
Windows systems, run ipconfig /all or use Settings > Network Connections.
Action: For the interface to send and receive packets, both the UP and RUNNING flags must be
set.
Action: If pinging a server on a different network. make sure that the route to that host network
or that the default gateway is correctly configured.
2. Possible Cause: Other link problems.
3. Possible Cause: IP address and network mask of CNA port are set incorrectly.
Action: Verify and set IP address and network mask if necessary:
•
Linux - Run the ifconfig command to determine if port has proper IP address and network
mask and to verify that the link is up.
•
Windows - Use Device Manager and network connection tools.
4. Possible Cause: Packets are not being received or stack is dropping packets at remote server
due to incorrect IP address set on adapter or incorrect MTU size.
Action: Verify if packets arrived at the remote server using the following commands:
•
Linux - Run the tcpdump command.
•
Windows - Run the Wireshark application.
Action: Verify MTU size on your system and increase size if necessary. Note that MTU size set
on adapter must not be more than MTU size set on attached FCoE switch. To set MTU size on
the adapter, refer to the “Adapter Configuration” Chapter in the
Brocade Adapters Installation
and Reference Manual
.
Action: Verify and set IP address and network mask if necessary:
•
Linux - Run the ifconfig command to determine if port has proper IP address and network
mask and to verify that the link is up.
•
Windows - Use Device Manager and network connection tools.
5. Possible Cause: If hosts with Windows operating systems do not reply to broadcast/multicast
ICMP ping commands, this is by design. Windows systems will not reply for security reasons.
Action: Refer to Windows KB137421 on
http://support.microsoft.com/kb/137421
.
Teaming errors
Ports configured as team members are in an error state and output from the BCU team --query
command shows mismatching of teaming parameters. Although you can still create teams, the
parameters configured for the first port (primary port) added to a team should match parameters
of subsequent ports added to the team or mismatching conflict errors result.
In the following example output from the BCU team --query command, a conflict displays for the
port associated with local area connection 6 because its PVID does not match the PVID of the
primary port (local area connection 3).
2/0 : Local Area Connection 3 (Primary) (Active) (Linkdown)
3/1 : Local Area Connection 6 )Conflict)
Conflict Reason: Mismatching PVIDs configured for adapters
