Category: Info

vCloud Air – Two interfaces ?

Everyday I talk to lot of vCloud Air customers, often I hear feedback vCloud Air UI is confusing.

The confusion is two interfaces, which is vCloud Air portal and vCloud director portal

According to me

  • vCloud Air Portal is simple and quick

vCloudAirTwoIF-1vCloudAirTwoIF-2

 

 

 

 

 

 

 

  • vCloud Director Portal is advanced and comprehensive

vCLoudAirTwoIf-3

The reasons why vCloud Air offers two interfaces
  • vCloud Air service leverage vCloud Director (vCD) to host the cloud services, vCD is well liked IaaS product from VMware.
    It is still used by many of the service providers to deliver IaaS cloud
  • The users who are very new, vCloud Air portal offers a simple / minimal view and can do the things within few clicks
  • Many of the VMware customers are familiar with vCloud Director UI, for them it is easy to adopt vCloud Air
  • Many of the advanced users, leverage APIs / SDKs for automation. Providing access to vCD makes them easier to use APIs and automation tools such as vRealize Automation and vRealize Orchestrator
  • Thorough vCloud air you can purchase multiple DCs from multiple available regions, vCloud Air portal acts like unified portal to manage / monitor all the VDCs
UI Comparison.

vCLoudAirTwoIf-4

Internet Access to a VM in vCloud Air OnDemand

By default the VMs in vCloud Air doesn’t not connect to internet. We need to configure the SNAT/DNAT rules to allow the internet connectivity in both ways.

Below is the procedure to allow internet access to a VM in  vCloud Air OnDemand.

Add Public IP –> Configure SNAT Rules –> Validate the Connectivity

Add a Public IP to a Gateway in vCloud Air OnDemand

Click Gateways –> Public Ips –> Add IP Address

SecondPost-Seq1

 

Create a SNAT Rule

 

SecPost-Seq1

Now the VMs connected to the org-network associated with the gateway will be to connect to internet.

vCloud Air OnDemand – An Intro

On Jan 20, 2015, VMware rolled out another version of Cloud service offering “vCloud Air On Demand”. This time VMware made the process very simple to access the service. Customers can use their credit cards to sign-up vCloud Air On Demand service(Pay-As-You-Go)(PAYG Model) and start their VMs in few clicks / minutes.

As a promotion, VMware offers 300$ credits to new customers

Click Here to Sign-Up

If someone wants to see the simplicity of accessing the service, I summarized the sign-up process and creating your first VM.

Sign-up process

Click Sign-Up –> Fill in your Details –> Credit Card Details –> Confirm your account –> Set your first password –> Boom

FirstPostSeq

 

Create your First Datacenter

For the first time you login, you will be asked where you want to create your first VPC (virtual private cloud).

You will be prompted to choose from available DCs, choose the one which closest to you .

 

FirstPostseq2

Create your First VM

vCloud Air service supports a wide variety of 32 & 64 bit Operating System, below is the list of supported OS

vCloud Air Supported Operating Systems

The current Operating Systems supported by vCloud Director are:

Microsoft Windows Linux
Microsoft Windows Server 2012 64-bit Red Hat Enterprise Linux 6
Microsoft Windows Server 2012 R2 64-bit Red Hat Enterprise Linux 5
Microsoft Windows 8 Red Hat Enterprise Linux 4
Microsoft Windows 8.1 SUSE Enterprise Linux 11
Microsoft Windows 7 SUSE Enterprise Linux 10
Microsoft Windows Server 2008 Oracle Linux 6
Microsoft Windows Server 2008 R2 64-bit Oracle Linux 5
Microsoft Windows Server 2003 Oracle Linux 4
Microsoft Windows Small Business Sever 32-bit CentOS
Microsoft Windows Vista Ubuntu Linux
Microsoft Windows XP Professional Other 3.x Linux
Microsoft Windows 2000 Other 2.6.x Linux
Microsoft Windows NT Other 2.4.x Linux
Microsoft Windows 3.1 Other Linux
Microsoft MS-DOS

But thats not all, as vCloud Air runs on VMware vSphere, the full list of vCloud Air supported Operating Systems and application are in the vSphere HCL: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=software&testConfig=16

Create VM

Look at this article  for allowing a VM to connect internet.

Also the billing and pricing is granular and can be viewed in the On-demand portal Resource Usage dashboard.

VMware has a pricing calculator / planner in their website, so a user can check approximate billing information prior signing up the service.

FirstPostSeq5

 

So overall look at vCloud Air Ondemand looks promising and really useful when you need a VM/Resources real quick without any hassle.

 

Log Locations of all VMware Products

In this post I tried consolidating all the VMware product’s log location for handy use.

 

vCenter

The vCenter Server logs are placed in a different directory on disk depending on vCenter Server version and the deployed platform:
vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareVMware VirtualCenterLogs
vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:ProgramDataVMwareVMware VirtualCenterLogs
vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/
vCenter Server 5.x Linux Virtual Appliance UI: /var/log/vmware/vami

Note: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.

Usage Log File Name
The main vCenter Server logs, consisting of all vSphere Client and WebServices connections, internal tasks and events, and communication with the vCenter Server Agent (vpxa) on managed ESX/ESXi hosts. vpxd.log
Profiled metrics for operations performed in vCenter Server. Used by the VPX Operational Dashboard (VOD) accessible at https://VCHostnameOrIPAddress/vod/index.html. vpxd-profiler.logprofiler.log
Non-fatal information logged about the vpxd process. vpxd-alert.log
Common Information Model monitoring information, including communication between vCenter Server and managed hosts’ CIM interface cim-diag.log and vws.log
Actions proposed and taken by VMware Distributed Resource Scheduler (DRS), grouped by the DRS-enabled cluster managed by vCenter Server. These logs are compressed. drmdump:
Health reports for the Licensing Services extension, connectivity logs to vCenter Server. ls.log
Dump of string used during the installation of vCenter Server with hashed information for DNS, username and output for JDBC creation. vimtool.log
Provides information about the historical performance data collection from the ESXi/ESX hosts stats.log
Health reports for the Storage Monitoring Service extension, connectivity logs to vCenter Server, the vCenter Server database and the xDB for vCenter Inventory Service. sms.log
Health reports for the ESX Agent Monitor extension, connectivity logs to vCenter Server. eam.log
Connectivity information and status of the VMware Webmanagement Services. catalina..log and localhost..log
Health status of the VMwareVCMSDS service and individual ADAM database objects, internal tasks and events, and replication logs between linked-mode vCenter Servers. jointool.log

 

vCenter 6.0

The VMware vCenter Server 6.0 logs are located in the %ALLUSERSPROFILE%VMWarevCenterServerlogs folder.
The VMware vCenter Server Appliance 6.0 logs are located in the /var/log/vmware/ folder.

vCenter Server logs are grouped by component and purpose in these sub-directories:

vCenter Server
vCenter Server Appliance
Description
vmware-vpxvpxd.log
vpxd/vpxd.log
The main vCenter Serverlog
vmware-vpxvpxd-profiler.log
vpxd/vpxd-profiler.log
Profile metrics for operations performed in vCenter Server
vmware-vpxvpxd-alert.log
vpxd/vpxd-alert.log
Non-fatal information logged about the vpxd process
perfchartsstats.log
perfcharts/stats.log
VMware Performance Charts
eameam.log
eam/eam.log
VMware ESX Agent Manager
invsvc
invsvc
VMware Inventory Service
netdump
netdumper
VMware vSphere ESXi Dump Collector
vapi vapi VMware vAPI Endpoint
vmdird
vmdird
VMware Directory Service daemon
vmsyslogcollector
syslog
vSphere Syslog Collector
vmware-spssps.log
vmware-sps/sps.log
VMware vSphere Profile-Driven Storage Service
vpostgres
vpostgres
vFabric Postgres database service
vsphere-client
vsphere-client
VMware vSphere Web Client
vws
vws
VMware System and Hardware Health Manager
workflow
workflow
VMware vCenter Workflow Manger
SSO SSO VMware Single Sign-On

 

Back to top

vSphere Profile-Driven Storage log files

The vSphere Profile-Driven Storage logs are placed in a different directory on disk depending on the vCenter Server version and the deployed platform:

  • vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareInfrastructureProfile-Driven StorageLogs
  • vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008: C:ProgramDataVMwareInfrastructureProfile-Driven StorageLogs
  • vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/spsNote: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of%ALLUSERSPROFILE%.
Usage Log
The main Profile-Driven Storage logs, consisting of all vCenter Server and Management Webservices connections, internal tasks and events, and information about the storage profile integrity. sps.log
This file consists of information about the installation of Profile-Driven Storage including computer name, operating system revision, the date of installation and the number of revisions that have been installed or upgraded on the system. vim-sps-install.log
This file provides information about the state of the Java runtime environment. wrapper.log

Back to top

vSphere Web Client service logs

For vSphere 5.0, all the logs for the vSphere Web Client service are located at:

  • Windows: C:Program FilesVMwareInfrastructurevSphere Web ClientDMServerserviceability
  • Linux: /usr/lib/vmware-vsphere-client/server/serviceability/

For vSphere 5.1, all the logs for the vSphere Web Client service are located at:

  • Windows: C:ProgramDataVMwarevSphere Web Clientserviceability
  • Linux: /var/log/vmware/vsphere-client/serviceability/

For vSphere 5.5, all the logs for the vSphere Web Client service are located at:

  • Windows: C:ProgramDataVMwarevSphere Web Clientserviceability
  • Linux: /var/log/vmware/vsphere-client/

 

Usage Log
The main vSphere Web Client log, consisting of all communication between underlying Flex endpoint connections, internal tasks and events logsvsphere_client_virgo.log
Individual HTTP requests from the Web browser logsaccesslocalhost_access_log..txt
 Information about plug-in bundle communication logsvirgo-serverlog.log
Time stamps of startup and shutdown of the vSphere Web Client service eventlogs/eventlog.log

Back to top

vCenter Single Sign-On

The SSO logs are placed in a different directory on disk depending on the vSphere version and the deployed platform:

 

vSphere 5.1 using vCenter Single Sign-On 5.1:

vCenter Server 5.1.x on Windows Server 2003 – C:Program FilesVMwareInfrastructureSSOServerlogs

vCenter Server 5.1.x on Windows Server 2008/2012 – C:Program FilesVMwareInfrastructureSSOServerlogs

vCenter Server Virtual Appliance 5.1.x – /var/log/vmware/sso/

vSphere 5.5 using vCenter Single Sign-On 5.5:

vCenter Server 5.5.x on 2003 – %ALLUSERSPROFILE%Application DataCISlogs

vCenter Server 5.5.x and 2008, 2012 – C:ProgramDataVMwareCISlogs

vCenter Server Virtual Appliance 5.5.x – /var/log/vmware/sso/

 

Note: If the service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.
Back to top

 SSO 5.1

 

Usage Log
SSO installer log Vminst.log
SSO Lookup Service log vm_vim_ls.log
MSI installer for SSO installation log – verbose vim-sso-msi.log
SSO database operations vim-sso-javalib.log
Standard Tomcat logs catalina.date.log
RSA’s Castle logs imsTrace.log and imsSystem.log
SSO admin serve ssoAdminServer.log
 Lookup server log lookupServer.log
Replication replicationTransport.log

Back to top

 SSO 5.5

Usage Log
SSO installer log Vminst.log
MSI installer for SSO installation log – verbose vim-sso-msi.log
 SSO Service log vim_ssoreg.log
 Endpoint information about each of the SSO Solution Users and identity sources extracted from previous vCenter Single Sign On 5.1.0 instance exported_sso.properties
MSI installer verbose log for OpenSSL installation vim-openssl-msi.log
 MSI installer verbose log for Python installation vim-python-msi.log
MSI installer verbose log for MIT Kerberos installation vim-kfw-msi.log
 Promotion and demotion operation information for the SSO instance when joined or removed from a linked configurations vmdirdvdcpromo.log
 VMware Directory Service setup post-installation log containing information about the localhost vmdirdvdcsetupIdu.log
 Health reports for the VMware Directory Service (VMDir) service and the VMDir database vmdirdvmdir.log
Key Distribution Center (kdc) run-time log, reports ports conflicts preventing the service from starting vmkdcdvmkdcd.log
 VMware Identity Management service run-time logs, time-stamped records of user attempts when accessing SSO for administrative purposes vmware-ssovmware-sts-idmd.log
VMware Identity Management service performance counter logs vmware-ssovmware-sts.ldmd-perf.log
Commons Daemon log once the Identity Management Service has started vmware-ssoVMwareIdentityMgmtService. date.log

Back to top

 vCenter Inventory Service

The vCenter Inventory Service logs are placed in a different directory on disk depending on the vCenter Server version and the deployed platform:

  • vCenter Server 5.x and earlier versions on Windows XP, 2000, 2003: %ALLUSERSPROFILE%Application DataVMwareInfrastructureInventory ServiceLogs
  • vCenter Server 5.x and earlier versions on Windows Vista, 7, 2008:C:ProgramDataVMwareInfrastructureInventory ServiceLogs
  • vCenter Server 5.x Linux Virtual Appliance: /var/log/vmware/vpx/inventoryserviceNote: If the vCenter Inventory Service is running under a specific user, the logs may be located in the profile directory of that user instead of %ALLUSERSPROFILE%.
Usage Log
The main vCenter Inventory Service logs, consisting of all vCenter Server and Single Sign-On connections, internal tasks and events, and information about the xDB. ds.log
This file contains information about the installation of Inventory Service including computer name, operating system revision, the date of installation and the number of revisions that have been installed or upgraded on the system. vim-is-install.log
This file provides information about the status of the Java runtime environment. wrapper.log

Back to top

VMware Converter logs

There are also several ways to diagnose issues by viewing the VMware Converter logs. The logs can contain information that is not apparent from error messages. In newer versions of VMware Converter, you can use the Export Log Data button. Otherwise, logs are typically stored in these directories:

  • Windows NT, 2000, XP, and 2003:
    • C:Documents and SettingsAll UsersApplication DataVMwareVMware Converter EnterpriseLogs
    • C:WINDOWSTempvmware-converter
    • C:WINDOWSTempvmware-temp
  • Windows Vista, 7, and 2008:
    • C:UsersAll UsersApplication DataVMwareVMware Converter EnterpriseLogs
  • Windows 8 and Windows 2012:
  • C:ProgramDataVMwareVMware vCenter Converter Standalonelogs
    • Note: In order to access this location in Windows Vista, 7, or 2008, you may need to go into the folder options and ensure thatShow Hidden Files is enabled and that Hide Protected Operating System Files is disabled.
    • C:WINDOWSTempvmware-converter
    • C:WINDOWSTempvmware-temp
  • Windows NT and 2000:
    • C:WINNTTempvmware-converter
    • C:WINNTTempvmware-temp
  • Linux:
    • $HOME/.vmware/VMware vCenter Converter Standalone/Logs
    • /var/log/vmware-vcenter-converter-standalone

Back to top

vCloud Director

Component Path
Cell Startup log. $VCLOUD_HOME/logs/cell.log
Debugging log messages from the cell $VCLOUD_HOME/logs/vcloud-container-debug.log
Warnings or errors in the cell $VCLOUD_HOME/logs/vcloud-container-info.log
Log of the Watchdog service – which restarts the vCD service if it hangs or stops $VCLOUD_HOME/logs/vmware-vcd-watchdog.log

Back to top

vShield Manager

vSM is a hardened Linux Appliance so use below commands in the vSM to view the logs

Component Commands
vShield Manager Log Show logShow manager logShow manager log followShow manager log last

Back to top

vShield Edge logs

vShield Edge log Show log
Show log follow

Back to top

vCloud Usage Meter

Usage Meter Log /var/log/usgmtr/um.log

Back to top

 

vCloud Connector logs

 

Usage Log
vCloud Connector Server Log /opt/vmware/hcagent/logs/hcs.log
vCloud Connector Node Log /opt/vmware/hcagent/logs/hca.log

Back to top

vCenter Operations

Component VM Path
Admin UI UI /var/log/vmware/admin.log
vSphere UI UI $ALIVE_BASE/user/log/web_std.log
Custom UI UI $ALIVE_BASE/user/log/web.log
CapIQ UI /var/log/vmware/ciq.log
Upgrades UI /var/log/vmware/upgradecoordinator.log
ActiveMQ AL $ALIVE_BASE/user/log/activemq.log
Analytics AL $ALIVE_BASE/user/log/analytics.log
Collector AL $ALIVE_BASE/user/log/collector.log
Adapter AL $ALIVE_BASE/user/log/adapters//_.log 

 

vRealize Automation Suite 6.x

Back to top

vRealize Automation Virtual Appliance Locations
Description
/var/log/vcac/catalina.out
tc Server Runtime logs, vRealize Automation webapp logs
/var/log/vco/app-server/catalina.out
vRealize Automation’s built-in vRealize Orchectrator logs
/var/log/apache2/access_log
Apache Access logs
/var/log/apache2/error_log
Apache GET/POST Error logs
/var/log/apache2/ssl_request_log
Apache SSL troubleshooting logs
vRealize Automation Infrastructure as a Service Locations
Description
C:Program Files (x86)VMwarevCACAgentsagent_namelogsfile
Plug-in logs example: CPI61, nsx, VC50, VC51Agent, VC51TPM, vc51withTPM, VC55Agent, vc55u, VDIAgent
C:Program Files (x86)VMwarevCACDistributed Execution ManagerDEMORLogsDEMOR_All Distributed Execution Manager logs
C:Program Files (x86)VMwarevCACDistributed Execution ManagerDEMWRLogsDEMWR_All Distributed Execution Worker logs
C:Program Files (x86)VMwarevCACServerLogs Manager Service logs
C:Program Files (x86)VMwarevCACServerConfigToolLogvCACConfiguration-date Repository Configuration logs
C:Program Files (x86)VMwarevCACServerModel Manager DataLogsnothing_today IIS Access logs (usually empty, but can be expected)
C:Program Files (x86)VMwarevCACServerModel Manager WebLogsRepository Repository logs
C:Program Files (x86)VMwarevCACServerWebsiteLogsWeb_Admin_All Web Admin logs
C:inetpublogs IIS logs
Identity Virtual Appliance Locations Description
/var/log/vmware/sso/catalina.out ID VA tc Server Runtime logs
/var/log/vmware/sso/ssoAdminServer.log
SSO Admin Server logsNote: Not applicable to vRealize Automation.
/var/log/vmware/sso/vmware-identity-sts-perf.log STS performance logs
/var/log/vmware/sso/vmware-identity-sts.log STS logs
/var/log/vmware/sso/vmware-sts-idmd-perf.log Identity service performance logs
/var/log/vmware/sso/vmware-sts-idmd.err Identity service error logs
/var/log/vmware/sso/vmware-sts-idmd.log Identity service logs
/var/log/vmware/vmafd/vmafdd.log Identity VA logs
/var/log/vmware/vmdir/vdcsetupldu.log Initial setup logs
/var/log/vmware/vmdir/vmafdvmdirclient.log VMware SSO LDAP initial configuration logs
/var/log/vmware/vmkdc/vmkdcd.log VMware SSO LDAP initial configuration logs
vRealize Application Services Location Description
/home/darwin/tcserver/darwin/logs/catalina.out Application Services tc Server Runtime logs
vMware vRealize Business Standard Description
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/catalina.out vRealize Business Advanced and Enterprise tc Server Runtime logs
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/auditFile.log REST API requests
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-external-api.log API logs
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-reflib-update.log vRealize Business standard reference library related changes.
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm-vc-dc.log Data collector logs
/usr/local/tcserver/vfabric-tc-server-standard/tcinstance1/logs/itfm.log vRealize Business Advanced and Enterprise logs
vCenter Server Appliance (VCSA) 5.5.x Locations Description
/var/log/vmware/vpx/vpxd.log vCenter VPXD logs
/var/log/vmware/vpx/vpxd-alert.log vCenter VPXD alert logs
/var/log/vmware/vpx/vws.log Management Web Service logs
/var/log/vmware/vpx/vmware-vpxd.log vCenter VPXD status change logs
/var/log/vmware/vpx/inventoryservice/ds.log vCenter Inventory Service logs
/var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log vSphere Client logs
/var/log/vmware/vsphere-client/logs/virgo-server/log.log vSphere Client logs
/var/log/vmware/vsphere-client/eventlogs/eventlog.log vSphere Client event logs
vCenter SSO Locations Description
/var/log/vmware/sso/catalina.out SSO tc Server Runtime logs
/var/log/vmware/sso/ssoAdminServer.log SSO Admin Server logs (only in 5.5.x version)
/var/log/vmware/sso/vmware-identity-sts-perf.log STS performance logs
/var/log/vmware/sso/vmware-identity-sts.log STS logs
/var/log/vmware/sso/vmware-sts-idmd-perf.log Identity service performance logs

Back to top

 vCenter Orchestrator

Each VMware vCenter Orchestrator log file serves a different purpose. Review the following to understand what each log file does.

Notes:

  • If you installed Orchestrator standalone, the default installation path is C:Program FilesVMwareOrchestrator.
  • If you installed Orchestrator with the vCenter Server installer, the default installation path is C:Program FilesVMwareInfrastructureOrchestrator.
  • Log file paths listed are relative to the default installation path.
File Default Location Explanation
boot.log app-serverservervmolog In this log you find details on the JBOSS boot, but nothing related to the vCO server. It might be useful in cases where a file from JBOSS is missing or the install is corrupted. This kind of issue is very rare.
boot-state.log app-serverservervmolog In this log you will find the boot state of the vCO server. If the server booted properly it writes an entry together with the vCO version. This file can be useful as a summary of the boot of vCO server. This is included by default in server.log.
scripts-log.log app-serverservervmolog This file contains the thread from all the executions of workflows and actions. It lets you isolate these executions from normal vCO operations. You can find the same information in server.log. If you need to know which workflow was executed you need to look at server.log instead.
server.log app-serverservervmolog
This is the main log of vCO server. It contains the same information as boot-state.log,scripts-log.log in addition to more data. Everything that happens on the vCO server is seen here. When debugging vCO or any application running on vCO (such as LCM), this is the first log you should open.
vmo-configuration.log configurationjettylogs In this log you find the configuration and validation of each component of vCO. This is the jetty service running on the vCO server. The file request.log, in the same directory, might be more useful if you want just a history of actions taken during configuration.
vmware_orchestrator_installer_output.txt
C:tmp
Note: This path is not relative.
This is the log file containing all the information about the installation of vCO. It shows if vCO was silently installed by vCenter or if it was an independent install. It also indicates if the configuration service was started at install or if it was left stopped for security reasons. This file is the only way to detect an issue during an installation.
vso.log apps This is the client log. It is mainly interesting for connection issues with the server and events on the client side.
yyyy-mm-dd.request.log configurationjettylogs This log shows all the elements that were needed to load and display the pages of the configurator. It keeps a history of which actions were taken for the configuration of vCO and when they were done. This might be very useful to identify a change in the behavior of the vCO server after a restart. However, it does not display the value of changed parameters, only that they were changed.
wrapper.log app-serverbin
The wrapper log contains some information that is also found in the server.log. However this is the only place you will be able to know if the VMware vCenter Orchestrator Server service was restarted by the wrapper or by a user.
vCenter_Orchestrator_InstallLog.log On the desktop of the user who installed Orchestrator. This file is created if you abort an installation or the installation fails.

Back to top
Please comment if you need any additional products.

History:

22-June-2015 – Added vCenter 6.0

Tech Tip : Did you know now you can access your VMware workstation from anywhere on any device to remotely monitor virtual servers and machines using windows virtual desktop from www.CloudDesktopOnline.com. If you prefer a server, Rent a server with 24*7 impeccable tech-support from Apps4Rent.

 

VMware vSphere ESXi Commands for everyday use

In this post, I tried listing down all commands that I use everyday for ESXi Troubleshooting. I have categorized the commands for easy accessibility.

I find these commands are very useful when the ESXi host disconnected from vCenter and when not able to connect to vSphere Client.

[toggle type=”first” title=”Virtual Machine Operations”]

To get All registered VMs on the Host:

[code]vim-cmd vmsvc/getallvms[/code]

Example:

~ # vim-cmd vmsvc/getallvms
Vmid Name     File                                  Guest OS Version       Annotation
1    DeskTop  [datastore1 (3)] DeskTop/DeskTop.vmx  windows8_64Guest       vmx-08
2    Domain   [datastore1 (3)] Domain/Domain.vmx    windows7Server64Guest  vmx-08
3    VCD55    [datastore1 (3)] VCD55/VCD55.vmx      centos64Guest          vmx-08
Power ON a VM:

[code]vim-cmd vmsvc/power.on <VMID> [/code]

Example:

~ # vim-cmd vmsvc/power.on 3
Powering on VM:
Power OFF a VM:

[code]vim-cmd vmsvc/power.off <VMID> [/code]

Example:

~ # vim-cmd vmsvc/power.off 3
Powering off VM:
 Gracefully shutdown a VM’s Guest OS:

[code]vim-cmd vmsvc/power.shutdown <VMID> [/code]

Example:

~ # vim-cmd vmsvc/power.shutdown 3
~ #
Register a VM

[code]vim-cmd solo/registervm <vmxpath> [/code]

Example:

~ # vim-cmd solo/registervm "/vmfs/volumes/datastore1 (3)/VCD55/VCD55.vmx"
4

UnRegister a VM:

[code]vim-cmd vmsvc/unregister <VMID> [/code]

Example:

~ # vim-cmd vmsvc/unregister 4
~ #

 

[/toggle]

[toggle title=”Host Operations”]

Enter Host into Maintenance mode:

[code] vim-cmd hostsvc/maintenance_mode_enter  [/code]

 

Exit Host into Maintenance mode:

[code] vim-cmd hostsvc/maintenance_mode_exit  [/code]

 

[/toggle]

[toggle title=”Storage”]

 

Storage Commands

 

LUNs

To get All disks attached to ESXi host.

[code] esxcfg-scsidevs -l [/code]

or

[code] esxcli core storage device list [/code]

Sample Output.

naa.600508b1001c0f0e831036c264b4203e
 Display Name: HP Serial Attached SCSI Disk (naa.600508b1001c0f0e831036c264b4203e)
 Has Settable Display Name: true
 Size: 429215
 Device Type: Direct-Access
 Multipath Plugin: NMP
 Devfs Path: /vmfs/devices/disks/naa.600508b1001c0f0e831036c264b4203e
 Vendor: HP
 Model: LOGICAL VOLUME
 Revision: 3.54
 SCSI Level: 5
 Is Pseudo: false
 Status: degraded
 Is RDM Capable: true
 Is Local: false
 Is Removable: false
 Is SSD: false
 Is Offline: false
 Is Perennially Reserved: false
 Queue Full Sample Size: 0
 Queue Full Threshold: 0
 Thin Provisioning Status: unknown
 Attached Filters:
 VAAI Status: unknown
 Other UIDs: vml.0200010000600508b1001c0f0e831036c264b4203e4c4f47494341
 Is Local SAS Device: false
 Is Boot USB Device: false
 No of outstanding IOs with competing worlds: 32

 

 To get All disks attached to ESXi host(Compact List)
~ # esxcfg-scsidevs -c
Device UID Device Type Console Device Size Multipath PluginDisplay Name
naa.600508b1001c0f0e831036c264b4203e Direct-Access /vmfs/devices/disks/naa.600508b1001c0f0e831036c264b4203e 429215MB NMP HP Serial Attached SCSI Disk (naa.600508b1001c0f0e831036c264b4203e)
LUN to Datastore Mapping
~ # esxcfg-scsidevs -m
naa.600508b1001c0f0e831036c264b4203e:3 /vmfs/devices/disks/naa.600508b1001c0f0e831036c264b4203e:3 5131890d-0c77f39a-0382-e4115b9b7270 0 datastore1 (3)

LUN Paths:

 

~ # esxcfg-mpath -L
 vmhba0:C0:T0:L1 state:active naa.600508b1001c0f0e831036c264b4203e vmhba0 0 0 1 NMP active san sas.5001438027641890 sas.1438027641890

 ~ # esxcfg-mpath -m
 vmhba0:C0:T0:L1 vmhba0 sas.5001438027641890 sas.1438027641890 naa.600508b1001c0f0e831036c264b4203e

 ~ # esxcfg-mpath -b
 naa.600508b1001c0f0e831036c264b4203e : HP Serial Attached SCSI Disk (naa.600508b1001c0f0e831036c264b4203e)
 vmhba0:C0:T0:L1 LUN:1 state:active sas Adapter: 5001438027641890 Target: 1438027641890

 

HBA Commands

To List all HBAs available on the ESXi Host.
~ # esxcfg-scsidevs -a
vmhba0 hpsa link-n/a sas.5001438027641890 (0:3:0.0) Hewlett-Packard Company Smart Array P220i
vmhba1 qlnativefc link-up fc.50060b0000c26205:50060b0000c26204 (0:5:0.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba2 qlnativefc link-n/a fc.50060b0000c26207:50060b0000c26206 (0:5:0.1) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba32 iscsi_vmk online iscsi.vmhba32 iSCSI Software Adapter
HBA and LUN Mapping.
~ # esxcfg-scsidevs -A
vmhba0 naa.600508b1001c0f0e831036c264b4203e
To Rescan a HBA

[code]esxcfg-rescan <HBANAME>[/code]

example

~ # esxcfg-rescan vmhba32
~ #

iSCSI Commands

Discovery Stats for a iSCSI adapter

[code]~ # vmkiscsi-tool -D <HBANAME>[/code]

Example

~ # vmkiscsi-tool -D vmhba32
=========Discovery Properties for Adapter vmhba32=========
 iSnsDiscoverySettable : 0
 iSnsDiscoveryEnabled : 0
 iSnsDiscoveryMethod : 0
 iSnsHost.ipAddress : ::
 staticDiscoverySettable : 0
 staticDiscoveryEnabled : 1
 sendTargetsDiscoverySettable : 0
 sendTargetsDiscoveryEnabled : 1
 slpDiscoverySettable : 0
 No Discovery Addresses Found
 No Static Discovery Targets Found

[code]~ # vmkiscsi-tool -E <HBANME>[/code]

Example

 ~ # vmkiscsi-tool -E vmhba32
 No active targets.
ISCSI – IQN Name

[code]~ # vmkiscsi-tool -I HBANAME[/code]

Example

~ # vmkiscsi-tool -I vmhba32
iSCSI Node Name: iqn.1998-01.com.vmware:is-tse-h44-56726a3c

MTU Value

[code]~ # vmkiscsi-tool -M vmhba32[/code]

Example.

 ~ # vmkiscsi-tool -M vmhba32
 MTU SETTABLE : Not Valid
 MTU Size : Not Valid

 

NFS Commands

To list all the mounted NFS datastores.
~ # esxcli storage nfs list

or

~ # esxcfg-nas -l

 

Add a NFS Datastore
~ # esxcli storage nfs add -H NFS_IP|NFS_HOSTNAME -s Share_mount_point_on_the_NFS -vDatastoreName

or

~ # esxcfg-nas -a -o NFS_IP -s Share_mount_point_on_the_NFSDatastoreName
Delete a NFS Datastore
 esxcli storage nfs remove -v NFS_Datastore_Name

or

esxcfg-nas -d NFS_Datastore_Name

 

 

[/toggle]

[toggle title=”Networking”]Still Working on [/toggle]

[toggle title=”vSphere Replication”]

[code]vim-cmd hbrsvc/[/code]

[/toggle]

 

[toggle title=”Advanced & Misc “]Working on[/toggle]