This document will outline how to configure from Factory Reset a Unifi 48-Port PoE Switch into a AWS Cloud Controller.
1. Reset your Unifi 48-Port PoE Switch by pressing and holding in the Reset button on the right-side of the switch for 5 seconds.
2. Verify that it is connected to the LAN that either your controller is located, or in this case a network that can provide DHCP Services and reach the internet for AWS Controller Registration.
3. Your Device will boot up with an acquired DHCP IP address. You can either find out the IP of the switch using the details provided from your local DHCP Server, or use a tool such as Zenmap or Nmap.
4. Once found, SSH into the device using ubnt/ubnt as the default login and password and perform set-inform http://:8080/inform this will then allow your device to show up within the Unifi Controller for adoption.
Note: You can also cat the /var/log/ on the server to get additional details if it is functioning or failing.
5. Make sure that your device can properly communicate to the AWS Controller (Permissions on the Security Groups associated with the Instance).
6. Once it shows up Pending Adoption, you will need to issue the set-inform command one more time for it then to change from Pending Adoption to Provisioning to Connected.
7. Once it is showing as Connected you can start pushing changes to the device.
1. Reset your Unifi 48-Port PoE Switch by pressing and holding in the Reset button on the right-side of the switch for 5 seconds.
2. Verify that it is connected to the LAN that either your controller is located, or in this case a network that can provide DHCP Services and reach the internet for AWS Controller Registration.
3. Your Device will boot up with an acquired DHCP IP address. You can either find out the IP of the switch using the details provided from your local DHCP Server, or use a tool such as Zenmap or Nmap.
4. Once found, SSH into the device using ubnt/ubnt as the default login and password and perform set-inform http://
Note: You can also cat the /var/log/ on the server to get additional details if it is functioning or failing.
5. Make sure that your device can properly communicate to the AWS Controller (Permissions on the Security Groups associated with the Instance).
6. Once it shows up Pending Adoption, you will need to issue the set-inform command one more time for it then to change from Pending Adoption to Provisioning to Connected.
7. Once it is showing as Connected you can start pushing changes to the device.
Comments
Post a Comment