You need the MAC address to arrange the controller in the configuration hierarchy, as well. If the MD is a virtual controller, you need to use the MAC from the management interface. If the MD is a hardware controller you need to use the MAC from the VLAN interface, which is used to connect to the MM. The “local-peer-mac” is the MAC of the MD. If you need to have a dynamic IP for the MD you can use the MAC for authentication, instead of the IP: (MM) * (config) #local-peer-mac 00:0c:29:35:c2:cf ipsec test123 If you have multiple MM controller, this makes the configuration on all of them. I always create the PSK at the “mm” level. Connect to the MM and create the PSK: (MM) * #cd /mmĮnter Configuration commands, one per line. Therefore you need to make the MM aware of the PSK. The communication between MM and MD is protected with IPSec. I assume, that you have the MM up and running and IP connectivity is possible between the Managed Device (MD) and the MM. This is still possible and much faster than with 6.x. #Aruba wireless controller blacklist mac address gui manual#The first part is about the manual deployment of controllers. Controller Deployment: The Manual Way with PSK Afterwards, I show you how the Zero Touch Provisioning works. Nevertheless, you have the option to deploy the controller the old way. There is no need to configure something on the controller. With ArubaOS 8 you configure everything on the Mobility Master (MM). The fact, that you have to configure stuff like the IP of the local controller, made this impossible. With ArubaOS 6.x it was not possible to have a complete Zero Touch Provisioning process. Controller Deployment is significantly easier with ArubaOS 8 and it is the first time, that we see Zero Touch Provisioning for controllers. In this post, I describe the different ways to deploy a controller with ArubaOS 8.
0 Comments
Leave a Reply. |
AuthorJanet ArchivesCategories |