Forum Discussion
NimbostratusRSTP - Viprion
Hi Guys,
Im looking to deploy a viprio chassis with three VCMP having its independent redudant link to two seperate switches and im having difficulties in handling the spanning tree configuration
We have c2400 chassis with three VCMP in three different network Tier. DMZ Tier, Agg Tier and Server Tier are the different layers in our network and each layer has its own spanning tree instance(each layer has its own root bridge).
I have the following questions
- Can the chassis have three seperate spanning tree instance independent to its VCMP so that the failover of restricted only to its layer
- As VCMP has its Vlans assigned, how can we control which interfaces are associated with its VCMP
- how can i make a set of interfaces to be part of separate spanning instance
- Even if the chassis is set to Passthrough mode, how does it identify the interfaces to pass its specific BPDU or does all BPDU goes through all interfaces and the switching environment controls it ?
- Does tagged and untagged vlans play any role to differentiate the VCMP Interface ?
Please provide any suggestion and methods to implement this.
7 Replies
Sriram_Kannan_1Im also doing initial testing of connected a 1600 to a switch with two uplinks. f5 is setup to passthrough and switch is running RSTP as root bridge.
Should one of the uplink be blocked as the BPDU pass through the f5 ?
Brad_ParkerCirrus
Are you able to do distributed trunking with your switches(dt-LACP/cross-stack etherchannel)? It at all possible I would consider creating distributed trunks rather than fussing with STP. We actually have each blade plugged into two different switches with one big distributed LACP trunk on the Viprion tagged with our VLANS.
- Sriram_Kannan_1Hi Brad We currently have each VCMP connected to separate switch using Trunk. As we have three layers with its own spanning instance how would this overcome it ?
- Brad_ParkerWhen you use distributed trunking, spanning tree doesn't come into play and doesn't need to be configured. The device(the virpion) which is connected to two different switches, sees it as one LACP trunk. The the switches, once configured for the distributed trunking, don't need to block any ports in the trunk. All ports can be utilized.
Brad_Parker_139Nacreous
Are you able to do distributed trunking with your switches(dt-LACP/cross-stack etherchannel)? It at all possible I would consider creating distributed trunks rather than fussing with STP. We actually have each blade plugged into two different switches with one big distributed LACP trunk on the Viprion tagged with our VLANS.
- Sriram_Kannan_1Hi Brad We currently have each VCMP connected to separate switch using Trunk. As we have three layers with its own spanning instance how would this overcome it ?
- Brad_Parker_139When you use distributed trunking, spanning tree doesn't come into play and doesn't need to be configured. The device(the virpion) which is connected to two different switches, sees it as one LACP trunk. The the switches, once configured for the distributed trunking, don't need to block any ports in the trunk. All ports can be utilized.
