19 October, 2020
Ans: 1. Virtual Machine Port Group - Used for Virtual Machine Network 2. Service Console Port Group - Used for Service Console Communications 3. VMKernel Port Group - Used for VMotion, iSCSI, NFS Communications
Ans: The port group segregates the type of communication.
Ans: Even though the license box is selected, it shows as "License Not Used" until you enable the VMotion option for specific vSwitch
Interested in mastering VMware Training? Enroll now for a FREE demo on "VMware Training"
Ans: A VLAN is a logical configuration on the switch port to segment the IP Traffic. For this to happen, the port must be trunked with the correct VLAN ID.
Ans: Yes, The vSwitches support VLAN Tagging, otherwise if the virtual machines in an esx host are connected to different VLANS, we need to install a separate physical nic (vSwitch) for every VLAN. That is the reason VMware included the VLAN tagging for vSwitches. So every vSwitch supports up to 1016 ports, and BTW they can support 1016 VLANS if needed, but an ESX server doesn’t support that many VM’s. :)
Ans: If the promiscuous mode set to Accept, all the communication is visible to all the virtual machines, in other words, all the packets are sent to all the ports on vSwitch If the promiscuous mode set to Reject, the packets are sent to the intended port so that the intended virtual machine was able to see the communication.
Ans: When we create a virtual machine the configuration wizard generates a MAC address for that machine, you can see it in the .vmx (VM Config) file. If it doesn't matches with the MAC address in the OS this setting does not allow incoming traffic to the VM. So by setting the Reject Option, both MAC addresses will remain the same, and the incoming traffic will be allowed to the VM.
Ans: When we create a virtual machine the configuration wizard generates a MAC address for that machine, you can see it in the .vmx (VM Config) file. If it doesn't matches with the MAC address in the OS this setting does not allow outgoing traffic from the VM. So by setting Reject Option, both MAC addresses will remain the same, and the outgoing traffic will be allowed from the VM.
Ans: VM provisioning, Task Scheduling, and Event Logging
Ans: Yes we can do vMotion between two datacenters, but the mandatory requirement is the VM should be powered off.
Ans: VC agent is an agent installed on the ESX server which enables the communication between VC and ESX server. The daemon associated with it is called VMware-hosted, and the service which corresponds to it is called as mgmt-VMWare, in the event of VC agent failure just restart the service by typing the following command at the service console
" service mgmt-VMware restart " VC agent installed on the ESX server when we add it to the VC, so at the time of installation if you are getting an error like " VC Agent service failed to install ", check the /Opt size whether it is sufficient or not.
Ans: Click Edit Menu on VC and Select Client Settings to change VI settings Click Administration Menu on VC and Select VC Management Server Configuration to Change VC Settings
Ans: .vmx - Virtual Machine Configuration File .nvram - Virtual Machine BIOS .vmdk - Virtual Machine Disk file .vswp - Virtual Machine Swap File .vmsd - Virtual MAchine Snapshot Database .vmsn - Virtual Machine Snapshot file .vmss - Virtual Machine Suspended State file .vmware.log - Current Log File .vmware-#.log - Old Log file
Ans: In VI 3.5 we can add Hard Disk and NIC's while the machine running.
Ans: Right, Click on VM, select edit settings, choose the options tab, and select boot option, set the delay how much you want.
Ans: We can convert a VM into Template, and it cannot be powered on once it changed to the template. This is used to quick provisioning of VM's.
Ans: copy the Sysprep files to the Virtual center directory on the server, so that the wizard will take the advantage of it.
Ans: VC itself includes the customization tools, as these operating systems are available as open-source.
Ans: Yes.. it can, if the template in one data center, we can deploy the VM from that template in another datacenter without any problem.
Ans: If you configure the VM with Mapped LUN's, then the snapshot failed. If it is mapped as virtual then we can take a snapshot of it. If you configure the VM with Mapped LUN's as physical, you need to remove it to take a snapshot.
Ans: Virtual Machine Configuration (What hardware is attached to it) State of the Virtual Machine Hard Disk file ( To revert back if needed) State of the Virtual Machine Memory (if it is powered on)
Ans: An agent needs to be installed on the Physical machine VI client needs to be installed with Converter Plug-in A server to import/export virtual machines
Ans: It is a backup framework, that supports 3rd party utilities to take backups of ESX servers and Virtual Machines. It's not a backup service.