Troubleshooting
Problem
The creation of multiple Virtual Local Area Networks (VLANs) on the BNT Virtual Fabric 10 Gigabit Switch Module for IBM BladeCenter, Option part number 46C7191, may cause Data Center Bridging Protocol (DCBX) errors due to optional Link Layer Discovery Protocol (LLDP) Type Length Values (TLVs) being enabled by default. For example, one might see the following log entries in the switch module event log: Jan 9 15:13:47 9.42.161.156 NOTICE server: link down on port INT6 Jan 9 15:13:48 9.42.161.156 NOTICEserver: link up on port INT6 Jan 9 15:13:50 9.42.161.156 NOTICE dcbx: Detected DCBX peer on port INT6 Jan 9 15:15:50 9.42.161.156 NOTICE dcbx: Peer on port INT6 stopped responding to DCBX message Also, attempting to add more VLANs may not be possible and could result in the BNT Virtual Fabric 10 Gigabit switch module returning the following event log entries: Jan 9 16:28:50 9.42.161.156 ERROR cfg: Error: Please reconfigure port INT6's Optional TLVs in order to avoid sending incomp
Resolving The Problem
Source
RETAIN tip: H204829
Symptom
The creation of multiple Virtual Local Area Networks (VLANs) on the BNT Virtual Fabric 10 Gigabit Switch Module for IBM BladeCenter, Option part number 46C7191, may cause Data Center Bridging Protocol (DCBX) errors due to optional Link Layer Discovery Protocol (LLDP) Type Length Values (TLVs) being enabled by default.
For example, one might see the following log entries in the switch module event log:
| Jan 9 15:13:47 9.42.161.156 NOTICE
server: link down on port INT6 Jan 9 15:13:48 9.42.161.156 NOTICE server: link up on port INT6 Jan 9 15:13:50 9.42.161.156 NOTICE dcbx: Detected DCBX peer on port INT6 Jan 9 15:15:50 9.42.161.156 NOTICE dcbx: Peer on port INT6 stopped responding to DCBX message |
Also, attempting to add more VLANs may not be possible and could result in the BNT Virtual Fabric 10 Gigabit switch module returning the following event log entries:
| Jan 9 16:28:50 9.42.161.156 ERROR | cfg: Error: Please reconfigure port INT6's Optional TLVs in order to avoid sending incomplete LLDPDUs! The LLDP TLVs must fit in 1514 bytes |
| Jan 9 16:28:50 9.42.161.156 ERROR | mgmt: Error: Apply not done |
Affected configurations
The system is configured with one or more of the following IBM Options:
- BNT Virtual Fabric 10 Gigabit Switch Module for IBM BladeCenter, Option part number 46C7191, replacement part number 46C7194
This tip is not system specific.
This tip is not software specific.
The system has the symptom described above.
Solution
Update the BNT Virtual Fabric 10 Gb Switch Module for IBM BladeCenter to version 6.8.6 or higher.
The file is available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and operating system on IBM Support's Fix Central web page, at the following URL:
Workaround
Disable optional LLDP TLVs that are not being used. Optional TLVs in use are environment specific, and need to be determined on a case by case basis.
To disable optional LLDP TLVs on a per port basis, perform the following:
- Telnet to the switch.
- Open the Configuration menu by typing cfg and pressing Enter.
- Open the Layer 2 Menu by typing l2 and pressing Enter.
- Open the LLDP Menu by typing lldp and pressing
Enter.
- Open the LLDP port menu by typing port and pressing
Enter.
- Enter a port number, for example, INT1 for blade Slot 1.
- Enter the Optional TLVs Menu by typing tlv and pressing Enter.
- Disable the Optional TLV. For example, to disable the vlanname
TLV:
- Type vlanname and press
Enter.
- Type disabled and press
Enter.
- Type vlanname and press
Enter.
- Apply the configuration changes by typing apply and pressing
Enter.
- Save the configuration changes by typing save and pressing
Enter.
The following shortcut can be used for steps 2-8 above:
| /cfg/l2/lldp/port INT1/tlv/vlanname disabled |
Note: The optional TLVs vlanname and portprot add the most data in an Ethernet packet and are the recommended TLVs to disable first.
Additional information
By default, all LLDP optional TLVs are enabled in the BNT Virtual Fabric 10 Gigabit switch module. As more VLANs are associated with a given switch port, it increases the amount of administrative data that has to be included in each 1514 byte packet. If too much of this administrative data is in the packet, the switch ends up truncating the LLDP optional TLV data, which prevents the DCBX peer from responding to errors. By not including unnecessary LLDP optional TLVs such as vlanname and portprot, it frees up space inside each packet that is sent, thus allowing more VLANs to be created.
The switch firmware monitors how much administrative data it needs to include as VLANs begin to get created for a given port. Hence, it attempts to warn users and prevent them from creating too many VLANs in order to allow the DCBX peer to respond to messages.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
30 January 2019
UID
ibm1MIGR-5089172