Setting up a static IP for Nebula Switch at the deployment stage

Usually, we recommend having our Nebula switches set to receiving a dynamically assigned IP. However, sometimes the user wants his Nebula Switch using a static IP. This guide will show you how to optimize the setup in order to ensure connectivity to the cloud (NCC).

In general, the followings are the normal steps to configure at the deployment stage:

1. Configure Nebula Switch with static IP via WebGUI or ZON utility.
   
2. Go to Nebula CC, register Nebula Switch and add it to the site (How to register a product in Nebula Control Center )
3. Configure static IP for the Nebula Switch on Nebula CC via NCC > Switch >Monitor > Switch > Click on the Switch you want to configure and proceed as in below screenshot:
   
   

Now, you can let the Nebula Switch connect to the Internet to get online on Nebula CC. The configuration on both the switch locally and in the cloud will match, preventing any mishappenings due to configuration overwriting.

Note: After alignment with the engineering department, the below stated is not current anymore - if the Nebula Control Center (NCC) learns, that the unit in question has an IP addresses with mismatches with the standard static IP address of the device (normally 192.168.1.1), then the NCC will not override the devices' static IP address with information set in the NCC. However, for reference, we will still leave the information stated below within this article. 

Why this procedure / Possible issues / Further information:
The default configuration on Nebula CC is DHCP, so if the Nebula Switch gets online before configuring static IP on Nebula CC first, it will get DHCP configuration from Nebula CC. If there is no DHCP server in the user's network environment, the Nebula Switch will disconnect from Nebula CC.

Although Nebula Switch has a roll back mechanism for management IP, it will still try to use DHCP to get online every 40 seconds. That means the Switch may offline every 40 seconds.

That is why we recommend following the steps above at the deployment stage.
If you really forget to pre-configure static IP on Nebula CC before the Nebula Switch gets online, you may still configure it afterward on Nebula CC to make the configuration on local device consistent with that on Nebula CC, then you may avoid the symptom above.