Additional checks

The following endpoint availability checks cannot be run from a JACE but if you have a Windows or Linux device attached to the same network as the JACE, or if you are installing a Supervisor this should provide some additional information.

Endpoint availability

Check to see if we can reach web endpoints required for device registration with a browser.

Go to Device Registration Url > ping (i.e. https://devreg.cloud.tridium.com/ping).
This should return a JSON formatted response.
Go to Device Authentication Url > api/authentication/rpkchallenge (i.e. https://gaprodsystemauthentication.sentience.honeywell.com/api/authentication/rpkchallenge).
This should return an XML formatted error message stating that the service does not support the GET method.
Go to Registration Url > api/swagger/public (i.e. https://gaprodregui.sentience.honeywell.com/api/swagger/public).
This should return a JSON formatted response.

If you cannot reach the endpoints you can attempt to see where the problem is with the trace route (tracert on Windows) command, this will show the path through the network that packets are taking.

Figure 15. Endpoint availability for device registration

Entries that get a * represent network messages that timed out. If a host gets three * then it is either down or configured not to respond to ping traffic. Services running in the cloud are usually configured not to respond to ping traffic; however, we can see if our network traffic is making it out of the local network environment.

In the example above note that on lines 17 and 19 we get a response from a server owned by AT&T and then on lines 22 through 25 we are getting responses from Microsoft owned machines. This tells us that we were able to route out of the local environment onto the public internet.

We can also learn other things from these traces, for example if a host has one or two * on its line then that means the host or a host leading up to it is dropping packets. This will degrade performance and could lead to other problems. Also if there is a big jump in response times from one line to the next that could also be indicative of a potential network problem.