Implementing Multi-Chassis Link Aggregation Groups (MC-LAG) between Nexus7K and HP 5950 TOR Switch

[Praveen3]

I have a query for forming a LAG between HPE 5950 [ IRF, virtual chassis ] and Cisco 7k [ vpc, virtual chasiss] 

---

---

[parnassus · Accepted solution]

From a logical topology standpoint you're required to setup two simple Link Aggregation Groups (LAGs), one on IRF side and the other on the vPC side, using LACP and permitting required VLANs...IRF will see just a logical switch and vPC will do the same...you can use a cross-connect connectivity pattern in which each single physical switch on each side (IRF and vPC) is connected to both members of other side...in the end 4 links will be enough (4 ports on IRF, 4 ports on vPC).

[Praveen3]

Hi parnassus ,

Thanks for your response.

Can you share sample configuration or URL for Link Aggregation between VPC and IRF.

[VoIP-Buddy]

In order to accomplish this, you should also use Dynamic LACP on both sides so that they can manage the link.

Best practice would be to put the links on different members of the virtual switch so that you have a bit of redundancy.  In the Comware world, a port on switch 1 and a second port on switch 2.

For example:

interface Bridge-Aggregation1
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 74 100
link-aggregation mode dynamic
# 

interface FortyGigE1/0/54
port link-mode bridge

port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 74 100
port link-aggregation group 1
#
interface FortyGigE2/0/54
port link-mode bridge
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 74 100
port link-aggregation group 1
#

In the Comware world it is very important that the only configuration you do directly on the ports is set the link-aggregation group.  After that, you do the entire configuration through the Bridge-aggregation interface.  It will send the config to the ports and manage it for you.

Regards,

David

[Praveen3]

Thanks for your email.