STM SatLink User Manual

Download

Page 1

STM SatLink Terminal

User Guide

Publication no. 101557, Rev. T, November 3th, 2006

Page 1

Page 2

™

Notice

Copyright Error! Reference source not found., STM Norway AS All rights reserved. Reproduction, adaptation or translation without prior written permission is prohibited, except as allowed under the copyright laws.

The names of products (hardware and/or software) mentioned herein are regarded to be the property of their respective companies, regardless of whether or not registration is indicated.

The information in this publication is subject to change without notice. STM Norway AS makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for particular purposes. Moreover, STM Norway AS shall not be held liable for errors that may occur herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this material.

Publication no. 101557, Rev. T, November 3th, 2006

Page 2

Page 3

Table of Contents

1.1

1.2

1.3

3.1

3.2

3.3

3.4

3.5

4.1

5.1

5.2

5.3

5.4

INTRODUCTION ........................................................................................................ 5

About this User Guide................................................................................................. 6

Initial Configuration ..................................................................................................... 7

Symbols...................................................................................................................... 7

UNPACKING .............................................................................................................. 8

INSTALLATION .......................................................................................................... 8

Before installation ....................................................................................................... 8

SatLink Terminal front and back panels ...................................................................... 9

IDU Installation ......................................................................................................... 12

ODU installation........................................................................................................ 13

Interface connections................................................................................................ 13

PC CONFIGURATION ............................................................................................. 15

Windows TCP/IP configuration.................................................................................. 15

USING THE COMMAND LINE INTERFACE OF THE SATLINK TERMINAL ............ 18

CLI users access rights............................................................................................. 18

Online help ............................................................................................................... 18

Logging of events ..................................................................................................... 19

CLI command summary............................................................................................ 20

6.1

6.2

6.3

6.4

6.5

7.1

7.2

8.1

8.2

8.3

8.4

10.

11.

11.1

11.2

12.

12.1

STM SATLINK TERMINAL CONFIGURATION......................................................... 22

Power on and logon.................................................................................................. 22

Initial configuration of parameters ............................................................................. 24

Forward Link acquisition, Tx power calibration, and fine adjustment of antenna

pointing and polarisation ........................................................................................... 32

Test of DVB-RCS connection.................................................................................... 37

Prepare the STM SatLink Terminal for normal operation........................................... 38

LAN DHCP SERVER............................................................................................... 39

Configuration of the DHCP server............................................................................. 39

Changing the SatLink Terminal LAN Interface IP address......................................... 40

QUALITY OF SERVICE............................................................................................ 41

Configuring QoS for the return link............................................................................ 42

Configuring the terminal for VoIP .............................................................................. 44

Configuring the terminal for Video (ViC).................................................................... 44

DSCP and DiffServ ................................................................................................... 45

BANDWIDTH ON DEMAND ..................................................................................... 47

TRAFFIC INITIATED LOGON................................................................................... 49

HEADER COMPRESSION ....................................................................................... 50

Enabling Header compression.................................................................................. 50

Disable Header compression.................................................................................... 51

ROUTING OF MULTICAST TRAFFIC ...................................................................... 52

Setting up routing of multicast traffic from the SatLink Terminal LAN to the gateway 52

13.

UPDATING THE STM SATLINK TERMINAL SW...................................................... 53

Publication no. 101557, Rev. T, November 3th, 2006

Page 3

Page 4

13.1

Automatic software update........................................................................................ 53

13.2

Manual software update............................................................................................ 54

13.3

Restoring the backup software.................................................................................. 55

14.

14.1

14.2

14.3

15.

15.1

15.2

15.3

15.4

15.5

16.

17.

APPENDIX A. USING THE WEB INTERFACE .................................................................... 74

APPENDIX B. ACCESSING THE COMMAND LINE INTERFACE VIA RS-232................... 75

APPENDIX C. TFTP SERVER ............................................................................................. 78

STM SATLINK AND DVB-S2.................................................................................... 56

DVB-S2 Modulation .................................................................................................. 57

DVB-S2 Coding ........................................................................................................ 57

DVB-S2 Configuration............................................................................................... 58

SOFTWARE OPTIONS ............................................................................................ 60

Network Address Translation.................................................................................... 61

Generic Routing Encapsulation (GRE) and IP Tunnelling ......................................... 66

TCP Performance Enhancing Proxy (PEP)............................................................... 67

4 QoS Classes.......................................................................................................... 69

Return link access control (RAC) .............................................................................. 70

DEFINITIONS, ACRONYMS AND ABBREVIATIONS............................................... 72

REFERENCES ......................................................................................................... 73

APPENDIX D. TELNET CLIENT .......................................................................................... 79

APPENDIX E. MANAGEMENT VIA SNMP .......................................................................... 80

APPENDIX F. CHANGING PRE-CONFIGURED PARAMETERS........................................ 81

APPENDIX G. ODU INSTALLATION.................................................................................... 82

APPENDIX H. CABLE SPECIFICATION.............................................................................. 88

APPENDIX I. STM SATLINK 403X. INTERFACING VSAT RX/TX ANTENNAS.................. 90

APPENDIX J. IDU OUTPUT POWER CALIBRATION WITH OTHER BUCS THAN SATLINK

3000 AND 403X........................................................................................................ 94

APPENDIX K. THE BOOT SW............................................................................................. 97

APPENDIX L. TROUBLESHOOTING.................................................................................. 98

APPENDIX M. COMPLIANCE ............................................................................................ 105

APPENDIX N. STANDARDISATION OF TIMING COMPENSATION ................................. 106

APPENDIX O. RECEIVER AND TRANSMITTER AUTO START........................................ 108

APPENDIX P. ACCESSING THE FORWARD LINK SIGNALLING..................................... 109

Publication no. 101557, Rev. T, November 3th, 2006

Page 4

Page 5

1. Introduction

The STM SatLink 1000, 1900, 1901 and 1910 are members of the STM SatLink Terminal family of DVB-RCS Terminals. They act as IP routers to interface one or more PCs for two-way communication via the satellite network.

Figure 1: SatLabs Approved STM SatLink 1000 and 1910 Indoor Units (IDUs)

Figure 2: STM SatLink Outdoor Unit (ODU)

Publication no. 101557, Rev. T, November 3th, 2006

Page 5

Page 6

1.1 About this User Guide

This User Guide covers the installation and operation of the STM SatLink 1000/1900/1901/1901, commonly also referred to as the indoor unit (IDU) of the DVB-RCS terminal, together with the accompanying outdoor unit (ODU) equipment. It is intended for DVB professionals, such as service providers and installers. Therefore, it does not contain information for non-professional users, such as given in the user manuals of consumer electronics products.

The information given pertains to the following software (SW) and hardware (HW) versions and releases: SatLink IDU Software

• STM SatLink Boot loader, P/N 101225, SW build 1.8.0.2 and later

• STM SatLink Boot loader, P/N 106267, version 9.0.0 and later

• STM SatLink DVB-RCS Terminal Software, P/N 101224, version 11.0.1 and later

SatLink IDU HW models

• STM SatLink 1000, P/N 103346

• STM SatLink 1900, P/N 100715

• STM SatLink 1901, P/N 102105

• STM SatLink 1910, P/N 103798

Ku-band Equipment Transceivers

• STM SatLink 4033, P/N 104804

• STM SatLink 4035, P/N 106546

BUCs

• Invacom TUL-204, P/N 104041

• JRC NJT5017F

LNBs

• Invacom LNB/OMT SPV-1SM, P/N 100816

• JRC NJR2535S

• JRC NJR2536S

• JRC NJR2537S

Antennas

• Andrew Type 960 - 0.96m Antenna, P/N 100883 and P/N 107482

• Andrew Type 123 - 1.2m Antenna, P/N 100882 and P/N 107483

• Andrew Type 184 - 1.80m Antenna, P/N 104216

• Andrew Type 244 - 2.40m Antenna, P/N 104612

• Visiosat KIT 90 EMIT - 0.9m Antenna, P/N 105645

• Visiosat KIT 120 EMIT - 1.2m Antenna, P/N 107077

C-band Equipment BUCs

• JRC NJT5652, P/N 105268

• JRC NJT5656, P/N 105269

• Norsat 3050XPTF, P/N 105271

• Zinwell ZTX-C3300F, P/N 105701

• Zinwell ZTX-C3301F, P/N 105276

• Zinwell ZTX-C3700F, P/N 105700

• Zinwell ZTX-C3701F, P/N 105274

LNB

• Zinwell ZC-VD1, P/N 105267

• Norsat 8000 series

Antennas

• Andrew Type 183 – 1.8m

• Andrew Type 243 – 2.4m

Publication no. 101557, Rev. T, November 3th, 2006

Page 6

Page 7

1.2 Initial Configuration

The STM SatLink Terminal must be configured before it can communicate via the satellite to and from the network operator Gateway. The parameters to be configured are explained in section 6.2.

The configuration of the terminal can be carried out using the configuration tools:

• Command Line Interface

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

Telnet

• Web-interface

• SNMP

Configuration via CLI and Web-interface is presented in this document. For terminal management via SNMP, the reader is referred to [6].

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.

Publication no. 101557, Rev. T, November 3th, 2006

Page 7

Page 8

2. Unpacking

Check that the following items are in the box received, then unpack.

• SatLink 1000, 1900, 1901, or 1910

• Stand for vertical placement (SatLink 1000 only)

• Power supply (SatLink 1000 only)

• Mains cord

• Brackets for 19” rack mounting (SatLink 1900/1901/1910 only)

3. Installation

3.1 Before installation

3.1.1 Safety

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 IDU, the ODU 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 Terminal.

• 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 your 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 Terminal shall be connected to the mains 110/230 VAC, 50-60Hz.

Publication no. 101557, Rev. T, November 3th, 2006

Page 8

Page 9

3.2 SatLink Terminal front and back panels

3.2.1 SatLink 1000 front and back panel

Figure 3: SatLink 1000 Front panel

LED Colour, indicates

Power

Error Satellite Receive

Transmit

Ethernet Link/Act

Blue, lights steadily when power switch is on and unit is powered. Flashes when loading software. Red, lights steadily when an error event occurs and during reboot.

Blue, flashes when the receiver is searching for the carrier. Lights steadily when receiver is on and functioning properly. Flashes when IP packets are received from the Satellite Interface (the Gateway). Blue, flashes rapidly when a continuous wave (CW) is transmitted. Lights steadily when the terminal is logged on to the DVB-RCS gateway. Flashes when IP packets are transmitted to the Satellite Interface (the Gateway). Blue, lights steadily when Ethernet connectivity is OK. Flashes slowly when Ethernet packets are transferred via the Ethernet interface.

Table 1: SatLink 1000 front-panel LEDs

Figure 4: SatLink 1000 back panel

Item Description

On/off switch Mains power on (1) or off (0). Mains Connector Connector for cable to the 24 V DC power transformer (external power supply provided

with STM SatLink 1000 Terminal) Ethernet Connector COM1 Connector Nine-pin connector for connecting CLI interface to a computer serial RS232 interface. Rx coaxial jack Tx coaxial jack

RJ45 connector for IP traffic to connect to a PC, Ethernet switch, IP router etc. 10BASE-T

or 100BASE-T modes are detected automatically.

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

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

Table 2: SatLink 1000 back panel description

Publication no. 101557, Rev. T, November 3th, 2006

Page 9

Page 10

3.2.2 SatLink 1910 front and back panel

Figure 5: SatLink 1910 Front panel

LED Colour, indicates

Power

Error Red, lights steadily when an error event occurs and during reboot. Satellite Receive Blue, flashes when the receiver is searching for the carrier.

Transmit

Ethernet Link/Act

Blue, lights steadily when power switch is on and unit is powered. Flashes when loading software.

Lights steadily when receiver is on and functioning properly. Flashes when IP packets are received from the Satellite Interface (the Gateway).

Blue, flashes rapidly when a continuous wave (CW) is transmitted. Lights steadily when the terminal is logged on to the DVB-RCS gateway. Flashes when IP packets are transmitted to the Satellite Interface (the Gateway). Blue, lights steadily when Ethernet connectivity is OK. Flashes slowly when Ethernet packets are transferred via the Ethernet interface.

Table 3: SatLink 1910 front-panel LEDs

Figure 6: SatLink 1910 back panel

Item Description

On/off switch Mains power on (1) or off (0). Mains Connector Standard recessed plug for Mains cord. Ethernet Connector COM1 Connector Cover for Accessory Card Not used. Rx coaxial jack Tx coaxial jack

RJ45 connector for IP traffic to connect to a PC, Ethernet switch, IP router etc. 10BASET or 100BASE-T modes are detected automatically. Nine-pin connector for connecting CLI interface to a computer serial RS232 interface.

Coaxial 75 Ω F-type jack for the cable to the LNB. Coaxial 75 Ω F-type jack for the cable to the BUC.

Table 4: Description of SatLink 1910 back panel

Publication no. 101557, Rev. T, November 3th, 2006

Page 10

Page 11

3.2.3 SatLink 1900 and 1901 front and back panels

Figure 7: SatLink 1900 and 1901 front panel.

LED Colour, indicates

Power

Error Satellite Receive

Transmit

Ethernet Receive Transmit

Blue, lights steadily when power switch is on and unit is powered. Flashes when the software is loading. Red, lights steadily when an error event occurs; lights steadily during reboot.

Blue, flashes when the receiver is searching for the carrier. Lights steadily when receiver is on and functioning properly. Flashes when IP packets are received from the Satellite Interface (the Gateway). Blue, flashes rapidly when a continuous wave (CW) is transmitted Lights steadily when the terminal is logged on to the DVB-RCS gateway. Flashes when IP packets are transmitted to the Satellite Interface (the Gateway). Blue, lit when Ethernet packets from the local network are being received.

Blue, lit when Ethernet packets are sent to the local network.

Table 5: SatLink 1900 and 1901 front-panel LEDs

Figure 8: SatLink 1900/1901 Back panel

Item Description

On/off switch Mains power on (1) or off (0). Mains Connector Standard recessed plug for Mains cord. COM1 Connector Ethernet Connector Node/Hub Push-button toggle

External I/O Not used Rx coaxial jack Tx coaxial jack

Nine-pin connector for connecting CLI interface to a computer serial RS232 interface.

RJ45 connector for IP traffic to connect to a PC, Ethernet switch, IP router etc. 10BASE-T or 100BASE-T modes are detected automatically. Selects HUB or NODE configuration of the Ethernet port. NODE normally is used when connecting to an Ethernet switch or Ethernet hub, while HUB is used when connecting directly to a single PC.

Coaxial 75 Ω F-type jack for the cable to the LNB. Coaxial 75 Ω F-type jack for the cable to the BUC.

Publication no. 101557, Rev. T, November 3th, 2006

Page 11

Page 12

Table 6: SatLink 1900 and 1901 back panel connectors and switches

3.3 IDU Installation

3.3.1 On desktop or shelf

Place the STM SatLink Terminal on a flat, stable surface, such as a desktop or shelf, close to the PC or network device to which it will be connected. Keep its top, bottom and all sides unobstructed to ensure free airflow. Rubber feet on the bottom provide adequate clearance. Ensure that there is at least 10 cm clearance at the back to allow room for cable connections.

3.3.2 In rack

The rack or cabinet should be properly secured to prevent tipping. Equipment that is 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 mains circuits are properly earthed and use the mains cord supplied with the

SatLink Terminal to connect it to the mains outlet.

• If your 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 in your country.

• 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 need be.

• 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 STM SatLink Terminal 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 STM SatLink Terminal in a location where the operating ambient temperature may

exceed 45°C.

• Ensure that the airflow around the sides and back of the SatLink Terminal is not restricted.

The STM SatLink 1900/1901/1910 can be mounted in any EIA-standard 19-inch telecommunications rack or cabinet. The STM SatLink 1000 needs to be placed on a shelf if it is to be placed in a rack.

Use a Torx screwdriver and attach the mounting brackets to the router 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.

Publication no. 101557, Rev. T, November 3th, 2006

Page 12

Page 13

Figure 9: Rack Mounting

3.4 ODU installation

Install the ODU as described in Appendix G and references [1], [2], [3], [4] and [5]. When installing the STM SatLink 403x transceiver, please check Table 15 in Appendix I whether an adapter is required to interface the antenna feed horn.

3.5 Interface connections

3.5.1 Rx/Tx cables between IDU and ODU

The coaxial cables from the ODU are connected to the type F coaxial jacks on the back panel of the STM SatLink Terminal. See Appendix H for specification of the cables to be used.

• Connect one coaxial cable from the ODU Tx module input to the jack marked Tx.

• Connect one coaxial cable from the LNB to the port marked Rx on the back panel.

Do not connect the Tx cable before the initial configuration of the STM SatLink Terminal is performed to ensure that incorrect or hazardous signals are not sent to the satellite

Use only 75  coaxial cables fitted with type F plugs for the Rx and Tx cables. Ensure that the cables meet the cable requirements specified in Appendix H. Make sure that the connectors are of a waterproof version such as F-connector RG6 Compression type from Cablecon (www.cablecon.dk), article no 99909446, STM article no 106208

Do not connect and disconnect the coaxial cables with power connected to the STM SatLink Terminal.

Hint Use different colour marking on the Tx and Rx coaxial cables to reduce the probability for interchanging the cables.

Publication no. 101557, Rev. T, November 3th, 2006

Page 13

Page 14

3.5.2 Ethernet connection to a Local Area Network (LAN)

The STM SatLink Terminal may be connected to a single PC or to a network via the RJ-45 Ethernet jack on the back panel.

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

• Plug the other end of the Ethernet cable into the RJ-45 jack a Local Area Network (LAN) device such

as an Ethernet hub, switch or router, according to its manufacturer’s instructions.

For the STM SatLink 1900 and 1901, toggle the back panel push button to set Ethernet HUB or NODE mode. Toggle to NODE when connecting to an Ethernet switch or an Ethernet hub and toggle to HUB when connecting to a single PC.

For the STM SatLink 1000 and 1910 there is no push button on the back panel as Ethernet HUB or NODE mode will be auto-detected and the correct mode chosen automatically.

3.5.3 Mains connection

The STM SatLink 1900/1901/1910 models have internal power supply and consequently are connected directly to a 110/230 VAC 50/60Hz outlet using a standard 230 VAC mains cord.

3.5.4 Power supply

The STM SatLink 1000 has an external power supply that is connected to a 110/230 VAC 50/60Hz outlet using a standard mains cord.

The STM SatLink 1000 must only be connected to the external power supply that is approved by STM , PN 104170 (LEI-S2425D / Model No. STD-2425). Use of another power supply will void warranty.

Publication no. 101557, Rev. T, November 3th, 2006

Page 14

Page 15

4. PC configuration

After installation as described in Chapter 3 is carried out, the STM SatLink Terminal is ready to be powered on.

4.1 Windows TCP/IP configuration

Verify that the TCP/IP configuration for PCs connected to the Terminal LAN is correct. Push the startbutton in Windows, select the Control panel and then open Network Connections. Right-click on the relevant Local Area Connection and select Properties. A new window showing the Network Connection Properties will pop up. In the General submenu of this window, scroll down, select Internet Protocol (TCP/IP) and then push the Properties button shown in Figure 10. Then configure the PC client to obtain the IP address automatically from the Terminal (section 4.1.1) or configure the PC with a static IP address (section 4.1.2).

Figure 10: Windows XP menu for configuring the client TCP/IP configuration.

Publication no. 101557, Rev. T, November 3th, 2006

Page 15

Page 16

4.1.1 Dynamic IP configuration of PCs connected to the STM SatLink Terminal LAN

By default the DHCP server in the STM SatLink Terminal is enabled. When the STM SatLink Terminal is powered on, all PCs connected to the STM SatLink LAN can automatically retrieve their IP configuration from the DHCP server. The user should verify that the Window clients are configured to obtain an IP address and DNS server address automatically. Figure 11 shows the correct Windows XP configuration when the DHCP server is enabled in the Terminal.

Figure 11: Windows XP TCP/IP setting when DHCP server is enabled in the Terminal

From an MS-DOS window, the user may type ipconfig /all command to verify that the computer has received correct configuration parameters from the DHCP server such as IP address, subnet mask, default Gateway, DNS servers and lease time.

Figure 12: ipconfig /all print out from an MS-DOS window

Publication no. 101557, Rev. T, November 3th, 2006

Page 16

Page 17

4.1.2 Static IP configuration of PCs connected to the STM SatLink Terminal LAN

When the DHCP server in the SatLink Terminal is disabled, all PCs attached to the STM SatLink Terminal LAN must be configured with static IP addresses that are within range of the STM SatLink Terminal subnet (see section 6.2.1). The IP configuration parameters to use for PCs connected to the STM SatLink Terminal LAN are supplied from the system operator or service provider. Please configure the IP address, Subnet mask, Default gateway, Preferred DNS server, and optionally the Alternate DNS server as shown in Figure 13.

Ensure that the actual IP addresses supplied by the system operator / service provider are configured and not the IP addresses in the example figure.

Figure 13: Windows XP TCP/IP setting when DHCP server is disabled in the Terminal

Example: A host may have the following configuration; IP address 192.168.0.2, Subnet mask 255.255.255.0 and default gateway 192.168.0.1, where the IP address of the default gateway should be the IP address of the STM SatLink Terminal LAN interface.

Publication no. 101557, Rev. T, November 3th, 2006

Page 17

Page 18

5. Using the Command Line Interface of the SatLink Terminal

The command line interface can be accessed via either Telnet or the RS-232 port for management of the STM SatLink Terminal as well as for showing status and reports.

5.1 CLI users access rights

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

• Level 2: installer

• Level 3-5: end users

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

User name Factory default password Privilege level install dvbrcs 2

When accessing the CLI via RS-232, if the login prompt is not displayed type ENTER. The login prompt

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

New users may be added with the CLI command command changed with the CLI command the user currently logged in, use the CLI command

user

For security reasons we recommend that you change the factory set password to your own personal one.

should then be displayed. Then login with the install user:

user add

user del

, and the password of the current user or users with lower privilege levels can be

user passwd

. To list all defined users with lower privilege level than

user show

commands.

, existing users deleted with the CLI

. Type

? user

to get further help on the

5.2 Online help

In the CLI a list of available commands can be displayed by typing ENTER key). The CLI command groups will then be shown:

Example:

# ? ? : ? <submenu|command> device : Device configuration dvb : DVB interface configuration eth : Ethernet configuration ip : IP configuration log : Event log misc : Miscellaneous commands odu : ODU configuration sw : Software upgrade & licenses user : User configuration

STM SatLink Terminals with Boot SW release 8.x.x or earlier, will have factory default password

satlink for the install user.

Publication no. 101557, Rev. T, November 3th, 2006

? <ENTER>

(question mark and the

Page 18

Page 19

To display the available commands within one sub-menu type

? <sub-menu>

Example:

# ? ip show : ip show [-mcast] set : ip set <ifnum> <ipaddr> <mask> addroute : ip addroute <destaddr> <netmask> <next hop> <ifnum> delroute : ip delroute <destaddr> <netmask> <next hop> dhcp : DHCP configuration qos : IP QOS configuration #

To get further help on a specific CLI command type Example:

# ? ip set

USAGE: ip set <ifnum> <ipaddr> <mask>

ifnum Interface number (1=LAN, 3=Satellite) ipaddr IP address for the interface mask Netmask for the interface

Set the IP address and subnet mask for the specified interface

Example: ip set 1 10.10.1.1 255.255.255.248 will set the LAN IP address to

10.10.1.1 and the LAN netmask to

255.255.255.248

See also: ip show, ip addroute, ip delroute

? <cmd>

5.3 Logging of events

The STM SatLink Terminal logs certain events to a log stored in RAM. See Appendix L.5 for a list of the different events and needed actions. Use the CLI command

The events are divided in four different severity levels:

0. Minor

1. Normal

2. Major

3. Critical Events with severity level Major will normally cause disruption in the data transfer, while events with severity level Critical normally will require user intervention in order to restore the data communication with the DVB-RCS gateway.

To have access to the log of events also after the terminal software has been rebooted, the event above a specified severity level can be logged to file. Use the CLI command events to file, set the minimum severity level of events that shall be logged to file and set the maximum size for the logfile. By default, Major and Critical events are logged to file.

Publication no. 101557, Rev. T, November 3th, 2006

log show

log file

to show the log from memory.

to enable logging of

Page 19

Page 20

Available in

5.4 CLI command summary

The available CLI commands are listed below.

CLI commands

Boot

? [sub-menu] [cmd] x x 5 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 dload <filename> <ipaddr> [<localname>] x x 2 upload <filename> <ipaddr> [<remotename>] x x 2 ping <ipaddr> x x 5 exit x x 5 logout x x 5 restart x x 5 save config x 5 device snmp show device snmp community <name> <ro|rw> [<ipaddr> <mask>]

device snmp delcommunity <name> device manager show device manager add <func> <if> [<ip> <mask>] device manager del <func> <if> [<ip> <mask>] device name <name> device contact <contact> device location <location> device show dvb popid <id> x 2 dvb tx autostart <on|off|traffic> [<timeout>] dvb tx calibrate [<freq> [<timeout>]] x 2 dvb tx cw <on|off> [<pow> [<freq>

[<timeout>]]] dvb tx cwfreq <freq> x 2 dvb tx eirp <eirp> x 2

dvb tx logoff x 2 dvb tx logon x 2 dvb tx outpow <pow> x 2 dvb tx show [-burst|-capacity|-queue|-ts] x 5 dvb rx autostart <on|off> x 2 dvb rx start x 2 dvb rx stop x 2 dvb rx fwdlink <idx> <pri> [<symbrate>

[<freq> [<mode> [<popid>]]]] dvb rx phy [-internal | -satlink100] x 2

dvb rx show [-pid] x 5 dvb cr show [-timeout|-interval|-capacity] x 2 dvb pos lat <deg> <min> <mindec> <dir> x 2 dvb pos long <deg> <min> <mindec> <dir> x 2 dvb pos alt <height> x 2 dvb pos delayburst <nera|satlabs|ticks> x 2 dvb pos show x 5

x 1 x 1

x 1 x 1 x 1 x 1 x 2 x 2 x 2 x 5

x 2

Available in

Application

User

Privilege

Level

Publication no. 101557, Rev. T, November 3th, 2006

Page 20

Page 21

Available in

laddr> <globport> <locaddr>

CLI commands

Boot

Available in

Application

User

Privilege

Level

eth mode <mode> x 5 eth show x 5 ip addroute <destaddr> <netmask> <next hop>

x x 2 <ifnum> ip delroute <destaddr> <netmask> <next hop> x x 2

ip qos mask <index> <group> {{+|-}<tag>

x 2 <tag-parms>}+ ip qos show x 5

ip set <ifnum> <ipaddr> <mask> x x 2 ip show [-mcast] x x 5

ip nat <enable|disable >2 ip nat global <add|del> <gladdr>2

ip nat static add <gladdr> <locaddr>2 ip nat static del <gladdr>2 ip nat napt add <g

x 2

x 2 <locport>2 ip nat napt del <gladdr> <globport>2

ip nat <show>2 ip dhcp <enable|disable> ip dhcp show ip dhcp leasetime <time> [unit] ip dhcp dns <primary> <secondary> ip dhcp exclude <no> ip gre add <destaddr> <netmask>

x 2

x 5

2 <tunnelipaddr>2 ip gre del <ifnum>2 ip gre show2

ip pep disable ip pep enable <mode> ip pep server <ipaddr> ip pep show log file <enable|disable>

5 [<severity> [<filesize>]] log show

odu lnb <type> odu txtype <type> odu antenna <type> odu show sw license <feature> <key> sw mcast <value> [<pid>] [<addr>] [<port>] sw upgrade [-default] [<filename>

2 [<tftp-ip-addr>]] sw restore

sw show user add <loginname> <passwd>

4 [privilege level] user del <loginname> x

user passwd {loginname | oldpasswd}

5 <newpasswd> user show x

CLI commands are available only when the license for this software option is installed.

Publication no. 101557, Rev. T, November 3th, 2006

Page 21

Page 22

6. STM SatLink Terminal configuration

Before powering on the STM SatLink Terminal for the first time, ensure that the Tx coaxial cable from the STM SatLink Terminal to the ODU is disconnected to avoid that incorrect and potentially damaging signals are sent to the satellite. Follow all the procedures below when installing the STM SatLink Terminal and lining up the ODU.

6.1 Power on and logon

1) To view the boot processes of the STM SatLink Terminal, please connect a PC to the serial interface

and launch a Terminal Emulator as described in Appendix B. Otherwise go to step 2.

2) Turn on the power of the STM SatLink Terminal.

3) When turning on the STM SatLink Terminal 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. Telnet is not available until the application has been started.

STM SatLink Boot-loader

- SW ID 106267, Revision 9.0.0.1

File system initialised Press return to enter boot-loader

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 DVB RCS application will load automatically once the boot SW load has completed. See Appendix K for further details concerning the boot SW. If access to the boot-loader is required, press return within 10 seconds to display the login-prompt for entering the boot-load. After the timer has expired, the DVB-RCS application will be loaded. The message

Loading application

will be shown when the application starts to load.

Publication no. 101557, Rev. T, November 3th, 2006

Page 22

Page 23

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 STM SatLink Terminal 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.

STM SatLink 1000 – Main Board ID 102805, Revision R6.0

- SW ID 101224, Revision 10.0.0 Build 37

File system initialised Ethernet Interface MAC Address : 00:60:c0:2f:a7:38 DVB Interface MAC Address : 00:60:c0:2f:a7:38

Retrieving configuration....done

When the STM SatLink Terminal is configured for use with the STM SatLink 4033/4035 transceiver and the TX cable is not connected to the ODU then the following error message will be shown when the SW has booted:

ODU Initialisation failed. Unable to establish DiSEqC communication. Please check connection to ODU and that the ODU supports DiSEqC communication

This is normal and just indicates that the terminal can not communicate with the transceiver since the cable is not yet connected.

5) At this point the Telnet server in the STM SatLink Terminal is started and a Telnet session can be

opened for managing the terminal. 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 D), PuTTY3, 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 B).

Use the STM SatLink Terminal’s Satellite Interface (DVB) IP address when using Telnet over the satellite link (from the Gateway), and the STM SatLink Terminal’s LAN (Ethernet) IP address when using Telnet from the local LAN.

When shipped from the factory the SatLink 1000 and 1910 Terminal LAN (Ethernet) IP-addresses are set to 192.168.0.1 and the subnet mask to 255.255.255.0. The SatLink 1900 and 1901 normally have the LAN IP address set to 10.10.10.10 and the subnet mask to 255.0.0.0 when shipped from the factory. If the STM SatLink Terminal LAN (Ethernet) IP-address is not known, one must use CLI via RS-232 to do the initial configuration.

The STM SatLink Terminal can handle at most three simultaneous Telnet connections including aborted connections. The Telnet session will be automatically terminated after 20 minutes without 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.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Publication no. 101557, Rev. T, November 3th, 2006

Page 23

Page 24

install

with the factory default password

dvbrcs

STM SatLink 1000 – Main Board ID 102805, Revision R6.0

- SW ID 101224, Revision 10.0.0 Build 37

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 that the Local Echo is enabled in the Telnet client.

The STM SatLink Terminal should now be ready to be configured as described in the following subsections.

6.2 Initial configuration of parameters

The terminal must be configured with a number of parameters before the terminal can acquire the forward link and communicate with the network Gateway. A default configuration specifying most of these parameters is usually pre-loaded on each STM SatLink Terminal, either in the factory or by the service provider before installation. The parameters that usually need to be configured by the installer are:

- Antenna/ODU to be used

- Forward link frequency and symbol rate

- Terminal geographical position

- Terminal population ID

- Target output power for transmission on the return link

- IP routing parameters.

Many DVB-RCS networks support automatic configuration of the terminal’s IP parameters when the terminal logs on to the network. In that case, the IP address configuration described in section 6.2.1 below can be skipped. Please check with your service provider if local configuration of the terminal’s IP addresses is necessary.

6.2.1 IP configuration

The DVB-RCS system operator manages all IP addresses in the DVB-RCS system including the DVB interface IP address and the LAN IP addresses of all DVB-RCS terminals. The IP-addresses can be set automatically in the terminal by the DVB-RCS system operator, or manually by the installer. Please check with your operator which method applies.

The procedure below is required for manual IP-address configuration only. If the DVB-RCS network supports automatic configuration of the terminal’s IP parameters, skip this part and go to section 6.2.2.

Please make sure that the IP addresses and netmasks are entered exactly as specified by the DVB-RCS system operator, as any deviation may result in loss of communication with the IP network.

dvbrcs

shipment from the factory.

is the factory default setting for the password. The password might have been changed after

Publication no. 101557, Rev. T, November 3th, 2006

Page 24

Page 25

1) Set the LAN IP address of the unit

– Enter the CLI command where

<aaa.bbb.ccc.ddd>

ip set 1 <aaa.bbb.ccc.ddd> <eee.fff.ggg.hhh>

is the IP address and

<eee.fff.ggg.hhh>

the netmask.

Example:

# ip set 1 10.10.20.1 255.255.255.248

2) Set the DVB IP address (Satellite interface) of the unit:

– Enter the CLI command where

<aaa.bbb.ccc.ddd>

ip set 3 <aaa.bbb.ccc.ddd> <eee.fff.ggg.hhh>

is the IP address and

<eee.fff.ggg.hhh>

the netmask.

Example:

# ip set 3 10.10.21.1 255.255.255.0

3) 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 LAN interface, interface 2 is not used, and interface 3 is the DVB (satellite) interface):

# ip show Interfaces If IPAddress SubnetMask BroadCastAddr MTU Alias AdminStatus 1 10.10.20.1 255.255.255.248 10.10.20.7 1500 eth0 1 2 N/A N/A N/A 4074 air0 1 3 10.10.21.1 255.255.255.0 192.168.255.255 4074 dvb0 1 Interface Statistics

------------- Input ----------------- ------------- Output ----------------

If UCast NUCast Disc Octets UCast NUCast Disc Octets 1 14496815 48920 1068 967104678 29153597 1278 1 970900724 2 0 0 0 0 0 0 0 0 3 14754693 70483 2506 486270184 21082393 0 4 1308841911 IP Receive Deliver Errors Discards Forward Request NoRoute Discards 73163754 667213 4 4 43077496 304307 0 280 Routing Table DestMask RouteMask NextHop If

0.0.0.0 0.0.0.0 10.10.21.254 3

10.10.20.0 255.255.255.248 0.0.0.0 1

10.10.21.0 255.255.255.0 0.0.0.0 3

4) Save the IP configuration to Flash

– Enter the CLI command:

save config

– Example:

# save config Saving Configuration. This will take ~20 secs # Configuration Saved

If the prompt sign (#) does not show, push enter.

Publication no. 101557, Rev. T, November 3th, 2006

Page 25

Page 26

6.2.2 Antenna and ODU parameter configuration

The STM SatLink Terminal is normally pre-configured to be used together with the STM SatLink 403x Transceiver. The CLI command ODU transmitter type and ODU receiver type, both set to STM SatLink 403x.

It is possible to configure the STM SatLink Terminal to operate together with other transmitters and receivers than SatLink 403x. The valid ODU transmitters (BUC) are listed in Table 7 and the valid ODU receivers (LNB) are listed in Table 9 (the list is also available using the CLI help command

? odu txtype).

Choosing the ODU transmitter to be STM SatLink 403x will automatically lock the

ODU receiver type to STM SatLink 403x.

Please make sure that the correct ODU transmitter (BUC) type is selected according to the table below as the return link communication will otherwise not work.

ODU

ODU Transmitter (BUC) STM Product Number

Transmitter #

(type)

Ku-band

30 Invacom TUL-204 104041 All 45 JRC NJT5017F All

C-band

80 JRC NJT5652 105268 All 81 JRC NJT5656 105269 All 85 Norsat 3050XPTF 105271 All 92 Zinwell ZTX-C3300F 105701 All 90 Zinwell ZTX-C3301F 105276 All 93 Zinwell ZTX-C3700F 105700 All 91 Zinwell ZTX-C3701F 105274 All

odu show

will show the ODU configuration with the two parameters,

HW Revision

(P/N)

106546 (SatLink 4035) All 11 STM SatLink 403x 104804 (SatLink 4033) All

Table 7: Overview of supported ODU transmitters (BUCs)

To configure use of an ODU transmitter (BUC) listed in the table above, please enter the CLI command

odu txtype <type>

where

type

is the number from the first column in the table above.

Example:

# odu txtype 45

selects the JRC NJT5017F transmitter. Use the command

odu show

to view the ODU configuration

parameters.

Publication no. 101557, Rev. T, November 3th, 2006

Page 26

Page 27

When using the STM SatLink 4033/4035 Transceiver, the STM SatLink Terminal must be configured with the antenna type in use in order to calculate the transmitted EIRP correctly. The following antennas are supported:

Antenna #

Antenna (Ku-band) Size

(type)

2 Andrew Type 960 0.96 m 1 Andrew Type 123 1.20 m 5 Andrew Type 184 1.80 m 7 Andrew Type 244 2.40 m 9 Visiosat KIT 90 EMIT 0.90 m

10 Visiosat KIT 120 EMIT 1.20 m

Table 8: Overview of supported Antenna types

Please see Appendix I (Table 15 on page 91) for more detailed information regarding the antennas that can be used with the STM SatLink 403x transceiver.

The STM SatLink Terminal is normally pre-configured to use the Andrew Type 960 antenna. If another antenna listed in the table above is to be used, please enter the CLI command where

type

is the antenna number from the first column in the table above.

odu antenna <type>

Example:

# odu antenna 1

selects the Andrew 1.2 m antenna. Use the command

odu show

to view the ODU configuration

parameters.

Example:

# odu show

Antenna Configuration

--------------------Type Andrew/Channel Master Type 960 - 96cm Tx Gain at 14.25 GHz 41.2dB

Transmitter (BUC) Configuration

------------------------------Type STM SatLink 4033 (14.0-14.5 GHz) ODU Serial No. 104804030303051100020000 ODU HW Version 3.3 ODU SW Version 1.3 Local oscillator 13.050000 GHz 24V DC supply On

Receiver (LNB) Configuration

---------------------------Type STM SatLink 403x (10.70-12.75 GHz) Local oscillator - High band 10.600000 GHz Local oscillator - Low band 9.750000 GHz Oscillator switching frequency 11.700000 GHz LO Switching mode 22kHz 13/18V DC supply 13V

Publication no. 101557, Rev. T, November 3th, 2006

Page 27

Page 28

The SatLink Terminal can be configured with one of the following LNBs:

ODU LNB #

ODU LNB STM P/N

(type)

Ku-band

20 Invacom SPV-1SM 100816 30 Zinwell ZK-VJ1 104730

C-band

80 Zinwell ZC-VD1 105267 85 Norsat 8000-series

Table 9: Overview of supported ODU receivers (LNB)

Enter the CLI command

# odu lnb <lnbtype>

where

type

is the number from the first column in the

table above to configure the correct LNB.

When ODU BUC is chosen to be the STM SatLink 403x transceiver, the LNB will automatically be set to STM SatLink 403x. The STM SatLink IDU will detect the STM SatLink transceiver model being used (i.e. STM SatLink 4033, or 4035) and display the detected model in the ODU Transmitter (BUC) Type field in the CLI

odu show

output.

Example:

# odu lnb 20

selects the Invacom SPV-1SM LNB. Use the command

# odu show

Antenna Configuration

--------------------Type Andrew/Channel Master Type 960 - 96cm Tx Gain at 14.25 GHz 41.2dB

Transmitter (BUC) Configuration

------------------------------Type Invacom TUL-204 (14.0-14.5 GHz) Local oscillator 13.050000 GHz 24V DC supply On

Receiver (LNB) Configuration

---------------------------Type Invacom SPV-1SM (10.70-12.75 GHz) Local oscillator - High band 10.600000 GHz Local oscillator - Low band 9.750000 GHz Oscillator switching frequency 11.700000 GHz LO Switching mode 22kHz 13/18V DC supply 13V

odu show

to view the ODU configuration :

Finally save the configuration to flash using the command

save config

The STM SatLink Terminal must be restarted for the new configuration to take effect.

Publication no. 101557, Rev. T, November 3th, 2006

Page 28

Page 29

6.2.3 Terminal position

In order to calculate the delay to the satellite correctly for the logon burst the STM SatLink Terminal must be configured with its own position.

The STM SatLink Terminal by default uses the timing compensation procedure compliant with STM Software Version R9.1 and earlier. For using the STM SatLink Terminal with a DVB-RCS Gateway requiring SatLabs compliant timing compensation or other proprietary timing compensation refer to Appendix N.

1) Find the position of the location where installing the STM SatLink Terminal using a standard GPS.

The STM SatLink Terminal position is entered in one of the following two formats:

a) degrees, minutes, 1/100 minutes, and direction b) degrees, minutes, seconds, and direction

To convert between the two formats use the formula 1/100 minutes = (seconds/60) x 100

Entering the direction as a number {0,1} selects format a, while entering the direction as a letter {‘n’,’s’,’e’,’w’} selects format b.

2) Configure the latitude:

Format a: Enter the CLI command deg = degrees [0, 180> min = minutes [0, 60> mindec = 1/100 minutes [0,100> dir = direction. 0 = North. 1 = South.

Format b: Enter the CLI command deg = degrees [0, 180> min = minutes [0, 60> sec = seconds [0, 60> dir = direction. ‘n’ = North. ‘s’ = South.

Example:

# dvb pos lat 59 52 15 0

# dvb pos lat 59 52 09 n

sets the latitude to 59°52.15'N.

dvb pos lat <deg> <min> <mindec> <dir>

dvb pos lat <deg> <min> <sec> <dir>

where

Publication no. 101557, Rev. T, November 3th, 2006

Page 29

Page 30

3) Configure the longitude:

Format a: Enter the CLI command

dvb pos long <deg> <min> <mindec> <dir>

deg = degrees [0, 180> min = minutes [0, 60> mindec = 1/100 minutes [0, 100> dir = direction. 0 = East. 1 = West.

Format b: Enter the CLI command

dvb pos long <deg> <min> <sec> <dir>

deg = degrees [0, 180> min = minutes [0, 60> sec = seconds [0, 60> dir = direction. ‘e’ = East. ‘w’ = West.

Example:

# dvb pos long 10 29 05 0

# dvb pos long 10 29 03 e

sets the longitude to 10°29.05'E.

4) Configure the altitude:

– Enter the CLI command

dvb pos alt <height>

where

height = height in meters

Example:

# dvb pos alt 60

sets the altitude to 60 meters.

5) Verify the Terminal position:

- Enter the CLI command

dvb pos show

Example:

# dvb pos show Latitude : 59d 52.15'N ( 59d 52' 9''N ) Longitude : 10d 29.05'E ( 10d 29' 3''E ) Altitude : 60 m Timing Reference : STM #

7) Save the Terminal position to Flash

– Enter the CLI command:

save config

where

6.2.4 Forward link parameters

The forward link parameters are used to identify the forward link (outbound link) that is transmitted from the Gateway to the DVB-RCS terminals. To set the symbol rate and receive frequency of the forward link, use the following CLI commands:

dvb rx fwdlink <idx> <pri> [<symbrate> [<freq> [<mode> [<popid>]]]]

Idx Table index [0,9] pri Forward link search order [0,9]. Search is started for priority 0 and ends with priority 9 symbrate Forward link symbolrate [sps] freq Forward link frequency [kHz] mode Valid modes: [dvbs,dvbs2]

Publication no. 101557, Rev. T, November 3th, 2006

Page 30

Page 31

popid Alternative population ID to use for forward link acquisition. Set to -1 to use default

population id (set with CLI command 'dvb popid')

Verify the settings by typing the CLI command

dvb rx show

and type

save config

to save the

configuration.

Example:

# dvb rx fwdlink 0 0 24500000 11250000 dvbs 2 # save config # dvb rx show

Satellite (DVB) RX Configuration

-------------------------------Auto start : Enabled

Idx Pri Freq[GHz] SymbRate[Msps] Mode PopId * 0 0 11.250000 24.500000 DVB-S 2

DVB Receiver Status

-------------------------------Rx State : Off

The above example shows how to configure the STM SatLink Terminal to use the following forward link:

• Rx symbol rate: 24.5 Msps

• Rx frequency: 11.25 GHz

6.2.5 Multiple Beam Configuration

Multiple beam configuration could be used for Maritime terminals, when they switch between different satellites and transponders.

It is also a useful feature when the GW operator is changing the fwd link frequency or symbol rate. Then the operator could configure both the current and the new Forwardlink on the terminals. When the old Forwardlink is removed, the terminal will start search for the second one, and lock to it, if available.

The terminal will start tuning on the forward link configuration with highest priority. When it is able to lock to a forward link configuration, it will use this, and start look for DVB-RCS tables distributed on the link. 10 different forward link configurations could be configured in the terminal.

Example:

# dvb rx fwdlink 5 5 14500000 11460000 dvbs 3 # save config # dvb rx show

Satellite (DVB) RX Configuration

-------------------------------Auto start : Enabled

Idx Pri Freq[GHz] SymbRate[Msps] Mode PopId 0 0 11.247000 24.500000 DVB-S 2 1 1 12.000000 30.000000 DVB-S 4 2 2 11.500000 30.000000 DVB-S 2 3 3 11.600000 2.000000 DVB-S 4 * 4 4 11.900000 11.000000 DVB-S 5 5 5 11.465000 14.500000 DVB-S 3

Publication no. 101557, Rev. T, November 3th, 2006

Page 31

Page 32

The above example shows the STM SatLink Terminal locked to a Forwardlink with:

• Rx symbol rate: 11.0 Msps

• Rx frequency: 11.9 GHz

6.2.6 Population ID

The STM SatLink Terminal will select which group in the DVB-RCS system it belongs to based on the configured population ID. The population ID to be used is assigned by the Gateway Operator. Set the population ID by using the CLI command

Example:

# dvb popid 2 # save config # dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Disabled Population ID : 2 IDU output power : -15 dBm EIRP : 42.0 dBW Default CW Frequency: 14.488000 GHz AAL5 Encapsulation : VC MUX

DVB Transmitter Status

---------------------State : Off #

The above example shows how to configure the STM SatLink Terminal to use population ID 2.

dvb popid <id>

, where id is the wanted population ID.

6.2.7 Tx output power

The last of the initial parameters to be configured is the transmit output power level. This parameter sets the target EIRP level that the SatLink Terminal shall use when transmitting on the return link. Configuration of this target level will be described in section 6.3.2 in conjunction with the calibration procedure of the power level.

Prior to performing the Tx power calibration, the SatLink Terminal must correctly acquire the Forward Link as described in section 6.3.1 below.

6.3 Forward Link acquisition, Tx power calibration, and fine adjustment of antenna pointing and polarisation

Please perform antenna and ODU installation and alignment as described in Appendix G and the initial parameter configuration described in section 6.2 before proceeding with the procedures described here.

6.3.1 Forward link acquisition

Connect the Rx cable between the ODU and IDU (if not already connected). Verify that the Rx power level is between 0 dBm and –65 dBm at the input of the IDU (between –25 dBm and –65 dBm for the SatLink 1900/1901).

Publication no. 101557, Rev. T, November 3th, 2006

Page 32

Page 33

If the antenna, ODU, and forward link parameters have been set correctly (section 6.2.2 - Antenna and ODU parameter configuration, and section 6.2.4 Forward link parameters) and the IDU Rx power level is as specified above, the STM SatLink Terminal is ready to acquire the forward link:

1. If not already logged on, start the STM SatLink Terminal and login as installer (user = install, factory

default password = dvbrcs) after having seen the message

Starting DVB interface.

2. Enter the CLI command dvb rx start to acquire the forward link.

3. The CLI message

Forward Link up

is displayed on the CLI output after successful acquisition of

the forward link

The reader is referred to Appendix P for a description of the steps performed by the SatLink terminal when acquiring the forward link.

If the STM SatLink Terminal reports Rx tuning failed please check the following:

• ODU parameter setting – section 6.2.2

• Forward link parameter setting – section 6.2.4

• That the Rx cable is properly connected to both the STM SatLink Terminal and the LNB

• That the signal level in to the IDU is between 0 dBm and –65 dBm (-25 dBm and –65 dBm for

SatLink 1900/1901)

• That the antenna/ODU has been properly aligned (both antenna pointing and polarisation adjustment

correct)

To ensure good performance (less than one error event at MPEG2-TS level per hour) for the forward link, please verify that the SNR value, reported using the

dvb rx show

command, is higher than the recommended values given in the table below. If the required SNR is not met, please verify the antenna pointing.

FEC Code

Rate

Required forward link SNR (Eb/No) for

achieving less than one error event per hour 1/2 3.7 dB 2/3 4.2 dB 3/4 4.7 dB 5/6 5.2 dB 7/8 5.6 dB

6.3.2 Tx power calibration

This section describes how to calibrate the Tx output power when using the STM SatLink 4033/4035 transceiver and the STM SatLink 3000 transmitter. See Appendix J for a description of how to do Tx power calibration for other transmitters.

Tx power level calibration and return link acquisition shall only be performed if the forward link has been acquired and is operating properly.

Table 10: Required forward link SNR values

Publication no. 101557, Rev. T, November 3th, 2006

Page 33

Page 34

1. Ensure that the STM SatLink Terminal configuration procedure in section 6.2 has been performed.

2. Ensure that the STM SatLink Terminal receiver is started and the Forward Link is acquired

• Check that the receiver is running by issuing the CLI command

not turned on, start the receiver by issuing the CLI command

• Check that the forward link has been acquired by verifying that the CLI message

is displayed on the CLI output.

dvb rx show

dvb rx start

. If the receiver is

Forward Link

3. Ensure that the STM SatLink Terminal transmitter is turned off

• Enter the CLI command

, use the command

dvb tx show

dvb tx logoff

. Verify that the transmitter is

to turn the transmitter off.

Off

. If the transmitter is

4. Ensure that the Tx cable from the STM SatLink Terminal to the ODU is connected

5. Use the CLI command

dvb tx eirp <level>

to configure the transmit EIRP level. The Terminal can either be configured to transmit at maximum level (operating at the P1dB compression point) using the command

dvb tx eirp max

, or alternatively the wanted EIRP level can be set to a given

level for use in a system where the power level received at the satellite is aligned for all terminals.

Example:

dvb tx eirp 42 sets the output to 42 dBW. dvb tx eirp max selects maximum output power

Save the configuration by using the CLI command

save config

Verify the transmitter configuration using the CLI command

dvb tx show

Example:

# dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Disabled Population ID : 2 IDU output power : -15 dBm EIRP : max Default CW Frequency: 14.488000 GHz AAL5 Encapsulation : VC Mux

DVB Transmitter Status

---------------------State : Off #

The CW frequency to use for measurements during the calibration procedure is obtained from the service provider or satellite operator. If the CW frequency needs to be changed, please consult Appendix F.2

7. Contact the satellite operator / control centre to clarify the line-up procedures for transmission power

calibration and fine adjustment and verification of polarisation of the STM SatLink terminal.

8. Have contact by phone with the control centre when performing the following measurements.

Publication no. 101557, Rev. T, November 3th, 2006

Page 34

Page 35

9. Issue the CLI command

dvb tx calibrate

to start the automatic transmitter power calibration routine. During this calibration, the transmit EIRP level is detected and the IDU output level is automatically adjusted to the level required for transmitting with the configured EIRP level. Hence no manual configuration of the IDU output power level or cable attenuation is required.

Ask the control centre if they can detect the transmitted CW. If they are not able to see the CW at the specified frequency and expected output power level, please power off the STM SatLink Terminal immediately.

Example:

# dvb tx calibrate Using preconfigured CW frequency 14.488000 GHz RF Wanted= 30.7, RF Measured= 0.0, If output= -30.1 RF Wanted= 30.7, RF Measured= 30.6, If output= -26.6 ODU output level stabilised Saving configuration

Note: CW transmission is still enabled to allow for crosspolarisation adjustment of the antenna

Configuration Saved

10. Verify the calibrated power levels using the CLI command

dvb tx show

Example:

dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Enabled Population ID : 2 IDU output power : -11 dBm EIRP : max Default CW Frequency: 14.488000 GHz AAL5 Encapsulation : VC MUX

DVB Transmitter Status

---------------------State : On IDU Output Power : -13.6 dBm ODU Output Power : 33.2 dBm EIRP : 46.5 dBW delta T : 263366 microseconds Frequency Correction : -2650 Hz #

Leave the CW on for fine adjustment of the antenna, or turn it off using the CLI command

dvb tx cw off

6.3.3 Fine adjustment of antenna pointing

If the CW from the power calibration routine is still on, it can be used for the antenna fine-adjustment as well. Otherwise start CW transmission on the default CW frequency by issuing the CLI command

tx cw on.

dvb

Publication no. 101557, Rev. T, November 3th, 2006

Page 35

Page 36

Ask the control centre if they are measuring the expected power level for the CW. If not, it is likely that the antenna pointing is not optimal. Fine-adjust the antenna pointing until the CW power level detected by the control centre is within their requirements.

6.3.4 Fine adjustment of antenna polarisation

Ask the control centre if the measured level of the CW on the crosspolar transponder is below their requirement. If not, fine adjust the rotation angle of the Rx/Tx/Feed Assembly with respect to the feed horn until the polarisation discrimination is within specified limits.

Publication no. 101557, Rev. T, November 3th, 2006

Page 36

Page 37

6.4 Test of DVB-RCS connection

After the ODU line-up procedure in section 6.3 (or alternatively, Appendix J.1) has been successfully completed the STM SatLink Terminal is ready to logon to the DVB-RCS network.

The STM SatLink Terminal is only allowed to log on to the DVB-RCS network if its DVB MAC address is registered at the Gateway. Registration of the terminal’s MAC address at the gateway is a network operator responsibility. The CLI command address of the STM SatLink Terminal or it can be found on the label underneath the STM SatLink Terminal chassis. The MAC address is also shown on the CLI message display during the boot procedure of the STM SatLink Terminal.

Example:

# device show

System Information

-------------------------------Name : Terminal-1025 Location : Oslo Contact : satlink.support@stmi.com System time : Thu Nov 20 12:03:15 2004

-------------------------------Model : SatLink 1000 HW ID : 103346 Main board ID : 102805 R5.2

MAC addresses

-------------------------------Ethernet (LAN) : 00:60:c0:2f:46:64 Satellite (DVB) : 00:60:c0:2f:46:64 #

Then do the following:

1. If the receiver is not already on, enter the CLI command

link. The STM SatLink Terminal has successfully locked to the forward link when the message

Forward link up

is displayed.

2. Enter the CLI command

dvb tx logon

network. If successfully logged on, an output similar to the example below is written to the Telnet/HyperTerminal window. Use the CLI command

Example:

Initial Synchronisation: Forward link up All tables acquired Logging on...successful Fine Synchronisation...achieved Return link up Two-way link established

device show

to start the transmitter and logon to the DVB-RCS

can be used to display the DVB MAC

dvb rx start

dvb tx show

to acquire the forward

to show the transmitter status.

Publication no. 101557, Rev. T, November 3th, 2006

Page 37

Page 38

4. To test the IP connection to the gateway open an MS-DOS window on the PC connected to the STM

SatLink Terminal LAN (Ethernet). Type the MS-DOS command ‘ping 10.10.10.1’ to test the connection to the gateway router5. If the router gives a positive reply to the ping message then the DVB-RCS satellite link is successfully up and running.

5. To test the connection to the Internet, type the MS-DOS command ‘ping www.stmnetworks.com’. If

a reply is received the PC connected to the STM SatLink Terminal has a working connection to the Internet via the DVB-RCS satellite network.

6.5 Prepare the STM SatLink Terminal for normal operation

The connection to the Internet over the DVB-RCS satellite network should now be tested and found working. The only thing left is then the final configuration to prepare the STM SatLink Terminal for normal operation.

The STM SatLink Terminal must be started and you must be logged in as a user with minimum privilege level 2 (e.g.

1. Configure the STM SatLink Terminal to automatically start the receiver by typing the CLI command

dvb rx autostart on

Setting the Rx autostart on will ensure that the receiver is started automatically after e.g. power failure, link failure, gateway restart, or a software failure, etc. without needing user intervention.

Verify that auto start is on for the receiver by typing the CLI command

2. Configure the STM SatLink Terminal to automatically start the transmitter by typing the CLI

command

Setting the Tx autostart on will ensure that the transmitter is started automatically after e.g. power failure, link failure, gateway restart, or a software failure, etc. without needing user intervention.

Or alternatively follow the procedure in section 10 if the terminal shall use traffic-initiated logon.

Verify that auto start is on for the transmitter by typing the CLI command

3. Save the configuration by typing the CLI command

install

user) before completing the following operations.

dvb tx autostart on

dvb rx show

save config

dvb tx show

Replace the IP address 10.10.10.1 with the actual IP address of the DVB-RCS gateway router if the

default IP configuration of the DVB-RCS gateway is not used.

Publication no. 101557, Rev. T, November 3th, 2006

Page 38

Page 39

7. LAN DHCP Server

To handle automated address assignment, the IETF has designed a protocol (RFC 2131) known as Dynamic Host Configuration Protocol (DHCP). DHCP allows a computer to acquire automatically all IP configuration information it needs when entering the network.

Whenever a new computer connects to the STM SatLink Terminal’s LAN and the DHCP server in the Terminal is enabled, the computer will be allocated an IP address by the DHCP server from the pool of addresses defined by the STM SatLink Terminal LAN subnet (defined by the LAN netmask). IP addresses that will not be allocated automatically to new computers are the STM SatLink Terminal’s own IP address and eventually IP addresses specifically excluded during configuration.

Many DVB-RCS networks support automatic configuration of the terminal’s DHCP server parameters when the terminal logs on to the network. In that case, the DHCP server configuration described in section 7.1 below should be skipped.

7.1 Configuration of the DHCP server

The terminal administrator has the possibility to configure the following parameters:

• Server Status: Enable or disable the STM SatLink Terminal LAN DHCP server.

• Lease time: Set the lease time for an IP address allocated to a host on the LAN

• No. of IP addresses excluded: Specifies the number of IP addresses to be excluded from the

available range of addresses defined by the STM SatLink Terminal LAN subnet. The excluded range of IP addresses will be the upper range of the LAN subnet. I.e. if the STM SatLink Terminal LAN is allocated the IP addresses 10.10.10.1 to 10.10.10.254, and 2 IP addresses are excluded for use by the DHCP server, then the DHCP server will have the IP address range

10.10.10.1 to 10.10.10.252 available for DHCP clients.

• Primary DNS server: IP address for the primary DNS server to be used by the hosts on the STM

SatLink Terminal LAN.

• Secondary DNS server: IP address for the secondary DNS server to be used by the hosts on the

STM SatLink Terminal LAN.

To enable the DHCP server, use the CLI command

The lease time of IP addresses can be configured using the CLI command Example

# ip dhcp leasetime 1 D

The command in this example will configure the lease time to 24 hours (one day).

ip dhcp enable.

ip dhcp leasetime.

Publication no. 101557, Rev. T, November 3th, 2006

Page 39

Page 40

To view the DHCP server configuration and, if enabled, the DHCP client table, use the CLI command

dhcp show.

Example:

# ip dhcp show

DHCP Server Status

------------------------------------------Server Status : Enabled Server IP address : 192.168.0.1 Server IP address range : Starting IP address : 192.168.0.1 Ending IP address : 192.168.0.254 No of IP addresses excluded : 1 Excluded IP address range : Starting IP address : 192.168.0.254 Ending IP address : 192.168.0.254 Lease Time : 1 Day 0 Hours 0 Minutes 0 Seconds

DHCP Client Table

----------------Host Name IP Address MAC Address Lease expires Test 192.168.0.2 1>00:06:5b:e0:6f:48 In less than 15 minutes #

The DHCP client table is only displayed when the DHCP server is enabled. The table will display the host name, the allocated IP address, the host MAC address and the address lease expiration time for each computer registered by the DHCP server.

Until the terminal has acquired lock on the forward link and received the system time via the Time and Date Table (TDT) from the Gateway, it will have no information of the current time. The DHCP server will in this situation only lease IP addresses to the LAN hosts for 15 minutes until the system time is set. The message

than 15 minutes

will be displayed in the DHCP client table.

Lease expires in less

7.2 Changing the SatLink Terminal LAN Interface IP address

If the IP address of the SatLink Terminal LAN Interface is changed, the IP addresses of all end-user devices that are connected to the SatLink Terminal LAN must be updated correspondingly.

This also applies to those end-user devices that have obtained their IP addresses automatically from the DHCP server. As the end-user devices will not normally issue a request to the DHCP server before the lease-time of their IP addresses has expired, an IP address update of these devices must be manually triggered by the end-user.

For example, to trigger a PC running Microsoft Windows OS to request a new IP address from the DHCP server, the end-user can issue the command ipconfig /renew in the DOS command window. If the end-user device does not have provisioned means for manually triggering a DHCP request for IP address update, please power off and on again the end-user device. This will normally result in the enduser device requesting the Terminal DHCP server for an IP address as part of the end-user device initialisation process.

Publication no. 101557, Rev. T, November 3th, 2006

Page 40

Page 41

8. Quality of Service

QoS is used to provide differentiated handling of different types of IP traffic. The aim is to be able to satisfy traffic flows for applications with different requirements, while at the same time minimising the required bandwidth on the return link. For example, to assure a given return link bandwidth with minimal delay jitter for VoIP or Video real time traffic by avoiding influence from traffic that is not so sensitive to delay jitter, e.g. Web browsing and FTP.

The STM SatLink Terminal does QoS differentiation on the return link based on the DiffServ architecture, and can work in networks that offer performance as per hop behaviour (PHB) as defined in the DiffServ architecture. QoS on the forward link is handled by the DVB-RCS Gateway alone, and not discussed further in this manual.

The STM SatLink Terminal supports use of the following PHBs and PHB groups on the return link6:

• Best Effort (BE) PHB

• Critical Data (CD) PHB

• Real Time Video Conferencing (RT-ViC) PHB group

• Real Time Voice over IP (RT-VoIP) PHB group

Internally the STM SatLink Terminal classifies the traffic that shall be sent on the return link into different QoS groups. One or more QoS groups will then be mapped to a PHB / PHB group in the network. The terminal internally supports the following QoS groups:

QoS Group ID QoS Group Name Maps to PHB

0 Best Effort Best Effort (BE) 1 VoIP Audio Real Time Voice over IP (RT-VoIP) 2 VoIP Signalling Real Time Voice over IP (RT-VoIP) 3 ViC Video Real Time Video Conferencing (RT-ViC) 4 ViC Audio Real Time Video Conferencing (RT-ViC) 5 ViC Signalling Real Time Video Conferencing (RT-ViC) 6 Critical Data Critical Data (CD)

The QoS implementation in the terminal is based on a multi-field classifier, i.e. the DSCP/TOS field and other fields in the IP header are used to classify which QoS group each IP packet belongs to. IP packets belonging to different QoS groups are then treated differently by the terminal. The terminal can be configured to support traffic differentiation based on DSCP values as used in DiffServ based networks.

Associated with each QoS group is a QoS policy. Parameters that impact the QoS policy are:

• Capacity request algorithm and parameters

The capacity request algorithms for real-time traffic are tailored to request a continuous rate capacity,

The capacity request algorithms for best effort and critical data are designed for more bursty and delay insensitive traffic such as Web browsing and FTP.

• Transmission PID or VPI/VCI

Used to give precedence to real-time traffic when interleaving traffic from different QoS groups at the MPEG/ATM level

• Drop policy

Critical Data and Real Time Video Conferencing are only available on the STM SatLink 1000, 1900,

and 1901 when the software license key for 4 QoS classes has been set (see section 15.4).

Publication no. 101557, Rev. T, November 3th, 2006

Page 41

Page 42

Real-time traffic packets are dropped at the head of the transmission queue if the queue overflows, while best effort traffic packets are dropped at the tail of the queue.

The transmission queue length are tailored for each QoS class

• Precedence

- Real-time traffic is given precedence over best effort traffic.

Typing CLI command

QOS Policy Table Grp Cls CrM Pri QLength Drop Timeout Description 0 0 0 0 400000 0 120 Best Effort 1 1 1 1 15000 1 120 VoIP Audio 2 1 1 2 4000 1 120 VoIP Signalling 3 2 1 5 500000 1 120 VIC Video 4 2 1 4 50000 1 120 VIC Audio 5 2 1 3 10000 1 120 VIC Signalling 6 3 0 6 400000 0 120 Critical Data

# ip qos show

will output, among other, the QoS Policy Table:

The parameters in the QoS policy Table are not user configurable.

8.1 Configuring QoS for the return link

In order to determine the QoS group an IP packet belongs to, the STM SatLink terminal uses a multi-field classifier. This multi-field classifier is used to perform a look-up in a QoS classification table. This table can store up to 15 different masks that the IP packets will be matched to.

The following parameters in the IP header can be used for doing the QoS classification:

• IP source address

• IP destination address

• DSCP / TOS

• Protocol type

• TCP/UDP source port number

• TCP/UDP destination port number

Additionally the QoS classificator in the STM SatLink Terminal can set the DSCP field in the IP header based on the multi-field classifier.

The format of the QoS classification table is:

Index QoS

Group

0-255 0-6 0-63 0-255 0-65535 0-65535

The index parameter is used to uniquely identify an entry in the QoS classification table and decides the order in which the QoS classification table is searched. When an IP packet is to be QoS classified, the QoS classification table is searched from index 0 and upwards. If a match is found, the search is stopped, and the IP packet is thereafter handled with the QoS Group for this entry in the QoS classification table. If a match is not found for an IP packet it will be treated as best effort traffic.

Dest. IP Address Mask

Source IP Address Mask

DSCP Range (Start-Stop values)

Protocol Type (up to 3 values)

TCP/UDP Source Port Range (StartStop values)

TCP/UDP Dest. Port Range (StartStop values)

Publication no. 101557, Rev. T, November 3th, 2006

Page 42

Page 43

The QoS Groups available for internal use in the STM SatLink Terminal are:

QoS Group ID QoS Group Name

0 Best Effort 1 VoIP Audio 2 VoIP Signalling 3 ViC Video 4 ViC Audio 5 ViC Signalling 6 Critical Data (CD)

In addition, the QoS classification table can be configured to block traffic from being sent to the return link (see section 15.5).

Factory default configuration is that the QoS classification table is empty, and all traffic is handled as Best Effort (QoS Group 0). A user with privilege rights 2 (user install or equivalent) can configure a QoS Classification table in the terminal as explained below, but the use of other QoS groups than 0 can be inhibited by the network operator/service provider. Please contact the network operator/service provider for use of QoS group 1-6 for VoIP and Video real-time traffic and prioritised effort traffic (CD). Please note that QoS Groups 3-6 for Video and Critical Data will only be available on the STM SatLink 1000, 1900, and 1901 if the software license for 4 QoS classes is configured (see section 15.4).

The CLI command to be used to configure the QoS Classification table is

< group> <list of tags>

. This command has a variable length where one or more tags with

ip qos mask <index>

different tag parameters can be set. The tags are the different IP header parameters that can be used for QoS classification:

tag and tags parameters for CLI command Function

+src <ipaddr> <mask>

-src

+dst <ipaddr> <mask>

Define or modify IP source address and netmask Delete IP source address and netmask Define or modify IP destination address and netmask

-dst +dscp <min> <max>

-dscp

+prot <n> <p1> … <pn>

Delete IP destination address and netmask Define or modify DSCP range Delete DSCP range Define protocol value [0,255]. Up to 3 protocol values can be defined (n can be 1, 2, or 3).

-prot +sport <min> <max>

-sport

+dport <min> <max>

-dport

+dscpmark <dscp>

-dscpmark

Delete protocol values Define TCP/UDP source port number range Delete TCP/UDP source port number range Define TCP/UDP destination port number range Delete TCP/UDP destination port number range Define DSCP value to set in IP header Delete DSCP value to set in IP header, i.e. do not change the DSCP value

To view the current QoS configuration, use the CLI command

ip qos show

Examples: To add an entry in the QoS classification table matching IP packets with DSCP range 10-15 and assign these to the VoIP Audio QoS Group:

Publication no. 101557, Rev. T, November 3th, 2006

Page 43

Page 44

# ip qos mask 1 1 +dscp 10 15

To add an entry in the QoS classification table matching protocol type 7 and assign this to the VoIP Audio QoS Group:

# ip qos mask 2 1 +prot 1 7

To add one more classification criteria for the same entry, e.g. destination address:

# ip qos mask 3 1 +dst 10.10.22.0 255.255.255.0

To delete one classification criteria from an entry of the QoS classification table:

# ip qos mask 3 1 –prot

To delete the whole entry from the QoS classification table:

# ip qos mask 3 –all

To add a new entry for classifying VoIP Audio traffic:

# ip qos mask 1 1 +src 10.10.10.1 255.255.255.255 +dscp 10 15

To add a new entry for classifying VoIP Signalling:

# ip qos mask 4 2 +src 10.10.10.1 255.255.255.255

To view the current QoS configuration:

# ip qos show QOS Policy Table Grp Cls CrM Pri QLength Drop Timeout Description 0 0 0 0 400000 0 120 Best Effort 1 1 1 1 15000 1 120 VoIP Audio 2 1 1 2 4000 1 120 VoIP Signalling QoS Classification table Idx Grp Classification Parms 1 1 IPSrc= 10.10.10.1/255.255.255.255 DSCP = 10..15 2 1 Protocols = 7 4 2 IPSrc= 10.10.10.1/255.255.255.255 5 0 match all #

8.2 Configuring the terminal for VoIP

There are two QoS alternatives for the VoIP PHB group:

1. All VoIP traffic is mapped to QoS group 1.

2. VoIP audio is mapped to QoS group 1 and VoIP signalling is mapped to QoS group 2

The second option will protect the VoIP signalling from fluctuations in the VoIP audio traffic. However, to use this option, the terminal’s QoS classificator must be able to distinguish between VoIP signalling and VoIP audio in order to separate them into different QoS groups.

8.3 Configuring the terminal for Video (ViC)

The following QoS alternatives are available for the ViC PHB group:

1. All ViC traffic is mapped to QoS group 3.

2. ViC video is mapped to QoS group 3 and ViC audio+signalling is mapped to QoS group 4

3. ViC video is mapped to QoS group 3, ViC audio is mapped to QoS group 4 and ViC signalling is

mapped to QoS group 5

Publication no. 101557, Rev. T, November 3th, 2006

Page 44

Page 45

The second alternative has the advantage that the audio and the audio-signalling are protected from fluctuations in video traffic. The third alternative has the additional advantage of giving extra protection to the ViC signalling. However, to use option two and three, the terminal’s QoS classificator must be able to distinguish between the video, audio, and signalling components of the Vic in order to separate them into different QoS groups.

8.4 DSCP and DiffServ

The following DSCP values are recommended to use on equipment connected to the STM SatLink Terminal:

Traffic Recommended DSCP Recommended QoS group Best Effort 0 (000000) 0 Critical Data 26 (AF31; 011010) 6 ViC bulk 46 (EF; 101110) if VoIP is not in

use

47 (101111) otherwise

ViC video 46 (EF; 101110) if VoIP is not in

use

47 (101111) otherwise ViC audio+ signalling 39 (100111) 4 ViC audio 39 (100111) 4 ViC signalling 35 (100011) 5 VoIP bulk 46 (EF; 101110) 1 VoIP audio 46 (EF; 101110) 1 VoIP signalling 43 (101011) 2 Unconditional packet dropping 3 (000011) n.a.

Recommended mapping to support standardised DiffServ compliance:

DSCP Recommended QoS group Comment

0 (000000) 0 Best effort 56 (111000) 6 Requires forwarding precedence 48 (110000) 6 Requires forwarding precedence

Other, not specifically treated 0 Best effort

Recommended mapping for support of the standardised AF PHB group, using AF class 3 as example:

DSCP Recommended QoS group Comment

26 (AF31; 011010) 6 AF Class 3 low drop precedence 28 (AF32, 011100) 0 AF Class 3 medium drop

precedence

30 (AF33, 011110) 0 AF Class 3 high drop precedence

Recommended mapping for support of the standardised EF PHB:

DSCP Recommended QoS group Comment

46 (EF; 101110) 1 This is an applicable mapping

for constant rate real-time applications like VoIP

Publication no. 101557, Rev. T, November 3th, 2006

Page 45

Page 46

46 (EF; 101110) 3 This is an applicable mapping

for variable rate real-time applications like ViC

Publication no. 101557, Rev. T, November 3th, 2006

Page 46

Page 47

9. Bandwidth on Demand

The STM SatLink System supports Bandwidth on Demand (BoD) based on the following modes:

• Rate-based BoD using low jitter assignments

• Volume-based BoD using immediate assignments, aiming at achieving good satellite resource

efficiency

• A combination of the above two BoD modes, targeting a balance between good performance and

good efficiency

These BoD modes use the DVB-RCS capacity request categories on the return link:

• Rate based (RBDC)

• Volume based (VBDC) /Absolute Volume Based (AVBDC)

Please refer to [10] for a detailed description of the return link capacity request categories.

As mentioned in section 8 the STM SatLink Terminal supports four PHB / PHB groups:

• Best Effort (BE) PHB

• Critical Data (CD) PHB

• Real Time Video Conferencing (RT-ViC) PHB group

• Real Time Voice over IP (RT-VoIP) PHB group

Default factory configuration of the STM SatLink Terminal is to use the Best Effort PHB for all return link traffic and utilise the Rate-based BoD mode. That is, the terminal is pre-configured to request capacity from the NCC/Gateway using the RBDC request category. Normally, the gateway or ISP will issue new Service Level Agreement parameters during the log-on sequence and, thus, override the default settings.

The capacity requested by the terminal and the capacity granted by the NCC to the STM SatLink Terminal on the return link can be viewed using the CLI command

Example:

# dvb tx show -capacity

Capacity parameters per channel:

------------------------------Channel CRA[kbps] Allocated[kbps] 0 0 156

Requested capacity per QoS class:

--------------------------------Channel CRClass MaxRBDC[kbps] MaxVBDC[kB] RateReq[kbps] VolReq[octs] Description 0 0 512 1000 138 0 Best Effort 0 1 128 0 0 0 VoiP 0 2 400 55 0 0 ViC

0 3 50 0 0 0 Critical Data

In the example above the NCC has not assigned any continuous rate capacity (CRA) to the terminal. The terminal is authorised to request up to a maximum of 512 kbps Rate Based Dynamic capacity and to have a maximum of 977 Kbytes of outstanding not yet granted Volume/Absolute Volume Based Dynamic Capacity requested for the Best Effort PHB. Additionally the terminal is authorised to request Rate Based Dynamic Capacity for the VoIP PHB Group, a combination of Rate and Volume Based Dynamic Capacity for the ViC PHB group, and Rate Based Dynamic Capacity for the Critical Data PHB. In this

dvb tx show -capacity

Publication no. 101557, Rev. T, November 3th, 2006

Page 47

Page 48

example the terminal requested 138 kbps capacity and was granted by the Gateway NCC a total of 156 kbps.

• Channel: All traffic in the current version of STM SatLink is transferred on the logical channel 0,

which is the default logical channel from the terminal to the satellite GW.

• CRA: Allocated CRA capacity (DVB-RCS Continuous Rate Assignment capacity). The DVB

RCS Gateway assigns CRA capacity to the terminal at logon. Changes in the CRA level assigned to the terminal during its log-on session are notified to the terminal. The amount of CRA to be assigned to the terminal is a network operator/service provider decision.

• Allocated: Allocated refers to the total aggregated amount of capacity

(CRA+RBDC+VBDC/AVBDC+FCA) that the NCC has granted to the terminal as a grand total for all QoS classes

• CRClass: CRClass 0 represents BW demand for the BE PHB. CRClass 1, 2 and 3 represents BW

demand for the VoIP PHB group, the ViC PHB group and the VoIP PHB group, respectively.

• MaxRBDC: Maximum RBDC is the upper limit of Rate-Based Dynamic Capacity that a terminal

can request. The maxRBDC is set from the DVB-RCS Gateway and is a network/service provider decision. The STM SatLink Terminal is pre-configured with a default value of maxRBDC for the Best Effort QoS class. This default value will be overwritten by the operator-defined value at logon.

• MaxVBDC: MaximumVBDC is the upper limit of not yet granted VBDC/AVBDC requested that a

terminal will have outstanding at any time. The maxVBDC is set from the DVB-RCS Gateway and is a network/service provider decision. The default value of this parameter is 0. This default value will be overwritten by the operator-defined value at log-on time

Publication no. 101557, Rev. T, November 3th, 2006

Page 48

Page 49

10. Traffic Initiated Logon

The SatLink Terminal can be configured to logon automatically to the DVB-RCS gateway when it has traffic to send and logoff again when it has had no traffic to send for a configurable timeout period. This mode is useful for terminal installations where low power consumption is important (e.g. when powered by solar power and batteries). It is also useful in systems where it is desirable to reduce the signalling bandwidth on the return channel (by avoiding use of dedicated SYNC slots when the terminal has no traffic to send).

The power saving mode requires the use of the STM SatLink 403x transceiver or the STM SatLink 3000 transmitter. The power consumption will then be reduced from typically 27W to approximately 12W when the terminal is logged off when using the SatLink 403x transceiver with SatLink 10007.

The STM SatLink Terminal can be configured to use traffic initiated logon by typing the CLI command

dvb tx autostart traffic <timeout>

will wait before logging off when it has no traffic to send.

Example:

dvb tx autostart traffic 5

configures the SatLink Terminal to use traffic initiated logon and automatically log off the network after not having any traffic to send for 5 minutes.

Verify the configuration of the transmitter mode and the timeout for traffic initiated logon by typing the CLI command

dvb tx show

where

is the timeout in minutes the terminal

When using the STM SatLink 4033 transmitter with STM SatLink 1000 the power consumption will be

reduced from typically 30W to approximately 12W when the terminal is logged off.

Publication no. 101557, Rev. T, November 3th, 2006

Page 49

Page 50

11. Header compression

The header compression feature has been implemented into the STM SatLink system to reduce the required bandwidth, specially for VoIP calls. But also other application benefits by the Header Compression feature. Header compression greatly reduces the amount of overhead associated with each encapsulated IP packet. It is accomplished by removing, or reducing, redundant information in the packet headers at one or more layers.

There are two options when using header compression on the STM SatLink system. One is to enable header compression only for the DSM-CC header. The other option is to enable it for both DSM-CC and IP/UDP header.

11.1 Enabling Header compression

The terminal will detect if the GW has the Header Compression enabled, and only use the feature if it is available on the GW. If the Header compression is enabled on the Terminal, but not on the GW, it does not take effect. The terminal will then continue transmit traffic as usual, without header compression.

To check if the Header Compression is an available feature on the GW, connect to the CLI interface of the terminal, and enable DSM-CC and UDP Header Compression and check the transmit status.

# dvb hdrcomp +dsmcc # dvb hdrcomp +udp # dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Enabled Population ID : 2 IDU output power : -23 dBm EIRP : max Default CW Frequency: 14.488000 GHz ATM mode : VC-Mux

Header Compression : UDP/IP/DSM-CC

DVB Transmitter Status

-------------------------------State : On

Header Compression : UDP/IP/DSM-CC

IDU Output Power : -22.9 dBm Eb/No : 13.5 dB Timing correction : 2605 us Frequency correction: 70 Hz

The text in bold shows the configured values and the status. In this example, Header compression is enabled on bothe the terminal and the GW. Always remember to save the new configuration, with the command:

SAVE CONFIG

Publication no. 101557, Rev. T, November 3th, 2006

Page 50

Page 51

If the Header compression is not available on the GW, the values:

# dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Enabled Population ID : 2 IDU output power : -23 dBm EIRP : max Default CW Frequency: 14.488000 GHz ATM mode : VC-Mux

Header Compression : UDP/IP/DSM-CC

DVB Transmitter Status

-------------------------------State : On

Header Compression : Disabled

IDU Output Power : -22.9 dBm Eb/No : 13.5 dB Timing correction : 2605 us Frequency correction: 70 Hz

DVB TX SHOW

command will display these

11.2 Disable Header compression

To disable the Header Compression, use the same set of commands, as used when it was enabled, but with a ‘–‘ instead of a ‘+’.

# dvb hdrcomp -dsmcc # dvb hdrcomp -udp # dvb tx show

Satellite (DVB) TX Configuration

-------------------------------Auto start : Enabled Population ID : 2 IDU output power : -23 dBm EIRP : max Default CW Frequency: 14.488000 GHz ATM mode : VC-Mux

Header Compression : None

DVB Transmitter Status

-------------------------------State : On

Header Compression : Disabled

IDU Output Power : -22.9 dBm Eb/No : 13.5 dB Timing correction : 2605 us Frequency correction: 70 Hz

Publication no. 101557, Rev. T, November 3th, 2006

Page 51

Page 52

12. Routing of Multicast Traffic

12.1 Setting up routing of multicast traffic from the SatLink Terminal LAN to the gateway

The STM SatLink Terminal can be configured to route multicast traffic from the LAN to the return channel (to the gateway). User privilege level 2 is required for configuring the multicast routing.

To set up static routing of a multicast group from the LAN to the satellite interface, use the CLI command

ip addroute <IP group address> <subnet mask> <ifnum>.

the IP multicast address that shall be routed from the Ethernet LAN to the gateway, netmask for this routing entry, and

ifnum

is the interface number (always set this to 3 = Satellite

Interface).

Example:

# ip addroute 224.0.2.2 255.255.255.255 3

The command in the example will set up a route for the multicast group with the IP address 224.0.2.2 to the satellite interface (to the gateway). The MAC address used on the return link will be calculated according to RFC 1112.

To view the defined multicast routes use the CLI command

ip show -mcast

Example:

# ip show -mcast IP Multicast Routing Table RouteAddress AddressMask IfIndex

224.0.0.2 255.255.255.255 1

224.0.2.2 255.255.255.255 3

Subnetwork internal multicast groups on the LAN will show up in the multicast route table. LAN internal multicast traffic is e.g. generated by Windows (Network neighbourhood, etc.). Such traffic will have the

IfIndex

To delete multicast routes use the CLI command

ip delroute <IP group address> <subnet mask> <ifnum>

Example:

# ip delroute 224.0.2.2 255.255.255.255 3

will delete the static route of the multicast group with the IP address 224.0.2.2 from the Ethernet LAN to the satellite interface (gateway).

Enter the CLI command

save config

to save the return link multicast configuration.

Where

set to 1.

IP group address

subnet mask

is the

Publication no. 101557, Rev. T, November 3th, 2006

Page 52

Page 53

13. Updating the STM SatLink Terminal SW

The flash in the STM SatLink Terminal can store two SW images, both the currently used SW and a backup version in case download of a new SW version fails.

Always use the command the software version of a terminal since this command automatically deletes old backup software versions and backs up the current software and the configuration.

Do not use the CLI command to delete old backup software version may block future automatic software upgrades.

13.1 Automatic software update

The STM SatLink Terminal may be configured for receiving software updates from the DVB-RCS gateway automatically. Whenever the software upgrade application at the DVB-RCS gateway transmits a new software image, the software upgrade routine in the STM SatLink Terminal will start receiving the software image given that the new software image has a newer revision than the current software. When the software download is completed successfully, the STM SatLink Terminal will restart automatically in order to activate the new software version.

To automatically receive software upgrades, the STM SatLink Terminal must be configured with the PID, the multicast IP address, and the UDP port allocated by the system operator for multicast software upgrade, with software upgrade via multicast enabled, and with the terminal receiver locked on the forward link. Issue the CLI command configuration:

# sw show

SW versions

-------------------------------Boot : 9.0.0.1 Current : 9.1.4.63 Backup : 9.1.3.60

Manual SW upgrade settings

-------------------------------TFTP server IP addr : 10.10.1.1 File name : dvb-rcst.tgz

Automatic SW upgrade settings

-------------------------------Activated : No PID : 511 IP address : 224.0.1.59 Port No. : 2001

Licenses for SW options

-------------------------------None

Users with privilege level 2 may activate and deactivate the automatic software upgrade routine, and change the PID, IP address, and UDP port number where the software is received by using the CLI command

sw mcast

Publication no. 101557, Rev. T, November 3th, 2006

sw upgrade

dload

sw show

as described in section 13.2 to manually upgrade

to upgrade the software of the terminal since failure

to examine the automatic software upgrade

Page 53

Page 54

Example:

# sw mcast 1 511 224.0.1.59 2001 #

will enable automatic reception of software upgrades on PID 511, IP address 224.0.1.59 and UDP port number 2001.

13.2 Manual software update

Users with minimum privilege level 2 may use the CLI command 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.

Below is described in detail how to upgrade the STM SatLink Terminal software:

1. Verify the default settings for the manual software upgrade with the CLI command

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

4. Execute the SW upgrade by typing

sw upgrade

sw show

, then restart the STM SatLink Terminal

Example:

# sw show

SW versions

-------------------------------Boot : 9.0.0.1 Current : 9.1.4.63 Backup : 9.1.3.60

Manual SW upgrade settings

-------------------------------TFTP server IP addr : 10.10.1.1 File name : dvb-rcst.tgz

Automatic SW upgrade settings

-------------------------------Activated : Yes PID : 511 IP address : 224.0.1.59 Port No. : 2001

Licenses for SW options

-------------------------------None #

# sw upgrade -default dvb-rcst.tgz 10.10.10.8

# sw upgrade

Software download in progress, please wait...................................

...........................................................................

File Transfer complete Configuration Saved

sw upgrade

to download a new

sw show

Publication no. 101557, Rev. T, November 3th, 2006

Page 54

Page 55

The terminal then reboots automatically.

13.3 Restoring the backup software

If, for some reason, the old software must be restored, then the following steps have to be executed. The current SW will be deleted when restoring the backup SW and the configuration used with the backup SW will be restored and activated.

1. Restore the previous SW and configuration with the command

Example:

# sw restore Restoring backup SW 9.1.3.55 Current SW 9.1.3.56 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 Terminal. Connection will be closed Reconnect when the terminal has restarted (1-2 minutes)

sw restor

Publication no. 101557, Rev. T, November 3th, 2006

Page 55

Page 56

14. STM SatLink and DVB-S2

The DVB-S standard is currently the most widely used transmission standard within the satellite communications field. When it was introduced in 1994 it represented state-of-the-art with respect to bandwidth and power efficiency. The key elements in the DVB-S standard were the use of QPSK modulation and concatenated Reed-Solomon / Viterbi coding for FEC protection of user data.

Recent advances in the field of digital coding and modulation techniques have made possible a technology upgrade of the DVB-S standard – known as the DVB-S2 standard. In the DVB-S2 standard there are primarily 3 features that directly translate to improved performance:

• Modulation – support both QPSK and 8-PSK

• Coding – LDPC-BCH with performance close to Shannon bound

• Reduced carrier roll-off

There are several ways the benefits of DVB-S2 can be realised. This will vary from system to system and is dependent on several factors such as satellite performance, link characteristics, RF equipment etc.

For a power limited transponder, DVB-S2 offers the possibility to push 30 % more user bits through the channel while maintaining the same link quality and transmit power.

For a bandwidth limited transponder the potential to save bandwidth is even bigger, as transmit power can be increased allowing higher FEC rates and/or moving from QPSK to 8-PSK modulation. In such scenarios bandwidth savings can approach 50 %.

But there are other ways to gain from DVB-S2 as well. With the improved coding performance of DVBS2 the satellite coverage area may be greatly expanded. As an example, consider the satellite coverage map below. With DVB-S2 one can tolerate 2 dB lower transmit EIRP from the satellite, which translates into a very significant expansion of territory covered by the service. This enables new markets and customers to be addressed without the need for setting up additional teleports or having to use multiple satellites to obtain the desired coverage area.

Figure 3: Sample satellite coverage area

Publication no. 101557, Rev. T, November 3th, 2006

Page 56

Page 57

14.1 DVB-S2 Modulation

The STM DVB-S2 ASIC’s supports 2 different modulation rates:

• QPSK

• 8-PSK

The figure below shows the modulation constellations for QPSK and 8-PSK modes supported by the DVB-S2 standard. With QPSK we transfer 2 bits per modulation symbol, while with 8-PSK we are able to transfer 3 bits per modulation symbol.

Hence the potential gain of going from QPSK to 8-PSK can be as high as 50 %.

QPSK

8-PSK

Figure 1: QPSK and 8-PSK constellations

14.2 DVB-S2 Coding

DVB-S2 uses advanced LDPC code concatenated with BCH codes. Together this coding scheme results in a performance that is only 0.7-1.0 dB away from the theoretical Shannon bound indicated by the dotted red line in the figure below. This translates to an improvement in coding gain of close around 2 dB compared to DVB-S systems using RS-Viterbi.

Figure 2: DVB-S2 Coding Performance

Publication no. 101557, Rev. T, November 3th, 2006

Page 57

Page 58

14.3 DVB-S2 Configuration

For operators that already have the SatLink 1910 IDU, a DVB-S2 upgrade path exists using the SatLink 100 extension module that plugs into the rear of the SatLink 1910. Units can be field-upgraded – there is no need to return units to STM for reconfiguration. The only requirement is that power is turned off when inserting the new extension card

Figure 5: The SatLink 100 DVB-S2 Extension Module

To enable the SatLink 100 card on a SatLink 1910 IDU, only one command is required on the CLI interface.

dvb rx phy -satlink100

Type the

# device show

System Information

-------------------------------Name : not set Location : not set Contact : not set System Up time : 2 days, 23:57:20 System time : not set, TDT not received

-------------------------------Model : SatLink 1910 HW ID : 103798 Main board ID : 103719 R6.5

Plugin-card HW

-------------------------------Model : SatLink 100 HW ID : 107261 Revision : 1.1 Serial Number : 0206010006

MAC addresses

-------------------------------Ethernet (LAN) : 00:60:c0:2f:ba:83 Satellite (DVB) : 00:60:c0:2f:ba:83

device show

command to verify that the card has been detected. See the text in bold.

Publication no. 101557, Rev. T, November 3th, 2006

Page 58

Page 59

When the card has been detected by the terminal, the DVB-S2 is configured the same was as DVB-S. described in section 6.2.4.

Example:

# dvb rx fwdlink 0 0 25000000 12380000 dvbs2 2 # save config # dvb rx show

Satellite (DVB) RX Configuration

-------------------------------Auto start : Disabled

Idx Pri Freq[GHz] SymbRate[Msps] Mode PopId * 0 0 12.380000 25.000000 DVB-S2 2

DVB Receiver Status (SatLink 100)

-------------------------------Rx State : Waiting for NIT (transponder one) Frequency : 12.380887 GHz Symbol Rate : 24.999998 Msps Modulation : 8PSK FEC Code rate : 2/3 Pilot : On Frame length : Long frame Roll off : 0.35 SNR : 15.2 dB

For V2 of the STM SatLink 1910 and 1000 IDU, there is no need for the SatLink 100 extension card. Both types are configured the same way as the example shows above.

Publication no. 101557, Rev. T, November 3th, 2006

Page 59

Page 60

15. Software options

The STM SatLink terminal supports the following features available as options and require license authorisation:

• Network Address Translation (NAPT, Global NAT, and Static NAT)

• GRE Tunnelling

• TCP/IP Performance Enhancing Proxy (PEP)

• 4 QoS Classes – Support for Video and Critical Data in addition to the two standard classes Best

Effort and VoIP.

• Return link access control (RAC)

• Maritime terminal (Mobil)

To show the list of the SW options that are authorised for use on the STM SatLink Terminal, use the CLI command

Example:

# sw show SW versions

-------------------------------Boot : 9.0.0.1 Current : 9.1.4.63 Backup : 9.1.3.60

Manual SW upgrade settings

-------------------------------TFTP server IP addr : 10.10.1.1 File name : dvb-rcst.tgz

Automatic SW upgrade settings

-------------------------------Activated : No PID : 511 IP address : 224.0.1.59 Port No. : 2001

Licenses for SW options

-------------------------------NAT PEP GRE QoS4 RAC

The licenses for optional SW functionality may be installed either remotely by the DVB-RCS System Operator or locally using the CLI command access to a new software option is wanted in order to receive a license key.

Example:

# sw license nat mykeyforenablingnat

Once the right to use a SW option has been authorised by means of license installation, the SW functionality can be enabled using the appropriate CLI command (as explained in the following subsections).

sw show

sw license

. Please contact the System Operator or ISP if

Publication no. 101557, Rev. T, November 3th, 2006

Page 60

Page 61

Example:

# ip nat enable

The CLI help function for the different SW options requiring licenses (e.g. not be available unless the SW option is authorised by installing the necessary license key.

? ip nat

) will

15.1 Network Address Translation

Network Address Translation is a mechanism to provide transparent IP-level access to the Internet from a local site with a private address range without requiring all the hosts on the site to have globally valid IP addresses. NAT translates addresses in incoming and outgoing IP packets by replacing the source address in each outgoing IP packet with the globally valid IP address, and replacing the destination address in each incoming IP packet with the private address of the destination host on the local site.

Network Address Port Translation (NAPT), sometimes called Port-Mapped NAT, is a popular variant of NAT providing concurrency by translating TCP or UDP protocol port numbers as well as addresses.

The STM SatLink Terminal supports:

- Dynamic NAPT

- Static NAPT

- Static NAT.

To enable Network Address Translation (NAPT or static NAT) in the STM SatLink Terminal, use the CLI command

Example:

# ip nat enable

To show the status of the Network Address Port Translation in the STM SatLink Terminal, use the CLI command

Example

# ip nat show NAT:

---Network Address Port Translation (NAPT): Enabled

NAT Status

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

ip nat enable.

ip nat show:8

15.1.1 Configuration of Dynamic NAPT

Dynamic NAPT applies for all LAN initiated connections that are to be routed over the DVB satellite interface. The source address of the outgoing packets will be replaced by the Global Address that is defined in the NAPT Global Address Table. Port numbers will be mapped to new port numbers that are automatically generated by the STM SatLink Terminal.

Please note that the CLI command

though the

# ip nat show

# ip nat enable

applies both for static NAT and NAPT even

status output only mentions NAPT enabled.

Publication no. 101557, Rev. T, November 3th, 2006

Page 61

Page 62

If no user-defined Global Address is configured, the default IP address used for address translation when NAPT is enabled will be set identical to the STM SatLink Terminal’s own DVB (satellite) interface IP address.

The CLI command

# ip nat global add <gladdr>

can be used to replace the default global address (i.e. the DVB Satellite interface IP address) with a user-defined global address. Correspondingly, the user defined global address can be deleted using the CLI command

# ip nat global del

Though the CLI command # ip nat global add <gladdr> allows the user to define more than one global address, in practice, only the first address in the NAT Global Address table will be used.

Please note that translation of outbound TCP/UDP fragmented datagrams will fail with NAT enabled. The reason is that only the first fragment contains the TCP/UDP header that would be necessary to associate the packet to a session for translation purposes. Subsequent fragments do not contain TCP/UDP port information, but simply carry the same fragmentation identifier specified in the first fragment. Consequently the sessions will be corrupted. Whether NAT drops or forwards also an ICMP fragmented packets depends on a number of things, such as the order in which the NAT router receives the ICMP fragments and the state of the translation table at that time. Under certain conditions, NAT translates the ICMP fragments differently, making it impossible for the destination device to reassemble the packet.

To view the currently configured dynamic NAPT entries, type the CLI command:

# ip nat show.

Example:

# ip nat global add 10.10.1.10 # ip nat show NAT Configuration

----------------Network Address Port Translation (NAPT): Enabled

Global Address Table If IP Address dvb0 10.10.1.10

NAT Status

---------Total Sessions 0 Active Sessions 0 Failed Sessions 0 Packet Translations 0

15.1.2 Configuration of Static NAPT

Static NAPT is used to map incoming connections to different local hosts dependent on their TCP/UDP port number.

When using static NAPT, both the IP addresses and port numbers of the incoming packets will be substituted with the IP addresses and port numbers that are defined using the CLI command:

# ip nat napt add <gladdr> <glport> <locaddr> [<locport>]

Multiple global address/port combinations can be mapped to the same local address/port.

Publication no. 101557, Rev. T, November 3th, 2006

Page 62

Page 63

Static NAPT entries in the address translation table are removed by issuing the CLI command:

# ip nat napt del <gladdr> <glport>

To view the currently configured static NAPT entries, type the CLI command:

# ip nat show

Publication no. 101557, Rev. T, November 3th, 2006

Page 63

Page 64

Example:

# ip nat napt add 10.10.2.2 5000 192.168.0.12 3000 # ip nat show NAT Configuration

----------------Network Address Port Translation (NAPT): Enabled

Global Address Table If IP Address dvb0 10.10.1.10

Static NAPT Map If Global Address/Port Local Address/Port dvb0 10.10.2.2/5000 192.168.0.12/3000

NAT Status

---------Total Sessions 0 Active Sessions 0 Failed Sessions 0 Packet Translations 0

Publication no. 101557, Rev. T, November 3th, 2006

Page 64

Page 65

15.1.3 Configuration of Static NAT

Static NAT provides two-way access to servers behind NAT. The destination IP address of the incoming packet is replaced by the corresponding local address that is configured in the Static NAT Map Table. Likewise, when the host device sends a packet towards the satellite network, the source IP address of the outgoing IP packet is replaced by the global address configured in the Static NAT Map Table.

The Static NAT MAP Table is configured using the following CLI command:

ip nat static add <globaddr> <locaddr>

Entries in the Static NAT MAP Table are deleted using:

ip nat static del <globaddr> <locaddr>

To view entries in the NAT tables, use

ip nat show.

Example:

# ip nat static add 10.10.2.1 192.168.0.10 # ip nat show NAT Configuration

----------------Network Address Port Translation (NAPT): Enabled

Global Address Table If IP Address dvb0 10.10.1.10

Static NAT Map If Global Address Local Address dvb0 10.10.2.1 192.168.0.10

Static NAPT Map If Global Address/Port Local Address/Port dvb0 10.10.2.2/5000 192.168.0.12/3000

NAT Status

---------Total Sessions 0 Active Sessions 0 Failed Sessions 0 Packet Translations 0

Publication no. 101557, Rev. T, November 3th, 2006

Page 65

Page 66

15.2 Generic Routing Encapsulation (GRE) and IP Tunnelling

The STM SatLink Terminal supports configuration of one IP tunnel from its DVB interface with Generic Routing Encapsulation (GRE) as specified in RFC 2784. Only the tunnel termination interface IP address, tunnel logical destination IP address and subnet mask need to be specified since the tunnel will always be set up from the DVB interface.

Example:

#ip gre add 192.168.1.0 255.255.255.0 10.20.1.1

Will set up a tunnel on the DVB interface to the IP address 10.20.1.1 for the subnet

192.168.1.0/255.255.255.0.

To verify that a GRE tunnel and a GRE interface have been created, use the CLI command

show.

Example:

# ip gre show

GRE Tunnel Interfaces:

---------------------If Tunnel Local Address Tunnel Remote Address 4 192.168.255.2 10.20.1.1

Interface number 4 has been allocated for the GRE interface. Use the CLI command that a new IP interface has been created and that 2 new entries have been added to the IP routing table. The first entry in order to route traffic with destination address equal to the tunnel remote address to the DVB interface. The second entry to route traffic with destination address belonging to the tunnel remote local subnet to the GRE interface.

# ip show Interfaces If IPAddress SubnetMask BroadCastAddr MTU Alias AdminStatus 1 10.10.20.115 255.255.255.248 10.10.20.119 1500 eth0 1 2 N/A N/A N/A 4074 air0 1 3 192.168.255.2 255.255.255.0 192.168.255.255 4074 dvb0 1 4 N/A N/A 255.255.255.255 4074 gre0 1 Interface Statistics

------------- Input ----------------- ------------- Output ---------------If UCast NUCast Disc Octets UCast NUCast Disc Octets 1 14 98 43 13737 18 29 0 4984 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 Routing Table DestMask RouteMask NextHop If

0.0.0.0 0.0.0.0 0.0.0.0 3

10.10.20.112 255.255.255.248 0.0.0.0 1

10.20.1.1 255.255.255.255 0.0.0.0 3

192.168.1.0 255.255.255.0 0.0.0.0 4

192.168.255.0 255.255.255.0 0.0.0.0 3

ip gre

ip show

to verify

Publication no. 101557, Rev. T, November 3th, 2006

Page 66

Page 67

To route unicast/multicast addresses specifically to the GRE interface, use the CLI command

addroute

Example

# ip addroute 225.0.0.2 255.255.255.255 4

will forward multicast datagrams with IP address 225.0.0.2 from the STM SatLink Terminal LAN interface to the GRE interface .

Forwarding of multicast IP traffic from DVB interface to GRE interface is not supported in the current release

As shown by the CLI command

# ip show -mcast IP Multicast Routing Table RouteAddress AddressMask IfIndex

225.0.0.2 255.255.255.255 4

239.255.255.250 255.255.255.255 1

ip show -mcast

15.3 TCP Performance Enhancing Proxy (PEP)

Conditions particular to satellite communication severely constrict the performance of TCP and reduce the end users experience of accessing the Internet over satellite. Large latency, elevated bit error rates, and asymmetric bandwidth are all characteristics of satellite networks that result in degraded TCP performance. Various TCP Performance Enhancing techniques are used to improve the performance of the TCP protocol over satellite links. The TCP PEP implementation in the SatLink System makes use of a TCP Performance Enhancing Server installed in the STM SatLink Gateway and a PEP software client embedded in the STM SatLink Terminal.

The STM SatLink Terminal embedded PEP client is an optional feature, which is enabled by entering a license key. Use of the terminal’s embedded PEP client is subject to the Network Operator/ISP supporting the PEP functionality using a PEP server on the gateway side. It is possible for the Network Operator/ISP to activate the embedded client software remotely from the gateway, thus requiring no end-user intervention. Alternatively, an end-user can receive a license key from the Network Operator/ISP and activate the functionality using the CLI command

Example:

# sw license pep mykeyforenablingpep

The PEP server in the Gateway may be installed in two different modes.

1. Re-direct mode

2. Transparent mode Re-direct mode is the default setting. The Network Operator/ISP should inform you if the gateway PEP server is installed in transparent instead of re-direct mode.

When operating in re-direct mode, the IP address of the TCP PEP Server in the gateway must be configured in the STM SatLink Terminal. If the terminal is authorised to use PEP, this is normally performed remotely by the SatLink Gateway when the terminal logs on to the network. Alternatively, the terminal user can locally configure the server address by means of the CLI command

using the PEP Server IP address provided by the Network Operator/ISP.

sw license

as shown in the example below.

ip pep server

Publication no. 101557, Rev. T, November 3th, 2006

Page 67

Page 68

To enable the PEP functionality, use the CLI command can assume the values

ip pep show.

redirect

trans

. To verify that the PEP functionality has been enabled, type

ip pep enable [<mode>]

, where <mode>

The CLI command sequence to configure and enable the PEP functionality is recapitulated below:

Example:

# sw license pep mykeyforenablingpep # ip pep server 10.0.0.10 # ip pep enable redirect

# ip pep show PEP Status : enabled PEP TCP Mode : Redirect Mode PEP TCP Server Address : 137.133.81.40 Maximum Connections : 512 Current Connections : 178 Total Connections : 584928 Transp Connections : 0 Failed Connections : 0 Received Segments : 29411430 Out of sequence Segments : 12338 Duplicate Segments : 5843 Transmitted Segments : 25883165 Retransmitted Segments : 10849

(to verify that the functionality is enabled)

The CLI command ip pep show displays current PEP configuration in addition to PEP status information. Table 11 provides a short description of the displayed parameters.

Parameters Description PEP status Indicates whether the PEP functionality in the terminal is enabled or disabled. PEP Mode Indicates whether the terminal is configured in Redirect or Transparent Mode PEP ServerAddress Shows that IP address of the Gateway PEP Server that the terminal PEP client

is configured to interact with.

Maximum Connections Shows the maximum number of TCP connections that the terminal PEP client

can handle simultaneously.

Current Connections Indicates the number of TCP connections that is handled by the terminal PEP

client at the moment.

Total Connections Indicates the total number of TCP connections that has been handled by the

PEP client since the PEP functionality was enabled.

Trans Connections Once the number of connections exceeds the threshold Maximum Connections

(i.e. 250 connections), the additional new connections are established without performance enhancement techniques being applied to these. The parameter Trans Connections indicates the number of connections that are passed “transparently” through the terminal without PEP due to the Maximum Connection threshold being exceeded.

Failed Connections Indicates the number of connections that were attempted established, but did

not succeed.

Table 11 Parameters displayed when typing ip pep show

Publication no. 101557, Rev. T, November 3th, 2006

Page 68

Page 69

15.4 4 QoS Classes

The Quality of Service functionality of the STM SatLink terminal is described in detail section 8. The Best Effort PHB and Real Time Voice over IP (RT-VoIP) PHB group are available on all STM SatLink Terminal models (provided the DVB-RCS Gateway the terminal is connected to supports these PHBs).

The Critical Data PHB and Real Time Video Conferencing PHB group are available as standard only on the STM SatLink 1910 and requires the QoS4 SW license key to be configured on the STM SatLink 1000, 1900, and 1901 models. The table below shows which QoS Groups on which Terminal models that require the QoS4 SW license key to be configured.

QoS Group Name PHB

SatLink

1000 0 Best Effort BE - - - 1 VoIP Audio RT-VoIP - - - 2 VoIP Signalling RT-VoIP - - - 3 ViC Video RT-ViC QoS4 QoS4 QoS4 4 ViC Audio RT-ViC QoS4 QoS4 QoS4 5 ViC Signalling RT-ViC QoS4 QoS4 QoS4 6 Critical Data CD QoS4 QoS4 QoS4 -

SW License key required QoS Group

SatLink

1900

SatLink

1901

SatLink

1910

Publication no. 101557, Rev. T, November 3th, 2006

Page 69

Page 70

15.5 Return link access control (RAC)

The multi-field classifier of the STM SatLink Terminal can also be used to block undesired traffic from being forwarded onto the return link. By mapping the return link traffic to the QoS group having index -1, the STM SatLink Terminal can drop traffic destined to the return link based on the following parameters in the IP header:

• IP source address

• IP destination address

• DSCP / TOS

• Protocol type

• TCP/UDP source port number

• TCP/UDP destination port number

Use the CLI command QoS Classification table. See section 8.1 for information of how this command is used for classifying return link traffic into different QoS classes. The command has a variable length where one ore more tags with different tag parameters can be set. The tags are the different IP header parameters that can be used by the multi-field classifier to identify traffic that shall be blocked.

tag and tags parameters for CLI command Function

+src <ipaddr> <mask>

-src +dst <ipaddr> <mask>

-dst +dscp <min> <max>

-dscp +prot <n> <p1> … <pn>

-prot +sport <min> <max>

-sport +dport <min> <max>

-dport

Examples: Deny one IP address to access the return link:

# ip qos mask 10 -1 +src 10.10.10.10 255.255.255.255

To block transmission to a certain TCP/UDP port range

# ip qos mask 11 -1 +dport 2000 3000

To delete the whole entry from the QoS classification table:

# ip qos mask 10 –all

To view the current QoS configuration:

ip qos mask <index> -1 <list of tags>

Define or modify IP source address and netmask Delete IP source address and netmask Define or modify IP destination address and netmask Delete IP destination address and netmask Define or modify DSCP range delete DSCP range Define protocol value [0,255]. Up to 3 protocol values can be defined (n can be 1, 2, or 3). Delete protocol values Define TCP/UDP source port number range Delete TCP/UDP source port number range Define TCP/UDP destination port number range Delete TCP/UDP destination port number range

to add RAC entries into the

Publication no. 101557, Rev. T, November 3th, 2006

Page 70

Page 71

11 -1 Dst port = 2000..3000 #

Publication no. 101557, Rev. T, November 3th, 2006

Page 71

Page 72

16. Definitions, Acronyms and Abbreviations

BE Best Effort BER Bit Error Rate BUC Block Up-Converter CD Critical Data CLI Command Line Interface CRA Continuous Rate Assignment CSC Common Signalling Channel CW Continuous Wave DiSEqC Digital Satellite Equipment Control DNS Domain Name Service DVB Digital Video Broadcasting DHCP Dynamic Host Configuration Protocol DSCP DiffServ Code Point EIRP Equivalent Isotropic Radiated Power FCA Free Capacity Assignment GW GateWay GRE Generic Routing Encapsulation HW HardWare ID IDentifier IDU InDoor Unit IETF Internet Engineering Task Force IF Intermediate Frequency IP Internet Protocol ICMP Internet Control Message Protocol GPS Global Positioning System LAN Local Area Network LED Light Emitting Diode LNB Low Noise Block MAC Medium Access Control MIB Management Information Base NAT Network Address Translation NAPT Network Address Port Translation NCC Network Control Centre ODU OutDoor Unit OMT Ortho-Mode Transducer OS Operating System PAT Program Association Table PEP Performance Enhancement Proxy PHB Per Hop Behaviour PID Packet Identifier QoS Quality of Service RAC Return link Access Control RBDC Rate Based Dynamic Capacity RCS Return Channel on Satellite RCST RCS Terminal RF Radio Frequency RFC Request For Comments RMT RCS Map Table RRM Radio Resource Management RT Real Time

Publication no. 101557, Rev. T, November 3th, 2006

Page 72

Page 73

RT-ViC Real Time Video Conferencing RT-VoIP Real Time Voice over IP

RX Receiver QEF Quasi-Error-Free SNMP Simple Network Management Protocol SNR Signal-to-Noise Ratio SW SoftWare TCP Transport Control Protocol TDT Time and Date Table TFTP Trivial File Transfer Protocol TOS Type Of Service TS Transport Stream TX Transmitter UDP User Datagram Protocol VBDC Volume-Based Dynamic Capacity XPD Cross-Polar Discrimination

17. References

[1] STM SatLink 4033/4035. 2W/3W Ku-band Transceivers. Installation Instruction, STM

document No. 105894.

[2] Andrew Assembly Instruction,. Type 960 Class I & II .96m Rx-Tx Antenna System.

Type 123 Class I & II 1.2m LFL Antenna System. Factory Assembled AZ/EL Cap Mount, STM document No. 101497.

[3] Channel Master Instruction and Assembly manual, Type 184 1.8m Offset Tx/Rx Antenna System,

STM document No. 104218.

[4] Assembly User’s Manual and Operating Instructions for 75 / 90 EMIT Transmit / Receive Antenna,

STM document No. 105647.

[5] User’s Assembly Manual and Operating Instructions for 120 cm Transmit / Receive Antenna,

Standard or EMIT, STM document No. 107837.

[6] STM SatLink Terminal. Management via SNMP, STM document No. 103951. [7] SatLabs Group website at www.satlabs.org [8] Digital Video Broadcasting website at www.dvb.org [9] European Telecommunications Standards Institute website at www.etsi.org [10] Digital Video Broadcasting (DVB); Interaction channel for satellite distribution systems,

ETSI EN 301 790, V1.3.1

Publication no. 101557, Rev. T, November 3th, 2006

Page 73

Page 74

Appendix A. Using the Web Interface

The Web interface supports managing the most common configuration parameters and viewing the status of the STM SatLink Terminal. The Web-browsers currently supported are Microsoft Internet Explorer

6.0, but other browsers like e.g. Opera 8.x normally works fine as well. The functions available via the Web-interface are:

• Viewing status information for the satellite interface

• Viewing traffic statistics

• Viewing device information

• Viewing status of the DHCP server

• Configuring the most common satellite interface parameters

• Configuring the most common IP parameters

• Return link line-up procedure

Advanced functions such as adding SW licenses, configuring GRE tunnels, downloading software updates manually, configuring automatic software updates, configuring system information, adding users and changing password, configuring SNMP access, and adding manual IP routes are only available from the CLI via Telnet or the RS-232 port. If experiencing any problems using the Web interface for management of the STM SatLink Terminal, please use the CLI via Telnet or RS-232 as a work-around for the problem. The NAT status and configuration web pages are only available if this SW option is authorised by installing the necessary license key for the NAT functionality.

To manage the SatLink terminal via the Web interface, start the web browser and type in the IP address of the STM SatLink Terminal in the address field as shown in Figure 14 below. Use the STM SatLink Terminal’s Satellite Interface (DVB) IP address when connecting to the terminal over the satellite link (from the Gateway), and the STM SatLink Terminal’s LAN (Ethernet) IP address when connecting to the terminal from the local LAN. Then enter the username and password to logon to the terminal.

Figure 14: Connecting to the web-interface

Publication no. 101557, Rev. T, November 3th, 2006

Page 74

Page 75

Appendix B. 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 STM SatLink Terminal 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 STM SatLink Terminal’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 good freeware terminal emulator is Tera Term Pro Web 3.1.3. The software can be downloaded from Ayera home page:

http://www.ayera.com/teraterm.

B.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 Terminal 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.

B.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 shots are from Windows XP Professional; other versions of Windows may display differently.

Figure 15: Hyper Terminal New Connection dialogue box

Publication no. 101557, Rev. T, November 3th, 2006

Page 75

Page 76

Enter a name and select an icon for the Connection, and click OK. The Connect To dialogue box, shown in Figure 16, will appear.

Figure 16: Hyper Terminal Connect To dialogue box

Select the COM port where the serial cable attached to the STM SatLink Terminal is connected, and click OK. The COM port Properties sheet will appear, as shown in Figure 17.

Figure 17: Hyper Terminal COM1 Properties sheet

Publication no. 101557, Rev. T, November 3th, 2006

Page 76

Page 77

Use the pull-down lists to enter:

• Bits per second: 38400

• 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.

Publication no. 101557, Rev. T, November 3th, 2006

Page 77

Page 78

Appendix C. TFTP server

TFTPD32 is a freeware TFTP server for Windows 9x/NT/XP PCs (but seems to work on Windows 2000 as well), which is small, and easy to install and use. Use the copy on the CD included with the SatLink Terminal, or use the link below and download the software.

http://tftpd32.jounin.net/

Short installation description:

1. Copy the TFTP server files to a PC located at either the gateway or a local LAN

2. Start the program tftpd32.exe

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. You are up and running with a TFTP server

6. The TFTP server can now be accessed from the STM SatLink Terminal by using the CLI

commands

TFTP upload from and download to the STM SatLink Terminal have been tested with version 2.51 of this TFTP server, but any TFTP server should work. It is however essential that the TFTP server has support for negotiation of block lengths up to 8 Kbytes in order to obtain satisfactory performance over the satellite link, in terms of acceptable download time.

The STM SatLink Terminal can access a TFTP server on both the satellite and the Ethernet interface.

upload

and

dload

Publication no. 101557, Rev. T, November 3th, 2006

Page 78

Page 79

Appendix D. Telnet Client

A good freeware Telnet client is Tera Term Pro Web 3.1.3. The software can be downloaded from Ayera home page: http://www.ayera.com/teraterm. 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 18: Tera Term Terminal Setup

When starting Tera Term, please chose the menu Setup and then Terminal. Please enable Local echo as shown in Figure 18. Then chose the menu Setup and then Save Setup to save this configuration.

Tera Term may as well be used as a replacement for HyperTerminal.

Publication no. 101557, Rev. T, November 3th, 2006

Page 79

Page 80

Appendix E. Management via SNMP

Management of the STM SatLink Terminal is supported via SNMP. For further information of SNMP management and the MIBs available, please refer to [6] and/or contact the system operator.

Publication no. 101557, Rev. T, November 3th, 2006

Page 80

Page 81

Appendix F. Changing pre-configured parameters

F.1 IP routes

To add an IP route use the CLI command

ip addroute <destaddr> <netmask> <next hop> <ifnum>

destaddr IP address of destination network or host netmask Netmask for destination network next hop IP address of the next router/host in the path to the destination network/host ifnum interface number on which route is to be added (1=LAN, 3=Satellite)

Example:

ip addroute 0.0.0.0 0.0.0.0 10.10.21.254 3

will set the default route to the satellite interface with next hop IP address 10.10.21.254.

The specified next hop IP address cannot be the same as the one attributed to the terminal’s DVB interface.

Use the CLI command

ip show

to verify the setting and the CLI command

save config

to store

the setting in the flash.

IP routes can be deleted with the

ip delroute <destaddr> <netmask> <next hop>

command.

F.2 Default CW frequency

The transmission of a pure tone (CW) is supported for aiding the antenna fine adjustment as well as for power calibration. A default frequency for CW transmission is stored in the STM SatLink Terminal configuration. This default frequency may be changed with the CLI command where

freq

is the return link frequency [kHz].

dvb tx cwfreq <freq>

Example:

dvb tx cwfreq 14123000

sets the CW frequency to 14.123 GHz.

Verify the new setting with the CLI command command

save config

dvb tx show

, save the configuration with the CLI

Publication no. 101557, Rev. T, November 3th, 2006

Page 81

Page 82

Antenna

Appendix G. ODU installation

The ODU comprises the antenna with feed-horn and mounting structure, and a transceiver that contains the LNB integrated with OMT, Tx-reject filter, and the transmitter (BUC). If the STM SatLink 4033/4035 transceiver is not used, the OMT, LNB and BUC may be supplied as two or three separate units. Two cables with F-connectors, one for Tx and one for Rx are connecting the ODU to the IDU.

Antenna Feed Horn

Transceiver mounted directly on antenna feed

Reflector

Figure 19: STM SatLink 4033/4035 Configuration

G.1 Assembly of SatLink 403x transceiver to feedhorn

The STM SatLink 403x is supplied with 6 pcs of UNC 6/32 for connection to the antenna flange. The parts are shown in the picture below. Please refer to Appendix I for information of how to connect the STM SatLink 403x to antenna feed horn interfaces with 6 or 8 M4 screws.

Figure 20: SatLink 4033/4035 and screws for mounting feed horn

Publication no. 101557, Rev. T, November 3th, 2006

Page 82

Page 83

When mounting the transceiver to the antenna horn, place the feed horn on a level surface and insert the O-ring supplied with the antenna feed horn into the groove as shown below:

Figure 21: Inserting O-ring into feed horn groove

Place the transceiver on to the feed horn and insert one of the UNC screws for alignment. Tighten the screw loosely by hand or with an Allen key. Make sure that the rubber gasket is not removed from the groove when doing this.

Figure 22: Mounting feed horn

Insert the remaining screws and tighten firmly with an Allen key. Always use screws from mounting kit supplied with the STM SatLink 4033/4035 (part no. 105773). Do not use other screws or apply washers!

Publication no. 101557, Rev. T, November 3th, 2006

Page 83

Page 84

Figure 23: Tightening with Allen key

Rx connector

Tx connector

Figure 24: Connecting cables from IDU

The IF connectors are placed in the chassis of the SatLink 403x. A protrusion on the case indicates ‘Rx’ and ‘Tx’ so that they are easily distinguishable. Cable connectors should be tightened firmly, but use of excessive force may damage the F-connectors on the transceiver.

Publication no. 101557, Rev. T, November 3th, 2006

Page 84

Page 85

G.2 Assembly and installation of the antenna

Different mounting structures for antennas are shown below. From the left-hand side, we have an Lshaped wall-mount, a three-leg mount and a standard straight mount. The tube diameter is 76 mm. For a correct mounting the surface must be vertical or horizontal, respectively.

Non-penetrating roof-mounting structures (requiring no screws or bolts) may also be used if the customer do not want to penetrate the roof. The foot can be rectangular, “H-shaped” or have another suitable form. It must be loaded with at least 75 kg depending on the antenna size and maximum wind force.

Install the antenna and adjust pointing and polarisation as described in the manufacturer’s installation instruction [2][3][4][5]. After connecting the cables from the IDU to the transceiver (or BUC/LNB/OMT) and completing the installation of the antenna with feed horn and transceiver (or BUC/LNB/OMT) proceed with fine adjustment of antenna pointing and polarisation assisted by the IDU as described in section 6.3.

Finally, the F-connectors must be protected against rain and humidity. Use a self-vulcanising tape suitable for out-door use. The cables must also be properly marked and should be strapped to the antenna feed mount.

Publication no. 101557, Rev. T, November 3th, 2006

Page 85

Page 86

Figure 25: Complete assembled ODU with cables strapped to antenna feed mount

G.2.1 Cables

STM recommends cables from Times Fiber. For cable lengths up to 62 m, Times Fiber series 6 (diameter

6.93 mm) can be used. For lengths up to 82 m, use series 11 (diameter 10.2 mm) and for longer lengths, use series 500 (diameter 14.2 mm).

Important: Do not use amplifiers or attenuators on the Tx-cable.

Use type “F” connectors for the cables.

The cable pulling from the ODU to the IDU must be performed according to the customer. Sharp bends on the cables must be avoided (see figure below).

Publication no. 101557, Rev. T, November 3th, 2006

Page 86

Page 87

Figure 26: Avoid sharp bends on cables

Publication no. 101557, Rev. T, November 3th, 2006

Page 87

Page 88

Appendix H. Cable Specification

This appendix provides the cable specification for use between the ODU and the STM SatLink IDU. Two separate cables are required, one cable for the transmit (Tx) signal and one cable for the receive (Rx) signal.

H.1 Cable Requirements

Frequency range: 950-1450 MHz, Tx 950-2150 MHz, Rx

Maximum attenuation: 25 dB, Tx 9 dB + 10logR dB, Rx

R: Minimum symbol-rate (Msps)

Maximum DC resistance: 2.5 Ω (Tx)

Screening effectiveness: >60 dB at 1000 MHz

Impedance: 75 Ohm

Connectors: F-type

Environmental requirements:

Temperature: -50°C to 80°C Humidity: 0 to 100% (Condensing) Atmosphere: Salt, Pollutants and Contaminants as Encountered in Coastal and

Industrial Areas

H.2 Recommended cable types

We recommend using cables from Times Fiber.

Type Outside

diameter (mm)

6-series 6.93 21.46 110 40 11-series 10.2 13.88 75 30.4 500-series 14.2 8.30 100 5.61

Table 12: Cables from Times Fiber

For the Rx-cable, amplifiers (or attenuators) may be used. No amplifiers or attenuators must be used on the Tx-cables.

Recommended connectors:

Moisture proof crimp connectors from Cablecon suitable for the 6-series and the 11-series of cables.

Attenuation at 1000 MHz (dB/100m)

Publication no. 101557, Rev. T, November 3th, 2006

Screening at 1000 MHz (dB)

DC-resistance (Ω/km)

Page 88

Page 89

Maximum cable lengths:

The maximum cable lengths for the Times Fiber cables are given in Table 13 and Table 14. The cable loss at 1450 MHz or the DC- resistance decides the range at Tx. At Rx, the range is decided by the cable loss at 2150 MHz together with the minimum symbol-rate.

Cable Range (m) from DC-resistance Range (m) from attenuation 6-series (6.93mm) 62 92 11-series (10.2mm) 82 142 500-series (14.2mm) 445 238

Table 13: Tx range

Range (m) with minimum symbol-rates: Cable 20 Msps 8 Msps 4 Msps 2 Msps 1 Msps

6-series

64 53 44 35 26 (6.93mm) 11-series

97 80 66 53 40 (10.2mm) 500-series

163 133 111 88 66 (14.2mm)

Table 14: Rx range

Publication no. 101557, Rev. T, November 3th, 2006

Page 89

Page 90

Appendix I. STM SatLink 403x. Interfacing VSAT RX/TX

antennas

The STM SatLink 403x series of Ku-band transceivers is configured with internal OMT as shown in Figure 27 below. The output interface of the transceiver (C120) is therefore connected directly to the feed horn of the antenna.

Figure 27: STM SatLink 403x output interface (Option A)

Antenna vendors offer different variants of the feed horn for their Ku-band RX/TX antennas. The different options are listed below.

Option Feed Horn Interface

A C120 – 6 UNC screws

B C120 – 6 or 8 M4 screws

Option A interfaces the STM SatLink 403x directly while Option B requires an adaptor in order to fit the STM SatLink 403x output interface. The hole patterns for option A and B are shown in Figure 28 and Figure 29.

Figure 28: Option A antenna feed hole pattern. Holes are distributed equally at 60 degrees apart. STM SatLink 403x fits directly to this pattern using 6 UNC screws for fastening.

Figure 29: Option B antenna feed hole pattern. Holes are equally distributed at 45 degrees apart. Some versions have only 6 holes. STM SatLink 403x fits on this pattern by means of adapter STM SatLink 4901 (STM P/N 107268).

Publication no. 101557, Rev. T, November 3th, 2006

Page 90

Page 91

An overview of different antennas that can be used with the STM SatLink 403x is given in the table below. The table shows which feed horn hole pattern (option A or B) the antenna is configured with, and whether an adapter is required for mounting the STM SatLink 403x to the antenna feed horn. The adapter, having model no. STM SatLink 4901, having STM P/N 107268, can be order from STM.

Manufacturer

Andrew Type 960 Class I Single offset A 0.96 m 107482 62-96051-02 No x x x Andrew Type 960 Class I Single offset B 0.96 m - 62-96052-11 STM SatLink 4901 x x x Andrew Type 960 Class II Single offset A 0.96 m 100883 62-96055-02 No x x x Andrew Type 960 Class II Single offset B 0.96 m - 62-96056-01 STM SatLink 4901 x x x Andrew Type 123 Class I Single offset A 1.20 m 107483 62-12351-02 No x x x Andrew Type 123 Class I Single offset B 1.20 m - 62-12356-11 STM SatLink 4901 x x x Andrew Type 123 Class II Single offset A 1.20 m 100882 62-12355-02 No x x x Andrew Type 123 Class II Single offset B 1.20 m - 62-12362-01 STM SatLink 4901 x x x Andrew Type 184 Dual Optics B 1.80 m 104216 62-18452-02 STM SatLink 4901 x Andrew Type 184 Class III Single offset Andrew Type 244 Dual Optics B 2.40 m 104612 62-24452-02 STM SatLink 4901 x Andrew Type 244 Class III Single offset Visiosat KIT 90 EMIT Single offset A 0.90 m 105645 0141088 No x Visiosat KIT 120 EMIT Single offset A 1.20 m 107077 0141143 No x

Antenna Model Description Feed horn

interface

option

B 1.80 m - 62-18356-01C STM SatLink 4901 x x

B 2.40 m - 62-24356-01C STM SatLink 4901 x x

Ant.

Size

STM P/N Manu-

facturer’s P/N

Adapter required

Antenna approvals

Eutel-

Intel-

sat

Ana

sat

-tel

Table 15 STM supported Ku-band antennas and feed interfaces.

Antennas with feed horn interface option B are often delivered with an OMT mounted on the feed horn. The OMT is not needed when using the STM SatLink 403x. Remove the OMT and insert adapter STM SatLink 4901 (STM P/N 107268) as described in Appendix I.1.

Publication no. 101557, Rev. T, November 3th, 2006

Page 91

Page 92

I.1 Mounting the feed horn interface adapter on the STM SatLink 403x

Antenna feeds with the option B hole patterns will require use of adapter kit STM SatLink 4901 (STM P/N 107268) for interfacing the STM SatLink 403x. Use the following procedure:

1) Insert the rubber gaskets supplied with the adapter on both sides of the adapter.

2) Use the 4 UNC screws to fasten the adapter to the STM SatLink 403x flange as shown in Figure 30.

3) Fasten the STM SatLink 403x to the antenna feed horn as shown in Figure 31.

Figure 30: Mounting of adapter STM SatLink 4901 (STM P/N 107268) on STM SatLink 403x. Remember to fit rubber gasket on both sides of the adapter to prevent moisture intrusion.

Figure 31: Mount the antenna feed to the adapter and fasten using M4 screws.

Fasten the adapter using 4 UNC screws supplied with the STM SatLink 403x. Hand tighten with Allen key.

I.2 Upgrading existing VSAT installations

When upgrading an existing VSAT site from a configuration with an antenna listed in Table 15 to a DVB-RCS site configured with the STM SatLink 403x transceiver, the antenna will normally be configured with a feed horn with the option B hole pattern (Figure 29) and an OMT. In order to fit the STM SatLink 403x to the antenna from the VSAT installation, do the following:

1. Remove the OMT. This part is not used when installing the STM SatLink 403x transceiver.

2. Use the adaptor STM SatLink 4901 (STM P/N 107268) to interface the STM SatLink 403x to a feed

horn with interface C120 / 4 screws as shown in Figure 30 and Figure 31,

Publication no. 101557, Rev. T, November 3th, 2006

Page 92

Page 93

Alternatively, feed horns (Andrew P/N 61-00233-01) with interface option A for Andrew 96 cm and

1.2 m antennas can be ordered separately.

Publication no. 101557, Rev. T, November 3th, 2006

Page 93

Page 94

Appendix J. IDU output power calibration with other BUCs

than SatLink 3000 and 403x

STM SatLink Terminal can be used together with the Norsat 1010/1020XRT, Invacom TUL-204, JRC NJT5017F as well as various C-band BUCs. These BUCs do not support DiSEqC communication and do not have a power detector to measure the actual output power from the HPA. A more complicated procedure to calibrate the Tx output power must then be run as described below.

J.1 Calibrating the IDU output power

This section describes how to calibrate the Tx output power when using one of the following ODU transmitters:

• Invacom TUL-204

• Norsat 1010/1020XRT

• JRC NJT5017F

• C-band BUCs

Please refer to section 6.3.2 for the description of the calibration procedure for the STM SatLink 3000 and SatLink 403x.

Ensure that the STM SatLink Terminal configuration procedure in section 6.2 has been performed. Ensure that the STM SatLink Terminal is configured to start the receiver (Rx) automatically, but not the transmitter (Tx). Enter the CLI command Enter the CLI command

Enter the CLI command

start

is set to

Disabled

Enter the CLI command

Ensure that the Tx and Rx cables from the STM SatLink Terminal to the ODU are connected. Restart the SatLink Terminal (issue the CLI command the STM SatLink Terminal has locked to the received carrier. The receiver has successfully acquired the forward link when the message Logon as the install user (user = install, factory default password = dvbrcs)

Call the control centre and have contact by phone for the following measurements. Set up a continuous wave (CW) with the following command:

dvb tx cw on <pow> <freq>

where

pow

freq

dvb rx autostart on dvb tx autostart off

dvb rx show

dvb tx show

. Verify that the parameter

. Verify that the transmitter is

. If the transmitter is On, use the command

save config

Forward link up

to save this configuration.

to enable receiver automatic start.

to disable transmitter automatic start.

restart

Auto start

Off

dvb tx logoff

), wait till the application has loaded and

is set to

Enabled

and the parameter

Auto

is displayed (see section 6.3.1 for further details).

= Transmitted IF power level from IDU in dBm.

This is an integer in the range –30 to +10. (Start with pow= -30)

= transmitted radio frequency in kHz. The frequency is only required the first time

the CW is turned on. Subsequent adjustment of the power level can be done without entering the frequency.

Publication no. 101557, Rev. T, November 3th, 2006

Page 94

Page 95

Example:

dvb tx cw on -30 14100000

will transmit a CW from the ODU output at 14.1 GHz with an IDU output power of –30 dBm from the STM SatLink Terminal.

Please check immediately with the control centre if they can detect the transmitted CW. If they are not able to see the CW at the specified frequency and expected output power level, please power off the STM SatLink Terminal immediately

The operator control centre will instruct you to adjust your power in positive or negative steps. Never make power adjustments steps larger than 5 dB. Please update the transmitted power level using the above

dvb tx cw on

command until the desired power level is measured at the control centre.

When the operator confirms that the correct power level has been reached, then turn off the CW transmission with

dvb tx cw off

before storing this power level as the nominal IDU power level to be

used for transmission. Type the CLI command:

dvb tx outpow <tx output power>

where

“tx output power”

is the power level in dBm. Verify the setting by issuing the CLI

command

dvb tx show

and save the setting by issuing the CLI command

save config

In the following example a complete power correction routine is carried out. Example:

dvb tx cw on -30 14100000

The operator instructs you to increase power by 5 dB (i.e. pow = -30 + 5 = -25). You type:

dvb tx cw on -25

The operator instructs you to decrease power by 3 dB. (i.e. pow = -25 - 3 = -28). You type:

dvb tx cw on -28

The operator instructs you to increase power by 1 dB. (i.e. pow = -28 + 1 = -27). You type:

dvb tx cw on -27

The operator confirms that the correct power setting is obtained. Confirm the nominal power setting by storing this power level. To configure the nominal power level, turn off the CW transmission with:

dvb tx cw off

Publication no. 101557, Rev. T, November 3th, 2006

Page 95

Page 96

and type the CLI command:

dvb tx outpow –27

Verify the setting by issuing the CLI command

dvb tx show

and save the setting by issuing the CLI command

save config

Publication no. 101557, Rev. T, November 3th, 2006

Page 96

Page 97

Appendix K. The boot SW

The STM SatLink Terminal has two SW applications installed:

1) Boot

2) DVB-RCS 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 STM SatLink Terminal.

The Boot SW is always loaded after powering on the STM SatLink Terminal. But normally the user need not care about the boot SW since the DVB-RCS application is loaded by default.

The boot-loader can only be accessed via RS-232 as described in Appendix B. After power on, an output similar to this is displayed on the HyperTerminal:

STM SatLink Boot-loader

- SW ID 101225, Revision 8.0.0.0

File system initialised Press return to enter boot-loader

In order to logon and use the boot SW, press return (the software will wait 10 seconds before automatically loading the DVB-RCS application):

1. When

2. When

is displayed type the user name

Password

is displayed type

In the boot-loader a minimal CLI is available, supporting the file system commands and access to the LAN. Type ? (question mark) to display the available CLI commands.

dvbrcs

install

dvbrcs is the factory default password and might have been changed by the user

Publication no. 101557, Rev. T, November 3th, 2006

Page 97

Page 98

Appendix L. Troubleshooting

L.1 Q&A

Question Answer

1. Input from keyboard is not displayed on the

screen, but information from the terminal is visible

2. Terminal displays “Receiver tuning failed for

…. “

3. Terminal displays “Logging on- Logon

failed” Line up has been performed and levels calibrated with Control Centre.

4. How do I enable NAT and GRE in the

terminal?

5. How do I change the login password? Password can be changed with the command

6. I have changed the password, but have lost it A new password will have to be defined for the

7. How do I load new Software on my SatLink

terminal

8. I can not find the answer to my question in

the list above

Verify that the Local Echo is enabled in the Telnet Client. In Windows XP, the Local Echo is enabled by the following procedure: C:\ Telnet Microsoft Telnet> set localecho Local echo on Microsoft Telnet>

To connect to the SatLink terminal, type the command Microsoft Telnet> open <ip-address> The terminal is missing all or parts of the information in the signal transmitted from the DVB-RCS Gateway. Verify that the receiver status is “locked” using the command DVB RX SHOW. If the status is anything other than” locked”, verify the interface connections according to chapter 3.5 above. If the status is “locked”, please contact the System Operator to confirm that the equipment has been configured correct. Verify that the GPS configuration is correct.

If transmit level calibration has not been performed, power off the SatLink terminal and contact the DVB-RCS system operator. The NAT and GRE feature require license keys to be enabled. Contact the System Operator or ISP to obtain this license.

# user passwd <newpasswd>

To change the password on a different user, the command is: # user passwd <loginname> <oldpasswd> <newpasswd>

user. Contact the System Operator for assistance. See description in chapter 13 above.

Contact the System Operator or STM at satlink.support@stmi.com

Publication no. 101557, Rev. T, November 3th, 2006

Page 98

Page 99

L.2 Debugging network connections

Ping is a useful tool to debug network connections.

A ping test can be done from a PC connected to the Ethernet port of the STM SatLink Terminal (e.g. from Microsoft command prompt).

Use the following commands:

1. Ping the Ethernet interface IP address of the STM SatLink Terminal (e.g. 10.10.20.1). If not OK

please check the Ethernet cable and the connection to the SatLink terminal. For SatLink 1900 and 1901 only: Check that the terminal’s Ethernet port is operating in the correct mode. The switch should be set to HUB for direct PC to STM SatLink Terminal connections using a straight Ethernet cable.

2. If the Ethernet connection is OK then check the IP configuration and routing table of the PC (e.g.

type the MS-DOS commands ipconfig and route print) and check the IP configuration of the STM SatLink Terminal (use the CLI command

3. If the ping to the SatLink Terminal is successful, try to ping a known Internet address (e.g.

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

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

The following commands may also be useful:

• ping –t <ipaddr> start a continuous ping test towards the specified IP address in order to gather

statistics

• use ctrl-break to read statistics during test (This option is not supported by all Windows operating

systems)

• use ctrl-c to stop the test

ip show

L.3 Manual software upgrade or dload fails

Manual software upgrade or download of file using CLI command sufficient available memory in the STM SatLink terminal file system. This can happen if several software images have been downloaded to the terminal without deleting the older backup images.

The STM SatLink Terminal file directory normally contains two application files, namely:

• dvb-rcst.tgz10 The current DVB-RCS application

• xxx.bak The back-up DVB-RCS application

in addition to the smaller configuration and log files.

To view the STM SatLink Terminal file directory, type the CLI command than the above listed application files.

The name may differ, but the extension will be “tgz”.

Publication no. 101557, Rev. T, November 3th, 2006

dload

can fail if there is not

dir

. There should not be more

Page 99

Page 100

Example:

# dir Volume Label :DVB-RCST10 Directory Name : DVB-RCST FileName Size Date Time oldLog.txt 9816 00/00/0000 00:34:20 activeLog.txt 3192 00/00/0000 00:00:25 xxx.bak 1691265 00/00/0000 00:04:21 dvb-rcst.tgz 1690755 00/00/0000 00:24:28 config.txt 5188 00/00/0000 00:00:13

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.

L.4 Collecting information if a problem occurs

If a problem occurs with the DVB-RCS terminals for which support might be needed, having the information listed below available will be helpful.

1. The terminal log from the HyperTerminal Window.

If possible log the output from the terminal 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 ip show -mcast dvb tx show dvb tx show -capacity dvb rx show dvb rx show -pid dvb pos show odu show sw show log show dir

2. The terminal 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>]

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 Appendix C for an example of how to install and set up a TFTP server.

If it is not possible to upload the terminal configuration file to a TFTP server the config.txt file might be dumped to the RS-232 port / HyperTerminal by using the CLI command The output from the HyperTerminal Windows can then be copied to a text file or dumped using the capture text feature of the HyperTerminal.

, where

TFTP-Ipaddress

type config.txt

Publication no. 101557, Rev. T, November 3th, 2006

Page 100