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

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more