[MUSIC] Okay, so then what about the manager? So Aruba Central introduces a following application, a new one, that helps simplify and automate site installations and device deployments. Site installations and device deployments at customer premises require extensive coordination between the I.T administrator and who's actually doing the installation themselves, who is the installation personnel. So there are multiple sites you can deploy. Businesses may require some time and manual effort to coordinate and manage site installations. In other words, they may not all be done at the same time by the same person. So the installation management service from Aruba simplifies and automates site deployments and helps I.T managers keep track of who's installing what. To access the install manager web application, you log into Central, this is basically what Central looks like here. And in the central UI at the customer level, select the organization. So if we're a Global, that's fine, but you can have sub levels here if you wanted to. And look for this install manager. So once you select the install manager, use the customer configuration site as a base for installation. And they're showing the different site installation names, city, status, and what devices are in there. So this is the site install. Once the site is added, you can click over here on Installers. Now, installers are technicians who are assigned the task of visiting a physical site and installing devices. It's the people that are doing the installation. So the Aruba Installer mobile app helps installers scan devices and take pictures and report the status to IT administrators who are actually doing the configuration. When an installer is added into the install manager, which there's in your installer tab, and you can go and hit Select or type in the name of the first and last code mobile, whatever, and when they're valid, when they're able to add devices. And then you can say which sites that they have access to. So enter the name, phone number to whom you want to assign a site for installing the devices. Specify the time until the installer's profile is valid, and then the technician will automatically be logged out of the Aruba Installer app on a specific date. So you don't have to follow up with them and remove their credentials. From the sites to Manage drop-down, select the sites you want to assign to the installer, and then say it. The install manager application is a web application intended for IT administrators who manage site installation activities. So us as the IT admins will go in here and hit + and actually add these installers in as well. That's what you saw in the previous screen here. And then the Aruba Installer mobile app would be distributed to the installer, we'll see here in just a minute. We can send them a text message. The mobile app allows the installer to scan the device's admin. And, again, they can download this directly from the app or Apple App Store or Google Play Store. To start it, you must download the Installer mobile app, sign up as an installer, and then the administrator can verify the installer registration status on the installer dashboard in the installer manager application in Central. So the Installer dashboard displays the following status, whether the installer has been invited, whether they registered, and whether they've been verified. Invited is that you've sent him an SMS notification and through that SMS, they could click the link and pull the app down. Registered means that they've actually logged in. And verified means the installer has accepted the installation of mine and successfully completed the registration itself. Yeah, so you're looking for that verified. This is what it looks like for them. The Aruba Installer personnel, their mobile app is intended for installation personnel who deploy devices on site. And the mobile app allows the installers scan devices connected to the network. The installer uses this app to scan serial numbers. So it's not a configuration tool, I mean it's very minor configuration, it's just pre-populating these serial numbers by taking pictures of them. So then, how do we obtain access? This is a licensed feature, you're getting a ton of cloud resources where you don't have the hardware scalability on premise, but instead you pushed those capabilities, those services like guest access, the inspection, the policy making, all of that to the cloud with Central. How do we license that effectively? So cloud management, we have two types of keys, the network infrastructure keys and service keys. Network keys are going to be based on the number of devices and how long that you register them, one year, three years, or five years. So for every access point that's an Instant AP or that you want to be managed by Central, you would have a license. For every switch, you would have a license. For every gateway, you would have a license. And gateways are effectively like edge routers that allow you to do software defined networking and really some cool deep packing inspection at your branch sites. So these are extremely useful tools. They are effectively the same hardware that we have for our controllers, but they're designed for WAN access and inspection. Whereas our switches and our access points aren't used to that regard as much. So services are going to be added value. You want to be able to do guest provisioning and registration. You want the guest Wi-Fi service. Or if you want to look at presence analytics and see who's connecting to what, when, and where. You want to be able to do a monitoring of wireless voice over IP or wired voice over IP, and be able to track the call quality, video, and wire calls, then a UCC service. So these are services that can be enabled on your account, just added values. So it's a new key for voice and video, and monitoring health call sessions. These keys give the ability to utilize subscriptions across your devices and services. Whereas adding the device itself, you need the network infrastructure key. Here's an example of some older part numbers. And I should fore-warn you that this is being updated all the time. So you want to check with your local, friendly Aruba count engineer, sales engineer to be able to find out what exactly the deal is and check on updated pricing and all of that. But you can the distinction between device management and service subscriptions here. And again, they're both time based. Here's some ordering information hardware. You have a one year parts and labor that can be extended for ST WAN. Branch and heading gateway subscriptions are 1, 3, 5, 7 or 10 year options are available with software support, and then virtual gateway if you want to run your gateways as just a virtual machine, that's fine too. So ST WAN are gateways, and these are the same model numbers you might recognize from our controllers, where they could be used with a different image than the one that would be used to manage strictly access points themselves. And again, this may change in the near future, so check and see because they're constantly iterating. I would say this is definitely a focus of what Aruba has been working on. Apps for key management, you got the account home, so manage your network subscription and user access. You can log into your account home, global settings and key management to take a look at what keys you have and how many, and you can add new keys here as well. When you purchase the subscription key, you can input this into your activate account or your Central account to be able to add more devices down the road. There's a better description here. And then finally, device subscriptions you can click on the i for more information about this. This allows you to take a look at available services such as device onboarding, management monitoring, and reports. And you can only assign the device subscription to the Aruba Central managed devices. And you can see the devices that have not yet been assigned keys. So you can see which customer, and what serial number, what devices have subscriptions and which ones don't. So a managed service provider is ultimately going to be responsible for assigning key subscription to each customer. So here, they're just adding the available services and which customers those go to. And again, you want to check for any updates on this that you want to add or make available. And then IAP GUI, once you have assigned a subscription key to a device, then you can go to the actual local device here, and Central will control that device. In this example, there's an Instant AP that has no configuration tab, no configuration tab up here, I'm sorry, over here. It's missing, and so the management has been set Aruba Central. If the Instant AP loses access to a Central account for more than 15 minutes, then it will roll up with a full local configuration that you can then manage. So it's not going to log you out. You'll continue to operate, you just won't have the cloud-based features and services offered through the cloud, but you'll still have wireless. So I know that was a lot of information covering some of the keys and licenses and how you do the onboarding of your devices. There's a quick discussion on some troubleshooting tips here where you can go to your IAP access points. And under Support, there's a number of pre-built commands here that you can distribute. And since when you log into one of your access points at a site in the same VLAN, all of the access points will come up, you can target which particular access point you want to run this command on if you need to do some low level troubleshooting. I would recommend calling tax support and making sure that Aruba supports you in this. But if you want to get some hands-on through command line or through the GUI, you can issue these commands and do your own troubleshooting to validate what the activation status is. So you can issue show activate and find the activation status. And here the status, fail-prov-no-shipped, it's an indication that activate does not know about this Instant AP or the IAP may not have Internet access, so check your plug. Show ap debug cloud-server, you can see the cloud config recved is set to FALSE, so it hasn't received a configuration yet. And again, it may be that internet access. If the IAP has internet access, then it's time to verify the activate account. So they can get to activate, but maybe nothing has been serving activate to direct it to Central. So some key little indicators there, show you provisioning, that the active provisioning service has been enabled. And what's the previous one here, show aruba-central. See that you don't have a server URL, so we should have a server URL on there. It could be that activate has no provision rule for the switch. So this is on a 2920 HP switch rather than in Instant AP. And you can do some debugging for Aruba Central zero touch provisioning, or show your logs recursively and see if there's any indication here that might lead you towards a resolution. All right, I think we're going to go ahead and stop there. When we come back in the next video, we'll look at central configuration concepts. So what do we do to actually do some basic config? But hopefully this is kind of explain how you get your infrastructure up and running tied into Central through tools like the cloud-based activate through your VCs on your Instant APs, your switches, or your gateways. Those are the only three devices, and only Aruba devices, that are going to be managed by Central. All right, I'll see you guys back in the next one.
