Difference between revisions of "Procedures (ESX)"

Jump to navigation Jump to search
279 bytes removed ,  14:34, 13 March 2012
m
Minor reformatting, page needs major revision
(Export from original ESX page)
 
m (Minor reformatting, page needs major revision)
Line 1: Line 1:
= Procedures =
Links to VMware KB docs...
Links to VMware KB docs...
* [http://kb.vmware.com/kb/1026380 VMware KB1026380 - Committing snapshots on ESX/ESXi host from command line]
* [http://kb.vmware.com/kb/1026380 VMware KB1026380 - Committing snapshots on ESX/ESXi host from command line]


== Quick commands ==
= Quick commands =
{|cellpadding="2" cellspacing="0" border="1"
{|cellpadding="2" cellspacing="0" border="1"
|-
|-
Line 23: Line 22:
|}
|}


== ESX Shutdown / Reboot ==
= ESX Shutdown / Reboot =
'''ESX'''
'''ESX'''
* Shutdown a host ready for power off  
* Shutdown a host ready for power off  
Line 37: Line 36:
** <code> /bin/host_shutdown.sh </code>
** <code> /bin/host_shutdown.sh </code>


== High Availability Stop/Start ==
= High Availability Stop/Start =
* Stop HA...
* Stop HA...
** <code>  /etc/init.d/VMWAREAAM51_vmware stop  </code>
** <code>  /etc/init.d/VMWAREAAM51_vmware stop  </code>
Line 43: Line 42:
** <code>  /etc/init.d/VMWAREAAM51_vmware start  </code>
** <code>  /etc/init.d/VMWAREAAM51_vmware start  </code>


== VMware Management Agent Restart ==
= VMware Management Agent Restart =
'''ESX'''
'''ESX'''
<pre>
<pre>
Line 73: Line 72:
<code> services.sh restart </code>
<code> services.sh restart </code>


== VMware Web Access Restart ==
= VMware Web Access Restart =
<pre>
<pre>
service vmware-webAccess restart
service vmware-webAccess restart
Line 82: Line 81:
</pre>
</pre>


== VM Start ==
= VM Start =
On the ESX that currently owns the VM...
On the ESX that currently owns the VM...
# Get the VM's config file path
# Get the VM's config file path
Line 91: Line 90:
#* <code> less \vm_path\vmware.log </code>
#* <code> less \vm_path\vmware.log </code>


== Maintenance Mode ==
= Maintenance Mode =
To put the ESX into maintenance mode with no access from the Infrastructure Client (VCP) use the following commands - use with caution
To put the ESX into maintenance mode with no access from the Infrastructure Client (VCP) use the following commands - use with caution


Line 110: Line 109:




== TCPDump Network Sniffer ==
= TCPDump Network Sniffer =
Basic network sniffer available in Service Console
Basic network sniffer available in Service Console


Line 120: Line 119:




== Security ==
= Security =
=== Password Complexity Override ===
== Password Complexity Override ==
In order to be able to change a user (or root) password to one that breaches password complexity checking
In order to be able to change a user (or root) password to one that breaches password complexity checking


Line 132: Line 131:
#* <code> esxcfg-auth --usepamqc=-1 -1 -1 -1  8 8 </code>
#* <code> esxcfg-auth --usepamqc=-1 -1 -1 -1  8 8 </code>


=== Regenerate Certificate ===
== Regenerate Certificate ==
You might need to regenerate certificates if
You might need to regenerate certificates if
* Change ESX host name
* Change ESX host name
Line 148: Line 147:




== NIC Operations ==
= NIC Operations =
=== Get NIC Firmware/Driver versions ===
== Get NIC Firmware/Driver versions ==
* '''ESX4'''
* '''ESX4'''
** <code> ethtool -i vmnic<no> </code>
** <code> ethtool -i vmnic<no> </code>
Line 157: Line 156:
** Where <code><no></code> is your NIC no, eg <code> vsish -e get net/pNics/vmnic1/properties </code>
** Where <code><no></code> is your NIC no, eg <code> vsish -e get net/pNics/vmnic1/properties </code>


== HBA and SAN Operations ==
= HBA and SAN Operations =
=== VMFS / LUN Addition ===
== VMFS / LUN Addition ==
The new LUN needs to be carved up and presented to all ESX's that should see it (normally all ESX's from a particular cluster).  Once completed, follow the procedure below to add to the ESX's...
The new LUN needs to be carved up and presented to all ESX's that should see it (normally all ESX's from a particular cluster).  Once completed, follow the procedure below to add to the ESX's...
# Pick ESX in cluster with lowest load
# Pick ESX in cluster with lowest load
Line 171: Line 170:
# On the remaining ESX's, go to '''Storage Adapters''', hit '''Rescan...''' (leave both boxes checked)
# On the remaining ESX's, go to '''Storage Adapters''', hit '''Rescan...''' (leave both boxes checked)


=== SAN LUN ID ===
== SAN LUN ID ==
The SAN LUN ID is used by SAN admin's to identify LUN's.  It's not readily available from the GUI and has to be extracted from the vml file...
The SAN LUN ID is used by SAN admin's to identify LUN's.  It's not readily available from the GUI and has to be extracted from the vml file...


Line 180: Line 179:
So the SAN LUN ID is <code> 60060160c6931100cc319eea7adddd11 </code>
So the SAN LUN ID is <code> 60060160c6931100cc319eea7adddd11 </code>


=== Emulex ===
== Emulex ==
==== Find Emulex HBA Driver and Firmware Version, and WWPN ====
=== Find Emulex HBA Driver and Firmware Version, and WWPN ===
Doesn't require Emulex HBA utility to be installed
Doesn't require Emulex HBA utility to be installed
# <code> cd /proc/scsi/lpfc </code>
# <code> cd /proc/scsi/lpfc </code>
Line 205: Line 204:
</pre>
</pre>


==== Install Emulex HBA Utility ====
=== Install Emulex HBA Utility ===
Can be found at [http://www.emulex.com/vmware/support/index.jsp Emulex Lputil].
Can be found at [http://www.emulex.com/vmware/support/index.jsp Emulex Lputil].


Line 217: Line 216:
#* <code> ./Install.sh </code>
#* <code> ./Install.sh </code>
<pre>
<pre>
[root@uklonesxp2 Emulex-lpfcutil-7.1.14]# ./Install.sh
[root@esx2 Emulex-lpfcutil-7.1.14]# ./Install.sh
Installing Emulex HBAAPI libraries and applications...
Installing Emulex HBAAPI libraries and applications...
Installation of Emulex HBAAPI libraries and utilities is completed.
Installation of Emulex HBAAPI libraries and utilities is completed.
Line 231: Line 230:
</pre>
</pre>


==== HBAnywhere Installation ====
=== HBAnywhere Installation ===
# Download the Driver and Application kit for VMware from [http://www.emulex.com/downloads/emulex/cnas-and-hbas/drivers/vmware/fc-74040-pkg.html Emulex's website].
# Download the Driver and Application kit for VMware from [http://www.emulex.com/downloads/emulex/cnas-and-hbas/drivers/vmware/fc-74040-pkg.html Emulex's website].
#* At time of writing the current version of package was <code>elxvmwarecorekit-esx35-4.0a45-1.i386.rpm</code>
#* At time of writing the current version of package was <code>elxvmwarecorekit-esx35-4.0a45-1.i386.rpm</code>
Line 239: Line 238:
#* EG <code> rpm -ivh elxvmwarecorekit-2.1a42-1.i386.rpm </code>
#* EG <code> rpm -ivh elxvmwarecorekit-2.1a42-1.i386.rpm </code>


==== Check Emulex HBA Firmware Version ====
=== Check Emulex HBA Firmware Version ===
Requires the HBA Utility to be installed 1st (see above)
Requires the HBA Utility to be installed 1st (see above)


Line 260: Line 259:




==== Update Emulex HBA Firmware ====
=== Update Emulex HBA Firmware ===
* '''Using HBA Utility''' (must be installed 1st - see above).  See the Emulex website for the latest version, eg [http://www.emulex.com/ts/downloads/lp1050/lp1050ex.jsp Emulex LP1050Ex]
* '''Using HBA Utility''' (must be installed 1st - see above).  See the Emulex website for the latest version, eg [http://www.emulex.com/ts/downloads/lp1050/lp1050ex.jsp Emulex LP1050Ex]


To update the firmware (example uses LP1050Ex-mf191a5)
To update the firmware (example uses LP1050Ex-mf191a5)
# Put the downloaded zip file on the UKLONVCP1 NFS Share, and unzip to a folder, eg EmulexLP1050Ex-mf191a5
# Downloaded the zip file, and unzip to a folder (eg EmulexLP1050Ex-mf191a5)
# Create folder in /var/updates;
# Create folder in /var/updates;
#* <code> mkdir /var/updates/EmulexLP1050Ex-mf191a5 </code>
#* <code> mkdir /var/updates/EmulexLP1050Ex-mf191a5 </code>
# Copy the firmware update onto the ESX
# Copy the firmware update onto the ESX
#* <code> cp /vmfs/volumes/UKLONVCP1\ NFS\ Share/EmulexLP1050Ex-mf191a5/mf191a5.all /var/updates/EmulexLP1050Ex-mf191a5/ </code>
#* <code> cp EmulexLP1050Ex-mf191a5/mf191a5.all /var/updates/EmulexLP1050Ex-mf191a5/ </code>
# Start the utility (on startup it should detect one or more HBA's;
# Start the utility (on startup it should detect one or more HBA's;
#* <code> /usr/sbin/lpfc/lputil </code>
#* <code> /usr/sbin/lpfc/lputil </code>
Line 313: Line 312:
#* EG <code>/usr/sbin/hbanyware/hbacmd download 10:00:00:00:c9:82:97:9e zf280a4.all</code>
#* EG <code>/usr/sbin/hbanyware/hbacmd download 10:00:00:00:c9:82:97:9e zf280a4.all</code>


==== EMCgrab Collection ====
== EMCgrab Collection ==
# Download correct verion from EMC's website
# Download correct verion from EMC's website
#* At time of writing the current version file was [ftp://ftp.emc.com/pub/emcgrab/ESX/Old_Releases/v1.1/ emcgrab_ESX_v1.1.tar]
#* At time of writing the current version file was [ftp://ftp.emc.com/pub/emcgrab/ESX/Old_Releases/v1.1/ emcgrab_ESX_v1.1.tar]
Line 324: Line 323:
# Results can be found in <code>\emcgrab\outputs</code> folder
# Results can be found in <code>\emcgrab\outputs</code> folder


=== QLogic ===
= QLogic =
==== Find QLogic HBA Driver and Firmware Version ====
== Find QLogic HBA Driver and Firmware Version ==
# <code> cd /proc/scsi/qla2300 </code>
# <code> cd /proc/scsi/qla2300 </code>
# <code>  more 1 </code> for HBA 1
# <code>  more 1 </code> for HBA 1
<pre>
<pre>
[root@uklonesxp1 qla2300]# more 1
[root@esx1 qla2300]# more 1
QLogic PCI to Fibre Channel Host Adapter for QLA2340 :
QLogic PCI to Fibre Channel Host Adapter for QLA2340 :
         Firmware version:  3.03.19, Driver version 7.07.04
         Firmware version:  3.03.19, Driver version 7.07.04
Line 339: Line 338:




==== Install QLogic HBA Utility ====
== Install QLogic HBA Utility ==
Installation instructions for the SANsurfer utility
Installation instructions for the SANsurfer utility
# Put the downloaded tgz file on the UKLONVCP1 NFS Share, eg scli-1.7.0-12.i386.rpm.gz
# Copy the downloaded tgz file (eg scli-1.7.0-12.i386.rpm.gz) to folder /var/updates (create if it doesn't exist)
# Copy to folder /var/updates (create if it doesn't exist)
#* <code> cp scli-1.7.0-12.i386.rpm.gz  /var/updates </code>
#* <code> cp /vmfs/volumes/UKLONVCP1\ NFS\ Share/scli-1.7.0-12.i386.rpm.gz  /var/updates </code>
# Uncompress the file with the following command;
# Uncompress the file with the following command;
#* <code> gunzip scli-1.7.0-12.i386.rpm.gz </code>
#* <code> gunzip scli-1.7.0-12.i386.rpm.gz </code>
Line 358: Line 356:




==== Update QLogic HBA Firmware ====
=== Update QLogic HBA Firmware ===
See QLogic website for latest version, you must ensure the firmware version is compatible with the current running driver version.  Requires SANsurfer to be installed 1st (see above)
See QLogic website for latest version, you must ensure the firmware version is compatible with the current running driver version.  Requires SANsurfer to be installed 1st (see above)


# Put the downloaded tgz file on the UKLONVCP1 NFS Share, eg q231x_234x_bios147.zip, and unzip to folder
# Put the downloaded tgz file on a NFS Share, eg q231x_234x_bios147.zip, and unzip to folder
# Create a new folder for the update;
# Create a new folder for the update;
#* <code> mkdir /var/updates/q231x_234x_bios147
#* <code> mkdir /var/updates/q231x_234x_bios147
# Copy the firmware onto the ESX server;
# Copy the firmware onto the ESX server;
#* <code> cp /vmfs/volumes/UKLONVCP1\ NFS\ Share/q231x_234x_bios147/QL23ROM.BIN /var/updates/q231x_234x_bios147/ </code>
#* <code> cp q231x_234x_bios147/QL23ROM.BIN /var/updates/q231x_234x_bios147/ </code>
# Move to the folder containing the update;
# Move to the folder containing the update;
#* <code> cd /var/updates/q231x_234x_bios147/ </code>
#* <code> cd /var/updates/q231x_234x_bios147/ </code>
Line 386: Line 384:




=== SAN Downtime ===
== SAN Downtime ==
ESX's don't like to loose the SAN, to the extent that during the scheduled SAN downtime the following is recommended...
ESX's don't like to loose the SAN, to the extent that during the scheduled SAN downtime the following is recommended...
# Shutdown ESX's (and hosted VM's) connected to affected storage
# Shutdown ESX's (and hosted VM's) connected to affected storage
Line 400: Line 398:
# Restart / migrate VM's
# Restart / migrate VM's


== Netflow ==
= Netflow =
'''Netflow is available on ESX v3 only, and is an experimental feature.  Netflow v5 is sent.'''
'''Netflow is available on ESX v3 only, and is an experimental feature.  Netflow v5 is sent.'''


Line 423: Line 421:
*# <code> vmkload_mod -u netflow </code>
*# <code> vmkload_mod -u netflow </code>


== Change Service Console IP Information ==
= Change Service Console IP Information =
Logged in as root use the esxcfg-vswif command <code>esxcfg-vswif <options> [vswif] </code>
Logged in as root use the esxcfg-vswif command <code>esxcfg-vswif <options> [vswif] </code>


Line 451: Line 449:
Note: You set the Service Console VLAN (to 1234) using a similar command to:  <code>esxcfg-vswitch -v1234 -p"Service Console" vSwitch0></code>
Note: You set the Service Console VLAN (to 1234) using a similar command to:  <code>esxcfg-vswitch -v1234 -p"Service Console" vSwitch0></code>


== Change Timezone ==
= Change Timezone =
# Log into the ESX Server service console as root.  
# Log into the ESX Server service console as root.  
# Find the desired time zone under the directory /usr/share/zoneinfo
# Find the desired time zone under the directory /usr/share/zoneinfo

Navigation menu