Important Points to Remember
n In the upstream direction when the AP transmits GRE frames to the switch, the bonding driver must be in
active-active mode and not in the default active-standby mode to allow link aggregation.
n If an AP’s uplink access switch ports are configured in static port-channel mode, then the AP will set the
Ethernet bonding mode to static port-channel (xor mode) only if gre-striping-ip is configured. If gre-
striping-ip is not configured, then the AP goes back to active-standby mode. In this scenario, the AP may
go down depending on the behavior of the upstream switch.
n If an AP’s uplink access switch ports are configured in dynamic LACP mode, the AP detects LACP-PDUs and
automatically sets the Ethernet bonding mode to LACP. If gre-striping-ip is not configured, then the AP’s
Ethernet bonding mode will continue to be in LACP mode, but the AP will send GRE traffic only through one
Ethernet port.
n In OAW-AP324/OAW-AP325 access points, if AP uplink packet capture is taken, the downstream traffic will
have sequence number in GRE header. Wireshark Aruba wlan decoder will not be able to decode these
packets correctly since it looks for known Aruba GRE tunnel IDs.
n Ensure that the gre-striping-ip is unique and not used by any other host on the subnet.
n LACP support is limited to a use case where Enet 0 and Enet 1 ports of the AP are connected to a switch, and
LACP is enabled on the two corresponding switch ports.
n The port priority is not applicable to the AP as both ports need to be used. This value is always set to the
maximum numerical priority(0xFF), which is the lowest priority.
n The system priority is not configurable. It is set to the maximum numerical value (0xFFFF), which is the
lowest priority. This leaves control of the aggregate to the upstream switch.
n The timeout value is not configurable.
n The key is not configurable and the default key value is 1.
n LACP cannot be enabled if wired AP functionality is enabled on the second port. You cannot enable LACP if
the Enet 1 port is shutdown.
Troubleshooting Link Aggregation
The following show commands in the CLI can be used to troubleshoot Link Aggregation on OAW-AP220 Series ,
OAW-AP270 Series, and OAW-AP320 Series access points:
n show ap debug lacp ap-name <ap-name>—Using this command, you can view if LACP is active on an
AP. It displays the number of GRE packets sent and received on the two Ethernet ports. Using this
command with verbose option on OAW-AP324/OAW-AP325 access points displays packet re-ordering
statistics of each wlan client.
n show ap database—Starting with AOS-W 6.4.2, the output of this command includes an LACP Striping
flag (s) to indicate of the APis configured with a LACP striping IP address,
n show datapath tunnel—Using this command on OAW-AP220 Series/OAW-AP270 Series access points,
you can verify if the 2.4GHz tunnels are anchored on the gre-striping-ip (The GRE IDs for these tunnels are
in a range between 0x8300 and 0x83F0) . On OAW-AP324/OAW-AP325 access points, use the verbose
option to verify that 5GHz tunnels have striping IP set in the column StripIP (The GRE IDs for these tunnels
are in a range between 0x8200 and 0x82F0).
n show datapath station—On OAW-AP324/OAW-AP325 access points, using this command displays the
LACP sequence number sent in the GRE header of the last packet to the client. This information is displayed
under Seq column.
n show ap remote debug anul-sta-entries—On OAW-AP324/OAW-AP325 access points, using this
command displays LAG enabled/disabled per station and data drops due to LAG packet reordering.
n show datapath user—Using this command, you can verify if the gre-striping-ip has an entry with the ‘L’
(local) flag
AOS-W 6.5.3.x | User Guide Access Points | 591
To Next Page
Loading...