Vsphere spanning-tree issue?

Answered Question
Feb 8th, 2010

Hi,

Our vmware team came to me with a question, they want to hook up a vmware vsphere machine to the network as described in the attached pdf file.

The 2 etherchannels between the 2 6500's are already in place.

Our 2 cisco 6500 switches are not VSS capable and we don't  have Cisco virtual switches, just the standard vswitches in vmware.

When i saw it i could only think about a spanning-tree loop.

So my 2 questions are:

1) Is this possible or will i create a loop with this design which will cause the 2 6500's to recalculate spanning tree for the 4 vlans in question and block a specific port for that vlan? or will the bpdu' s not be sent?

2) What is the recommended design for redundancy without VSS or Cisco's virtual switches?

Thanks

Attachment: 
I have this problem too.
0 votes
Correct Answer by dominic.caron about 6 years 10 months ago

Hi,

The Vswitch included with Vmware will not cause a loop. If you receive a frame from the uplink, only two thing can occur, it will be forwarded to one of the VM or it will be dropped. The only way you can cause a loop is if you bridge 2 virtual interface inside a virtual server.

You usualy configure portfast on the interface connecting to the ESX server. This will identify the port as an edge port to 802.1w. Lease spanning-tree in place just in case a virtual server is misconfigured.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
dominic.caron Mon, 02/08/2010 - 11:28

Hi,

The Vswitch included with Vmware will not cause a loop. If you receive a frame from the uplink, only two thing can occur, it will be forwarded to one of the VM or it will be dropped. The only way you can cause a loop is if you bridge 2 virtual interface inside a virtual server.

You usualy configure portfast on the interface connecting to the ESX server. This will identify the port as an edge port to 802.1w. Lease spanning-tree in place just in case a virtual server is misconfigured.

Actions

This Discussion

Related Content