Knowledgebase / FAQ - ip-connect GmbH
Knowledgeroot - Version: 0.9.9.5
Menü verstecken Menü ausklappen Menü neuladen Menü einklappen
Menü schliessen
  1.    (Zuletzt geändert von Gast an 15.02.2012 15:38:24)

Mittels vSphere-CLI können die ESXi 4 Hosts realtiv einfach upgedated werden.

Vorgehensweise:
1) Upgrade-ZIP-Paket von der VMware-Website auf einen Speicherort herunterladen, auf den die vSphere-CLI-Maschine zugreifen kann.
-> upgrade-from-ESXi4.0-to-4.1.0-0.0.build#-release.zip
Das Upgrade-ZIP-Paket enthält ein Bulletin “esxupdate” und ein Upgrade-Bulletin.

2) Alle virtuellen Maschinen ausschalten, die auf dem Host ausgeführt werden, und den
Host in den Wartungsmodus setzen.

3) Installieren des esxupdate-Bulletins durch Ausführung des folgenden Befehls auf der vSphere-CLIMaschine.
vihostupdate –server Hostname oder IP-Adresse -i -b Speicherort des ESXi-Upgrade-ZIP-Pakets -B ESXi410-GA-esxupdate

4) Installieren des Upgrade-Bulletins durch Ausführung des folgenden Befehls auf der vSphere-CLI-Maschine.
vihostupdate –server Hostname oder IP-Adresse -i -b Speicherort des ESXi-Upgrade-ZIP-Pakets -B ESXi410-GA

5) Überprüfung durch Ausführung des folgenden Befehls, ob die Bulletins auf dem ESXi-Host installiert wurden.
vihostupdate.pl –server Hostname oder IP-Adresse –query

6) Host neustarten.

 

Für ESXi 5 folgende Anleitung übernehmen:

 

01: Make sure you have the vMA 5.0 or the vCLI installed and configured or that you have ESXi Shell access on the ESXi 5 host.

 

02: Download the patch bundle directly from VMware Support. This download will be .zip file.  Do not extract it.

 

03: Upload the .zip file to a datastore that is accessible on the ESXi host you wish to update. The syntax below will use /vmfs/volumes/datastore1, and you may need to adjust as necessary. Note that the .zip file is uploaded to the ESXi host.

 

Note:  In the examples below, the syntax is specific for the vMA. Adjust accordingly, if you are using another approach.


04: Obtain local console access to the vMA and login with the vi-admin account.

 

05. To determine if the host needs to be placed in maintenance mode, issue the following command:

 

esxcli --server=10.10.10.10 --username=root software sources vib get -d /vmfs/volumes/datastore1/ESXi500-201109001.zip | grep "Maintenance Mode Required: True" 

 

06.  If grep returns "Maintenance Mode Required: True" results, then issue the following command to place the host in maintenance mode:

 

vicfg-hostops --server 10.10.10.10 --operation enter 

 

07. Verify that the host is in maintenance mode, by issuing the following command:

 

vicfg-hostops --server=10.10.10.10 --operation info 

 

Note: You could also use the vSphere Client to put the ESXi 5 host in maintenance mode.

 

08. To verify which VIBs are already installed on the ESXi 5 host, issue the following command:

 

esxcli --server=10.10.10.10 --username=root software vib list | more

 

09. To find out which VIBs are available in the depot (the downloaded .zip file), issue the following command:

 

esxcli --server=10.10.10.10 --username=root software sources vib list --depot=/vmfs/volumes/datastore1/ESXi500-201109001.zip | more

 

10. To update the ESXi 5 host with the VIBs included in the depot, issue the following command:

 

esxcli --server=10.10.10.10 --username=root software vib update --depot=/vmfs/volumes/datastore1/ESXi500-201109001.zip 

 

11. When the update is complete, verify the information presented. If prompted, reboot the ESXi 5 host by issuing the following command:

 

vicfg-hostops --server 10.10.10.10 --operation reboot

 

12. Verify the patch bundle was installed, by issuing the following command:

 

esxcli --server=10.10.10.10 --username=root software vib list | more

 

13. If applicable, take the ESXi 5 host out of maintenance mode using the vSphere Client or with the following command:

 

 

verschieben [Oben]

  2.--help    (Zuletzt geändert von rsch an 20.04.2011 06:58:09)

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>vihostupdate.pl --help

Synopsis: C:\Program Files (x86)\VMware\VMware vSphere CLI\bin\vihostupdate.pl OPTIONS


Command-specific options:
   --bulletin
    -B

             Parameter to specify the selective bulletin(s) to install. Use
             comma to specify multiple bulletins (eg. bulletin1,bulletin2).
             All bulletins will be installed if this option is not specified.

   --bundle
    -b

             Parameter to specify the location of the offline bundle.

   --install
    -i

             Install the host with selective bulletins from the bundle, the depot or local offline bundle.

   --list
    -l

             List the bulletins in the bundle or in the depot.

   --metadata
    -m

             Parameter to specify the location of the depot metadata.zip

   --nosigcheck
    -c

             Ignore integrity checking during install operation (unsupported).

   --query
    -q

             Query the bulletins that are already installed in the host.

   --remove
    -r

             Remove selective bulletins from the host.

   --scan
    -s

             Scan the host against the bundle or the depot for applicable bulletins.


Common VI options:
   --config (variable VI_CONFIG)
      Location of the VI Perl configuration file
   --credstore (variable VI_CREDSTORE)
      Name of the credential store file defaults to <HOME>/.vmware/credstore/vicredentials.xml on Linux and <APPDATA>/VMware/credstore/vicredentials.xml on Windows
   --encoding (variable VI_ENCODING, default 'utf8')
      Encoding: utf8, cp936 (Simplified Chinese), iso-8859-1 (German), shiftjis (Japanese)
   --help
      Display usage information for the script
   --passthroughauth (variable VI_PASSTHROUGHAUTH)
      Attempt to use pass-through authentication
   --passthroughauthpackage (variable VI_PASSTHROUGHAUTHPACKAGE, default 'Negotiate')
      Pass-through authentication negotiation package
   --password (variable VI_PASSWORD)
      Password
   --portnumber (variable VI_PORTNUMBER)
      Port used to connect to server
   --protocol (variable VI_PROTOCOL, default 'https')
      Protocol used to connect to server
   --savesessionfile (variable VI_SAVESESSIONFILE)
      File to save session ID/cookie to utilize
   --server (variable VI_SERVER, default 'localhost')
      VI server to connect to. Required if url is not present
   --servicepath (variable VI_SERVICEPATH, default '/sdk/webService')
      Service path used to connect to server
   --sessionfile (variable VI_SESSIONFILE)
      File containing session ID/cookie to utilize
   --url (variable VI_URL)
      VI SDK URL to connect to. Required if server is not present
   --username (variable VI_USERNAME)
      Username
   --verbose (variable VI_VERBOSE)
      Display additional debugging information
   --version
      Display version information for the script
 

verschieben [Oben]