SatLink VSAT User Guide
Publication no. 101557
Copyright © 2009 – STM Group, Inc.
Page 37 (160)
To display the available commands within one sub-menu type ? <sub-menu>.
Example:
?
? ip
show : ip show [-mcast]
set : ip set <ifnum> {<ipaddr> <mask>}|nonum
addroute : ip addroute <destaddr> <netmask> [<next hop>] [<if>]
delroute : ip delroute <destaddr> [<netmask> [<next hop> [<if>]]]
intf : Interface configuration
gre : GRE configuration
dhcp : DHCP configuration
dns : DNS configuration
nat : NAT configuration
qos : IP QOS configuration
mfc : IP MFC configuration
pep : PEP configuration
udpsend : ip udpsend <options>
udprecv : ip udprecv <options>
To get further help on a specific CLI command type
? <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
8.3 Logging of Events
The SatLink VSAT logs certain events to a log stored in RAM. See Appendix K.5 for a list of the
different events and needed actions. 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 Hub.
To have access to the log of events also after the VSAT 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
To Next Page
Loading...
