Link to home
Start Free TrialLog in
Avatar of Pau Lo
Pau Lo

asked on

vCenter Change Control

1) Do you put all patch updates released for esxi through a formal change control process?
2) Is there an easy way perhaps in vcenter to see the dates patches had been applied to esxi hosts (to help track back to change control system to ensure it went through change control)
3) do you have the luxury of test esxi hosts to test the updates on before applying to production servers
4) have you every experienced any issues with applying esxi patches to production systems?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Pau Lo
Pau Lo


in relation to 4, how do you get around this, i.e revert to backup and not apply the patch again? or report the issues to vmware and hope they drebug their updates?
Avatar of Pau Lo


for 2, I appreicate this lists current build, I was more after a patch history log to show what  patches were applied on what date....
2.) esxcli software vib list at the console will show the following patches and install date

Name                           Version                                Vendor    Acceptance Level  Install Date
-----------------------------  -------------------------------------  --------  ----------------  ------------
misc-cnic-register             1.78.1.v55.7-1OEM.550.0.0.1198611      Broadcom  VMwareCertified   2013-12-11
net-bnx2                       2.2.3t.v55.7-1OEM.550.0.0.1198611      Broadcom  VMwareCertified   2013-12-11
net-bnx2x                      1.78.28.v55.2-1OEM.550.0.0.1198611     Broadcom  VMwareCertified   2013-12-11
net-cnic                       1.78.12.v55.6-1OEM.550.0.0.1198611     Broadcom  VMwareCertified   2013-12-11
net-tg3                        3.133d.v55.1-1OEM.550.0.0.1198611      Broadcom  VMwareCertified   2013-12-11
scsi-bnx2fc                    1.78.16.v55.4-1OEM.550.0.0.1198611     Broadcom  VMwareCertified   2013-12-11
scsi-bnx2i                     2.78.11.v55.4-1OEM.550.0.0.1198611     Broadcom  VMwareCertified   2013-12-11
dell-configuration-vib         5.5-0A01                               Dell      PartnerSupported  2013-12-11
dell-eql-host-connection-mgr   1.2.0-352701                           Dell      VMwareAccepted    2013-12-17
dell-eql-hostprofile           1.2.0-352701                           Dell      VMwareAccepted    2013-12-17
dell-eql-routed-psp            1.2.0-352701                           Dell      VMwareAccepted    2013-12-17
elxnet                         10.0.575.7-1OEM.550.0.0.1198611        Emulex    VMwareCertified   2013-12-11
ima-be2iscsi                  Emulex    VMwareCertified   2013-12-11
lpfc                           10.0.575.8-1OEM.550.0.0.1198611        Emulex    VMwareCertified   2013-12-11
scsi-be2iscsi                 Emulex    VMwareCertified   2013-12-11
net-igb                        Intel     VMwareCertified   2013-12-11
net-ixgbe                      3.18.7-1OEM.550.0.0.1198611            Intel     VMwareCertified   2013-12-11
scsi-mpt2sas           LSI       VMwareCertified   2013-12-11
NetAppNasPlugin                1.0-21                                 NetApp    VMwareAccepted    2014-09-25
ima-qla4xxx                    500.2.01.31-1vmw.0.3.040121            QLogic    VMwareCertified   2013-12-11
net-qlcnic                     5.5.164-1OEM.550.0.0.1198611           QLogic    VMwareCertified   2013-12-11

4). We rollback, to the previous version. We then test this build if available in isolation, to check and confirm the issue, and then escalate to VMware Support.