STM SatLink VSAT - Page 167

SatLink VSAT User Guide
Publication no. 101557
Rev 14.1.1-2
Copyright 2006-2012 – STM Group, Inc.
Page 166 (182)
Operator for assistance.
9.
NIT not received. The RCST cannot find a
valid Network Information Table.
Check that NIT is not missing and the linkage
descriptor of type 7 (RCS Map Service) is also
available. Without this descriptor, the RCST can
not locate the FLS which holds the description of
the Return Link service (i.e., the RCS Map table).
10.
Rx tuning failed for RMT TS (from NIT)
The secondary transponder signaled from the
Hub cannot be found.
Possible configuration error at Hub, or temporary
outage. Please contact Hub Operator for
assistance.
11.
PAT not received on RMT TS.
Please contact Hub Operator for assistance.
12.
PMT not received on RMT TS.
Please contact Hub Operator for assistance.
13.
RMT not received. The RCST cannot find a
valid RCS Map Table.
This is probably due to the RMT missing, or due
to a missing linkage descriptor of type 129 (RCS
FLS Service) with an appropriate population ID.
Please contact Hub Operator for assistance.
14.
Rx tuning failed for DVB-RCS FLS TS
(from RMT).
Please contact Hub Operator for assistance.
15.
PAT not received on RMT TS.
Please contact Hub Operator for assistance.
16.
PMT not received on RMT TS. The RCST
cannot find the Program Map Table for the
RMT Service.
Please contact Hub Operator for assistance.
17.
RMT not received.
This is probably due to the RMT missing, or due
to a missing linkage descriptor of type 129 (RCS
FLS Service) with an appropriate population ID.
If the problem still persists, please contact Hub
Operator for assistance.
18.
Rx tuning failed for DVB-RCS FLS TS
(from RMT).
Please contact Hub Operator for assistance.
19.
PAT not received on DVB-RCS TS. The
RCST cannot find the Program Association
Table on the FLS for the DVB-RCS
signaling tables.
Please contact Hub Operator for assistance.
20.
PMT not received on DVB-RCS TS.
Please contact Hub Operator for assistance.
21.
TIM not received. The Broadcast TIM has
not been received (or misses some critical
parameter).
The broadcast TIM must contain a contention
control and correction control descriptor before
logon can commence. If problem still persists,
please contact Hub Operator for assistance.
22.
Sync Max Tries Exceeded - Fine Sync not
achieved.
Please contact Hub Operator for assistance.
23.
Logon Failed. No response from Hub.
Please contact Hub Operator for assistance.
24.
Logon Denied.
The VSAT is not authorized to log on to the
satellite network. Please contact the Hub
Operator. The VSAT will not attempt additional
logon.
25.
Logon Failed -- Hub busy.
The Hub has insufficient resources to serve the
logon request from the VSAT. The VSAT will,
after a timeout, perform another logon attempt. If
the situation persists there may be something
wrong with the VSAT configuration at the Hub
side. Please contact Hub Operator for assistance.
26.
Hold State.
The VSAT has been put in hold state by the Hub
Operator. Only the Hub Operator can release it
again. Contact the Hub Operator for assistance.