Skip to main content

Upgrade ESXi 6.5 using CLI command in seconds

 Hello All,


This is my first blog after decided to shutdown soon known forum egyeng.com and transfer posts to the blog.

I welcome you and wish you a great career, It will be my pleasure when you following me in blogs here.

You could upgrade ESXi in few seconds using CLI commands.

Please use offline bundle of ESXi version 6.5 , you could upload it directly to one of datastores or attach it as ISO file to console and then copy it to datastore.

1. after attach ISO to CD, then mount it in ESX via CLI.
To find the device reference of your CDROM:
esxcfg-mpath -l
Example output:
Code:
ide.vmhba32-ide.0:0-mpx.vmhba32:C0:T0:L0
   Runtime Name: vmhba32:C0:T0:L0
   Device: mpx.vmhba32:C0:T0:L0
   Device Display Name: Local TEAC CD-ROM (mpx.vmhba32:C0:T0:L0)
    State: active
   Transport: ide
Load the iso9660 module with this command:
vmkload_mod iso9660

Mount the CDROM using the device determined earlier with esxcfg-mpath -l:
/sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba32:C0:T0:L0
The CDROM will be mounted under /vmfs/volumes/ [CDROM Label] /



2. You need to know the ISO profile using below command
Code:
esxcli software profile update -p ESXi-6.5.0-20170702001-standard -d /vmfs/volumes/SCSIDatastore1/UPDATE~1.ZIP
Code:
You will find output like below
Name                              Vendor        Acceptance Level
--------------------------------  ------------  ----------------
ESXi-6.5.0-20170701001s-no-tools  VMware, Inc.  PartnerSupported
ESXi-6.5.0-20170702001-no-tools   VMware, Inc.  PartnerSupported
ESXi-6.5.0-20170701001s-standard  VMware, Inc.  PartnerSupported
ESXi-6.5.0-20170702001-standard   VMware, Inc.  PartnerSupported
Choose the Standard one.

3. now you will run the command to perform the upgrade.
Code:
esxcli software profile update -p ESXi-6.5.0-20170702001-standard -d /vmfs/volumes/SCSIDatastore1/UPDATE~1.ZIP
Hold for 3 minutes and all will be done, ESXi will be rebooted. be patient for few minutes then when you see ESXi is up via console, you may need to reconnect the ESXi from Web client.

On other side, if Vcenter is Appliance version and have any issues in viewing right status you could reboot all services from its console as below.

Code:
service-control --start --all
and this reboots all Linux services for refresh the VCenter services, note this make web client down for few minutes.

Comments

Post a Comment

Popular posts from this blog

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu
Post a Comment
Read more

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output
1 comment
Read more

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664
Post a Comment
Read more