Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 967
  • Last Modified:

Cisco-HP Link Aggregation?

I am looking to get some help on setting up a Trunk/channel-group link between a Cisco Catalyst 3570 and an HP Procurve 2810.  I was able to setup a single link to carry all my vlan traffic between the 2 devices, but before I can put it into production I would like to add a second link.  I had found an article that had me setup a static link between the 2, but the link was never able to communicate.  Does anyone know the proper way to set this link up?  Thank you!
  • 2
  • 2
2 Solutions
Can you try to use LACP between them instead of static?
PC2009Author Commented:
I was looking at that, but I have a question.  The HP doc I have says

"The trunk group defined on ProCurve is a Dynamic trunk “Dyn1” and belongs to Vlan1.  It cannot be assigned to any other vlans except via GVRP.  To allocate trunk port to Vlans, one should prefer the “static” trunk, with or without LACP or FEC protocols"

We are not using GVRP, so does this mean I will not be able to use vlans on the HP switch?
I think this would be a good place to start

Cisco side

cisco(config)# interface range fastethernet 0/47-48
cisco(config-if-range)# channel-group 1 mode on
cisco(config-if-range)# interface po 1
cisco(config-if-range)# switchport trunk encapsulation dot1q
cisco(config-if-range)# switchport mode trunk
cisco(config-if-range)# switchport trunk allowed vlan 1,3-5,6 etc
cisco(config-if-range)# exit


procurve(config)# trunk b23-b24 Trk1 Trunk
procurve(config)# trunk b21-b22 Trk2 Trunk
procurve(config)# vlan 1
procurve(vlan-1)# ip address
procurve(vlan-1)# vlan 3
procurve(vlan-3)# tagged trk1-trk2
procurve(vlan-3)# vlan 4
procurve(vlan-4)# tagged trk1-trk2
procurve(vlan-4)# vlan 5
Here is a good article to read about differences and examples
PC2009Author Commented:
Thank you both, I actually used both of your comments to make things work.  The Cisco side was very easy to setup, but I had to make a change on the Procurve config.  I set it for lacp not trunk...

procurve(config)# trunk 47-48 Trk1 lacp

This link was also very helpful and I will place it here for folks in the future who run into the same issue.


Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now