Explore topic-wise InterviewSolutions in .

• Link Status only
• Beacon Probing

Link Status only – Relies solely on the link status provided by the network adapter. This detects failures, such as cable pulls and physical switch power failures, but it cannot detect CONFIGURATION errors, such as a physical switch port being blocked by spanning tree or misconfigured to the wrong VLAN or cable pulls on the other SIDE of a physical switch.

Beacon Probing – Sends out and listens for beacon probes — Ethernet broadcast frames sent by physical adapters to detect upstream network connection failures — on all physical Ethernet adapters in the team. In addition to link status, to determine link FAILURE. This detects many of the failures which are not detected by Link Status.

Link Status only – Relies solely on the link status provided by the network adapter. This detects failures, such as cable pulls and physical switch power failures, but it cannot detect configuration errors, such as a physical switch port being blocked by spanning tree or misconfigured to the wrong VLAN or cable pulls on the other side of a physical switch.

Beacon Probing – Sends out and listens for beacon probes — Ethernet broadcast frames sent by physical adapters to detect upstream network connection failures — on all physical Ethernet adapters in the team. In addition to link status, to determine link failure. This detects many of the failures which are not detected by Link Status.

• PROMISCUOUS MODE – REJECT
• MAC Address changes – Accept
• FORGED Transmits – Accept

There are 3 types of VLAN tagging available in VSPHERE:

1. Virtual SWITCH Tagging (VST)
2. External Switch Tagging (EST)
3. Virtual Guest Tagging (VGT)

There are 3 types of VLAN tagging available in Vsphere:

A VLAN is the VIRTUAL LAN which is used to broke down the Broadcast traffic into many logical groups. Basically, one PHYSICAL switch comprise of one broadcast DOMAIN. VLAN used to separate the one broadcast domain into many SMALL pieces to separate the networks within the broadcast domain.

A VLAN is the VIRTUAL LAN which is used to broke down the Broadcast traffic into many logical groups. Basically, one physical switch comprise of one broadcast domain. VLAN used to separate the one broadcast domain into many small pieces to separate the networks within the broadcast domain.

Which is same as the Mac Address changes SETTING but it WORKED for the OUTGOING TRAFFIC but the MAC address changes setting is for incoming traffic.

Which is same as the Mac Address changes setting but it worked for the outgoing traffic but the MAC address changes setting is for incoming traffic.

• Route based on the originating virtual SWITCH port ID
• Route based on source MAC HASH
• Route based on IP hash
• Route based on the originating virtual switch port ID – Chooses an uplink based on the virtual port where the traffic entered the virtual switch. The traffic will be always send with that same uplink until that PARTICULAR uplink is failed and failed over to another NIC.
• Route based on source MAC hash – Choose an uplink based on a hash of the source Ethernet MAC address.The traffic will be always send with that same uplink until that particular uplink is failed and failed over to another NIC.
• Route based on IP hash – Choose an uplink based on a hash of the source and destination IP ADDRESSES of each PACKET.

Traffic shaping POLICIES are disabled by default.

There are 3 DIFFERENT traffic shaping policy setting:

• Average Bandwidth
• Peak Bandwidth
• Burst Size

Traffic shaping policies are disabled by default.

There are 3 different traffic shaping policy setting:

All the virtual machines NICS are provide with the MAC address at the time of creation and it is stored in .VMX file. If the packet doesn’t MATCH with the MAC address as same as in the .VMX file , it does not allow incoming traffic to the VM by setting this OPTION as reject.

If it is set as Accept,ESX accepts requests to CHANGE the effective MAC address to other than the MAC address save din the .VMX file.

All the virtual machines nics are provide with the MAC address at the time of creation and it is stored in .VMX file. If the packet doesn’t match with the MAC address as same as in the .VMX file , it does not allow incoming traffic to the VM by setting this option as reject.

If it is set as Accept,ESX accepts requests to change the effective MAC address to other than the MAC address save din the .VMX file.

/ -root
Swap
/var
/Var/core
/opt
/home
/tmp

/ -root
Swap
/var
/Var/core
/opt
/home
/tmp

When the TIME of Virtual switch created, VSWITCH is created with 56 PORTS by default. We can extend the no of ports by editing the vswitch PROPERTIES.

When the time of Virtual switch created, Vswitch is created with 56 ports by default. We can extend the no of ports by editing the vswitch properties.

All the Virtual Machines which are CONFIGURED in VM PORT Group are able to connect to the other machines on the network. So this port group ENABLES communication between vSwitch and Physical Switch by the use of uplink (Physical NIC) associated with the port group.

All the Virtual Machines which are configured in VM Port Group are able to connect to the other machines on the network. So this port group enables communication between vSwitch and Physical Switch by the use of uplink (Physical NIC) associated with the port group.

VIRTUAL Machine PORT group is USED by Virtual machine communication.

Virtual Machine port group is used by Virtual machine communication.

Vmkernel PORT is used by ESX/ESXi for vmotion, ISCSI & NFS communications. ESXi uses Vmkernel as the MANAGEMENT network since it don’t have service CONSOLE built with it.

Vmkernel port is used by ESX/ESXi for vmotion, ISCSI & NFS communications. ESXi uses Vmkernel as the management network since it don’t have service console built with it.

SERVICE console PORT group required to manage the ESX server and it ACTS as the management network for the ESX. vCenter/vSphere CLIENT uses the service console IP’s to communicate with the ESX server. 

Service console port group required to manage the ESX server and it acts as the management network for the ESX. vCenter/vSphere Client uses the service console IP’s to communicate with the ESX server. 

VMWare KERNEL is a Proprietary kernel of vmware and is not BASED on any of the flavors of Linux operating systems, .VMkernel requires an operating system to boot and MANAGE the kernel. A SERVICE console is being provided when VMWare kernel is booted. Only service console is based up on Redhat Linux OS not VMkernel.

VMWare Kernel is a Proprietary kernel of vmware and is not based on any of the flavors of Linux operating systems, .VMkernel requires an operating system to boot and manage the kernel. A service console is being provided when VMWare kernel is booted. Only service console is based up on Redhat Linux OS not VMkernel.

There are 3 TYPES of port groups in ESX:

1. Service CONSOLE port group
2. VMkernel Port group
3. VIRTUAL machine port group

There are only 2 types of port group in ESXi:

1. Vmkernel Port group
2. Virtual Machine Port group

There are 3 types of port groups in ESX:

There are only 2 types of port group in ESXi:

• SERVICE SSHD RESTART
• Service ntpd restart
• Service vmware–webaccess restart

VC agent is an agent INSTALLED on ESX SERVER which enables communication between VC and ESX server. This Agent will be installed on ESX/ESXi will be done when you try to add the ESx host in VCENTER.

VC agent is an agent installed on ESX server which enables communication between VC and ESX server. This Agent will be installed on ESX/ESXi will be done when you try to add the ESx host in Vcenter.

• service mgmt–vmware restart (restarts HOST agent(vmware–hostd) on vmware ESX SERVER)
• service vmware-vpxa restrat (restarts VCENTER agent service)
• service network restart (restarts management networks on ESX)

The SERVICE console is DEVELOPED BASED up on Redhat Linux Operating system, it is USED to manage the VMKernel.

The service console is developed based up on Redhat Linux Operating system, it is used to manage the VMKernel.