LACP ifgrp Fails to Negotiate with Aruba CX Switches
Applies to
- ONTAP 9
- Aruba CX 8400 Switches (AOS-CX 10.13.1060)
- Multi-chassis LAG (LACP)
Issue
- After connecting to Aruba CX 8400 switches configured in a VSX pair, the interface group configured with multimode_lacp does not come online.
- The individual member ports are physically up, but the ifgrp shows no active ports and LACP negotiation fails.
EMS log messages:
pvif.lacp.outofsync:alert: ifgrp a0a, port e9a cannot synchronize with the LACP aggregate.pvif.lacp.outofsync:alert: ifgrp a0a, port e9c cannot synchronize with the LACP aggregate.- ifconfig -v shows LAG ID as all zeros, indicating no successful LACP negotiation.
- Aruba switch logs show partner out-of-sync and defaulted state:
LAG127 State change for interface 1/3/6: Actorstate: ALIO, Partnerstate PLIOPartner is out of sync for interface 1/3/6Partner is lost (timed out) for interface 1/3/6. State: DefaultedState->DefaultedState- ONTAP-side traces confirmed LACP PDUs were being sent correctly without VLAN tags at the driver capture level.
- Switch-side traces showed VLAN tag 1 appended to the LACP PDUs. The Aruba switch's native VLAN handling was adding the tag below the ONTAP capture point.
