OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 2 December 20, 2023 Updated the advisory to add to the workaround in the Resolution. 1 August 01, 2023 Original Document Release. On the HPE Edgeline e920 server with an HPE e920 10GbE 2p Network Mezzanine Kit on VMware ESXi 8.0, the network port of the mezzanine card will show as disconnected when a vSwitch is edited to an MTU value other than the 1500 default (or if it is created with a value other than the default). Changing the default 1500 MTU value of a vSwitch created on the network ports for the NVIDIA Mellanox ConnectX-6 LX 10GbE 2p Network Interface Card (NIC) will fail on the first attempt and succeed on the second attempt, but the host ports will display as "Line Down" (or disconnected) on the ESXi Host Client screen. This will occur when the mezzanine card is running firmware version 26.31.1014 and the driver is VMware ESXi 8.0 inbox.
Any HPE Edgeline e920 server blades with an HPE e920 10GbE 2p Network Mezzanine Kit (P40899-B21) installed in an HPE Edgeline EL8000 Chassis, and the Operating System (OS) environment is VMvisor-Installer-8.0-20513097.x86_64.
This issue will be resolved in a future release of HPE Edgeline. For the workaround, perform the steps for the following two procedures: 1st Procedure Perform the steps below to create the vSwitches with an MTU size of more than 1500 in Edgeline e920 server with NVIDIA Mellanox ConnectX-6 LX 10G 2p Mezz card: Log into the ESXi Host Client, navigate to Networking and click on the Virtual switches. Click "Add standard virtual switch" to create a new one. Since creating a new vswitch with an MTU size of more than 1500 will fail, create a vswitch with the default MTU size of 1500 and it will create successfully. For Example: Create vs1 with uplink vmnic1 and vs2 with uplink vmnic2. Click "vs1" and navigate to the "Edit" settings to modify the MTU size to a value higher than 1500, for example: 4000/5000/9000. This attempt will fail, and it changes the vmnic1 link status to "Down." (The link status will be refreshed by the ESXi Host Client.) Click on "Edit" settings again, and modify the MTU size to a value higher than 1500, for example: 4000/5000/9000. Now the MTU value can be changed to to higher than 1500. Repeat steps 4 and 5 for vs2. Reboot the ESXi host to bring the link status of vmnic1 and vmnic2 back to "Up." After the reboot, the vs1 and vs2 switches will have the uplink vmnic1 and vmnic2 with a link status UP with the required MTU size. Note : To delete the vs1 and vs2 switches with the MTU size of more than 1500, follow the steps below: Click on vs1, go to "Edit" settings, and click "Remove." This will fail with an error, and vs1 will not delete, but the "vmnic1" link status will go down after this. Change the MTU size of vs1 switch back to 1500. Go to the Edit settings and click on Remove. Now the vs1 will be able to be deleted. Continue to repeat the previous steps 1 through 3 to delete vs2. 2nd Procedure Downgrade the nmlx5-core/nmlx5-rdma driver version from version 4.23.0.31 to version 4.19.71.1-1 . Download the nmlx5_core 4.19.71.1 NIC Driver for Mellanox ConnectX-6 ethernet adapters from the VMware website. Store the extracted (Mellanox-nmlx5_4.19.71.1-1OEM.700.1.0.15525992_17850538-package.zip) on the ESXi datastore. Remove the inbox nmlx5-core and nmlx5-rdma 4.23.0.36 drivers with the force option: Reboot the host. Install the nmlx5-core and nmlx5-rdma 4.19.71.1 drivers using the extracted vib: Reboot the host. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts.Sign up for Support Alerts at the following URL: HPE Email Preference Center NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches and other support software downloads, refer to the Navigation Tips document. SEARCH TIP: For hints on locating similar documents on HPE.com, refer to the Search Tips document.
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
