VMware vSphere

 View Only
  • 1.  Procedure check for upgrading to ESXi 6.5

    Posted Aug 01, 2018 04:56 PM

    Hello all,

    I am in the process of trying to upgrade a stand-alone UCS C240 M3S server from ESXi 5.5 to 6.5 and have run into issues.

    When trying to upgrade using "esxcli software profile update -d path/file.zip profile" I get a DependancyError with the following:

    [DependencyError]

    VIB Cisco_bootbank_net-enic_2.1.2.42-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB Cisco_bootbank_net-enic_2.1.2.42-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB VMware_bootbank_net-qlge_1.0.0.47-1vmw.500.0.0.406165 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB cisco_bootbank_scsi-fnic_1.6.0.5-1OEM.500.0.0.472560 requires com.vmware.libfcoe-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB Intel_bootbank_net-ixgbe_3.18.7-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB cisco_bootbank_scsi-fnic_1.6.0.5-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB cisco_bootbank_scsi-fnic_1.6.0.5-1OEM.500.0.0.472560 requires com.vmware.libfc-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB VMware_bootbank_net-qlge_1.0.0.47-1vmw.500.0.0.406165 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB cisco_bootbank_scsi-fnic_1.6.0.5-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB QLogic_bootbank_scsi-qla4xxx_634.5.26.0-1OEM.500.0.0.472560 requires com.vmware.iscsi_linux-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    VIB Intel_bootbank_net-ixgbe_3.18.7-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB QLogic_bootbank_scsi-qla4xxx_634.5.26.0-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

    VIB QLogic_bootbank_scsi-qla4xxx_634.5.26.0-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

    Please refer to the log file for more details.

    Digging through the various forum posts here it seems like I have several VIBs that either need to updated or removed.  Following another forum post I ran the following two commands with these results:

    ~ # esxcli network nic list

    Name     PCI Device     Driver  Link  Speed  Duplex  MAC Address         MTU  Description

    -------  -------------  ------  ----  -----  ------  -----------------  ----  -------------------------------------------------

    vmnic0   0000:002:00.0  igb     Up     1000  Full    f0:7f:06:c4:1a:56  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic1   0000:002:00.1  igb     Down      0  Half    f0:7f:06:c4:1a:57  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic10  0000:006:00.2  igb     Down      0  Half    a0:36:9f:4e:df:ee  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic11  0000:006:00.3  igb     Down      0  Half    a0:36:9f:4e:df:ef  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic2   0000:002:00.2  igb     Down      0  Half    f0:7f:06:c4:1a:58  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic3   0000:002:00.3  igb     Down      0  Half    f0:7f:06:c4:1a:59  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic4   0000:004:00.0  igb     Down      0  Half    a0:36:9f:52:df:30  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic5   0000:004:00.1  igb     Down      0  Half    a0:36:9f:52:df:31  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic6   0000:004:00.2  igb     Down      0  Half    a0:36:9f:52:df:32  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic7   0000:004:00.3  igb     Down      0  Half    a0:36:9f:52:df:33  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic8   0000:006:00.0  igb     Up     1000  Full    a0:36:9f:4e:df:ec  1500  Intel Corporation I350 Gigabit Network Connection

    vmnic9   0000:006:00.1  igb     Down      0  Half    a0:36:9f:4e:df:ed  1500  Intel Corporation I350 Gigabit Network Connection

    ~ #

    ~ # esxcfg-scsidevs -a

    vmhba0  megaraid_sas      link-n/a  unknown.vmhba0                          (0:130:0.0) LSI / Symbios Logic MegaRAID SAS Fusion Controller

    ~ #

    It appears that I am only using the "net-igb" and "scsi-megaraid-sas" device drivers, of which neither are showing an error.

    In looking at the VIBs that are included with the Cisco Custom 6.5 U2 (build 8294253) zip file, it looks like I can update the following using the "esxcli software vib update -d path/file.vib" command:

    VMW_bootbank_net-enic_2.1.2.38-2vmw.650.0.0.4564106.vib

    INT_bootbank_net-ixgbe_4.4.1-1OEM.600.0.0.2159203.vib

    CSCO_bootbank_scsi-fnic_1.6.0.37-1OEM.600.0.0.2494585.vib

    VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.650.0.0.4564106.vib

    And then remove the others which are not in use and may be legacy using the "esxcli software vib remove -n vib-name" command:

    net-qlcnic

    net-qlge

    scsi-qla2xxx

    After this is done, I can then try and run the ESXi upgrade again.

    So the big question is... is my logic / process anywhere even close to being correct?  Wanting to make sure I'm on the right track before trying this.



  • 2.  RE: Procedure check for upgrading to ESXi 6.5
    Best Answer

    Posted Aug 01, 2018 05:07 PM

    Welcome to the Community,

    unless you are using drivers other than those in Cisco's customized ESXi image, you may run the upgrade like this:

    esxcli software sources profile list -d /vmfs/volumes/datastore1/Patches/<Imagename>.zip

    esxcli software profile install -d /vmfs/volumes/datastore1/Patches/<Imagename>.zip -p <Profile-Name-from-previous-command> --ok-to-remove --dry-run

    "--ok-to-remove" will ensure that obsolete vibs will be removed

    "--dry-run" can be used to test what the command will do. Once satisfied, run the command again without this option.


    André



  • 3.  RE: Procedure check for upgrading to ESXi 6.5

    Posted Aug 05, 2018 12:30 AM

    Hello André,

    Finally had a maintenance window long enough to bring things down and give your esxcli command adjustments a try (install instead of update, and using the --ok-to-remove flag), and it worked like a charm.  Thank you so much for replying, I've been banging my head on this every Saturday for the last month.