HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Any impacts from having different LAG GroupID between VC modules !!!

 
chuckk281
Trusted Contributor

Any impacts from having different LAG GroupID between VC modules !!!

Charles had a Link Aggregation Group (LAG) ID question:

 

*****************

 

I was just wondering if there where any bad consequences from

having different LAG GroupID between VC modules !!!

 

VC Bay1 = ports X1 & X2  LAG GrouID = 23

VC Bay2 = ports X1 & X2  LAG GrouID = 25

 

Is it worth my time redoing this and forced them to use the same GroupID ?

 

******************

 

Mark responded:

 

******************

 

LAG IDs are specific to a module and have no relevance between modules.

So no, no bad consequences and leave as is.

 

*******************

 

Other comments or questions?