Comware Based

Problems with LACP betwen 5940 and 2930M

 
SOLVED
Go to solution
LPAX
Occasional Advisor

Problems with LACP betwen 5940 and 2930M

Hello everyone,
I ask for help with a strange problem.
I have a network infrastructure consisting of 2 HPE5940 switches (mod. JH398A) in IRF mode and 6 HPE2930M stacks. All stacks are connected in LACP to 2 5940. The trunk and LACP configurations are the same for all switches, but on two stacks only one port joins the LACP, the other is "blocked".
This is the message I have on the 2930M log
I 05/10/21 04:41:21 00435 ports: ST2-CMDR: port 2 / A1 is Blocked by LACP
I 05/10/21 04:41:21 00077 ports: ST2-CMDR: port 2 / A1 in Trk1 is now off-line
the sh lacp peer command gives me this output

LACP Peer Information.

System ID: 9020c2-180c4a

Local Local Port Oper LACP Tx
Port  Trunk System                 ID Port  Priority Key Mode Timer
------ ------ -----------------        ----- --------- ------- -------- -----
1 / A1  Trk1   4caea3-4fd2c0        14     32768    14  Active   Slow
2 / A1  Trk1  000000-000000   55     32768    14  Active   Slow

from side 5940 the command display link-aggregation verbose of the corresponding aggregate gives me this output

Loadsharing Type: Shar - Loadsharing, NonS - Non-Loadsharing
Port Status: S - Selected, U - Unselected, I - Individual
Port: A - Auto port, M - Management port, R - Reference port
Flags: A - LACP_Activity, B - LACP_Timeout, C - Aggregation,
D - Synchronization, E - Collecting, F - Distributing,
G - Defaulted, H - Expired

Aggregate Interface: Bridge-Aggregation114
Creation Mode: Manual
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLANs: None
System ID: 0x8000, 4cae-a34f-d2c0
Local:
Port             Status Priority  Index Oper-Key Flag
XGE1 / 1/14  S         32768    14      14              {ACDEF}
XGE2 / 1/14 U         32768    55      14              {AC}
Remote:
Actor                   Priority  Index  Oper-Key  SystemID                           Flag
XGE1 / 1/14 (R)  0             50       532            0xc4a, 9020-c218-0c4a   {ACDEF}
XGE2 / 1/14        0             103      532            0xc4a, 9020-c218-0c4a   {AEF}

Those who previously managed the infrastructure configured the MSTP.

The optical links are all functional.

Thanks in advance

Luigi

14 REPLIES 14
akg7
HPE Pro

Re: Problems with LACP betwen 5940 and 2930M

Hello,

I have some questions:

1. What is the interface type on Aruba 2930 switches, is it 10gig or FE port?

2. Can you share 'show lacp' output?

3. Please share show log from Aruba 2930 and display log from 5940 switch?

4. Check the duplex mode on both swithes interface?

 

Thanks!

I am an HPE Employee

Accept or Kudo

parnassus
Honored Contributor

Re: Problems with LACP betwen 5940 and 2930M

Hi @LPAX can you share the Aruba 2930F configuration related to involved interfaces (Trk1, 1/A1 and 2/A1)?

We expect that Trk1 (LACP) = 1/A1 + 2/A1 where Port Trunk's member interfaces 1/A1 and 2/A1 were in their default states/configurations when Trk1 was formed, all subsequent configurations are then applied to Trk1.

What's about Spanning Tree configuration on Trk1?


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

Re: Problems with LACP betwen 5940 and 2930M

Hello everybody,

the configuration on the ports is the same as for the other switches which have no problems.

This is the configuration on 2930M

-------------------------------------------------------------------------

interface 1/A1
name "TRUNK_VS_HP_1/1/14"
untagged vlan 1
trunk trk1 lacp
no snmp-server enable traps link-change
exit

ASI-PUD# sh run int 2/a1

Running configuration:

interface 2/A1
name "TRUNK_VS_HP_2/1/14"
untagged vlan 1
trunk trk1 lacp
no snmp-server enable traps link-change
exit

ASI-PUD# sh run int trk1

Running configuration:

interface Trk1
tagged vlan 2-3,10,13,20,27,64,100,210,777,900-902
untagged vlan 1
spanning-tree priority 4
exit

-----------------------------------------------------------------------------------

This is the configuration on 5940

____________________________________________________________________________

<ASI-CS-A>display current-configuration interface Ten-GigabitEthernet 1/1/14
#
interface Ten-GigabitEthernet1/1/14
port link-mode bridge
description RACK-PUD-A
port link-type trunk
port trunk permit vlan 1 to 3 10 13 20 27 64 100 210 777 900 to 902
port link-aggregation group 114
#
return
<ASI-CS-A>display current-configuration interface Ten-GigabitEthernet 2/1/14
#
interface Ten-GigabitEthernet2/1/14
port link-mode bridge
description RACK-PUD-B
port link-type trunk
port trunk permit vlan 1 to 3 10 13 20 27 64 100 210 777 900 to 902
duplex full
shutdown
port link-aggregation group 114
#
return
<ASI-CS-A>display current-configuration interface Bridge-Aggregation 114
#
interface Bridge-Aggregation114
description NODO-PUD
port link-type trunk
port trunk permit vlan 1 to 3 10 13 20 27 64 100 210 777 900 to 902
link-aggregation mode dynamic
#
return

this is the output of the display stp interface Bridge-Aggregation 114 command

----[CIST][Port1629(Bridge-Aggregation114)][FORWARDING]----
Port protocol : Enabled
Port role : Designated Port
Port ID : 128.1629
Port cost(Legacy) : Config=auto, Active=2
Desg.bridge/port : 0.4cae-a34f-d2c0, 128.1629
Port edged : Config=disabled, Active=disabled
Point-to-Point : Config=auto, Active=true
Transmit limit : 10 packets/hello-time
TC-Restriction : Disabled
Role-Restriction : Disabled
Protection type : Config=none, Active=none
MST BPDU format : Config=auto, Active=802.1s
Port Config-
Digest-Snooping : Disabled
Rapid transition : False
Num of VLANs mapped : 14
Port times : Hello 2s MaxAge 20s FwdDelay 15s MsgAge 0s RemHops 20
BPDU sent : 5038042
TCN: 0, Config: 0, RST: 0, MST: 5038042
BPDU received : 0
TCN: 0, Config: 0, RST: 0, MST: 0

Thanks in advance

Luigi

LPAX
Occasional Advisor

Re: Problems with LACP betwen 5940 and 2930M

the TenGiga 2/1/14 interface on 5940 is shutdown because when it is UP I have continuous UP / DOWN interface alarms

Luigi

akg7
HPE Pro

Re: Problems with LACP betwen 5940 and 2930M

Hello @LPAX,

Since the configuration on the ports are  same as for the other switches which have no problems.

Also you are getting continuous UP / DOWN interface alarms if TenGiga 2/1/14 interface on 5940 is 'UP'.

1. Can you please share the exact log when tengig 2/1/14 port was 'UP'?

2. For troubleshooting purpose, if you have any spare transceiver then try to replace or swap with it and check again?

Thanks!

 

I am an HPE Employee

Accept or Kudo

LPAX
Occasional Advisor

Re: Problems with LACP betwen 5940 and 2930M

Hello everyone,
I replaced both SFP and SFP + modules.
However, giving the various commands to see the signal levels on the optical fiber I have good results.
The only oddity I encounter is on the 5940, it seems to recognize the SFP + module but not the speed or the duplex, trying to use the other LSWM124XG2Q module installed on the switch.
This is the 5940 log when I put UP the port, in this case it is the Ten 2/1/18 port (the other module)

%May 13 11:02:50:056 2021 ASI-CS-A LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port Ten-GigabitEthernet2/1/18 (IfIndex 181), neighbor's chassis ID is 9020-c218-0c4a, port ID is 103.
%May 13 11:02:51:291 2021 ASI-CS-A IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:51:319 2021 ASI-CS-A IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:51:331 2021 ASI-CS-A LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE2/1/18 of aggregation group BAGG114 changed to the inactive state, because the physical state of the port is down.
%May 13 11:02:52:786 2021 ASI-CS-A IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet2/1/18 changed to up.
%May 13 11:02:52:799 2021 ASI-CS-A LAGG/6/LAGG_ACTIVE: Member port XGE2/1/18 of aggregation group BAGG114 changed to the active state.
%May 13 11:02:52:820 2021 ASI-CS-A IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet2/1/18 changed to up.
%May 13 11:02:52:055 2021 ASI-CS-A LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port Ten-GigabitEthernet2/1/18 (IfIndex 181), neighbor's chassis ID is 9020-c218-0c4a, port ID is 103.
%May 13 11:02:55:430 2021 ASI-CS-A IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:55:459 2021 ASI-CS-A IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:55:465 2021 ASI-CS-A LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE2/1/18 of aggregation group BAGG114 changed to the inactive state, because the physical state of the port is down.
%May 13 11:02:58:326 2021 ASI-CS-A IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet2/1/18 changed to up.
%May 13 11:02:58:345 2021 ASI-CS-A LAGG/6/LAGG_ACTIVE: Member port XGE2/1/18 of aggregation group BAGG114 changed to the active state.
%May 13 11:02:58:375 2021 ASI-CS-A IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet2/1/18 changed to up.
%May 13 11:02:58:740 2021 ASI-CS-A IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:58:770 2021 ASI-CS-A IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet2/1/18 changed to down.
%May 13 11:02:58:777 2021 ASI-CS-A LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE2/1/18 of aggregation group BAGG114 changed to the inactive state, because the physical state of the port is down.

This is the output of the display transceiver diagnosis interface Ten-GigabitEthernet 2/1/18 command on 5940

<ASI-CS-A>display transceiver diagnosis interface Ten-GigabitEthernet 2/1/18
Ten-GigabitEthernet2/1/18 transceiver diagnostic information:
Current diagnostic parameters:
Temp.(C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)
23                   3.30            5.35          -4.04                    -2.17
Alarm thresholds:
Temp.(C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)
High 73          3.80           9.35          1.00                      -1.00
Low   -3         2.81            1.00         -11.90                     -10.30

and this on 2930M

ASI-PUD# sh int transceiver 2/a1 det

Transceiver in 2/A1
Interface Index : 103
Type : SFP+SR
Model : J9150D
Connector Type : LC
Wavelength : 850nm
Transfer Distance : 80m (50um), 20m (62.5um), 300m (50um OM3),
Diagnostic Support : DOM
Serial Number : CN09KJW0M0

Status
Temperature : 31.875C
Voltage : 3.2263V
Tx Bias : 5.502mA
Tx Power : 0.5715mW, -2.430dBm
Rx Power : 0.3882mW, -4.109dBm

 

Thanks in advance

Luigi

akg7
HPE Pro

Re: Problems with LACP betwen 5940 and 2930M

Hello @LPAX ,

In some cases signals looks fine for SFP however the SFP is faulty. As you mentioned that you have replaced it.

I believe the device is on latest software version and spanning tree is enabled on BAGG ports?

Thanks!

I am an HPE Employee

Accept or Kudo

LPAX
Occasional Advisor

Re: Problems with LACP betwen 5940 and 2930M

Hello @akg7 ,

spanning-tree is enabled on BAGG ports and I think the firmware is the latest

Switch 2930M

Status and Counters - General System Information

System Name : ASI-PUD
System Contact :
System Location :
MAC Age Time (sec) : 300
Time Zone : 60
Daylight Time Rule : Continental-US-and-Canada

Software revision : WC.16.08.0008
Base MAC Addr : 9020c2-180c4a

Member :1

ROM Version : WC.17.02.0006
Up Time : 118 days
CPU Util (%) : 10
MAC Addr : 9020c2-180c40
Serial Number : SG93JQN5QT
Memory - Total : 340,754,944
Free : 208,033,524

 

Member :2

ROM Version : WC.17.02.0006
Up Time : 118 days
CPU Util (%) : 7
MAC Addr : 9020c2-180c80
Serial Number : SG93JQN5QP
Memory - Total : 340,754,944
Free : 175,778,976

Switch 5940

HPE Comware Software, Version 7.1.070, Release 2702
Copyright (c) 2010-2019 Hewlett Packard Enterprise Development LP
HPE FF 5940 4-slot Switch uptime is 17 weeks, 0 days, 2 hours, 15 minutes
Last reboot reason : Cold reboot

Boot image: flash:/5940-cmw710-boot-r2702.bin
Boot image version: 7.1.070, Release 2702
Compiled May 20 2019 11:00:00
System image: flash:/5940-cmw710-system-r2702.bin
System image version: 7.1.070, Release 2702
Compiled May 20 2019 11:00:00

 

Thanks in advance

Luigi

akg7
HPE Pro

Re: Problems with LACP betwen 5940 and 2930M

Hello @ LPAX,

 

From commands output looks everything is fine. I would like to request you to configure BAGG and ports one more time and if issue remains then log a case on HPE Support Center portal for further resolution using the link: https://support.hpe.com/hpesc/public/home/

 

Thanks!

I am an HPE Employee

Accept or Kudo