|
<< Click to Display Table of Contents >> Navigation: Support > Athena Support > Getting Started with Athena for Clubs > 4. Updating Orion > Troubleshooting Connecting to the Network Manager |
To check the connection status of the Network Manager, from the menu bar click on Athena -> Network Manager Connection Status. Athena will attempt to ping (via ICMP) the hostname or IP of the Network Manager. The ping result will then be displayed, along with the IoT Connection status.
When Orion starts up it attempts to connect to the Network Manager. On boot up if you receive a message similar to "nnnnnn-CORE-001 is not a known hostname", (where nnnnnn is your Orion Account Number) this message is coming from the Windows Operating System. It means that the network Windows is currently on, the Network Manager is unknown.
1.Check that the Network Manager is turned on.
2.Check that the Windows desktop running Orion is connected to the same isolated Athena network as the Network Manager.
3.Check that your Windows desktop can ping the Network Manager's hostname. See Athena's Network Requirements for information on how the Athena network needs to be configured. Use the available Network Port Tester, located under Athena > Networking Help, to ping the device. Alternatively, from the Windows PowerShell run:
ping {OrionAccountNumber}-CORE-001
4.Check the Customer Information Sheet for the IP address that were assigned to the Network Manager, or if you configured your own Athena Network check with your Network Administrator to learn the IP addresses. Attempt to ping these addresses as well.
When Orion starts up it attempts to connect to the Network Manager. On boot up if you receive the message, "Can not initialize IoT Client: Exception connecting to the broker", this message means Orion can not connect to it ("IoT Client" and "broker" are both terms for the Network Manager). Follow the guide below to troubleshoot your connection.
1.Test if the Targets and Monitors can connect. If they can this means the Network Manager is up and running correctly. If the Targets and Monitors can not connect check:
a.Is the Network Manager on?
b.Is the Network Manager connected on your ranges isolated Athena network? See Network Manager Setup for more information.
c.Does the Network Manager have a static IP address, or did that address recently change? Did you give Scopos that IP address? This is necessary because the static IP is part of your ranges configuration that has to be pushed down to the Network Manager. See Network Manager Setup for more information.
2.Check that the Windows desktop running Orion is connected to the same isolated Athena network as the Network Manager.
3.Check the RangeConfiguration-A.json file in the My Matches/Athena directory. Under the Network Manager section does the CoreStateAddress and IoTAddress values both read {OrionAccountNumber}-CORE-001. Where OrionAcccount Number is your 6 digit Orion account number. For example "001234-CORE-001".
4.Check that your Windows desktop can ping the Network Manager's hostname. See Athena's Network Requirements for information on how the Athena network needs to be configured. Use the available Network Port Tester, located under Athena > Networking Help, to ping the device. Alternatively, from the Windows PowerShell run:
ping {OrionAccountNumber}-CORE-001
5.Check that the system clock and timezone on your Windows machine is correct. It should be set to sync automatically.
The following Windows command may be used to check the clock synchronization between your Windows computer and the Network Manger. It must be run from Windows Power Shell. Expected time differences will be about .1s or less.
w32tm /stripchart /computer:[hostname of Network Manager] /dataonly /samples:3
6.Check that the system clock and timezone on the Network Manager is correct. It should be set to synchronize with NTP servers on the Internet.
7.Did you import the Athena group's Certificate Authority into Windows. See How to import Root CA for more information.
See Also