Académique Documents
Professionnel Documents
Culture Documents
Enterprise plus license features: Storage DRS/ Storage IO control/ NW IO control/ Distributed switch/ Host profile and Auto deploy
PORT NO
SSL- 636, WEB CLINET-8080, WEB SERVICE -8443, VCENTER -902/903(HEARTBEAT) ISCSI -3260, SNMP-161/162 NTP -123, SSH-22, FTP-21
LDAP -389, KERBEROS-88 GLOBAL CATLOG 3268 RDP-3389 DNS-53
ESXi6
ESXi 5.5
ESXi 5.1
ESXi 5.0
ESXi 4.x
VM Hardware Ver 10
PhysicalCPU 320
Physical RAM per host4 TB
VM Hardware Ver 9
PhysicalCPU 320
Physical RAM per host 2TB
Max Size of Virtual RDM 2TB
vCPU 2048VMDK size 2 TB
Web client features
Vmotion features
Vsphere data protection /network features
Single sign on
License
vSphere Essentials /vSphere Essentials Plus
vSphere Standard /vSphere Enterprise
vSphere Enterprise Plus"
License
"vSphere Essentials
/Essentials Plus / Standard
/ Advanced / Enterprise
/Enterprise Plus
Single sign on
Oracle/SQL database
40 GB Nic support
VMDK size 62 TB
vCPU 4028
virtual machines Hardware 11: vFlash Read Cache support
128 vCPUs /4 TB vRAM /32 serial VMware VSAN support
ports
Microsoft Windows 2012
Cluster Support
Storage: Virtual Volumes (VVol) RAM 4 TB
Network backup can
improved Storage IO Control
restore/import
Virtual SAN (VSAN 6.0)
SORAGE
NETWORKING
VM-INT-PRINT Page 1
STORAGE
VMFS3 and 5 difference
VMFS3
VMFS5
2tb
MBR style
Block size 1/2/4/8
Sub block size 64kb
RDM support 2TB
Supported host ESX3,4,5x
64tb Storage
GPT Partion table
Only 1 MB
8kb
64TB
Only esxi 5.X above
Commands
Df-h (to check HDD size
Esxcfg-rescan
Esxcli storage core adapter rescanlist
Esxcli iscsi adapter list
vmkfstools
VMDk types
Thick Eager Zeroed: Entire disk space is reserved and unavailable for use by other virtual machines. /Disk will be zeroed out during the creation, Creation time is slow. /Writing performance
is fast
Thick Lazy Zeroed : Data is not erased creating the disk, Fast creation/Writing performance is slow
Thin Provision Disk only use as much data store space /Creation time is very fast/worst first write performance
STORAGE : Migration of a virtual machine files and disks from one datastore to another with Zero downtime, I/Os written to both source and mirrored disks Block-level bitmap identifies hot
and cold block
1) First, the entire state of a virtual machine is encapsulated by a set of files stored on shared storageVMware vStorage VMFS allows multiple ESX to access the same virtual machine files
concurrently
2) VMotion keeps the transfer period imperceptible to users by keeping track of on-going memory transactions in a bitmap.
3) 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
Steps involved in VMWare SvMotion ?
"svMotion copies all the files expect virtual machine disk and create the directory as same the Virtual Machine name on the destination storage.
It uses Changed Block tracking to track the virtual machine disk. The change block tracking knows which region disk includes data. This data will be stored in bitmap and reside either in
memory or in a file.
Pre-copies Virtual machine disk and swap file will start from the source to destination datastore as the first iteration. once it is completed, It only transfers the region which were modified or
written after the first iteration.
ESX performs fast suspend and resume of the virtual Machine. The final changed regions will be copied to the destination before the virtual Machine is resumed on the destination datastore.
Virtual Machine will continue running on the destination datastore and source file and disk will be deleted."
Enhance Vmotion EVC:
Enhanced vMotion enables live virtual machine migration when shared storage is not available.
It is a combination of vmotion & storage vmotion migrated between host & cluster without shared storage, only 2 concrunate host vmotion.
What is single sign-on
Single sign-on (SSO)is a session/user authentication process that permits a user to enter one name and password in order to access multiple applications. The process authenticates the user
for all the applications they have been given rights to and eliminates further prompts when they switch applications during a particular session.
VM-INT-PRINT Page 2
NETWORKING
NETWORKING
Esxcfg-vmknic -l to check ip config
Esxcfg-vswitch -l /Esxcfg-nics -l esxcli netwrok firewall g
Standard Switch
Distributed Switch
NetFlow
A network analysis tool for monitoring the network and for gaining visibility into virtual machine traffic,
A tool that can be used for profiling, intrusion detection, networking forensics, and compliance
Port Mirroring
Port mirroring is a technology that duplicates network packets of a switch port (source) to another port
(destination).
The source s trac is monitored at the desEnaEon.
Port mirroring is used: To assist in troubleshooting >As input for network analysis
appliances
Promiscuous Mode : by default reject with no effect on which frames are receiving
MAC ADDRESS CHANGE : by default accept , it set to reject, gust change to MAC address, no frame
receives.
FORGE TRANSMIT: by default accept help, for creation attacks
TRAFFIC SHAPING :to control VM n/w bandwidth, it disable by default, you can set average peak burst
bandwidth
NETWORK FAILURE: defect by vmkernal by monitoring link state +beacning, Beconing include a load of
62 byte packet approx. every 1 min per physical nic
PORT GROUP : (Segregate type of communication) switched can be sub-divided into smaller units called
port group, port groups are used to manage n/w traffic
(1)Vmkernal (2)VM
VLAN tagging: Esxi support 802.1Q vlan tagging, vlan support by giving a port group vlan id with vlan 1)
Logical grouped n/w independent of physical n/w b) improve performance 3)cost cutting as n/w
without routers. VLAN configured at portgroup level, A group of port group tagged as vlan id.
ACCESS PORT
VM-INT-PRINT Page 3
HA
HA: Enables HA in cluster agent is configured. Agent is responsible for sending heartbeat. HA monitor the available resource in cluster in all the time. HA relies on Master & Slave.
First power on host in master, reaming as slave.
If Master host fail, randomly chosen new Master host from Slave host. at least 1 Master be working. Every 15 Sec by default interval detect failure. you can modify interval by
using HA advance setting.
A host failure is detected, HA service is stopped sending heart beat to other host, it will be isolated by default, isolated host has powered on vms now vm can failover to other
host.
HA Requirements
Cluster features / Minmum 2 esxi- max 32/ 64 (for esxi6) / VMKernal port / 7gb memory / shared storage
How HA Works
1. Install the Agent, FDM host will give MOID No (wallet no)
2. Election process - Master and Slave (Majority of data store and MOID- manage object id (3 digit no) who is having greatest no become Master will be elected.
3. Master contact vcenter- vcenter eill give the information of cluster, protected VMs (running VMs)
4. Vmohost compatibility will check
5. Create host details (it will create folder on all data store also locally (/etc/opt/)
6. Master send the heartbeat packet
7. If master died -it wait aprox 10 seconds, 15 seconds after that it will practice the election process ( election process will happen)
8. New master Host will take the responsible of protected the vms, > Restart the VMs
9. If slave is down - Master wait 5 seconds, 10 seconds and contct storage check the log
What is a slot A slot is a logical representation of the memory and CPU resources that satisfy the requirements for any powered-on virtual machine in the cluster.
What are the slot sizes
Max usages of Cpu and Memory reservations of the Vm.
If no reservations then the default of 256 MHz for Cpu and Memory overhead for Memory is used.
Esxi syslog, esxi dump collector
Log files Vcenter
Vpxd.log: vsphere linet and web services connections and events
Vpxd-profiler.log, profiler.log and scoreboard.log: profiled metrics for operations performed in vcenter
Vsphre logs
/var/log/auth.log : Esxi shell authentication information such as success and failures
/var/log/esxupdate.log: esxi patch and update logs (Useful if you need to know why patch fails)
/var/log/hostd.log : Hostmanagement service logs including virtual machine and host tasks and events
/var/log/shell.log: usage logs that track commands that were run
/var/log/syslog : Management service initialization scheduled tasks and DCUI usuage
/var/log/vod.log : vmkernel observation events
/var/log/vmkernel.log/ core vmkernel logs including device discovery, storage and networking devices and driver information, and virtual machine startup infromation
/var/log/vmkwarning.log: a summary of warnings and alert log messages excerpted from the vmkernal logs
/var/log/vmksummary.log: esxi host startup/shutdown, and an hourly heartbeat with uptime, number of virtual machine running, and service resource consukption
VM-INT-PRINT Page 4
DRS & FT
Friday, June 03, 2016
11:58 PM
DRS : DRS continuously monitors utilization across the hosts and moves virtual machines to balance the computing capacity
Types of DRS. / Fully automated/Partially automated/Manual
Intel_ My Bridge & Sandy Bridge /Pile driver
AMD- Virtualized CPU performance counter
VTurse, code Analy
VM Anti-Affinity - Virtual Machines are kept on different hosts from each other (Enterprise Plus is required
Affinity VM kept together
FT is a technology used by VMware to provide zero downtime for a virtual machine Continuous protection for a VM even in case of a host failure
Is the technique of having 2 VMs in lockstep with each other on 2 separate hosts. In the event of host failure, the second VM will pickup where the first one failed assuming its
exact identity with no interruption in service or loss in connectivity
FT 6.0 features - SMP FT (4vCPUs) / 64GB memory/10Gbps recommended /VADP backup supported
what is FT? Fault Tolerance provides zero down time, zero data loss and continues availability of the applications.
what are the requirements of Fault Tolerance?
Vm should be in shared Datastore. /Single Vcpu for Vm. /Hardware virtualization should be enabled in BIOS / 3 nics of minimum of 1GB.
Cpus must mach and be from a specific list of processors. /Only 4 ft enabled Vm in a single Esx.
VM-INT-PRINT Page 5
VIRTUAL MACHINE
Configuration file (<VM_name>.vmx) / Swap files (<VM_name>.vswp) (vmx-<VM_name>.vswp) /BIOS file (<VM_name>.nvram)
Log files (vmware.log) / Template file (<VM_name>.vmtx) / Raw device map file (<VM_name>-rdm.vmdk) /Disk descriptor file (<VM_name>.vmdk)
Disk data file (<VM_name>-flat.vmdk) / Suspend state file (<VM_name>.vmss) /Snapshot data file (<VM_name>.vmsd) /Snapshot state file (<VM_name>.vmsn)
Snapshot disk file (<VM_name>-delta.vmdk)
MEMORY :
Transparent page sharing/ Ballooning technic /Swap/Memory compression
Ballooning : Memory ballooning is a memory management technique that allows a physical host to take advantage of unused memory on its guest virtual machines (VMs).
vSwap file : allocated memory for vm-reserved memory for vm
CLONE AND TEMPLATE
CLONE
1. Cone copy for VM
2. You cannot convert back to cloned VM
3.Template cannot be edited or Powered On
TEMPLATE
1.Master copy of VM
2.Can be converted VM to update the base template
SNAPSHOT
Point in time capture VM
VMSN - it will content memory
VMSD- how many snapshot we have
Delta.vmdk - Date file
virtual machine. This includes disks, memory, and other devices, such as virtual network interface cards.
A newely created VMware Snapshot is comprised of following files:
<vm>-<number>.vmdk
<vm>-<number>-delta.vmdk
<vm>.vmsd
<vm>Snapshot<number>.vmsn
Step 1. Firstly, a request to create, remove, or revert a snapshot for a virtual machine is sent from the client to the server using the VMware API.
Step 2. The request is forwarded to the VMware ESX host that is currently hosting the virtual machine that has issue.
Step 3. If the snapshot includes the memory option, the ESX host writes the memory of the virtual machine to disk.
Step 4. If the snapshot includes the quiesce option, the ESX host requests the guest operating system to quiesce the disks via VMware Tools.
Step 5. The ESX host makes the appropriate changes to the virtual machine's snapshot database (.vmsd file) and the changes are reflected in the Snapshot Manager of the virtual
machine.
Step 6. The ESX host calls a function similar to the Virtual Disk API functions to make changes to the child disks (-delta.vmdk and .vmdk files) and the disk chain.
A snapshot consists of a set of files:
the memory state file (.vmsn),
the description file (-00000#.vmdk),
the delta file (-00000#-delta.vmdk).
The snapshot list file (.vmsd) keeps track of the virtual machines snapshots.
Delta disk: When you take a virtual machine snapshot, the state of the virtual disk at the time the snapshot is taken is preserved. When this occurs, the guest operating system
cannot write to its .vmdk file. Instead, changes are captured in an alternate file named VM_name-delta.vmdk.
Memory state file: VM_name-Snapshot#.vmsn, where # is the next number in the sequence, starting with 1. This file holds the memory state at the time the snapshot was taken. If
memory is captured, the size of this file is the size of the virtual machines maximum memory. If memory is not captured, the file is much smaller.
Disk descriptor file: VM_name-00000#.vmdk. This file is a small text file that contains information about the snapshot.
Snapshot delta file: VM_name-00000#-delta.vmdk. This file contains the changes to the virtual disks data at the time the snapshot was taken.
What is a VMWare SnapShot?
A snapshot is a point in time image of a virtual guest operating system (VM). That snapshot contains an image of the VMs disk, RAM, and devices at the time the snapshot was
taken. With the snapshot, you can return the VM to that point in time, whenever you choose. You can take snapshots of your VMs, no matter what guest OS you have and the
snapshot functionality can be used for features like performing image level backups of the VMs without ever shutting them down.
How Snapshot Works?
When a snapshot is created a number of files are created in the directory for that virtual machine.
VMnameX.vmsn (Where X is the number of the snapshot taken) This file stores the state of the virtual machine when the snapshot was taken.
VMnameX.vmem (Where X is the number of the snapshot taken) This file stores the state of the virtual machine memory when the snapshot was taken.
VMname.nnnnnn.vmdk (where nnnnnn is the number of the disk image, not corresponding to the snapshot number) These are log files which store changes to the virtual machine,
since snapshot was taken.
When a VM is reverted to specific date snapshot then ESX server will roll back the changes and brings the state of vm and data of snapshot date and time using .vmdk log files.
When snapshot is deleted it do not affect the current state of the virtual machine or any other snapshot. All data associated with the deleted snapshot is permanently committed
to the parent disk.
.lck- That indicate VM currently running
Snapshot Files
.VMDK file
.VMDK _ that is delta file (each snapshots create each delta file) it's read only file
.VMSN _ that is slat sanapshot file (each snapshots create each vmsn file)
Snapahot
How snapshot works
http://www.stratogen.net/blog/hidden-vmware-snapshots/
Snapshots include
VM-INT-PRINT Page 6
Snapshots include
Contents of VM Virtual disks /VM setting / The VM memory
Note: Capturing VM memory in a snapshot is optional because it consumes hard disk space in the datastores. If you don't capture memory in the snapshot, the VM will be powered
off when you ever to the snapshot
Best Practices for VM snapshots
Snapshots are not backups / snapshots are not complete copies of the orginal .vmdk file /snapshots can grow to the same size as the orginal base disk file
/ use no single snapshot for more than 24-72 hours /An excessive number of snapshots may cause decreased VM performance
/Configure automated vCenter server alarms to trigger when a virtual machine is running from snapshots /we can have up to 32 snapshot. Vmware suggest take max 3 snapshots
vMotion :-vMotion enables live migration of running virtual machines from one host to another with zero downtime
How VMotion works
VM pages copying (pre copy) source to destination. / Copying bitmpa image / Create bitmap file /Source pausing the I/O
Once copying is done Vmotional task deleted the source initialization Vm source update the RARP (Reverse ARP) request
Steps involved in VMWare vMotion ?
A request has been made that VM-1 should be migrated (or VMotioned) from ESX A to ESX B.
VM-1s memory is pre-copied from ESX A to ESX B while ongoing changes are written to a memory bitmap on ESX A.
VM-1 is quiesced on ESX A and VM-1s memory bitmap is copied to ESX B.
VM-1 is started on ESX B and all access to VM-1 is now directed to the copy running on ESX B.
The rest of VM-1s memory is copied from ESX A all the while memory is being read and written from VM-1 on ESX A when applications attempt to access that memory on VM-1 on
ESX B.
If the migration is successful, VM-1 is unregistered on ESX A.
Prerequisites
1. Vsphere Essentials plus, Standard, Enterprise or Enterprise Plus license
2. Host must be licensed for vMotion
3. Configure host with at least one vMotion n/w interface (vmkernel port group)
4. Shared storage (this has been compromised in 5.1)
5. Same VLAN and VLAN label
6. GigaBit Ethernet network required between hosts
7. Processor compatibility between hosts
8. vMotion does not support migration of applications clustered using Microsoft clustering service
9. No CD ROM attached
10. No affinity is enabled
11. VMware tools should be installed
VM-INT-PRINT Page 7
VCENTER SERVER
VCENTER SERVER
CENTER 5.1 UPGRADE STEPS
Vcenter (Including single sign-on Installtion / Update Manager / ESXi Hosts / VM Tools /
Virtual Machine Hardware / Datastores
1)Take the backup of database
2)Stop the Vcenter services and run the upgrade>vCenter Server
3)Update manager /Vsphere client /etc
4)Upgrade the ESXi
5)Upgrade Data storage (Upgrade VMFS)
6)Upgrade VMtools
7)Virtual Machine Hardware
8)License configuration
Vcenter installation pre-requirements
OS/Database /Part of domain /IP /License/Ports need to be opened 80/443- Web access 902/903/ ESX heartbeat/VM console 8080/8443 Web services 389 LDAP / 686 SSL
/636 -VC Linked Mde /60099-Web services /10443 VC Inventory service HTTPS / 10109-VC Inventory service management /10111-VC Inventory service linked mode
communications
Vcenter installation/Up gradation pre-request ion
/64 bit OS /64 bit CPU /4GB RAM/ .Net / AD authentication /DNS both lookup /Database/Run pre upgrade checker/ License
VC 5,5 installation process.
Configure Database,/ configured ODBC connection, /VC Single sign-on, /VSphere Web client, /VC Inventory services, / Vcenter Server,/ Vsphere client,
Vcenter Upgrade Steps
Take backup of Database / Vcenter upgrade 1st > Single sign on/ VC Inventory Services /VC server/Clinet/Web clinet/ Update Manager /Esxi Hosts/ VM Tools /VM Hardware
/Datastore
ESXi Upgrdation Steps
Update via booting from DVD /Update Manager>ESXi Image>Import ESXi Image> >Attach>Esxi> / >Scan>Upgrades / >Admin View> />Remediate>
VM-INT-PRINT Page 8
3:04 PM
ESXI COMMANDS
Ping/vmkping/tcpdump/nslookup
esxtop
service.sh restart
hostd /etc/init.d/hostd restart
vpxa /etc/init.d/vpxa restar
How will you turn start / stop a VM through command prompt?
"vim-cmd vmsvc/getallvms
vim-cmd vmsvc/power.getstat {vmID}
vim-cmd vmsvc/power.off {vmID}
vim-cmd vmsvc/power.off {vmID}"
Forecely stopping VM with esxcli
#esxcli vm process list - to get world id of vms
Esxcli<conn_options>vm process kill --type (soft/hard/force)
Esxcli vm process kill --world-id --type
Vmware -v to check version
Uname -a to check kernal version
Vm-support
VM-INT-PRINT Page 9
VM-INT-PRINT Page 10
ACTIVE DIRECTORY
Schema Master :Schema contains set of classes and attributes. eg User, computer, printer are the objects in AD which are having their own set of attributes.
Global Catalog :The global catalog contains a complete replication of all objects in Active Directory for its own domain, and contains a partial replication of all objects in other
domain in the forest.
Group Policy
Group Scope: Domain local , Global , Universal. Group type : Security , Distribution.
TRUST: To allow users in one domain to access resources in another
Trust Type Tree-root Trust/Shortcut Trust/External Trust/Realm Trust/Forest Trust
GROUP POLICY :GPO : Local Policy > Site GPO > Domain GPO > OU GPO > Child OU GPO
OVERRIDE POILICY: this prevents child contains from over riding polices set at higher level
BLOCK INHERTIANCE: stops containers inheriting polices from parent contains
LOOPBACK POLICY - It is apply direct to system, who login to the computer
SITE AND SERVICES
REPLICATION :replication happen base on USN number KCC-Inter site replication /STG-same site repl/
Repadmin/kcc site: sitename /repadmin /syncall /repadmin /bridgeheads
BRIDGEHEAD SERVER : The server which is responsible for communication or updating information between servers is called Bridgehead server.
What is the usage of sites & services?
Using sites & services we can create high availability connections between different sites and also we can have control on all sites in order to manage replication between
domains.
KCC Knowldge Consistency checker -Automatically makes connections between sites /Reconfigures the connection when links go down /Runs in the background and does not
need to be configured /Created both intrasite and intersite connections
What is Bridge Head Server?
BHS (Bridge Head Servers) is responsible for initiating replication between the sites. Inter-site replication can be done between BHS in one site and BHS in another site.
Explain Site & difference between inter-site and intra-site replication?
Site is one or more IP subnets connected by a high speed link .It contains connection objects and computer objects and mainly used for AD replication.
Intra-site replication can be done between the domain controllers in the same site. Inter-site replication can be done between two different sites over WAN links
Replication Intervals 5 min in same sites. Replication Intervals 3 Hours between different sites.
Create site
Subents> Create new subnet
Configuring Sites
>Create a site
>Create a Subnet
>Add a Domain Controller to the site
What is Bridge Head Server?
BHS (Bridge Head Servers) is responsible for initiating replication between the sites. Inter-site replication can be done between BHS in one site and BHS in another site.
repadmin /syncall initiates replication
repadmin /showreps displays replication partners
repadmin /kcc re-creates replication topology automatically
DNS
TYPES OF DNS: primary/secondary/AD integrated/forwarder caching only dns
STUBZONE: read only, like secondary, 1)copy of SOA record 2)NS name server record 3)Host record
What is DNS? DNS stands for Domain Name System. It resolves the IP addresses to host names and Host names to IP addresses.
How DNS Work? DNS contact local dns server, then it will contact Root hint dns server,
Local cache check (ipconfig /flushdns and ipconfig /registerdns) / Host file Check (C:\Windows\System32\drivers\etc\Host) / Preferred DNS server
What is round-robin rotation? Round robin is formula which is used to define replication partners.
DHCP
DHCP : BORA process (B broadcast O offer R request A acknowledgement
SUPER SCOPE : super scope combination of multiple scope/ when we give multi range ip from single server with the help of vlan switch,
What is scope & super scope?
In DHCP, scope is used to specify a range of IP Address which will be leased to the DHCP clients.
Super scope is the combination of multiple scopes.
CLUSTER
CLUSTER: Which is used to provide high availability for mission critical application
CLUSTER TYPE: Network load balancing (NLB) /Server Cluster: active-active /active-passive
NETWROK LOAD BALNCING CLUSTER: Divided amount of work between 2 or more computer. Ex web serice, FTP, IIS, Proxy, Terminal server.
QUORAM : A shared storage need to provide for all servers which keeps information about clustered application and session state and is useful in FAILOVER situation. This is
very important if Quorum disk fails entire cluster will fails
Different types of Quorum in Windows server 2008 ?
1.Node Majority - Used when Odd number of nodes are in cluster.
2.Node and Disk Majority - Even number of nodes(but not a multi-site cluster)
3.Node and File Share Majority - Even number of nodes, multi-site cluster
4.No Majority: Disk Only - Even number of nodes, no shared storage
What is Clustering. Briefly define & explain it?
Clustering is a technology, which is used to provide High Availability for mission critical applications. We can configure cluster by installing MCS (Microsoft cluster service)
component from Add remove programs, which can only available in Enterprise Edition and Data center edition.
In Windows we can configure two types of clusters
Network load balancing (NLB) cluster : for balancing load between servers. This cluster will not provide any high availability. Usually preferable at edge servers like web or
VM-INT-PRINT Page 12
Network load balancing (NLB) cluster : for balancing load between servers. This cluster will not provide any high availability. Usually preferable at edge servers like web or
proxy.
Server Cluster: This provides High availability by configuring active-active or active-passive cluster. In 2 node active-passive cluster one node will be active and one node will be
stand by. When active server fails the application will FAILOVER to stand by server automatically. When the original server backs we need to FAILBACK the application
Quorum: A shared storage need to provide for all servers which keeps information about clustered application and session state and is useful in FAILOVER situation. This is very
important if Quorum disk fails entire cluster will fails
Heartbeat: Heartbeat is a private connectivity between the servers in the cluster, which is used to identify the status of other servers in cluster.
Windows 2008 R2vCluster requirement
Cluster services. / 2 NIC 1) Production 2) Heartbeat /Cluster Name /IP /SAN DISK -Quorma
Disable the NetBIOS name for heartbeat network (WINS)disable NetBIOS over TCP/IP for both nodes
Install .net framework For installing service 1-disk -1 ip-serivice name
2) Configure quorum disk, check the disks both the node.
3) Install Cluster service both the node. (failover clustering)
4) Create cluster> add both node>Validate report
5) Give >cluster name> validate
6) Next go to another node>Manager cluster> give the cluster name
7) Disable the NetBIOS for heart bit network
8) Install .net framework
9) Install Application.
Cluster log generation
cmd>cluster log /g (C:\Windows\Cluster\Reports
2008 cluster features
Cluster validation /simplifies cluster setup /support GPT partion style /Support for multiple subnet / IPv6/
2008R2 Features in clustering
Validation enhancements / Migration wizard / powershell support /new role support /cluster shared volumes
VM-INT-PRINT Page 13
HARDWARE HP,DELL,IBM
Server enclousre
HP
ILO HP(Integrated Lights-Out)
HP Smart Start cd, 10.10 Ver latest
PSP- Proliant support pack (V.10.10)
HP (SIM) Systems Insight Manager (To
Manage the HP servers)
HP System Management Home Page,
HP Array configuration Utility
HP Server Models : ProLiant DL380 G4, HP
ProLiant DL360 G6 Server
Array controller battery
HP ProLiant BL blades /HP ProLiant DL /HP
ProLiant ML /HP ProLiant Scalable Systems
/HP ProLiant Micro Server
HP Integrity systems
HP Integrity Superdome servers
HP Integrity Server blades
HP Integrity Rack servers
HP Non Stop servers
HP Integrity Non Stop Blade System
HP Integrity Non Stop servers
HP Integrity BL Server Blades
HP ProLiant BL Server Blades
HP SIM
HP
HP Servers Model
Proliant DL380
ProLiant DL380 G4
ProLiant DL585 G2
ProLiant DL980 G7
ProLiant DL785 G6
ProLiant DL585 G7
ProLiant DL585 G6
ProLiant DL580 G7
ProLiant DL580 G5
ProLiant DL385p Gen8
ProLiant DL385 G7
ProLiant DL385 G6
ProLiant DL380 G7
DELL
DRAC (Dell Remote Access Card )
Dell Systems Build and Update
Utility to build the server
Dell Open Manage CD (OS CD)
Dell Open Manage IT Assistant (To
Manage the Dell servers)
Dell Openmanage Essentials
Dell Open Manage Server
Administrator
DELL SUU DVD VE7.4
Server Models: Power Edge
Dell OpenManage
Dell System E-Support Tool (DSET)
DELL
Tower Servers
PowerEdge R410
/420/510/515/520/610/620/710/7
15/720/720xd/R810/815/820/910/
Rack Server
Rack Servers -PowerEdge M-Series
Blade Servers
PowerEdge M420 /M520/M610
/M610x/M620/M820/M910/M915
DELL Servers Model
PowerEdge 1950
PowerEdge R710
Dell PowerEdge R900
PowerEdge T710
PowerEdge T620
PowerEdge T610
PowerEdge T605
PowerEdge R910
PowerEdge R905
PowerEdge R900
PowerEdge R805
PowerEdge R720
HP Report>Programs>Hp SystemTool>HP
INSIGHT DIAGNOSTICS ONLINE EDITION
FOR WINDOWS
Profile creation
Port group
VM-INT-PRINT Page 14
IBM
RSA (Remote Supervisor Adapter)
IBM Server Guide Setup and Installation CD v9.41
IBM System Director v6.3.3
IBM update express ver 9.51
IBM server Models- IBM System HS22
Model: System x3850 X5-[7143B6G] 40 CPUs X2.261 GHz
/Processor Type: Intel(R) CPU E7-4860 @2.27GHz
14 Blade each chassis can be installed
Blade server support only 4 NIC and Rack server support more
network card.
IBM SERVER MODELS
IBM System x3950 M2 4 Node
IBM System x3950 M2
IBM System x3950
IBM System x3850 X5
IBM System x3850 M2
IBM System x3800
dsa_portable Report
VM-INT-PRINT Page 15
VM-INT-PRINT Page 16
VM ISSUES
ESXI ISSUES
VIRTUAL MACHINE ISSUES
VCENTER ISSUES
NETWORKING ISSUES
STORAGE ISSUES
TEMPLATE/CLONE/SNAPSHOTS issue
HA ISSUES
DRS ISSUES
HOST PROFILE ISSUES
UPDATE MANAGER ISSUES
Update Manager is unable to scan ESX/ESXi hosts.
VMWARE CONVERTER ISSUES
ESXI ISSUES
VIRTUAL MACHINE ISSUES
VM PERFORMANCE ISSUE
Issue: My vm is not starting .Check is there any snapshots, > Consolidate >Kb1007969
Unable to extend the c drive via diskextend > stop the Index service
VM backups are failing due the Physical nic is down.
VM not able to restart - start via command line <vim-cmd
When I try to power on VM it is displaying error message Cant map memory for VM: Cannot allocate memory.
Due to insufficient Service console memory this error will be displayed, By increasing service console memory we can overcome this error.
VMWARE ISSUE
Issue: My vm is not starting
Check is there any snapshots, > Consolidate >Kb1007969
Symptoms
Investigating virtual machine file locks on ESXi/ESX (10051)
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=10051
A virtual machine cannot power on.
Powering on a virtual machine fails.
Unable to power on a virtual machine.
Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails with the error:
Failed to add disk scsi0:1. Failed to power on scsi0:1
When powering on the virtual machine, see these errors:
Unable to open Swap File
Unable to access a file since it is locked
Unable to access a file <filename> since it is locked
Unable to access Virtual machine configuration
In the /var/log/vmkernel log file, you see entries similar to:
WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free
WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>
When opening a console to the virtual machine, you may receive the error:
Error connecting to <path><virtual machine>.vmx because the VMX is not started
Powering on the virtual machine results in the power on task remaining at 95% indefinitely.
Cannot power on the virtual machine after deploying it from a template.
The virtual machine reports conflicting power states between vCenter Server and the ESXi/ESX host console.
Attempting to view or open the .vmx file using a text editor (for example, cat or vi), reports an error similar to:
cat: can't open '[name of vm].vmx': Invalid argument
Resolution
# vim-cmd vmsvc/getallvms
# esxcli vm process list
# esxcli vm process kill --type=soft --world-id=1268395
VCENTER ISSUES
VCENTER SERVER ISSUES ?
Symptoms
Top 20 vCenter Server 5.5 issues
http://blogs.vmware.com/kb/2014/02/top-20-vcenter-server-5-5-issues.html
Installation problems with vCenter Server (2045613)
VirtualCenter Server service when it does not start or fails on vCenter Server (1003926)
Resolution
Check the event id
In the %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs\vpxd.log file on vCenter Server
vCenter Server 4.x, the log files are stored in this directory by default:
VM-INT-PRINT Page 17
vCenter Server 4.x, the log files are stored in this directory by default:
%ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs
Windows 2008, the vpxd.log file is located at C:\ProgramData\VMware\VMware VirtualCenter\Logs.
Verify that the configuration of the ODBC Data Source Name (DSN) used for connection to the database for vCenter Server is correct. For more information, see vCenter
Server installation fails with ODBC and DSN errors (1003928).
Verify if there is enough free disk space on vCenter Server. For more information, see The VMware VirtualCenter Server service does not start due to insufficient disk space
(2083927).
Verify that ports 902, 80, 8080, 8433 and 443 are not being used by any other application.
Verify the health of the database server that is being used for vCenter Server. If the hard drives are out of space, the database transaction logs are full, or if the database is
heavily fragmented, vCenter Server may not start. For more information, see Investigating the health of a vCenter Server database (1003979).
Verify if the VMware VirtualCenter Server service is running with the proper credentials. For more information, see After installing vCenter Server, the VMware VirtualCenter
Server service fails to start (1004280).
Verify that critical folders exist on vCenter Server. For more information, see Missing folders on a vCenter Server prevent VirtualCenter Server service from starting
(1005882).
Verify that no hardware or software changes are made to vCenter Server that causes the issue. If you have recently made any changes to the vCenter Server, undo these
changes temporarily for testing purposes.
Before launching vCenter Server, ensure that the VMwareVCMSDS service is running.
Verify that the vpxd.exe file is present in C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe location. If this file is not present, reinstall vCenter Server.
Symptoms
Troubleshooting a failed vCenter Server installation (1003890)
vCenter Server installation fails to complete
Unable to complete a vCenter Server installation
Installing vCenter Server fails
You may see one or more of these errors during vCenter Server installation:
Invalid Virtual Infrastructure Web Service https port number or TCP/IP port in use
Error 25036.VMware VirtualCenter Server could not be installed.
Error 25060. Setup failed to execute sqlcmd.exe
This installation package is not supported by this processor type. Contact your product vendor.
re-configure your DSN to use one of the supported drivers
An error occurred, please try again in another vSphere session
Resolution
Verify that the minimum system requirements for vCenter Server
Verify the problem is not being caused by the installation media.
Verify the ODBC Data Source is configured correctly
Verify the health of the Database server that is to be used for VirtualCenter. If the hard drives are out of space, the database transaction logs are full, or if the database is
heavily fragmented VirtualCenter may complete the installation.
Verify that ports 902, 80, and 443 are not being used by any other application. If another application such as Microsoft Internet Information Server (IIS), is utilizing any of the
ports VirtualCenter may fail to install
Confirm that your virtual machine's anti-virus, anti-malware or IDS programs are not blocking or interfering with the install. Consult the manufacturer's documentation for
instructions on disabling.
NETWORKING ISSUES
NETWORKING ISSUE ?
Symptoms
Troubleshooting network connectivity issues for Windows virtual machines in VMware Workstation (2019836)
The virtual machine does not have network connectivity.
You cannot connect to the Internet from the guest operating system.
Your virtual machine does not have an IP address.
Bridged, Host-only, or NAT networking fails.
After upgrading from a previous version of VMware Workstation, there is no Internet connection.
You see a red X over the network connection icon in the system tray.
Your Ethernet controller drivers are not installed.
When you open Internet Explorer, you see the message:
Internet Explorer cannot display the webpage
When you hover your mouse over the network icon in the system tray, you see one of these messages:
Not connected
No connections are available
Resolution
Make sure that your Host machine has a working network connection.
Run an anti-virus scan on your virtual machine to make sure there are no viruses or other malware interfering with your Internet connection.
Ensure that the network adapter is enabled.
Shut down the virtual machine, then restart your Host Machine
Confirm that Workstation services are working properly.
Uninstall and reinstall VMware Tools.
Uninstall and reinstall all network adapters in the Device Manage
Reset TCP/IP and Winsock settings to default:
VM-INT-PRINT Page 18
Symptoms
Troubleshooting network performance issues in a vSphere environment (1004087)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004087
Troubleshooting virtual machine network connection issues (1003893)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003893
Virtual machines fail to connect to the network.
There is no network connectivity to or from a single virtual machine.
You cannot connect to the Internet.
A TCP/IP connection fails to and from a single virtual machine.
You may see one or more of the following errors:
Destination Host Unreachable
Network error: Connection Refused
Network cable is unplugged
Ping request could not find host (IP address/hostname). Please check the name and try again.
Unable to resolve target system name (IP address/hostname).
Resolution
If this virtual machine was converted from a physical system, verify that there are no hidden network adapters present.
Verify that the virtual machine's IPSec configuration is configured correctly and that it is not corrupted
STORAGE ISSUES
STORAGE ISSUE?
VicfgSymptoms
Troubleshooting storage issues when using VMware products (2013160)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2013160
Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions) (1008205)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008205
Symptoms
Troubleshooting fibre channel storage connectivity (1003680)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003680
Targets on the storage array are visible, but one or more LUNs are not visible
LUN not visible
LUN cannot connect
Connectivity issues to the storage array
LUN is missing
ESX/ESXi host initiators are not logging into the array
You see one of these errors:
Unknown inaccessible
SCSI: 4506: "Cannot find a path to device vmhba1:0:8 in a good state"
Resolution
Verify that none of the hosts can see any targets in a shared storage environment
Verify that a rescan does not restore visibility to all the targets or brings all the LUNs back
Verify the connectivity to the LUNs.
Verify that the fibre switch zoning configuration permits the ESX/ESXi host to see the storage array.
Verify that the fibre switch propagates RSCN messages to the ESX/ESXi hosts.
Verify that the storage array is listed in the VMware Hardware Compatibility Guide
Verify that the initiator is registered on the array, and that the storage array is configured correctly.
Verify the physical hardware:
The storage processors on the array.
The fibre switch and the Gigabit Interface Converter (GBIC) units in the switch.
The fibre cables between the fibre switch and the array.
The array itself.
Symptoms
Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions) (1008205)
esxtop and latency statistics that can be used when troubleshooting performance issues with SAN-connected storage (Fibre Channel or iSCSI).
The interactive esxtop utility can be used to provide I/O metrics over various devices attached to a VMware ESX host.
To monitor storage performance per HBA:
Start esxtop by typing esxtop at the command line.
Press d to switch to disk view (HBA mode).
To view the entire Device name, press SHIFT + L and enter 36 in Change the name field size.
Press f to modify the fields that are displayed.
Press b, c, d, e, h, and j to toggle the fields and press Enter.
Press s and then 2 to alter the update time to every 2 seconds and press Enter.
See Analyzing esxtop columns for a description of relevant columns. For more information, see Interpreting esxtop Statistics.
VM-INT-PRINT Page 19
VMOTIONS ISSUES
Symptoms
Diagnosing a vMotion failure at 10% or higher in vCenter Server (1003734)
Performing vMotion fails at 14% despite vmkping succeeding from source to target IP address (2042654)
Troubleshooting when a virtual machine loses network connection after vMotion (1003839)
VMware vMotion fails at 10%
vMotion fails with network errors (1030264)
vMotion times out
The VirtualCenter/vCenter Server reports these errors:
Migration will cause the virtual machine's configuration to be modified to preserve the CPU feature requirements for it's guest operating system.
Operation timed out
A general system error occurred:
Failed waiting for data. Error 16. Invalid argument
A general system error occurred: failed to look up VMotion destination resource pool object
Resolution
Ensure that vMotion is enabled on all ESX/ESXi hosts.
Verify that VMkernel network connectivity exists using vmkping.
Verify that VMkernel networking configuration is valid.
If Jumbo Frames are enabled (MTU of 9000) (9000 -8 bytes (ICMP header) -20 bytes (IP header) for a total of 8972), ensure that vmkping is run like vmkping -d -s 8972
<destinationIPaddress>. You may experience problems with the trunk between two physical switches that have been misconfigured to an MTU of 1500.
You can diagnose MTU- related issues by running the vmkping command:
# vmkping -I vmkX -d -s 8972 target.ip.address
Verify that Name Resolution is valid on the host.
Verify that Console OS network connectivity exists
Verify if the ESXi/ESX host can be reconnected or if reconnecting the ESX/ESXi host resolves the issue
Verify that the required disk space is available
This issue may be caused by SAN configuration. Specifically, this issue may occur if zoning is set up differently on different servers in the same cluster.
Check the ESX/ESXi host's routing table # esxcfg-route -l
Run the vmkping -I command to select the desired vmkernel interface to send ICMP traffic:
# vmkping -I vmkX x.x.x.x
Symptoms
Troubleshooting when a virtual machine loses network connection after vMotion (1003839)
The virtual machine loses its network connection.
There is no network connectivity to or from a single virtual machine.
A TCP/IP connection fails to and from a single virtual machine
Resolution
Ping another virtual machine on the same virtual switch
Ping the ESX Service Console
Ping the default gateway
Ping a target outside the network
Verify the physical switch setup
Verify that the correct version of VMware Tools is installed.
TEMPLATE/CLONE/SNAPSHOTS issue
CLONING VIRTUAL MACHINE ISSUE
Troubleshooting template deployment or cloning when it fails in vCenter Server (1004050)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004050
Symptoms
Deploying a template fails
Cannot deploy a virtual machine
Failure when cloning virtual machines
Failure to boot guest operating system after installing VMware Tools
Cannot clone a virtual machine
You see errors similar to:
Network copy failed for file.
[] /home/vmware/xxx/nvram
VM-INT-PRINT Page 20
When attempting to clone a virtual machine through vCenter Server, you see the error:
Failed to connect to host
Resolution
These steps eliminate common causes for the problem by verifying the sysprep files, verifying the virtual machine configuration, and verifying the the vCenter Server
configuration.
The correct version of sysprep is critical in deployments. Verify that the correct version of Microsoft sysprep has been installed to properly do the customization
Verify that virtual machines are installed with the latest version of VMware Tools.
Verify that the guest operating system is defined correctly. Incorrect definitions can cause deployment failures.
create a brand new template and then test the deployment.
Symptoms
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004002
Slow deployment of templates from within vCenter Server
Slow deployment of clone in vCenter Server
You are experiencing high CPU utilization on an ESX/ESXi host
You are experiencing high memory utilization on an ESX/ESXi host
Slow response when administering an ESX/ESXi host
Slow performance when copying files between shared VMFS storage (fibre-channel SAN) and local VMFS storage
Resolution
networking (Duplex Mismatch) and storage configuration of the ESX/ESXi.
create a brand new template and test the deployment
Checking your firmware and BIOS levels to ensure compatibility with ESX/ESXi (103725
SNAPSHOT ISSUE?
VMware snapshots backups are failing. - Check is there any backup> consolidated
Troubleshooting issues when creating or committing snapshots in VMware ESXi/ESX (1038963)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1038963
Symptoms
You cannot take a snapshot of the virtual machine.
You cannot create snapshots on the virtual machine.
You cannot commit the snapshot of the virtual machine.
You cannot delete snapshots off the virtual machine.
There are no snapshots visible in Snapshot Manager.
Resolution
VMware recommends having free space equal to the snapshots and base disk size before committing snapshots.
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1006847
If you do not have enough free space, migrate to another disk that has enough free space and
consolidate the snapshots into a new virtual disk file (VMDK). For more information on
consolidating disk files, see Consolidating snapshots (1007849).
To commit snapshots to a base disk from the command-line:
Find the path to the VMX file of the virtual machine either from the VMware
Infrastructure/vSphere Client or by running this command:
# vmware-cmd -l
/vmfs/volumes/volume-UUID-or-name/vm1/vm1.vmx
/vmfs/volumes/volume-UUID-or-name/vm2/vm2.vmx
Determine if the virtual machine has snapshots with this command:
# vmware-cmd /vmfs/volumes/volume-UUID-or-name/vm1/vm1.vmx hassnapshot
The output looks like:
hassnapshot() =
or
hassnapshot() = 1
If the result is not equal to one (1), there are no snapshots for the virtual machine and there is no reason to proceed further.
Remove (or commit) the snapshot by running this command:
# vmware-cmd /vmfs/volumes/volume-UUID-or-name/vm1/vm1.vmx removesnapshots
removesnapshots() = 1
If the result is one (1), the snapshots have been successfully committed. If the result is
something other than one (1),
Run this command to get a list of virtual machines and the VMID for each virtual machine:
# vim-cmd vmsvc/getallvms
To verify if the snapshot exists, run this command and check the Snapshot Name, Snapshot Created
On, and Snapshot State:
# vim-cmd vmsvc/snapshot.get [VMID]
Run this command to create a new snapshot:
# vim-cmd vmsvc/snapshot.create [VmId] [snapshotName] [snapshotDescription] [includeMemory]
[quiesced]
For example, to create a snapshot on the virtual machine named testvm:
# vim-cmd vmsvc/snapshot.create 3 snapshot1 snapshot 0 0
Run this command to remove all snapshots:
# vim-cmd vmsvc/snapshot.removeall [VMID]
VM-INT-PRINT Page 21
HA ISSUES
Symptoms
Unable to configure VMware High Availability (HA).
After host failure 2 VMS not restared and moved to other host
Configuring VMware HA fails at about 97% completion.
Configuring VMware HA fails between 85 to 91%.
Reconfiguring VMware HA fails.
Adding an ESX host to a cluster fails.
Enabling VMware HA in a cluster fails.
Host fails to remediate or exit Maintenance Mode.
These errors are generated when attempting to configure VMware HA
Host disconnects from the vCenter Server.
ESXi host enters a not responding state in the vCenter Server.
Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735)
Resolution
Check the connectivity Ping IP/DNS/FQDNS
Verify nslookup IP /nslookup ServerName
Verify the hostname with esxi commandline > hostname -s
domain name /etc/resolv.conf
/etc/sysconfig/network
/etc/vmeare/esx.conf
dns verify nslookup short_hostname
Verify the VMkername/IP portgroup name in all the esxi servers
VMotion VMkernel port is on the same vSwitch as the primary Service
Verify hosts file on the ESX host is located at /etc/hosts . IP/Server with fully qulified name
The VMware Virtual Center Server must also have an entry here 192.168.0.20 virtualcenter.domain.com virtualcenter
DRS ISSUES
DRS RELATED ISSUE ?
Symptoms
Applying DRS settings to an ESX or ESXi host generates an error (1004667)
Cannot apply DRS resource settings to an ESX host.
Attempting to apply DRS resource settings to an ESX host through vCenter Server may result in these errors:
Resolution
Verify the below
The hostd.log file contains entries similar to:
This is a known issue affecting vSphere 3.x, 4.x, and 5.x.
ESXi 5.5 Patch Release ESXi550-201501001
ESXi 5.1 Update 3.
To work around this issue:
Restart the management agents on the ESX host.
/etc/init.d/hostd restart
/etc/init.d/vpxa restart
Remove the floppy or CDROM devices
Verify the VMware tools
Remove the ESXi host from the DRS cluster, then re-add it to the cluster:
VM-INT-PRINT Page 22
Symptoms
Reason
Resolution
http://www.systemadminguide.in/search/label/Windows%20VMware%20Interview%20questions
Virtual Machine
VMs will be shown as inaccessible in the vCenter
http://www.systemadminguide.in/2013/12/vm-appears-as-inaccessible-in-vcenter.html
Issue:- With the vSphere Client, if you edit a VM's settings and then select one of its virtual disks, the option to resize the disk is greyed out. -When trying to extend the disk
using vmkftools for resizing, you will receive the below error:
Failed to extend the disk. Failed to lock the file. -When you extend the disk using vsphere client, the change is not getting reflected.
http://www.systemadminguide.in/2013/06/vm-disk-cannot-be-resized-failed-to.html
Symptom: The host and VMs in a vcenter server appears to be disconnected.
http://www.systemadminguide.in/2014/01/esxi-host-shows-disconnected-vmware.html
I just created a new virtual machine and attached to an existing disk. Every time I power on the VM, I get a blue screen. What could the problem be?
Make sure the OS type that you selected when you created the VM matches the OS type installed on the virtual disk. For example, if you selected Windows 2003 Standard
for the VM when you created it, but the existing virtual disk has Windows 2000 Standard installed, you'll probably encounter issues.
I'm having problems with my installation. What should I do?
Ensure that the hardware you're loading ESX Server on is supported. The same goes for the configuration. If you are certain the hardware and configuration are supported,
then run the vm-support script mentioned previously.
I followed the directions for Active Directory authentication, and I still can't log in using an account and password in AD. What should I do?
Check the time on your ESX Server and Active Directory and make sure they're synced up. Kerberos is very sensitive to being out of sync and could reject credentials if the
time is not within specific limits. You can also review the System event logs for clues.
Issue:Sometime we may find an iscsi target associated to an iscsi adapter being greyed out and marked as Dead or Error. In VMkernel log you may receive an error as given below
http://www.systemadminguide.in/2013/06/issue-sometime-we-may-find-iscsi-target.html
ESXi 5 Unresponsive VM How to Power Off using esxtop command
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165
Killing a VM using esxtop command on esxi
use the k command in esxtop to kill a running virtual machine process. SSH to the host and perform the following.
Step 1 Run esxtop by typing esxtop
Step 2 -Press c to switch to the CPU resource utilization screen (This is the default view)
Step 3 -Press Shift+f to display the list of fields
Step 4 -Press c to add the column for the Leader World ID
Step 5 -Identify the target virtual machine by its Name and Leader World ID (LWID)
Step 6 -Press k
Step 7 -At the World to kill prompt, type in the Leader World ID from step 5 and press Enter
Step 8 -Wait up to 30 seconds and validate that the process is no longer listed
Virtual machines appear as invalid or orphaned in vCenter Server
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003742
http://www.viktorious.nl/2013/06/10/repairing-orphaned-vms-after-an-esxi-host-got-permanently-lost/
Troubleshooting virtual machine performance issues
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008360
Symptoms
one of our VM is very slow due to CPU utilization( 70%).
We are running a several application service which is occupy 500kb (per min) and its like a messaging service. Currently we have allocated 2 vCPU and 6GB memory.
I have checked esxtop and found CPU utilization is high. Whether the allocate CPU and memory is fine or we need to increase the CPU and memory. Its a LINUX VM.
Resolution
1) confirm if VM or host prob, by vmotion to another host. Prob persist, VM prob.
2) if more than 1 tier of storage, need to storage vmotion to confirm if yr storage bottleneck
3) only Linux VM, can check top to see if CPU, or ram is heavily used by which process id, then u can adjust the bottleneck parameter accordingly
Symptoms
exchange having network latency, Packet loss is more but Microsoft recommendation is 0
Resolution
Check the below points
How many vms are hosted on that host and did you have network utilisation on host
What type of network card u r using - E1000
Did u also verified that what is the latency is been notice on storage due to that I have also found packet drop
No storage latency ..their saying its network packets
Microsoft suggest to increase buffer value in exchange side
VM-INT-PRINT Page 23
issue here a virtual machines gets booted remotely and has 2nics with two gateways on one nic the VM boots fine but when try to boot the same VM on the other nic
getting a blue screen error
Checked all hardware version all same
U need to click on VM and goto all vcenteractions >>> export system logs (System logs will give error message)
check h/w version
anybody has any command or script to find when a virtual machine was created
vmspot.com
The vcheck script will give you vm creation date and a lot more
http://www.vmspot.com/a-very-simple-powercli-script-to-gather-vm-creation-dates/
Symptoms VMWARE vcenter inventory services unable to Start.
vcenter level search option not working
getting error: '1053- VMware management web services are running
Resolution start - run _ type services.msc predd enter
reinstall inventory service
need to restore the inventory database from the backup if you have as it looks like a known old bug of esxi 5.0
VM-INT-PRINT Page 24