Manual

Networks without Barriers
SatLink 8550/8560 FLS

User Guide
Revision PB1 – June 6, 2010
SatLink 85xx FLS User Guide
STATEMENT OF CONFIDENTIALITY / DISCLAIMER
The information disclosed herein is confidential and proprietary to STM and is being furnished
under a non-disclosure agreement. This document may not be disclosed to third parties without
the prior written consent of STM. The recipient of this document shall respect the security status
of the information.
© Copyright 2009-2010 STM Group, Inc. All rights reserved.
www.stmi.com
Publication no. 200197 Copyright © 2009-2010 – STM Group, Inc. Page 1 (59)
Table of Contents
1 INTRODUCTION ...........................................................................................................4
1.1 About This User Guide ..................................................................................................4
1.2 Installation and Configuration overview .........................................................................4
1.3 Symbols .........................................................................................................................5
2 UNPACKING .................................................................................................................5
3 INSTALLATION .............................................................................................................6
3.1 Before Installation ..........................................................................................................6
3.2 SatLink 85XX front and back panels .............................................................................6
3.3 SatLink 85xx Installation ................................................................................................9
3.4 Interface Connections..................................................................................................10
4 USING THE COMMAND LINE INTERFACE OF THE SATLINK 85XX .......................12
4.1 CLI users access rights ...............................................................................................12
4.2 Online help ..................................................................................................................12
4.3 Logging of events ........................................................................................................13
4.4 CLI command summary ..............................................................................................14
5 SYSTEM INSTALLATION ...........................................................................................16
5.1 Installation of the SatLink 85xx FLS ............................................................................16
5.2 SatLink 85xx ................................................................................................................16
6 SATLINK 85XX CONFIGURATION .............................................................................17
6.1 Power on and logon .....................................................................................................17
6.2 Configuring preliminary parameters ............................................................................18
6.3 FLS Line-up .................................................................................................................23
6.4 Configuring FLS parameter in SatLink NMS ...............................................................23
6.5 Redundancy ................................................................................................................24
6.6 Checking the FLS Status .............................................................................................26
7 UPDATING THE SATLINK 85XX SW .........................................................................28
7.1 Restoring the backup software ....................................................................................29
8 FLSUP FUNCTIONALITY ...........................................................................................30
9 ADVANCED STATISTICS/STATUS MONITORING ...................................................30
9.1 CLI command fls show ................................................................................................30
9.2 CLI command ncr show ...............................................................................................32
9.3 CLI command ip show .................................................................................................33
9.4 CLI command eth show ...............................................................................................33
9.5 CLI command ipe show ...............................................................................................34
9.6 CLI command device show .........................................................................................34
9.7 CLI command sw show ...............................................................................................35
9.8 CLI command tpserver show .......................................................................................35
9.9 Frequency....................................................................................................................36
10 DEFINITIONS, ACRONYMS AND ABBREVIATION ...................................................37
11 REFERENCES ............................................................................................................39
APPENDIX A. ACCESSING THE COMMAND LINE INTERFACE VIA RS-232 .........................39
A.1 Cable connection ..................................................................................................................39
A.2 PC configuration of HyperTerminal to access the CLI via RS-232 .......................................39
APPENDIX B. TFTP SERVER ....................................................................................................42

APPENDIX C. TERA TERM TERMINAL EMULATOR ................................................................42
APPENDIX D. MANAGEMENT VIA SNMP .................................................................................43
D.1 SNMP version compliance....................................................................................................43
D.2 MIB-II supported by SatLink 85xx .........................................................................................44
D.3 STM FLS MIB .......................................................................................................................45
D.4 Access policies .....................................................................................................................45
D.5 SNMP Traps for SatLink 85xx ..............................................................................................47
D.6 Setting a MIB object and saving the configuration................................................................48
APPENDIX E. THE BOOT SW....................................................................................................48
APPENDIX F. TROUBLESHOOTING .........................................................................................49
F.1 Frequently Asked Questions (FAQ) ......................................................................................49
F.2 Troubleshooting with LEDs ...................................................................................................49
F.3 Boot of SatLink 85xx without config- and application files ....................................................50
F.4 Manual software upgrade or dload fails ................................................................................50
F.5 Collecting information if a problem occurs ............................................................................50
F.6 List of events that may be logged .........................................................................................51
APPENDIX G. SNMP TRAPS AND LIST OF ALARMS SUPPORTED .......................................54
G.1 Alarm Format ........................................................................................................................54
G.2 Alarm Definitions ..................................................................................................................54
APPENDIX H. CABLE SPECIFICATION ....................................................................................55
H.1 TX L-band Cable Requirements ...........................................................................................55
H.2 10 MHz- 1PPS Cable Requirements ....................................................................................55
APPENDIX I. ADVANCED CONFIGURATIONS .........................................................................55
I.1 IPE PID Configuration ............................................................................................................55
I.2 Setting Symbol Rate...............................................................................................................56
I.3 MODCOD Configuration.........................................................................................................56
I.4 Output Power Rate .................................................................................................................57
I.5 RollOff Factor Configuration ...................................................................................................58
I.6 DVB-S2 Mode ........................................................................................................................58
I.7 Setting Frame Length .............................................................................................................58
I.8 Setting NCR PID ....................................................................................................................59
APPENDIX J. COMPLIANCE......................................................................................................59
J.1 SatLink 85xx Compatibility ..................................................................................................59
1 Introduction
The SatLink 85xx FLS is a high-performance Forward Link System (FLS) for DVB-based IP distribution
hubs with DVB-S2 ACM support. It efficiently combines the functions of a general purpose traffic
shaper, IP encapsulator, NCR and SI table inserter, and a DVB-S2 modulator with up-converter. User
traffic and SI tables are input to the FLS via a standard 10/100 Ethernet port. The compact unit supports
symbol rates up to 25 Msps (8550FLS), 45 Msps (8560FLS) and high-throughput packet processing,
making it well-suited for high-capacity DVB and DVB-RCS IP networks.
This User Guide covers the installation and operation of the SatLink 85xx FLS. The entire regular
configuration for the SatLink 85xx FLS is done using the SatLink NMS. For further details please refer to
section 14 Forward Link Management in 104980 SatLink Hub Operators Guide. The CLI commands
are only used for preliminary configuration such as IP address and SNMP configuration.
Figure 1: SatLink 8550
1.1 About This User Guide

The information given pertains to the following software (SW) and hardware (HW) versions:
SatLink 8550 Software
• SatLink Boot loader, P/N 105898, version 9.0.1.1 or later
• SatLink 8550 FLS Application Software, P/N 120009, version 13.1.0 or later
Satlink 8560 Software

• SatLink Boot loader, P/N 120333, version 14.0.0 or later
• SatLink 8560 FLS Application Software, P/N 120330, version 14.0.0 or later
SatLink 85xx HW models

• STM SatLink 180 ASI/10MHz Plug-in card for SatLink 8550, P/N 104032
• SatLink 8550, P/N 108294
• SatLink 8560, P/N 120235
1.2 Installation and Configuration overview
The SatLink 85xx must be installed and configured before it can be put in service in the SatLink Hub.
The SatLink 85xx FLS must be configured with a few parameters to enable it to be managed by the
SatLink Hub NMS. The preliminary configuration of SatLink 855xx FLS is done by using the command
line interface. For detailed information on SatLink 85xx configuration please refer to the section 6
SatLink 85xx Configuration. The installation of SatLink 85xx as Forward Link System includes
integrated NCR, IP encapsulator and L-Band modulator. For detailed information on system installation
please refer to section 5 System installation. The following figure provides a network overview of
SatLink 85xx FLS configured in 1: 1 redundancy mode in typical SatLink Hub Network.
Figure 2 : Typical Satlink Hub Configuration
1.3 Symbols
NOTE
Additional information that the reader should pay special attention to.
Warning
System malfunction may occur if the warning-information is violated.
2 Unpacking
Check that the following items are in the box received, and then unpack the unit.
SatLink 8550
• Main cord
• Brackets for 19” rack mounting
SatLink 8560
• Main cord
• Screws for rack mounting
3 Installation
3.1 Before Installation
3.1.1 Safety Measures

Follow these guidelines to ensure general safety:
• Always comply with national and local electrical codes.

• Keep the installation area clear and dust free during and after installation.
• Keep tools and all components away from walk areas.
• Do not wear loose clothing, jewellery (including rings and chains), or other items that might get
caught on the SatLink 85xx or the interconnecting cables.
• Do not work on the system or connect or disconnect cables during lightning storms.
Follow these guidelines when working with electrical equipment:
• Disconnect all power and external cables before installing or removing a SatLink 85xx.
• Do not work alone when potentially hazardous conditions exist.
• Never assume that power has been disconnected from a circuit; always check.
• Do not act in any way that creates a potential hazard to people or makes the equipment unsafe.
• Never install equipment that appears damaged.
• Carefully examine work area for possible hazards such as moist floors, unearthed mains extension
cables and missing protective earths.
Should an electrical accident occur:
• Be cautious – do not become a victim yourself.

• Turn off electrical power to the system.
• If possible, send another person to get medical aid. Otherwise, assess the condition of the victim and
then call for help.
• Determine if the victim needs artificial respiration or external cardiac compressions; then take
appropriate action.
3.1.2 Site requirements

The STM SatLink 85XX shall be connected to the mains 110/230 VAC, 50-60Hz.
3.2 SatLink 85XX front and back panels
3.2.1 SatLink 8550/8560 front panel
Figure 3: SatLink 8550 front panel
Figure 4: SatLink 8560 front panel
LED Colour, indicates

Power White, lights steadily when power switch is on and unit is powered. Flashes when loading
software.
Error Red, lights steadily during reboot. Blinks when an error occurs. (Refer to Appendix 0 for
details on error codes)
Satellite Tx White, flashes when the transmitter starts sending L band signal.
Sync White, flashes with 1 second interval when synchronised with 10 MHz and 1 PPS external
references.
Ethernet Trf White, lights steadily when Ethernet traffic connectivity is OK.
Flashes when Ethernet packets are transferred via the Ethernet traffic interface.
Table 1: SatLink 8550 front-panel LEDs
LED Colour, indicates

Power White, lights steadily when power switch is on and unit is powered. Flashes when loading
software.
Error Red, lights steadily during reboot. Blinks when an error occurs. (Refer to Appendix 0 for
details on error codes)
Satellite White, flashes when the transmitter starts sending L band signal.
Transmit
Ethernet Trf White, lights steadily when Ethernet traffic connectivity is OK.
Flashes when Ethernet packets are transferred via the Ethernet traffic interface.
Table 2: SatLink 8560 front-panel LEDs
3.2.2 SatLink 8550/8560 back panel
Figure 5: SatLink 8550 back panel (SatLink 180 mounted)
Figure 6: SatLink 8560 back panel
Item Description
On/off switch Mains power on (1) or off (0).
Mains Connector Connector for 110V/240V AC mains
Management Ethernet RJ45 connector for Management Ethernet interface. To be connected to the Management
Connector LAN in the SatLink Hub. 100BASE-T full duplex mode.
Traffic Ethernet RJ45 connector for Traffic Ethernet interface. To be connected to the Traffic LAN in the
Connector SatLink Hub. 100BASE-T full duplex mode.
COM1 RS-232 DB9 connector for Command Line Interface.
Connector For initial configuration and debugging purpose only.
ASI RX Coaxial 75 Ω BNC Female-type connector. Interface reserved for future use.
ASI TX Coaxial 75 Ω BNC Female-type connector. Interface reserved for future use.
Extension Slot SatLink 180 10 MHz 50 Ω SMA female connector for 10 MHz reference signal.
mounted 1 PPS 50 Ω SMA female connector for 1PPS reference signal.
Rx coaxial jack Not used
Rx 140 coaxial jack Not used
TX coaxial jack Coaxial 75 Ω F Female- type jack to the BUC/Up Convertor
Table 3: SatLink 8550 back panel description
Item Description
On/off switch Mains power on (1) or off (0).
Mains Connector Connector for 110V/240V AC mains
Management Ethernet RJ45 connector for Management Ethernet interface. To be connected to the Management
Connector LAN in the SatLink Hub. 100BASE-T full duplex mode.
Traffic Ethernet RJ45 connector for Traffic Ethernet interface. To be connected to the Traffic LAN in the
Connector SatLink Hub. 100BASE-T full duplex mode.
COM1 RS-232 DB9 connector for Command Line Interface.
Connector For initial configuration and debugging purpose only.
1PPS 50 Ω SMA female connector for 10 MHz reference signal.
10 MHz 50 Ω SMA female connector for 1PPS reference signal.
24-48 VDC 4A To Tx It allows us to use an external power to supply DC to BUC. This way we can use a 48
volts BUC for instance which we cannot with SL8550 or SL8560 internal power supply
which is only 24 Volts.
TX coaxial jack Coaxial 75 Ω F Female- type jack to the BUC/Up Convertor
Table 4: SatLink 8560 back panel description
3.3 SatLink 85xx Installation
3.3.1 In rack mounting
The rack or cabinet should be properly secured to prevent tipping. Equipment installed in
a rack or cabinet should be mounted as low as possible, with the heaviest units lower down,
and lighter units toward the top.
Precautions:
• Ensure that the main circuits are properly grounded and use the mains cord supplied with the SatLink
85xx to connect it to the mains outlet.
• If the installation requires a different mains cord than the one supplied, ensure that the cord used is
certified as indicated by the stamped or embossed logo of the electrical safety authority.
• If the on/off switch on the back panel is difficult to reach when the unit is fitted in the rack, ensure
that the mains outlet into which it is plugged can be reached so it may be unplugged if necessary.
• Ensure that the unit does not overload the mains circuit, wiring or over-current protection. To
determine the possibility of overloading the supply circuits, add together the ampere ratings of all
devices installed on the same circuit as the SatLink 85xx and compare the total with the rating limit
for the circuit. The maximum ampere ratings are usually printed on units near their mains connectors.
• Do not install the SatLink 85xx in a location where the operating ambient temperature may exceed
45°C.
• Ensure that the airflow around the sides and back of the SatLink 85xx is not restricted.
The SatLink 85xx can be mounted in any EIA-standard 19-inch telecommunications rack or cabinet.
Use a Torx screwdriver and attach the mounting brackets to the FLS with the screws supplied. Hold the
unit securely, brackets attached, and move it vertically until rack holes line up with the bracket notches,
then insert and tighten the four screws holding the brackets to the rack.
Figure 7: Rack Mounting
3.4 Interface Connections
3.4.1 Main connection

The STM SatLink 85xx models have internal power supply and consequently are connected directly to a
110/230 VAC 50/60Hz outlet using a standard 230 VAC main cord.
3.4.2 Tx cable between the SatLink 85xx and BUC or Up Converter

The cable from the BUC/Up Converter shall be connected to the Tx Female jack on the back panel of the
SatLink 85xx.
Use only 75 Ω cables fitted with F male plugs for the Tx cable.
3.4.3 Ethernet connection to the Management- and Traffic Local Area Networks
(LANs)
The SatLink 85xx shall be connected to the Management- and Traffic LANs via the RJ-45 Ethernet
connectors on the back panel.
• Plug one end of the Ethernet cables into the RJ-45 connector on the back panel.
• Plug the other end of the Ethernet cables to the Ethernet switches for the Management- and Traffic
Local Area Network (LAN) in the SatLink Hub.
Make sure that the interfaces are connected to the right LANs.
It is strongly recommended to configure all Ethernet devices connected to the

SatLink 85xx in 100 Mbps full duplex mode, and not use auto-negotiation.
3.4.4 10 MHz and 1PPS interface

The STM SatLink 180 PN104032 plug-in card shall be mounted in the STM SatLink 8550 extension slot
in order to have the 10MHz and 1PPS interface available.
The SatLink 8560 FLS has inbuilt 10MHz and 1PPS interface available therefore we don’t need SatLink
180 plug-in card for SatLink 8560 FLS.
The SatLink 85xx or SatLink 180 shall be connected to an external 10MHz clock using a 50 Ω cable. The
signal delivered shall be in the range 1 Volt peak to peak +/- 0.5 Volt (7dBm to 16.5 dBm).
The SatLink 85xx or SatLink180 shall be connected to an external 1 PPS clock using a 50 Ω cable. The
1PPS signal shall be a TTL signal with voltage between 0 V and 3 V. The low value of the 1 PPS shall be
in the range [0 V, 1 V] while the high value of the 1 PPS shall be in the range [2 V, 3 V].
Use only cable lengths up to 3 meter when connecting the SatLink 85xx to the
10 MHz and 1 PPS reference in order to comply with CE Electromagnetic
compatibility requirements (Article 3.1.b of the R&TTE Directive).
Figure 8: STM SatLink 180 plug-in card
Always power off the STM SatLink 8550 before mounting the STM SatLink 180 plug-in
card.
3.4.5 COM1/RS-232 interface for accessing the command line interface
The Command Line Interface may be accessed from a local PC connected to the SatLink 85xx RS-232
interface via a serial cable. HyperTerminal or any compatible terminal emulation program can be used to
access the CLI interface via RS-232, as described in details in Appendix A. Accessing the Command
Line Interface via RS-232.
4 Using the Command Line Interface of the SatLink

85xx
The command line interface can be accessed via either Telnet or the RS-232 port for management of the
SatLink 85xx as well as for showing status and reports. Appendix A. Accessing the Command Line
Interface via RS-232 describes further in details the configuration steps to access the CLI via a terminal
emulation program.
4.1 CLI users access rights

When shipped from the factory, one user is pre-configured in the SatLink 85xx:
User name Factory default password Privilege level

root admin123 1
Table 5: default user name/password
When accessing the CLI via RS-232, if the login prompt is not displayed type ENTER. The login prompt
Login: should then be displayed. Then login with the root user:
Login: root
Password: admin123
New users may be added with the CLI command user add, existing users deleted with the CLI
command user del, and the password of the current user or users with lower privilege levels can be
changed with the CLI command user passwd. To list all defined users with lower privilege level than
the user currently logged in, use the CLI command user show. Type ? user to get further help on the
user commands.
4.2 Online help

A list of available CLI commands can be displayed by typing ? <ENTER> (question mark and the
ENTER). The CLI command groups will then be shown:
Example:
# ?
? : ? <submenu|command>
fls : Main commands for FLS
device : Device configuration
dvb : DVB interface configuration
eth : Ethernet configuration
ip : IP configuration
log : Event log
misc : Miscellaneous commands
sw : Software upgrade & licenses
user : User configuration
ncr : NCR configuration
tpserver : TP server configuration
debug : Debug commands
ipe : IPE Configuration
#
To list the commands in a sub-menu type '? <sub-menu>'
Example:
# ? ip
show : ip show [-mcast]
set : ip set [-volatile] <ifnum> {<ipaddr> <mask>}|nonum
addroute : ip addroute <destaddr> <netmask> [<next hop>] [<if>]
delroute : ip delroute <destaddr> [<netmask> [<next hop> [<if>]]]
intf : Interface configuration
mfc : IP MFC configuration
For detailed help on a command type '? <command>'

Example:
# ? ip set
USAGE:
ip set [-volatile] <ifnum> {<ipaddr> <mask>}|nonum
-volatile The address will not saved in persistent memory

ifnum Interface number
ipaddr IP address for the interface
mask Netmask for the interface
nonum 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 the

subnet of its source VLAN.
If the interface is a VLAN, then its corresponding virtual VLANs IP
will be cleared.
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
#
4.3 Logging of events

The SatLink 85xx supports logging of events. See F.6 List of events that may be logged for a list of the
different events and what action needs 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:

• Minor
• Normal
• Major
• 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 recover.
To have access to the log of events also after the SatLink 85xx 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 log file. The factory default settings are that logging of events with severity level Major and
Critical to file is enabled.
4.4 CLI command summary

The available CLI commands are listed below.
CLI commands Available in Available in User

Boot Application SW Privilege
SW Level
ping {<ipaddr> [<options>]}|<-enablemonitor|- x x 5

disablemonitor>
del <filename> x x 2
ren <filename1> <filename2> x x 2
mv <filename1> <filename2> x x 2
dir [ext] x x 5
type <filename> x x 5
save config x 5
dload <filename> <ipaddr> x x 2
upload <filename> <ipaddr> x x 2
Restart x x 5
Logout x x 5
exit x x 5
? [sub-menu] [cmd] x x 5
device name <name> X 2
device contact <contact> x 2
device location <location> x 2
device telnet show [-sessionId] x 2
device telnet disconnect <sessionId> x 2
device manager show x 2
device manager add <func> <if> [<ip> <mask>] x 2
device manager del <func> <if> [<ip> <mask>] x 2
device show x 5
device snmp community <name> <ro|rw> [<ipaddr> x 1
<mask>]
device snmp delcommunity <name> x 1
device snmp show x 5
device snmp trapdest add <manager Ip> x 2
<community name>[-port <manager port> -ver
<snmp version>]
device snmp trapdest del <manager Ip> x 2
device setid <sl100 | sl110 | sl150 |sl180 | x 2
sl181> <rev><serialno>
eth show x 5
eth vlan [-del | -allow | -block] <id> [<if>] X 3
eth primap [-del] <pri> <qos> x 3
ip show [-mcast] x 5
ip addroute <destaddr> <netmask> [<next hop>] x x 2
[<if>]
ip delroute <destaddr> [<netmask> [<next hop> x x 2
[<if>]]]
ip set [-volatile]<ifnum> {<ipaddr> x x 2
<mask>}|nonum
ip mfc show [module id] x 5
ip mfc mask <module id> <sub index> <index> x 2
<group>
ip intf <add|del> <if> x 2
log file <enable|disable> x 5
[<severity> [<filesize>]]
log show [<number> |<-all> |<-conf> | [-file x 5
<number>]
sw license <feature> <key> x 2
sw upgrade [-default] [<filename> x 2
[<tftp-ip-addr>]]
sw restore x 2
CLI commands Available in Available in User

Boot Application SW Privilege
SW Level
sw show x 5
ncr show [-si|-snr] x 1
ncr pid <pid> x 1
ncr delay <ncr_offset_1> [<ncr_offset_2>] x 1
ncr siaction <none|stop|reset> x 1
ncr print <off|normal|all> x 1
ipe show x 5
ipe mac <macAddr> <qos> {<maxrate>|-del} x 5
[<minMODCOD> <maxMODCOD> <SNR offset>]
ipe pid <pid> {<maxrate>|-del} [<packing delay> x 5

<packing threshold>]
ipe ratecalc <interv> [<drop wr BE> <VoIP> x 5
<ViC> <CD>]
fls show [-mac [<mac address>]|[-subnet x 1
<subnet> <mask>]
fls on [-volatile] x 1
fls off x 1
dvb addroute <destaddr> <netmask> <qosClass> x 2
mpe 0 <pid> [<macadd>]
dvb delroute <destaddr> <netmask> <qosClass> x 2
dvb showroute [<destaddr> [<qosClass>]] | [- x 5
act]
dvb hdrcomp -show x 2
dvb tx show x 5
dvb tx outpow <pow> x 2
dvb tx freq <tx frequency > x 1
dvb tx symbrate <tx symbol rate> x 1
dvb tx rolloff <35|25|20> x 3
dvb tx pilot <on|off> x 3
dvb tx s2mode <ccm|vcm|acm> x 3
dvb tx ccmframelength <long|short> x 3
dvb tx acmmargin <margin> x 3
dvb tx ccmmodcod <modcod> x 3
dvb tx acmmodcod <modcod> [<long|short|both> x 3
[<RequiredSNR>]|-del]]
dvb tx cw <on|off> x 2
tpserver ipaddr <1|2> <ip address> x 1
tpserver proto <tcp|udp> x 1
tpserver show x 1
user add <loginname> <passwd> x x 5
[privilege level]
user del <loginname> x x 5
user passwd {loginname | oldpasswd} <newpasswd> x x 5
user show x x 5
Table 6: SatLink 85xx CLI commands summary
The CLI commands are available through the RS-232 interface or Telnet on the MGMT interface.
Always use the logout command from the Terminal Emulator to terminate a
Telnet session.
The factory default IP-address of the MGMT interface of the SatLink 85xx is 10.10.10.79 and
10.10.11.79.
5 System installation
5.1 Installation of the SatLink 85xx FLS
This chapter provides an overview for building a Forward Link System with SatLink 85xx, which is
including integrated NCR, IP encapsulator and L-Band modulator.
The following equipments can be used to build a Forward Link System

• SatLink 8550 with SatLink 180 plug-in card installed or Satlink 8560 where SatLink 180 plug-in
card is not required.
• Combiner (optional, used to combine more than one units to access the same TX port)
• Newtec 2185 switch or passive combiner can be used in 1:1 FLS redundancy mode or
• Pickering switch (Pickering switch is used if the FLS is using multiple TX antenna ports N: M
mode).
1PPS 10 MHZ TRF MGMT
SL 8550/8560 Tx
75
Combiner
Tx
SL 8550/8560
75
Figure 9 : SatLink 8550/8560 Forward Link in 1:1 redundancy
5.2 SatLink 85xx
The SatLink 8550 is specified to operate with the transmit power from -35 dBm to -5 dBm and with
transmit frequency in range 950-1450 MHz on it’s transmit port. Whereas SatLink 8560 is specified to
operate with transmit power from -35 dBm to +10 dBm.
Model Tx level range

SatLink 8550 -35 dBm to -5 dBm
SatLink 8560 -35 dBm to +10 dBm
Follow the procedure described below when installing the SatLink 85xx:
1) Connect the BUC/Up Converter IF cable to 950-1450 MHz IF Tx connector.
2) Connect the SatLink 85xx to the 10 MHz reference.
3) Connect the SatLink 85xx to the 1 PPS reference.
4) Connect the Ethernet management and Traffic connectors to the SatLink 85xx.
6 SatLink 85xx Configuration

6.1 Power on and logon
1) To view the boot processes of the SatLink 85xx, connect a PC to the COM1 serial interface and
launch a terminal emulator application such as TeraTerm (see Appendix C. Tera Term terminal
emulator) or HyperTerminal (see Appendix A. Accessing the Command Line Interface via RS-232).
Otherwise go to step 2.
2) Turn on the power of the SatLink 85xx.
3) When turning on the SatLink 85xx first the Boot SW is loaded. A message such as the one below is
displayed on the CLI/RS-232 when the boot SW starts. Note that Telnet is not available before the
application has been started.
Boot-loader
SW ID 105898, Revision 9.0.1.1
128 MB RAM test passed OK
Filesystem information table initialisation Please Wait....done

237 sectors ,31064064 Byte used
File system initialised
Press return to enter boot-loader
Loading application.............Shutdown Boot

Enable reset and jump to start address: 0xc0000
Under normal circumstances the user should not need to enter the boot-loader and should ignore the
“press return to enter boot-loader” message. The application software will load automatically once the
boot SW load has completed. See Appendix E. The boot SW for further details concerning the boot
SW.
The user should press return within 10 seconds to display the login-prompt for entering the boot-
loader if access to the boot-loader is required. Otherwise, the application SW will be loaded when the
10 seconds timer has expired. The message Loading application will be shown when the
application starts to load.
4) Wait for the application software to be loaded and activated (typically takes 1-1.5 minutes).
The power LED on the front of the SatLink 85xx will blink when the SW is booting and will stay on
when the SW has successfully started. If watching the boot process on the RS-232 output, a printout
similar to this will be displayed when the SW has booted.

Extract and load firmware.............................done
Management Port MAC Address : 00:20:0e:00:9f:16
Traffic Port MAC Address : 00:20:0e:00:9f:17
DVB Interface MAC Address : 00:20:0e:00:9f:16
Retrieving configuration....done
5) At this point the Telnet server in the SatLink 85xx is started and a Telnet session can be opened for
managing the unit. Local Echo must be enabled in the Telnet Client if the input from the keyboard
shall be displayed. Recommended Telnet clients are Tera Term (see Appendix C. Tera Term
terminal emulator), PuTTY, and the built in Telnet client in Windows. Note that Local Echo by
default is set to “off” in Windows XP. Alternatively HyperTerminal or another terminal emulator
connected via the serial interface can be used (see Appendix A. Accessing the Command Line
Interface via RS-232). From this point the SatLink 85xx can also be managed via SNMP.
The SatLink 85xx can handle at most three simultaneous Telnet connections including aborted
connections. The Telnet session will be automatically terminated after 20 minutes without any
activity. If a Telnet session is refused, this can be due to all three connections being aborted. Please
wait until the timeout has expired and try again.
6) Login as the administrator user root with the factory default password admin123:
Login: root
Password: admin123
Satlink 8550
- Main board ID 108283, Revision R6.0
- SW ID 120009, Revision 13.1.0 Build 13
One must press Enter once to get the login-prompt to display if using the CLI via
RS-232. If the input from the keyboard is not displayed when typing the username
and password, check if that the Local Echo is enabled in the Telnet client.
7) The SatLink 85xx should now be ready to be configured as described in the following sub-sections.
6.2 Configuring preliminary parameters
The SatLink 85xx FLS must be configured with a few preliminary parameters to enable it to be managed
by the SatLink Hub NMS. To ensure the first time installation is done based on factory default
configuration it is recommended to delete the existing configuration (del config.txt) and restart the
SatLink 85xx. This will ensure that no unintended configuration is used. The parameters that need to be
configured by the installer are:
- SatLink 85xx IP addresses (TRF and MGMT )

- Time Server IP address and Protocol
- SNMP Configuration
6.2.1 IP configuration
The SatLink 85xx has two Ethernet interfaces. One Ethernet interface is dedicated for management
(MGMT) while the second is dedicated for user data (TRF). When the configuration has been completed,
both shall be connected to their respective Ethernet switch in the hub rack.
1) Set the MGMT-LAN IP address of the unit (management interface)

– Enter the CLI command ip set 1 <aaa.bbb.ccc.ddd> <eee.fff.ggg.hhh>
where <aaa.bbb.ccc.ddd> is the IP address and <eee.fff.ggg.hhh> the netmask.
Example:
# ip set 1 10.10.10.70 255.255.255.0
2) Set the TRF-LAN IP address (user data interface) of the unit:

– Enter the CLI command ip set 2 <aaa.bbb.ccc.ddd> <eee.fff.ggg.hhh>
where <aaa.bbb.ccc.ddd> is the IP address and <eee.fff.ggg.hhh> the netmask.
Example:
# ip set 2 10.10.11.20 255.255.255.0
3) Set the IP address configuration for interface 13 on NMforms under FLS ->IP Encapsulator tab on
Virtual Management IP Address with Virtual Management Subnet Mask set as 24 as shown in the
following figure:
Figure 10 : NMForms FLS Window
This IP address is configured automatically on FLS by FlSup on interface 13 with status as volatile in
order to enabling moving this virtual IP address between FLS units when NMS performs FLS
redundancy switcing.
4) Set the IP address configuration for interface 15 on NMforms under FLS->IP Encapsulator tab on
Traffic IP Address with Traffic Subnet Mask 24.This IP address is configured automatically on FLS
by FlSup on interface 15 with status as volatile so that it can be used on its spare.
It is recommended to configure IP addresses on all interfaces according to the

generic routing table in 200063 Generic Addressing and Routing for the DVB-RCS-
Networks document.
5) Verify that the IP addresses and netmasks are set correctly:

– Enter the CLI command ip show
Example:
If the values above have been configured the ip show command shall give the following result.
(Interface 1 is the MGMT-LAN interface, interface 2 is the TRF-LAN (user data interface):
# ip show
Interfaces
If IPAddress SubnetMask BroadCastAddr MTU Alias AdminStatus
1 10.10.10.72 255.255.255.0 10.10.10.255 1500 eth0 1
2 10.10.11.24 255.255.255.0 10.10.11.255 1500 eth1 1
3 N/A N/A N/A 4074 air0 1

4 N/A N/A 255.255.255.255 4074 dvb0 1
13 10.10.10.110 255.255.255.0 10.10.10.255 1500 Vir3-eth0 1 -
volatile
15 10.10.11.26 255.255.255.0 10.10.11.255 1500 Vir4-eth1 1 -
volatile
Interface Statistics
------------- Input ----------------- ------------- Output ----------------
If UCast NUCast Disc Octets UCast NUCast Disc Octets
1 32458 6493 106 9991818 5436 24 0 759151
2 187 1581 106 138833 0 20 1 1140
3 0 0 0 0 0 0 0 0
4 0 0 0 0 177 0 0 34716
13 0 0 0 0 0 0 0 0
15 0 0 0 0 0 0 0 0
IP Receive Deliver Errors Discards Forward Request NoRoute Discards
34026 33798 8 8 220 5469 0 10
Routing Table
DestMask RouteMask NextHop If
0.0.0.0 0.0.0.0 0.0.0.0 4
10.10.10.0 255.255.255.0 0.0.0.0 1
10.10.11.0 255.255.255.0 0.0.0.0 2
#
Ensure that the correct routes have been automatically defined to the MGMT and TRF LANs (in this
example that the destination mask 10.10.10.0 with route mask 255.255.255.0 is defined for the MGMT-
LAN interface).
6) Test the MGMT interface by pinging the MGMT router or any device connected to the MGMT LAN.
– Enter the CLI command: ping DEVICE_IP_ADDRESS
Test the TRF interface by pinging the TRF router or any device connected to the TRF LAN.
– Enter the CLI command: ping DEVICE_IP_ADDRESS
7) Test the router interface by pinging router.

- Enter the CLI command: ping ROUTER_IP_ADDRESS e.g. ping 10.10.11.4
8) Test the connection to DB server by pinging the DB server.

- Enter CLI command: ping DB-SRV-APPL e.g. ping 10.10.10.6
9) Test the connection to NCC gateway.

- Enter CLI command: ping NCC-GATEWAY-IP ADDRESS e.g.ping 10.10.10.138 (FLI)
and ping 10.10.10.140(NCCGW_00)
10) Test the connection to NMS Host.

- Enter CLI command: ping NMS-HOST-IP ADDRESS e.g. ping 10.10.10.4(Enterprise
class hub) and Ping 10.10.10.25 (Carrier class hub)
11) Save the IP configuration to Flash
Enter the CLI command: save config
– Example:
# save config
Saving Configuration. This will take ~20 secs
# Configuration Saved
6.2.2 Configuring the Time Server IP address and Protocol
In order to retrieve the UTC time from a Time Protocol (TP) server, the SatLink 85xx is configured by
default with the following parameters:
• Primary TP server IP address: 10.10.10.30
• Secondary TP server IP address: 10.10.10.31
• Selection of UDP or TCP option: UDP
Verify the settings by typing the CLI command tpserver show and type save config to save
the configuration.
The configuration steps described below shall be followed if it is required to modify the default
configuration:
1) Enter the CLI command tpserver ipaddr 1 <primary>, where <primary> is the primary
TP server IP address.
2) Enter the CLI command tpserver ipaddr 2 <secondary>, where <secondary> is the
secondary TP server IP address.
3) Enter the CLI command tpserver proto <tcp|udp> to select the protocol used to
communicate with the TP server.
4) Type save config to save the configuration.
Example:
#tpserver ipaddr 1 10.10.10.30

#tpserver ipaddr 2 10.10.10.31
#tpserver proto udp
#tpserver show
Time Server Ip Address1 : 10.10.10.30
Time Server Protocol : UDP
6.2.3 SNMP Configuration
The following SNMP configuration must be performed locally on the SL85xx FLS using CLI in order to
enable automatic configuration and monitoring of the SL85xx FLS from SatLink Hub NMS.
1. Set the SNMP community public to Read/write
The community name must be identical to the community name configured in NMforms. The SNMP
community name can be set on NMforms under ConfigurationNetworkSystem Parameters as
shown in the following figure:
Figure 11 : NMForms System Parameters Window

Example:
#
SNMP management access:

-----------------------
Community String Access IpAddress Subnet
private Read/Write 0.0.0.0
0.0.0.0
public Read/Write 0.0.0.0
0.0.0.0
SNMP Trap Destination
Trap Dest Ip Port Community Version
---------------------------------------------------------------------
10.10.10.25 162 public SnmpV2
2. Set SNMP trap destination
device snmp trapdest add
Setting SNMP trap destination for Carrier Class hub:
Example:
#
device snmp trap add 10.10.10.25 public
All SNMP traps will be displayed on the OpManager alarm viewer. For carrier class hubs OpManager is
by default installed on MGMT-SRV-00 with IP address 10.10.10.25.
Setting SNMP trap destination for Enterprise hub:

Example:
device snmp trap add 10.10.10.16 public
For Enterprise hubs OpManager is by default installed on workstation WKST-00 with IP address
10.10.10.16.
After configuring the SNMP parameters for SatLink 85xx FLS make sure that the SNMP access from
NMS to SatLink 85xx is working correctly using the following procedure:
1. Check the FLS configuration using CLI command fls show and make sure that all the
parameters are successfully configured.
2. Make sure that the community type on NMforms is same as that of the FLS community type.
Once the configuration for IP, TP server and SNMP has been completed, save the configuration using the
CLI command # save config.
6.3 FLS Line-up

The correct frequency and power level for TX signal can be verified using CW transmission and
connecting the output of FLS to the spectrum analyzer. The following procedure can be used to verify the
correct power and frequency level for TX signal:-
1. Connect the FLS output to the spectrum analyzer.

2. Turn off the FLS transmission by using the CLI command # fls off.
3. Start transmitting the CW using the CLI command # dvb tx cw on.
The frequency and power level of the CW displayed on the spectrum analyzer should be same as on the
NM form for this FLS.
The following procedure is used to verify the power and frequency level for TX signal using PRBS
transmission:-
1. Connect the FLS output to the spectrum analyzer.

2. Turn off the FLS transmission using the CLI command # fls off.
3. Start transmitting the PRBS using the command # dvb tx prbs on.
4. Check the status using the CLI command # dvb tx show.
6.4 Configuring FLS parameter in SatLink NMS

The following FLS parameters are controlled by the SatLink Hub NMS through FLSup and configured
automatically to the SatLink 85xx FLS:
• L-band transmit power level
• RF TX frequency
• Transmit Symbol rate
• Transmit MODCODs
• DVB-S2 Mode: ACM, VCM or CCM
• NCR PID
• IPE PIDs
• DVB route record
• Rate control record for PID and MAC
• Frame length
• Roll Off
• Pilot
All the above mentioned parameters are configured using NMforms. For further information on
configuring these parameters in NMforms, please refer to SatLink Hub Operators Guide Section 14.2
FLS and NIT table.
6.5 Redundancy
The SatLink HUB supports the following redundancy schemes for the FLS:
• Non-redundant
• 1:1 redundant
• N:M redundant
Non-redundant : A unique IF ID is specified and FLS Mode is set to “Non-redundant”
1:1 Redundancy: The same IF ID is used for the pair and FLS Mode is set to Operational for
primary FLS, and the corresponding FLS is set to Spare.
SL 8550/8560 (Active) Tx
75
Combiner
Tx
SL 8550/8560 (Spare)
75
Figure 12 : 1:1 Redundancy
N: M Redundancy: The same IF ID is used for all the FLSs. The FLS Mode is set to Operational for
all the FLSs to be carrying traffic and Spare for the FLS to be the backup FLS of
the others.
SL 8550/8560 (Active) TX
75
TX
SL 8550/8560 (Active) 75 Combiner
SL 8550/8560 (Spare) TX
75
Figure 13 : 2:1 Redundancy
Pickering switch is used if the FLS is using multiple TX antenna ports (N: M mode).
The FLS can be in any of the below mentioned modes depending on its configuration:
• OPERATIONAL
An FLS configured as OPERATIONAL will be the active FLS in a redundant set-up. The
operational FLS shall be configured with a unique IF ID. Multiple FLSs can be defined as
OPERATIONAL at the same time, allowing for an N: 1 or more generally N:M redundancy
scheme. The FLS can be defined either with the same or with different IF IDs, i.e. FLSs are
serving the same or different Satellites/Beams.
• SPARE
An FLS in SPARE mode will only be active if the OPERATIONAL FLS is in ERROR status
or MAINTENANCE mode. The configuration of the FLS topology is set in NM forms.
• NON-REDUNDANT
Used for FLSs running in a non-redundant mode.
• MAINTENANCE
May be used to perform work on an OPERATIONAL FLS. A SPARE FLS in active status
will not switch back to an OPERATIONAL FLS in MAINTENANCE mode. e.g. if the
power is switched off at the OPERATIONAL active FLS and the mode is set to
MAINTENANCE in NM form, the FLS will come up as IDLE when rebooted.
For information on configuring the different modes for FLS on NM form please refer to the section 14 in
104980 SatLink Hub Operators Guide.
On the basis of FLS mode, the following FLS statuses are available:
FLS Mode Mode Status

Non-Redundant Non-Redundant Active
Error
Maintenance
Redundant Operational Active
Idle
Error
Spare Active
Idle
Error
Maintenance
Table 7 : FLS Status Table
6.5.1 SatLink 85xx Redundancy Switching
This section explains the redundancy switching i.e. switchover and switchback for the SatLink 85xx FLS.
The following process of redundancy switching is explained with FLS-00 and FLS-01 being configured
in 1:1 redundant mode as shown in fig.10.
The status of FLS-00 is active and it is in operational mode. Whereas the status of FLS-01 is idle and it is
in spare mode. FLSup triggers the automatic switchover as soon as it detects the status change (from
active to error) on operational FLS (FLS-00) i.e. if primary FLS fails or reports an error. The switch over
changes the status of spare FLS (FLS-01) from idle to active and the primary FLS (FLS-00) will show
error status.
Once the error on primary FLS is resolved, the FLSup will update the status (from error to idle) for
primary FLS (FLS-00). The status of primary FLS (FLS-01) needs to be changed from idle to active as
the system is running in degraded mode. The status of primary FLS is changed from idle to active by
doing manual switch back. To do the manual switch back follow the below mentioned procedure:
1. Change the status of operational and spare FLS’s on NM form as per the below mentioned table:
Mode From To
Operational Idle Active
Spare Active Idle
Table 8 : Switch Back Table
By performing the manual switch back, the FLS (FLS-00) will get back to its original mode and status i.e.
operational and active.
Manual switchover:
The manual switchover is used only if the operational FLS (FLS-00) needs some maintenance. The
manual switchover can be done by changing the mode from operational to maintenance on primary FLS
(FLS-00). The FLSup detects this status change and updates the status (from idle to active) on spare FLS
(FLS-01). After the maintenance on primary FLS is completed, it is recommended to change the mode on
(FLS-00) from maintenance to operational before doing switchback. The status of primary FLS (FLS-00)
needs to be changed (from idle to active) by doing manual switch back. To do the manual switch back
follow the below mentioned procedure:
1. Change the status of operational and spare FLS’s on NM form as per the below mentioned
table:
Mode From To
Operational Idle Active
Spare Active Idle
6.6 Checking the FLS Status

After configuring the SatLink 85xx as per the procedure mentioned in the previous sections check the
FLS status in NMforms. The FLS status in NMforms can be seen on Equipment tab under Configuration-
>FLS Config->FLS and NIT as shown in the following figure:
Figure 14 : NMForms FLS Status Check

Parameter Description
FLS ID Identifies the Forward Link.
Description Name of the Forward link or beam.
Operational / Spare / Non-Redundant / Maintenance. Set
FLS Mode to Operational for active FLS, and spare for the
redundant partner.
Display the current status of the FLS. Should be Active
FLS Status
for the Operational FLS and Idle for the Spare.
When a SPARE FLS is ACTIVE, this parameter
Stand-in- for FLS ID
identifies the FLS that the spare FLS is stand-in for.
IF ID Intermediate output frequency identifier.
Further it is recommended to log in to the FLS CLI to verify that the FLS is working correctly.
Type the CLI command fls show i.e.
fls show
Transmission : On
Operational Status : OK
Output mode : L-band - On
Output power : -23.0 dBm

Frequency : 1.450000 GHz
Symbol Rate : 2.000000 Msps
DVB-S2 Mode : ACM
Pilot : On
Roll off : 0.25
ACM MODCODs : MODCOD FrameLength Required SNR

7 QPSK-3/4 Long 5.1
9 QPSK-5/6 Long 6.4
14 8PSK-3/4 Long 9.3
|DVB Routes | Rate Control Records | |

MAC
|Records | PID MAC | Queues|
-------+----------+-----------+---------- |--------|
Defined: 23 | 5 | 2 | 5 | - |
Active : 0 | 0 | - | - | 1 |
Max : 5000 | 25000 | 50 | 20000 | 16382 |
----------------------------------------------------
Stream Rates (kbps):

TS Pid Max ScaledM Current CongestionFactor
0 Dummy 0 0 2881 0
1 SI 1084 1084 6 0
2 PCR 0 0 12 0
Channel Rates:
Current: 18 kbps CongestF: 100
Max : 2892 - 4337 kbps (dependent on MODCOD)
3099 kbps with current mix of MODCODs
Rate per MODCOD (kbps)

MODCOD Payload Padding
7 33 657
9 0 0
14 0 0
#
• The transmission status for the FLS should be On.
• Operational status OK.
• Output mode L-band-On.
7 Updating the SatLink 85xx SW

The flash in the SatLink 85xx can store two SW images, the current active SW and a backup version.
Users with minimum privilege level 2 may use the CLI command sw upgrade to download a new
software image from the default TFTP server. After successful download of a new software image, the
previous software version will be stored as a backup version before enabling the new software.
The procedure for upgrading the SatLink 85xx software is described below:
1. Verify the default settings for the manual software upgrade with the CLI command sw show
2. If necessary, update the default settings for the manual software update by using the CLI command
sw upgrade –default <upgraded-SW-filename> <tftp-ip-address>
3. Verify the settings with the CLI command sw show
4. Execute the SW upgrade by typing sw upgrade
Example:
# sw show
SW versions:
Boot : 9.0.0.1
Current : 13.1.0.13
Backup : 13.0.1.14
Manual SW upgrade settings:

TFTP server IP addr : 10.10.1.1
File name : new.tgz
Licenses for SW options:

LOW-SYMBRATE
15Msps
20Msps
25Msps
QOS-4
HEAD-COMP
TOOL
ACM
8PSK
16APSK
# sw upgrade
Software download in progress, please
wait..................................................................
......................................................................
......................................................................
......................................................................
......................................................................
...............................................File Transfer complete
Software download completed - Preparing to restart the unit
Configuration Saved
The SatLink 85xx then reboots automatically and prints the following message:
Boot-loader
SW ID 105898, Revision 9.0.1.1
128 MB RAM test passed OK
Filesystem information table initialisation Please Wait....done

237 sectors ,31064064 Byte used
Loading application.............Shutdown Boot

Enable reset and jump to start address: 0xc0000
Satlink 8550
- Main board ID 108283, Revision R6.0
- SW ID 120009, Revision 13.1.0 Build 13

Extract and load firmware.............................done
Management Port MAC Address : 00:20:0e:00:9f:16
Traffic Port MAC Address : 00:20:0e:00:9f:17
If the configuration fails to be saved after the software upgrade is completed, the
SatLink 85xx will not reboot. A manual restart initiated by the hub operator is
needed to finalize the upgrade.
7.1 Restoring the backup software
If it is necessary to restore the old software, the following steps have to be executed. Please note that the
current SW will be deleted when restoring the backup SW.
1. Restore the previous SW with the command sw restore. The SatLink 85xx will restore the
old software and restart automatically.
Example:
# sw restore
Restoring backup SW 13.0.1.14Current SW 13.1.0.13 will be deleted
Do you want to continue (Y/N)?Y
Backup SW restored. Saving configuration and restarting
Saving Configuration. This will take ~20 secs
Configuration Saved
Restarting unit. Connection will be closed
Reconnect when the unit has restarted (1-2 minutes)
8 FLSup Functionality
FLSup is the NMS service that supervises the forward link subsystem (including modulators and
redundancy switching).
The FLSUP process performs the following tasks:
• Upload the configuration to the FLS from NMS after power on and after redundancy switching
• Uplink power control
• Monitor the health of the forward links, and perform switchover to spare forward link chains
when problems are detected
For further information on FLSup, please refer to SatLink Hub Operators Guide Section 14.4 FLSup.
9 Advanced statistics/status monitoring

This appendix provides the user with CLI examples and explanations for monitoring statistics and various
statuses from the SatLink 85xx.
9.1 CLI command fls show

This command can be used for retrieving the status for:
• Transmission
• Operational Status
• Output mode
• Output power
• Frequency
• Symbol Rate
• DVB-S2 Mode
• Pilot
• Roll off
• ACM MODCODs
• Stream Rates
• Channel Rates
DVB-S2 ACM mode
When the STM FLS is used in DVB-S2 ACM mode the actual MODCODs used is decided based on the
reported SNR from each VSAT. Each MODCOD has a defined minimum SNR threshold, and will only
be used for VSAT who are capable of receiving the given MODCOD.
#fls show
Transmission : On

DVB-S2 Mode : ACM
Pilot : On
Roll off : 0.25
ACM MODCODs : MODCOD FrameLength Required SNR

7 QPSK-3/4 Long
5.1
9 QPSK-5/6 Long
6.4
14 8PSK-3/4 Long
9.3
|DVB Routes| Rate Control Records | |

MAC |Records | PID MAC | Queues|
-------+----------+-----------+-----------|--------|
Defined: 5| 9| 2 | 5 | - |
Active : 4| 4| - | - | 5 |
Max : 5000| 25000| 50 | 20000 | 16382 |
----------------------------------------------------

0 Dummy 0 0 2855 0
1 SI 1084 1084 28 0
2 PCR 0 0 11 0
3 1230 4337 4337 0 100
4 1231 4337 4337 0 100
Channel Rates:
Max : 2892 - 4337 kbps (dependent on MODCOD)
3089 kbps with current mix of MODCODs
Rate per MODCOD (kbps)

MODCOD Payload Padding
7 41 753
9 0 0
14 0 0
#
DVB-S2 CCM Mode
When the FLS is configured in DVB-S2 CCM mode all transmission is done using a single MODCOD
which is never changed. .
# fls show
Transmission : On

DVB-S2 Mode : CCM
S2 ModCod : 7
Modulation : QPSK
FEC Code rate : 3/4
Pilot : On
Frame length : Long frame
Transmission mode : CCM
Roll off : 0.25
|DVB Routes| Rate Control Records | |
MAC |Records | PID MAC |
Queues|
-------+----------+-----------+-----------|--------|
Defined: 10 | 100 | 4 | 34
| - |
Active : 6 | 5 | - | -
| 6 |
Max : 5000 | 25000 | 50 | 20000 |
16382 |
----------------------------------------------------

0 Dummy 0 0 36715 0
1 SI 2000 2000 36 0
2 PCR 0 0 12 0
3 1330 36151 36151 2 100
Channel Rates:
Max : 36151 kbps
9.2 CLI command ncr show

The CLI command ncr show is used to report the NCR state. In normal state, NCR Operational Status
is reported as ok and NCR Generator state will be on. The default NCR PID is 8190.
-------------------------------------------------
NCR Generator State : on
NCR Generator State : off
NCR Operational Status : OK
NCR PID : 8190
NCR Delay offset 1 : 0 ticks
NCR Delay offset 2 : 0 ticks
Action on missing SI input : None
NCR PID should be same as configured inNMforms(set by FLSup).
9.3 CLI command ip show

The CLI command ip show and can be used for displaying:
1. IP configuration
2. IP statistics per port
3. Routing table
# ip show
Interfaces
If IPAddress SubnetMask BroadCastAddr MTU Alias AdminStatus
1 10.10.10.70 255.255.255.0 10.10.10.255 1500 eth0 1
2 10.10.11.20 255.255.255.0 10.10.11.255 1500 eth1 1
3 N/A N/A N/A 4074 air0 1
4 N/A N/A 255.255.255.255 4074 dvb0 1
13 10.10.10.58 255.255.255.0 10.10.10.255 1500 Vir3-eth0 1 -
volatile
15 10.10.11.22 255.255.255.0 10.10.11.255 1500 Vir4-eth1 1 -
volatile
Interface Statistics
------------- Input ----------------- ------------- Output ----------------
If UCast NUCast Disc Octets UCast NUCast Disc Octets
1 116765 19203 472 27111716 18068 133 0 2349626
2 6 8412 472 552029 14 110 1 7560
3 0 0 0 0 0 0 0 0
4 0 0 0 0 0 0 0 0
13 0 0 0 0 0 0 0 0
15 0 0 0 0 0 0 0 0
IP Receive Deliver Errors Discards Forward Request NoRoute Discards
124409 124414 0 0 0 18307 0 0
Routing Table
DestMask RouteMask NextHop If
0.0.0.0 0.0.0.0 0.0.0.0 4
10.10.10.0 255.255.255.0 0.0.0.0 1
10.10.11.0 255.255.255.0 0.0.0.0 2
9.4 CLI command eth show

The CLI command eth show can be used for displaying:
1. Status of the PHY device: disconnected, 100 MBps full duplex.
2. Ethernet statistics per interface.
Example:
# eth show
VLAN Configurations
VLAN Id IF Index Inter VLAN Comm
Ethernet User Priority to QoS Group mapping

Priority QoS Group
PHY device 1 : 'Kending 8721b' 100MBps Full Duplex

Dir Frames Unicast Multicast Broadcast Discards
CRC errs
RX 140088 120314 973 18801 1
0
TX 18764 18629 119 16 0
-
PHY device 2 : 'Kending 8721b' 100MBps Full Duplex

Dir Frames Unicast Multicast Broadcast Discards CRC
errs
RX 8643 6 6108 2529 1
0
TX 126 14 109 3 0
-
In this example:
• The status for the PHY device of the Management interface appears as 100 MBps full duplex,
the CRC error counter is equal to 0 which indicates that the Ethernet link for management data is
operational.
• The status of the PHY device for the Traffic interface appears as disconnected; further
troubleshooting of the Ethernet link for traffic data is required. Most likely explanations are:
o Ethernet cable disconnected
o Ethernet node connected to the TRF port is configured with a speed different than 100
Mbps full duplex or is disabled.
9.5 CLI command ipe show

The CLI command ipe show will show the Traffic PID information and Max rate configured for each
VSAT. While FLSUP is running then FLS will get the IPE configuration from NM forms.
# ipe show
MODCOD SNR
VSAT MAC QoS MaxRate Min Max offset
00:20:0e:10:08:91 0 1110000 1 23 0.0
00:20:0e:10:08:91 1 200000 1 23 0.0
00:20:0e:10:0d:7f 0 1110000 1 23 0.0
00:20:0e:10:0d:7f 1 200000 1 23 0.0
00:20:0e:10:10:68 0 1110000 1 23 0.0
00:20:0e:10:10:68 1 200000 1 23 0.0
01:00:5e:00:0b:0e 0 0 1 28 0.0
01:00:5e:00:0b:0f 0 0 1 28 0.0
MAC Rate Control record used: 8, Max: 20000
PID MaxRate Delay Threshold

1110 1110000 10 180
1111 200000 10 180
1112 1112000 10 180
1113 200000 10 180
PID Rate Control record used: 4, Max: 50
The number of queues per PID is limited to 1000. The maximum supported
number of VSATs that one SL8550 FLS can support is 5000. In this case
minimum 5 PIDs have to be used per QoS class. SL8560 FLS can support 10000
VSATs.
9.6 CLI command device show
This command will show about the hardware information for the SatLink 85xx including MAC addresses
of the Ethernet ports.
# device show
System Information:
Name : FLS-00_1st-Beam
Location : T&C_HUB_UAE
Contact : STM
System Up time : 0 days, 02:08:37
Core temperature : 65.0 degrees C.
CPU Load : 3%
System time(UTC) : 28 January 2009 09:31:02
HW:
Model : Satlink 8550
HW ID : 108294
Main board ID : 108283 R4.0
Plugin-card HW:
Model : SatLink 180
HW ID : 104032
Revision : 4.3
Serial Number : 0207070026
MAC addresses:
Management Port : 00:20:0e:00:9f:3a
Traffic Port : 00:20:0e:00:9f:3b
Satellite (DVB) : 00:20:0e:00:9f:3a
9.7 CLI command sw show

The CLI command sw show is used to check the software details like, software version, software
upgrade settings and license details..
# sw show
SW versions:
Boot : 9.0.0.1
Current : 13.1.0.13
Backup : 13.0.1.14
Manual SW upgrade settings:

TFTP server IP addr : 10.10.1.1
File name : new.tgz
Licenses for SW options:

15Msps
20Msps
25Msps
QOS-4
ACM
8PSK
9.8 CLI command tpserver show

In order to retrieve the UTC time from a Time Protocol (TP) server, the SatLink 85xx is configured by
default with the following parameters:
• Primary TP server IP address: 10.10.10.30
• Secondary TP server IP address: 10.10.10.31
• Selection of UDP or TCP option: UDP
1 The configuration steps described below shall be followed if it is required to modify the default
configuration:Enter the CLI command tpserver ipaddr 1 <primary>, where
<primary> is the primary TP server IP address.
2 Enter the CLI command tpserver ipaddr 2 <secondary>, where <secondary> is the
secondary TP server IP address.
3 Enter the CLI command tpserver proto <tcp|udp> to select the protocol used to
communicate with the TP server.
4 Verify the settings by typing the CLI command tp show and type save config to save the
configuration.
Example:
# tpserver show

Time Server Protocol : UDP
#
9.9 Frequency
Set Lband Tx center frequency.i.e. dvb tx freq xxxx
Example:
dvb tx freq <frequency>
Sets the transmitter frequency in kHz for DVB-S2 mode
• The output frequency must be of the range 950 to 1450 MHz.
10 Definitions, Acronyms and Abbreviation

8PSK 8-ary Phase Shift Keying
ACM Adaptive Coding and Modulation
BUC Block Up-Converter
CCM Controlled Carrier Modulation
CLI Command Line Interface
CSC Common Signalling Channel
CW Continuous Wave
dB DeciBel
dBm DeciBel relative to 1 mW
DNS Domain Name Service
DVB Digital Video Broadcasting
DHCP Dynamic Host Configuration Protocol
ETH Ethernet
FLS Forward Link System
GPS Global Positioning System
HW HardWare
Hz Hertz
ID IDentifier
IETF Internet Engineering Task Force
IF Intermediate Frequency
IP Internet Protocol
INT Internal
SMI Structure of Management Information
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
SPS Symbols Per Seconds
SW Software
SYNC Synchronising Channel
KSPS Kilo Symbols Per Second
LAN Local Area Network
LED Light Emitting Diode
LNB Low Noise Block
MAC Medium Access Control
MBPS Mega Bits Per Second
MCR Multi-Carrier Receiver
MGMT-LAN Management Local Area Network
MIB Management Information Base
MIPS Mega Instructions Per Second
MSPS Mega Symbols Per Seconds
NCC Network Control Centre
NCR Network Clock Reference
NM-Forms Network Management Graphical Interface
OS Operating System
PID Packet Identifier
PPS Pulse Per Second
QoS Quality of Service
QPSK Quaternary Phase Shift Keying
RF Radio Frequency1RU 1 Rack Unit
SNMP Simple Network Management Protocol
SW SoftWare
TCP Transport Control Protocol
TFTP Trivial File Transfer Protocol
TP Time Protocol
TRF Traffic Burst Type
TRF-LAN Traffic Local Area Network
Tx Transmitter
UDP User Datagram Protocol
11 References
[1] SatLink Hub Operators Manual, STM document No. 104980
[2] RFC1213-Management Information Base for Network Management of TCP/IP-based internets:
MIB-II
Appendix A. Accessing the Command Line Interface via RS-

232
In some special situations the Command Line Interface via Telnet may not be accessible or will not
output the required amount of debug information. Typical examples of such situations are:
• The SatLink 85xx is configured with an Ethernet IP address not known to the user
• One needs to enter the boot-loader
• Detailed debugging
The Command Line Interface may then be accessed from a local PC connected to the SatLink 85xx’s
RS-232 interface via a serial cable. HyperTerminal or any compatible terminal emulation program is used
to access the CLI interface via RS-232.
A.1 Cable connection

To get access to the command-line interface (CLI) via the RS-232 connection, a serial cable is connected
from the SatLink 85xx directly to a COM port on a PC:
• Plug the 9-pin connector (DB09) (male) into the rear panel of the SatLink Terminal.
• Plug the 9-pin connector (DB09) (female) into a COM port on the PC.
A.2 PC configuration of HyperTerminal to access the CLI via RS-232

In Windows, click the Start button and select All Programs > Accessories > Communications >
HyperTerminal. HyperTerminal will then start and the Connection Description dialogue box, shown in
Figure 15, will appear. The screen shot are from Windows XP Professional. Please note that other
versions of Windows may display differently.
Figure 15: Hyper Terminal New Connection dialogue box
Enter a name and select an icon for the Connection, and click OK. The Connect To dialogue box, shown
in Figure 5, will appear.
Figure 16: Hyper Terminal Connect To dialogue box
Select the COM port where the serial cable attached to the SatLink 85xx is connected, and click OK. The
COM port Properties tab will appear, as shown in Figure 16.
Figure 17: Hyper Terminal COM1 Properties property tab
Use the pull-down lists to enter:

• Bits per second: 115200
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
Click Apply to accept the properties. The property sheet will close and communication with the
SatLink Terminal may begin.
Note that it may be necessary to press the enter key to display the login prompt.
When closing the session and exiting HyperTerminal, allow the program to save the session, which will
place an icon and session name into the HyperTerminal directory on the Start menu, allowing for future
quick connections.
Appendix B. TFTP server

TFTPD32 is a freeware TFTP server for Windows 9x/NT/XP PCs
Installation description:
1. Copy the TFTP server files to a PC connected to the Hub management LAN
2. Start the program
3. Select correct server interface if using a PC with more than one Ethernet card.
4. Select correct base directory (directory where the files to be downloaded are stored, and where
uploaded files will be stored)
5. The TFTP server can now be accessed from the SatLink 85xx by using the CLI commands
upload and dload.
TFTP upload from and download to the SatLink 85xx has been tested with version 3.23 of this TFTP
server, but any TFTP server should work.
The SatLink 85xx can access a TFTP server from the management interface (MGMT-LAN) or from the
user data interface (TRF-LAN) provided that management over the user data interface is enabled.
Appendix C. Tera Term terminal emulator

A recommended freeware Telnet client is Tera Term Pro Web 3.1.3. The software can be downloaded
from Ayera home page. Especially when running Telnet from Windows XP it is recommended to use
Tera Term instead of the built in Telnet Client in Windows XP, since setting Local Echo in the Windows
XP client does not seem to work.
Figure 48: Tera Term Terminal Setup
When starting Tera Term, perform the following configuration steps:

• Select Terminal from the menu Setup.
• Select Local echo as shown in Figure 418.
• Select Save Setup from the menu Setup to save the configuration.
Appendix D. Management via SNMP

The STM SatLink 85xx FLS can be monitored and managed using the standardised Simple Network
Management Protocol (SNMP).
The management information that can be collected and controlled by an SNMP management application
is contained in so-called Management Information Databases (MIBs). The STM SatLink 85xx FLS
supports two such MIBs:
• MIB-II (relevant parts)
• STM proprietary SatLink MIB
MIBs are components in the Internet Engineering Task Force (IETF) defined Structure of Management
Information (SMI). SMI version 2 as defined by IETF STD58 is supported.
D.1 SNMP version compliance
The SatLink 85xx FLS supports SNMP version 2c as defined by IETF in RFC 1901 and RFC 3417.
In accordance with SNMPv2c, the access rights associated with the attached community name is checked
when an SNMP message arrives. The predefined access rights for the given community name together
with the predefined maximum access rights of the object ID(s) addressed by the SNMP message
determines the effective access rights. The STM SatLink 85xx FLS is also equipped with optional
enhanced SNMP access control as described later.
D.2 MIB-II supported by SatLink 85xx

The STM SatLink 85xx supports relevant parts of MIB-II (RFC1213). The following object groups of
MIB-II are supported:
• System
• Interface
• IP 1
• ICMP
• UDP
internet(1)
mgmt(2)
mib-II(1)
rfc-1213
system(1)
interface(2)
ip(4)
(1)...(19)
ipAddrTable(20)
ipNetToMediaTable(22)
ipForward(24)
rfc-2096
ipCidrRouteTable(4)
icmp(5)
udp(7)
Figure 59: Supported parts of MIB-II
1
ipRouteTable and ipRoutingDiscards are not supported, ipForward.ipCidrRouteTable (RFC2096) is
supported instead
D.3 STM FLS MIB
D.3.1 Overview of STM SatLink MIB

The STM SatLink MIB contains proprietary MIB objects that together with the supported MIB-II objects
allow the complete configuration and management of the STM SatLink 85xx FLS.
D.3.2 MIB object definitions

The STM SatLink MIB is distributed separately in the standard ASN.1 syntax text file format used for an
IETF STD58 compliant MIB. A set of MIB objects sufficient for the STM SatLink 85xx FLS is available
as a separate distribution. The current version of the STM SatLink MIB is 200812291200Z.
enterprises(1)
stmNetworksIncMib(24386)
stmDvbRcs(50)
fls8550(6)
dvbSystem (1) dvbTx(3) dvbIp(5) dvbNcrGen(6) dvbEthernet(8) dvbTrap(20) trapLisClient dvbTelnet(23)

(15)
ipMulticast(1) ethVlanIf
sysHW (3) txStatis(2) Table(1) trapDestinationTable(1) telnetStatusT
ipDvbRouteTable(4) able(1)
sysSW(4) txStatistics(3) ethPriQosMa
ipIfAddrTable(6) pTable(2)
sysAccess(6) txDvbSConfig (11)
iipTpSrv(9)
sysLog(7) ipMfc((10)
sysCmd(8) ipMpe(11)
sysPerformance(
sysDeb(12)
Figure 20. The part of the STM MIB supported by the STM SatLink 85xx FLS.
D.4 Access policies

Access to the STM SatLink 85xx FLS MIBs is limited as follows: first by a restriction based on
community name and maximum access right combination, and then optionally by the SNMP request’s
source IP address and netmask and/or source interface.
When only community name and maximum access rights limit the access, then filtering in the SatLink
85xx FLS is achieved by checking the SNMP message’s community name and maximum access rights
only. Otherwise also the source IP address, netmask, and/or source interface of the SNMP message is
checked. If all these parameters of the SNMP message match the values stored in the MIB object that
controls the access rights, the SNMP message is processed. Otherwise it is discarded.
The STM SatLink 85xx FLS is configured with default community name public with read-
only access and private with read-write access when shipped from factory.
D.4.1 CLI commands for configuring SNMP access
CLI commands User Privilege Level
device snmp community <name> <ro|rw> [<ipaddr> <mask>] 1

device snmp delcommunity <name> 1
device snmp show 1
device manager add snmp <if> [<ip> <mask>] 1
device manager del snmp <if> [<ip> <mask>] 1
device manager show 1
Device snmp and device manager CLI commands only available for user with privilege
level 1 (the root user).
D.4.2 Access configuration
To be able to access the SatLink 85xx FLS MIB, it is necessary to configure both the SatLink 85xx FLS
and the MIB browser application.
1. The MIB browser application has to be configured with the correct community name both for read
access and write access.
2. The SatLink 85xx FLS SNMP access list has to be configured via CLI, using the device snmp
community command and optionally the device manager add snmp command.
Example 1:
Define an access type with the name “public”, with read-write maximum access right and with no
restriction on the SNMP request’s IP address and netmask.
# device snmp community public rw

# device snmp show

-----------------------
public Read/Write 0.0.0.0 0.0.0.0
Example 2:
Define an access type with name “user”, with read-only maximum access and with restriction to the
10.10.20.0 sub-net for the SNMP request source.
# device snmp community user ro 10.10.20.0 255.255.255.0

# device snmp show

-----------------------
normal-user Read only 10.10.10.0 255.255.255.0
Example 3:
Remove the access type with name “user”.
# device snmp delcommunity user

# device snmp show

-----------------------
D.5 SNMP Traps for SatLink 85xx

The STM SatLink 85xx FLS supports SNMP Traps V2. In order to send traps to the SNMP Manager, the
trap destination address must be configured with the IP address of the SNMP Manager.
A detailed description of alarms and events that may be reported by the STM SatLink 85xx FLS is given
in Appendix G. SNMP TRAPS and list of alarms supported.
D.5.1 Access CLI commands for configuring SNMP TRAP destination addresses
CLI commands User Privilege Level
device snmp trapdest add <manager Ip> <community 1

name>[-port <manager port> -ver <snmp version>]
device snmp trapdest del <manager Ip> 1
device snmp show 1
In order to use the “device snmp” CLI commands, log in as a user with privilege level 1
(root user)
Example:
Define a destination address for reception of the SNMP traps.
# device snmp trap add 10.10.10.16 public

# device snmp show
# device snmp show

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

operator Read/Write 0.0.0.0 0.0.0.0
SNMP Trap Destination

Trap Dest Ip Port Community Version
---------------------------------------------------------------------
10.10.10.16 162 public SnmpV1 & V2
The default manager port and SNMP version number are 162 and SNMP V2.
D.6 Setting a MIB object and saving the configuration

When the STM SatLink 85xx is shipped from the factory, the essential MIB objects of the SatLink 85xx
FLS MIB are given default values.
When changing the value of a MIB object with write access, the new value will in general be activated
when they are set. The value will apply as long as the STM SatLink 85xx FLS is powered on. If no
special action is taken to save the new MIB value, the value will revert to the default value upon power-
on.
To save a new value so that it will survive a unit power off-on, one must explicitly issue a MIB save
command by setting the MIB object sysCmdSaveConfig to 1.
Saving the configuration can take up to 20 seconds.
Appendix E. The boot SW

The SatLink 85xx FLS has two SW applications installed:
1) Boot
2) FLS Application
The Boot SW is stored outside the file system and can be compared with the BIOS and MS-DOS on a PC.
It is used to have access to file system and the LAN when there is no application loaded on the SatLink
85xx.
The Boot SW is always loaded after powering on the SatLink 85xx. But normally the user need not care
about the boot SW since the application SW is loaded by default.
The boot-loader can only be accessed via RS-232 as described in Appendix A. Accessing the Command
Line Interface via RS-232. After power on, an output similar to this is displayed on the HyperTerminal:
Boot-loader
- SW ID105898, Revision 9.0.1.1

In order to logon and use the boot SW, press return (the software will wait 10 seconds before
automatically loading the application SW):
1. When Login is displayed type the user name root

2. When Password is displayed type admin123
In the boot-loader there is available a minimal CLI supporting the file system commands and access to the
MGMT LAN. Type ? (Question mark) to display the available CLI commands.
Appendix F. Troubleshooting
F.1 Frequently Asked Questions (FAQ)
Question Answer
1. I see a lot of Time server not responding STM has experienced similar problems with some
alarms logged with severity minor by the Time Server. The SatLink 85xx only need to
SatLink 85xx. retrieve the time during the initialisation phase.
Once configured, the SatLink 85xx continue to
pool the Time Server every 20 seconds and an
event is logged each time the response timeout.
This does not affect the performance of the
SatLink 85xx.
2. How do I load new Software on my SatLink See description in chapter 7.

85xx?
3. SI input missing Check if the correct IP addresses have been
assigned to interface 13 and 15.
4. I cannot find the answer to my question in Contact the System Operator or STM at
the list above satlink.support@stmi.com
F.2 Troubleshooting with LEDs

The SatLink 85xx supports front and rear panels LEDs that may be used to give a rapid operating status
of the unit as described in the paragraph below.
LED Description/Action
TX rear panel LED The TX rear panel LED may be in one of the following states:
1. The LED is off when no TX signal is detected by the SatLink 85xx
or the signal level is below the minimum input level required by the
receiver.
2. The LED is on when the TX signal level is within the operating
range.
3. The LED is blinking when the TX signal level is above the
maximum input level.
The TX input level shall be adjusted in case the LED is not in state 2.
Sync front panel LED The SYNC front panel LED will flash with 1 second interval once the
SatLink 8550 has synchronised with the 10 MHz external reference, the
1 PPS external references and has retrieved the UTC time for the TP
server.
If it is not the case, use the alarm LED and rear panel LEDs to
troubleshoot further the problem. Either there is a problem with the 10
MHz, 1 PPS reference or the SatLink 8550 is not able to retrieve the
UTC time from the TP server.
Troubleshooting with SatLink 85xx LEDs
The following rear and front panel LEDs apply to SatLink 8550 only:
F.3 Boot of SatLink 85xx without config- and application files
In case the SatLink 85xx is booting without a valid config.txt file and without application SW file stored
in the file system, the following default MGMT LAN configuration is restored from flash:
o IP-address 10.10.1.3
o subnet mask 255.0.0.0
F.4 Manual software upgrade or dload fails

Manual software upgrade or download of file using CLI command dload may fail if there is not
sufficient available memory in the SatLink 85xx file system. This is likely to happen when too many files
have been downloaded to the file system without deleting the older backup images.
The SatLink 85xx file directory normally contains two application files, namely:
• Fls_85xx-X.X.X.X.tgz 2 The current application SW
• xxx.bak The back-up application SW
in addition to the smaller configuration and log files.
To view the SatLink 85xx file directory, type the CLI command dir. There should not be more than the
above listed application files.
Example:
#
dir
FileName Size Date Time
oldLog.txt 9806 00/00/0000 00:00:50
activeLog.txt 5542 00/00/0000 00:00:49
fls_8550-13.1.0.10.tgz 3488493 27/01/2009 11:27:50
xxx.bak 3487060 25/01/2009 10:39:43
config.old 11032 27/01/2009 11:27:55
config.txt 10997 00/00/0000 00:00:50
If the directory list reveals that there are other large files present, please delete these files using the CLI
command del and retry the manual sw upgrade (or dload) procedure.
F.5 Collecting information if a problem occurs

If a problem occurs with the SatLink 85xx for which support might be needed, having the information
listed below available will be helpful.
1. The unit log from the HyperTerminal Window.

If possible log the output from the unit to the HyperTerminal Window when the problem occurs.
The output from the HyperTerminal window can either be copied to a text file by setting the capture
text options in HyperTerminal (-> Transfer -> Capture Text) or copied directly from the
HyperTerminal windows using the normal Windows copy function (CTRL+C). The content can then
be pasted in a text editor such as Notepad or Word to generate a file suitable for being included as an
e-mail attachment.
When logging to HyperTerminal please issue the following CLI commands and capture the output.
ip show
2
The name may differ, but the extension will be “tgz”.
eth show
dvb tx show
ncr show
fls show
test tx
ncr show –si
sw show
log show
test memory
test memory all
dir
2. The unit configuration file, config.txt.
If possible please upload the configuration file to a PC with a TFTP server using the CLI command
upload config.txt <TFTP-Ipaddress> [<remotefilename>], where TFTP-
Ipaddress is the IP address for the TFTP server and remotefilename is an optional parameter
specifying the filename to store the file as on the TFTP server if a different name than config.txt is
wanted. Please refer to 0 for an example of how to install and set up a TFTP server.
If it is not possible to upload the unit configuration file to a TFTP server the config.txt file might be
dumped to the RS-232 port / HyperTerminal by using the CLI command type config.txt. The
output from the HyperTerminal Windows can then be copied to a text file or dumped using the
capture text feature of the HyperTerminal.
F.6 List of events that may be logged

The following are the most common events that may be shown in the log from the SatLink 85xx FLS.
Use the CLI command log show to display the list of events stored in memory and the CLI command
type activeLog.txt to 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 Critical
normally will require user intervention in order to recover.
Event Severity User action Comment

required
Memory Minor Restart the The SatLink 85xx software application failed
Allocation SatLink 85xx to allocate memory. Note that for some
Failed scenarios, memory allocation failure might
not necessarily affect the performance. If the
service is corrupted, reboot the SatLink 85xx.
If the problem persists, contact STM.
Memory Pool Minor Restart the The SatLink 85xx software application failed
Allocation SatLink 85xx to allocate memory. If the service is
Failed corrupted, reboot the SatLink 85xx. If the
problem persists, contact STM .
CRU Buffer Minor Restart the The SatLink 85xx software application failed
Allocation SatLink 85xx to allocate memory. Note that for some
Failed scenarios, CRU buffer allocation failure
might not necessarily affect the performance.
If the service is corrupted, reboot the SatLink
85xx. If the problem persists, contact STM.

required
Unit Major Verify The SatLink 85xx detects that its internal
Temperature environmental temperature is high and will turn on the FAN
High temperature and to full speed.
that the FAN is
operational.
Unit Critical Verify The SatLink 85xx detects that its internal
Temperature environmental temperature is too high and above the
Critical temperature and maximum allowed threshold.
that the FAN is The unit will reboot to cool down the board.
operational. Verify that the room temperature where the
SatLink 85xx is within the normal operating
range. Should the problem persist, the unit
should be returned to STM for repair.
File not found Major Verify that the The SatLink 85xx is not able to upload the
file is present on file specified in the command from the TFTP
the TFTP server server.
and that the TFTP
server is pointing
to the correct
directory.
File transfer Major Check available The File transfer has been aborted either due
error space on file to an IP connection interruption between the
system SatLink 85xx and the TFTP serve or due to a
lack of available space on the SatLink 85xx's
file system.
SW checksum Major Check validity of A checksum error is reported on the
error *.tgz file. application *.tgz file downloaded during the
Try to reload the software upgrade. The file will be deleted
*.tgz-file. and the software upgrade will be aborted.
If the problem persists, contact STM.
Manual SW Normal None Successful SatLink 85xx software upgrade
upgrade via TFTP.
completed
NCR Error Major Verify The SatLink 85xx is not lock with 1PPS and
Management 10 MgHz and its not sync with the time
Network LAN server Then check the coaxial cxable s for 1
and 1 PPS and 10 PPS and 10 MgHz , also check the
MgHz are locked. management network connection to sync
Confirm the with the time server
server sync with
the time server .
Firmware Critical Restart the The SatLink 85xx is not able to load the
download Error SatLink 85xx. firmware into the FPGAs.
The SatLink 85xx should be returned to STM
for repair.
Firmware DCM Critical Check the FPGAs DCM are not able to achieve lock.
unlock hardware integrity Check the 10 MHz reference. The SatLink
85xx should be returned to STM for repair.
10MHz clock Critical Check 10 MHz 10 MHz reference is lost.
missing external reference Check that the external reference is within
the specification for the SatLink 85xx.

required
1PPS Missing – Critical / Check 1 PPS The 1PPS reference is lost.
cannot start Normal external Check that the external reference is within
NCR reference the specification for the SatLink 85xx.
This event can be classified as :

- Critical : The SatLink 85xx is in
configuration state and need the 1 PPS to
be present to proceed to synchronization.
- Normal : The SatLink 85xx is in
operational state. A missing 1 PPS signal
will not affect the performance of the
product.
10MHz clock OK Normal None 10MHz reference has been recovered.
1 PPS OK Normal None 1PPS reference has been recovered.
Ethernet Critical Check the TRF The SatLink 85xx detects no link activity on
Traffic port interface link the TRF Ethernet interface.
disconnected speed and verify
that the Ethernet
cable is correctly
connected
Ethernet Normal None Link activity on the TRF Ethernet interface
Traffic has been detected again
connected
Unit has Major None Logged following a unit restart.
restarted
No response Critical / Check the validity Check the consistency of the TP client
from Time Normal of the TP server configuration in the SatLink 85xx.
server IP address Check the Ethernet connection from the
SatLink 85xx to the TP server.
This event can be classified as :

- Critical : The SatLink 85xx is in
configuration state and need a response
from the Time Server to proceed to
synchronization
Normal : The SatLink 85xx is in operational
state. A missing response from the Time
Server will not affect the performance of the
product.
Tftp server Critical Check IP The SatLink 85xx is not able to establish the
unreachable connection with connection with the TFTP server.
the TFTP server This is likely to be due to an IP configuration
or network problem. Verify the IP connection
with the TFTP server by pinging the server
from the command line interface.
List of events logged by the Event logger
Appendix G. SNMP TRAPS and list of alarms supported
The following section gives a general description of alarms that may be reported with SNMP TRAPS by
the SatLink 85xx.
G.1 Alarm Format

An alarm describes a situation that is persistent. An alarm is reported to the SNMP TRAP manager with
the following format:
Severity: Each alarm must be classified in one of the following severities:

Critical Failure affecting half (or more) of the SatLink Hub traffic capacity, or if
applicable, failure affecting half (or more) of the SatLink Hub traffic
capacity for a given coverage area.
Major Failure affecting less than half of the SatLink Hub traffic capacity.
Minor Failure not affecting the SatLink Hub traffic capacity.
Message: Text that is presented to the SatLink Hub operator when an alarm is raised.
G.2 Alarm Definitions
Alarm: TimeSrvNotResponding
Severity: Critical
Message: None of the configured TP servers is responding, NCR generator cannot start.
Action:
Alarm: LostExtClock
Severity:
Message: The 10 Mhz input not detected.
Action: Make sure that the 10 MHz cable is connected to FLS.
Alarm: 1PPS Missing
Severity: Critical
Message: The 1 PPs input not detected, NCR generator cannot start.
Action: Make sure that 1PPS cable is connected to FLS.
Alarm: TXFifoUnderflow
Severity:
Message: CPU not filling sufficient data.
Action:
Alarm: EthTrfMissing
Severity:
Message: Ethernet traffic port not connected.
Action: Make sure that Ethernet traffic cable is connected to FLS.
Alarm: SIInputTrfError
Severity:
Message: Continuity error or duplicates in SI table input above 1 %.
Action:
Alarm: SIInputTrfMissing
Severity:
Message: No SI table input.
Action:
Alarm: EthRxPacketDrop
Severity:
Message: More than 1 of 1000 packet dropped on traffic Ethernet.
Action:
Appendix H. Cable Specification

This appendix provides the cable specification for the cables to be used between SatLink 85xx FLS and
BUC/Up Converter and time server. Three separate cables are required; one cable for the transmitting
signal (Tx) signal and two cables for the 10 MHz and 1 PPS external references.
H.1 TX L-band Cable Requirements
Frequency range: 950 – 1450 MHz

Impedance: 75 Ohm
Connectors: RF-M-type
H.2 10 MHz- 1PPS Cable Requirements
Frequency range: DC-10MHz

Impedance: 50 Ohm
Connectors: SMA male for cables RG141
Cable model: RG141
Appendix I. Advanced configurations

This appendix provides the user with configuration examples if changes to the standard configuration are
required. Normally these settings are set automatically by the SatLink Hub NMS. Doing manual
configuration of these parameters may cause incompatibilities with the SatLink Hub NMS and should
only be done in special cases where e.g. the SatLink 85xx is used without management from the SatLink
Hub NMS.
I.1 IPE PID Configuration
In order for the SatLink 85xx FLS to forward user traffic, at least one traffic PID must be configured in
the PID table.
1) Enter the CLI command ipe pid <pid> <maxrate> [<packing delay> <packing
threshold>], where <pid>, is the traffic PID value.
2) Verify the settings by typing the CLI command ipe show and type save config to save the
configuration.
Example:
# ipe pid <pid> <maxrate> [<packing delay> <packing threshold>]

# ipe pid <pid> -del
# ipe show
MODCOD SNR
VSAT MAC QoS MaxRate Min Max offset

00:20:0e:10:08:91 0 1110000 1 23 0.0
00:20:0e:10:08:91 1 200000 1 23 0.0
00:20:0e:10:0d:7f 0 1110000 1 23 0.0
00:20:0e:10:0d:7f 1 200000 1 23 0.0
00:20:0e:10:10:68 0 1110000 1 23 0.0
00:20:0e:10:10:68 1 200000 1 23 0.0
01:00:5e:00:0b:0e 0 0 1 28 0.0
01:00:5e:00:0b:0f 0 0 1 28 0.0
MAC Rate Control record used: 8, Max: 20000
PID MaxRate Delay Threshold

1110 1110000 10 180
1111 200000 10 180
1112 1112000 10 180
1113 200000 10 180
PID Rate Control record used: 4, Max: 50
Queue Rate calc interval: 15 sec

Drop waring Threshold: BE: 50 %%, VoIP: 50 %%, ViC: 10 %%, CD: 10 %%,
The example above shows how to delete IPE PID, how to configure IPE PID as a standard PID for the
forward link traffic and how to display the content of the IPE PID table configuration.
I.2 Setting Symbol Rate
Set the symbol rate i.e. dvb tx symbrate xxxx
Example:
dvb tx symbrate <frequency>
Sets the transmitter symbolrate in symbols/second for DVB-S mode
• The range for symbol rate is 1 to 25 Msps
I.3 MODCOD Configuration
Two types of MODCODs can be configured using the SatLink 85xx FLS. These are:
1. CCM
2. ACM
1. Set CCM
Example:
dvb tx ccmmodcod
USAGE:
dvb tx ccmmodcod <modcod>
modcod DVBS2 MODCOD:

1: QPSK 1/4, 2: QPSK 1/3, 3: QPSK 2/5, 4: QPSK 1/2
5: QPSK 3/5, 6: QPSK 2/3, 7: QPSK 3/4, 8: QPSK 4/5
9: QPSK 5/6, 10: QPSK 8/9, 11: QPSK 9/10 12: 8PSK 3/5,
13: 8PSK 2/3, 14: 8PSK 3/4, 15: 8PSK 5/6 16: 8PSK 8/9,
17: 8PSK 9/10 18: 16APSK 2/3, 19: 16APSK 3/4, 20: 16APSK 4/5,
21: 16APSK 5/6 22: 16APSK 8/9, 23: 16APSK 9/10
Set the TX MODCOD for CCM mode
2. Set ACM
Example:
dvb tx acmmodcod
USAGE:
dvb tx acmmodcod <modcod> <frameLength> [<RequiredSNR>]
dvb tx acmmodcod <modcod> -del
modcod DVBS2 MODCOD:

1: QPSK 1/4, 2: QPSK 1/3, 3: QPSK 2/5, 4: QPSK
1/2
5: QPSK 3/5, 6: QPSK 2/3, 7: QPSK 3/4, 8: QPSK
4/5
9: QPSK 5/6, 10: QPSK 8/9, 11: QPSK 9/10 12: 8PSK
3/5,
13: 8PSK 2/3, 14: 8PSK 3/4, 15: 8PSK 5/6 16: 8PSK
8/9,
17: 8PSK 9/10 18: 16APSK 2/3, 19: 16APSK 3/4, 20: 16APSK 4/5,
21: 16APSK 5/6 22: 16APSK 8/9, 23: 16APSK 9/10
RequiredSNR Required SNR reported to use this MODCOD in dB

Range -2.0 .. 23.5 dB
frameLength FEC frame length: long , short or both long and short
allowed
long, (also called normal)
short
both, The FLS will automatically select long or short
-del Delete the modcod from the table
Set the TX MODCODs for ACM mode
SW licenses is required to set the DVB type as ACM and change the MODCOD
from QPSK to 8 PSK.
I.4 Output Power Rate
Set Tx output power rate i.e. dvb tx outpow xx
Example:
dvb tx outpow <pow>
Configure the TX output power [dBm]
pow TX output power in 0.1dBm resolution, legal range -35 to 0
Example:
dvb tx outpow -5.5 sets the IDU output power to -5.5 dBm
• The range for output power is -35 to -5 dbm.
I.5 RollOff Factor Configuration
Set the Tx RollOff
Example:
dvb tx rolloff
USAGE:
dvb tx rolloff <fact>
fact 35 : 0.35
25 : 0.25
20 : 0.20
Set the Rolloff factor
I.6 DVB-S2 Mode
Set the DVB S2mode
Example:
dvb tx s2mode
USAGE:
dvb tx s2mode <ccm|vcm|acm>
Set the DVB-S2 mode
I.7 Setting Frame Length
Set the CCMFrame Length
Example:
dvb tx ccmframelength
USAGE:
dvb tx ccmframelength <long|short>
Set the TX FEC frame length for CCM mode
I.8 Setting NCR PID
Set the NCR PID in the ncr i.e. ncr pid <value>
Example:
ncr pid <value>
To set the NCR Generator pid value pid values (0 - 8190).
Appendix J. Compliance
J.1 SatLink 85xx Compatibility
The SatLink 85xx comply with the essential requirements of Article 3 of the R&TTE 1999/5/EC
Directive, if used for its intended use.
J.1.1 Safety (Article 3.1.a of the R&TTE Directive)

This equipment has been designed and tested to meet the requirements of the following standards:
• EN 60950-1:2001 + A11:2004
• EN 60950-1:2001 First Edition
J.1.2 Electromagnetic compatibility (Article 3.1.b of the R&TTE Directive)
This equipment has been designed and tested to meet the requirements of the following standards:
• EN 301 489-1:V.1.6.1 :2005
• EN 301 489-12:V.1.2.1 :2003
• EN 301 489-1-V1.4.1 (2002-08) EMC standard for radio equipment
• EN 301 489-12-V1.2.1 (2003-05) Specific conditions for Fixed Satellite Service.

Manual

Uploaded by

Copyright:

Available Formats

You might also like

Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual

Uploaded by

Copyright:

Available Formats

Networks without Barriers

SatLink 8550/8560 FLS

STATEMENT OF CONFIDENTIALITY / DISCLAIMER

© Copyright 2009-2010 STM Group, Inc. All rights reserved.

APPENDIX B. TFTP SERVER ....................................................................................................42

Figure 1: SatLink 8550

1.1 About This User Guide

Satlink 8560 Software

SatLink 85xx HW models

1.2 Installation and Configuration overview

Figure 2 : Typical Satlink Hub Configuration

System malfunction may occur if the warning-information is violated.

3.1.1 Safety Measures

• Always comply with national and local electrical codes.

Follow these guidelines when working with electrical equipment:

Should an electrical accident occur:

• Be cautious – do not become a victim yourself.

3.1.2 Site requirements

3.2 SatLink 85XX front and back panels

3.2.1 SatLink 8550/8560 front panel

Figure 3: SatLink 8550 front panel

Figure 4: SatLink 8560 front panel

LED Colour, indicates

Table 1: SatLink 8550 front-panel LEDs

LED Colour, indicates

Table 2: SatLink 8560 front-panel LEDs

3.2.2 SatLink 8550/8560 back panel

Figure 5: SatLink 8550 back panel (SatLink 180 mounted)

Figure 6: SatLink 8560 back panel

3.3 SatLink 85xx Installation

3.3.1 In rack mounting

Figure 7: Rack Mounting

3.4 Interface Connections

3.4.1 Main connection

3.4.2 Tx cable between the SatLink 85xx and BUC or Up Converter

It is strongly recommended to configure all Ethernet devices connected to the

3.4.4 10 MHz and 1PPS interface

Figure 8: STM SatLink 180 plug-in card

3.4.5 COM1/RS-232 interface for accessing the command line interface

4 Using the Command Line Interface of the SatLink

4.1 CLI users access rights

User name Factory default password Privilege level

4.2 Online help

To list the commands in a sub-menu type '? <sub-menu>'

For detailed help on a command type '? <command>'

-volatile The address will not saved in persistent memory

If the interface is Virtual-VLAN, then the IP should be from the

4.3 Logging of events

The events are divided in four different severity levels:

4.4 CLI command summary

CLI commands Available in Available in User

ping {<ipaddr> [<options>]}|<-enablemonitor|- x x 5

CLI commands Available in Available in User

ipe pid <pid> {<maxrate>|-del} [<packing delay> x 5

The following equipments can be used to build a Forward Link System

1PPS 10 MHZ TRF MGMT

Figure 9 : SatLink 8550/8560 Forward Link in 1:1 redundancy

5.2 SatLink 85xx

Model Tx level range