Product and Software: This article applies to ArubaOS 3.3.2 and later.When configuring a mesh link for bridging, it is important to ensure that VLAN tagging is properly implemented. Proper VLAN tagging includes having the same native VLAN throughout for untagged traffic.
On Aruba controllers, the following profiles are used for configuring bridging across a mesh link:
To be specific, the configuration on an Aruba controller running ArubaOS 3.4.0.x would be as follows:
Wired AP profile
================ap wired-ap-profile "mesh" wired-ap-enable forward-mode bridge switchport mode trunk switchport trunk native vlan 10 switchport trunk allowed vlan 100,200,300 trusted!AP system profile
=================ap system-profile "mesh" native-vlan-id 10!AP group configuration
======================ap-group "mesh" dot11a-radio-profile "mesh" dot11g-radio-profile "mesh" wired-ap-profile "mesh" ap-system-profile "mesh" mesh-cluster-profile "mesh" priority 1!Sample Ethernet configuration for the switch that may be connected to the mesh portal or mesh point
=====================================================================interface fastethernet 2/4 description "fe2/4" trusted switchport mode trunk switchport trunk native vlan 10 switchport trunk allowed vlan 100,200,300!
When the forwarding mode is changed in the wired AP profile, the AP reboots. The AP reboots even after the forwarding mode has been changed after the wired AP profile has been applied the AP group.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.