STM SatLink VSAT - Page 177

SatLink VSAT User Guide
Publication no. 101557
Rev 14.1.1-2
Copyright 2006-2012 – STM Group, Inc.
Page 176 (182)
Event
Severity
User action required
Comment
DLCP clear all
dynamic routes and
entries
Normal
None.
The VSAT has closed all dynamic links
and deleted all dynamic routes. This
happens when the SatLink VSAT logs on /
off from the Mesh Network.
DLCP clear all session
data and logon
Normal
None.
The VSAT has closed all dynamic links
and deleted all dynamic routes. The VSAT
tries to log on to the Mesh Controller.
DLCP max number of
connections reached
Normal
None.
The VSAT has reached the maximum
number of licensed connections. New
connections are discarded.
DLCP max pending
request reached, force
DLCP re-logon
Major
None.
The VSAT has too many pending requests
waiting for response from the Mesh
controller. The VSAT logs off from Mesh
Controller and attempts to log on again.
BRX HW initialization
failed
Critical
None.
The VSAT has failed to initialize the burst
receiver for mesh communication. Contact
you Hub operator, mesh return carrier
configuration shall be verified.
Mesh synchronization
Normal
None.
This event is logged when the VSAT
achieves synchronization on the Mesh
carrier.
Mesh synchronization
lost
Major
None.
This event is logged when the STM mesh
capable SatLink VSAT is losing
synchronization on the mesh carriers. The
VSAT will automatically logoff from the
Star Network and re-logon to re-establish
Mesh synchronization.
TCP module detected
high packet loss on
FWD link
Major
None
This event is generated when a lot of DUP
ACKs are detected on the Satellite
Network. This is an indication that there is
loss on the Satellite Network. This will
reset the PEP/TCP connections for which
the DUP ACK count is high.