Cloud Managed Networks

I am working on a pilot project to deploy a wireless setup across two geographical regions and each region having multiple sites. Reason for the multiple region is a multiple clearpass on prem setup and sites will be pointed to the nearest clearpass. Once the concept of how to configure all of this is complete, we have many sites we will need to convert from campus mode to Aruba Central.

So in Aruba Central, I am trying to understand the relationship between groups and sites and how to pre-configure for things like the virtual controller at each site. I currently have a group configured and two sites under it. I have 2 AP's up and configured to one of the sites and the VC name for that site was something like setmeupaf34ee which I am guessing is a default name which was populated when the AP's attached to the site. I have renamed the VC to something more recognizable and it is working.

So two issues I am not understanding here.

1. How does one pre-configure a site with AP's and setup the VC name with all the correct info like the VC IP for that site. I see no way of doing that for my second site I have yet to deploy.
2. Based off the above, it totally confuses me that the VC configs appear to be at the group level and not the site level. For someone like me who is very structured oriented, this makes no sense.
3. Oh, and I do have a third question. From a standpoint where I am deploying a new Aruba Central connected site, we need to roll this out with IPv6 only for the management portion of the design. Is this even possible as it appears to me that IPv6 for management is off by default. The basic design will be a vlan for management, and two additional vlan's each supporting a WLAN with the network connection being a trunk.

Apologies for basic questions. I have tried to find some guides or tutorials for design and deployment, but really haven't found anything that is clear on any of this.. 

Hi.

You first need to grasp the concept of sites and groups in Central. This is nicely explained in help pages and documentation. Also some basic trainings and videos about Central are of great help here.

In short:

1. Group is configuration entity. You add devices with similar configuration in a group. Then you are able to manage configuration of al devices in the same group at once.
2. Site is a geographical concept. You move devices into the site based on their location. There is no configuration for devices from site perspective. Devices on site can belong to different groups based on required device configuration.

Device can be a member of one group and can be located on one site. Devices from different groups can be located in the same site. This concept allows you to change configuration on multiple sites by changing the group configuration.

I would really suggest that you look some of the youtube videos on Central on Airheads Broadcasting Channel. It will become much more clear why the concept is like this.

Best, Gorazd

I am working on a pilot project to deploy a wireless setup across two geographical regions and each region having multiple sites. Reason for the multiple region is a multiple clearpass on prem setup and sites will be pointed to the nearest clearpass. Once the concept of how to configure all of this is complete, we have many sites we will need to convert from campus mode to Aruba Central.

So in Aruba Central, I am trying to understand the relationship between groups and sites and how to pre-configure for things like the virtual controller at each site. I currently have a group configured and two sites under it. I have 2 AP's up and configured to one of the sites and the VC name for that site was something like setmeupaf34ee which I am guessing is a default name which was populated when the AP's attached to the site. I have renamed the VC to something more recognizable and it is working.

So two issues I am not understanding here.

1. How does one pre-configure a site with AP's and setup the VC name with all the correct info like the VC IP for that site. I see no way of doing that for my second site I have yet to deploy.
2. Based off the above, it totally confuses me that the VC configs appear to be at the group level and not the site level. For someone like me who is very structured oriented, this makes no sense.
3. Oh, and I do have a third question. From a standpoint where I am deploying a new Aruba Central connected site, we need to roll this out with IPv6 only for the management portion of the design. Is this even possible as it appears to me that IPv6 for management is off by default. The basic design will be a vlan for management, and two additional vlan's each supporting a WLAN with the network connection being a trunk.

Apologies for basic questions. I have tried to find some guides or tutorials for design and deployment, but really haven't found anything that is clear on any of this.. 

Gorazd,

Thanks for the info. I will try and find the videos and work through them.

With the info provided though, I now get that the group is a configuration item. But looking through group settings, I still cannot figure out how to pre define a VC. The only way I have been able to set something like the VC IP, is to wait until an AP has actually connected to central and I get the default VC config for that site. Then it shows up so I can configure it. Is there not any way to config a VC name and attach to a site before the site is online?

Hi.

You first need to grasp the concept of sites and groups in Central. This is nicely explained in help pages and documentation. Also some basic trainings and videos about Central are of great help here.

In short:

1. Group is configuration entity. You add devices with similar configuration in a group. Then you are able to manage configuration of al devices in the same group at once.
2. Site is a geographical concept. You move devices into the site based on their location. There is no configuration for devices from site perspective. Devices on site can belong to different groups based on required device configuration.

Device can be a member of one group and can be located on one site. Devices from different groups can be located in the same site. This concept allows you to change configuration on multiple sites by changing the group configuration.

I would really suggest that you look some of the youtube videos on Central on Airheads Broadcasting Channel. It will become much more clear why the concept is like this.

Best, Gorazd

I am working on a pilot project to deploy a wireless setup across two geographical regions and each region having multiple sites. Reason for the multiple region is a multiple clearpass on prem setup and sites will be pointed to the nearest clearpass. Once the concept of how to configure all of this is complete, we have many sites we will need to convert from campus mode to Aruba Central.

So in Aruba Central, I am trying to understand the relationship between groups and sites and how to pre-configure for things like the virtual controller at each site. I currently have a group configured and two sites under it. I have 2 AP's up and configured to one of the sites and the VC name for that site was something like setmeupaf34ee which I am guessing is a default name which was populated when the AP's attached to the site. I have renamed the VC to something more recognizable and it is working.

So two issues I am not understanding here.

1. How does one pre-configure a site with AP's and setup the VC name with all the correct info like the VC IP for that site. I see no way of doing that for my second site I have yet to deploy.
2. Based off the above, it totally confuses me that the VC configs appear to be at the group level and not the site level. For someone like me who is very structured oriented, this makes no sense.
3. Oh, and I do have a third question. From a standpoint where I am deploying a new Aruba Central connected site, we need to roll this out with IPv6 only for the management portion of the design. Is this even possible as it appears to me that IPv6 for management is off by default. The basic design will be a vlan for management, and two additional vlan's each supporting a WLAN with the network connection being a trunk.

Apologies for basic questions. I have tried to find some guides or tutorials for design and deployment, but really haven't found anything that is clear on any of this..