Comware Based

LACP randomly fail between hpe5700 and cisco 6509

 
SOLVED
Go to solution
lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

Hi

I can't publish all the conf of our cisco......

reading show tech or show diags there is no physical errors on the links.

We think about STP problem/event...

We successfully enable lacp and stp logs on cisco for now and we are wainting the next random error.

thks for your help and advices

regards

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

The error come again on our switchs.....

Reading and analyzing the logs it seems linked to server reboot.

The attached doc show our network topology.

The server reboot all the nights à 2:30 AM.

Every 3 weeks, this reboot is followed by a channel-misconfig error on Port-channel 14 of the Cisco 6500.

But the logs below seems indicate it's the hp5700 which cut the port for unknown reason and when the port come up in the followiong seconds there is a channel misconfiguration detection at the Cisco level.

 

Logs for the H3C 5700 switch :

Jan 19 02:31:50 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.RX CURRENT--
Jan 19 02:31:50 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/35 FSM.PTX PERIODIC_TX--
Jan 19 02:31:50 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/35 FSM.PTX SLOW_PERIODIC--
Jan 19 02:31:50 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/33.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x304, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0xee, state=0x3d Collector: type=3, len=16, col-max-delay=0x8000 Terminator: type=0, len=0
Jan 19 02:31:50 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/35.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x2, pri=0x8000, port-index=0xf0, state=0x3d Partner: type=2, len=20, sys-pri=0x1, sys-mac=02a0-9895-db05, key=0x1, pri=0x0, port-index=0x2, state=0x3d Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.ACTOR-CHURN ACTOR_CHURN_MONITOR--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.ACTOR-CHURN NO_ACTOR_CHURN--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.ACTOR-CHURN NO_ACTOR_CHURN--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX COLLECTING_DISTRIBUTING--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX COLLECTING_DISTRIBUTING--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX DETACHED--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.MUX WAITING--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.PARTNER-CHURN NO_PARTNER_CHURN--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.RX CURRENT--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/33 FSM.RX CURRENT--
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/33.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x304, state=0x1 Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0xee, state=0x3d Collector: type=3, len=16, col-max-delay=0x8000 Terminator: type=0, len=0
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/33.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0xee, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x304, state=0x9 Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:51 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/33.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0xee, state=0x5 Partner: type=2, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x304, state=0x9 Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:51 2017 hp5700 %%10LLDP/6/LLDP_DELETE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor deleted on Port Ten-GigabitEthernet2/0/33 (IfIndex 238), Chassis ID is 0011-5dbe-3000, Port ID is Te3/3.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/3/PHY_UPDOWN: Bridge-Aggregation33 link status is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet1/0/33 link status is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet2/0/33 link status is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Bridge-Aggregation33 is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet1/0/33 is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet2/0/33 is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet2/0/33 is down.
Jan 19 02:31:52 2017 hp5700 %%10IFNET/5/LINK_UPDOWN: Line protocol on the interface Ten-GigabitEthernet2/0/33 is up.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/6/LAGG_ACTIVE: Member port XGE1/0/33 of aggregation group BAGG33 changed to the active state.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/6/LAGG_ACTIVE: Member port XGE2/0/33 of aggregation group BAGG33 changed to the active state.
Jan 19 02:31:52 2017 hp5700 %%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.
Jan 19 02:31:52 2017 hp5700 %%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.
Jan 19 02:31:52 2017 hp5700 %%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.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE2/0/33 of aggregation group BAGG33 changed to the inactive state, because the physical state of the port is down.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of member port up/down.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of member port up/down.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Event: Group 33 updated because of partner port other reason.
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.ACTOR-CHURN ACTOR_CHURN_MONITOR--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.ACTOR-CHURN NO_ACTOR_CHURN--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.ACTOR-CHURN NO_ACTOR_CHURN--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX ATTACHED--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX COLLECTING_DISTRIBUTING--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX COLLECTING_DISTRIBUTING--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX DETACHED--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.MUX WAITING--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.PARTNER-CHURN NO_PARTNER_CHURN--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.RX CURRENT--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.RX CURRENT--
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Packet: PACKET.Ten-GigabitEthernet1/0/33.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x104, state=0x1 Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0x21, state=0x3d Collector: type=3, len=16, col-max-delay=0x8000 Terminator: type=0, len=0
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Packet: PACKET.Ten-GigabitEthernet1/0/33.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0x21, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x104, state=0x9 Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:52 2017 hp5700 %%10LAGG/7/Packet: PACKET.Ten-GigabitEthernet1/0/33.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x1, pri=0x8000, port-index=0x21, state=0x5 Partner: type=2, len=20, sys-pri=0x8000, sys-mac=0011-5dbe-3000, key=0xe, pri=0x8000, port-index=0x104, state=0x9 Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:52 2017 hp5700 %%10LLDP/6/LLDP_DELETE_NEIGHBOR: Nearest bridge agent neighbor deleted on Port Ten-GigabitEthernet1/0/33 (IfIndex 33), Chassis ID is 0011-5dbe-3000, Port ID is Te1/3.
Jan 19 02:31:54 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/34 FSM.RX CURRENT--
Jan 19 02:31:54 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/34.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=4431-92d6-82de, key=0x11, pri=0x8000, port-index=0x36, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x6, pri=0x8000, port-index=0xef, state=0x3d Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:56 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/35 FSM.RX CURRENT--
Jan 19 02:31:56 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/35.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x1, sys-mac=02a0-9895-db05, key=0x1, pri=0x0, port-index=0x2, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x2, pri=0x8000, port-index=0xf0, state=0x3d Collector: type=3, len=16, col-max-delay=0x64 Terminator: type=0, len=0
Jan 19 02:31:57 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.PTX PERIODIC_TX--
Jan 19 02:31:57 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/33 FSM.PTX SLOW_PERIODIC--
Jan 19 02:31:57 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/35 FSM.RX CURRENT--
Jan 19 02:31:57 2017 hp5700 %%10LAGG/7/Packet: PACKET.Ten-GigabitEthernet1/0/35.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x1, sys-mac=02a0-9895-db05, key=0x1, pri=0x0, port-index=0x1, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x2, pri=0x8000, port-index=0x23, state=0x3d Collector: type=3, len=16, col-max-delay=0x64 Terminator: type=0, len=0
Jan 19 02:31:58 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/34 FSM.PTX PERIODIC_TX--
Jan 19 02:31:58 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/34 FSM.PTX SLOW_PERIODIC--
Jan 19 02:31:58 2017 hp5700 %%10LAGG/7/Fsm: -Slot=2; Ten-GigabitEthernet2/0/37 FSM.RX CURRENT--
Jan 19 02:31:58 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/34.send. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x6, pri=0x8000, port-index=0xef, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=4431-92d6-82de, key=0x11, pri=0x8000, port-index=0x36, state=0x3d Collector: type=3, len=16, col-max-delay=0x0 Terminator: type=0, len=0
Jan 19 02:31:58 2017 hp5700 %%10LAGG/7/Packet: -Slot=2; PACKET.Ten-GigabitEthernet2/0/37.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x1, sys-mac=02a0-9895-daaf, key=0x1, pri=0x0, port-index=0x2, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x4, pri=0x8000, port-index=0xf2, state=0x3d Collector: type=3, len=16, col-max-delay=0x64 Terminator: type=0, len=0
Jan 19 02:31:59 2017 hp5700 %%10LAGG/7/Fsm: Ten-GigabitEthernet1/0/37 FSM.RX CURRENT--
Jan 19 02:31:59 2017 hp5700 %%10LAGG/7/Packet: PACKET.Ten-GigabitEthernet1/0/37.receive. size=110, subtype=1, version=1 Actor: type=1, len=20, sys-pri=0x1, sys-mac=02a0-9895-daaf, key=0x1, pri=0x0, port-index=0x1, state=0x3d Partner: type=2, len=20, sys-pri=0x8000, sys-mac=e8f7-24b9-40d3, key=0x4, pri=0x8000, port-index=0x25, state=0x3d Collector: type=3, len=16, col-max-delay=0x64 Terminator: type=0, len=0

 

Logs for the Cisco 6500:

Jan 19 02:31:50 cisco6500 22027920: Jan 19 02:31:48.873 CET: SP: RSTP(1010): starting topology change timer for 35 seconds
Jan 19 02:31:52 cisco6500 22027942: Jan 19 02:31:51.487 CET: SP: LACP: 
Jan 19 02:31:52 cisco6500 22027951: Jan 19 02:31:52.307 CET: SP: LACP: 
Jan 19 02:31:52 cisco6500 22027952: Jan 19 02:31:52.437 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/3, changed state to down
Jan 19 02:31:52 cisco6500 22027953: Jan 19 02:31:52.437 CET: FEC: pagp_switch_is_in_port_channel: Te1/3 is part of agport
Jan 19 02:31:52 cisco6500 22027954: Jan 19 02:31:52.481 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/3, changed state to down
Jan 19 02:31:52 cisco6500 22027955: Jan 19 02:31:52.481 CET: FEC: pagp_switch_is_in_port_channel: Te3/3 is part of agport
Jan 19 02:31:52 cisco6500 22027957: Jan 19 02:31:52.489 CET: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/3, changed state to down
Jan 19 02:31:52 cisco6500 22027958: Jan 19 02:31:52.517 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel14, changed state to down
Jan 19 02:31:52 cisco6500 22027959: Jan 19 02:31:52.517 CET: FEC: pagp_switch_is_in_port_channel: Po14 is not part of any agport
Jan 19 02:31:52 cisco6500 22027960: Jan 19 02:31:52.525 CET: FEC: pagp_switch_portlist_in_channelgroup: Te1/3 part of group 14 
Jan 19 02:31:52 cisco6500 22027961: Jan 19 02:31:52.525 CET: FEC: pagp_switch_portlist_in_channelgroup: Te3/3 part of group 14 
Jan 19 02:31:52 cisco6500 22027962: Jan 19 02:31:52.525 CET: FEC: pagp_switch_portlist_in_channelgroup: Te3/3 part of group 14 
Jan 19 02:31:53 cisco6500 22027963: Jan 19 02:31:52.537 CET: %LINK-3-UPDOWN: Interface Port-channel14, changed state to down
Jan 19 02:31:53 cisco6500 22027964: Jan 19 02:31:52.541 CET: %LINK-3-UPDOWN: Interface TenGigabitEthernet3/3, changed state to down
Jan 19 02:31:54 cisco6500 22027965: Jan 19 02:31:52.713 CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Te1/3, putting Te1/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027966: Jan 19 02:31:52.737 CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Te3/3, putting Te3/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027967: Jan 19 02:31:53.157 CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Te1/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027968: Jan 19 02:31:53.157 CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Te3/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027969: Jan 19 02:31:53.157 CET: %PM-SPSTBY-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Po14 in err-disable state
Jan 19 02:31:54 cisco6500 22027973: Jan 19 02:31:52.431 CET: %PM-SP-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Te1/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027975: Jan 19 02:31:52.475 CET: SP: LACP: if_down: Te1/3
Jan 19 02:31:54 cisco6500 22027980: Jan 19 02:31:52.475 CET: %PM-SP-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Te3/3 in err-disable state
Jan 19 02:31:54 cisco6500 22027982: Jan 19 02:31:52.527 CET: SP: LACP: if_down: Te3/3
Jan 19 02:31:54 cisco6500 22027987: Jan 19 02:31:52.527 CET: %PM-SP-4-ERR_DISABLE: channel-misconfig error detected on Po14, putting Po14 in err-disable state
Jan 19 02:31:54 cisco6500 22027988: Jan 19 02:31:52.759 CET: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/3, changed state to down
Jan 19 02:31:54 cisco6500 22027989: Jan 19 02:31:52.759 CET: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface TenGigabitEthernet3/3, changed state to down
Jan 19 02:31:54 cisco6500 22027990: Jan 19 02:31:52.759 CET: %LINK-SP-3-UPDOWN: Interface TenGigabitEthernet1/3, changed state to down
Jan 19 02:31:54 cisco6500 22027991: Jan 19 02:31:52.759 CET: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface Port-channel14, changed state to down
Jan 19 02:31:54 cisco6500 22027992: Jan 19 02:31:52.759 CET: %LINK-SP-3-UPDOWN: Interface Port-channel14, changed state to down
Jan 19 02:31:54 cisco6500 22027993: Jan 19 02:31:52.759 CET: %LINK-SP-3-UPDOWN: Interface TenGigabitEthernet3/3, changed state to down
Jan 19 02:31:57 cisco6500 22028027: Jan 19 02:31:56.961 CET: SP: LACP: 

Thanks for your advices

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

network topology

peyrache
Respected Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

so now need to debug LACP packets during event i think

do you have log from switch where Server is connected ?

JY

peyrache
Respected Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

also there a know issue on Blade switch with LACP dont' know is relevant in your case

ymptom:
LACP packets received from downstream port-channel members are flooded by the 3120 switch instead of being processed.

Conditions:
Issue seen on CBS3120 switch running 12.2(40)EX1

Workaround:
Instead of LACP please use a "mode on" for bundling the member links.

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

Here the logs of the Cisco CBS :

<189>150915: Jan 19 02:31:18.826 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/14, changed state to down
<191>150916: Jan 19 02:31:18.868 CET:  STP: PVST vlan 1010 port Gi0/14 created, ext id 4492944
<191>150917: Jan 19 02:31:18.868 CET: RSTP(1010): initializing port Gi0/14
<191>150918: Jan 19 02:31:18.868 CET: RSTP(1010): Gi0/14 is now designated
<191>150919: Jan 19 02:31:18.876 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150920: Jan 19 02:31:20.210 CET: RSTP(1010): transmitting a proposal on Gi0/14
<189>150921: Jan 19 02:31:20.839 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/14, changed state to up
<191>150922: Jan 19 02:31:22.224 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150923: Jan 19 02:31:24.237 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150924: Jan 19 02:31:26.250 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150925: Jan 19 02:31:28.263 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150926: Jan 19 02:31:30.277 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150927: Jan 19 02:31:32.290 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150928: Jan 19 02:31:33.876 CET: RSTP(1010): Gi0/14 fdwhile Expired
<191>150929: Jan 19 02:31:34.312 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150930: Jan 19 02:31:36.325 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150931: Jan 19 02:31:38.338 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150932: Jan 19 02:31:40.352 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150933: Jan 19 02:31:42.365 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150934: Jan 19 02:31:44.378 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150935: Jan 19 02:31:46.392 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150936: Jan 19 02:31:48.405 CET: RSTP(1010): transmitting a proposal on Gi0/14
<191>150937: Jan 19 02:31:48.883 CET: RSTP(1010): Gi0/14 fdwhile Expired
<191>150938: Jan 19 02:31:52.633 CET: RSTP(1): updt roles, received superior bpdu on Po1
<191>150939: Jan 19 02:31:52.633 CET: RSTP(1): synced Po1
<191>150940: Jan 19 02:31:52.641 CET: RSTP(1): transmitting an agreement on Po1 as a response to a proposal
<191>150941: Jan 19 02:31:52.834 CET: RSTP(1): updt roles, received superior bpdu on Po1
<191>150942: Jan 19 02:31:52.834 CET: RSTP(1): synced Po1
<191>150943: Jan 19 02:31:52.843 CET: RSTP(1): transmitting an agreement on Po1 as a response to a proposal
<191>150944: Jan 19 02:31:56.752 CET: RSTP(1011): Po1 rcvd info expired
<191>150945: Jan 19 02:31:56.752 CET: RSTP(1011): updt roles, information on root port Po1 expired
<191>150946: Jan 19 02:31:56.752 CET: RSTP(1011): we become the root bridge
<191>150947: Jan 19 02:31:56.752 CET: RSTP(1011): Po1 is now designated
<191>150948: Jan 19 02:31:56.760 CET: RSTP(1011): updt roles, received superior bpdu on Po1
<191>150949: Jan 19 02:31:56.760 CET: RSTP(1011): Po1 is now root port
<191>150950: Jan 19 02:31:57.633 CET: RSTP(31): Po1 rcvd info expired
<191>150951: Jan 19 02:31:57.633 CET: RSTP(31): updt roles, information on root port Po1 expired
<191>150952: Jan 19 02:31:57.633 CET: RSTP(31): we become the root bridge
<191>150953: Jan 19 02:31:57.633 CET: RSTP(31): Po1 is now designated
<191>150954: Jan 19 02:31:57.641 CET: RSTP(1010): Po1 rcvd info expired
<191>150955: Jan 19 02:31:57.641 CET: RSTP(1010): updt roles, information on root port Po1 expired
<191>150956: Jan 19 02:31:57.641 CET: RSTP(1010): we become the root bridge
<191>150957: Jan 19 02:31:57.641 CET: RSTP(1010): Po1 is now designated
<191>150958: Jan 19 02:31:57.641 CET: RSTP(1020): Po1 rcvd info expired
<191>150959: Jan 19 02:31:57.641 CET: RSTP(1020): updt roles, information on root port Po1 expired
<191>150960: Jan 19 02:31:57.641 CET: RSTP(1020): we become the root bridge
<191>150961: Jan 19 02:31:57.641 CET: RSTP(1020): Po1 is now designated
<191>150962: Jan 19 02:31:57.641 CET: RSTP(1030): Po1 rcvd info expired
<191>150963: Jan 19 02:31:57.641 CET: RSTP(1030): updt roles, information on root port Po1 expired
<191>150964: Jan 19 02:31:57.641 CET: RSTP(1030): we become the root bridge
<191>150965: Jan 19 02:31:57.641 CET: RSTP(1030): Po1 is now designated
<191>150966: Jan 19 02:31:57.641 CET: RSTP(31): updt roles, received superior bpdu on Po1
<191>150967: Jan 19 02:31:57.641 CET: RSTP(31): Po1 is now root port
<191>150968: Jan 19 02:31:57.658 CET: RSTP(1010): updt roles, received superior bpdu on Po1
<191>150969: Jan 19 02:31:57.658 CET: RSTP(1010): Po1 is now root port
<191>150970: Jan 19 02:31:57.658 CET: RSTP(1020): updt roles, received superior bpdu on Po1
<191>150971: Jan 19 02:31:57.658 CET: RSTP(1020): Po1 is now root port
<191>150972: Jan 19 02:31:57.658 CET: RSTP(1010): updt roles, received superior bpdu on Po1
<191>150973: Jan 19 02:31:57.658 CET: RSTP(1030): updt roles, received superior bpdu on Po1
<191>150974: Jan 19 02:31:57.658 CET: RSTP(1030): Po1 is now root port
<191>150975: Jan 19 02:31:57.675 CET: RSTP(1040): Po1 rcvd info expired
<191>150976: Jan 19 02:31:57.675 CET: RSTP(1040): updt roles, information on root port Po1 expired
<191>150977: Jan 19 02:31:57.675 CET: RSTP(1040): we become the root bridge
lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

I don't really understand what is downstream channels....

peyrache
Respected Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

ethernet port of server side inside HPE Chassis

what is the verion of CBS ?

JY

lozair31
Advisor

Re: LACP randomly fail between hpe5700 and cisco 6509

It's a :12.2(50) version as shown below :

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 24 WS-CBS3032-DEL-F 12.2(50)SE3 CBS31X0-UNIVERSAL-M  

peyrache
Respected Contributor

Re: LACP randomly fail between hpe5700 and cisco 6509

could you update to at least most recent version please ?