vApp Network Examples

Organization vDC Network Examples

New VCP-Cloud Exam

On February 18, we released a new exam to qualify candidates for the VCP-Cloud Certification. This new exam (exam code VCPC550) is based on vCloud Automation Center 5.2 and vCloud Director 5.5, where the existing exam (exam code VCPC510) is based on vCloud Director 5.1. Passing either of these exams will earn VCP-Cloud certification* if you have also taken an approved required course (see list below).

---

vCloud Automation Center 5.2 and vCloud Director 5.5 Based Exam – Exam Code VCPC550

Download the Exam Blueprint

Request Authorization

Attendance at one of these courses is required:

• vCloud Director: Install, Configure, Manage [V5.5]
• VMware vCloud Automation Center: Install, Configure, Manage [V5.2]

vCloud Director 5.1 Based Exam – Exam Code VCPC510

Download the Exam Blueprint

Request Authorization

Attendance at one of these courses is required:

• vCloud Director: Install, Configure, Manage [V5.1]
• VMware vCloud: Deploy and Manage the VMware Cloud [V1.5]

HTML5 virtual machine console fails to open after restarting VMware vCenter Server Appliance 5.5 (2060604)

Symptoms

• The HTML5 virtual machine console fails to open after restarting the vCenter Server Appliance (VCSA).
• Opening the HTML5 console of a virtual machine fails.
• You see an error similar to:
  
  Could not connect to VCSA_Address:7331
• The vsphere_client_virgo.log file (located at: /var/log/vmware/vsphere-client/logs/)contains entries similar to:
  
  [YYYY-MM-DD 15:12:37.938] [WARN ] Thread-39 com.vmware.mks.LifeCycleManager  Process has unexpetedly ended with exception: org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "java" (in directory "/usr/lib/vmware-vsphere-client/server/work/tmp/console-distro"): error=2, No such file or directory)

Cause

This issue occurs if the VMWARE_JAVA_HOME environmental variable is not properly set after restarting the vCenter Server Appliance. 

Resolution

This is a known issue affecting vSphere Web Client 5.5 running in VCSA 5.5.

 

To work around this issue, set the VMWARE_JAVA_HOME environmental variable to /usr/java/jre-vmware.

 

To set the VMWARE_JAVA_HOME environmental variable:

1. Connect to the vCenter Server Appliance via SSH as the root user.
   
   Note: To enable SSH on the vCenter Server Appliance 5.5, see Enable or Disable SSH Administrator Login on the VMware vCenter Server Appliance in the vCenter Server and Host Management Guide.
   
2. Open the wrapper.conf file (located at: /usr/lib/vmware-vsphere-client/server/wrapper/conf/) using a text editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
3. Add this line under the Environmental Variables section:
   
   set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware
   
   For example, modify the default configuration file to:
   
   # Environment Variables
   ##################
   # Location of virgo server directory
   set.VIRGO_KERNEL_HOME=/usr/lib/vmware-vsphere-client/server
   # Location of NGC instance directory
   set.default.INSTANCE_DIR=/user/lib/vmware-vsphere-client/server
   set.default.CONFIG_DIR=%INSTANCE_DIR%/configuration
   set.default.JMX_PORT=9875
   set.default.LOG_DIR=/var/log/vmware-vsphere-client/server
   set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware
   
4. Save and close the wrapper.conf file.
5. Restart the vSphere Web Client using this command:
   
   /etc/init.d/vsphere-client restart
   Note: If the issue persists, you may need to reboot the vCenter Server Appliance and restart the vSphere Web Client again.

Source:-

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2060604

How Does vCloud Director 5.1 Fit In?

Virtual Machine Hardware Maximums

VMware Virtual Appliances Default Username and Password

VMware Appliances	Username	Password
vSphere Management Assistant (vMA)	vi-admin	Can be Provided during initial configuration
VMware vCenter Server Appliance(vCSA)	root	vmware
VMware vShield Manager Appliance	admin	default
vSphere Data Recovery Appliance	root	vmw@re
VMware vCenter Operations Manager	admin	admin
VMware vCloud Director Appliance	root	Default0

VMware Certification Levels

To Know more about Vmware Certifications Visit this Page:-
http://mylearn.vmware.com/portals/certification/

Vmware Product Walkthroughs

http://vmwarewalkthroughs.com/

Device and I/O Virtualization

Memory Virtualization

CPU Virtualization

Identifying the vCenter Single Sign-On server deployment mode (2035817)

Details

vCenter Single Sign-On (SSO) can be deployed in three modes: Basic, Cluster (HA), and Multisite. You can choose one of these modes during the installation. However, after installation, the vSphere Web Client does not indicate the mode in which the server is running.

 

This article provides information on identifying the deployment mode in which SSO is running.

Solution

To identify the SSO deployment mode:

1. In the vCenter Single Sign-On server, click Start > Run, type regedit, and click OK. The Registry Editor window opens.
2. Browse to the HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Infrastructure\SSOServer\SetupType key.
3. Check the value of this key. This value determines the SSO deployment mode.
   
   The value of this key can be:
4. • Basic
   • Primary
   • HA
   • Multisite

Note: There are four types of possible values, even though there are only three deployment types. This is because the first node deployed in an HA or Multisite is identified as the Primary node.

Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2035817 

Use Cases for PVLAN

3 Types of Private VLANs

There are 3 types of PVLANs configurable in a vSphere 5 environment. These include:

1. Promiscuous (Primary) – Can communicate with all interfaces in the VLAN. It is the primary PVLAN and is by default the first created. Only 1 promiscuous PVLAN per VLAN can be present at any given time. Routers are typically associated with promiscuous ports.
2. Isolated (Secondary) – Can communicate only with the promiscuous port not with other clients on the same PVLAN. A common use cases for  isolated PVLANs include an ISP’s DMZ.
3. Community (Secondary) - Can communicate with other clients on the same VLAN and the promiscuous port. Commonly used in DVI environments.

Session Files in vMA

Session Files
An alternative to vi-fastpass for automating cached credentials are session files.
Session files are Perl script files that save session credentials in an aptly named saved session file, called save_ session.pl.

Example
save_session.pl –server ‘servername‘  –user name root –password password –savesessionfile /home/vi-admin/esxsession
Once this has been saved, add it to the end of a command run through the vMA.

Example
vicfg-nics -l –sessionfile /home/vi-admin/esxsession

vmware-cmd Command

NAME

vmware-cmd - perform virtual machine operations

---

SYNOPSIS

General Options

  vmware-cmd [--help | -q | -v]

Server Operations

 vmware-cmd -s <conn_option> 
   [-l |
    -s register <config_file_path> [<datacenter>] [<resource_pool>] |
    -s unregister <config_file_path> ]

Virtual Machine Operations

 vmware-cmd <conn_option> <config_file_path>
    [answer |
     connectdevice <device_name> |
     createsnapshot <name> <description> quiesce [0|1] memory [0|1] |
     disconnectdevice <device_name> |
     getconfigfile |
     getguestinfo <variable> |
     getproductinfo [product|platform|build|majorversion|minorversion] |
     getstate |
     gettoolslastactive |
     getuptime |
     hassnapshot |
     reset [soft|hard] |
     removesnapshots
     revertsnapshot |
     setguestinfo <variable> <value> |
     start |
     suspend [soft|hard] ]

---

DESCRIPTION

vmware-cmd provides an interface to perform operations on a virtual machine. You can retrieve information such as the power state, register and unregister the virtual machine, set configuration variables, and manage snapshots.

---

OPTIONS

CONNECTION OPTIONS

The vmware_cmd vSphere CLI command connection options differ from those of most other vSphere CLI commands.

-H <host>

Specifies an ESX/ESXi host or a vCenter Server system.

-h | --vihost <esx_host>

Specifies a target host if the host specified by -H <host> is a vCenter Server system.

-O <port>

Specifies an alternative port. Default is 443

-U <user_name>

Name of the user who connects to the target. This user must have privileges to perform the operation.

-P <password>

Password of the user specified by <username>. Required if a user is specified.

--config <connection_config_file>

Location of a configuration file that specifies connection information.

--credstore <cred_store>

Name of a credential store file.

--sessionfile <session_file>

Name of a session file that was saved earlier using the vSphere SDK for Perl session/save_session.pl script.

--passthroughauth <passthroughauth>

If you specify this option, the system attempts to connect using Microsoft Windows Security Support Provider Interface (SSPI).

GENERAL OPTIONS

--help

Prints a help message for each command-specific and each connection option. Calling the script with no arguments or with --help has the same effect.

-q

Turns on quiet mode with minimal output.

-v

Turns on verbose mode.

---

OPERATIONS

The following operations require that you specify the path to the virtual machine configuration file. Choose one of the following formats:

Datastore prefix style: [ds_name] <relative_path>

For example:

  '[myStorage1] testvms/VM1/VM1.vmx' (Linux) 
  "[myStorage1] testvms\VM1\VM1.vmx" (Windows)

UUID-based path: folder/subfolder/file

For example:

  '/vmfs/volumes/mystorage/testvms/VM1/VM1.vmx' (Linux) 
  "/vmfs/volumes/mystorage/testvms/VM1/VM1.vmx" (Windows)

SERVER OPERATIONS

-l

Lists all registered virtual machines.

-s register <config_file_path[<datacenter>] [<resource_pool>]

Registers a virtual machine.

If -H specifies a vCenter Server system, you must specify the datacenter and the resource pool to register the virtual machine in. The default datacenter is ha-datacenter and the default resource pool is Resources.

If -H specifies an ESX/ESXi system, you usually do not specify the resource pool and datacenter. However, if two virtual machines with the same name exist in two resource pools, you must specify the resource pool.

-s unregister

Unregisters a virtual machine.

VIRTUAL MACHINE OPERATIONS

<config_file_path> answer

Prompts the user to answer a question for a virtual machine waiting for user input.

connectdevice <config_file_path> <device_name>

Connects a virtual device to a virtual machine.

<config_file_path> createsnapshot <name> <description> quiesce 0|1 memory 0|1

Creates a snapshot of the specified virtual machine, providing a name and description for the snapshot.

If the <quiesce> flag is 1 and the virtual machine is powered on when the snapshot is taken, VMware Tools is used to quiesce the file system in the virtual machine. Quiescing a file system is a process of bringing the on-disk data of a physical or virtual computer into a state suitable for backups. This process might include such operations as flushing dirty buffers from the operating system's in-memory cache to disk, or other higher-level application-specific tasks.

If the <memory> flag is 1, a dump of the internal state of the virtual machine is included in the snapshot. Memory snapshots take longer to create.

<config_file_path> disconnectdevice

Disconnects the specified virtual device from the virtual machine.

<config_file_path> getconfigfile

Returns a string containing the name of the virtual machine configuration file. This command fails if the virtual machine is not connected.

<config_file_path> getguestinfo

Retrieves the value for a GuestInfo variable. The variable contains the attributes of the guest operating system of a virtual machine. For example, you can run the following command to retrieve the IP address of a virtual machine: vmware-cmd <config_file-path> getguestinfo ip You usually use this command when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

<config_file_path> getproductinfo

Returns information about the product, where <prodinfo> is product, platform, build, majorversion (product major version number), or minorversion (product minor version number). If product is specified, the return value is one of the following:

  esx -- VMware ESX
  embeddedESX -- VMware ESXi
  unknown (unknown product type)

If platform is specified, the return value is one of the following:

  win32-x86 -- x86-based Windows system
  linux-x86 -- x86-based Linux system
  vmnix-x86 -- x86 ESX/ESXi microkernel

<config_file_path> getstate

Retrieves the execution state of a virtual machine. The state can be on, off, suspended, or unknown.

<config_file_path> gettoolslastactive

Returns an integer indicating how much time has passed, in seconds, since the last heartbeat was detected from the VMware Tools service. This value is initialized to zero when the virtual machine powers on. It stays at zero until the first heartbeat is detected. After the first heartbeat, the value is always greater than zero until the virtual machine is power cycled again. The command can return one of the following:

• 0 -- VMware Tools are not installed or not running.
• 1 -- Guest operating system is responding normally.
• 5 -- Intermittent heartbeat. There might be a problem with the guest operating system.
• 100 -- No heartbeat. Guest operating system might have stopped responding

<config_file_path> getuptime

Returns the uptime (in seconds) of the guest operating system on the virtual machine.

<config_file_path> hassnapshot

Returns 1 if the virtual machine already has a snapshot. Returns 0 otherwise.

<config_file_path> removesnapshots

Removes all snapshots belonging to the virtual machine. If no snapshot exists, does nothing.

<config_file_path> reset [soft|hard]

Shuts down, and then reboots a virtual machine. The powerop_mode can be hard or soft. Default is soft.

<config_file_path> revertsnapshot

Reverts the virtual machine to the current snapshot. If no snapshot exists, does nothing and leaves the virtual machine state unchanged.

<config_file_path> setguestinfo<variable> <value>

Writes a GuestInfo variable into memory. This is an advanced command. You usually use this command when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

<config_file_path> start

Powers on a previously powered-off virtual machine or resumes a suspended virtual machine.

<config_file_path> stop

Shuts down and powers off a virtual machine. The powerop_mode can be hard or soft. Default is soft.

<config_file_path> suspend [soft|hard]

Suspends a virtual machine. The default powerop_mode is soft.

---

EXAMPLES

The following examples assume you are specifying connection options, either explicitly or, for example, by specifying the server, user name, and password. Run vmware-cmd --help for a list of common options including connection options.

SERVER OPERATIONS

List all the registered virtual machines:

 vmware-cmd <connection_options> -l

Register a virtual machine:

 vmware-cmd <connection_options>
    -s register /vmfs/volumes/storage1/MyVM/MyVM.vmx

Unregister a virtual machine:

 vmware-cmd <connection_options>
    -s unregister /vmfs/volumes/storage1/MyVM/MyVM.vmx

VIRTUAL MACHINE OPERATIONS

Get the execution state of a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getstate

Power on a virtual machine with 'soft' power mode (requires VMware Tools):

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx start soft

Power on a virtual machine with 'hard' power mode:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx start hard

Set a guest info variable for a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx setguestinfo VarABC 102

Retrieve the value for a guest info variable for a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getguestinfo VarABC

Get the platform information:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getproductinfo platform

Get the build information:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getproductinfo build

Connect a virtual CD/DVD drive to a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx connectdevice "CD/DVD Drive 2"

Disconnect a virtual CD/DVD drive from a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx disconnectdevice "CD/DVD Drive 2"

Retrieve the path to the configuration file for a virtual machine:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getconfigfile

Retrieve the uptime of a virtual machine's guest OS:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getuptime

Answer a question for a virtual machine requesting input:

 vmware-cmd <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx answer

Retrieve the VMware tools status:

 vmware-cmd -U <connection_options>
    /vmfs/volumes/storage1/MyVM/MyVM.vmx gettoolslastactive

DATACENTER OPERATIONS

You can perform any of the datacenter operations on a vCenter Server system by specifying the vCenterServer system using the -H option and the ESX/ESXi host using the --vihost | -h option. To register a virtual machine on a vCenter Server system, you have to specify the datacenter and resource pool name. For example:

Register a virtual machine.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC --vihost ESXHost
    -s register /vmfs/volumes/storage1/MyVM/MyVM.vmx DatacenterA PoolC

Get the execution state of a virtual machine.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC -h ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getstate

Get the product information.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC --vihost ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx getproductinfo product

Determine if the virtual machine has snapshot.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC -h ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx hassnapshot

Create a snapshot.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC -h ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx createsnapshot  <name> <description>
       <quiesce> <memory>

Revert the virtual machine to the last snapshot.

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC -h ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx revertsnapshot

Remove all the snapshots of virtual machine

 vmware-cmd -U <myuser> -P <mypassword> -H VCServerABC -h ESXHost
    /vmfs/volumes/storage1/MyVM/MyVM.vmx removesnapshots

Thanks to Vmware Documentation

vicfg-advcfg Command

NAME

vicfg-advcfg - query and modify advanced VMkernel options. Use when instructed by Technical Support.

vicfg-advcfg - enable and disable CIM providers.

---

SYNOPSIS

 vicfg-advcfg <connection_options>
   [--default <value> |
    --get <path> |
    --get-kernel <boot_parameter> |
    --quiet |
    --help |
    --set <value> <option> |
    --set 0|1 UserVars.CIMEnabled |
    --set 0|1 UserVars.CIMOEMProvidersEnabled |
    --set 0|1 UserVars.CIMCustomProvidersEnabled |
    --set-kernel <value> <boot_parameter> |
    --set-message <message> |
    --vihost <esx_target>]

---

DESCRIPTION

The vicfg-advcfg command offers a number of low-level advanced options.

Most options are not intended for customer use. You might use this command when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

You can use the vicfg-advcfg -s option to enable and disable CIM providers.

---

OPTIONS

connection_options

Specifies the target server and authentication information if required. Run vicfg-advcfg --help for a list of all connection options.

--default | -d <option>

Sets the value of a specific configuration item to the default value defined by the VMkernel. Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--get | -g <config_option>

Gets the value of a configuration option based on its path, and print the value to stdout. Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--get-kernel | -j <boot_param>

Gets the value of a VMkernel boot parameter. Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--help

Prints a help message for each command-specific and each connection option. Calling the script with no arguments or with --help has the same effect.

--quiet | -q

No output to stdout while executing the command.

--set | -s <value> <option>

Sets the value of a configuration option based on its path. Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--set | -s 0|1 UserVars.CIMEnabled

Enables or disables all CIM providers.

--set | -s 0|1 UserVars.CIMOEMProvidersEnabled

Enables or disables OEM CIM providers.

--set | -s 0|1 UserVars.CIMCustomProvidersEnabled

Enables or disables IHV CIM providers.

--set-kernel | -k <value> <boot_param>

Sets the value of a VMkernel boot parameter. Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--set-message | -m <message>

Sets DCUI welcome message (valid for vSphere 4.0 and later). Use this option when VMware Technical Support or a VMware Knowledge Base article instruct you to do so.

--list | -l

Lists all VMkernel advanced config options.

--vihost | -h <esx_target<gt

>

When you execute a vSphere CLI with the --server option pointing to a vCenter Server System, you can use --vihost to specify the ESX/ESXi host to run the command against.

---

EXAMPLES

The following examples assume you are specifying connection options. Run vicfg-advcfg --help for a list of common options including connection options.

Set the value of a specific configuration item given its identifying path and the value to set:

 vicfg-advcfg <conn_options> -s 1 VMkernel.Boot.xapicForce

Get the value of a specific configuration item given its identifying path, and print the value to stdout:

 vicfg-advcfg <conn_options> -g VMkernel.Boot.xapicForce

Set the value of a specific configuration item to the default value defined by the VMkernel:

 vicfg-advcfg <conn_options> -d Irq.RoutingPolicy

Retrieve a VMkernel option:

 vicfg-advcfg <conn_options> --get-kernel assumeCommonBusClock

Set a VMkernel option:

 vicfg-advcfg <conn_options> --set-kernel 1 assumeCommonBusClock

Set a DCUI welcome message

 vicfg-advcfg <conn_options> --set-message "Welcome message"

Enable all CIM providers:

 vicfg-advcfg.pl <conn_options> -s 1 UserVars.CIMEnabled

Enable OEM CIM providers:

 vicfg-advcfg.pl <conn_options> -s 1 UserVars.CIMOEMProvidersEnabled

Disable IHV CIM providers:

 vicfg-advcfg.pl <conn_options> -s 0 UserVars.CIMCustomProvidersEnabled

Thanks to Vmware Documentation