Wireless Access

Occasional Contributor II

Getting ready to move our controller

We have the steps to move our controller to a new location (same vlan different IP) but we're a little confused as to why there is a vlan on our procurve switches called "wireless". At the moment, this vlan only exists on the switches that are in the same building as the controller. All of our other buildings scatterd throughout the northwest do not have this vlan. 


The controller has the following network config:

vlan 4: controller's IP

vlan 10: guest vlan

vlan 85: staff vlan


The controller acts as a DHCP server for the staff and guest. 

Port 1 on the controller is connected to our wireless vlan on our switch and it's in access mode (trusted) with vlan ID 85

Port 2 on the controller is connected to vlan 4 and it's in trunk mode allowing vlan's 4, 10 


My questions is: do we need to configure this "wireless" vlan on the switches in the new location or can we simply change the interface vlan 4 to the new IP address and subnet mask, change the controller's gateway and reload?

Guru Elite

Re: Getting ready to move our controller

Type "show vlan status" on the commandline of the controller.  Those are the only VLANs you would have to account for.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Search Airheads
Showing results for 
Search instead for 
Did you mean: