ESXi 3.5 to 4.1 upgrade

Similar Questions

• ESXi 5.1 to 5.5 upgrade

  Hi all

  I intend to spend any esxi 5.1 5.1 to our newly built 5.5 vCenter vCenter army.

  We not have distributed switches, SRM, Vmware view etc...
  Not also concerned historical data in vCenter 5.1

  What is the best way to do it?

  Here is my planned approach

  • Create new cluster on vCenter 5.5 that will even
    as cluster in vCenter 5.1.
  • Disconnect hosts in vCenter 5.1 and register
    ESXi host to vCenter 5.5
  • I guess when I do this standard will all be
    always available as it is esxi host specific not vcenter.
  • We have 5 guests clustered, so I intend to
    remove a host both the cluster and esxi 5.1 to 5.5 upgrade using Update Manager
    5.5 the new vCenter.
  • Given that I don't update facility, I'm not sure will
    switch support will be always there after upgrade. We use iscsi for storage
    and it uses a standard switch. If it is not available I can recreate after upgrade.
  • Anything that suggests on pit fall that I need attention in this plan, please suggest.

  Thank you...

  I did these migrations several times in the past and that you are having problems.

  What I usually do in such cases is to:

  • Disable HA in two groups (the current/old as well as new)
  • Make sure you of EVC is configured correctly to the new cluster (if necessary)
  • disconnect and remove all hosts (one by one) from the old server vCenter Server and add them to the new cluster
  • configure settings like HA cluster, DRS...
  • Once everything works as expected begin the upgrade of the host

  Be sure to reconfigure your backup software (and any other 3rd party software and Add-ons) after migrating to the new vCenter Server hosts.

  André

• Images IBM ESXi 4.1 to 5.5 upgrade

  The upgrade to ESXi 4.1 Patch 5 on 30-01 - 2012 Build #582267 with customization of IBM to VMware vSphere Hypervisor (ESXi) 5.5 with customization of IBM for VMware ESXi - 5.5.0 - 1746974-IBM - 20140428.iso image downloaded from the IBM site. When you attempt to upgrade using Update Manager 5.5 receive the following error:

  
  Unsupported configuration:

  Software modules oem-ibmcustomization oem-vmware-esx-drives-net-vxge oem-vmware-esx-drivers-scsi-3w-9xxx vmware-esx drivers-net be2net published by third-party providers are installed on the host computer. The upgrade of the host will remove these modules.
  

  The release notes for State 5.5:

  Migration of third-party Solutions
  You cannot migrate directly from third-party solutions installed on an ESX or ESXi host as part of an upgrade of the host. Architectural changes between 5.1 and 5.5 ESXi ESXi result in the loss of third-party components, and system instability. To perform these migrations, you can create an ISO file personalized with Image Builder. For more information on the upgrade of your third-party host performing all customizations, see the Upgrade vSphere documentation. For more information on the use of Image Generator to make a custom ISO, see vSphere Installation and configurationdocumentation.

  Does it mean that our IBM specific upgrade path is not supported? If so, the need for a new installation and then apply this ESXi host host profile?

  Thank you,-Jeff

  I received the following IBM:

  "As long as no additional VIBs have been added to the current image of VMware ESXi 4.x custom IBM installed on the host server, it is safe to force a migration to custom image 5.x because the VIBs of third parties that have been added to the original image by IBM have equivalents in the custom image ESXi 5.0."

  That said I think that we can proceed with the procedure of forced Migration to upgrade these hosts.

• After Esxi 5.1 USB passthrough problem upgrade to Esxi 6. 0 b

  Hello

  Recently, I upgraded my ESXi host from version 5.1 to 6.0.0.2809209. Passthrough ESXi 5.1 USB worked without problem. I updated 5.1 to 6.0 when usb smart card readers is connected. Now USB smart card readers did not appear on ESXi 6. 0b.

  I couldn't find any usb tethering in settings of the virtual computer .

  

  output file /var/log/USB.log

  
  

  2015 10-12 T 19: 30:10Z usbarb [33783]: VTHREAD initialize the main thread 3 "usbArb" pid 33783
  2015 10-12 T 19: 30:10Z usbarb [33783]: DictionaryLoad: could not open the file "/ usr/lib/vmware/config ': no such file or directory.
  2015 10-12 T 19: 30:10Z usbarb [33783]: preferences PREF file optional not found in/usr/lib/vmware/config. Using the default values.
  2015 10-12 T 19: 30:10Z usbarb [33783]: DictionaryLoad: cannot open the file '//.vmware/config': no such file or directory.
  2015 10-12 T 19: 30:10Z usbarb [33783]: found option preferences of PREF file in / / .vmware/config. Using the default values.
  2015 10-12 T 19: 30:10Z usbarb [33783]: deactivation of the preferences of the user PREF because disableUserPreferences is set.
  2015 10-12 T 19: 30:10Z usbarb [33783]: PREF cannot load the user's preferences.
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - PARAMETERS GLOBAL/usr/lib/vmware/settings
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - NOT PERSISTENT
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - USER PREFERENCES
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - default USER IS //.vmware/config
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - HOST by default IS/etc/vmware/config
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT libdir = ' / usr/lib/vmware. "
  2015 10-12 T 19: 30:10Z usbarb [33783]: authd.proxy.nfc = DICT ' vmware - pass: ha - nfc ".
  2015 10-12 T 19: 30:10Z usbarb [33783]: authd.proxy.nfcssl = DICT ' vmware - pass: ha-nfcssl. "
  2015 10-12 T 19: 30:10Z usbarb [33783]: authd.proxy.vpxa - nfcssl = DICT ' vmware - vpxa:vpxa - nfcssl.
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT authd.proxy.vpxa - nfc = "vmware - vpxa:vpxa - nfc.
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT authd.fullpath = "/ sbin/authd '.
  2015 10-12 T 19: 30:10Z usbarb [33783]: DICT - SITE by default IS/usr/lib/vmware/config
  2015 10-12 T 19: 30:10Z usbarb [33783]: USBArb: error in ' / etc/vmware/usbarb.rules' at line 1:0, ' [' or ' {' expected near end of file.}]
  2015 10-12 T 19: 30:10Z usbarb [33783]: VMware USB Arbitration Service Version 13.1.14
  2015 10-12 T 19: 30:10Z usbarb [33783]: USBArb: trying to connect to an arbitrator on/var/run/vmware/usbarbitrator-socket.
  2015 10-12 T 19: 30:10Z usbarb [33783]: SOCKET create new socket, connect to/var/run/vmware/usbarbitrator-socket
  2015 10-12 T 19: 30:10Z usbarb [33783]: SOCKET connection failed, error 2: no such file or directory
  2015 10-12 T 19: 30:10Z usbarb [33783]: USBArb: unable to connect to the existing arbitrator.
  2015 10-12 T 19: 30:17Z usbarb [33783]: USBArb: UsbArbPipeConnected: connected to the client socket: 12
  2015 10-12 T 19: 30:17Z usbarb [33783]: USBArb: 34213 Client connected (version: 6)
  2015 10-12 T 19: 54:37Z usbarb [33783]: USBArb: customer closing, error: 2
  2015 10-12 T 19: 54:37Z usbarb [33783]: USBArb: 34213 Client disconnected

  lsusb and tail f /var/log/vmkernel.log | grep-i USB

  output of commands is empty.

  
  

  usbarbitrator chkconfig - list

  usbarbitrator on

  How can I solve this problem?

  Thank you

  OK I solved my problem.

  (1) I remove material passthrough.

  (2) I have been fallow in Re: error Usb referee 6. and 7. advice.

  And I am able to reach USB CCID of Esxi 6.0 virtual machine host.

  Thank you

• How can I reinstall / store data recovery an ESXi 4.1 lost during an upgrade to 5.5?

  I was running a host of ESXi 4.1 on a Dell T110 II with two RAID, a managed arrays by the controller integrated RAID that contained the system of ESXi and a small data store (channel) and the other controlled by a 6405e Adaptec controller which contained my main data store (BunkerHill). In the process of upgrading from 4.1 to ESXi 5.5, I forgot to include the drivers for the Adaptec 6405e controller and even if the upgrade of the host, he did not see the BunkerHill data store.

  I downloaded and installed the VIB for the controller 6405e and after restart the host ESXi 5.5 shows the Adaptec RAID under storage adapters, but the BunkerHill data store is still not visible and all virtual machines guests appearing on this show as unknown in the inventory. The channel data store and two invited VMS it holds are visible. Below a part of the kernel log is filtered on the RAID controller device name.

  I would like to get the recognizable BunkerHill data store before continuing the upgrade and would be grateful if someone could point me in the right direction (KB article, display, etc. that explains what I do). I need to reinstall 4.1 on the work of RAID (ESXi 5.5 and channel data bank) and then trying to reconnect the main data store, or are there changes I can do from the console to manually get the market things?

  Tips are appreciated,

  Thank you

  
  

  rSid

  (2015 06-16 T 03: 39:59.758Z cpu1:33296) PCI: 1095: 0000:03:00.0 named "vmhba2" (has ")

  (2015 06-16 T 03: 40:08.781Z cpu0:33415) VMK_PCI: 395: 0000:03:00.0 device name: vmhba2

  (2015 06-16 T 03: 40:08.781Z cpu0:33415) DMA: 612: DMA 'vmhba2' engine, created using the Mapper "DMANull."

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 976: path 'vmhba2:C0:T0:L0': seller: model "Adaptec": "BukerHill" Rev: 'V1.0 '.

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 979: path "vmhba2:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 1105: path 'vmhba2:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:08.782Z cpu0:33415) ScsiScan: 1503: Add the path: vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:09.238Z cpu1:33415) ScsiNpiv: 1510: GetInfo for adapter vmhba2, [0x4108984b0280], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2015 06-16 T 03: 40:19.582Z cpu2:33177) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba2:C0:T0:L0 '.

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:19.596Z cpu0:33177) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba2:C0:T0:L0 for the device "unregistered".

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 7420: get VPD 83 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 7456: get VPD 86 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 03: 40:19.596Z cpu3:33177) ScsiDeviceIO: 6170: QErr setting for mpx.vmhba2:C0:T0:L0 of the unit could not detect. Failure of the error.

  (2015 06-16 T 03: 40:19.839Z cpu3:33177) SFS: 5091: pilot no. FS claimed device 'mpx.vmhba2:C0:T0:L0:1': not supported

  (2015 06-16 T 03: 40:19.839Z cpu3:33177) ScsiDevice: 3443: device successfully registered "mpx.vmhba2:C0:T0:L0" from plugin "NMP" of type 0

  (2015 06-16 T 03: 40:24.005Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:24.352Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:24.676Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:29.840Z cpu0:33780) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:29.990Z cpu0:33785) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:30.177Z cpu0:32908) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 40:30.177Z cpu0:32908) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 40:30.194Z cpu2:33786) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:36.672Z cpu3:34032) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8089cdc0, 34344) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089cdc0) 0 x 85, CmdSN 0x0 34344 to dev 'mpx.vmhba2:C0:T0:L0' world not a sense H:0 x D:0 x 2 P:0 x 0 0 data not valid: 0 x 5 0x20 0x0.

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x4d (0x412e8089cdc0, 34344) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 03: 40:41.839Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089cdc0) 0x4d, CmdSN 0x1 worldwide 34344 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 03: 42:04.870Z cpu1:32909 opID = affe9c27) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 42:04.870Z cpu0:32909 opID = affe9c27) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 42:04.939Z cpu2:34420 opID = f965f306) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 43:25.893Z cpu0:32907 opID = de9d40eb) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 43:25.894Z cpu0:32907 opID = de9d40eb) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 43:25.976Z cpu1:34414 opID = 12fa472c) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 03: 43:39.199Z cpu1:32906 opID = f8418990) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 03: 43:39.199Z cpu1:32906 opID = f8418990) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 03: 43:39.272Z cpu0:34043 opID = 8eb97c3d) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 32:43.729Z cpu1:33296) PCI: 1095: 0000:03:00.0 named "vmhba2" (has ")

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) VMK_PCI: 395: 0000:03:00.0 device name: vmhba2

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) DMA: 612: DMA 'vmhba2' engine, created using the Mapper "DMANull."

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 976: path 'vmhba2:C0:T0:L0': seller: model "Adaptec": "BukerHill" Rev: 'V1.0 '.

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 979: path "vmhba2:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 1105: path 'vmhba2:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 32:51.512Z cpu0:33415) ScsiScan: 1503: Add the path: vmhba2:C0:T0:L0

  (2015 06-16 T 04: 32:51.940Z cpu1:33415) ScsiNpiv: 1510: GetInfo for adapter vmhba2, [0x4108984b0280], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2015 06-16 T 04: 33:02.185Z cpu2:33177) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba2:C0:T0:L0 '.

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba2:C0:T0:L0 for the device "unregistered".

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiDeviceIO: 7420: get VPD 83 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 04: 33:02.199Z cpu0:33177) ScsiDeviceIO: 7456: get VPD 86 inquiry for device "mpx.vmhba2:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2015 06-16 T 04: 33:02.199Z cpu1:33177) ScsiDeviceIO: 6170: QErr setting for mpx.vmhba2:C0:T0:L0 of the unit could not detect. Failure of the error.

  (2015 06-16 T 04: 33:02.439Z cpu0:33177) SFS: 5091: pilot no. FS claimed device 'mpx.vmhba2:C0:T0:L0:1': not supported

  (2015 06-16 T 04: 33:02.439Z cpu0:33177) ScsiDevice: 3443: device successfully registered "mpx.vmhba2:C0:T0:L0" from plugin "NMP" of type 0

  (2015 06-16 T 04: 33:06.593Z cpu2:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:06.992Z cpu0:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:07.322Z cpu1:33177) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.467Z cpu2:33780) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.608Z cpu2:33785) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:12.791Z cpu1:32908) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 33:12.791Z cpu1:32908) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 33:12.807Z cpu0:33786) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:21.919Z cpu2:34032) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8089db80, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089db80) 0 x 85, CmdSN 0x0 34335 to dev 'mpx.vmhba2:C0:T0:L0' world not a sense H:0 x D:0 x 2 P:0 x 0 0 data not valid: 0 x 5 0x20 0x0.

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x4d (0x412e8089db80, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 04: 33:27.109Z cpu2:32787) ScsiDeviceIO: 2338: Cmd (0x412e8089db80) 0x4d, CmdSN 0x1 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 04: 54:09.845Z cpu0:32906 opID = 372194ec) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 54:09.845Z cpu0:32906 opID = 372194ec) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 54:36.638Z cpu1:32910 opID = 6037ca3e) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 54:36.638Z cpu1:32910 opID = 6037ca3e) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 54:36.713Z cpu0:34040 opID = 2ffcf7c7) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 04: 55:22.146Z cpu0:32909 opID = a7c2c9af) ScsiUid: 273: "vmhba2:C0:T0:L0" path does not support VPD device Id page.

  (2015 06-16 T 04: 55:22.146Z cpu0:32909 opID = a7c2c9af) VMWARE SCSI Id: Id for vmhba2:C0:T0:L0

  (2015 06-16 T 04: 55:22.218Z cpu3:34041 opID = c15706cb) LVM: 8389: found device mpx.vmhba2:C0:T0:L0:1 can get to be a snapshot:

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8084d6c0, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8084d6c0) 0 x 85, CmdSN 0x3 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 03:27.938Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8084d6c0) 0x4d, CmdSN 0x4 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e80875440, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e80875440) 0 x 85, CmdSN 0x6 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 33:28.102Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e80875440) 0x4d, CmdSN 0 x 7 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 50:56.541Z cpu0:47363) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 51:17.866Z cpu1:47425) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x10

  (2015 06-16 T 05: 52:04.275Z cpu2:32787) WARNING: ScsiDeviceIO: 1223: mpx.vmhba2:C0:T0:L0 camera performance has deteriorated. Latency of I/O increased value average of 414 microseconds to 13216 microseconds.

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8083a380, 48445) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8083a380) 0 x 85, CmdSN 0x9 worldwide 48445 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  (2015 06-16 T 05: 53:30.257Z cpu0:32785) ScsiDeviceIO: 2338: Cmd (0x412e8083a380) 0x4d, CmdSN 0xa worldwide 48445 to dev 'mpx.vmhba2:C0:T0:L0' has no meaning H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 05: 58:07.182Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:07.182Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:07.183Z cpu2:49346) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x20

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 05: 58:28.217Z cpu0:49408) WARNING: ScsiDeviceIO: 7006: IEC device "mpx.vmhba2:C0:T0:L0" a bad ECODE page: 0x0

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e8088b8c0, 50440) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) ScsiDeviceIO: 2338: Cmd (0x412e8088b8c0) 0 x 85, CmdSN 0xc worldwide 50440 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 00:42.324Z cpu1:32786) ScsiDeviceIO: 2338: Cmd (0x412e8088b8c0) 0x4d, CmdSN 0xd worldwide 50440 to dev 'mpx.vmhba2:C0:T0:L0' has no meaning H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0 x 85 (0x412e80896800, 34335) dev 'mpx.vmhba2:C0:T0:L0' on the way 'vmhba2:C0:T0:L0' failed: H:0 x D:0 x 2 P:0 valid 0 x 0 sense-data: 0 x 5 0x20 0x0. Bill: NO

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) ScsiDeviceIO: 2338: Cmd (0x412e80896800) 0 x 85, CmdSN 0xf worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0 20 x 0 x 0.

  (2015 06-16 T 06: 03:28.267Z cpu3:32788) ScsiDeviceIO: 2338: Cmd (0x412e80896800) 0x4d, CmdSN 0x10 worldwide 34335 to dev 'mpx.vmhba2:C0:T0:L0' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 5 0x20 0x0.

  Hello

  looks like resignaturing volumes data store could help.

  Here is another discussion of a user to get similar errors: Vmware 5.5 Upgrade breaks access the VMFS data store (kind of)

  More information: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011387 and literature vSphere Documentation Center

  cykVM

• host ESXi 4.1 to 5.5 upgrade

  Hi all, hope this helps.

  I installed a new 5.5 vcenter and always running a vcenter 4.1, running both at the same time, I have migrated a crowd of 4.1 through to my platform of 5.5 and want to update the host to 5.5 (I have a license), my question is, will this affect my other storage on the san, other hosts on 4.1 run here , and I do not wish to upgrade this one 5.5 if it will affect the other storage on the old vcenter (things always work) he seem quite simple to do, but not sure about that something and can not afford to make the mistake with the old esx environment...

  You can upgrade the host ESXi 4.1 managed by vCenter 5.5 without problems. For more safety, unplug the host HBA when you perform the upgrade if you use CF. If I understand correctly, both the upgrade to 5.5 ESXi and ESXi 4.1 hosts existing use same data warehouses. The only drawback I see is after the upgrade to 5.5 ESXi host, do not improve data warehouses of VMFS3 to VMFS5 so as not to affect the environment 4.1 existing.

• ESXi (free) 4.1-> 5.1 upgrade?

  I currently have (installable, unincorporated) ESXi hypervisor 4.1 FREE edition with a license that had been generated by a person (no access to this account of people more)

  First of all, I want to upgrade to the latest 5.1 ESXi (hypervisor ONLY).

  1. the ESXi 5.1 is still available for free download?

  2. can I put my Server 4.1 existing "on-site" machine 5.1 without losing my configs? (I think it's possible)

  3. I have a free trial period of 60 days where I can use the advanced features such as the API management with write capabilities?

  4. I can then buy an essential Kit and making my 5.1 trial permanent newly converted (with vCenter management as available with Essestial)

  Thank you

  1. you can register for a free license of ESXi VMware vSphere Hypervisor (ESXi) 5

  2. basically, Yes. ESXi 5 allows interactive upgrades from the CD. Make sure that your hardware is supported. (http://www.vmware.com/go/hcl)

  3. I'm not sure if an upgrade will be renewed the evaluation period. I think that it will not. However, you could just rin "(starry VMFS) Install" and save the virtual machines again to the inventory after re-configuration of the host.

  4. Yes, you can change the license key. The binaries are the same for free and paid edition.

  André

• ESXi v5.0 to v5.1 - upgrade or install - what and why?

  I'm a newbie to ESXi responsible of three Dell Poweredge with two to six computers virtual servers on each host. Each host has two data warehouses and boot from a USB key using hard disk emulation.

  I update interactively using a DVD with iso serious on it.

  One of the given choices is to install (default) or upgrade.

  My experience in the PC world, when given that choice when installing an MS OS, I would opt for a new installation or an upgrade, especially to keep the ghosts and help isolate problems that may arise.

  What are the differences between the two, and why should I choose one over the other?

  If I install, I have access to existing data warehouses and the virtual machines on them? What parameters, if any, I'm likely to need to reapply?

  What are the disadvantages of an upgrade?

  All advise is greatly appreciated.

  Thank you.

  Yes, with the option to upgrade, the settings will be migrated to the new version.

  André

• ESXi 4.0 (free version) to upgrade to ESXi 4.1 (or 5?)

  I contacted the licenses support who told me that I was using the free version, and that the 4 4.1 update was not available.

  He said he thought that it would be possible to download the 4.1 update 3 installable and who would work to upgrade.  Is this true?

  I'm basically just trying get the USB so my Backup Exec Server passthrough feature will keep panicking because I'm trying to backup over the network.

  Now there is always a small risk to change a running system, so the best is to check that you have a good backup.

  Anyway, the ESXi 5 installation CD will discover the installed version and ask you what to do. The options are an upgrade of the host or installation (with or without preserving the existing data store).

  André

  PS: Do not try with the ESXi 4.1 installation CD. This will overwrite the installation disc!

• ESXi 4.0 to 5.0 upgrade

  First of all the part I: good subject?

  HY,

  First part II: I'm new to VMware... Be prepared to explain the basics of... (I'm just learning by using and now need some more general information about the update process... to understand what the idea)

  I have 2 physical servers. One with ESXi 4.0 and the other with ESXi 4.1. On these systems of ESXi, I run a total of 10 servers. To manage them and all servers on them, I use two separate vSphere customers.

  Now I want to move to ESXi 5.0 and I don't know which way I have to choose...

  The simplest way seemes to vCenter Update Manager. But I do not have a vCenter. The first question is: should I buy a just save some time on the upgrade of my virtual "sphere"...? (Q1) Is there an update for vSphere Client Manager? (Q2)

  What are the other options? (Q3) so I have no vCenter should I do with the command line? (Q4)

  If you would like to recommend buying a vCenter I have a few questions:

  -Cannot run vCenter on the ESXi which should be updated... right? (because it cannot update its own ESXi host) (Q5)

  -I can run vCenter since a normal Dektop PC (not as a virtual machine)... right? (Q6)

  A few Questions about the update process:

  We always have an ESXi host with some servers on this... We must therefore update ESXi as well as all the servers that are running on it... (in addition, we need update vCenter and vSphere Client)

  Here is how I would do or how I understand the process: (with vCenter)

  (1) install vCenter 5.1 (which is compatible with 4.x and 5.x) on a Dektop PC and connect to my ESXi 4.0

  (2) install for my vCenter Update Manager...

  3) update ready for ESXi with UpdateManager

  4) update ready for all virtual machines with UpdateManager

  (4) start updates

  These statements are correct?

  -Can I update my ESXi and my VM automatically when I use and properly configure the Update Manager (Q7)

  -l'UpdateManager can roll automatically when an update fails? (but what when the ESXi update was ok, but some of the virtual machine cannot lie?) (Q8)

  Or... Would you recommend to separately update?

  -copy all the VM to a new location

  -convert the virtual machine is there to 5.0

  -ESXi 5.0 update and bind the new data store (where is all VM 5.0) and then test the 5.0 VM on the new 5.0 ESXi... if ok remove the old data store 4.0 (and if wanted to move the 5.0VM back to the old data store)... If NOK reinstall ESXi 4.0 and bind old data store where is all 4.0 VM...

  If you want, you can use the 'Qx' legend behind the question to answer a specific Question...

  Thank you very much in advance for your help!

  UPGRADE to ESXi:

  I checked again, the documentation and it looks really is possible to upgrade a host which was previously installed with ESXi 3.5 upgrade to ESXi 4 then 5 ESXi. I've never done, but in all cases the old hardware was not supported for the latest version of ESXi.

  In any case, the problem is not related to the VMFS version, but rather to the layout of the partition. ESXi 3.5 created 2 partitions bootbank with 48 GB each and with ESXi 4/5 the size of this partition must be of 250GB.

  I say try the interactive CD upgrade, but make sure you have a current backup of your virtual machines.

  UPGRADE of the virtual computer:

  The option to upgrade virtual hardware displayed only for virtual machines with older versions of hardware. If you want to see what it looks like, create a virtual dummy with HW version 4 machine by selecting "custom" in the installation wizard.

  Last UPDATED (general):

  Except for the order of upgrade of the tools and HW version, it seems ok. First upgrade tools to ensure that the virtual machine uses drivers required for the hardware upgrade.

  André

• ESXi 4.0 to 4.1 upgrade - cannot access the client

  Hi all, I'm quite new to VMware, I have a server I just start, it's a physical server for VMware Vsphere hypervisor, Esxi 4.0 on it and I am unable to connect to the machine using the clients that you download from the web interface as 4.0 does not seem to work because of the update of the .NET framework.

  To remedy this, I need to upgrade the server to 4.1 but my question is this... How change the server if I can't connect to the server using the client?, is there another way?

  Any help would be greatly appreciated

  Welcome to the VMware forums communities.

  For the client error this might help - http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vsphere-client-error-parsing-the-server-server-ip-clients-xml-file-login-will-continue-contact-your-system-administrator.html.

  To update the host, you can use (vCLI) vSphere command-line Interface.  You can download that from the VMware web site.

  (1) use the command of the vicfg-hostops put the host in maintenance mode - http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vicfg-hostops.html

  (2) use vihostupdate to upgrade your host - http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vihostupdate.html.

• Details on the VMA for free ESXi and ESXi 4.0 to 4.1 upgrade

  Hi all

  I recently did a upgrade to ESXi 4.0 U1 to ESXi 4.1 (and before doing so did not noticed that MAS will be more usable in 4.1). I wanted to just make sure that there is currently no way to using VMrun to automate the decommissioning and snapshot and reboot of the Guest OS on ESXi 4.1 and that there is not just an error in my code?

  vmrun h https://ESXI_SERVER/sdk u root Pei _PASSWORD_ t stop server "VM_NAME" "" sweet

  I work for a non-profit and my budget is tight at best (around $150.00 USD) per year for this project. My only choice is to roll back to 4.0 U1?

  Brent cordially

  When you say vMA will be more usable in 4.1, what do you mean by that? If you have upgraded to vSphere 4.1 and you want to use vMA, then you must download the version 4.1 of vMA compared to version 4.0.

  If you are referring to the license "bug" to VIX, VIX releases allowing yet it works on ESXi free is VIX 1.6.2 but the problem has also been fixed on the side of ESX (i) of things from 4.1. If you rely on this feature, you can return to 4.0.x.

  That said, you always have the option to use the Busybox Console (Tech Support Mode) to manage and perform various host and virtual machine using vimshoperations, it works with both a licensed version and free ESXi as the commands are executed within TSM and this could be an alternative without having to demote ESXi

• The upgrade to ESXi 4.0.261974 to ESXi 4.1.0 errors with "upgrade package validation failed"

  Hello

  I'm trying to upgrade a host 4, 0.x ESXi 4.1 using the vSphere host update utility WSXi. First, it downloads the patches as expected, I select the host, and select "Upgrade of home", and then I select the file "upgrade - ESXi4.0 - to-ESXi4.1.xxxxxx.zip" I downloaded. After a while, I get the message "upgrade package validation failure (not to read the metadata of upgrade file that is located in a folder temporary users where it was unzipped to)" and the update will fail. I tried with the client installed on an XP and a box of Windows 7 with the same question, and I tried a new download without any positive result. What I am doing wrong?

  Thanks for your help.

  See if that helps

  http://blog.vmpros.nl/2010/07/15/VMware-failed-to-read-the-upgrade-package-metadata-XML-upgrading-to-ESXi-4-1/#more-2953

• ESXi 4 ESX 4 Update 1 upgrade

  Hello

  I have here a typical situation. We rotated 2 standalone ESXi 4 with VM and templates stored in the local data warehouses. We finally decided to upgrade to ESX 4 update 1 to be able to use the service console to use most of the features of the CLI.

  The ESXi 4 has 2 data warehouses locally that contains templates of a store of data and the virtual computer on the other. It is important for us to have the operation of the virtual machine. We do not have a shared storage.

  We have obtained the licenses now and want to spend ESXi ESX 4update 4 1. Is this possible? If so, how and if not, what would be the alternatives?

  All entries would be greatly appreciated.

  Thank you

  There is no option to migrate since ESXi 4 to ESX 4.

  concerning

  Maniac

• ESXi 3.5 to ESX 4 upgrade?

  Sorry if this is a stupid question, but I'll ask anyway...

  You can switch ESXi 3.5 to ESX4 (not ESXi4)?

  My situation is this, I find backup or image of virtual machine software is not compatible with ESXi versions so I have to run ESX.  I am currently running VI3 with two ESXi hosts.  I'll be updating my Virtual Center to vSphere and my hosts to ESX4 and just want to know if the upgrade of the ESX host can be done in a single step or I have to do a fresh install of ESX4 on each host as they are currenty ESXi running.

  TIA - Steve

  Steve, please note, if you go for the new installation in the mod text or graphical user interface, all the partitions\data (including VMFS) in the disk\LUN where you install will be deleted. There is no option to preserve the VMFS volumes in the installer of GUI\Text 4.0. So take the back of your virtual machines front of new installation OR opt for an installation by script. Installation script has the ability to preserve vmfs datastore.

  : +: VCP, RHCE, EMCPA.