The AP is currently located in our small business facility. We use default DHCP with no special options. All previously connected devices can access the internet normally.
I've set up Alcatel Cirrus and entered our new device with its serial number and MAC address. However, the status of the device is stuck at "waiting for first contact".
I've restarted and even reset the device twice now.
Hi, the "waiting for first contact" while you restarted the AP several times would mean that something is preventing the AP to access internet. can you connect to the AP through ssh (User id : support, Password : aos2016) and type "ocloud_show" to check what's the status on the AP and may be try try to do a nslookup on the activation server ("activation.myovcloud.com") to see if the connectivity is really OK ? generally speaking verify that you have met all of the Network and Device Prerequisites as described in the OV registration section help (NTP server ort port 123 for external NTP, port 443, DNS if using external DNS, etc. note that if you are using a web proxy the DHCP option would have to provide the necessary inputs (URL, port, username, etc.)
(copied from answer 2)
Hi, thank you very much for the suggestions. It turns out that our business router was configured to provide an IP via DHCP Option 138. However, we do not need this option in our facility, nor does the Access Points. We plan on using and configuring it locally, so the Omni Vista registration from our side was seen as mandatory to get this thing going. After disabling DHCP Option 138 and a factory reset of the AP, the AP now boots without the Omni Vista management mode. Local configuration is now possible and already done. (I found out by running wireshark on the router and seeing the AP trying to connect via TCP Port 1883 to the router, which of course is denied) Thank you again for your help.
It turns out that our business router was configured to provide an IP via DHCP Option 138. However, we do not need this option in our facility, nor does the Access Points. We plan on using and configuring it locally, so the Omni Vista registration from our side was seen as mandatory to get this thing going.
After disabling DHCP Option 138 and a factory reset of the AP, the AP now boots without the Omni Vista management mode. Local configuration is now possible and already done. (I found out by running wireshark on the router and seeing the AP trying to connect via TCP Port 1883 to the router, which of course is denied)
Thank you again for your help.