Wireless Access

Hello airheads community,

I recently became part of the network team where our wireless SME has departed. I have a project which requires that we change the management addresses on several switches hanging off aruba meshed (portal to point) access points. Please pardon my lack of knowledge of aruba.

Currently, it appears the setup is for those switches to have a trunk on the "remote" switch side and then an access on the access switch side.  This has a single vlan that is l2 on the portal side. This is a L2 only vlan that appears to be created to only exist for the APs to build a tunnel (capwap i assume?) to the controller, along with the internal DHCP pool for the AP's. The controller then has a second interface with a default route where it assumingly dumps out the traffic. I can provide more information about the topology if needed.

The problem is i cannot reach my new gateway once the IP is set. I thought this was likely a L2  issue , so i added the vlan to the remote switch and also trunked it in/out of the controller and added it to the controller's vlans. However, i still don't see the the new vlan  on the mac table on the controller's output interface. (show mac address-table int). I also thought this was possibly a allowed vlan on the mesh issue, so  i checked that and it's allowing all. Is there possibly a seperate setting somewhere that allows the vlans on the ethernet interface off the AP or even something else i am overlooking? I can see the other "tunneled" vlans on the controller's output interface, which are allowed in the controller.

Thank you.

What version of AOS are you running?

Hello airheads community,

I recently became part of the network team where our wireless SME has departed. I have a project which requires that we change the management addresses on several switches hanging off aruba meshed (portal to point) access points. Please pardon my lack of knowledge of aruba.

Currently, it appears the setup is for those switches to have a trunk on the "remote" switch side and then an access on the access switch side.  This has a single vlan that is l2 on the portal side. This is a L2 only vlan that appears to be created to only exist for the APs to build a tunnel (capwap i assume?) to the controller, along with the internal DHCP pool for the AP's. The controller then has a second interface with a default route where it assumingly dumps out the traffic. I can provide more information about the topology if needed.

The problem is i cannot reach my new gateway once the IP is set. I thought this was likely a L2  issue , so i added the vlan to the remote switch and also trunked it in/out of the controller and added it to the controller's vlans. However, i still don't see the the new vlan  on the mac table on the controller's output interface. (show mac address-table int). I also thought this was possibly a allowed vlan on the mesh issue, so  i checked that and it's allowing all. Is there possibly a seperate setting somewhere that allows the vlans on the ethernet interface off the AP or even something else i am overlooking? I can see the other "tunneled" vlans on the controller's output interface, which are allowed in the controller.

Thank you.

Hi chulcher,

Model:Aruba7210-US
Version:8.10.0.14-FIPS LSR

Is the model and version of the aruba controller.

What version of AOS are you running?

Hello airheads community,

I recently became part of the network team where our wireless SME has departed. I have a project which requires that we change the management addresses on several switches hanging off aruba meshed (portal to point) access points. Please pardon my lack of knowledge of aruba.

Currently, it appears the setup is for those switches to have a trunk on the "remote" switch side and then an access on the access switch side.  This has a single vlan that is l2 on the portal side. This is a L2 only vlan that appears to be created to only exist for the APs to build a tunnel (capwap i assume?) to the controller, along with the internal DHCP pool for the AP's. The controller then has a second interface with a default route where it assumingly dumps out the traffic. I can provide more information about the topology if needed.

The problem is i cannot reach my new gateway once the IP is set. I thought this was likely a L2  issue , so i added the vlan to the remote switch and also trunked it in/out of the controller and added it to the controller's vlans. However, i still don't see the the new vlan  on the mac table on the controller's output interface. (show mac address-table int). I also thought this was possibly a allowed vlan on the mesh issue, so  i checked that and it's allowing all. Is there possibly a seperate setting somewhere that allows the vlans on the ethernet interface off the AP or even something else i am overlooking? I can see the other "tunneled" vlans on the controller's output interface, which are allowed in the controller.

Thank you.