01-31-2018 08:53 AM
In a few days I have to implement the following scenario where I have a network where the management VLAN for IAPs is 800 and is tagged in the core:
For this to work I have to set the uplink management VLAN to 800 for each IAP. I wouldn't like to change the uplink management VLAN of each IAP, leave the default setting where the IAP management traffic will be untagged and which is the Aruba recommendation.
What can I do to not change the uplink management VLAN? Is the only way for this to work to change the uplink management VLAN in each IAP? By the way it will be tedious since I have a lot of IAPs.
The Aruba Instant VRD says "An uplink management VLAN is a “per AP” configuration and you must modify it only in an environment in which you cannot modify the native VLAN of a trunk to be functional."
I guess if a set the native VLAN to 800 on the trunks which connect to the IAPs, this scenario will not work because the native VLAN on the trunk connected to the core is different (VLAN 1). What do you think? Any other solution? Please help.
Many thanks in advance,
Solved! Go to Solution.
02-05-2018 02:39 AM
Set your management VLAN 800 as native/untagged on the switch ports that connect the IAPs.
It is not recommended to change the Management VLAN id in the IAP for the reasons you mention and more. If you need a specific VLAN on your infrastructure (800 in your case) to be the management VLAN for the IAP's, just put that as untagged/native on the IAP uplink ports. The IAP will internally see it as native VLAN and will not have notice of the actual VLAN id, but does not need that either.
Here an example for Aruba switches, where the AP connected to port 1 is assigned VLAN10 for management:
sw-workshop-01# show running-config interface 1 Running configuration: interface 1 tagged vlan 11-14 untagged vlan 10
There is NO management VLAN configuration on the IAP side, leave that option default.
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).