Brocade Adapters Troubleshooting Guide
25
53-1001582-01
Ethernet network interface problems (CNAs only)
2
Network stack runs out of heap
The network stack on VMware systems is running out of heap space.
Possible Cause: Enabling NetQueue and using jumbo frames has caused the network stack to run
out of heap with default values set for netPktHeapMaxSize and netPktHeapMinSize. Leaving
default values can result in unpredictable behavior.
Action: Perform the following steps.
1. Log in to the VI Client.
2. Click the Configuration tab for the ESX Server host.
3. Click Advanced Settings.
4. Click VMkernel.
5. Find the corresponding value field for VMkernel.Boot.netPktHeapMaxSize, and enter 128.
6. Find the corresponding value field for VMkernel.Boot.netPktHeapMinSize, and enter 32.
7. Click OK to save the changes.
8. Reboot the system.
NIC numbering unexpected on VMware systems
After installing CNA drivers on VMware systems, NIC numbering is not what is normally expected.
For example, instead of vmnic32 or vmnic33, number is vmnic2 and vmnic3.
Possible Cause: CNA hardware was installed before drivers.
Action: When installing a CNAs on a VMware systems, it is advisable to install the driver before the
CNA cards so that the NICs will be properly enumerated in the system. To resolve the problem, you
must perform the following steps.
1. Uninstall the drivers.
2. Remove the CNA card.
3. Reboot your system without the CNA.
4. Install the drivers.
5. Install the card.
6. Reboot the host system.
Ping to remote host is failing
Pings generated between servers are failing or there is no response from ping.
1. Possible Cause: Ethernet interface on either server is in the following states:
•
Administratively down. Running the Linux or VMware ifconfig command shows that the UP
flag is not set.
•
Administratively up, but link is down. Running the Linux or VMware ifconfig command
shows that the RUNNING flag is not set.
