Community Feedback

Good Day All,

We recently moved from individual ISP connections to one 1G circuit to fan out to all the locations on our installation. Originally each location had its own VC and we could manage the swarm for each accordingly. Now we have only one VC and if we reboot the swarm we are rebooting 60+ APs. Not the ideal network management we want. What is the best way to separate each building so that we can manage them better? I was looking at Groups but the explanations for them is to group like items for configurations. I did setup a Site (which is pretty cool how it maps it) and added the switch and APs for that building but not sure where to go from there.

For a little more background, we went with Central and Aruba IAPs so we could hit the ground running and we really didn't make many configuration changes from the default.

Any assistance would be greatly appreciated. 

Hey Barry,

Based on my limited knowledge of your environment, I think you are on the right track.

In the current Central architecture you would "Group" together devices of similar configuration

          So if you have IAPs with all the same WLAN and RF configurations, they could go all in the same Group (regardless of their geo location)

Then you could create a "Site" design, such that you could monitor and report on the devices at a particular location. 

It is also worth noting that the Configuration architecture will be changing for the better in the New Central, to allow for more granular level of configuration, while still managing at a high level. 

Good Day All,

We recently moved from individual ISP connections to one 1G circuit to fan out to all the locations on our installation. Originally each location had its own VC and we could manage the swarm for each accordingly. Now we have only one VC and if we reboot the swarm we are rebooting 60+ APs. Not the ideal network management we want. What is the best way to separate each building so that we can manage them better? I was looking at Groups but the explanations for them is to group like items for configurations. I did setup a Site (which is pretty cool how it maps it) and added the switch and APs for that building but not sure where to go from there.

For a little more background, we went with Central and Aruba IAPs so we could hit the ground running and we really didn't make many configuration changes from the default.

Any assistance would be greatly appreciated. 

Hey Zak,

So I set up all my different buildings as sites, all 47. What would be the best way to have a Virtual Controller at each site? Would I just set up a different VLAN for each site? The end goal is to have the ability to reboot the site swarm rather than the entire swarm.

Thanks!

Hey Barry,

Based on my limited knowledge of your environment, I think you are on the right track.

In the current Central architecture you would "Group" together devices of similar configuration

          So if you have IAPs with all the same WLAN and RF configurations, they could go all in the same Group (regardless of their geo location)

Then you could create a "Site" design, such that you could monitor and report on the devices at a particular location. 

It is also worth noting that the Configuration architecture will be changing for the better in the New Central, to allow for more granular level of configuration, while still managing at a high level. 

Good Day All,

We recently moved from individual ISP connections to one 1G circuit to fan out to all the locations on our installation. Originally each location had its own VC and we could manage the swarm for each accordingly. Now we have only one VC and if we reboot the swarm we are rebooting 60+ APs. Not the ideal network management we want. What is the best way to separate each building so that we can manage them better? I was looking at Groups but the explanations for them is to group like items for configurations. I did setup a Site (which is pretty cool how it maps it) and added the switch and APs for that building but not sure where to go from there.

For a little more background, we went with Central and Aruba IAPs so we could hit the ground running and we really didn't make many configuration changes from the default.

Any assistance would be greatly appreciated. 

You are running an 8.x code correct?

Hey Zak,

So I set up all my different buildings as sites, all 47. What would be the best way to have a Virtual Controller at each site? Would I just set up a different VLAN for each site? The end goal is to have the ability to reboot the site swarm rather than the entire swarm.

Thanks!

Hey Barry,

Based on my limited knowledge of your environment, I think you are on the right track.

In the current Central architecture you would "Group" together devices of similar configuration

          So if you have IAPs with all the same WLAN and RF configurations, they could go all in the same Group (regardless of their geo location)

Then you could create a "Site" design, such that you could monitor and report on the devices at a particular location. 

It is also worth noting that the Configuration architecture will be changing for the better in the New Central, to allow for more granular level of configuration, while still managing at a high level. 

Good Day All,

We recently moved from individual ISP connections to one 1G circuit to fan out to all the locations on our installation. Originally each location had its own VC and we could manage the swarm for each accordingly. Now we have only one VC and if we reboot the swarm we are rebooting 60+ APs. Not the ideal network management we want. What is the best way to separate each building so that we can manage them better? I was looking at Groups but the explanations for them is to group like items for configurations. I did setup a Site (which is pretty cool how it maps it) and added the switch and APs for that building but not sure where to go from there.

For a little more background, we went with Central and Aruba IAPs so we could hit the ground running and we really didn't make many configuration changes from the default.

Any assistance would be greatly appreciated. 

Yes, if you are referring to the firmware, we are on 8.11.X on all but two odd ball APs

You are running an 8.x code correct?

Hey Zak,

So I set up all my different buildings as sites, all 47. What would be the best way to have a Virtual Controller at each site? Would I just set up a different VLAN for each site? The end goal is to have the ability to reboot the site swarm rather than the entire swarm.

Thanks!

Hey Barry,

Based on my limited knowledge of your environment, I think you are on the right track.

In the current Central architecture you would "Group" together devices of similar configuration

          So if you have IAPs with all the same WLAN and RF configurations, they could go all in the same Group (regardless of their geo location)

Then you could create a "Site" design, such that you could monitor and report on the devices at a particular location. 

It is also worth noting that the Configuration architecture will be changing for the better in the New Central, to allow for more granular level of configuration, while still managing at a high level. 

Good Day All,

We recently moved from individual ISP connections to one 1G circuit to fan out to all the locations on our installation. Originally each location had its own VC and we could manage the swarm for each accordingly. Now we have only one VC and if we reboot the swarm we are rebooting 60+ APs. Not the ideal network management we want. What is the best way to separate each building so that we can manage them better? I was looking at Groups but the explanations for them is to group like items for configurations. I did setup a Site (which is pretty cool how it maps it) and added the switch and APs for that building but not sure where to go from there.

For a little more background, we went with Central and Aruba IAPs so we could hit the ground running and we really didn't make many configuration changes from the default.

Any assistance would be greatly appreciated.