Académique Documents
Professionnel Documents
Culture Documents
1. What is HA?
VMware HA delivers the availability needed by many applications running in virtual machines, independent of the
operating system and application running in it. VMware HA provides uniform, cost-effective failover protection
against hardware and operating system failures within your virtualized IT environment.
Restarts virtual machines on other physical servers in the resource pool without manual intervention
when server failure is detected.
Protects applications from operating system failures by automatically restarting virtual machines when
an operating system failure is detected.
2. How HA works?
VMware HA continuously monitors all servers in a resource pool and detects server failures. An agent placed on
each server maintains a ³heartbeat´ with the other servers in the resource pool and a loss of ³heartbeat´ initiates
the restart process of all affected virtual machines on other servers. VMware HA ensures that sufficient resources
are available in the resource pool at all times to be able to restart virtual machines on different physical servers in
the event of server failure. Restart of virtual machines is made possible by the Virtual Machine File System
(VMFS) clustered file system which gives multiple ESX Server instances read-write access to the same virtual
machine files, concurrently. VMware HA is easily configured for a resource pool through VirtualCenter.
2
Automate the monitoring of physical server availability. HA detects
server failures and initiates the virtual machine restart without any human intervention.
Ensure that capacity is always available in order to restart all virtual machines affected by
server failure. HA continuously monitors capacity utilization and ³reserves´ spare
capacity to be able to restart virtual machines.
2
Protect any application with automatic restart in a different physical
server in the resource pool.
(when used with VMware Distributed Resource Scheduler (DRS)). Automate the
optimal placement of virtual machines restarted after server failure.
c 2
With VMware HA, a set of ESX Server hosts is combined into a cluster with a shared pool ofresources. VMware
HA monitors all hosts in the cluster. If one of the hosts fails, VMware HAimmediately responds by restarting each
affected virtual machine on a different host.
VMware HA Features
Using a cluster enabled for VMware HA provides the following features:
Automatic failover is provided on ESX Server host hardware failure for all running virtualmachines within the
bounds of failover capacity.
VMware HA provides automatic detection of server failures and initiates the virtualmachine restart without any
human intervention.
VMware HA can take advantage of DRS to provide for dynamic and intelligent resourceallocation and
optimization of virtual machines after failover. After a host has failed andvirtual machines have been restarted on
other hosts, DRS can provide further migrationrecommendations or migrate virtual machines for more optimum
host placement andbalanced resource allocation.
VMware HA supports easy-to-use configuration and monitoring using VirtualCenter. HAensures that capacity is
always available (within the limits of specified failover capacity) inorder to restart all virtual machines affected by
server failure (based on resourcereservations configured for the virtual machines.)
HA continuously monitors capacity utilization and "reserves" spare capacity to be able torestart virtual
machines. Virtual Machines can fully utilize spare failover capacity whenthere hasn't been a failure.
3. What is DRS?
Dynamically allocate IT resources to the highest priority applications. Create rules and policies to
prioritize how resources are allocated to virtual machines.
Give IT autonomy to business organizations. Provide dedicated IT infrastructure to business units while
still achieving higher hardware utilization through resource pooling.
Empower business units to build and manage virtual machines within their resource pool while giving
central IT control over hardware resources.
Improve service levels for all applications. VMware DRS continuously balance capacity will ensure that
each virtual machine has access to appropriate resources at any point in time.
Easily deploy new capacity. VMware DRS will seamlessly take advantage of the additional capacity of
new servers added to a resource pool by redistributing virtual machines without system disruption.
Automate planned server maintenance. VMware DRS can automatically migrate all virtual machines off
physical servers to enable scheduled server maintenance with zero downtime.
Dramatically increase system administrator productivity. Enable system administrators to monitor and
effectively manage more IT infrastructure.
Features
The following is a list of the key features of VMware DRS.
!
"
#
Organize resource pools hierarchically to match available IT
resources to the business organization. VMware DRS ensures that resource utilization is maximized
while business units retain control and autonomy of their infrastructure. Resource pools can be flexibly
added, removed, or reorganized as business needs or organization change.
Assign priorities in the form of shares or reservations to virtual machines within
resource pools and to sub resource pools to reflect business priorities. For example, the production sub
resource pool can have higher shares of the total resources in a cluster and business critical
applications within the production resource pool can have fixed guarantees(reservations) of CPU
bandwidth and memory,
2
Create rules that govern placement of virtual machines on physical servers. For
example, a group of virtual machines can be set to always run on the same server for performance
reasons. Alternatively, certain virtual machines can be set to always run on different servers to increase
availability. New in vSphere 4.1 is the ability to restrict placement of virtual machines to a group of
physical servers in a cluster. This is useful for controlling the mobility of virtual machines that run
software licensed for a specific group of physical servers. In addition, this feature can be used to keep
sets of virtual machines on different racks or blade systems for availability reasons.
Reduce energy consumption in the datacenter by using the Distributed Power
Management (DPM) feature of DRS to consolidate workloads and power off servers when they are not
needed by the virtual machines in the cluster. When resource requirements of virtual machines
increase, DPM brings hosts back online so service levels can be met.
2
VMware DRS collects resource usage information from servers and
virtual machines, and then generates recommendations to optimize virtual machine allocation. These
recommendations can be executed automatically or manually.
a
When a virtual machine is first powered on, VMware DRS either
automatically places the virtual machine on the most appropriate physical server or makes a
recommendation.
a
#
VMware DRS continuously optimizes resource allocations based
on defined resource allocation rules and resource utilization. The resource allocation changes
can be automatically executed by performing live migration of virtual machines through
vMotion. Alternatively, in manual mode, VMware DRS provides execution recommendations
for system administrators.
X$ Manage CPU and memory across up to 32 servers and 1280 virtual
machines per DRS cluster.
4. What is vMotion?
Perform hardware maintenance without scheduling downtime and disrupting business operations.
Identify the optimal placement for a virtual machine in seconds with a migration wizard providing real-
time availability information.
Migrate any virtual machine running any operating system across any type of hardware and storage
supported by vSphere, including Fibre Channel SAN, NAS and iSCSI SAN.
Prioritize live migrations to ensure that mission-critical virtual machines maintain access to the
resources they need.
First, the entire state of a virtual machine is encapsulated by a set of files stored on shared storage such as Fibre
Channel or iSCSI Storage Area Network (SAN) or Network Attached Storage (NAS). VMware vStorage VMFS
allows multiple installations of VMware ESX® to access the same virtual machine files concurrently.
Second, the active memory and precise execution state of the virtual machine is rapidly transferred over a high
speed network, allowing the virtual machine to instantaneously switch from running on the source ESX host to
the destination ESX host. VMotion keeps the transfer period imperceptible to users by keeping track of on-going
memory transactions in a bitmap.
Once the entire memory and system state has been copied over to the target ESX host, VMotion suspends the
source virtual machine, copies the bitmap to the target ESX host, and resumes the virtual machine on the target
ESX host. This entire process takes less than two seconds on a Gigabit Ethernet network.
Third, the networks being used by the virtual machine are also virtualized by the underlying ESX host, ensuring
that even after the migration, the virtual machine network identity and network connections are preserved.
VMotion manages the virtual MAC address as part of the process. Once the destination machine is activated,
VMotion pings the network router to ensure that it is aware of the new physical location of the virtual MAC
address.
Since the migration of a virtual machine with VMotion preserves the precise execution state, the network identity,
and the active network connections, the result is zero downtime and no disruption to users.
£
"
.
Proven by thousands of customers in production environments since 2004, VMotion continues to set the standard
for the most dependable live migration capabilities.
Perform live migrations with downtime unnoticeable to the end users. Optimal use of CPU and network resources
ensures that the live migrations occur quickly and efficiently.
"
Migrate virtual machines running any operating system across any type of hardware and storage supported by
VMware ESX.
Support for Fibre Channel SAN.
Implement live migration of virtual machines utilizing a wide range of up to 4GB Fibre Channel SAN storage
systems.
NAS and iSCSI SAN support. Implement live migration of virtual machines with lower-cost,
more easily managed shared storage.
Customizable CPU compatibility settings. Ensure that virtual machines can be migrated across different
versions of hardware. Enable virtual machines to benefit from the latest CPU innovations.
New - Enhanced VMotion Compatibility. Live migrate virtual machines across different generations of
hardware. Migrate virtual machines from older servers to new ones without disruption or downtime.
"
Migration wizard.
Quickly identify the best destination for a virtual machine usingreal-time information provided by migration
wizard.
Multiple concurrent migrations.
Perform multiple concurrent migrations to continuouslyoptimize virtual machine placement across the entire
IT environment.
Priority levels.
Assign a priority to each live migration operation to ensure thatthe most important virtual machines always have
access to theresources they need.
Scheduled migration tasks.
Automate migrations to happen at pre-defined times, andwithout an administrator¶s presence.
Migration audit trail.
Maintain a detailed record of migration operations, includingdate/time and the administrators responsible for
initiating them.
Before moving a virtual machines disk file, Storage VMotionmoves the ³home directory´ of the virtual machine to
the newlocation. The home directory contains meta data about thevirtual machine (configuration, swap and log
files). Afterrelocating the home directory, Storage VMotion copies thecontents of the entire virtual machine
storage disk file to thedestination storage host, leveraging ³changed block tracking´ tomaintain data integrity
during the migration process. Next, thesoftware queries the changed block tracking module todetermine what
regions of the disk were written to during thefirst iteration, and then performs a second iteration of copy,where
those regions that were changed during the first iterationcopy (there can be several more iterations).
Once the process is complete, the virtual machine is quicklysuspended and resumed so that it can begin using
the virtualmachine home directory and disk file on the destinationdatastore location. Before VMware ESX allows
the virtualmachine to start running again, the final changed regions of thesource disk are copied over to the
destination and the sourcehome and disks are removed.
This approach guarantees complete transactional integrity and isfast enough to be unnoticeable to the end user.
£
c c
No interruption or downtime for users and applications duringvirtual machine storage disk migrations.
"
Storage VMotion can migrate storage disk files for virtualmachines running any operating system across any type
ofhardware and storage supported by VMware ESX.
1) How we manage the licenses, i.e. timely updating licenses, briefly
explain?
------------------------------------------------------------------------------------------------
-----------------------
2) If we found HA issue, what are steps we should follow to resolve the
issues?
To troubleshoot HA errors:
Note: Most of these troubleshooting steps are done on the ESX console.
1.Run this command to verify that host name is in lowercase and is fully
qualified:
hostname
hostname ±s
hostname ±i
4.Verify that the host name in /etc/hosts is lowercase and both FQDN
and shortname are present.
5.Verify that the search domain is present in the /etc/resolv.conf fil e and
is in lowercase.
6.Verify that the host name in /etc/sysconfig/network is FQDN and is in
lowercase.
7.Verify that the host name in the /etc/vmware/esx.conf file is FQDN and
is in lowercase.
8.Verify that the system name returned by the uname -a command is in
lowercase.
9.Verify that the host name is in your DNS server and is in lowercase. To
do this, run these commands:
a.nslookup<hostname>
Where <hostname> is the name of the host.
b.nslookup<FQDN_name>
c.nslookup<ipaddress>
10.Make sure the route for the service console is correct. To do this,
from each host, ping the other hosts in the environment.
11.Verify that all primary service consoles have the same name.
12.Verify that all primary service consoles are in the same IP subnet .
13.If the vmkernel port group of vMotion is on same vSwitch as primary
Service Console port group, add das.allowVmotionNetworks=1 to the
advanced settings of
HA.
14.If the host has multiple service consoles, add das.allowNetwork0 to
the Advanced HA Settings of the cluster to ensure that only the primary
service
available.
If you are unable to configure HA after verifying these troubleshooting
steps:
1.Run this command on the ESX host to stop vpxa:
servicevmware-vpxa stop
The host appears as not responding in the vCenter Server after a while.
------------------------------------------------------------------------------------------------
-----------------------
3) Redundancy between NICs in an ESX server & how many minimum
NICs required for esx
------------------------------------------------------------------------------------------------
-----------------------
4) Minimum requirements for VMotion configure?
------------------------------------------------------------------------------------------------
-----------------------
5) How licenses calculated/purchased for VMware environment?
------------------------------------------------------------------------------------------------
-----------------------
6) What are the partitions of an ESX server?
Service Console Partitions and Sizes for Each ESX Server Host
/dev/sda (Primary)
N/A swap 1600 MB Change for maximum service console swap size
/dev/sda (Extended)
/var ext3 4096 MB Create partition to avoid overfilling root with log files
/opt ext3 2048 MB Create partition to avoid overfilling root with VMware
HA log files
/home ext3 1024 MB Create partition to avoid overfilling root with agent /
user files
------------------------------------------------------------------------------------------------
------------------------------
7) Whether we need licenses for HA, DRS feature?
Yes,
------------------------------------------------------------------------------------------------
------------------------------
8) What should be the main reason for purple screen errors?
------------------------------------------------------------------------------------------------
------------------------------
9) How to configure virtual switches & what is port-group & what is
VLAN?
------------------------------------------------------------------------------------------------
-----------------
10) Whether HA use VMotion or not?
------------------------------------------------------------------------------------------------
-----------------
11) Whether DRS use VMotion or not?
yes
------------------------------------------------------------------------------------------------
-----------------
12) What are processes & port numbers for virtual center, HA running in
ESX?
Ports and descriptions:
443 - Listens for connections from the vSphere Client, vSphere Web
Access Client, and other SDK clients. Open port 443 in the firewall to
enable the vCenter
389 - This port is used for Lightweight Directory Access Protocol (LDAP)
services. Who says LDAP, says Active Directory Services for the
vCenter Server
group.
636 ± SSL port of the local instance for vCenter Linked Mode. It¶s the
port of the local vCenter Server ADAM Instance.
902 - Used to send data to managed hosts. To send data to your ESX or
ESXi hosts. Also this port is used for remote console access to virtual
machines from
vSphere Client. This port must not be blocked by firewalls between the
server and the hosts or between hosts.
tolocalhosts if the clients are installed on the same host as the vCenter
Server service.
--------Various services are installed when you deploy vCenter, in total 5
services are installed----------
------------------------------------------------------------------------------------------------
---------------
------------------------------------------------------------------------------------------------
----------------------
14) Explain the purpose of Redo log files?
------------------------------------------------------------------------------------------------
-------------------------
15) VM is not able to power off, how to trouble shoot d issues?
To determine if you must use the command line, attempt to power off the
virtual machine:
1.Connect VMware Infrastructure (VI) Client to the Virtual Center Server.
Right-click on the virtual machine and click Power off.
2.Connect VI Client directly to the ESX host. Right-click on the virtual
machine and click Power off.
If this does not work, you must use the command line method.
Determining the virtual machine's state
1.Determine the host on which the virtual machine is running. This
information is available in the virtual machine's Summary tab when
viewed in the VI Client
page.
2.Log in as root to the ESX host using an SSH client.
3.Run the following command to verify that the virtual machine is running
on this host:
# vmware-cmd -l
The output of this command returns the full path to each virtual machine
running on the ESX host. Verify that the virtual machine is listed, and
record the
# /vmfs/volumes/<UUID>/<VMDIR>/<VMNAME>.vmx
4.Run the following command to determine the state in which the ESX
host believes the virtual machine to be operating:
# vmware-cmd<path.vmx>getstate
If the output from this command is getstate() = off, the ESX host may be
unaware it is still running the virtual machine. This article provides
additional
Use the following procedure when you want to investigate the cause of
the issue. This command attempts to power off the virtual machine while
collecting
2.Kill the virtual machine by using the following command in the home
directory of the virtual machine:
# vm-support -X <world_ID>
Note: This command uses several different methods to stop the virtual
machine. When attempting each method, the command waits for a pre-
determined amount of
# cat /proc/vmware/vm/*/names
# less -S /proc/vmware/vm/####/cpu/status
3.Scroll to the right with the arrow keys until you see the group field. It
appears similar to:
Group
vm.####
4.Run the following command to shut the virtual machine down with the
group ID:
# /usr/lib/vmware/bin/vmkload_app -k 9 ####
If the preceding steps fail, perform the following steps for an ESX 4.x
host:
1.List all running virtual machines to find the vmxCartelID of the affected
virtual machine with the command:
# /usr/lib/vmware/bin/vmdumper -l
2.Scroll through the list until you see your virtual machine's name. The
output appears similar to:
3.Run the following command to shut the virtual machine down with the
vmxCartelID:
# /usr/lib/vmware/bin/vmkload_app -k 9 ####
Powering off the virtual machine using the vmware-cmd command
This procedure uses the ESX command line tool, and attempts to
gracefully power off the virtual machine. It works if the virtual machine's
process is running
vmware-cmd<path.vmx> stop
# vmware-cmd<path.vmx>getstate
2.From the Service Console of the ESX host, run the command:
# vmware-cmd<path.vmx>stop hard
Note: <path.vmx> is the complete path to the configuration file, as
determined in the previous section. To verify that it is stopped, run t he
command:
# vmware-cmd<path.vmx>getstate
3.If the virtual machine is still inaccessible, proceed to the next section.
Using the ESX command line to kill the virtual machine
If the virtual machine does not power off using the steps in this article, i t
has likely lost control of its process. You need to manually kill the
process
have unanticipated results. If you are not comfortable with the following
procedure, contact VMware Technical Support and open a Service
Request. Please
The output of this command appears similar to the following if the .vmx
process is running:
Server;version=3.5.0;licensename=VMware ESX
Server;licenseversion=2.0 build-158874; -@ pipe=/tmp/vmhsdaemon-
0/vmx569228e44baf49d1; /vmfs/volumes/49392e30-
162037d0-17c6-001f29e9abec/<VMDIR>/<VMNAME>.vmx
The process ID (PID) for this process is in bold. In this example, the PID
is 3093. Take note of this number for use in the following steps.
Caution: Ensure that you identify the line specific only to the virtual
machine you are attempting to repair. If you continue this process for
another
virtual machine the one in question, you can cause downtime for the
other virtual machine.
If the .vmx process is listed, it is possible that the virtual machine has
lost control of the process and that it must be stopped manually.
# kill<PID>
# kill -9 <PID>
------------------------------------------------------------------------------------------------
------------------------------
16) Why we use two different ports for licenses, and what r those port
No.?
27000 --- License transactions from ESX Server 3i to the license server
(lmgrd.exe).|Outgoing TCP|
27010 --- License transactions from ESX Server 3i to the license server
(vmwarelm.exe).|Outgoing TCP|
------------------------------------------------------------------------------------------------
------------------------------
17) VC server is not coming up, how to troubleshoot?
------------------------------------------------------------------------------------------------
------------------------------
18) Difference between ESX3.5 & 4.0?
------------------------------------------------------------------------------------------------
------------------------------
19) Briefly describe about update Manager, is it possible to update the
powered off vms by update manager?
------------------------------------------------------------------------------------------------
------------------------------
20) Explain VMware Snapshot & what is d command to take a
snapshot?
------------------------------------------------------------------------------------------------
------------------------------
21) Suppose we have 3 port groups configured in a single Vswitch
(connected to single physical NIC of the esx host) with 3 different VLANs
so how d VMs from
------------------------------------------------------------------------------------------------
------------------------------
22) What is d command to list all the running VMs & registered VMs?
------------------------------------------------------------------------------------------------
------------------------------
24) What r d P2V conversion processes/tools available, how we can
perform d P2V of a Linux server with d help of CLI commands (in case
no specific tools
available)?
Converter server to Source computer 445, 139, 9089, 9090 137, 138 If
the source computer uses NetBIOS, port 445 is not required. If NetBIOS
is not being
used, ports 137, 138, and 139 are not required. If in doubt, make sure
that none of the ports are blocked.
Note: Unless you have installed Converter server to the source
computer, the account used for authentication to the source computer
must have a password, the
source computer must have network file sharing enabled, and it cannot
be using Simple File Sharing.
Converter server to VirtualCenter443 Only required if the conversion
target is VirtualCenter.
Converter client to Converter server 443 Only required if a custom
installation was performed and the Converter server and client portions
are on different
computers.
Source computer to ESX 443, 902 If the conversion target is
VirtualCenter then only port 902 is required.
Converting a powered on Linux operating system (P2V)
Source Destination TCP Ports Notes
Converter server to Source computer 22 The Converter server must be
able to establish an SSH connection with the source computer.
Converter client to Converter server 443 Only required if a custom
installation was performed and the Converter server and client portions
are on different
computers.
Converter server to VirtualCenter 443 Only required if the conversion
target is VirtualCenter.
Converter server to ESX 443, 902, 903 If the conversion target is
VirtualCenter, only ports 902 and 903 are required.
Converter server to Helper virtual machine 443
Helper virtual machine Source computer 22 The helper virtual machine
must be able to establish an SSH connection with the source computer.
By default the
Converter server to Fileshare path 445, 139 137, 138 This is only
required for standalone virtual machine sources or destinations.
required. If in doubt, make sure that none of the ports are blocked.
Converter client to Converter server 443 Only required if a custom
installation was performed and the Converter server and client portions
are on different
computers.
Converter server to VirtualCenter443 Only required if the target is
VirtualCenter.
Converter server to ESX 443, 902 If the conversion target is
VirtualCenter, only port 902 is required.
------------------------------------------------------------------------------------------------
------------------------------
25) What is d command to check d status of a VM?
vmware-cmd<path.vmx>getstate
For example:
vmware-vim-cmdvmsvc/power.getstate 160
------------------------------------------------------------------------------------------------
------------------------------
26) What is d command to rescan the HBAs?
esxcfg-rescan
------------------------------------------------------------------------------------------------
------------------------------
27) How to find the world ID of a particular VM and what is d VMware
proprietary command to kill the same?
vm-support -x
esxclivmsvm list
List all running virtual machines on the system to see the W orld ID of the
virtual machine you want to
stop.
esxclivmsvm list
The command supports three --type options. Try the types sequentially
(soft before hard, hard before
force). The following types are supported through the --type option:
. soft ± Gives the VMX process a chance to shut down cleanly (like kill or
kill -SIGTERM)
. hard ± Stops the VMX process immediately (like kill -9 or kill -SIGKILL)
. force ± Stops the VMX process when other options do not work.
If all three options do not work, reboot your ESX/ESXi host to resolve the
issue.
------------------------------------------------------------------------------------------------
------------------------------
28) what is d command to add a route in esx to communicate to different
network segment?
##! /bin/bash # case "$1" in 'start') echo "Adding additional routes... "
#ln /etc/init.d/routes
------------------------------------------------------------------------------------------------
------------------------------
------------------------------------------------------------------------------------------------
------------------------------
ESX Host ± 8GB RAM -> Default allocated Service Console RAM =
300MB
ESX Host ± 16GB RAM -> Default allocated Service Console RAM =
400MB
ESX Host ± 32GB RAM -> Default allocated Service Console RAM =
500MB
ESX Host ± 64GB RAM -> Default allocated Service Console RAM =
602MB
ESX Host ± 96GB RAM -> Default allocated Service Console RAM =
661MB
ESX Host ± 128GB RAM -> Default allocated Service Console RAM =
703MB
ESX Host ± 256GB RAM -> Default allocated Service Console RAM =
800MB
cp /etc/vmware/esx.conf /etc/vmware/esx.conf.old
cp /boot/grub/grub.conf /boot/grub/grub.conf.old
/bin/sed -i -e µs/272/800/¶ /etc/vmware/esx.conf
/bin/sed -i -e µs/512/800/¶ /etc/vmware/esx.conf
/bin/sed -i -e µs/272M/800M/¶ /boot/grub/grub.conf
/bin/sed -i -e µs/512M/800M/¶ /boot/grub/grub.conf
/bin/sed -i -e µs/277504/818176/¶ /boot/grub/grub.conf
/bin/sed -i -e µs/523264/818176/¶ /boot/grub/grub.conf
-----------------------------------------------------------------------------------------
ESX 4.x 8000 TCP ESX/ESXi Host (VM Target) TO ESX/ESXi Host
(VM Source) VMotion Communication on VMKernel Interface
ESX 4.x 8000 TCP ESX/ESXi Host (VM Source) TO ESX/ESXi Host
(VM Target) VMotion Communication on VMKernel Interface
ESXi 4.x 8000 TCP ESX/ESXi Host (VM Target) TO ESX/ESXi Host (VM
Source) VMotion Communication on VMkernel Interface
ESXi 4.x 8000 TCP ESX/ESXi Host (VM Source) TO ESX/ESXi Host
(VM Target) VMotion Communication on VMkernel Interface
to VM)
Converter 4.x 22 TCP vCenter Converter Server Source Computer to
be converted Required for conversion of Linux-based source computers
different systems
NetBIOS
Converter 4.x 902 TCP Source Computer to be converted ESX/ESXi
Host Required for data transport during cloning of system to be
converted to target ESX/ESXi
Host
------------------------------------------------------------------------------------------------
------------------------------
32) How to create Vmkcore partition after the esx build?
------------------------------------------------------------------------------------------------
------------------------------
33) What r d agents will install, after adding an esx in VC server?
Vmwarevcenter Agent
------------------------------------------------------------------------------------------------
----------
34) What r d port No. for VMware management service?
------------------------------------------------------------------------------------------------
----------
35) What is d max No of VMs can run per host?
320
------------------------------------------------------------------------------------------------
----------
36) What r all d files going to b create after a vm build?
.vmx, .vmfx, .vmsd, .vmdk (when start 3 more files are created --- .log,
vswp, .nvram)
------------------------------------------------------------------------------------------------
----------
37) What r d location of VC server log files?
C:\ProgramData\VMware\VMware VirtualCenter\Logs
------------------------------------------------------------------------------------------------
---------
38) What r d necessary log files in ESX server?
1) Vmkernel
a. Location: /var/log/
b. Filename: vmkernel
2) Vmkernel Warnings
a. Location: /var/log/
b. Filename: vmkwarning
3) Vmkernel Summary
a. Location: /var/log/
b. Filename: vmksummary
c. This log records information used to determine uptime and
availability statistics for ESX Server. This log is not easily readable by
humans, import
a. Location: /var/log
b. Filename: boot.log
c. Log file of all actions that occurred during the ESX server boot.
a. Location: /var/log/vmware/
b. Filename: hostd.log
6) Service Console
a. Location: /var/log/
b. Filename: messages
7) Web Access
a. Location: /var/log/vmware/webAccess
b. Filename: various files in this location
8) Authentication Log
a. Location: /var/log/
b. Filename: secure
a. Location: /var/log/vmware/aam/
b. Filename: aam_config_util_*.log
a. Location: /var/log/vmware/vpx
b. Filename: vpxa.log
b. FileName: vmware.log
1) Location:
3) Logs rotate each time vpxd is started, and also when it reaches 5
MB in size
VI Client Logs
Miscellaneous Logs
1) Core Dump
a. Location: %SystemRoot%\Temp
c. This file contains various information about the license file and
server.
esx-console logs
sysboot-vmkernel-boot.log , sysboot-dmesg-boot.log, sysboot-vmkernel-
late.log, sysboot-dmesg-late.og, sysboot.log
cd /vmfs/volumes/ESX-Storage-94-1/esxconsole-4c44398f-4238-b888-
226e-001e0bcd236a/logs/
Core-dump location
cd vmfs/volumes/ESX-Storage-94-1/esxconsole-4c44398f-4238-b888-
226e-001e0bcd236a/core-dumps
------------------------------------------------------------------------------------------------
----------------------
39) What is ESXTOP command and how to use this command (with all
the fields/options)?
^L - redraw screen
space - update display
h or ? - help; show this text
q - quit
Sort by:
U:%USED R:%RDY N:GID
Switch display:
c:cpu i:interrupt m:memory n:network
d:disk adapter u:disk device v:disk VM p:power mgmt
For example, the following command would run esxtop in batch mode,
updating all statistics to the file perfstats.csv every 10 seconds for 360
iterations (a
------------------------------------------------------------------------------------------------
-
40) What is d location of esx dump file and how to read it?
Core-dump location
cd vmfs/volumes/ESX-Storage-94-1/esxconsole-4c44398f-4238-b888-
226e-001e0bcd236a/core-dumps
------------------------------------------------------------------------------------------------
-----
41) What id d location of the license file (*.LIC) in VC server and ESX
server?
C:\ProgramData\VMware\VMware VirtualCenter\licenses\site\VMware
VirtualCenter Server\4.0\4.1.0.2
------------------------------------------------------------------------------------------------
----
42) What is d command to check the VMFS version and ESX version?
vmkfstools -P storageN
vmware -v and
vimsh -n -e 'hostsvc/hostsummary' | grepfullName OR
cat /proc/vmware/version
------------------------------------------------------------------------------------------------
-----------
43) How to extend the OS drive of a guest OS (windows VM)
vmkfstools<conn_options> -X 50M
/vmfs/volumes/Storage2/testvm/testvm.vmdk
------------------------------------------------------------------------------------------------
----------
44) What is d command to clone a VM?
# vmkfstools -i
/vmfs/volumes/Datastore04/rhel5_test_template/rhel5_test_template.vm
dk /vmfs/volumes/Datastore04/rhel5_test_clone/rhel5_test_clone.vmdk
------------------------------------------------------------------------------------------------
-----------
45) What is d command to check all d virtual switch configuration
details?
you how to create a new virtual switch and place the service console
port group on it.
Note: To create Service Consoles one at time, you may need to delete
all previous settings. For more information, see Recreating Service
Console Networking
8.Create the vswif (Service Console) interface. For example, run the
command:
Nothing to flush.
[root@esx]# esxcfg-vswif ±l
Name Port Group IP Address Netmask Broadcast Enabled DHCP
v swif0 Service Console 192.168.1.10 255.255.255.0 192.168.1.255 true
false
------------------------------------------------------------------------------------------------
----------------------------------------------
46) What is d command to upgrade the FS fromVMFS2 to VMFS3?
The first thing that you will need to do to perform the upgrade is log into
the ESX 3 host as root. Once logged in then you need to unload the
ESX 3 VMFS
drivers that are currently loaded. The unloading of the VMFS drivers is
for both VMFS 2 and VMFS 3. To perform this you need to run the
commands below.
vmkload_mod -u vmfs2
vmkload_mod -u vmfs3
You then need to load a specific driver for ESX3 that is called the "ESX3
Auxiliary FS driver". The command below that loads this driver also
includes the
vmkload_modfsauxfsauxFunction=upgrade
vmkfstools -T /vmfs/volumes/<yourvmfsvolumename>
Once the upgrade is completed, you need to check and confirm that the
volume is vmfs3. You can do this by running the following command
which is once again
anothervmkfstools command.
vmkfstools -P /vmfs/volumes/<yourmvfsvolumename>
You should also confirm that all your files are ok by checking the file
system. The commonly used list command for file systems at the service
console is "ls
-l". If you have any more volumes to upgrade you may rinse and repeat
the steps above until they are all done. Once all your volumes are
upgraded you do
need to unload the "auxiliary driver" that we loaded before and reload
the normal VMFS drivers. Two ways of doing this, one is to reboot and
the other is to
vmkload_mod -u fsaux
vmkload_mod vmfs2
vmkload_mod vmfs3
------------------------------------------------------------------------------------------------
-------------------------------
47) What is RDM and what r all d File Systems (FS) it supports?
------------------------------------------------------------------------------------------------
-------------------------------
48) What is SRM and how it works?
workloads. Multiple sites can even recover into a single shared recovery
site. Site Recovery Manager can also help with planned datacenter
failovers such as
datacenter migrations.
Non-Disruptive Testing
Automated Failover
. Protect more of your environment with added support for NFS storage
replication.
. Set up many-to-one failover using shared recovery sites.
. Leverage new features in vSphere.
------------------------------------------------------------------------------------------------
-------------------------------
49) What is d series of H/W (virtual) used for VM¶s virtual mother
mother/main board?
------------------------------------------------------------------------------------------------
-------------------------------
50) What r d date store path selections & what r d options available for
network load balancing?
You can display information about paths by running vicfg-mpath with one
of the following options:
. List all devices with their corresponding paths, state of the path,
adapter type, and other information.
vicfg-mpath<conn_options> --list-paths
. Display a short listing of all paths.
vicfg-mpath<conn_options> --list-compact
. List all paths with adapter and device mappings.
vicfg-mpath<conn_options> --list-map
Policy Description
VMW_PSP_FIXED The host always uses the preferred path to the disk
when that path is available. If the host
cannot access the disk through the preferred path, it tries the alternative
paths. If you use the
VMW_PSP_MRU The host uses a path to the disk until the path
becomes unavailable. When the path becomes
unavailable, the host selects one of the alternative paths. The host does
not revert back to the
original path when that path becomes available again. There is no
preferred path setting with
the MRU policy. MRU is the default policy for active Opassive storage
devices and is required
for those devices.