Followed up with Aruba TAC and found a loop was created when the port-channel was brought online because traffic was routing through different vlan than management. Our configuration includes 3 port-channels between the WLC and MC .
Original Message:
Sent: Jul 11, 2023 11:24 AM
From: Herman Robers
Subject: Aruba 7240XM LACPDU error invalid intIfNum 3
It may be best to go over your configuration and logs with your Aruba partner, or Aruba Support. It's hard for me to make conclusions based on the available information.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 11, 2023 09:58 AM
From: kilbourne.angela
Subject: Aruba 7240XM LACPDU error invalid intIfNum 3
Physical connections appear to be correct and active on both sides
(atomic655-ocsc-wlc01-1) #show lacp sum
LACP 0
LACP Counter Table
------------------
Port PDUTx PDURx MrkTx MrkRx MrkRspTx MrkRspRx ErrPktRx Age Ena Dis
---- ----- ----- ----- ----- -------- -------- -------- --- --- ---
GE 0/0/0 2351 2352 0 0 0 0 0 70431s 1 0
GE 0/0/1 2353 2357 0 0 0 0 0 70428s 1 0
LACP Neighbor Table
-------------------
Port Flags Pri OperKey State Num Dev Id
---- ----- --- ------- ----- --- ------
GE 0/0/0 SA 1 0x25 0x3d 0x25 02:01:00:00:01:00
GE 0/0/1 SA 1 0x25 0x3d 0x40d 02:01:00:00:01:00
LACP Internal Table
-------------------
Port Flags Pri AdminKey OperKey State Num Status
---- ----- --- -------- ------- ----- --- ------
GE 0/0/0 SA 255 0x1 0x1 0x3d 0x1 up
GE 0/0/1 SA 255 0x1 0x1 0x3d 0x2 up
LACP 1
LACP Counter Table
------------------
Port PDUTx PDURx MrkTx MrkRx MrkRspTx MrkRspRx ErrPktRx Age Ena Dis
---- ----- ----- ----- ----- -------- -------- -------- --- --- ---
GE 0/0/2 43 45 0 0 0 0 0 0s 3 3
GE 0/0/3 43 43 0 0 0 0 0 0s 3 3
LACP Neighbor Table
-------------------
Port Flags Pri OperKey State Num Dev Id
---- ----- --- ------- ----- --- ------
GE 0/0/2 SP 0 0x0 0x0 0x0 00:00:00:00:00:00
GE 0/0/3 SP 0 0x0 0x0 0x0 00:00:00:00:00:00
LACP Internal Table
-------------------
Port Flags Pri AdminKey OperKey State Num Status
---- ----- --- -------- ------- ----- --- ------
GE 0/0/2 SA 255 0x2 0x2 0x45 0x3 down
GE 0/0/3 SA 255 0x2 0x2 0x45 0x4 down
LACP 2
LACP Counter Table
------------------
Port PDUTx PDURx MrkTx MrkRx MrkRspTx MrkRspRx ErrPktRx Age Ena Dis
---- ----- ----- ----- ----- -------- -------- -------- --- --- ---
GE 0/0/4 5 7 0 0 0 0 0 0s 0 0
GE 0/0/5 5 5 0 0 0 0 0 0s 0 0
LACP Neighbor Table
-------------------
Port Flags Pri OperKey State Num Dev Id
---- ----- --- ------- ----- --- ------
GE 0/0/4 SP 0 0x0 0x0 0x0 00:00:00:00:00:00
GE 0/0/5 SP 0 0x0 0x0 0x0 00:00:00:00:00:00
LACP Internal Table
-------------------
Port Flags Pri AdminKey OperKey State Num Status
---- ----- --- -------- ------- ----- --- ------
GE 0/0/4 SA 255 0x3 0x3 0x45 0x5 down
GE 0/0/5 SA 255 0x3 0x3 0x45 0x6 down
###
(atomic655-ocsc-mc01-1) *[mynode] # show lacp sum
LACP 0
LACP Counter Table
------------------
Port PDUTx PDURx MrkTx MrkRx MrkRspTx MrkRspRx ErrPktRx Age Ena Dis
---- ----- ----- ----- ----- -------- -------- -------- --- --- ---
GE 0/0/0 2349 2352 0 0 0 0 0 3473s 2 1
GE 0/0/1 2344 2347 0 0 0 0 0 70283s 1 0
LACP Neighbor Table
-------------------
Port Flags Pri OperKey State Num Dev Id
---- ----- --- ------- ----- --- ------
GE 0/0/0 SA 1 0x23 0x3d 0x23 02:01:00:00:01:00
GE 0/0/1 SA 1 0x23 0x3d 0x40b 02:01:00:00:01:00
LACP Internal Table
-------------------
Port Flags Pri AdminKey OperKey State Num Status
---- ----- --- -------- ------- ----- --- ------
GE 0/0/0 SA 255 0x1 0x1 0x3d 0x1 up
GE 0/0/1 SA 255 0x1 0x1 0x3d 0x2 up
Original Message:
Sent: Jul 11, 2023 05:03 AM
From: Herman Robers
Subject: Aruba 7240XM LACPDU error invalid intIfNum 3
Seems to me that a LACP packet is received on the wrong interface. Could it be that you connected the LACP interface to the wrong ports? Or could the LACP mode be wrong?
Note that the 7240XM (or Aruba controllers/gateways in general) starts counting with port 0/0, where the 8325XM starts counting at port 1 (or 0/1 or so).
With LLDP show commands you may be able to see what ports are physically connected where.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 07, 2023 06:52 PM
From: kilbourne.angela
Subject: Aruba 7240XM LACPDU error invalid intIfNum 3
Hello All,
Can anyone give me some insight as to what is happening here?
Jul 7 12:37:03 2023 <vrrp 399816> <4491> <ERRS> |vrrp| gsm_object_lookup failed for potno: 0
Jul 7 12:38:57 2023 <cfgm 399816> <3598> <ERRS> |cfgm| handle_write: State(READY:CONFIG PROPAGATION:CFGID-111:PEND-111:INITCFGID:111) FD=33:Detected no heartbeat response from conductor since (Fri Jul 7 12:36:56 2023 ). Disconnecting
Jul 7 12:39:28 2023 <cfgm 399816> <3598> <ERRS> |cfgm| handle_read: State(READY:CONFIG PROPAGATION:CFGID-111:PEND-111:INITCFGID:0) FD=33:Failure receiving heartbeat response header information Result=-1 Err=Connection timed out
Jul 7 12:39:37 2023 <cfgm 399816> <3598> <ERRS> |cfgm| collect_boc_log BOC disconnect detected for 5 minutes, requesting BOC logs from FPCLI
Jul 7 12:39:58 2023 <cfgm 399816> <3598> <ERRS> |cfgm| handle_read: State(READY:CONFIG PROPAGATION:CFGID-111:PEND-111:INITCFGID:0) FD=33:Failure receiving heartbeat response header information Result=-1 Err=Connection timed out
Jul 7 12:40:58 2023 <cfgm 399816> <3598> <ERRS> |cfgm| handle_read: State(READY:CONFIG PROPAGATION:CFGID-111:PEND-111:INITCFGID:0) FD=33:Failure receiving heartbeat response header information Result=-1 Err=Connection timed out
Jul 7 12:40:58 2023 <cfgm 399816> <3598> <ERRS> |cfgm| cfgm_rollback_timeout: State(UNINITIALIZED:CONFIG PROPAGATION:CFGID-111:PEND-111:INITCFGID:0) FD=-1:Rollback to id 101, with state CONFIG ROLLBACK
Jul 7 12:40:59 2023 <vrrp 399816> <4491> <ERRS> |vrrp| gsm_object_lookup failed for potno: 0
Jul 7 12:41:01 2023 <lagm 243000> <3636> <ERRS> |lagm| LACP: LACPDU received on invalid intIfNum 4
Jul 7 12:41:07 2023 <cfgm 399816> <3598> <ERRS> |cfgm| cfgm_rollback_is_bad_config: State(READY:CONFIG ROLLBACK:CFGID-101:PEND-101:INITCFGID:0) FD=33:Rollback config id 111 as bad
Jul 7 12:41:09 2023 <cluster_mgr 352302> <5509> <ERRS> |cluster_mgr| cluster_proc_dds_peer_channel_add_event, peer_index for peer 10.120.0.20 is 0!
Jul 7 12:41:17 2023 <cfgm 399816> <3598> <ERRS> |cfgm| cfgm_rollback_is_bad_config: State(READY:CONFIG ROLLBACK:CFGID-101:PEND-101:INITCFGID:0) FD=33:Rollback config id 111 as bad
Jul 7 12:41:34 2023 <lagm 243000> <3636> <ERRS> |lagm| LACP: LACPDU received on invalid intIfNum 4
Jul 7 12:41:37 2023 <cfgm 399816> <3598> <ERRS> |cfgm| cfgm_rollback_is_bad_config: State(READY:CONFIG ROLLBACK:CFGID-101:PEND-101:INITCFGID:0) FD=33:Rollback config id 111 as bad
Jul 7 12:42:04 2023 <lagm 243000> <3636> <ERRS> |lagm| LACP: LACPDU received on invalid intIfNum 4
Jul 7 12:42:07 2023 <cfgm 399816> <3598> <ERRS> |cfgm| cfgm_rollback_is_bad_config: State(READY:CONFIG ROLLBACK:CFGID-101:PEND-101:INITCFGID:0) FD=33:Rollback config id 111 as bad
When enabling LACP the port-channel comes up on both sides between wlc 8325XM running vsx and MM-HW-5K mobility controller but the wireless controller gets stuck during propagation and attempts roll back.
We have another port-channel that is setup identically and is not producing this behavior
Thanks