Virtual Connect - LAG ID vs CISCO Channel-ID

[Jorge Fabregas]

Hello guys,

I just configured a LACP bond between a Cisco switch and Virtual Connect. The channel seems to be working and I see both links active (on the VC side) and sharing the same LAG ID.

My question is: This LAG ID that VCs shows... does it needs to match the "Channel ID" on the Cisco side? In my case, it doesn't match.

Thanks,
Jorge

[Michael Leu · Accepted solution]

Hello Jorge,

in my environment the LAG IDs and Cisco "Channel ID" are also totally different. It works fine.

If you click on the [?] button in the VC Manager there is a helpful explanation:
LAG ID
Identifies the group of ports that have been aggregated together to form an 802.3ad Link Aggregation Group. This ID is unique only within a single VC-Enet module, meaning the same LAG ID can be used on different VC-Enet modules, but it is only meaningful for ports within the same VC-Enet module.

[Jorge Fabregas]

Thanks Michael for confirming and for the help tip (I missed that one)!

Thanks again.

All the best,
Jorge