Vaisala Hydromet Data Collection Platform - Manual (Page 334)

User's Guide ______________________________________________________________________
332 _________________________________________________________________ M210933EN-C
Troubleshooting TCP/IP-Based Telemetry
Typical possibilities for troubleshooting TCP/IP-based telemetry
operation with the QML logger are as follows:
1. Use the warnings command to check for any modem-related
warnings.
2. Use the net warnings command to check for any IP-specific
warnings.
3. Use the ipconfig command to see the current IP configuration in
the QML logger. The command output gives you information on
all open network interfaces and their configuration, such as IP
addresses, gateways, and DNS servers.
4. Use the netif command to see whether the network interface you
are trying to use is open. If required, the interface can be opened
with the command netif open <interface name>.
5. Check that the IP addresses used for the QML logger interfaces are
correct with respect to your overall network configuration.
6. Use the ping command to test the connection to the destination IP
address or host. If the destination cannot be reached, you can test
whether the connection to the gateway works; if it does, the
problem might be in the connection between the gateway and the
destination host.
7. For the FTP and NTP services, use the commands ftp test <server>
and ntp test <server> to check the connection to the server. You
can also use the ping command to check whether the server is
reachable.
8. As applicable in your network, ensure that there are no firewalls
blocking the traffic to/from the QML logger.
NOTE This manual will not attempt to give general guidelines on network
design or troubleshooting issues, such as IP addressing.
Troubleshooting IP networking usually also involves issues not related
to the QML logger or its configuration; this section includes only the
troubleshooting possibilities at the QML logger end.