Cloud Managed Networks

Hi all

We are moving an existing on prem controller to Central.

So we already have a gateway and some AP's working and tested with Central

In the old Controller and Clearpass infrastruture,  we have some AP groups , just for separating some SSID's

In Central we are only using one group ( imagine group A) for all AP's and gateway and a switch.

My concerns are from this point on..

Should I create several sites for diferrent locations? with only one group for all AP's and gateway?

and how to have some AP's as we had on on prem,  broadcasting only some of the ssid, not all? ( i only see this in Central doing this setting one by one AP) 

In a few days we will have the secondary controller on another site ( assume that will be also in group A)  , to get all the existing settings for the already migrated gateway correct?

I know that groups in Central are for " same configurations" and sites are for separting only location based.

Hope i made it clear.

Regards

Hi Beconnect,

With Aruba Central AOS10 you will create one AP group when you like all access points in that group get the same configuration.

On device level of each AP you can make exceptions, when some APs have to send other SSIDs or radio settings for example. You can multi select en edit or using  the API interface.

But when you have many exceptoins. It makes more sense to determine in advance which type of locations you have, for example a separate group for high and low density environments or a separate group for outdoor locations with different SSIDs.

For exmaple groups:

AOS10-AP-LT1    (normal campus)

AOS10-AP-LT2    (high density areas)

AOS10-AP-LT3    (small locatiions)

When using branch controller per location be sure that AP and Controller is in the same SITE. Sites are responsible for controller clustering so the AP knowns to which controller it must connect. See also the manual for some variable in this.

------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------

Original Message:
Sent: Jan 04, 2024 06:22 PM
From: beconnect
Subject: Aruba Central groups and sites

Hi all

We are moving an existing on prem controller to Central.

So we already have a gateway and some AP's working and tested with Central

In the old Controller and Clearpass infrastruture,  we have some AP groups , just for separating some SSID's

In Central we are only using one group ( imagine group A) for all AP's and gateway and a switch.

My concerns are from this point on..

Should I create several sites for diferrent locations? with only one group for all AP's and gateway?

and how to have some AP's as we had on on prem,  broadcasting only some of the ssid, not all? ( i only see this in Central doing this setting one by one AP) 

In a few days we will have the secondary controller on another site ( assume that will be also in group A)  , to get all the existing settings for the already migrated gateway correct?

I know that groups in Central are for " same configurations" and sites are for separting only location based.

Hope i made it clear.

Regards

Original Message:
Sent: 1/5/2024 6:11:00 PM
From: mkk
Subject: RE: Aruba Central groups and sites

Hi Beconnect,

With Aruba Central AOS10 you will create one AP group when you like all access points in that group get the same configuration.

On device level of each AP you can make exceptions, when some APs have to send other SSIDs or radio settings for example. You can multi select en edit or using  the API interface.

But when you have many exceptoins. It makes more sense to determine in advance which type of locations you have, for example a separate group for high and low density environments or a separate group for outdoor locations with different SSIDs.

For exmaple groups:

AOS10-AP-LT1    (normal campus)

AOS10-AP-LT2    (high density areas)

AOS10-AP-LT3    (small locatiions)

When using branch controller per location be sure that AP and Controller is in the same SITE. Sites are responsible for controller clustering so the AP knowns to which controller it must connect. See also the manual for some variable in this.

------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own

Original Message:
Sent: Jan 04, 2024 06:22 PM
From: beconnect
Subject: Aruba Central groups and sites

Hi all

We are moving an existing on prem controller to Central.

So we already have a gateway and some AP's working and tested with Central

In the old Controller and Clearpass infrastruture,  we have some AP groups , just for separating some SSID's

In Central we are only using one group ( imagine group A) for all AP's and gateway and a switch.

My concerns are from this point on..

Should I create several sites for diferrent locations? with only one group for all AP's and gateway?

and how to have some AP's as we had on on prem,  broadcasting only some of the ssid, not all? ( i only see this in Central doing this setting one by one AP) 

In a few days we will have the secondary controller on another site ( assume that will be also in group A)  , to get all the existing settings for the already migrated gateway correct?

I know that groups in Central are for " same configurations" and sites are for separting only location based.

Hope i made it clear.

Regards

I would advise to contact Aruba to validate your design because there are some different kind of setups.

• What is the network role for the group of your 7220 gateways  (mobility | Branch | VPN Concentrator)?
• How are the 2 locations between the 7220 connected (l2-stretched or routed)?
• How are the 30 locations connect to the 7220?
• How many ap/clients/devices per location on the 30 sites?

Note that tunneled SSID from a AOS10 Access Point group are only supported on the LAN and not designed for MAN or WAN.

In my Home setup i was able to create a tunnel ssid and connect to a mobility gateway in another site configuration.

Original Message:
Sent: 1/5/2024 6:11:00 PM
From: mkk
Subject: RE: Aruba Central groups and sites

Hi Beconnect,

With Aruba Central AOS10 you will create one AP group when you like all access points in that group get the same configuration.

On device level of each AP you can make exceptions, when some APs have to send other SSIDs or radio settings for example. You can multi select en edit or using  the API interface.

But when you have many exceptoins. It makes more sense to determine in advance which type of locations you have, for example a separate group for high and low density environments or a separate group for outdoor locations with different SSIDs.

For exmaple groups:

AOS10-AP-LT1    (normal campus)

AOS10-AP-LT2    (high density areas)

AOS10-AP-LT3    (small locatiions)

When using branch controller per location be sure that AP and Controller is in the same SITE. Sites are responsible for controller clustering so the AP knowns to which controller it must connect. See also the manual for some variable in this.

------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own

Original Message:
Sent: Jan 04, 2024 06:22 PM
From: beconnect
Subject: Aruba Central groups and sites

Hi all

We are moving an existing on prem controller to Central.

So we already have a gateway and some AP's working and tested with Central

In the old Controller and Clearpass infrastruture,  we have some AP groups , just for separating some SSID's

In Central we are only using one group ( imagine group A) for all AP's and gateway and a switch.

My concerns are from this point on..

Should I create several sites for diferrent locations? with only one group for all AP's and gateway?

and how to have some AP's as we had on on prem,  broadcasting only some of the ssid, not all? ( i only see this in Central doing this setting one by one AP) 

In a few days we will have the secondary controller on another site ( assume that will be also in group A)  , to get all the existing settings for the already migrated gateway correct?

I know that groups in Central are for " same configurations" and sites are for separting only location based.

Hope i made it clear.

Regards

Hi Thanks 

I think we are ok now

We are using only a group and creating some sites to distinguish locations.

If you clone a group its not going to clone all ssid's correct? you should re-configure all again?

Regards

I would advise to contact Aruba to validate your design because there are some different kind of setups.

• What is the network role for the group of your 7220 gateways  (mobility | Branch | VPN Concentrator)?
• How are the 2 locations between the 7220 connected (l2-stretched or routed)?
• How are the 30 locations connect to the 7220?
• How many ap/clients/devices per location on the 30 sites?

Note that tunneled SSID from a AOS10 Access Point group are only supported on the LAN and not designed for MAN or WAN.

In my Home setup i was able to create a tunnel ssid and connect to a mobility gateway in another site configuration.

Original Message:
Sent: 1/5/2024 6:11:00 PM
From: mkk
Subject: RE: Aruba Central groups and sites

Hi Beconnect,

With Aruba Central AOS10 you will create one AP group when you like all access points in that group get the same configuration.

On device level of each AP you can make exceptions, when some APs have to send other SSIDs or radio settings for example. You can multi select en edit or using  the API interface.

But when you have many exceptoins. It makes more sense to determine in advance which type of locations you have, for example a separate group for high and low density environments or a separate group for outdoor locations with different SSIDs.

For exmaple groups:

AOS10-AP-LT1    (normal campus)

AOS10-AP-LT2    (high density areas)

AOS10-AP-LT3    (small locatiions)

When using branch controller per location be sure that AP and Controller is in the same SITE. Sites are responsible for controller clustering so the AP knowns to which controller it must connect. See also the manual for some variable in this.

------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own

Original Message:
Sent: Jan 04, 2024 06:22 PM
From: beconnect
Subject: Aruba Central groups and sites

Hi all

We are moving an existing on prem controller to Central.

So we already have a gateway and some AP's working and tested with Central

In the old Controller and Clearpass infrastruture,  we have some AP groups , just for separating some SSID's

In Central we are only using one group ( imagine group A) for all AP's and gateway and a switch.

My concerns are from this point on..

Should I create several sites for diferrent locations? with only one group for all AP's and gateway?

and how to have some AP's as we had on on prem,  broadcasting only some of the ssid, not all? ( i only see this in Central doing this setting one by one AP) 

In a few days we will have the secondary controller on another site ( assume that will be also in group A)  , to get all the existing settings for the already migrated gateway correct?

I know that groups in Central are for " same configurations" and sites are for separting only location based.

Hope i made it clear.

Regards