The IoT Gateway's IP address depends your network. In general, the IoT Gateway will take the IP address that is given by your network.
Some networks are configured to dynamically allocate IP addresses to devices that come onto the local network. Other networks are more restrictive and may require further information about the Gateway.
In the case that your network uses DNS to dynamically allocate IP addresses, an IP address will be assigned to the Gateway upon initial setup.
In this case, you will be able to see the IP in your Tulip account after selecting the Gateway on the Stations page:
If your network requires more specific Gateway information, each Gateway will appear on your network with their hostname corresponding to the Gateway's serial number. For instance, the Gateway with a serial number of GTW-04-7C672D2F will have a corresponding hostname of "GTW-04-7C672D2F" that should appear on your network with other device information such as MAC address.
The hostname or MAC address can be used to allow the device onto the network or to assign a static IP for the Gateway.
There are two typical cases where the Gateway will not be given an IP address. When performing the initial Gateway authentication to your Tulip account, if the Gateway is not able to get an IP address you will not be able to proceed with setup and you will see the following error on the first step of setup:
In this case you should confer with your IT department to setup a hostname whitelist or enable dynamic DNS for the network. For your IT department to create a hostname whitelist, all IoT Gateway hostnames start with "GTW-" prefix. Your IT department can use that as a means of filtering hostnames.
A second consideration is when you have already successfully set up an IoT Gateway on your network and then the Gateway is no longer "connected" to your Tulip account.
In this case, if you go to the Stations tab in your Tulip account, the gateway icon will appear similar to the following image:
Where the red icon indicates that the Gateway is offline, i.e. not connected. In this case you should do the following:
- Ensure that the ethernet cable is securely attached.
- Ensure that the Gateway is connected to a valid network.
- Confer with your IT department to see if there have been rule changes that may have excluded your Gateway. An example is that the IT department stopped dynamically issuing IPs, in which case they will need to add the Tulip Gateway hostnames to their hostname whitelist.