This article will show how Nebula devices communicate with Nebula Control Center and which Ports are used [NETCONF Information], Nebula Cloud Control TCP ports, Call home process, what Nebula servers are used for NETCONF, NCC, NTP, Zero Touch Provisioning, USG FLEX service, Monitor service for USG FLEX, also the Access point (AP) onboarding process enhancement for 6.50 and how APs come online in Nebula.
Table of Content
A lot of customer inquiries we receive are regarding connectivity issues between Nebula devices and the Nebula Control Center. In order to shed some light on this topic, we decided to create this knowledge base in order to let you know at least the way these devices intercommunicate with the Cloud.
2) Ports needed for devices to come online in NCC
There are the following ports currently being used for communicating between NCC and the Nebula devices.
- Port 443 and 6667 are used in TCP for Nebula Cloud Management
- Since firmware version 5.50 on the Access points, also port 4335 is being used - as future passes by, eventually implemented onto other units(NETCONF_CALL_HOME)
- Port 123 is used in UDP for Network Time Protocol(NTP).
Ports information can be also obtained on NCC > Help > Firewall Information.
|Nebula Cloud Management (NETCONF)||d.nebula.zyxel.com||220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206||4335 / 6667||TCP|
|Nebula Cloud Management||s.nebula.zyxel.com||Dynamic||443||TCP|
|Network Time Protocol||*.pool.ntp.org||Dynamic||123||UDP|
|Nebula Cloud Management (Zero Touch Provisioning)||d-a.nebula.zyxel.com||Dynamic||443||TCP|
|Nebula Cloud Management (Configure related service for USG FLEX series)||d-cp.nebula.zyxel.com||220.127.116.11, 18.104.22.168||4335||TCP|
|Nebula Cloud Management (Monitor related service for USG FLEX series)||d-mp.nebula.zyxel.com||22.214.171.124, 126.96.36.199, 188.8.131.52||443||TCP|
3) Communication Process (Call Home)
Communication between Nebula devices and NCC is named Call Home and comprised of 4 steps as below:
Get IP address/ DNS Server from local DHCP Server
By default, Nebula devices are DHCP clients. When they are powered on, they will try to get IP address and DNS Server information from the local DHCP Server.
NETCONF over TLS
Next, they will proceed TCP Handshake to Nebula Control Center and then Nebula Control Center will establish TLS (Transport Layer Security) Handshake to the devices. This phase is called NETCONF over TLS
They will be provisioned by Nebula Control Center with NTP setting to synchronize time.
Configure and Monitor
In the last phase, by sending get and edit-config requests from Nebula Control Center to Nebula devices, users can configure settings and monitor the status of the devices on the Nebula Control Center web GUI platform. The above two steps are the Cloud Connection between Nebula devices and Nebula Control Center.
4) AP Onboarding Enhancement (from 6.50)
In the old communication process, the Access point (AP) needed to apply the cloud mode default settings to successfully go online in Nebula. Additional process are then required to reset the device information, which takes about 90 seconds as seen below:
In firmware 6.50 and forward, the AP can now skip the process to show "up to date" status in Nebula much faster. This applies only when the device has:
- Default (factory) setting
- Changed Management IP (Interface) or;
- Admin password
In our internal testing, we can see that the process now takes around 6-8 minutes before the device has gone online and shown "up-to-date":
Do you want to have a look directly at one of our test devices? Have a look here in our virtual Lab: