topic Re: Does the management vlan selection have any impact on cloud management / HiveManager? in Aerohive Migrated Content

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

AnonymousM — Wed, 23 Jan 2019 22:51:13 GMT

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).

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

samantha_lynn — Wed, 23 Jan 2019 22:54:08 GMT

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.

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

AnonymousM — Wed, 23 Jan 2019 23:59:20 GMT

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.

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

samantha_lynn — Thu, 24 Jan 2019 00:05:14 GMT

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.

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

AnonymousM — Thu, 24 Jan 2019 00:22:39 GMT

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.

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

samantha_lynn — Thu, 24 Jan 2019 00:25:09 GMT

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.

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

AnonymousM — Thu, 24 Jan 2019 22:24:06 GMT

Sam, I was planning on running thought the procedure in a lab environment, but that is proving to be a little more difficult than expected. What I wanted to prove out is that if I leave MGT Interface VLAN to 1 and change vlan 1 to no ipaddress, move the existing ipaddress to vlan 20 the AP will still be accessible to cloud management, following the best order stated above. Can you confirm that I will have access to the AP from the cloud if I follow the procedure above?

I can change the MGT Interface VLAN prior to the layer 3 change. Just want to verify your best order.

Thanks

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

samantha_lynn — Thu, 24 Jan 2019 23:14:24 GMT

That should be fine so long as the management VLAN is still active on your backend, the AP wouldn't need to pull client IP addresses from the management network. The AP will still need a DHCP server on the native VLAN so it can pull an IP address too, but that doesn't need to match the management VLAN.

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

AnonymousM — Thu, 24 Jan 2019 23:43:49 GMT

To Sam,

I thought I would try the reply to this email vs. another post. I am not sure if I should open a support case to be more interactive in what I am trying to do with the setup I have.
The network, from end to end, is setup on vlan 1. I am segmenting it per site, off vlan1.
There is no management vlan per se. Do I need to specify a management vlan? (appears so – no disabling that option - which would be nice to have that option) If so it will be the new assigned vlan. In this sites case vlan 20.
Will the VA cloud management and the AP communicate with the management vlan set to vlan 1 if the IP address of the AP is part of vlan 20? This is the question I am grappling with and wanted to just test out.
Do I need to change the management vlan to 20 prior to moving off vlan1? The IP address of the AP will not change.

Thanks

John Krumenacher

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

samantha_lynn — Thu, 24 Jan 2019 23:50:02 GMT

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.