• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Vmware interview points
 

Vmware interview points

on

  • 1,826 views

 

Statistics

Views

Total Views
1,826
Views on SlideShare
1,826
Embed Views
0

Actions

Likes
0
Downloads
255
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Vmware interview points Vmware interview points Document Transcript

    • P2V Checklist :1. Decide on the clone method (Hot or Cold).Note: If the source machine is a domain controller, database server, email server,or anyother service with frequently changing data, a cold conversion must be performed.Tip: For a domain controller the best way is to create a new virtual machine and promote itto a DC then decommission the old DC.2. Does the physical machine use serial ports?If yes, it is still possible to P2V, however that VM will need to be resticted to an individualESX server with the physical serial device attached.3. Does the physical machine use parallel ports?If yes, it is still possible to P2V, however that VM will need to be resticted to an individualESX server with the physical parallel device attached.4. Does the physical machine use and USB devices?If yes, you will need to look into using USBanywhere, which allows to use USB over thenetwork.5. Check there is enough storage space for the new VM. Take into account thecurrent data size plus growth.Note: Disks can be resized upon conversion so if there is a large quantity of unused spaceon the physical this can be removed to save space.6. Check there is enough RAM available in the virtual environment to accomodatethe new VMs needs.7. Check there is enough CPU available in the virtual environment to accomodatethe new VMs needs.Note: Physical machines with multiple CPUs but only using single threaded applicationsshould be set to 1vCPU. Adding extra CPUs would waste CPU time / cycles because theapplications would not make use of it.8. Check the network the physical machine is connected to, is available in thevirtual environment.9. Monitor the physical machine for the following utilization metrics:Difference between HA and Vmotion?  VMotion and HA are different features.+15133740425
    • Step By Step :1. Verify that the system you want to P2V is running a Windows OS. If it isnt, you wontbe able to use the P2V assistant.2. Create a virtual disk, or disks, with enough space to house the data on the machine youwant to P2V and attach it/them to the helper VM.3. Boot the system that you plan to P2V to the P2V boot disk and assign the appropriatenetwork settings--IP address, netmask, gateway, and name server.4. Open the P2V Assistant on the helper VM and choose to clone a source computersphysical disk, and click Next.5. Type in the IP address you assigned to the machine to be cloned and hit Next.6. Choose the disk that you want to configure and click Next. Note that you can only cloneone disk at a time, so if you have multiple disks, youll need to re-run this process for eachof them.7. Choose whether you want to reconfigure the disk now or later and click Next. Might aswell have the P2V assistant reconfigure it.8. Choose to copy the disk to a physical disk on the system. Choose to copy it to thevirtual disk that you added to the system in step 2 and click Next.9. If you want to change partitions around, this screen is the easiest place to do so. If not,leave everything the way it is and click Next.10. The final step is to choose which VMware product you plan to run the virtualized systemon. Make the appropriate choice, click Next, and then Finish.11. Once the disk has been copied, shutdown the helper VM, remove the disk that youadded in step 2, attack that disk to a new VM, and start that VM up.
    • Installing ESXi 4.1 with Boot from SAN :1. Document network/port mappings in vSphere Client on existing ESX server2. Put host into maintenance mode3. Shutdown host4. Remove host from Storage Group in EMC Navisphere5. Create dedicated Storage Group per host for the boot LUN in Navisphere6. Create the 5GB boot LUN for the host7. Add the boot LUN to the host’s Storage Group8. Connect to the host console via the Dell Remote Access Card (DRAC)9. Attach ESXi media via DRAC virtual media10. Power on host (physically or via the DRAC)11. Press CTRL+Q to enter Qlogic FastUtil12. Select Configuration Settings13. Select Adapter Settings14. Change “HBA BIOS” to Enabled [ESC]15. Select “Selectable Boot”16. Change to “Enabled”17. Change primary from zeroes to the disk with the address of the owning SP 1. Compare the address with the EMC Storage Processor (SP) Front-End Port addresses in Navisphere 2. If the disk shows as “LUNZ”, do not enable Selectable Boot or configure a disk (skip to 21) Escape and Save settings, but don’t leave the utility At the main menu, select “Select Host Adapter” Change to the next adapter Repeat steps 12 through 20 Exit the utility, reboot, and press F2 to enter Setup Change Boot Hard Disk Sequence to put the SAN disk first Exit BIOS and reboot Press F11 for boot menu Select Virtual CD In Setup on the “Select a Disk” screen, select the remote 5GB LUN Press F11 to begin install Press Enter to reboot the host After setup completes, configure password, time, and network Add host to vCenter and configure networking (per step 1) Add LUNs to the host’s Storage Group in Navisphere Rescan for storage on host in vCenter
    • vMware Issues in production :1.HA issue because of DNS, the hosts are unable to communicate together. After adding all server IPs ineach server /etc/hosts file.2.VM was not powered on, when the swap file was locked by another host, It powered on afterreleasing the lock.Resource pool : o Esxi resource pool is a pool of CPU and memory resources. o resources are allocated based on the CPU and memory shares that are defined.Promiscuous mode : o If we enable the mode in a switch, It gives the switch visibility to all vms.Traffic shaping :We can control the vSwitch traffic. o average bandwidth - estabilish the number of bits. o burst bandwidth - estabilish the number of bytes. o peak bandwidth.vMware vshield Zone : o It gives the network access protection between running VMs in the virtual datacenter.VCB :VCB is a backup framework, which enables third party backup tools to take backups. o Centralized backups of esxi virtual servers o It provides file level backups of Esxi servers,both full and incremental. o Provides image level backups and utilizes vmware snap shots. o It provides LAN-free backup,because the VCB server connected to SAN through FC.Port Groups : The port group segregates the type of communication. o Virtual machine port group - used for VM network. o VMkernal portgroup includes NFS or iSCSI,vMotion. o Service console poertgroup - only for ESX.
    • NIC Teaming : o It is used to distribute the network traffic between the adapters. o Reroute the traffic in the event of adapter failure and load balancing.Virtual Machine Port group : o It allow VMs to connect to the physical machine. o This group enables communication between vSwitch and physical switch.VC Core services : o VM provisioning o Task scheduling o Event loggingWhat are the devices that can be added while the virtual Machine running o VI 3.5 - HD and NICs. o vShepere 4.0 - Memory and processor along with HD and NICs.Snap Shot : o Its the running state image of the virtual machine with file system and memory state.Considerations when we initiate a snapshot : o VM Configuration file. o VM Hard Disk. o VM Memory.Command for restart host : o service mgmt-vmware restartHigh availability (HA) : o HA gives high availability to valued application and VMs. o It will restart the VMs with minimum downtime. o HA is not dependent on VC or vMotion.CPU Ready :CPU Ready shows how long a virtual machine is waiting to be scheduled on a physical processor. Avirtual machine waiting many thousands of milliseconds to be scheduled on a processor might indicate
    • that the ESX/ESXi host is overloaded, a resource pool has too tight a limit, or the virtual machine has toofew CPU shares