Comware Based

LACP randomly fail between hpe5700 and cisco 6509

 
SOLVED
Go to solution
lozair31
Advisor

LACP randomly fail between hpe5700 and cisco 6509

Hi,

we encounter here a LACP problem between two devices, this LACP is constructed with two Ten Gigabit interfaces on each side. :

  • HPE5700-32XGT-8XG-2QSFP+ (interfacename =Bridgeaggregation33 [ XGE1/0/33 + XGE2/0/33 ])
  • Cisco 6509 (interfacename=Po14 [ Te1/3 + Te3/3 ]).

 

Randomly, once a week, the Cisco 6509 set PortChannel 14 in errdisabled state and cut the link to the HPE5700 with the following message :

CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Te1/3, putting Te1/3 in err-disable state
CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Te3/3, putting Te3/3 in err-disable state
%PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Te1/3 in err-disable state

On the same time these logs appears on HPE5700 :

<190>Dec  3 02:33:59 2016 SWITCH %%10LAGG/6/LAGG_INACTIVE_CONFIGURATION: Member port XGE1/0/33 of aggregation group BAGG33 changed to the inactive state, because the aggregation configuration of the port is incorrect.
<190>Dec  3 02:34:00 2016 SWITCH %%10LAGG/6/LAGG_ACTIVE: Member port XGE1/0/33 of aggregation group BAGG33 changed to the active state.
<190>Dec  3 02:34:00 2016 SWITCH %%10LAGG/6/LAGG_INACTIVE_CONFIGURATION: Member port XGE2/0/33 of aggregation group BAGG33 changed to the inactive state, because the aggregation configuration of the port is incorrect.
<190>Dec  3 02:34:00 2016 SWITCH %%10LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE1/0/33 of aggregation group BAGG33 changed to the inactive state, because the physical state of the port is down.
<187>Dec  3 02:34:00 2016 SWITCH %%10IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet2/0/33 link status is down.
<189>Dec  3 02:34:00 2016 SWITCH %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet2/0/33 is down.
<187>Dec  3 02:34:00 2016 SWITCH %%10IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/33 link status is down.
<189>Dec  3 02:34:00 2016 SWITCH %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet1/0/33 is down.
<190>Dec  3 02:34:00 2016 SWITCH %%10LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE1/0/33 of aggregation group BAGG33 changed to the inactive state, because the physical state of the port is down.
<187>Dec  3 02:34:00 2016 SWITCH %%10IFNET/3/PHY_UPDOWN: Bridge-Aggregation33 link status is down.
<189>Dec  3 02:34:00 2016 SWITCH %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Bridge-Aggregation33 is down.

 

Reading the logs, it seems there is an event on HPE5700 around bridge aggregation 33 port members. This event seems produce the err-disable protection on the cisco side..After five minutes the Cisco leave the err-disable state on the portchannel 14 and all works like a charm...

.We have read the docs and guides about LACP but we can't identify the reason of this random event on the HPE5700. I want precise there is no errors on the links between cisco and HP.

We use the following configuratoin on the HP :

Config

 

interface Ten-GigabitEthernet1/0/33
description "XXXXXXXXXX"
port link-type trunk
port trunk permit vlan all
port link-aggregation group 33

interface Ten-GigabitEthernet2/0/33
description "XXXXXXXXXX"
port link-type trunk
port trunk permit vlan all
port link-aggregation group 33

interface Bridge-Aggregation33
description "YYYYYYYYY"
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic


 

 

State

 

display interface Ten-GigabitEthernet 1/0/33
Ten-GigabitEthernet1/0/33
Current state: UP
Line protocol state: UP
IP packet frame type: Ethernet II, hardware address: e8f7-24b9-411c
Description: "palays port"
Bandwidth: 10000000 kbps
Loopback is not set
Media type is optical fiber, port hardware type is 10G_BASE_SR_SFP
10Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 10000
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
PVID: 1
MDI type: Automdix
Port link-type: Trunk

display interface Ten-GigabitEthernet 2/0/33
Ten-GigabitEthernet2/0/33
Current state: UP
Line protocol state: UP
IP packet frame type: Ethernet II, hardware address: e8f7-24b6-9ae3
Description: "palays port"
Bandwidth: 10000000 kbps
Loopback is not set
Media type is optical fiber, port hardware type is 10G_BASE_SR_SFP
10Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
Maximum frame length: 10000
Allow jumbo frames to pass
Broadcast max-ratio: 100%
Multicast max-ratio: 100%
Unicast max-ratio: 100%
PVID: 1
MDI type: Automdix
Port link-type: Trunk

display interface Bridge-Aggregation 33
Bridge-Aggregation33
Current state: UP
IP packet frame type: Ethernet II, hardware address: e8f7-24b9-411c
Description: "Aggregation de liens vers palays"
Bandwidth: 20000000 kbps
20Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
PVID: 1
Port link-type: Trunk

 

Thanks for your help or advices

33 REPLIES 33
peyrache
Respected Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

hello

shall you post firmware versions for both please

thanks

JY

Vince-Whirlwind
Honored Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

What if you use link aggregation-mode static instead of dynamic?

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

the firmware versions :

HPE5700 :

Current software images:
!   flash:/5700-cmw710-boot-r2422p01.bin
!   flash:/5700-cmw710-system-r2422p01.bin

Cisco 6509 :

Image: Software: s72033_rp-ADVENTERPRISEK9-M, 12.2(33)SXJ9, RELEASE SOFTWARE (fc4)
!Image: Compiled: Mon 16-Mar-15 14:07 by prod_rel_team
!Image: disk1:s72033-adventerprisek9-mz.122-33.SXJ9.bin

Hope this can help

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

We don't test it.

This link join network core router to our server switch stack.......

Do you think this can resolve the issue ?

parnassus
Honored Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

What is the display link-aggregation verbose command's output on the HPE 5700?

Mumble Mumble...you cited stack ("This link join network core router to our server switch stack......."), do you have an IRF Stack of HPE 5700 units or just a single HPE 5700 Switch?


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

Re: LACP randomly fail between hpe5700 and cisco 6509

should be great to be in Static in both side if problem still occured

debug lacp on cisco side witl help to get more details

JY

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

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

Aggregate Interface: Bridge-Aggregation33
Aggregation Mode: Dynamic
Loadsharing Type: Shar
Management VLAN : None
System ID: 0x8000, e8f7-24b9-40d3
Local: 
  Port             Status  Priority Oper-Key  Flag
--------------------------------------------------------------------------------
  XGE1/0/33        S       32768    1         {ACDEF}
  XGE2/0/33        S       32768    1         {ACDEF}
Remote: 
  Actor            Partner Priority Oper-Key  SystemID               Flag   
--------------------------------------------------------------------------------
  XGE1/0/33        260     32768    14        0x8000, 0011-5dbe-3000 {ACDEF}
  XGE2/0/33        772     32768    14        0x8000, 0011-5dbe-3000 {ACDEF}

Yes we have an IRF Stack of two HPE switch

display irf
MemberID    Role    Priority  CPU-Mac         Description
 *+1        Master  32        00e0-fc0f-8c02  ---
   2        Standby 1         00e0-fc0f-8c03  ---
--------------------------------------------------
 * indicates the device is the master.
 + indicates the device through which the user logs in.

 The bridge MAC of the IRF is: e8f7-24b9-40d3
 Auto upgrade                : yes
 Mac persistent              : always
 Domain ID                   : 0
 IRF mode                    : normal
lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

We will attempt this config if the error come again

thks for your advice

VoIP-Buddy
HPE Pro

Re: LACP randomly fail between hpe5700 and cisco 6509

The only gotcha with static link-agg is that the links never go down.  If something happens, you'll be sending packets into a black hole.

I would debug lacp on the 5700's as well to see what is causing this event.

You might also want to check Spanning Tree, if it is enabled, to see if one of the ports is blocked.

David

I work for HPE

Accept or Kudo