Comware Based
1752361 Members
6014 Online
108787 Solutions
New Discussion юеВ

Configuring LACP in switch A5120

 
hugolia
Regular Visitor

Configuring LACP in switch A5120

I need to configure a link-aggregation with LACP in a switch A5120-48.

I follow the guides but when I display the status of the LACP found that the operation key of the ports are different and cannot find any reference in any manual about how to change these keys.

Aggregation Interface: Bridge-Aggregation1
Aggregation Mode: Dynamic
Loadsharing Type: Shar
System ID: 0x8000, 5c8a-38bf-d2e1
Local:
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------

  GE1/0/41         U       32768    2         {ACG}
  GE1/0/42         U       32768    2         {ACG}
  GE1/0/43         U       32768    3         {ACG}
  GE1/0/44         U       32768    4         {ACG}

 

How can I change the oper-key on the ports?

 

7 REPLIES 7
parnassus
Honored Contributor

Re: Configuring LACP in switch A5120

For equally configured interfaces (let we start with 1/0/41, 1/0/42, 1/0/43 and 1/0/44 in a default condition) all members of the same LAG (Link Aggregation Group), once the LAG is defined the operation key should be exactly the same automatically assigned by the Switch.

"Operational key

When aggregating ports, the system automatically assigns each port an operational key based on port information such as port rate and duplex mode. Any change to this  information triggers a recalculation of this operational key. The operational key of a port indicates the aggregation capability of the port.

In an aggregation group, all selected member ports are assigned the same operational key."


I'm not an HPE Employee
Kudos and Accepted Solution banner
hugolia
Regular Visitor

Re: Configuring LACP in switch A5120

I understand PARNASSUS's reply, but in my case ports 1/0/43 and 1/0/44 are not assigned the same oper-keys as the others ports in the LAG.

We have reset the ports to default, and recreated the LAG many times. We had done this thru the Web-GUI and the CLI. And always with the same result: ports 1/0/43 and 1/0/44 are assigned different keys.

We had created another LAG without problems in the same switch on ports 1/0/45, 1/0/46, 1/0/47, and 1/0/48.

parnassus
Honored Contributor

Re: Configuring LACP in switch A5120

In Comware operating system based switches the order of steps to follow in order to correctly setup a LAG is really important (Were your procedures exactly the same in both cases?).

Which software version your Switch is running on exactly?

I'm not an HPE Employee
Kudos and Accepted Solution banner
hugolia
Regular Visitor

Re: Configuring LACP in switch A5120

We follow the guide we found in the web step by step in all cases.

Software version is: 5.20.99

parnassus
Honored Contributor

Re: Configuring LACP in switch A5120


@hugolia wrote:

We follow the guide we found in the web step by step in all cases.

Software version is: 5.20.99


The 5.20.99 string describes the specific Comware 5 version your Switch is running on...to see the the exact (and complete) Comware 5 (or 7) software version it is running on, the display version command should be issued at CLI.


I'm not an HPE Employee
Kudos and Accepted Solution banner
hugolia
Regular Visitor

Re: Configuring LACP in switch A5120

This is the complete switch version:

<HP A5120-48G EI>display version
HP Comware Platform Software
Comware Software, Version 5.20.99, Release 2220P02
Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P.
HP A5120-48G EI Switch with 2 Interface Slots uptime is 107 weeks, 3 days, 22 hours, 49 minutes

HP A5120-48G EI Switch with 2 Interface Slots with 1 Processor
128M    bytes SDRAM
16384K  bytes Flash Memory

Hardware Version is REV.C
CPLD Version is 007
Bootrom Version is 618
[SubSlot 0] 48GE+4SFP Hardware Version is REV.C
[SubSlot 1] 2 SFP+ Hardware Version is REV.A
[SubSlot 2] 2 SFP+ Hardware Version is REV.A

parnassus
Honored Contributor

Re: Configuring LACP in switch A5120

Your Switch is running a 5 Years old software version R2220P02 (April 2013)...why not testing again LAG configuration on problematic ports - from scratch - once software version R2222P09 (April 2018) has been deployed?

I'm not an HPE Employee
Kudos and Accepted Solution banner