HPE Synergy
1768294 Members
2475 Online
108966 Solutions
New Discussion

Re: Same VLAN id on different UplinkSets

 
SOLVED
Go to solution
adel_g
Visitor

Same VLAN id on different UplinkSets

Hi,

Can we have same vlan id on different UplinkSet? We got an error while trying to add same vlan id to different uplink sets and would like to know if it's becasue some error on our configuration or a SYNERGY limitation.

We have same vlan id on different UplinkSet on C7000 without any problem. It help us to migrate ToR switches whithout downtime. It seems it's not possible to do so on SYNERGY and that's a limitation for me.

This is the scenario:

- 2 SYNERGY enclosures on the same LE and EG. 

- 2 Composer firmware: 6.10.0.0-0437859

- 2 Virtual Connect SE 100Gb, one on each enclosure. Both VCs are on the same LI & LIG. Virtual Connect SE 100Gb F32 Module firmware: 2.2.1.1002

- 2 UplinkSets created under the LI and LIG.

Thanks

Adel

 

3 REPLIES 3
msobers22
Trusted Contributor
Solution

Re: Same VLAN id on different UplinkSets

Hello,

You have one Ethernet LIG correct? You cannot have the same VLAN in two uplink sets in the same LIG. The only way to do this would be to create separate LIGs for each VC 100 F32 module. You would have to select "non-redundant (A-side only) and for one LIG and non-redundant (B-side only) for the second one. 

This configuration simulates how it was on c7000. 

I hope that makes sense.

 

 

adel_g
Visitor

Re: Same VLAN id on different UplinkSets

Hello,

msobers22, thank you for your quick response !!!!

Yes, we have one Ethernet LIG. The two VC 100 F32 modules are linked to the current ethernet LIG. 

Can we do wthat you suggest without downtime?

Is your topology still redundant? If one C 100 F32 module fail or the uplink connected to it fail then all traffic will switch to the other side?

Thanks

Adel

msobers22
Trusted Contributor

Re: Same VLAN id on different UplinkSets

Hello,

Please refer to the HPE Virtual Connect traffic flow with HPE Synergy Technical White paper. The configuration I described is called Classic Active-Active. Here is the link to the pdf. https://www.hpe.com/psnow/doc/a00042387enw 

Downtime will be required to implement the changes. 

The best practice is the Muti-module link aggregation (MLAG) configuration. It provides various levels of fault tolerance and load distribution for the Ethernet traffic.  

Regards