VMware Interview Question No.5

 

Below mentioned Out of 4 Scenarios, which all scenarios depicts correct IO path in vSphere Networking.

Scenario-1: 

  • 2VMs connected to 2 different portgroups of same vSwitch. 
  • Each Portgroup of vSwitch mapped to dedicated uplink as shown in diagram.

VMwithTwoDifferentPortgroupAndSamevSwitch

IO Path:

Packet from VM1 -> PG-0 -> vSwitch0 -> vmnic0 ( uplink0) -> Physical Switch Port-0 -> Physical Switch Port-1 -> vmnic1 ( uplink1) -> PG-1 -> VM2.

Scenario-2: 

  • 2VMs connected to 2 different portgroups of 2-different vSwitch. 
  • Both vSwitch mapped to single uplink as shown in diagram.

scenario2

IO Path:

Packet from VM1 -> PG-0 -> vSwitch0 -> vmnic0 ( uplink0) -> Physical Switch  -> vmnic0 ( uplink0) -> vSwitch-1 -> PG-1 -> VM2.


Scenario-3: 

  • 2VMs connected to 2 different portgroups of same vSwitch. 
  • There is no uplink connected to vSwitch0.

scenario3

IO Path:

Packet from VM1 -> PG-0 -> vSwitch0  -> PG-1 -> VM2.

 

Scenario-4: 

  • 2VMs connected to 2 different portgroups of same vSwitch. 
  • Both vSwitches are connected to each other and there is no uplink connected to vSwitches.

scenario4

IO Path:

Packet from VM1 -> PG-0 -> vSwitch0  -> vSwitch-1 -> PG-1 -> VM2.

Options are mentioned below:

  1. Scenario-1 and Scenario-3
  2. Scenario-2 and Scenario-4
  3. Scenario-3 and Scenario-4
  4. None of the above

ANSWER : NONE OF THE ABOVE

Scenario-1:

Reason:
VMs traffic will never go on uplink hence IO path mentioned in the scenario-1 is not correct.

Explanation:
If VMs are connected to same vSwitch even though mapped with two different portgroups. VM traffic will never go on uplink until specific policy is configured on portgroup like VLAN.

Since there is no policy configuration mentioned in our question so I/O path mentioned in scenario-1 will not be correct answer.

Scenario-2:

Reason:
Same Uplink can’t be assigned to two vSwitches hence I/O path mentioned in the scenario-2 is also not correct.

Explanation:
Network configuration mentioned in this scenario depicts wrong configuration or unsupported configuration.

If 1-uplink is mapped to Switch-1 then same uplink can’t be claimed by another switch without impacting previous switch-1 networking which is not recommended.
Hence I/O path mentioned in scenario-2 will also not be correct answer.

Scenario-3:

Reason:
VMs traffic will never leave esxi host or vswitch hence no uplink would be required for packet forwarding between vm1<->vm2.

Explanation:
If VMs are connected to two different portgroups of same vSwitch. VM packet will not leave ESXi host or vSwitch until specific policy is configured on Portgroup like VLAN.
In scenario-3, there is no policy configured on portgroup so VMs packet will not leave vSwitch or ESXi host.
Since there will be no traffic goes on Uplink hence I/O path describe in this scenario is CORRECT one.
Scenario-4:

Reason:
Cascading of vSwitches is NOT ALLOWED in VMware vSphere Networking.

Explanation:

VMware doesn’t allow interconnecting or cascading two virtual switches unlike physical world. Since it’s unsupported or invalid configuration hence I/O paths mentioned in this scenario is also Incorrect.

Please feel free to drop your queries and i’ll be happy to answer them

govmlab on sabtwittergovmlab on sablinkedingovmlab on sabgooglegovmlab on sabfacebookgovmlab on sabemail
I am VMware Solution Architect with 10+ Years of enriching experience in Datacenter Virtualization Technologies, Storage Area Networks and Software Defined Datacenter, Networking and Storage.
I hold Numerous certification including RHCE, CCNA, VCP4.0, VCP5.1, VCP5.5, vCloud and EMC certification.
While spending countless hours exploring the product inside and out and learning everything about it, Eventually I discovered my passion for teaching and helping others learn from my knowledge and experience so turned to Trainer cum Blogger to educate every single person keen to learn Virtualization.

Leave a Reply