End-Customer Owns Both Devices and Subscriptions But MSP Manages (Deployment Model 2)
In this deployment model, the account type must be Standard Enterprise Mode. Aruba recommends that you contact your Aruba Central sales representative or the Aruba Central Support team if you are an MSP proposing this model to your end-customer.
In this model, the end-customer owns both the devices and subscriptions, but the MSP manages the end-customer's network. The end-customer can be one of the following:
- An existing Aruba customer who owns Aruba devices, but does not have an Aruba Central account.
- An existing Aruba customer who owns Aruba devices and is managing the network using Aruba Central.
In this model, to manage end-customer-owned devices and subscriptions, the MSP can use the Aruba Central Standard Enterprise mode.
The MSP need not create an Aruba Central account of their own, but can instead add their (MSP) administrator to the end-customer's Aruba Central account. The MSP administrator will only have access to each end-customer account.
Setup and Provisioning
The end-customer purchases the devices and subscriptions. The end-customer contacts the MSP to manage the network. As the devices and subscriptions are owned by the end-customer, the MSP uses the Aruba Central Standard Enterprise mode to set up and provision the tenant account.
The MSP has to request the end-customer to add the MSP administrator to their Aruba Central account. The MSP administrator can use the option to switch between end-customer accounts.
Monitoring and Reporting
As the MSP is not using the MSP mode, there is no single pane view of end-customer accounts managed by the MSP. The MSP has to monitor each end-customer individually. The MSP administrator has to use the Aruba Central Standard Enterprise mode to monitor the end-customer network.
Managing Firmware and Maintenance
The MSP has to use the menu under to view the latest supported firmware version of the device, details of the device, and the option to upgrade the device. The MSP administrator has to manage software upgrades for each end-customer individually.
Example Deployment Scenario
In this scenario, an MSP has to configure Instant APs and manage end-customer networks at two different sites. The following are the site details:
Considering the requirements, each site needs two Instant APs. The only difference between the sites is the VLAN ID.
Deployment Using User-Defined UI Groups
The MSP Managed Service Provider. The Managed Service Provider (MSP) mode is a multi-tenant operational mode that Aruba Central accounts can be converted into, provided these accounts have subscribed to the Aruba Central app. can configure Instant APs at both sites using user-defined UI groups. As the Wi-Fi Wi-Fi is a technology that allows electronic devices to connect to a WLAN network, mainly using the 2.4 GHz and 5 GHz radio bands. Wi-Fi can apply to products that use any 802.11 standard. configuration per site is different, one UI group must be created for each site.
For each site, the tenant account administrator has to do the following:
- Create a new UI group for each site.
- Configure the UI group with Wi-Fi settings specific to each site.
- Map the Instant APs in each site to the respective UI group.
- One user-defined UI group is created for each site.
- For any new site with a different VLAN ID, the tenant account administrator must create a new UI group.
- If a configuration change is required at all sites, the tenant account administrator must manually edit each UI group as each group is independent of the other. For example, to change the Wi-Fi SSID name from to , the tenant account administrator must edit UI group.
Deployment Using Template Groups
The MSP can configure Instant APs at both sites using template groups. The tenant account administrator can create a single template group for both sites with a variable file that differentiates the VLAN setting per device.
Template groups are not supported at the MSP level. However, template groups can be defined and managed at each tenant account individually.
For both sites, the tenant account administrator has to do the following:
- Create one tenant template group.
- Configure the newly created template group by uploading a base configuration with the setting and a variable for the SSID VLAN.
- Upload a variable file with unique entries for each Instant AP. For the Instant APs part of , the VLAN variable value is 20. For the Instant APs part of , the VLAN variable value is 40.
- Map Instant APs to the common template group. and
- One tenant template group is created for both sites.
- For every additional site with a different VLAN ID, the same template group can be used with a modified variable file.
- If a configuration change is required at all sites, the common template group can be updated and pushed to all sites. For example, to change the Wi-Fi SSID name from to , the tenant account administrator can edit the common template group and push the configuration changes to all sites.