Nera SatLink 1000, User Manual

Page: 21 / 120

Nera SatLink Terminal User Guide – Revision P
19
To display the available commands within one command group type
? <group>
.
Example:
# ? ip
For detailed help on a command type '? ip <command>'
addroute : ip addroute <destaddr> <netmask> <next hop> <ifnum>
delroute : ip delroute <destaddr> <netmask> <next hop>
qos : sub menu for configuration of Return Link QoS
set : ip set <ifnum> <ipaddr> <mask>
show : ip show [-mcast]
dhcp : sub menu for dhcp
#
To get further help on a specific CLI command type
? <group> <cmd>
.
Example:
# ? ip set
USAGE:
ip set <ifnum> <ipaddr> <mask>
ifnum Interface number (1=LAN, 3=Satellite)
ipaddr IP address for the interface
mask Netmask for the interface
Set the IP address and subnet mask for the specified interface
Example:
ip set 1 10.10.1.1 255.255.255.248 will set the LAN IP address to
10.10.1.1 and the LAN netmask to
255.255.255.248
See also:
ip show, ip addroute, ip delroute
#
5.4 Logging of events
The Nera SatLink Terminal logs certain events to a log stored in RAM. See Appendix J.4 for a list of the
different events and what action that need to be taken for the different events. Use the CLI command
log
show
to show the log from memory.
The events are divided in four different severity levels:
0.
Minor
1. Normal
2. Major
3. Critical
Events with severity level Major will normally cause disruption in the data transfer, while events with
severity level Critical normally will require user intervention in order to restore the data communication
with the DVB-RCS gateway.
To have access to the log of events also after the terminal software has been rebooted, the event above a
specified severity level can be logged to file. Use the CLI command
log file
to enable logging of
events to file, set the minimum severity level of events that shall be logged to file and set the maximum
size for the logfile. The factory default settings are that logging of events with severity level Major and
Critical to file is enabled.