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
Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

LACP between HP 5830 (IRF) and HP Procurve 5412

 
aali
Frequent Advisor

LACP between HP 5830 (IRF) and HP Procurve 5412

I have HP 5830 switches IRF together in a Colo and HP Procurve 5412 switch in our Data Center.

 

We have a 300MB Ethernet Hand Off between two locations via Cox Communciation connected between 5830s and 5412 and link is up and running fine.

 

For redudancy and more bandwith we added a 2nd Ethernet hand off via Time Warner and I can't LACP both circuits together.

 

See the config below:

 

5830s

 

Interface bridgeaggregation 1

Link-type mode dynamic

port  link-type trunk

port trunk permit vlan 2 100 

 

interface gigabit 1/0/3

port link-aggregation group 1

 

interface gigabit 2/0/3

port link-aggregation group 1

 

5412

trunk C1 D1 trk1 trunk

 

vlan 2

tagged trk1

 

vlan 100

tagged trk1

 

 

all physical links are up at both end, but having some issue with HP 5830 switches, see below:

 

display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
        D -- Synchronization, E -- Collecting, F -- Distributing,
        G -- Defaulted, H -- Expired

Aggregation Interface: Bridge-Aggregation1
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, d07e-28f0-71a6
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  GE1/0/3          S       32768    1         {ACDEFG}
  GE2/0/3          U       32768    1         {ACG}
Remote:
  Actor            Partner Priority Oper-Key  SystemID               Flag
--------------------------------------------------------------------------------
  GE1/0/3          0       32768    0         0x8000, 0000-0000-0000 {DEF}
  GE2/0/3          0       32768    0         0x8000, 0000-0000-0000 {DEF}
[IRV-COLO-SW1]dis
[IRV-COLO-SW1]display link
[IRV-COLO-SW1]display link-aggregation summ
[IRV-COLO-SW1]display link-aggregation summary
Aggregation Interface Type:
BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, d07e-28f0-71a6

AGG         AGG       Partner ID               Select Unselect   Share
Interface   Mode                               Ports  Ports      Type
-------------------------------------------------------------------------------
BAGG1       D         0x8000, 0000-0000-0000   1      1          Shar

 

Can some shed some lights as why port 2/0/3 wouldn't become the member of bridge aggregation group 1

11 REPLIES
ThomasGlanzmann
Frequent Advisor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Hello,

in the bridge aggregation group you need to specify 'mad enable' see also IRF configuration guide.

 

interface Bridge-Aggregation2
 port link-type trunk
 port trunk permit vlan all
 link-aggregation mode dynamic
 mad enable

interface GigabitEthernet2/0/23
 port link-mode bridge
 port link-type trunk
 port trunk permit vlan all
 port link-aggregation group 2

interface GigabitEthernet3/0/23
 port link-mode bridge
 port link-type trunk
 port trunk permit vlan all
 port link-aggregation group 2

 

Let me know if it works for you.

 

Cheers,

       Thomas

aali
Frequent Advisor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Thomas,

 

Thanks for your reply.  MAD is one of the IRF features to prevent split-brain, not the requirement.  My IRF is functional.  The problem I am having is the LACP between 5830s in Colo and Procurve 5412 in HQ over the (2) WAN Ethernet Hand Off Circuits.

 

Thanks,

 

 

showneek
Respected Contributor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Hi,

 

It seems you have on 5830s  Link-type mode dynamic, that means static LACP. Thats correct.

 

But on 5412 you have trunk C1 D1 trk1 trunkthat means non-protocol trunk, not LACP.

 

Try to configure trunk on 5412 as static LACP... trunk C1 D1 trk1 LACP.


Not sure if you can only change type or delete this trunk and create new LACP trunk and tag trk1 again in appropriate vlans.

 

BR,

Jan

 

 

aali
Frequent Advisor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Tried that as well, but couldn't get that to work either.

 

With LACP settings at the 5412, the sTP will put the Trk1 in blocking mode and nothing would work.

 

One thing to mention that at 5830, I have stp enabled with MSTP mode, and at the 5412, the mode is standarad STP.

 

Not sure if STP plays a role here with LACP settings.

 

Thanks,

 

Apachez-
Trusted Contributor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Is this how it looks in your config?

 

"

Interface bridgeaggregation 1

Link-type mode dynamic

port  link-type trunk

port trunk permit vlan 2 100 

 

interface gigabit 1/0/3

port link-aggregation group 1

 

interface gigabit 2/0/3

port link-aggregation group 1

"

 

Because when setting up bagg-interfaces on comware you first create the bagg:

 

"

Interface bridgeaggregation 1

Link-type mode dynamic

"

 

then you go to each physical which will be part of this bagg and join them to this bagg-interface:

 

"

interface gigabit 1/0/3

port link-aggregation group 1

 

interface gigabit 2/0/3

port link-aggregation group 1

"

 

and finally you return to the bagg-interface to complete the configuration of adding vlans, trunk/hybrid/access etc:

 

"

port  link-type trunk

port trunk permit vlan 2 100

"

 

The thing here is that once completed the resulting configuration (display current-configuration) should look like this:

 

"

Interface bridgeaggregation 1

Link-type mode dynamic

port  link-type trunk

port trunk permit vlan 2 100 

 

interface gigabit 1/0/3

port  link-type trunk

port trunk permit vlan 2 100

port link-aggregation group 1

 

interface gigabit 2/0/3

port  link-type trunk

port trunk permit vlan 2 100

port link-aggregation group 1

"

 

That is whatever you config in the bagg-interface will be automagically copied down to the physical interfaces.

 

Perhaps its something like this which is missing in your case?

 

Also you should verify which vlan you wish to use as PVID for this trunk (otherwise vlan1 will be used by default).

aali
Frequent Advisor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

This is how i did it and will redo it again to make sure.  Will see what happens.

 

Is there any issues with doing LACP over two different Service provider's WAN circuits?

 

 

Apachez-
Trusted Contributor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Well you cant use a single LACP towards two different ISPs.

 

That is one cable to ISP1 and one cable to ISP2.

 

aali
Frequent Advisor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

We own the Ethernet Hand off circuits and can do anything such L2 or L3 etc.

 

Both providers are just providing the physicals circuits and nothing else.  The key is end-to-end which are 5830s and 5412.

 

 

Apachez-
Trusted Contributor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Oh, ok... then I assume this one should work:

 

http://robertparten.com/trunking-between-3com-and-hp-switches/

ChrisVazquez
Frequent Visitor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

This solution worked for me in a similar situation (5120s in IRF connecting to a 2620), except I had to clean the slate on the physical interfaces first by undo'ing some config.  After that, this ordering worked.

 

Thanks!

manuel.bitzi
Trusted Contributor

Re: LACP between HP 5830 (IRF) and HP Procurve 5412

Please check with your provider if LACP-PAckets won't be dropped. Usually they will be dropped on ethernet-service-links.

 

br

Manuel

H3CSE, MASE Network Infrastructure [2011], Switzerland