Cisco ENIC and FNIC packages for VMware ESXi 5.1 and 5.5 contain the same bulletin ID

Products

• VMware

Issue/Introduction

Symptoms:

• When a VUM repository contains a VUM baseline with the VMware ESXi 5.1 or 5.5 version of the Cisco fiber channel NIC (fnic) driver version 1.5.0.45 or 1.6.0.4 or Cisco Ethernet NIC (enic) driver version 2.1.2.42 and you attempt to add a second version, VUM rejects the request.
  
• You see in the vmware.xml file the same Bulletin ID in the registered bundle and the bundle you are trying to load.
• VMware Update Manager does not load an updated bundle.
• Update Manager reports that an updated bundle is already present, even though it is not.

Cause

VMware Update Manager (VUM) uses a bulletin ID in the metadata files as a globally unique identifier for a VMware Installation Bundle (VIB) package. The same bulletin ID was used for two separate ENIC or FNIC driver packages built from the same source code with different package-level checksums.

This means when the VUM repository contains one of the FNIC/ENIC driver offline bundles and the user tries to import the other FNIC/ENIC driver offline bundle, the import of the second offline bundle fails. VUM reports that the driver already is present in the repository.

Cisco driver versions impacted by this issue:

• enic 2.1.2.42
• enic-2.1.2.38
  
• fnic 1.5.0.45
• fnic 1.6.0.5

Resolution

To resolve this issue, download the corrected driver packages from VMware Downloads.

Use VMware Update Manager to install them. Cisco and VMware have updated the driver packages, available at the Download VMware vSphere page.

ENIC drivers:

• enic-2.1.2.38
• enic-2.1.2.42

FNIC drivers:

• fnic-1.5.0.45
• fnic-1.6.0.5

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box