cancel
Showing results for 
Search instead for 
Did you mean: 

Does the management vlan selection have any impact on cloud management / HiveManager?

Does the management vlan selection have any impact on cloud management / HiveManager?

AnonymousM
Valued Contributor II

Does the management vlan selection have any impact on cloud management / HiveManager? In other words if changing vlan assignment on a switch port (say vlan1 to vlan20) but keeping the IP network the same (switching the IP on the SVIs from vlan1 to vlan20).

1 ACCEPTED SOLUTION

samantha_lynn
Esteemed Contributor III

You do need to specify a management VLAN, that isn't something we can leave blank. Yes, the AP will still work if you have a different management VLAN and Native VLAN, so long as both are supported through the backend. I'm not sure what you mean by "change the management vlan to 20 prior to moving off vlan1", I would just recommend setting the VLAN you want it to use and then pushing that out to the AP once your backend switches are ready to support the new VLAN.

View solution in original post

9 REPLIES 9

samantha_lynn
Esteemed Contributor III

Yes that is the best order to do this in. The switches should be prepared for the requests when the APs start sending traffic down the new VLAN, otherwise we'll have a break in connectivity while we update.

AnonymousM
Valued Contributor II

All WiFi client traffic is applied to other, various, vlans. The wired network is changing from vlan 1 to 20 (switch port access) and the IP address of the AP is 192.168.1.1 in vlan 1 and will stay 192.168.1.1 when we change vlan 1 to vlan 20. Your recommendation would be to add vlan 20 to the trunk interface on the switch. Next change the MGT Interface VLAN to 20 on the APs via HiveManager NG and deploy.

samantha_lynn
Esteemed Contributor III

The APs have management traffic and client traffic, it doesn't necessarily matter what VLAN you put each kind of traffic on, and these can be the same or different. I would say one of the more common reasons for having client and management traffic on different VLANs is to accommodate the amount of traffic coming through. I would recommend updating the switch ports first so that the traffic doesn't get dropped when you move the APs over to the new VLAN.

AnonymousM
Valued Contributor II

Thank you Sam,

I am trying to understand the value of the AP having a MGT Interface VLAN 1. I have a small site that changed all access ports from vlan 1 to vlan 20. (trunk ports added vlan 20) IP addressing stayed as is. The vlan changed was backed out for fear the APs couldn't be managed by cloud-va.aerohive.com. Looking at this now, I could have changed that setting after the port change in the cloud and deployed it to that sites APs. This is just 1 site that we will be making changes like this. I am trying to determine if I deploy a change like this just prior, or post switch port changes. Thoughts on your experience with this type of change?

Thanks again.

samantha_lynn
Esteemed Contributor III

The settings you change within the HiveManager, including what management VLAN the devices will use, will not affect the HiveManager instance itself. To change HiveManager settings you would need to go in to the :3000 login for the web UI, or the CLI of the HiveManager itself.

 

The only thing to worry about with the VLANs you set for the devices in your configuration is to make sure that the switches the devices are passing traffic through allow all of the VLANs in use.

GTM-P2G8KFN