Manual SL 2900 Lite

8/10/2019 Manual SL 2900 Lite

1/33

SatLink 2900 VSATUser Guide

Revision 15.0.0-2

November 2013

Networks without Barriers


2/33

Table of Contents

INTRODUCTION ........................................................... ................................................................. .................. 21.

1.1

INITIAL CONFIGURATION................................................................ .............................................................. 2

INSTALLATION ............................................................................................................................................... 32.

2.1 SATLINK 2900FRONT AND REAR PANEL.............................................................................................. ....... 32.2 ETHERNET CONNECTION TO A LOCAL AREANETWORK (LAN) .................................................................... 42.3 POWER CONNECTION.................................................................................................................................... 4

ACCESSING THE COMMAND LINE INTERFACE VIA SERIAL CONSOLE PORT .......................... 53.

3.1 CABLE CONNECTION.................................................................................................................. .................. 53.2 CONFIGURATION OF PUTTY TO ACCESS THE CLIVIA SERIAL TO USBCABLE. .................................. .......... 5

USING THE COMMAND LINE INTERFACE OF THE SATLINK VSAT .................. ............................. 74.

4.1

CLIUSER ACCESS RIGHTS.............................................................. ............................................................. 7

4.2

ONLINE HELP............................................................................................................................................... 7

4.3 MOST USED COMMANDS................................................................. .............................................................. 84.4 LINE-UP.......................................................... ................................................................. ........................... 18

EXTENSIONS FOR MOBILE VSATS .......................................................................................................... 205.

5.1 TRANSMIT INHIBIT FUNCTION............................................................................................................ ........ 205.2 GPSINTERFACE......................................................................................................................................... 215.3 RXLOCK SIGNAL...................................................... ................................................................. ................ 22

APPENDIX. TROUBLESHOOTING .................................................................................................... ........ 246.

6.1 Q&A .......................................................................................................................................................... 246.2 DEBUGGINGNETWORK CONNECTIONS................................................................. ...................................... 26

6.3

COLLECTING INFORMATION IF A PROBLEM OCCURS.......................................................................... ........ 266.4 LIST OF EVENTS THAT MAY BE LOGGED.................................................................................................... 27


3/33

SatLink VSAT User Guide

Introduction1.The SatLink 1000, 1910, 2000, and 2900 are the indoor units (IDUs) of the SatLink family of DVB-RCSVSATs. They perform several functions: they are satellite modems (at Layer 1); they handle data link

layer processing (at Layer 2) for both satellite and LAN communications; and they act as IP routers andDHCP servers (at Layer 3). All SatLink IDUs provide an Ethernet 10/100 LAN interface for one or morePCs to engage in two-way communication via a SatLink (or any DVB-RCS compliant) satellite network.In addition, the SatLink 2000 and 2900 support DVB-RCS2, which is the next generation of the originalDVB-RCS open standard, providing linear modulation with 16-state Turbo FEC for QPSK, 8PSK and16QAM, Adaptive Coding and Modulation (ACM) on each return link carrier, new efficient Layer 2encapsulation (Return Link Encapsulation), new SI table formats, enhanced statistics and monitoring,among other improvements and new features.

Figure 1: SatLink 2900 Indoor Unit (IDU)

1.1 Initial Configuration

The VSAT IDU must be configured before it can communicate via the satellite to and from the networkHub. The parameters to be configured are explained in the following sections.

The configuration of the VSAT IDU can be carried out using the following configuration tools:

Web-interface (basic configuration only) Command Line Interface (CLI)

- Via RS232/Terminal emulator (e.g. HyperTerminal)- Telnet

SNMP

In this manual, we are going to focus on the Command Line Interface via Serial cable.


4/33


Installation2.

2.1 SatLink 2900 Front and Rear Panel

Figure 2: SatLink 2900 Front Panel

LED Color: indicates

Power White: lights steadily when power switch is on and unit is powered. Flashes whenloading software.

Error Red: flashes slowly when an error event occurs and lights steadily during reboot.

Satellite Receive White: flashes when the receiver is searching for the carrier.Lights steadily when receiver is on and functioning properly.Flashes when IP packets are received from the Satellite Interface (the Hub).

Transmit White: flashes rapidly when a continuous wave (CW) is transmitted.Lights steadily when the VSAT is logged on to the DVB-RCS Hub.Flashes when IP packets are transmitted to the Satellite Interface (the Hub).

Ethernet Link/Act White: lights steadily when Ethernet connectivity is OK.Flashes slowly when Ethernet packets are transferred via the Ethernet interface.

Table 1: SatLink 2900 Front Panel LEDs

Figure 3: SatLink 2900 Rear Panel

Item Description

On/Off switch Power on (1) or off (0).

Power Connector Standard recessed plug for 110-240VAC power cord.

LAN 1 Ethernet Connector RJ45 connector for IP traffic to connect to a PC, Ethernet switch, IP router etc.10BASE-T, 100BASE-T or 1000BASE-T mode is detected automatically.

LAN 2 Ethernet Connector RJ45 connector for IP traffic to connect to a PC, Ethernet switch, IP router etc.10BASE-T, 100BASE-T or 1000BASE-T mode is detected automatically.

USB Port Not used.

DC Power Connector Connector for alternative 24VDC (19-36VDC) power supply. Typically used whenpowered from solar panels. The right pin of the DC power connector is GND.

COM1 Connector Nine pin connector for connecting CLI interface to a computers DB-9 serialinterface.

Cover for Accessory Card Not used.

J1 Digital I/O used for Mobile applications. Please refer to section5.1.1 for moreinformation.

RX coaxial jack Coaxial 75 F-type jack for the cable to the LNB.

TX coaxial jack Coaxial 75 F-type jack for the cable to the BUC.

Table 2: SatLink 2900 Rear Panel


5/33


2.2 Ethernet connection to a Local Area Network (LAN)

The VSAT IDU may be connected to a single PC or to a network via the RJ-45 Ethernet jack on the backpanel.

Plug one end of the Ethernet cable into the RJ-45 jack on the back panel.

Plug the other end of the Ethernet cable into the RJ-45 jack a Local Area Network (LAN) device,such as an Ethernet hub, switch, or router, according to its manufacturers instructions.

The SatLink VSAT will auto-detect if Ethernet HUB or NODE mode is used and will automatically chosethe correct mode; hence there is no need to use a cross-over Ethernet cable for direct connections to PCs.

All SatLink IDU models have only one Ethernet port, except for the SatLink 2900, which

has two Ethernet ports.The second Ethernet interface (LAN 2) is enabled by default onSatLink 2900 units that have been loaded with SW 14.2.0 or newer in factory.

To enable the second Ethernet interface on SatLink 2900 units shipped with SW 14.1 from

factory, the following procedure has to be used:1. Upgrade the unit to SW 14.2.0 or newer

2. Restore factory default configuration (CLI commands "del config.txt" + "restart")

3. Configure the unit again from scratch

2.3 Power Connection

The SatLink 1910 and 2900 models have internal power supply and consequently are connected directlyto a 110/230 VAC 50/60Hz outlet using a standard 230 VAC power cord.


6/33


Accessing the Command Line Interface via3.Serial Console Port

In some special situations, the Command Line Interface via Telnet may not be accessible or will notoutput the required amount of debug information. Typical examples of such situations are:

The VSAT is configured with an unknown IP address

One needs to enter the boot-loader

Detailed debugging

The Command Line Interface may then be accessed from a local PC connected to the VSATs RS -232interface via a serial cable. HyperTerminal, or any compatible terminal emulation program, is used toaccess the CLI interface via RS-232. A good freeware terminal emulator is Putty. The software can bedownloaded fromhttp://www.putty.org/

3.1 Cable ConnectionTo get access to the command-line interface (CLI) via the serial connection, a serial cable is connectedfrom the SatLink VSAT directly to a COM port on a PC:

Plug the 9-pin connector (DB09) (male) into the rear panel of the SatLink VSAT.

Plug the 9-pin connector (DB09) (female) into a COM port on the PC.You may also use a Serial-to-USB cable if your PC has not a COM port. In this case you may need tocheck in the Windows Control Panel, within the Devices Administration, which COM port is assigned tothe USB connector.

3.2 Configuration of Putty to Access the CLI via Serial to USB Cable.

Start the program Putty. The Putty screen will then start as shown inFigure ,will appear.

Figure 4: Putty Configuration Box
http://www.putty.org/http://www.putty.org/http://www.putty.org/http://www.putty.org/


7/33


Set the Serial line information as the COM your PC has assigned to the USB connection. After, set thespeed as 38400 and the connection type as Serial.

Figure 5: Putty Serial Line Connection Options Box

You may also set the Serial Connection Options as shown in Figure 5

Bits per second: 38400

Data bits: 8

Parity: None

Stop bits: 1

Flow control: none or XON/XOFF

The property sheet will close and communication with the SatLink VSAT may begin.

Note that it may be necessary to press the enter key to display the login prompt.


8/33


Using the Command Line Interface of the SatLink VSAT4.The command line interface can be accessed via either Telnet or the RS-232 port for management of theSatLink VSAT IDU, as well as for showing status and reports.

4.1 CLI User Access Rights

Four levels of CLI user access rights are available for differentiating user privileges:

Level 2: installer

Level 3-5: end users

When shipped from the factory, one user is pre-configured in the SatLink VSAT:

User name Factory default password Privilege level

install dvbrcs 2

If the login prompt is not displayed when accessing the CLI via RS-232, type . The loginprompt, Login:should then be displayed. Then login with the install user:

Login: install

Password: dvbrcs

When the command prompt is displayed, you will now have access to the CLI with privilege level 2.

4.2 Online Help

In the CLI, a list of available commands can be displayed by typing? (question mark and theENTER key). The CLI command groups will then be shown:

Example:# ?

? : ?

device : Device configuration

dvb : DVB interface configuration

eth : Ethernet configuration

ip : IP configuration

log : Event log

misc : Miscellaneous commands

odu : ODU configuration

sw : Software upgrade & licenses

user : User configuration

To display the available commands within one sub-menu, type? .Example:# ? device

snmp : SNMP configuration

manager : Device access management

telnet : Telnet server management

name : device name

contact : device contact

location : device location

show : device show [-dvbs2]


9/33


4.3 Most used commands

4.3.1 IP Configuration

# ip show (Command to show the IP configuration)InterfacesIf IPAddress SubnetMask BroadCastAddr MTU Alias AdminStatus1 192.168.0.1 255.255.255.0 192.168.0.255 1500 eth0 12 N/A N/A N/A 4074 air0 13 192.168.252.0 255.255.255.255 192.168.252.39 4074 dvb0 1

NAPT: Enabled Global Address: 88.84.83.0

DNS Client ConfigurationPrimary DNS Server: 217.15.32.2, Secondary DNS Server: 194.179.1.100

Interface Statistics------------- Input ----------------- ------------- Output ----------------

If UCast NUCast Disc Octets UCast NUCast Disc Octets1 1527375 133105 5464 181175248 2598098 21779 0 25470057852 0 0 0 0 0 0 0 03 2997039 0 63549 2625664770 982588 0 0 124756424IP Receive Deliver Errors Discards Forward Request NoRoute Discards

7267229 81340 153 153 5082048 24114 0 11014

Interface Directed Routing Table

In If Out If

Routing TableDestMask RouteMask NextHop If0.0.0.0 0.0.0.0 0.0.0.0 3

192.168.0.0 255.255.255.0 0.0.0.0 1192.168.252.0 255.255.255.255 0.0.0.0 3

# ? ip set (Command to show how to configure IP within Interfaces)

USAGE:ip set { }|nonum

ifnum Interface number (1=LAN, 3=Satellite)ipaddr IP address for the interfacemask Netmask for the interfacenonum Use nonum instead of ipaddr and mask to remove the IP address

Set the IP address and subnet mask for the specified interface.

If the interface is Virtual-VLAN, then the IP should be from thesubnet of its source VLAN.If the interface is a VLAN, then its corresponding virtual VLANs IPwill be cleared.


10/33


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

# ip nat show (Command to show NAT configuration)NAT Configuration-----------------Network Address Port Translation (NAPT): EnabledGlobal Address TableIf IP Addressdvb0 88.84.83.0NAT Status----------Total Sessions 43662Active Sessions 2

Failed Sessions 0Packet Translations 4117481

# ? ip nat (Command to show how to configure NAT)enable : ip nat enabledisable : ip nat disableglobal : {add|del} []static : { add | del }napt : { add | del [] }show : ip nat show

Example:

#ip nat enable (enable nat)#ip nat global add 88.88.88.88 (assign ip 88.88.88.88 to the global nat)#ip nat static add 88.88.88.88 10.10.10.1 (assign static nat from public ip 88.88.88.88 to private ip10.10.10.1)

# ip pep show (Commnand to show PEP configuration)PEP Status : enabledPEP TCP Mode : Transparent ModePEP TCP Server Address: Not ConfiguredFunc Max Total Current Transp FailedTCP 1024 118880 5 0 0TCP Packet statistics:Rx=4450461, Out of seq=84876, Duplicates=109Tx=3226909, Retransmitted=47272

# ? ip pep (Command to show how to configure PEP)enable : ip pep enable [redirect|trans|httpa]]disable : ip pep disable [httpa]show : ip pep show [-cache]server : ip pep server flush : ip pep flush -cachebypass : ip pep bypass []

dynbypass : ip pep dynbypass


11/33


4.3.2 Forward Link Configuration

# ? dvb rx fwdlink

USAGE:dvb rx fwdlink [ [ [ [ [ [ [ [ [ []]]]]]]]]]dvb rx fwdlink -del|-disable|-enable

idx Table index [0,19]-del Delete table entry-disable Disable table entry-enable Enable table entrypri Forward link search order [0..255] Search starts with lowest number and ends with highest.symbrate Forward link symbolrate [sps]freq Forward link frequency [kHz]

mode Valid modes: [dvbs,dvbs2]popid Population ID

Popid value set to -1 means that the global popid value set using an earlier software version is used.satid Satellite Id selected from following list:

ID NAME BAND SATPOS----------------------------------------------0- Must manually specify and enter 'satpos'.1- SATMEX 5 C,Ku 116.80 W2- SATMEX 6 C,Ku 113.00 W3- GALAXY 28 C,Ku,Ka 89.00 W4- TELSTAR 14 Ku 63.00 W

5- AMAZONAS 2 C,Ku 61.00 W6- AMAZONAS 1 C,Ku 61.00 W7- INTELSAT 14 C,Ku 45.00 W8- NSS-10 C 37.50 W9- TELSTAR 11N Ku 37.50 W10- INTELSAT 903 C,Ku 34.50 W11- HISPASAT 1D Ku 30.00 W12- HISPASAT 1C Ku 30.00 W13- INTELSAT 907 C,Ku 27.50 W14- NSS-7 C,Ku 20.00 W15- INTELSAT 10-02 C,Ku 1.00 W16- EUTELSAT W6 Ku 21.50 E

17- PAKSAT 1 C,Ku 38.00 E18- EXPRESS AM 1 L,C,Ku 40.00 E19- YAHSAT 1A C,Ku 52.50 E20- INTELSAT 706 C,Ku 54.85 E21- EUTELSAT W5 Ku 70.50 E22- NSS-6 Ku,Ka 95.00 E23- ASIASAT 5 C,Ku 100.50 E24- PALAPA C2 C 150.50 E25- GE 23 C,Ku 172.00 E26- SES-4 C,Ku 22.00 W27- ABS-1 C,Ku 75.00 E-----------------------------------------


12/33


satpos Satellite orbital position of sattellite in 1/10 degrees. Range -180.0 .. 180.0 (-1800..1800).Negative values is West

Note: When satid is set to nonzero value then this field is predefined, and it shall not be possibleto change directly. Only if satid is 0, then it is possible to change this value

rxpol Specifying the polarization of the signal, 0 = horizontal, 1 = verticaltxpol Specifying the tx polarization relative to the rx polariztion0 = Cross polarisation (default), 1 = Co-polar

satpolrot Satellite polarisation rotation angle (satellite polarization skew) Range -15.0 . 15.0 (150..150).satincl Maximum inclination of orbit of satellite that the antenna will search for the satellite given in

1/10 of degrees.Examples: 1 which means 0.1 degrees

20 which means 2.0 degreesMaximum allowed value is 150 which means 15.0 deg.This parameter shall be set to 0 for satellites not in inclined orbit.

Configures the DVB receiver table. When starting the receiver the VSAT will search for the FWD link

with lowest priority in the table.If not found, it will continue to the FWD link with second lowest priorityand so on. When successful lock on a FWD link is achieved, the priority of this FWD link will always beset to 0 and the priority of other FWD links increased if necessary to ensure the shortest acquisition timefor future FWD link acquisitions.When configuring a new FWD link the symbrate and freq parameters must always be set. But whenmodifying an existing FWD link table entry, only the index and pri parameters are required.

Example:dvb rx fwdlink 1 1 2700000 1200000 dvbs2 4 20 0 (inserts fwd line 2.7 Msps 1.2 GHz in DVBS2

mode, popid 4 for IS706 with rxpol Horizontal and txpol cross-pol)

# dvb rx show (Command to show RX information)

Satellite (DVB) RX Configuration--------------------------------Auto start : EnabledRX watchdog : 15 minute

Idx Pri SymbRate[Msps] Freq[GHz] Mode PopId Enable0 0 8.500000 11.026918 DVB-S2 2 Yes1 1 12.000000 11.024818 DVB-S2 2 Yes2 2 8.500000 11.026918 DVB-S2 2 Yes

* 8 8 6.500000 11.028118 DVB-S2 2 Yes

Satellite (DVB) Receiver Status--------------------------------Rx State : OnDVB State : Forward link upNetwork : 1326, STM SpainFrequency : 11.028094 GHzSymbol Rate : 6.499999 MspsS2 ModCod : 13Modulation : 8PSK

FEC Code rate : 2/3

Pilot : OnFrame length : Long frameTransmission mode : CCM


13/33


Roll off : 0.20SNR : 14.1 dBInput Power : -36 dBm

4.3.3 Line Up Frequency configuration

# ? dvb tx cwfreq (Command to show how to configure cw freq)USAGE:dvb tx cwfreq freq Return link frequency [kHz]

Set the default CW frequencyExample:dvb tx cwfreq 14100500 (Set the default CW frequency to 14.1005 GHz)

# dvb tx show (Command to show TX information)

Satellite (DVB) TX Configuration--------------------------------Auto start : EnabledIDU output power : -22 dBmEIRP : 44.0 dBWDefault CW Frequency: 14.074206 GHzATM mode : VC-MuxHeader Compression : RTP/UDP/IP/DSM-CCSatellite (DVB) Transmitter Status--------------------------------State : On (TDMA)Timeout : 0 min 0 secIDU Output Power : -18.9 dBmODU Output Power : 35.3 dBmEIRP : 48.6 dBWEb/No : 5.0 dBHeader Compression : RTP/UDP/IP/DSM-CCTiming correction : -70 us (286704 us)Frequency correction: 640 Hz

4.3.4 ODU

# odu show (Command to show ODU information)Antenna

---------------------Type ASC/Andrew/Channel Master Type 123 - 1.2mTx Gain at 14.25 GHz 43.3dBTransmitter (BUC)-------------------------------Type SatLink 4033 (14.0-14.5 GHz)ODU Serial No. 104804040203070700470000ODU HW Version 4.2ODU SW Version 1.3Local oscillator 13.050000 GHz24V DC supply OnTemperature 15 Deg C

Receiver (LNB)----------------------------


14/33


Type SatLink 403x (10.70-12.75 GHz)Local oscillator - High band 10.600000 GHzLocal oscillator - Low band 9.750000 GHzOscillator switching frequency 11.700000 GHz

LO Switching mode 22kHz13/18V DC supply 13V

? odu antenna (Command to show how to configure the antenna)odu antenna type What type of antenna is installed

Antenna #type

Antenna (Ku-band) Type Size

21 ASC Signal Type 845TX Fixed 0.84 m

2 ASC/Andrew/Channel Master Type 960 Fixed 0.96 m



7 ASC/Andrew/Channel Master Type 244 Fixed 2.4 m23 BrasilSat SOB107-098 Fixed 0.98 m

24 BrasilSat SOB107-12 Fixed 1.2 m

25 BrasilSat SOB107-18 Fixed 1.8 m

31 General Dynamics Series 3740 Fixed 0.74 m

26 Intellian v60 Mobile 0.6 m

27 Intellian v80G Mobile 0.8 m



37 Jotron B60Ku Mobile 0.6 m



32 OrSat AL-7103 MKII Mobile 1.15 m

11 Patriot TX-090KU Fixed 0.9 m



14 Patriot TX-240KUBATWING Fixed 2.4 m

15 Prodelin Series 1132 Fixed 1.2 m



22 Raven G98 (0.99 x 0.965 m) Fixed 0.98 m

36 Raysat E7000 Mobile 0.6 m

18 Seatel 2406 Mobile 0.6 m

8 Seatel 4003 Mobile 1.0 m19 Seatel 4006 Mobile 1.0 m




30 Thrane & Thrane SAILOR 900 Mobile 1.03 m

6 Visiosat Fixed 0.75m

9 Visiosat KIT 90 EMIT Fixed 0.9 m

10 Visiosat KIT 120 EMIT Fixed 1.2 m

Select installed antenna typeExample:

odu antenna 12 (selects the Patriot 1.0m antenna)


15/33


# ? odu lnb (Command to show how to configure the LNB)USAGE:odu lnb type LNB type installed

ODU LNB #(type) ODU LNB

Ka-band

100 Invacom Transceiver 3W, 19.20-20.20 GHz

Ku-band

20 Invacom SPV-1SM, 10.70-12.75 GHz



30 Zinwell ZK-VJ1, 10.70-12.75 GHz

40 JRC NJR2535S, 11.70-12.20 GHz

41 JRC NJR2536S, 12.25-12.75 GHz

42 JRC NJR2537S, 10.95-11.70 GHz

43 JRC NJR2183F, 11.20-11.70 GHz

61 Jotron, 10.70-12.75 GHz

62 Thrane & Thrane SAILOR 900, 10.70-12.75 GHz71 AZIMUTH AZ-QLKUF01 4-band LNB, 10.70-12.75 GHz

72 SMW Q-PLL Type R, 10.70-12.75 GHz

73 SMW Q-PLL Type O, 10.70-12.75 GHz

C-band

80 Zinwell ZC-VD1, 3.4-4.2 GHz

85 Norsat 8XXX-series, 3.4-4.2 GHz

95 NexGenWave NEX-800, 3.4-4.2 GHz

Select LNB type used for receptionNote: The SatLink 403x are transceivers with built in LNB.

When selecting any of these transceivers the corresponding LNB willbe configured automatically.

Example:

odu lnb 20 (select the Invacom SPV-1SM LNB)

# ? odu txtype (Command to show how to configure the BUC)USAGE:odu txtype type Type of BUC (ODU transmitter) that is installed


16/33


ODUTransmitter #

(type)

ODU Transmitter (BUC)

Ka-band

100 Invacom Transceiver 3W, 29.5-30.0 GHz

Ku-band11 STM SatLink 403x, 14.0-14.5 GHz

20 Norsat 1010XRT / 1020XRT, 14.0-14.5 GHz

30 Invacom TUL-204, 14.0-14.5 GHz

42 JRC NJT5096, 13.75-14.25 GHz

43 JRC NJT5097, 13.75-14.25 GHz

45 JRC NJT5017, 14.0-14.5 GHz

46 JRC NJT5118 w/ext. power supply, 14.0-14.5 GHz

47 JRC NJT5037, 14.0-14.5 GHz

61 Jotron DRU17F16XSE (Skyware DR7), 13.75-14.5 GHz

62 Thrane & Thrane SAILOR 900, 13.75-14.5 GHz

65 ND SatCom RFT 35W w/ext. power supply, 14.0-14.5GHz

71 CODAN 6908 w/ext. power supply, 14.0-14.5 GHz, LO15.45 GHz

72 CODAN 6916 w/ext. power supply, 14.0-14.5 GHz

73 CODAN 6908 w/ext. power supply, 13.75-14.5 GHz, LO12.8 GHz

74 CODAN 4908 w/ext. power supply, 14.0-14.5 GHz

75 Actox ABAxKUS, 14.0-14.5 GHz

C-band

80 JRC NJT5652, 5.85-6.35 GHz

81 JRC NJT5656, 5.85-6.35 GHz

92 Zinwell ZTX-C3300F, 5.925-6.425 GHz




95 NexGenWave TA33BPXE-01, 6.425-6.725 GHz

Select installed BUC typeNote: The SatLink 403x are transceivers with built in LNB.

When selecting any of these transceivers the corresponding LNB willbe configured automatically.

Example:

odu txtype 20 (select the Norsat 1010XRT BUC)

4.3.5 GPS

# dvb pos show (Commnad to show GPS information)

Latitude : 60d 3.07'N ( 60d 3' 4''N )Longitude : 10d 41.32'E ( 10d 41' 19''E )Altitude : 350 mTiming Reference : NeraPositionSearchN : 0# ? dvb poslat : dvb pos lat long : dvb pos long alt : dvb pos alt delayburst : dvb pos delayburst search : dvb pos search show : dvb pos show


17/33


4.3.6 SW and HW information

# sw show (Command to show SW information)SW versions:

Boot : 9.0.1.7Current : 13.0.5.83Backup : 13.0.4.79

Manual SW upgrade settings:TFTP server IP addr : 10.10.10.25File name : dvb-rcs-12.1.3.82.tgz

Automatic SW upgrade settings:Activated : NoPID : 511IP address : 224.0.1.59Port No. : 2001

Licenses for SW options:

NATGREPEP-TCPQOS-4RACPEP-HTTP

# ? sw (Command to show how to configure SW)upgrade : sw upgrade [-default] [ []]show : sw showrestore : sw restore

license : sw license mcast : sw mcast [] [] []

Example:

# sw upgrade satlink-vsat2-15.0.2.44.tgz 10.10.14.8 (Command to Upgrade sw version)Software download in progress, pleasewait.....................................................................................................Download completeFile Transfer completeConfiguration Saved

# device show (Command to show HW information)System Information:

Name : STMTESTLocation :Contact :System Up time : 31 days, 09:13:55CPU Load : 10%System time(UTC) : 28 October 2011 09:18:08

HW:Model : SatLink 1000HW ID : 103346Main board ID : 108198 R1.1

MAC addresses:Ethernet (LAN) : 00:20:0e:00:8c:93

Satellite (DVB) : 00:20:0e:00:8c:93


18/33


4.3.7 Troubleshooting

# log showfile (Command to show the LOG file)LOG SHOW at 28/10/2011 09:22:28All events logged to file-----------------------------------------------------------------------------Event Date Time Src Severity-----------------------------------------------------------------------------DVB-S/S2 Demodulator lost lock(RX : 0, Rx pkg : 0, Rx pkg err: 0) 19/08/2011 11:29:37 MajorNCR lock lost (Rx unlocked) 19/08/2011 11:29:38 MajorGW Initiated Logoff 19/08/2011 11:30:04 MajorDVB-S/S2 Demodulator lost lock

(RX : 0, Rx pkg : 0, Rx pkg err: 0) 19/08/2011 19:21:35 MajorNCR lock lost (Rx unlocked) 19/08/2011 19:21:35 MajorGW Initiated Logoff 19/08/2011 19:22:05 MajorDVB-S/S2 Demodulator lost lock(RX : 0, Rx pkg : 0, Rx pkg err: 0) 25/08/2011 18:05:55 MajorNCR lock lost (Rx unlocked) 25/08/2011 18:05:55 MajorGW Initiated Logoff 25/08/2011 18:06:20 MajorUnit has restarted after power off **/**/**** **:**:** Major

# dvb cr show (Command to show Return Channel configuration)Capacity parameters per channel:-------------------------------Channel CRA[kbps] Allocated[kbps]

0 0 0Requested capacity per QoS class:---------------------------------Channel CRClass MaxRBDC[kbps] MaxVBDC[kB] RateReq[kbps] VolReq[octs] Description

0 0 256 100 2 0 Best Effort0 1 0 0 0 0 VoiP0 2 0 0 0 0 ViC0 3 0 0 0 0 Critical Data

RBDC timeout 1 VBDC timeout 20VBDC computation interval 200 ms (configured 0)

# ip dns resolvewww.google.com(Command to show DNS Resolution)Sent to DNS Waiting up to 30 sec ...Domain name: www.google.com IP= 74.125.39.104

# arp show (Command to show devices connected to the VSAT)NetAddr State MacAddr If192.168.0.2 Dynamic 00:21:29:bd:be:67 1192.168.0.5 Dynamic 00:11:25:f6:17:fb 1192.168.0.6 Dynamic 00:11:25:f6:37:53 1192.168.0.7 Dynamic 00:11:25:f7:92:fe 1192.168.0.8 Dynamic 00:11:25:f6:b4:d0 1

192.168.0.9 Dynamic 00:11:25:f6:18:30 1192.168.0.10 Dynamic 00:11:25:f7:77:a0 1
http://www.google.com/http://www.google.com/http://www.google.com/http://www.google.com/


19/33


192.168.0.11 Dynamic 00:11:25:f7:b3:40 1192.168.0.12 Dynamic 00:11:25:f5:1b:5c 1192.168.0.13 Dynamic 00:16:35:a5:35:3e 1192.168.0.14 Dynamic 00:16:35:79:4b:74 1

# ip dhcp show (Command to show DHCP information)DHCP Server Status-------------------------------------------Server Status : Enabled

Server IP address : 192.168.0.1Server IP address range :

Starting IP address : 192.168.0.1Ending IP address : 192.168.0.254

No of IP addresses excluded : 1Excluded IP address range :

Starting IP address : 192.168.0.254Ending IP address : 192.168.0.254

Lease Time : 1 Week 0 Hours 0 Minutes 0 SecondsPrimary DNS server : 192.168.0.1Secondary DNS server : 217.15.32.2DHCP Client Table-----------------Host Name IP Address HW MAC Address Lease expires

192.168.0.3 1 00:11:25:f6:b4:d0 Thu Nov 3 08:16:28 2011192.168.0.2 1 00:21:29:bd:be:67 Tue Nov 1 01:31:34 2011

# ping 192.168.0.10 (Command to show PING Replay)

64 bytes from 192.168.0.10: time=2 ms64 bytes from 192.168.0.10: time=2 ms64 bytes from 192.168.0.10: time=2 ms64 bytes from 192.168.0.10: time=2 ms--- 192.168.0.10 ping statistics ---5 packets transmitted, 5 received, 0 percent packet lossrtt min/avg/max = 2/2/2 ms

# eth show (Command to show Ethernet Configuration)PHY Device : Kending 8721bConfiguration : Auto NegotiationStatus : 100MBps Full Duplex (0x786d1598)Dir Frames Unicast Multicast Broadcast Discards CRC errsRX 38669165 380385 17489329 20798201 1250 0TX 735866 5902 45710 165 0 -

4.4 Line-up

4.4.1 Forward Link Acquisition

Connect the RX cable between the ODU and IDU (if not already connected). Verify that the RX powerlevel is between -25 dBm and -65 dBm at the input of the IDU.


20/33


Note: The SatLink 2000 and 2900 are able to estimate the input power level in the range of

-70 to -5 dBm. If the input power level is outside this range then -100 dBm and +5 dBm will

be reported respectively.

If the antenna, ODU, and Forward Link parameters have been set correctly (see sectionError! Referencesource not found.4 - Error! Reference source not found., and section Error! Reference source notfound.- Error! Reference source not found.) and the IDU RX power level is as specified above, theVSAT is ready to acquire the Forward Link:

1. If not already logged on, start the VSAT and login asinstaller(user = install, factory default

password = dvbrcs) after having seen the messageStarting DVB interface.

2. Enter the CLI commanddvb rx startto acquire the Forward Link.

3. The CLI message Forward Link up is displayed on the CLI output after successful acquisition ofthe Forward Link.

If the VSAT reports that RX tuning failed please check the following:

ODU parameter settingsection Error! Reference source not found.

Forward Link parameter settingsection Error! Reference source not found.

That the RX cable is properly connected to both the VSAT and the LNB

That the signal level in to the IDU is between -25 dBm and -65 dBm

That the antenna/ODU has been properly aligned (both antenna pointing and polarization adjustmentcorrect)

To ensure good performance (less than one error event at MPEG2-TS level per hour) for the ForwardLink, the SNR value, reported using the dvb rx show command, shall be verified to be at a minimum

level before line-up is completed. If, after repeated antenna/ODU alignment, the minimum SNR value isnot obtained, the system operator/service provider shall be contacted.

4.4.2 Fine Adjustment of Antenna Pointing

If the CW from the power calibration routine is still on, it can be used for fine-adjustment of the antenna

as well. Otherwise, start CW transmission on the default CW frequency by issuing the CLI commanddvbtx cw on.

Ask the control center if they are measuring the expected power level for the CW. If not, it

is likely that the antenna pointing is not optimal. Fine-adjust the antenna pointing until theCW power level detected by the control center is within their requirements.

4.4.3 Fine Adjustment of Antenna Polarization

Ask the control center if the measured level of the CW on the cross-polar transponder is below theirrequirement. If not, adjust the rotation angle of the RX/TX/Feed Assembly with respect to the feed hornuntil the polarization discrimination is within specified limits.


21/33


Extensions for Mobile VSATs5.The extensions in this appendix are available for the SatLink 1910 and 2900 VSATs with the MOBILEsoftware license key set. To use the transmit inhibit function described in section5.1,the SatLink 1910

must be equipped with the SatLink 100 plug-in card, revision 2.0 or newer. For the SatLink 2900, thetransmit inhibit function is supported via the built in J1 connector and no plug-in card is required forsupporting the transmit inhibit function.

The below example shows a printout of the sw showCLI command for a VSAT with the appropriatemobile license:

# sw show

SW versions:

Boot : 9.0.1.7

Current : 13.0.2.65

Manual SW upgrade settings:

TFTP server IP addr : 10.10.1.1

File name : new.tgz

Automatic SW upgrade settings:

Activated : Yes

Upgrade status : Waiting

PID : 1022

IP address : 224.0.1.59

Port No. : 2001

Licenses for SW options:

GRE

MOBILE

PEP-TCP

QOS-4

PEP-HTTP

VLAN

5.1 Transmit Inhibit Function

In order to comply with FCC regulations, an external push button has to be installed on Maritime VSATinstallations, making the VSAT transmitter stop transmission within 100 ms after pushing the button.

The SatLink 2900 and SatLink 1910 (with SatLink 100 plug-in card installed) are capable of interfacingan external push button to implement this transmit inhibit function, typically being used to avoidexposing people who have to work in the area around the antenna to the transmitted signal. When transmitinhibit mode is cleared by releasing the external switch, the transmitter will be re-enabled.

Note: In addition to this transmit inhibit function via external push button, when the

mobile VSAT communicates via LAN interface with the Antenna Controller Unit (ACU),

the ACU may also request the mobile VSAT to inhibit (mute) its transmission.

5.1.1 SatLink 2900

The J1 (RJ45) connector on SatLink 2900 has the sametransmitinhibitfunctionality as of RJ11connector on the SatLink 100 for the SatLink 1910. The transmit inhibit switch is connected to theJ1connector at pin 1 of the RJ45 connector for the input signal (Tx) as shown inFigure 2below.


22/33


Figure 2: J1 Connector Pin Mapping

5.2 GPS Interface

The SatLink 1910 and SatLink 2900 with a mobile license key set can automatically read their GPSposition from an external GPS via the NMEA-0183 protocol and hence constantly have available thecorrect GPS position for use in calculating correct delay to the satellite to enable the logon burst to be sentwith correct timing when the mobile VSAT wants to enter a SatLink network.

The SatLink 2900 can automatically read its GPS position from the GPS input received via the J1connector (uses pin 2 and common GND on pin 6 inFigure 2). On the SatLink 1910 the GPS input isread via the DSUB connector using a special adapter cable.

Two NMEA-0183 GPS strings, GPGLL and GPGGA, are supported by the SatLink mobile VSATs.

The GPGLL GPS string concerns the geographic position. STM supports the following string:

$GPGLL,4916.45,N,12311.12,W,225444,A,*31

This string indicates a latitude of 49 degrees, 16.45 minutes North and a longitude of 123 degrees, 11.12minutes West, with a fix taken at 22:54:44 UTC. Data status is set to A, or active (can be set to V, orvoid). Checksum data is indicated by the 31 at the end of the string.

The GPGGA GPS string concerns the global positioning system fix data. STM supports the followingstring:

$GPGGA,123519,4807.038,N,01131.000,E,1,08,0.9,545.4,M,46.9,M,,*47

Parsing out the fields sequentially in the string, we find that this string indicates a fix taken at 12:35:19UTC, for the latitude 48 degrees, 7.038 seconds North and the longitude 11 degrees, 31 seconds East.The 1 following the E indicates a selection from one of 9 possible options for fix quality, 0-8. Theseoptions are:

0: Invalid1: GPS Fix (SPS)2: DGPS Fix3: PPS Fix4: Real Time Kinematic5: Float RTK

RJ 45

Tx inhibit switchconnects to pin 1 Rx lock Signal

connects to pin 3 GNDGPS inputconnects to pin 2


23/33


6: Estimated (Dead Reckoning)7: Manual Input Mode8: Simulation Mode

After the fix quality option comes 08, representing the number of satellites being tracked. Thehorizontal dilution of position is 0.9. The altitude in meters above sea level is 535.4 meters, and theheight of geoid (mean sea level) above the WGS854 ellipsoid is 46.9 meters. The two empty fieldsrepresent the time in seconds since the last DGPS update and the DGPS station ID number. At the end ofthe string is the Checksum data, 47.

Serial interface settings specified for use with NMEA-0183 are:

Baud Rate: 4800Data: 8 bitsParity: NoneStop: 1 bit

Flow Control: None

Illegal/invalid values received in the NMEA-0183 GPS strings, GPGLL, or GPGGA trigger warningmessages. These can be checked in the event log.

# log show

LOG SHOW at 26/07/2012 03:47:10

Last 200 events stored in volatile memory

-----------------------------------------------------------------------------

Event Date Time Src Severity

-----------------------------------------------------------------------------

Invalid GPS received & ignored cnt=1--` 26/07/2012 03:32:01 Minor ==> from (2)Invalid GPS received & ignored cnt=2--` 26/07/2012 03:33:28 Minor ==> from (3)Invalid GPS received & ignored cnt=3--(GPGGA Missing separator, or not GPGGA or

bad cksum) 26/07/2012 03:36:25 Minor ==> from (5)

Invalid GPS received & ignored cnt=4--` 26/07/2012 03:38:22 Minor ==> from (7)

Invalid GPS received & ignored cnt=5--` 26/07/2012 03:40:20 Minor ==> from (8)Invalid GPS received & ignored cnt=6--(GPGLL Missing separator, or not GPGLL or

bad cksum) 26/07/2012 03:41:42 Minor ==> from (10)Invalid GPS received & ignored cnt=7--(GPGLL Missing separator, or not GPGLL or

bad cksum) 26/07/2012 03:45:29 Minor ==> from (11)

5.3 RX Lock Signal

The SatLink 2900 outputs a RX lock signal on connector J1 to signal to external units when it is locked tothe Forward Link. The output signal is a 3.3V TTL signal, where "low" signals that the RX is locked and"high" signals that the RX is not locked. SeeFigure 2where the lock signal is found on pin 3 and usesthe common GND on pin 6.


24/33


In figure 8 you can find an example of the cable connection from SL 2900 to a Seatel TMS, to connectGPS, RX Lock and Tx Inhibit cables

Figure 8. Connection between SL 2900 and Seatel TMS


25/33


Appendix. Troubleshooting6.

6.1 Q&A

Question Answer1. Input from keyboard is not displayed on the

screen, but information from the VSAT isvisible.

Verify that the Local Echo is enabled in theTelnet Client.

In Windows XP, the Local Echo is enabled by thefollowing procedure:C:\ TelnetMicrosoft Telnet> set localechoLocal echo onMicrosoft Telnet>

To connect to the SatLink VSAT, type the

command:Microsoft Telnet> open

2. VSAT displays Receiver tuning failed for

The VSAT is missing all or part of theinformation in the signal transmitted from theDVB-RCS Hub.

Verify that the receiver status is locked usingthe command DVB RX SHOW.

If the status is anything other than locked,verify the interface connections according to

section Error! Reference source not found.Error! Reference source not found..

If the status is locked, please contact the HubOperator to confirm that the equipment has beenconfigured correctly.

3. VSAT displays Logging on- Logon failedLineup has been performed and levelscalibrated with Control Center.

Verify that the GPS configuration is correct.

If transmit level calibration has not beenperformed, power off the SatLink VSAT andcontact the DVB-RCS system operator.

4. How do I enable GRE in the VSAT? The GRE feature requires license keys to be

enabled. Contact the Hub Operator or ISP toobtain this license.

5. How do I change the login password? The password can be changed with the command# user passwd

To change the password on a different user, thecommand is:# user passwd

6. I have changed the password, but have lost it. A new password will have to be defined for theuser. Contact the Hub Operator for assistance.

7. How do I load new software on my SatLink

VSAT?

See description in section Error! Reference

source not found.Error! Reference source notfound..


26/33


8. Rx tuning failed for NIT TS. The initialtransponder cannot be found.

Please check freq/symbrate/lnb and antenna. Ifproblem still persists, please contact HubOperator 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 alsoavailable. Without this descriptor, the RCSTcannot locate the FLS which holds the descriptionof the Return Link service (i.e., the RCS Maptable).

10. Rx tuning failed for RMT TS (from NIT)The secondary transponder signaled from theHub cannot be found.

Possible configuration error at Hub, or temporaryoutage. Please contact Hub Operator forassistance.

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 avalid RCS Map Table.

This is probably due to the RMT missing, or dueto 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 RCSTcannot find the Program Map Table for theRMT Service.


17. RMT not received. This is probably due to the RMT missing, or dueto a missing linkage descriptor of type 129 (RCSFLS Service) with an appropriate population ID.

If the problem still persists, please contact HubOperator for assistance.

18. Rx tuning failed for DVB-RCS FLS TS(from RMT).


19. PAT not received on DVB-RCS TS. TheRCST cannot find the Program AssociationTable on the FLS for the DVB-RCSsignaling tables.


20. PMT not received on DVB-RCS TS. Please contact Hub Operator for assistance.

21. TIM not received. The Broadcast TIM hasnot been received (or misses some criticalparameter).

The broadcast TIM must contain a contentioncontrol and correction control descriptor beforelogon 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 thesatellite network. Please contact the HubOperator. The VSAT will not attempt additionallogon.

25. Logon Failed -- Hub busy. The Hub has insufficient resources to serve thelogon request from the VSAT. The VSAT will,after a timeout, perform another logon attempt. Ifthe situation persists there may be somethingwrong with the VSAT configuration at the Hubside. Please contact Hub Operator for assistance.


27/33


26. Hold State. The VSAT has been put in hold state by the HubOperator. Only the Hub Operator can release itagain. Contact the Hub Operator for assistance.

27. Manual Mode not logging on. The VSAT is set to accept manual logon only.

Please log on manually or configure it to log onautomatically.

28. Sync Max Loss Exceeded - Logging off. The VSAT has sent the maximum allowednumber of synchronization messages to the Hubwithout response. This may happen for a numberof reasons. Please check power level, antenna,etc. If the problem persists, please contact HubOperator for assistance.

6.2 Debugging Network Connections

Ping is a useful tool to debug network connections.

A ping test can be done from a PC connected to the Ethernet port of the VSAT (e.g., from Microsoftcommand prompt).

Use the following commands:

1. Ping the Ethernet interface IP address of the VSAT (e.g. 10.10.20.1). If not OK please check theEthernet cable and the connection to the SatLink VSAT.For SatLink 1900 and 1901 only: Check that the VSATs Ethernet port is operating in the correct

mode. The switch should be set to HUB for direct PC to VSAT connections using a straightEthernet cable.

2. If the Ethernet connection is OK then check the IP configuration and routing table of the PC (e.g.,type the MS-DOS commands ipconfigandroute print) and check the IP configuration of the

VSAT (use the CLI commandip show).3. If the ping to the SatLink VSAT is successful, try to ping a known Internet address (e.g.

www.google.com). If successful, the connection to the Internet is OK.If not OK check that the PC DNS IP address is correct. Try also to ping a known IP address onthe Internet (e.g., ping 195.204.181.169).

4. If none of the above solves the problem, the System Operator must be contacted.

6.3 Collecting Information if a Problem Occurs

If a problem occurs with the SatLink VSAT for which support might be needed, having the information

listed below available will be helpful.

1. The VSAT log from the Putty window.If possible, log the output from the VSAT to the Putty window when the problem occurs.

The output from the Putty window can copied directly from the Putty window just selecting thecontent from the window itself. This will copy the content and no need to CTRL+C. The content canthen be pasted into a text editor such as Notepad or Word to generate a file suitable for being includedas an e-mail attachment just pasting with CTRL+V

When logging into Putty, please issue the following CLI commands and capture the output.

ip show

dvb tx show


28/33


dvb tx show -capacity

dvb rx show

dvb rx show -pid

dvb pos show

odu show

sw show

log show -all

dir

2. The VSAT configuration file, config.txt.

If possible, please upload the configuration file to a PC with a TFTP server using the CLI commandupload config.txt [], where TFTP-Ipaddressis

the IP address for the TFTP server and remotefilenameis an optional parameter specifying thefilename to store the file as on the TFTP server if a different name than config.txt is wanted. Pleaserefer to Error! Reference source not found.for an example of how to install and set up a TFTP

server.

If it is not possible to upload the VSAT configuration file to a TFTP server; the config.txt file might

be dumped to the RS-232 port / Putty by using the CLI commandtype config.txt. The outputfrom the Putty can then be copied to a text file.

6.4 List of Events that May be Logged

The following are the most common events that may be shown in the log from the VSAT. Use the CLI

command log showto display the list of events stored in memory and the CLI command

type activeLog.txtto display the list of events stored on the flash file system.

Events of type Major will normally cause disruption in the data transfer, while events of type Criticalnormally will require user intervention in order to restore the data communication with the DVB-RCSHub.

Event Severity User action required Comment

NCR lock lost Major None The VSAT must log off, but willautomatically try to reacquire the ForwardLink and log on again. If the problempersists, please contact the Hub operator.

DVB-S/S2Demodulator lostlock

Major None The VSAT has lost the Forward Link fromthe Hub. All 2-way IP communication willbe broken. This is normally caused by a fade

event caused by rain or snow. If the problempersists also after the weather improves,please check that the VSAT antenna has notbeen put out of its correct position beforecontacting the Hub operator.

DVB-S/S2Demodulator Re-synchronization

Minor None There was a short interruption to thereception of the Forward Link from the Hub.Normally this happens during rain fades.Normally no or only 1-2 IP packets are lostduring such an event.

CMT not received Major None The VSAT must log off, but willautomatically try to log on again. If the

problem persists, please contact the Huboperator.


29/33



Logon retrytimeout

Minor None The VSAT was not able to log on to theHub. After a timer has expired the VSATwill retry logging on to the Hub.

Logon failure Major None The VSAT was not able to log on to theHub. Please check that correct GPS positionand population ID has been configured.

After a timer has expired, the VSAT willretry logging on to the Hub. If the problempersists, please contact the Hub operator.

GW Busy Major None The Hub does not allow the VSAT to log on.After a timer has expired the VSAT willretry logging on to the Hub. If the problempersists, 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 initiatedlogoff

Major None The Hub operator has forced the VSAT tologoff.

Fine Sync failure Major None The VSAT was not able to enter the finesynchronization state when trying to log on.After a timer has expired the VSAT willretry logging on to the Hub.

ODU power onfailure

Critical Check that cable to ODUis connected and that theVSAT is configured forthe correct ODU (type

CLI commandodu

show)

The VSAT is not able to establish DiSEqCcommunication with the ODU. Possiblecauses 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 initiatedlogoff.

Entering holdstate

Major None The Hub operator has put the VSAT inHold-state. When the VSAT is in the Hold-state it is not allowed to try to log on to theHub. To get an explanation of why theVSAT has been put in Hold-state pleasecontact the Hub operator.

Leaving hold state Normal None The VSAT is again allowed to log on to the

Hub.Unit has restartedafter power off

Major None Normal message when unit is powered on.

Unit has restarted Major Check log with CLIcommandlog show -file

If the event happens multiple times withoutany explanation please contact the HubOperator and provide printout of the CLI

command log show file.

Restart cmd fromlocal or remoteoperator

Major None Unit has been restarted by the operator fromthe hub or locally.


30/33



Automatic Restart Critical None The VSAT was forced to restart due tofollowing possible reasons, included in thelog:

Forward Link search has timed out VSAT is unable to allocate memory

Tuning failuretransponder one

Major Check RX configuration(frequency,symbol rate).Check that the cable toLNB is properlyconnected.

The VSAT is not able to acquire a lock onthe initial Forward Link transponder (the onethat is configured in the VSAT). If theproblem does not disappear within 10-60minutes, please contact the Hub operator.

Tuning failuretransponder two

Major None The VSAT is not able to acquire a lock onthe second Forward Link transponder. If theproblem does not disappear within 10-60minutes, please contact the Hub operator.

Tuning failuretransponder three

Major None The VSAT is not able to acquire a lock onthe third Forward Link transponder. If theproblem does not disappear within 10-60minutes please contact the Hub operator.

Missing Table Major None The VSAT is not receiving a mandatoryDVB-S2/DVB-RCS table on the ForwardLink. If the problem does not disappearwithin 10-60 minutes please contact the Huboperator.

TCTInconsistency

Critical Restart VSAT There is an error in the received TCT table.

If the problem does not disappear within 10-60 minutes, please contact the Hub operator.

DVB-RCSlinkage descriptornot found

Major None The VSAT is not receiving a mandatoryDVB-S/2DVB-RCS descriptor on theForward Link. Please check the configuredpopulation ID of the VSAT. If the problemdoes not disappear within 10-60 minutes,please contact the Hub operator.

Forward Link isUp

Normal None The VSAT has completed acquisition of theForward Link tables.

VSAT tuned to anew Forward Link

Normal None The VSAT logs the Forward Linkinformation when transponder one is found.

Included information are: Network name

Forward Link rate

Forward Link frequency

Frequency out ofrange

Major Check ODU configuration TX or RX frequencies outside the supportedranges of the IDU and ODU have beendetected. Please check that the ODUconfiguration matches the frequencies in useon the satellite and that the ODU in use iscompatible with the IDU IF interface.


31/33



ODUCommunicationFailure

Critical Check that cable to ODUis connected and that theVSAT is configured for

the correct ODU (typeCLI command odu

show)

The VSAT is not able to establish DiSEqCcommunication with the ODU. Possiblecauses may be:

- Cable to ODU not connected- IDU not configured for correct ODU- The ODU is defect and must be repairedThe VSAT will restart automatically.

ODUTemperature HighWarning

Major Check outsidetemperature. Check TXcable connecting IDU toODU.

The temperature in the ODU has become toohigh. If this happens several times withoutextreme weather conditions please checkthat there is no problem with the cableconnecting the IDU and ODU. Please checkif there are errors on the DiSEqCcommunication between the IDU and ODU

by using CLI command odu show

diseqc. If DiSEqC errors are reported, thelikely source of the problem is a bad TXcable connecting the IDU to the ODU, orpoor connection of the cable to theconnectors. Please always ensure that thereis a good connection of the shield of thecable (GND) to connectors in both ends ofthe cable.

ODUTemperatureCritical

Critical Check outsidetemperature. Check TXcable connecting IDU toODU.

The temperature in the ODU has become toohigh. If this happens several times withoutextreme weather conditions please checkthat there is no problem with the cableconnecting the IDU and ODU. Please checkif there are errors on the DiSEqCcommunication between the IDU and ODU


diseqc. If DiSEqC errors are reported thelikely source of the problem is a bad TXcable connecting the IDU to the ODU, orpoor connection of the cable to theconnectors. Please always ensure that thereis a good connection of the shield of thecable (GND) to connectors in both ends of

the cable.

The VSAT might stop transmitting (if theForward Link is reacquired).

ODU turned itselfoff

Critical Restart VSAT. If thefailure occurs again theODU must be sent forrepair.

The ODU has powered itself downmostlikely because it has detected a failure. If thishappens more than once the ODU must besent for repair.


32/33



ODU PLL LockLost

Critical Check if problem iscaused by faulty DiSEqCcommunication. If not

send ODU for repair.

First check if there are errors on the DiSEqCcommunication between the IDU and ODU


diseqc. If DiSEqC errors are reported thelikely source of the problem is a bad TXcable connecting the IDU to the ODU, orpoor connection of the cable to theconnectors. Please always ensure that thereis a good connection of the shield of thecable (GND) to connectors in both ends ofthe cable. If no errors are reported on theDISEqC communication, then the ODU isnot able to transmit with the correct TXfrequency and must be sent for repair.

ODU Short

Circuit

Critical Find and remove cause of

short-circuit.Restart VSAT.

The power supply to the BUC has been

short-circuited. After removing the cause ofshort-circuit, the VSAT must be restarted inorder to recover.

LNB Short Circuit Critical Find and remove cause ofshort-circuit.Restart VSAT.

The power supply to the LNB has beenshort-circuited. After removing the cause ofshort-circuit, the VSAT must be restarted torecover.

Unit TemperatureHigh

Major Check temperature at IDUlocation

Temperature inside the IDU is getting toohigh.

Unit TemperatureCritical

Critical Check temperature at IDUlocation

Temperature inside the IDU has gotten toohigh.

Failed to loadfirmware Critical Send the IDU for repair. The IDU cannot access the satellite interfacebecause failing to load the firmware. TheIDU must be sent for repair.

TFTP Serverunreachable

Major Check IP connection withthe TFTP server.

The VSAT is not able to establishconnection with the TFTP server. Likely tobe an IP configuration or network problem.Verify the IP connection with the TFTPserver by pinging.

File not found Major Verify that the file ispresent on the TFTPserver.

The VSAT is not able to upload the filespecified in the command from the TFTPserver. Verify that the file is available on theTFTP server.

File transfer error Major Check available space onfile system.

The File transfer has been aborted either dueto an IP connection interruption between theVSAT and the TFTP server or due to a lackof available space on the VSAT's filesystem.

Manual SWUpgradedcompleted

Normal None. It reports successful VSAT software upgradevia TFTP.

Automatic SWdownload started

Normal None. The VSAT has started automatic downloadvia Multicast of a new software version.


33/33



Automatic SWdownloadcompleted

Normal None. The VSAT has successfully downloaded anew software version via Multicast. TheVSAT will automatically restart and activate

the new software version.

SW upgradefailed

Critical Retry SW upgrade. TFTP download of new software imagefailed.

IP address conflicton LAN

Normal Check IP configuration ofthe VSAT.

The VSAT has detected conflicting IPaddress on the LAN interface.

DNS server reply:Recursion NotAvailable

Critical Change configuration ofHub DNS server to allowreply recursion.

DNS server does not allow reply recursion.

DNS WARNING Normal Check configuration ofthe DNS primary andsecondary IP address.

No connectivity with DNS server.

IP Address for Major None. The VSAT IP address of the LAN or DVBinterface is changed. New IP address isvisible in the log.

IP NetMask for Major None. The VSAT network mask of the LAN orDVB interface is changed. The new networkmask is visible in the log.

Created virtual Inf Major None. A virtual interface is created.

Deleted virtual Inf Major None. A virtual interface is deleted.

Route added Major None. A new IP route is configured in the VSAT.

Save ConfigExecuted

Major None. The VSAT configuration is saved.

No Global NAT

Addr defined

Major Add global NAT address

to the VSATconfiguration.

The VSAT NAT functionality is enabled but

no global NAT address is defined.

VSAT IP cannotbe used as GlobalNAT Addr

Major Check NAT configurationof the VSAT.

The VSAT does not allow using the DVBaddress as global NAT address.

TCP moduledetected highpacket loss onFWD link

Major None This event is generated when a lot of DUPACKs are detected on the Satellite Network.This is an indication that there is loss on theSatellite Network. This will reset thePEP/TCP connections for which the DUPACK count is high.

Documents

Manual SL 2900 Lite