The VSAT has sent the maximum allowed
number of synchronization messages to the Hub
without response. This may happen for a number
of reasons. Please check power level, antenna,
etc. If the problem persists, please contact Hub
Operator for assistance.
K.2 Debugging Network Connections
Ping is a useful tool to debug network connections.
A ping test can be done from a PC connected to the Ethernet port of the VSAT (e.g., from Microsoft
command prompt).
Use the following commands:
1. Ping the Ethernet interface IP address of the VSAT (e.g. 10.10.20.1). If not OK please check the
Ethernet cable and the connection to the SatLink VSAT.
For SatLink 1900 and 1901 only: Check that the VSAT‘s Ethernet port is operating in the correct
mode. The switch should be set to HUB for direct PC to VSAT connections using a straight
Ethernet cable.
2. If the Ethernet connection is OK then check the IP configuration and routing table of the PC (e.g.,
type the MS-DOS commands ipconfig and route print) and check the IP configuration of the
VSAT (use the CLI command ip show).
3. If the ping to the SatLink VSAT is successful, try to ping a known Internet address (e.g.
www.google.com). If successful, the connection to the Internet is OK.
If not OK check that the PC DNS IP address is correct. Try also to ping a known IP address on
the Internet (e.g., ping 195.204.181.169).
4. If none of the above solves the problem, the System Operator must be contacted.
The following commands may also be useful:
ping –t <ipaddr> start a continuous ping test towards the specified IP address in order to gather
statistics
use ctrl-break to read statistics during test (This option is not supported by all Windows operating
systems)
use ctrl-c to stop the test
K.3 Manual Software Upgrade or dload Fails
Manual software upgrade or download of file using CLI command dload can fail if there is not
sufficient available memory in the VSAT file system. This can happen if several software images have
been downloaded to the VSAT without deleting the older backup images.