STM SatLink VSAT - Page 171

SatLink VSAT User Guide
Publication no. 101557
Rev 14.1.1-2
Copyright 2006-2012 – STM Group, Inc.
Page 170 (182)
Event
Severity
User action required
Comment
GW Busy
Major
None
The Hub does not allow the VSAT to log
on. After a timer has expired the VSAT
will retry logging on to the Hub. If the
problem persists, please contact the Hub
operator.
Logon denied
Critical
Call DVB-RCS
Hub operator
The VSAT is not allowed to log on to the
Hub.
GW initiated logoff
Major
None
The Hub operator has forced the VSAT to
logoff.
Fine Sync failure
Major
None
The VSAT was not able to enter the fine
synchronization state when trying to log
on. After a timer has expired the VSAT
will retry logging on to the Hub.
ODU power on failure
Critical
Check that cable to
ODU is connected
and that the VSAT
is configured for the
correct ODU (type
CLI command odu
show)
The VSAT is not able to establish DiSEqC
communication with the ODU. Possible
causes may be:
- Cable to ODU not connected
- IDU not configured for correct ODU
- The ODU is defect and must be
repaired
Logon successful
Normal
None
The VSAT succeeded to log on to the
Hub.
Terminal Logoff
Normal
None
This event is logged after a user initiated
logoff.
Entering hold state
Major
None
The Hub operator has put the VSAT in
Hold-state. When the VSAT is in the
Hold-state it is not allowed to try to log on
to the Hub. To get an explanation of why
the VSAT has been put in Hold-state
please contact the Hub operator.
Leaving hold state
Normal
None
The VSAT is again allowed to log on to
the Hub.
Unit has restarted after
power off
Major
None
Normal message when unit is powered on.
Unit has restarted
Major
Check log with CLI
command
log show -file
If the event happens multiple times
without any explanation please contact the
Hub Operator and provide printout of the
CLI command log show –file.
Restart cmd from local
or remote operator
Major
None
Unit has been restarted by the operator
from the hub or locally.
Automatic Restart
Critical
None
The VSAT was forced to restart due to
following possible reasons, included in the
log:
 Forward Link search has timed
out
 VSAT is unable to allocate
memory