Wireless Access

Hi, I am trying to deploy a Mesh network using Aruba 365s.  I have been able to get the Mesh to work using a mesh profile assigned to an AP-group.

I have an AP that requires slightly different configuration than the majority of the Mesh APs.  I am using bridge mode in the wried-ap-profile with TRUNK set for the AP-group, this single AP needs to use Access port instead.

The AP is assigned to the AP-group and works using the groups configuration.  I thought I could override the AP-group configuration by assigning a different wired-ap profile directly to the AP but it doesn't appear to work, it just uses the AP-group mesh configuration.

Does anyone have any experience of this? Is this the correct method or do I have to assigne all Mesh configuration profiles to the AP directly?

Regards

Dale Shaw

Attachment(s)

Mesh AP config.txt   6 KB 1 version

You can either create a separate group for the mesh point and create the config there, or you can apply at the CLI as an ap-specific command (we don't have ap-specific commands supported in the GUI yet). Just verify that you've applied the AP-specific command and that the config works on the bench before installation.

Thank you for your advice Jerrod.  

After further investigation I have identified that the AP specific configuration was working.  

Spanning tree on the switchport was disabling the port becasue it was recieving BPDUs identified as a trunk port, even though it is configured as an access port on the wired-ap-profile.

Jul 29 10:08:26.753: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk GigabitEthernet0/1 VLAN56.
Jul 29 10:08:26.753: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking GigabitEthernet0/1 on VLAN0056. Inconsistent port type.

I disabled spanning tree on the switch and it worked.  I'm not sure why this is or if it is supposed to behave like this.

Regards

Dale Shaw

Mesh is carrying all switch traffic, if the switches trigger on BPDU, you can disable the remote switch from sending any BPDUs or disable BPDUguard.