Nevion TNS-544

TNS544
TSoIP Switch
User’s Manual
Revision: 2.6.B (5219)
2017-09-01
Valid for SW version 2.6.4 and newer
nevion.com
Contents
1 History 9
2 Introduction 11
2.1 Scope 11
2.2 Warnings, cautions and notes 11
2.3 Heed warnings 12
2.4 Contact information 12
3 Short Product Description 13
3.1 Summary of features 13

3.2 Options 14
3.2.1 Hardware options 14
3.2.2 Software options 15
4 Getting Started 17
4.1 Configure the management interface 17

4.2 Configure device name and time settings 18
4.3 Configure operation 18
4.3.1 Enabling IP inputs 18
4.3.2 Enabling the Switch 19
4.3.3 Enabling IP output 19
5 Installing the Equipment 21
5.1 Inspect the package content 21

5.2 Installation Environment 21
5.3 Equipment installation 22
5.4 Ventilation 22
5.5 Power supply 23
5.5.1 AC power supply 23
5.5.1.1 Dual AC power supplies 23
5.5.1.2 AC power cable 23
5.5.1.3 Protective Earth/technical Earth 24
5.5.1.4 Connecting to the AC power supply 24
5.5.2 DC power supply 25
5.5.2.1 Dual DC power supplies 25
5.5.2.2 DC power cable 25
5.5.3 Powering up/down 26
6 Functional Description 27
6.1 Input and output 28

6.1.1 Protocol mapping 29
6.2 Management subsystem 29
6.2.1 Graphical user interface 30
6.2.2 Configuration database 30
6.2.3 Alarm manager 31
6.3 Time synchronisation 31
6.4 The SFP module 32
7 Physical Description 33
7.1 ASI ports 33

7.1.1 ASI input ports 34
7.1.2 ASI output ports 34
7.2 1 PPS Input 34
7.3 Ethernet data ports 35
7.4 Ethernet management port 35
7.5 Power supply 36
7.6 Technical earth 36
7.6.1 Alarm/Reset connector 36
7.6.2 Serial USB interface 37
8 Operating the Equipment 39
8.1 Accessing the graphical user interface 39

8.2 Password protection 39
8.2.1 Resetting the password list 40
8.3 Changing the IP address of the unit 40
8.3.1 Changing IP address via the Web GUI 40
8.3.2 Changing the management port IP address via terminal interface 41
8.3.3 Configuring automatic IP address assignment 42
8.3.4 Detecting the management port IP address 43
8.3.4.1 USB Interface 43
8.3.4.2 Nevion Detect 43
9 WEB Interface 45
9.1 Login 45
9.2 Status header 46
9.3 Status 47
9.3.1 Current Status 47
9.3.2 Alarm log 49
9.4 Device Info 51
9.4.1 Product info 51
9.4.2 Alarms 53
9.4.2.1 Device alarms 54
9.4.2.2 Global configuration 55
9.4.2.3 Relays and LED 55
9.4.2.4 Alarm log settings 58
9.4.3 Time Settings 58
9.4.3.1 Daylight saving time 61
9.4.4 Network 62
9.4.4.1 Interfaces 63
9.4.4.1.1 Main 63
9.4.4.1.2 Interface Settings 64
9.4.4.1.3 DHCP Settings 64
9.4.4.1.4 DHCP Status 65
9.4.4.1.5 Manual IP Settings 66
9.4.4.1.6 Interface Status 66
9.4.4.1.7 Detect Settings 67
9.4.4.1.8 Alarms 67
9.4.4.1.9 Advanced 67
9.4.4.1.10 Status 68
9.4.4.1.11 VLAN 70
9.4.4.1.12 Main Settings 70
9.4.4.1.13 Manual IP Settings 71
9.4.4.1.14 Advanced Settings 71
9.4.4.1.15 DHCP settings and status 71
9.4.4.1.16 SFP 71
9.4.4.2 DNS Settings 80
9.4.4.3 IP Routing 80
9.4.4.4 TXP Settings 81
9.4.4.5 SNMP Settings 82
9.4.4.6 Tools 83
9.4.4.6.1 Ping 83
9.4.4.6.2 Traceroute 85
9.4.5 Clock Regulator 86
9.4.5.1 Main 86
9.4.5.2 Alarms 87
9.4.6 Configuration Manager 88
9.4.6.1 Save/Load Configs 88
9.4.6.1.1 Save Configuration To File 88
9.4.6.1.2 Load Configuration From file 89
9.4.6.1.3 Load Configuration from Remote Device 89
9.4.6.1.4 Load options 90
9.4.6.2 Boot Log 91
9.4.6.3 Stored Configurations 91
9.4.7 Maintenance 92
9.4.7.1 General 92
9.4.7.2 Software Upgrade 94
9.4.7.3 Feature Upgrade 96
9.4.8 Users 96
9.4.9 GUI Preferences 97
9.5 Inputs 98
9.5.1 Inputs Overview 99
9.5.1.1 IP Inputs 100
9.5.1.2 Copy Inputs 102
9.5.2 TS (Transport Stream) Inputs 102
9.5.2.1 ASI Input Sections 103
9.5.2.2 Alarms 106
9.5.2.3 IP 110
9.5.2.3.1 FEC 112
9.5.2.3.2 Ping 114
9.5.2.3.3 Regulator 115
9.5.2.4 Copy 117
9.5.2.5 Services 118
9.5.2.5.1 Service List 118
9.5.2.6 PIDs 122
9.5.2.6.1 PIDs Grid 122
9.5.2.6.2 PID rates 124
9.5.2.7 Tables 125
9.5.2.7.1 Tables 126
9.5.2.7.2 Sources 127
9.5.2.7.3 Settings 128
9.5.3 Switch 129
9.5.3.1 Main 130
9.5.3.2 Inputs 134
9.5.3.3 Alarms 136
9.6 Outputs 136
9.6.1 Outputs overview 136
9.6.2 (Switch) Output 137
9.6.2.1 Switch Main 137
9.6.2.2 Alarms 139
9.6.3 Output to IP destination 139
9.6.3.1 Main 140
9.6.3.2 FEC 143
9.6.3.3 Ping 145
9.6.3.4 RIP-2 146
10 SNMP 149
10.1 SNMP agent characteristics 149

10.2 MIB naming conventions 149
10.3 MIB overview 149
10.3.1 Supported standard MIBs 149
10.3.2 Custom MIBs 149
10.4 SNMP related configuration settings 151
10.4.1 Community strings 151
10.4.2 Trap destination table 151
10.4.3 Trap configuration 151
10.5 Alarm/status related SNMP TRAPs 152
10.5.1 The main trap messages 152
10.5.2 Severity indications 152
10.5.3 Alarm event fields 153
10.5.4 Matching of on/off traps 154
10.5.5 Legacy trap messages 154
10.6 Using net-snmp to access MIB information 155
10.6.1 Reading a parameter with snmpget 155
10.6.2 Writing a parameter with snmpset 156
11 Examples of Use 157
11.1 Introduction 157

11.2 Installation in a system 157
11.3 Seamless switching for identical signals 157
11.4 Seamless SFN for DVB-T Networks 158
11.5 Seamless SFN for DVB-T2 Networks 159
12 Preventive Maintenance and Fault-finding 161
12.1 Preventive maintenance 161

12.1.1 Routine inspection 161
12.1.2 Cleaning 161
12.1.3 Servicing 161
12.1.4 Warranty 162
12.2 Fault-finding 162
12.2.1 Preliminary checks 162
12.2.2 PSU LED not lit / power supply problem 163
12.2.3 Fan(s) not working / unit overheating 164
12.3 Disposing of this equipment 164
12.4 Returning the unit 164
A Glossary 165
B Technical Specification 171
B.1 Physical details 171

B.1.1 Half-width version 171
B.1.2 Full-width (dual power) version 171
B.2 Environmental conditions 171
B.3 Power 172
B.3.1 AC Mains supply 172
B.3.2 DC supply 172
B.4 Input/output ports 173
B.4.1 DVB ASI port 173
B.4.2 Ethernet management port 173
B.4.3 Ethernet data port 173
B.4.4 Serial USB interface 174
B.5 Alarm ports 174
B.5.1 Alarm relay/reset port specification 174
B.6 External reference 174
B.6.1 10MHz/1 PPS input 175
B.7 Compliance 175
B.7.1 Safety 175
B.7.2 Electromagnetic compatibility - EMC 175
B.7.3 CE marking 175
B.7.4 Interface to “public telecommunication system” 176
C Forward Error Correction in IP Networks 177
C.1 IP stream distortion 177

C.2 Standardisation 178
C.3 FEC matrix 178
C.4 Transmission aspects 181
C.5 Quality of service and packet loss in IP networks 182
C.6 Error improvement 183
C.7 Latency and overhead 184
D Quality of Service, Setting Packet Priority 187
D.1 MPLS 187

D.2 Layer 3 routing 187
D.2.1 TNS544 configuration 188
D.3 Layer 2 priority 188
D.3.1 TNS544 configuration 188
E Alarms 189
F References 201
History 9
1 History
Revision Date Comments

2.6.B September 2017 – Removed alarms not applicable to this product.
2.6 November 2014 – Added description of new Switch modes.

– Changed look of users manual.
2.0 February 2012 – Added description of new parameters on Switch page.

– Added description of Input Copies.
– Nevion branding.
1.4 September 2012 – Added description of ASI version
1.2 May 2012 – Initial release
ID: um_tsoipswitch TNS544 TSoIP Switch User’s Manual Rev. 2.6.B (5219)
10
TNS544 TSoIP Switch User’s Manual Rev. 2.6.B (5219) ID: um_tsoipswitch
Introduction 11
2 Introduction
2.1 Scope
This manual is written for operators and users of the TNS544 TSoIP Switch and provides necessary
information for installation, operation and day-to-day maintenance of the unit. The manual covers
the functionality of the software version 2.6.4 or later, and continues to be relevant to subsequent
software versions where the functionality of the equipment has not been changed. When a new
software version changes the functionality of the product, an updated version of this manual will
be provided.
The manual covers the following topics:
• Getting started
• Equipment installation
• Operating instructions
• WEB interface description
• Preventive maintenance and fault finding
• Alarm listing
• Technical specifications
2.2 Warnings, cautions and notes

Throughout this manual warnings, cautions and notes are highlighted as shown below:
Warning: This is a warning. Warnings give information, which if strictly

observed, will prevent personal injury and death, or damage to personal
property or the environment.
Caution: This is a caution. Cautions give information, which if strictly

followed, will prevent damage to equipment or other goods.
Note: Notes provide supplementary information. They are highlighted for

emphasis, as in this example, and are placed immediately after the relevant
text.
12 Introduction
2.3 Heed warnings

• All warnings marked on the product and in this manual should be adhered to. The
manufacturer cannot be held responsible for injury or damage resulting from negli-
gence of warnings and cautions given.
• All the safety and operating instructions should be read before this product is installed
and operated.
• All operating and usage instructions should be followed.
• The safety and operating instructions should be retained for future reference.
2.4 Contact information

Our primary goal is to provide first class customer care tailored to your specific business and
operational requirements.
Please contact us at:
Telephone +47 22 88 97 50
Fax +47 22 88 97 51
E-mail [email protected]
WEB http://www.nevion.com
Mail and visiting address Nevion
Lysaker Torg 5
NO-1366 Lysaker
Norway
Short Product Description 13
3 Short Product Description

The TNS544 is part of the Nevion nSure product line which safeguards the delivery of high-quality
video content, by providing 24/7 monitoring and redundancy switching.
The TNS544 provides intelligent redundancy switch-over between MPEG Transport Streams in
IP-based video centric networks. It ensures the robust transmission of Transport Streams by con-
tinuously monitoring all inputs, switching seamlessly to the back-up stream if errors are detected
or services or components are lost.
The TNS544 offers flexible configuration of inputs, number of switches and outputs. It can be
delivered with up to four 2:1 or two 4:1 switches in one device. All inputs are monitored simulta-
neously in each switch. Any delay differences between the inputs are automatically compensated
enabling seamless switching without any disturbance to end users. The TNS544 also supports
switching between non-identical Transport Streams without having sync loss on the output.
3.1 Summary of features

Features of the TNS544 include:
• Intelligent Transport Stream switching
− Automatic/manual seamless switching
− Automatic network delay compensation
− Fully transparent operation at TS packet level (no PCR restamping or packet re-ordering)
• High density and flexible switch configuration
− Up to 4 independent switches in 1RU half-width 19“
− Configurable number of inputs per switch (2-4 inputs)
− Switch inputs may be ASI, IP or any combination of ASI and IP (if equipped with ASI
connectors)
− 4 secured ASI outputs on power loss
− Output diversity (up to 8 TS over IP outputs per switch and/or up to 4 ASI outputs)
− Fully configurable alarm based switching criteria
− Several alignment modes for various stream types: Null Packet agnostic, SFN Seam-
less, Diversity.
• TS monitoring and error detection
− Simultaneous monitoring of all input MPEG Transport Streams
− Error detection according to ETSI TR 101 290 specification (priority 1 and Transport_error)
− Content alarms
14 Short Product Description
• Industry-leading support for IP video technologies
− Two Gigabit Ethernet interfaces for TS over IP
− IP multicast, unicast and multiple unicast support
− Optional support for Ethernet over Sonet OC-3 / SDH STM-1
− IP wrapping of Transport Streams using SMPTE 2022-2
− Forward Error Correction according to SMPTE 2022-1
− Support for multiple VLANs (IEEE 802.1Q)
− TOS/COS field support for traffic prioritisation
• User-friendly configuration and control
− WEB/XML based remote control
− Easy access to unit from any WEB browser
− Easy integration to NMS systems with SNMP Trap support
− SNMPv2c agent
− Equipment monitoring from Nevion Connect
3.2 Options
The TNS544 is modular and may be equipped according to user requirements. Available hardware
and software options are described below.
3.2.1 Hardware options
ASI ports
The TNS544 is fitted with 8 ASI connectors, of which 4 are inputs and 4 are secured outputs.
On power loss (or by manual configuration) the outputs are wired to the inputs.
SFP Module
The TNS544 is equipped with an SFP socket. Different types of SFP modules may optionally
be delivered to provide optical Gigabit transportation.
Dual power supplies

The TNS544 may optionally be delivered with dual internal wide-ranging AC power sup-
plies. In this case the size of the cabinet is always full-width 1RU. The power supplies cover
the voltage range 100-240 VAC, 50/60 Hz.
Short Product Description 15
3.2.2 Software options
The TNS544 functionality depends on the software licences installed. The following table de-
scribes the features available as software options. Please refer to Section 9.4.7.3 for more informa-
tion how to obtain and enable feature upgrades.
Table 3.1 Functionality enabled through software licences
Functionality Code Max Description

value
SFP module SFP - Enables operation of the Small form-factor pluggable (SFP) transceiver
slot.
SFP configuration SFPC - Enables configuration interface and parameter storage for some
specifically supported SFP modules.
Seamless SFN SSFN - Controls whether seamless SFN switching for DVB-T and DVB-T2
networks is available.
Forward Error Correction FEC - Controls availability of the FEC feature for IP outputs and IP inputs.
SFN Rate Lock SFNR - Controls whether the device can use DVB-T MIP timestamps to lock
outgoing rate when in IP to ASI mode.
Number of seamless switches SSWX 4 Controls the number of active Transport Stream Switching Units.
Connect control TCON - Enables supervision of the unit through the Connect Software.
16
Getting Started 17
4 Getting Started
This section provides a short description of the minimum steps that must be taken in order to start
operating the TNS544.
If you are an experienced user of Nevion equipment or similar types of TS switching equipment
the following description should enable you to quickly install the TNS544 TSoIP Switch and start
operation. If this is your first time to install such equipment you are strongly adviced to read the
full installation procedure. To gain full benefit of the product functionality and capabilities refer
to the user interface description.
The procedures outlined below are based on the assumption that the unit is in the factory default
state.
4.1 Configure the management interface

Since the TNS544 is all Web controlled the first step is to set up the IP address for the management
interface.
Changing the default IP address using the Web interface requires that your management computer
may be configured with a static IP address. If a static IP address cannot be configured on your
computer the IP address may be configured via the terminal interface. The procedure is described
in the user manual, refer to section 8.3.2.
Note: Avoid connecting through a network at this stage, as this may give
unpredictable results due to possible IP address conflict.
1. Connect an Ethernet cable directly between the PC and the Ethernet Control port of the
TNS544. The default IP address of the TNS544 is 10.0.0.10/255.255.255.0. Configure the
PC to be on the same subnet as the TNS544.
2. Open your Web browser and type http://10.0.0.10 in the address field of the browser.
Log into the GUI with username admin and password salvador.
3. Browse to Device Info > Network > Control in the GUI, and set the IP address settings
required for your network. Click Apply to activate the new parameters.
4. The connection with your management PC will now be lost. To re-connect to the TNS544
connect both the “Control” port of the unit and the management PC to the network. The
IP settings of the management PC must now be set to agree with the network used.
5. Again, open your Web browser and type http: (New-IP-Address) in the address field of the
browser. Log into the GUI with username admin and password salvador.
18 Getting Started
4.2 Configure device name and time settings

1. Assign a name for the device in order to more easily identify the unit in the network.
Browse to Device Info > Product Info and enter a Name and Inventory ID. Click Apply to
activate.
2. Set date and time of the real time clock to ensure correct time stamping of the alarm log
entries. Browse to Device Info > Time Settings. The internal clock may be used to time
stamp alarm log entries, in which case a manual Date and Time adjust is all that is needed.
Click Apply to activate.
You may enable an external time source to provide a common reference for alarm logs of
all units of a system. Refer to the user manual for details.
4.3 Configure operation

A TNS544 can be configured with up to 4 switches. A Switch may be sourced from up to 4 inputs,
IP and/or ASI, and the output of the Switch may be routed to one or several IP outputs or ASI
outputs. Transport streams received on IP are de-encapsulated in to TS packets and the switching
occurs on TS level. After switching, the output of the Switch is appropriately encapsulated before
being sent to an IP output interface. The TNS544 operation does not distinguish between single
program and multi program transport streams.
4.3.1 Enabling IP inputs
This procedure enables an IP input.
1. Browse to Inputs > Inputs Overview > IP Inputs. At the bottom of the page, click the
Add IP Input button. Click Apply. An entry for the new input appears in the table, with
default values for all parameters.
2. Open the IP input configuration page by clicking on the table entry.
3. In the Main page, IP RX Configuration field, tick the Enable input check box and type an
identifying name, e.g. the service name, in the Input label box. Specify the UDP receive
port. If the signal to receive is an IP multicast click the Join multicast check box and enter
the multicast address in the adjacent field.
4. Select the Ethernet interface from the alternatives in the Source interface pull-down list.
Click Apply to activate.
5. The IP RX Status field will indicate if the attached network cable carries a valid signal
and the remaining status fields will report the properties and contents of the incoming
transport stream.
The coloured indicator at the top of the page shows the overall signal status.
Getting Started 19
4.3.2 Enabling the Switch
This procedure enables the Switch and adds an IP input.
1. Browse to Inputs > Switch. In the Main page, Switch Configuration field, tick the Enable
check box and type an identifying name, e.g. the switch name, in the label box.
2. For automatic switching, tick the Automatic Switch check box. Specify the initial buffer-
ing time. Click Apply.
3. The Switch Status field presents a graphical view of the Switch status and Switch Statis-
tics field indicates how many times switching has been occured for both automatic and
manual switches.
4. Go to the Inputs page, Switch Input Configuration field. At the bottom of the page, choose
one of the pre-defined IP input and click the Add button. Click Apply. Alternatively, a new
IP input can be added buy choosing ’New IP Input’. An entry for the new IP input appears
in the table in the Switch Input Status
5. In the Switch Input Status field, the inputs, their alarms levels, groups and delays are
illustrated.
For further details on switch setup see Section 9.5.3.
4.3.3 Enabling IP output
This procedure enables IP outputs.
1. Go to the Output > Switch Outputs > Switch Main page and click on the Add Destination
button at the bottom of the page.
2. Having confirmed the addition of an IP destination, the IP outputs field changes to allow
specifying IP destination parameters.
3. Choose the IP output and tick the Enable box in the Basic IP Configuration field and enter
the appropriate destination address in the field provided. Select RTP or UDP protocol and
enter the UDP destination port number in the box provided.
4. Click Apply to commit the changes.
5. The IP Status field indicates the default physical interface used. This may be changed by
clicking the Manual destination interface in the Basic IP Configuration field and selecting
the desired interface from the pull-down list.
The IP status field also indicates when the destination has been reached (Resolved = Yes) and the
bit rate of the IP encapsulated transport stream. Several additional IP parameters may be set in the
Output > Switch Outputs > IP destination > Switch Main page. See section 9.6.3.1 for details.
20
Installing the Equipment 21
5 Installing the Equipment
Caution: The TNS544 must be handled carefully to prevent safety hazards

and equipment damage. Ensure that the personnel designated to install
the unit have the required skill and knowledge. Follow the instructions
for installation and use only installation accessories recommended by the
manufacturers.
5.1 Inspect the package content

• Inspect the shipping container for damage. Keep the shipping container and cushioning
material until you have inspected the contents of the shipment for completeness and have
checked that the TNS544 is mechanically and electrically in order.
• Verify that you received the following items:
− TNS544 with correct power supply option
− Power cord(s)
− CD-ROM containing documentation and Flash Player installation files
− Any optional accessories you have ordered
Note: 48 VDC versions do not ship with a power cord; instead a Power
D-SUB male connector for soldering to the supply leads is supplied.
5.2 Installation Environment

As with any electronic device, the TNS544 should be placed where it will not be subjected to
extreme temperatures, humidity, or electromagnetic interference. Specifically, the selected site
should meet the following requirements:
• The ambient temperature should be between 0 and 50 ◦ C (32 and 122 ◦ F).
• The relative humidity should be less than 95 %, non-condensing. Do not install the unit
in areas of high humidity or where there is danger of water ingress.
• Surrounding electric devices should comply with the electromagnetic field (EMC) stan-
dard IEC 801-3, Level 2 (less than 3 V/m field strength).
• The AC power outlet (when applicable) should be within 1.8 meters (6 feet) of the TNS544.
• Where appropriate, ensure that this product has an adequate level of lightning protec-
tion. Alternatively, during a lightning storm or if it is left unused and unattended for
long periods of time, unplug it from the power supply and disconnect signal cables. This
prevents damage to the product due to lightning and power-line surges.
Warning: If the TNS544 has been subject to a lightning strike or a power

surge which has stopped it working, disconnect the power immediately.
Do not re-apply power until it has been checked for safety. If in doubt
contact Nevion.
5.3 Equipment installation

The TNS544 is designed for stationary use in a standard 19" rack. When installing please observe
the following points:
• Route cables safely to avoid them being pinched, crushed or otherwise interfered with.
Do not run AC power cables and signal cables in the same duct or conduit.
• The TNS544 has all connectors at the rear. When mounting the unit, ensure that the in-
stallation allows easy access to the rear of the unit.
• The fans contained in this unit are not fitted with dust/insect filters. Pay particular atten-
tion to this when considering the environment in which it shall be used.
• Make sure that the equipment is adequately ventilated. Do not block the ventilation holes
on each side of the TNS544.
5.4 Ventilation
Openings in the cabinet are provided for ventilation to protect it from overheating and ensure
reliable operation. The openings must not be blocked or covered. Allow at least 50 mm free air-
space each side of the unit.
Warning: Never insert objects of any kind into this equipment through
openings as they may touch dangerous voltage points or create shorts that
could result in a fire or electric shock. Never spill liquid of any kind on or
into the product.
• This product should never be placed near or over a radiator or heat register. Do not place
in a built-in installation (e.g. a rack) unless proper ventilation is provided in accordance
with the device airflow design as depicted in Figure 5.1 .
• The TNS544 may be vertically stacked in 19" racks without intermediate ventilation pan-
els. In systems with stacked units forced-air cooling may be required to reduce the oper-
ating ambient temperature.
Figure 5.1 shows the air path through the unit, where cool air is taken from the left hand
side, seen from the front.
Cool Warm
CP541
Air In Air Out
Figure 5.1 Air path through the unit
5.5 Power supply

The TNS544 may be delivered rated for AC or DC operation, respectively.
Warning: This product should be operated only from the type of power
source indicated on the marking label. Please consult a qualified electrical
engineer or your local power company if you are not sure of the power
supplied at your premises.
5.5.1 AC power supply
The TNS544 has a wide-range power supply accepting the voltage range 100-240 VAC, 50/60 Hz.
Please refer to Appendix B for a detailed specification of the AC power supply.
5.5.1.1 Dual AC power supplies
Alternatively, the TNS544 may be fitted with dual internal wide-range AC power supplies. If so,
the size of the cabinet is full-width 19" rack, 1RU. The power supplies cover the voltage range
100-240 VAC, 50/60 Hz.
During normal operation, load-sharing is used between the internal supplies. In case of a single
power supply failure alarms will be raised and the unit will continue operating off the second
power supply. To guard against failure in the external power circuitry it is imperative to connect
each power supply to separate AC mains circuits.
Please refer to Appendix B for a detailed specification of the AC power supply.
5.5.1.2 AC power cable
Ensure that the AC power cable is suitable for the country in which the unit is to be operated.
Caution: Power supply cords should be routed so that they are not likely
to be trod on or pinched by items placed upon or against them. Pay
particular attention to cords at plugs and convenience receptacles.
The unit is supplied with a two meter detachable mains supply cable equipped with a moulded
plug suitable for Europe, UK or USA, as appropriate. The wires in the mains cable are coloured
in accordance with the wire colour code shown in Table 5.1.
Table 5.1 Supply cable wiring colours
Wire UK (BS 1363) EUROPE (CEE 7/7) USA (NEMA 5-15P)

Earth Green-and yellow Green-and yellow Green
Neutral Blue Blue White
Live Brown Brown Black
5.5.1.3 Protective Earth/technical Earth

To achieve protection against earth faults in the installation introduced by connecting signal cables
etc., the equipment should always be connected to protective earth. If the mains supply cable is
disconnected while signal cables are connected to the equipment, an earth connection should be
ensured using the Technical Earth connection terminal on the rear panel of the unit.
Warning: This unit must be correctly earthed through the moulded plug
supplied. If the local mains supply does not provide an earth connection
do not connect the unit.
Caution: Consult the supply requirements in Appendix B prior to con-

necting the unit to the supply.
The unit has a Technical Earth terminal located in the rear panel. Its use is recommended. This is
not a protective earth for electrical shock protection; the terminal is provided in order to:
1. Ensure that all equipment chassis fixed in the rack are at the same technical earth poten-
tial. To achieve this, connect a wire between the Technical Earth terminal and a suitable
point in the rack. To be effective all interconnected units should be earthed this way.
2. Eliminate the migration of stray charges when interconnecting equipment.
Warning: If the terminal screw has to be replaced, use an M4x12mm long

pozidrive pan head. Using a longer screw may imply a safety hazard.
5.5.1.4 Connecting to the AC power supply
Warning: Do not overload wall outlets and extension cords as this can
result in fire hazard or electrical shock. The unit is not equipped with an
on/off switch. Ensure that the outlet socket is installed near the equipment
so that it is easily accessible. Failure to isolate the equipment properly may
cause a safety hazard.
To connect the unit to the local AC power supply, connect the AC power lead to the TNS544 mains
input connector(s) and then to the local mains supply.
5.5.2 DC power supply
The TNS544 can be delivered with a 48 VDC power supply for use in environments where this
is required. The DC power supply accepts an input voltage range of 36-72 VDC. Please refer to
Appendix B for detailed specification of the power supply.
5.5.2.1 Dual DC power supplies
Alternatively, the TNS544 may be fitted with dual internal wide-range DC power supplies. If so,
the size of the cabinet is full-width 19" rack, 1RU. The power supplies cover the voltage range 36-72
VDC.
During normal operation, load-sharing is used between the internal supplies. In case of a single
power supply failure alarms will be raised and the unit will continue operating off the second
power supply. To guard against failure in the external power circuitry it is imperative to connect
each power supply to separate DC mains circuits.
Please refer to Appendix B for a detailed specification of the DC power supply.
5.5.2.2 DC power cable
Units delivered with DC power supply have a 3-pin male D-SUB power connector instead of the
standard mains power connector. Also a female 3-pin D-SUB connector is supplied. The pin as-
signment is shown in Table 5.2. The power cable itself is not supplied.
Table 5.2 DC power connector pin

assignment
Pin Placement Specification

1 top + (positive terminal)
2 middle - (negative terminal)
3 bottom Chassis Ground
To connect the unit to the local DC power supply:
1. Use an electronics soldering iron or a hot air workstation to attach the supplied female
D-SUB power connector to suitable power leads.
2. Connect the power leads to your local power supply.
3. Connect the DC power connector, with attached power leads, to the TNS544 power input
connector.
5.5.3 Powering up/down
Before powering-up the unit, please ensure that:
• The unit is installed in a suitable location
• The unit has been connected to external equipment as required
Power up the unit by inserting the power cable connected to the power source. When the unit has
finished the start-up procedure, the fans will run at normal speed. Please check that all cooling
fans are rotating. If they are not, power down the unit immediately.
Power down the unit by removing the power supply connector at the rear of the unit.
Functional Description 27
6 Functional Description
The TNS544 is designed to perform seamless switching of MPEG-2 Transport Streams TS, where
the input may be IP and/or ASI. Seamless switching is supported when using identical input
transport streams. Identical input transport streams have the exact same TS packets at the same
packet locations in the stream.
The product offers an easy-to use WEB based user interface giving access to all configuration set-
tings and monitoring results. The TNS544 may be integrated with network management systems
via the SNMP interface.
This chapter gives a brief description of the inner workings of the TNS544, to give a better under-
standing of how the product works, how you use it and what you can use it for.
Figure 6.1 shows a functional block diagram of the main components inside TNS544. The different
blocks are described in more detail in the following sections.
Input Seamless operation Output
Optional ASI Optional ASI

TS seamless switch
· Service monitoring
· PID monitoring
...
IP in · ETR 290 Pri 1 IP out
Management
· Graphical user interface Time Power

· Alarm generation synchronisation 230VAC/48DC
HTTP/XML Config. Alarm

SNMP database Relay
1PPS
Administration
Alarm log
Alarm traps
Figure 6.1 TNS544 block diagram
Each input is fed to a user specified seamless switch. The switch will match the streams and group
them into matching groups. In case of sync loss on one of the input streams, the TNS544 will switch
to one of the other inputs in a seamless way, causing no glitch or other errors at the output.
In case of higher level errors (content errors), a high level sophisticated switch logic takes care of
the switching. Any kind of detectable alarm for an input may be used as switch criteria.
At any time, an operator may switch from the current selected IP stream on a switch to a different
IP stream on the same switch. This on-demand switching will also be seamless.
Note: Seamless switching is only possible when the two incoming streams
are identical. In case the streams are from different sources, switching will
be done on a TS packet boundary to at least avoid sync loss at the output.
6.1 Input and output

The input interface includes two seperate ethernet ports and one SFP socket that can be used to
receive or transmit MPEG-2 Transport Streams over IP. However, only two of the three interfaces
may be active at any one time. One of the Ethernet inputs may be substituted for a SFP module
giving the option to provide input via e.g. optical fibre. Use of a SFP module is user configurable,
provided this software option has been licensed.
Figure 6.2 gives a detailed overview of how the input and output interfaces are related and how
they are connected to the seamless switches.
ASI Inputs ASI Outputs
1.IN 1.OUT
(secured)
2.IN 2.OUT
(secured)
3.IN 3.OUT
(secured)
4.IN 4.OUT
(secured)
TS Seamless Switch
Buffer
Buffer
TSoIP inputs
Buffer TSoIP output
Buffer
Ethernet / VLAN / IP layer

Data 1
OR Ethernet / VLAN / IP layer

Data 2 SFP
Figure 6.2 Inputs and outputs
If the unit is equipped with ASI connectors, the are 8 ASI connectors, which consists of 4 pairs
with one input and one ouput. Each output has a controllable relay which let’s the user select if
the output TS should come from the corresponding input or from any of the switches. On power
loss the ASI relay will fall back to it’s upper position, i.e. each output is wired to it’s corresponding
input. On power loss there will be no IP output. All ASI output ports should be terminated with
a 75 ohms termination, or by connected to another equipment.
These are the following capabilities of the TNS544 TSoIP Switch:
• The TNS544 may have from 1 to 4 switches, where the number of switches is a licenced
feature (SSWX).
• All inputs may be routed to any of the switches, but an input may not be routed to more
than one switch simultaneously.
• A switch may have from 1 to 4 inputs, where each input may be ASI or IP or a combination
of ASI and IP inputs.
• Each switch may have up to 8 IP output copies, and up to 4 ASI output copies. In total
there are 4 ASI output ports shared among the switches.
• All IP inputs and IP outputs may use any VLAN on any of the Ethernet/SFP interfaces.
• An ASI output may only used as an output of the same switch as it’s corresponding input.
If however the corresponding input is not used as a switch source, the output may be used
as an output of any switch.
6.1.1 Protocol mapping
Ethernet Optional IP UDP RTP 1-7 MPEG TS packets

14 bytes VLAN 20 bytes 8 bytes 12 bytes 188 – 1316 bytes
[IEEE 802.3/802.3u] 4 bytes [RFC 769] (RFC 768) (RFC 1889) [ISO/IEC 13818-1]
[802.1q]
Figure 6.3 Protocol mapping
When transmitting TS streams over IP, the protocol mapping is according to figure 6.3. The VLAN
framing and RTP encapsulation are optional.
The RTP layer is important for diagnosing network related problems, since it contains a sequence
number that can be used for packet loss detection.
The maximum transfer unit (MTU) for Ethernet is usually 1500 bytes. This limits the number of
transport stream packets to embed into the outgoing Ethernet/IP frames to be between 1 and 7.
6.2 Management subsystem

The management subsystem is a set of modules that handles all the interfaces to monitor and
control the operation of the TNS544.
The management subsystem communicates with the users, both humans and machines, via the
following interfaces:
• Front panel and back panel LEDs for status
• Graphical user interface via Flash application in WEB browser
• SNMP traps on alarms
• SNMPv2c Agent
• TXP (XML Protocol) to retrieve and set configuration and status
• Alarm relays on alarms
• SNTP client for real time clock synchronisation
• Terminal interface either over Telnet or USB interface for debugging
• FTP server for direct file system access
The management subsystem communicates with other internal modules to make the unit perform
the wanted operations.
6.2.1 Graphical user interface
Operators monitor and control the TNS544 mainly via the Adobe Flash GUI application served
from the device’s WEB server. The GUI application is accessed via a WEB browser that commu-
nicates with the configuration framework through an HTTP/XML based protocol.
The device exposes extensive status information to the web GUI providing detailed reports and
real-time monitoring displays to the device administrator.
All the device configuration parameters available on the TNS544 can be controlled from the web
GUI.
6.2.2 Configuration database
The management subsystem processes configuration changes as transactions. All configuration

changes made to the device are validated against the current running configuration before com-
mitting them to the device. This limits the risks of the administrator implementing changes that
may cause down-time on the unit due to incompatible configuration settings.
Configurations can be imported and exported via the GUI. It is possible to clone the entire config-
uration of one device to another by exporting the configuration of one device and importing it to
another.
Configurations exported via the web GUI are formatted as human readable/modifiable XML files.
These files can be viewed or altered using any standard text or XML editor such as Windows
Notepad.
To simplify cloning of devices, certain exported parameters within the XML file are tagged as
device specific and therefore will be ignored when imported to either the same device or another.
These parameters are as follows:
• Device Name and Inventory ID
• IP network parameters
• On-device stored configurations
6.2.3 Alarm manager
The TNS544 contains an integrated alarm manager responsible for consistently displaying the
alarm status of each individual interface.
“Port Alarms” are alarms bound to a specific input or output port via a port indexing system.
The alarm severity for port related alarms can be configured per port level. “Device Alarms”
are global to the device and are not bound to any specific port. They do not follow the indexing
scheme. These are classified as “System Alarms”.
Alarms are graphically represented in a tree structure optimized for simplified individual viewing
and configuration. The “Device Alarm” tree is available from the “Device Info” page. The alarm
tree for each port is available on the “Alarms” page for each port.
The alarm manager presents the alarm of highest severity upon the external interfaces of the de-
vice. The severity level of each individual alarm can be defined by the administrator. Alarm
configuration is covered in greater detail in the “Alarm configuration” section.
SNMP traps are dispatched to registered receivers whenever there is an alarm status change.
Alarm relay 1 and alarm LED are controlled to signal whenever there is a critical alarm present.
Alarm relay 2 is configurable.
The alarm manager keeps a log in non-volatile memory of the latest 10000 alarms that have oc-
curred.
As an additional option, the alarm manager in the TNS544 supports so-called Virtual Alarm Relays.
These are highly programmable items that can be customised to react to virtually any given alarm
event or combination of alarm events. The status of each virtual alarm relay can be viewed in the
GUI and can also be exported using SNMP. Details on configuring the virtual alarm relays can be
found in the WEB interface section.
6.3 Time synchronisation

The TNS544 contains an internal real-time clock that is used for all internal timestamps. The in-
ternal clock is battery backed up in order to continue operating while the unit has no power.
The internal time can be synchronised as follows:
• Manual setting.
• From NTP servers using SNTP protocol. Up to four NTP servers can be configured for
NTP server redundancy.
More than one clock source may be specified in a prioritised order. If one source fails the next
priority source will be used.
6.4 The SFP module

The SFP module (SFP = small form-factor pluggable) is a third-party product providing an extra,
optional interface to the TNS544. Depending on the module type it may act as a direct bridge to
E3 and T3 telecom network lines using coaxial cable, or provide a high-speed STM-1/OC-3 optical
interface employing single or multi-mode optical fibre.
Figure 6.4 A
typical SFP module
An SFP module may be configurable or non-configurable. Using a configurable SFP module the
parameters relevant to its operation are controlled through the TNS544 WEB interface. Control
information is passed to and from the SFP module using the I 2C protocol.
A wider range of settings are available using the SFP module internal WEB server. To access the
internal WEB server an SFP configuration adapter is required. For further information on this,
and for detailed technical specifications, refer to the vendor’s manual for the specific device.
The TNS544 provides a slot to accommodate an SFP module. Access to the SFP interface is possible
if the SFP software is installed and the feature key has been licensed (see Section 9.4.7).
The SFP interface must be expressly enabled from the TNS544 user interface (Device Info > Main-
tenance > General) by selecting SFP from the Electrical/SFP dropdown menu and hitting Apply
After rebooting, the user interface will reflect the presence of the SFP network interface. This is
managed the same way as other network interfaces, but with an extra WEB page tab to support
SFP specific functionality.
Physical Description 33
7 Physical Description
The TNS544 TSoIP Switch consists of a main board in a screened, self-ventilated cabinet. The unit
is 1RU high and two units can be mounted side-by-side behind a common front panel in a 19 inch
rack. All inputs and outputs are located on the rear panel and there are no front panel keypad or
display.
The front panel provides four LEDs per TNS544. The meaning of each LED indicator is shown in
table 7.1.
Table 7.1 Front panel LED descriptions
Indicator Colour Description

Power Green This LED is lit when power is on and initialisation is complete
Alarm Red This LED is lit when a failure is detected by the unit
These LEDs are replicated on the rear panel, as shown in figures 7.1 and 7.2 depending on the
units ASI hardware configuration.
Mains Power
Connector
1 IN 1 OUT 2 IN 2 OUT 3 IN 3 OUT 4 IN 4 OUT
DATA 2 DATA 1 CONTROL 1PPS/

SFP ALARM /RESET
10MHz
USB
GND
AC100-240V
PSU ALARM 0.7A 50-60Hz
SFP USB Ethernet Alarm/Reset 1PPS Technical

Port Port Management Port Interface Input Earth
Ethernet
Data Ports
Figure 7.1 Rear panel no ASI connectors
Remove mains supply before moving or installing the equipment. Ensure ESD precautions are
observed while interconnecting equipment.
7.1 ASI ports

The TNS544 may be shipped with or without ASI connectors. If equipped with an ASI board, there
will be 8 ASI connectors on the rear panel, which are fixed as either input or output connectors.
There are in total 4 ASI inputs and 4 ASI outputs, located in pairs of 1 input and 1 output as seen
in figure 7.2. The input and output pairs are also connected through a passive relay, such that on
power loss all input and output ASI pairs will be connected. See figure 6.2 for a circuit diagram. It
ASI inputs ASI outputs Mains Power

Connector
1 IN 1 OUT 2 IN 2 OUT 3 IN 3 OUT 4 IN 4 OUT
DATA 2 DATA 1 CONTROL 1PPS/

SFP ALARM /RESET
10MHz
USB
GND
AC100-240V
PSU ALARM 0.7A 50-60Hz
SFP USB Ethernet Alarm/Reset 1PPS Technical

Port Port Management Port Interface Input Earth
Ethernet
Data Ports
Figure 7.2 Rear panel with ASI connectors
is also possible to force a passive connection for each relay while power is connected, see chapter
9.6.2.1 for details on how to do this.
For physical specification of the ASI ports, please refer to Appendix B: Technical Specification.
7.1.1 ASI input ports
Inputs signals connected to the ASI ports should be a DVB or ATSC compliant transport streams,
depending on the selected setting (see Section 9.4.7.1 and 9.5.2.1).
7.1.2 ASI output ports
The ASI port ouputs a DVB compliant transport stream. When no stream can be supplied the
output will be idle characters, only. If a stream is supplied the output will be a combination of
MPEG-2 transport stream data bytes and idle characters.
7.2 1 PPS Input

An optional interface module provides an input connector for a 1 PPS synchronisation signal for
the internal system clock. Connecting an 1 PPS signal will reduce potential output jitter.
The signal is:
• 1 PPS. 50 Ω TTL input for a 1 pulse-per-second signal.
For physical parameters of the 1 PPS port, see appendix B.6.1.
7.3 Ethernet data ports

Two Ethernet ports are provided for data transmission. The default port setting is auto sense be-
tween 10, 100 and 1000 Mbit/s. The operator is able to force the interface speed to fixed 100 Mbit/s
or fixed 1000 Mbit/s. This is useful to minimize the synchronisation time when reconnecting sig-
nal cables.
For flexibility, the TNS544 provides an optional SFP (Small Form-Factor Pluggable) slot to accom-
modate a copper or optical interface SFP, allowing customers to use different SFPs for special dis-
tance, cost, existing infrastructure and future expansion requirements. The TNS544 is prepared
for electrical (1000Base-T) or optical 1000BASE-SX and 1000BASE-LX SFP transceivers. When the
SFP module is in use Ethernet port Data2 is no longer available.
The LEDs for the electrical Ethernet data port are used as follows:
Table 7.2 Ethernet data port LEDs
LED indicator Location Description Colour

Speed Left 10 Mbit/s Unlit
100 Mbit/s Green
1000 Mbit/s Yellow
Traffic and link Right Lit=Link, Blink=data tx or rx Green
Note: The TNS544 interface to the SFP slot is always Gigabit Ethernet.
Other bitrates are not supported.
Note: In case the SFP port is used, only the electrical Ethernet port
“DATA1” will be available for use. The second data port will be deacti-
vated when SFP is turned on using the settings in the user’s interface.
7.4 Ethernet management port

The TNS544 provides one Ethernet port for control and management. The default port setting is
Auto sense, 10 or 100 Mbit/s. Connect the management port to the management network. The
LEDs for the management port indicate as follows:
Table 7.3 Ethernet management port LEDs
LED indicator Location Description Colour

Speed Left Unlit = 10 Mbit/s, Lit = 100 Mbit/s Green
Traffic and link Right Lit=Link, Blink=data tx or rx Green
7.5 Power supply

Section 5.5 provides details of the power supply, protective earth and security. Read all these
instructions prior to connecting the units power cable.
7.6 Technical earth

Connect the Technical earth to a suitable earth point.
7.6.1 Alarm/Reset connector
The unit is equipped with a 9-pin male DSub connector to provide alarm information.
Two programmable relays are provided. The first relay is always activated on a critical alarm or
when the unit is not powered. Please refer to section 9.4.2.3 for a description how to program the
relays.
The pin-out of the connector is shown in table 7.4.
Table 7.4 Alarm/Reset

connector pin out
Pin Function
1. Relay 2 - Closed on alarm (NC)
2. Relay 2 Common
3. Relay 2 - Open on alarm (NO)
4. Prepared for +5V Output
5. Ground
6. Alarm Relay - Closed on alarm (NC)
7. Alarm Relay Common
8. Alarm Relay - Open on alarm (NO)
9. Optional Reset Input / GPI
When there is a critical (level 6) alarm in the unit, if the unit is not powered or if any other pro-
grammed condition for relay 1 is satisfied there will be a connection between pin 6 and pin 7.
When the above conditions are not present there will be a connection between pin 7 and pin 8.
The optional (additional) relay will follow the same behaviour except that it can also be pro-
grammed not to be activated for a critical (level 6) alarm.
A connection between pin 9 and 5 (or a TTL low on pin 9) will hold the unit in reset if this function
has been enabled. The connection must be held for 0.5 seconds in order to activate the reset. This
can be used to force a hard reset of the unit from an external control system. This pin can also be
used as a general purpose input (GPI).
For more details regarding the alarm relay please refer to Appendix on Technical Specifications B.
7.6.2 Serial USB interface
The TNS544 provides a USB interface intended for initial IP address setup. The interface conforms
to the USB 1.1 specification through a Mini USB connector.
The USB interface requires a special COM port driver on the PC that shall communicate with the
device. This driver is provided on the product CD shipped with the device.
38
Operating the Equipment 39
8 Operating the Equipment

The TNS544 is configured and controlled locally and remotely through a Flash-based Web inter-
face. The only application required on the computer to use this interface is a Web browser and the
Adobe Flash Player.
Note: Adobe Flash Player 9.0 or newer is required to use the Web interface
of the TNS544. As a general rule it is recommended to always use the
latest official release of Flash Player (version 10 or newer). If the Flash
Player is not installed on the adminstrator PC, a copy is provided on the CD delivered
with the device. Alternatively, the latest Adobe Flash Player can be downloaded
free of charge from http://www.adobe.com.
Note: When using Microsoft Internet Explorer, version 6.0 or higher is

required. It is however recommended to upgrade to version 8.0 or newer
for best performance.
8.1 Accessing the graphical user interface

The default IP address of the TNS544 will most probably not be suitable for the network where the
unit will operate. Therefore the user should change the IP address of the management interface
so that access may be gained from the network.
The TNS544 offers two options to alter the user interface IP address; through an Ethernet connec-
tion or using a USB terminal interface. If your management computer allows setting a fixed IP
address, change the IP address using the Ethernet option described in Section 8.3.1.
If a static address cannot be configured on your management computer, Section 8.3.2 gives the
procedure to initially configure device network parameters (IP, netmask, etc...) using the USB
terminal interface.
Configuring the device functionality according to operational needs is done using the Web inter-
face, see Chapter 9.
8.2 Password protection

Remote access to the device is controlled by password protection. If you access the TNS544 using
the USB terminal interface a password is not required.
There are 3 user levels providing different user privileges, each with a separate default password:
Username Default password Privileges

admin salvador Full access to device
operator natal Configure setting, cannot alter passwords
guest guest View configuration and alarm logs
The passwords can later be changed, either from the Web GUI or via the terminal.
8.2.1 Resetting the password list
If a password is lost, the password list can be reset to factory defaults via the local USB terminal
interface. To reset the password list, type the following command in the terminal interface:
userdb factory_defaults
Note: The factory_defaults option on the userdb command is avail-

able without administrator previledges only when accessing the terminal
via the local USB interface. In remote terminal sessions with a Telnet
client, administrator privileges are required to run the same command.
8.3 Changing the IP address of the unit

The TNS544 is supplied with a dedicated management Ethernet port, labeled Control. The default
IP configuration (IP address and netmask) of the port is 10.0.0.10/255.255.255.0.
8.3.1 Changing IP address via the Web GUI
Changing the default IP address using the Web interface requires that your management computer
may be configured with a static IP address.
Note: Avoid connecting through a network at this stage, as this may give
unpredictable results due to possible IP address conflicts.
1. Connect an Ethernet cable directly between the PC and the Ethernet control port of the
TNS544. Configure the PC to be on the same sub net as the TNS544. See Figure 8.2.
2. Open your web browser and type http://10.0.0.10 in the address field of the browser. Log
into the GUI with username admin and password salvador.
3. Browse to Device Info -> Network -> Control in the GUI, and set the correct IP address
settings. Click apply to activate the new parameters. Figure 8.1 shows this GUI screen.
Note: Contact with the unit’s GUI will be lost. Please type http://<your
new IP address> in your browser to reconnect to the unit.
Windows XP example
The screen-shot in Figure 8.2 shows how to configure the network interface in Windows XP to
communicate with the TNS544 with factory default settings. The IP address/netmask is set
Figure 8.1 Configuring network settings via the Web GUI
Figure 8.2 Setting static IP address 10.0.0.11 in Windows XP
to 10.0.0.11/255.255.255.0 which is on the same sub net as the TNS544, and does not conflict
with the IP address of the device.
Note: If several new devices are accessed, one after another, the ARP
cache of the computer from which the devices are being accessed may
have to be flushed between each device, since the same IP address will be
used for different MAC addresses. On Windows XP this is done on the command
line typing the command ’arp -d *’
8.3.2 Changing the management port IP address via terminal interface
If a static IP address cannot be configured on your computer, follow the procedure below to con-
figure the IP address via the terminal interface.
1. Install the USB driver from the product CD (setup_ftdi_usb_drivers.exe). (This step may be
omitted if the driver has already been installed.)
2. Connect your computer USB port to the TNS544 USB port using a suitable cable.
3. Access the terminal interface using a suitable terminal program, emulating an ANSI ter-
minal, on your PC (e.g. HyperTerminal). The USB will appear as a virtual COM port on
your PC. No specific serial port settings are required. Assure "scroll lock" is not on. Type
<enter> and see that you have a prompt (app>).
4. Test that the connection is successful by hitting the <Enter> key. If successfull an >app
prompt should be shown.
5. In the terminal, type the following command and press <Enter>:
net ipconfig --ip <ip address> --mask <subnet mask> --gw <default gateway>.
Example:
app>net ipconfig --ip 10.40.80.100 --mask 255.255.255.0 --gw 10.40.80.1
This will result in the IP address 10.40.80.100 being set. The subnet mask is set to 255.255.255.0
and the default gateway to 10.40.80.1.
Note: The product CD shipped with the TNS544 contains a USB driver
to use for serial communication with the device on the USB port. The
MS Windows driver installation script is configured to give a one-to-one
relationship between the physical USB port number on the PC and the COM port
number to use on the PC. Drivers retrieved from http://www.ftdichip.com will also
work, but these may not have the same COM port number mapping.
8.3.3 Configuring automatic IP address assignment
The TNS544 can be configured to obtain an IP address automatically from a DHCP server on the
network. See section 8.3.1 for how to connect, and section 9.4.4.1.1.1 for how to configure this
from the GUI. Alternatively, configure it in the terminal by connecting as in 8.3.2 and issuing the
following command:
ipconfig --dhcp 1 --hostname <your_device_name>
Example:
ipconfig --dhcp 1 --hostname bonemachine-100
Replace <your_device_name> with the name to register in the DNS system for your device. After
this, it should be possible to contact the unit in a browser using the URL:
http://<your_device_name>
To disable automatic IP assignment, use the command
ipconfig --dhcp 0
Note: Hostname registration is only done via the DHCP server, so if

DHCP is not enabled the hostname is not registered. The default hostname
used is on the format TNS544-<serial-no>-<interface-no>
Note: If automatic IP address assignment is configured and the interface

is connected to a network that does not support DHCP, the interface will
not receive an address and will fall back to a link local address after about 1
minute, using the first available address in the range 169.254.1.0 - 169.254.254.255.
If you have a unit that has been configured with DHCP, but current network does
not support it, you should be able to connect to the device for reconfiguration on a
local network connection using the address 169.254.1.0. If more devices are using
link local addresses, try 169.254.1.1, 169.254.1.2, etc.
8.3.4 Detecting the management port IP address

If you have a unit and do not know the IP address of the Control Interface there are a few options
available. The simplest solution is connecting through the USB interface.
8.3.4.1 USB Interface

See 8.3.2 on how to connect to the unit using the USB Interface.
Type the following command to list the currently assigned IP addresses:
app>net ipconfig
8.3.4.2 Nevion Detect

If you are not able to connect through the USB Interface, you may use the Nevion Detect software.
This software may be found on the Nevion Product CD (version 2.20 and newer), or by contacting
Nevion Support (see Section 2.4). An User’s Manual is also included.
The Nevion Detect software detects devices by sending broadcast messages that the TNS544 and
other Nevion devices will recognize and reply to with some essential information. The PC running
Nevion Detect may be on a totally different subnet than the TNS544, such that the device will be
discovered regardless of IP addresses and IP submasks.
Warning: Some Ethernet equipment might block broadcast traffic. Con-

nect your PC directly to the TNS544 to avoid this.
Note: It is possible to avoid that the TNS544 is detected by the Nevion

Detect software. See Section 9.4.4.1.1 for details on how to do this.
44
WEB Interface 45
9 WEB Interface
The TNS544 is entirely controlled through a WEB interface using the web browser’s Flash plugin.
After log-in the main status page appears displaying an overall view of the device functionality
and status. It also displays a number of tabs giving access to all functional controls of the device.
This chapter goes through the different GUI pages used to control the TNS544 and get status in-
formation.
9.1 Login
Access the TNS544 by entering its IP address in the address field of your favourite browser. When
accessing the TNS544 the first time, the progress bar (Figure 9.1) should appear while the Flash
application is loading from the device.
Figure 9.1 Flash application loading
When the loading of the Flash application is finished, the login window (see Figure 9.2) is dis-
played. Type the username and password to enter the GUI application. The default passwords
are listed in Section 8.2.
Figure 9.2 GUI login window
The login dialogue has an option “Save password”, which makes the browser store the username
and password in a cookie and use them as default values at next login.
46 WEB Interface
9.2 Status header

After successful login the start page is shown. The top part of the page (shown in Figure 9.3) is
called the status header, while the bottom part of the page (shown in Figure 9.4) is called the status
footer.
Figure 9.3 The status header
Figure 9.4 The status footer
In the status header the product name is shown on the left hand side, along with the configurable
product label, see Section 9.4.1.
The status header displays an alarm indicator showing the overall alarm status of the device. The
colour of the indicator shows the highest level alarm currently active in the unit. It is green if no
alarm is active. Other possible colours are described in Appendix E.
Several items are presented in the right corner/section of the header. Starting from the left:
• A text showing the current user name.
• A button to log out from the GUI.
• A button to switch current user level.
• The Nevion logo.
• A button for minimising the header. Using this hides a lot of the header information and
gives more space for the rest of the page.
In the status footer the following items are present from left to right.
• The current software version
• The name of the current configuration, if any. See Section 9.4.1 for details on how to
configure this.
• The local device time.
• An activity indicator.
Note: The activity indicator shows one box for each request being
processed by the unit. Each box may change from green to red if ex-
cessive time elapses during the processing. During normal operation, no
squares should turn red. If squares start turning red there might be a problem with
the communication between the device and the computer, or the device may be
busy. If the device has not responded to a request within 20 seconds, the indicator
turns yellow. If no response has been received after 40 seconds, it turns red.
WEB Interface 47
A tab bar is located beneath the status header. The exact number of tabs and tab labelling depends
on the units operational mode and licences. Clicking a tab will open the corresponding page with
a navigation pane to the left as shown in Figure 9.5. This pane is used to navigate between sub-
pages of the tab.
Figure 9.5 Status navigator
Note: The navigator can be collapsed to economise on screen space. Click

the vertical grey line with two small arrows to the left of the navigator.
9.3 Status
The status page presents an overview of the device operational status as well as a log of alarm
events.
There are two sub-pages within the status page.
Current Status
Indicates the running status of the device.
Alarm Log
Presents the device alarm log and provides operations for clearing the log or exporting it as
a comma separated value file (.CSV).
9.3.1 Current Status
This page displays the current status of the device. It consists of a block diagram illustrating the
device with its input and output ports, an overview of the currently active network interfaces and
a list of currently active alarms.
Block Diagram
The block diagram provides a compact view of the unit status. It shows:
• The name of the functional units of the device.
• The name and alarm status of each input/output port.
• The status of non-I/O port related alarms.
The alarm status is shown with colours indicating the severity of the alarm. The various
severities and colours used are described in Appendix E.
48 WEB Interface
Figure 9.6 Current status
Access to additional information pertaining to the various ports of the block diagram is pro-
vided by hovering the mouse pointer over the port within the diagram. The port represen-
tations in the diagram also act as shortcuts to the corresponding configuration page for the
port. The shortcut is activated by clicking on the port in the diagram.
If an input switch is defined, it is shown in the status diagram as a box inside the device block
in front of a MUX block. The block shows the ports that are members of the switching group,
and the currently selected port. Clicking the switch block will take you to the configuration
page for the switch.
Right-clicking the status block diagram top bar offers a shortcut to clear device statistics pa-
rameters. Selecting Reset device statistics brings up a dialogue where you can select which
information to clear.
Current Alarms
The bottom part of the page shows the currently active alarms. Some alarms may contain
several sub-entries that are displayed by clicking on the arrow in front of the entry’s descrip-
tion. The severity of each alarm is represented by an error indicator (visually similar to a
LED). The colour of the indicator represents the severity level configured for the specified
alarm. The various severities and colours used are described in Appendix E.
The Current Alarms table contains six columns:
Description
Description of the alarm condition.
For sub-entries, the extended index is shown in brackets. To the left is an indicator visualising
the severity of the alarm. The indicator has a tool-tip providing a textual description of the
alarm severity.
WEB Interface 49
On Time
The time when the alarm was raised.
Alarm type
Category of the alarm, i.e. Port, System, Switch etc.
Source
This identifies the source of the alarm. For port alarms, this is a reference to the specific
port raising the alarm. This field has a tool-tip showing the subid1 and subid2 values for the
alarm.
Subid1
Reserved for future use in multi-slot chassis and is always set to 1 in the TNS544.
Subid2
The device or port to which the alarm relates. The value is zero for alarms that are
related to the device rather than to a specific port. Values of 1 and up reference specific
ports.
Alarm ID
Each alarm condition has an associated numerical alarm ID.
Details
An optional string to provide more alarm information in human readable form. The format
of this string depends on the alarm type. Hovering the mouse over this field produces a
tool-tip displaying the full text.
A detailed overview of alarm conditions is given in Appendix E.
9.3.2 Alarm log
Figure 9.7 Alarm log
The alarm log shows every alarm that has been triggered since the last time the alarm log was
cleared.
50 WEB Interface
The table consists of the same columns as the Current Alarms table, but does not show details by
default. You can change which columns to show, including the details column, in Section 9.4.2.4.
Additionally a column named Off Time shows the time the alarm condition was cleared. Rows
will not have the Off Time set if the alarm is still active.
Each row provides additional information via a tool-tip shown when hovering the cursor over the
row. The tool-tip entries are:
Sequence #
A number identifying this specific alarm instance. This number is incremented each time an
alarm condition is raised.
SubID 1
The primary numerical index of the alarm instance. This index is reserved for future use and
is always set to 1 in the TNS544.
SubID 2
The secondary numerical index of the alarm instance. When the alarm is of type Port alarm
this index contains the port number for which the alarm was raised. Other types of alarms
may use this index to identify a sub module, but normally it is set to 0.
SubID 3
The tertiary numerical index of the alarm instance. The use of SubID 3 depends on the type
of alarm. Some of the Port type alarms use this index to signal the PID value or Service ID
for which the alarm was raised. For example, if the CC Error of a PID is raised then the PID
value is given by SubID 3.
Details
An optional string providing more information about the alarm in human readable form.
The content and format of this string depends on the alarm type.
Beneath the alarm table is a caption showing the total count of alarms currently stored in the alarm
log.
To the right of the table are three buttons and a check box.
Clear Alarm Log

Clears all alarms from the alarm log.
Export to File
Saves the alarm log to a comma-separated value (.CSV) file. The button opens a file dialogue
where the user can choose the destination to save the file on the computer.
Export to Browser
Opens the complete log in a new browser window, showing the alarm log as a comma-
separated value list. The format of this list is a text file (not HTML or XML).
Enable updates
This check box can be unchecked to stop the log from scrolling if new alarms are triggered
while watching the log.
The alarm log is stored in non-volatile memory, so the content is kept even if the unit is rebooted.
WEB Interface 51
The log is circular. Events occurring after the maximum number of entries has been reached over-
write the oldest entries in the log. The maximum number of stored entries is 10000.
9.4 Device Info

The device info page contains all the information and settings that are not related to a single input
or output port. It is divided into multiple sub pages accessed via the navigation list to the left. In
the list of physical interfaces in the navigation list, the currently active interface is shown in bold.
See Figure 9.8.
Figure 9.8 Device Info navigator
The exact layout of the navigator depends on the resources and features currently available in the
device.
9.4.1 Product info
The product info page contains general device information.
Name
Configures the current user defined name of the unit. This parameter, together with the
management network parameters are used as device identifiers and remain untouched if the
unit configuration is changed by loading a different configuration file. See Section 9.4.6.
The device name is shown in the web GUI status header (see Section 9.3.1), and in the web
browser title bar to facilitate identification of each device.
Inventory ID
Configures the current user defined inventory ID of the unit. This parameter, together with
the management network parameters are used as device identifiers and remain untouched
52 WEB Interface
Figure 9.9 Product Information
if the unit configuration is modified. It is only intended as a label/tag and will not affect the
operation of the unit.
Configuration ID
Configure a user defined name for the current configuration of the unit. This name will, if
given, be displayed in brackets after the unit name in the status header as shown in Figure
9.3. The Configuration ID does not, as opposed to the Name and Inventory ID fields, remain
untouched when loading a new unit configuration. Loading a new unit configuration will
change the Configuration ID. See Section 9.4.6 on how to load a new configuration.
Product name
Displays the name of the product as designated by Nevion.
Serial number
The serial number of the device.
Software version
The version of the software currently installed on the device. The software version is given
by the following syntax:
<major_version>.<minor_version>.<patch_version>
The convention for the SW version numbering is as follows:
major_version
Incremented for significant SW changes.
minor_version
Incremented for minor changes. The minor version number is even for official retail
releases and odd for beta releases.
patch_version
If minor_version is even, patch_version gives the patch level of that version. A patch
WEB Interface 53
level of zero means the SW is built on the latest code base, an even patch_version means
this is a released SW patch on a previous release. An odd patch_version means that this
is a test version. If minor is odd, this is a beta version, and the patch_version simply
gives the build number.
Software build time

Reports the time of which the current release image was built.
Device up time
The amount of time that has passed since the device was last reset.
Internal temperature
This shows the current internal temperature of the unit in degrees Celsius and Fahrenheit.
Fan speed
This bar chart shows the current speed of the device fans relative to full speed.
Flash Power LED button

The Flash Power LED button activates flashing the green power LED on the device in ques-
tion. This is useful for identifying which device is currently being configured. Each click of
the button extends the blinking period by five seconds up to a maximum of about 30 seconds
of blinking.
9.4.2 Alarms
The Alarms page is shown in Figure 9.10:
Figure 9.10 Alarm configuration
This page displays the status of all system alarms and allows the user to program the severity
of these alarms. Global alarm configuration is performed on this page, as well as alarm relay
configuration and alarm log configuration.
It gives access to the following sub pages:
54 WEB Interface
• Device Alarms
• Global configuration
• Relay and LED configuration
• Alarm Log Settings
9.4.2.1 Device alarms
The page shown in Figure 9.10 provides the administrator with an interface to view the status and
configure the behaviour of all alarms related to the system. At the top the Reset Alarm Counters
button allows resetting all alarm counters simultaneously.
The page is divided into two parts. On the left is a tree that shows all the alarms. The colour of
the folder icon and the specific indicator represents the current status of the alarm. The text to the
right of the tree shows the currently configured severity of the alarm.
The right hand side of the page displays the Alarm Details field when an alarm is selected:
Alarm ID
The internal numerical ID of the selected alarm.
Alarm
Title of the alarm.
Description
Brief description of the condition of the alarm.
Severity
A configurable option defining the severity of the alarm. Options in the pull-down box range
between Filtered (meaning ignored) to Critical. The text in brackets represents the default
setting.
Alarm turned on
The number of times the alarm has transitioned from off to on since last reset of the alarm
counter.
Error count
Not used.
’Reset Counters’ button

When clicked, clears the alarm counters for the current alarm.
The right-click context menu of the device alarm page provides an option to reset the counters of
all the alarms in the Device Info tree.
WEB Interface 55
9.4.2.2 Global configuration
Figure 9.11 Global alarm configuration
This page provides an interface to configure globally the behaviour of all alarms. By default ports
use the global configuration settings but each port alarm can be configured individually to over-
ride these settings.
For each alarm a custom severity level can be configured. In addition the alarms can be omitted
from the alarm log and trap transmission.
Edited rows are highlighted until changes have been applied.
Tip: For the Log and Send Trap columns, you can quickly select/deselect
all items by right-clicking on the header fields in the columns.
9.4.2.3 Relays and LED

This page lets the user configure the alarm severity level that shall turn the relays and alarm LED
on. The behaviour of Alarm relay 1 and Alarm relay 2, and the Alarm LED may be configured
individually for each alarm severity level. Note that the Alarm relay 1 and the Alarm LED will
always be enabled for alarm severity level Critical, as indicated by the disabled check boxes in the
Relay and LED level triggers field. The current state of the relays and LED is indicated inside the
associated brackets.
The General purpose input field allows the user to enable pin 9 of the alarm D-SUB connector as
a remote reset input. See Section 7.6.1. GPI status indicates if the input signal is active.
For further details on the physical relays refer to Section B.5.1.
The Virtual Relays field shown in Figure 9.12 also includes settings for the so-called virtual relays.
These are programmable status indicators that can be set to react to any specific alarm condition.
In the simplest case you may want to enable a relay in case a specific alarm ID turns up. In another
case you may want to enable a relay if a specific alarm turns up on a given port.
56 WEB Interface
Figure 9.12 Relays and LED configuration
Each relay status are exported on SNMP. Activation of a virtual relay also generates a specific
alarm, named "Virtual alarm relay activated" (ID=169).
The key element in the settings of the virtual relays is the Expression value. The expression is
very close to SQL in syntax and specifies when the relay should be activated. The behaviour is as
follows for each virtual relay:
1. Each active alarm event is evaluated against the Expression for the virtual relay (if en-
abled).
2. If the expression evaluates to true, the Count value is increased by 1. You can at any time
see the current count value. The Count value simply tells you how many of the current
(active) alarm events in the unit that matches the expression.
3. If the count value is larger than or equal (>=) to the Count Thresh. value the relay is
activated.
The expressions are validated before they are accepted by the unit. Table 9.1 shows the field
values you may enter in an expression.
Table 9.1.a Legal field values to use in expressions
Field name Extracts from event: Type Sample expression

id Alarm ID Number id = 169
text Alarm text Text text = ’Defective fan’
type_num Type number Number type_num = 13
WEB Interface 57
Table 9.1.b Legal field values to use in expressions
Field name Extracts from event: Type Sample expression

type_text Type text Text type_text = ’port’
sev Severity (number 2-6) Number sev = 6
details Alarm details (text) Text details = ’PID 113’
subid1 Alarm subid1 value Number subid1 = 1
port Synonym for subid2 Number port = 2
service Synonym for subid3 Number service = 102
pid Synonym for subid3 Number pid = 2000
In the expressions you may enter parentheses to group sub-expressions together. Together with
the supported list of operators this gives great flexibility in constructing advanced “match” pat-
terns.
Table 9.2 summarises the operator types you are allowed to use. Please note that the examples
below are used for illustration purposes only. For example, the plus and minus operators may not
be very useful in practise, but they are included in this table for completeness.
Table 9.2 Legal operators to use in expressions
Operator Description Sample

= Equal id = 169
!= Not equal id != 169
AND Logical AND id = 169 AND port = 2
OR Logical OR id = 169 OR id = 200
IN Set operator. Returns true if left-hand part is included in set to the right. id IN (169,200,201)
+ Addition id + 9 = 169
- Subtraction id - 8 = 160
* Multiply id * 10 = 100
/ Divide id / 20 = 8
> Greater than id > 100
< Less than id < 90
>= Greater than or equal id >= 100
<= Less than or equal id <= 100
Some examples are given in Table 9.3.

Note the last example in the table: Here the count threshold value must be set to 2 to get the
expected behaviour. This is because the expression entered matches two different alarm events
(port=1 or port=2), and in order to match them both two matches are required in the global alarm
list.
58 WEB Interface
Table 9.3 Expression examples
Task Expression Count threshold value

To generate an alarm when any alarm with id = 200 1
ID = 200 turns up (independent on source)
To generate an alarm when alarm with ID = (id = 200) AND (port = 1) 1
200 turns up on port with ID = 1 (subid2 =
1)
To generate an alarm when alarm with ID = (id = 200) AND ((port = 1) OR (port 2
200 turns up on both port 1 AND port 2 = 2))
9.4.2.4 Alarm log settings
This page is used to set alarm log properties.
Figure 9.13 Configuring the alarm log
Log delimiter
This parameter is used when exporting the alarm log. It specifies the column separator char-
acter. The default value for the delimiter is ;. The character used may affect auto-importing
of the exported file into your favourite tool used to inspect the file content.
Columns
Each of the columns in the alarm log table has a checkbox. Columns that are selected are
shown on the alarm log page.
9.4.3 Time Settings
The time settings page lets the user configure time zone, the source for synchronising the inter-
nal device time clock and set the internal clock in case of failure of all external sources of clock
synchronisation. The main use of the device time is stamping the entries of the alarm log.
The page consists of several parts. Top left is the General box, containing the following parameters:
Current time
The current time as reported by the device.
Time zone
Drop-down list to configure the time zone of the unit.
WEB Interface 59
Figure 9.14 Time Settings
Status
The status of the time synchroniser.
Active
The time source currently in use by the time synchroniser.
The Manual Adjust Time field allows the operator to set the time. The manually configured time
will only be used when no other time sources are configured in the Prioritised time sources list.
The Timesource prioritisation field contains two lists showing configured time sources. Disabled
time sources are greyed out. Enabled time sources are shown with an indication of the time source
status. The list to the right shows time sources that are defined but not used by the time synchro-
niser. Enabled time sources may be moved to the leftmost list by using the arrow-left button, and
back again by using the arrow-right button. Time sources in the left hand list are used by the time
synchroniser to set the time. They are listed in prioritised order; the source with the highest prior-
ity at the top. The order of priority can be altered by clicking an item in the list and using the up or
down arrows to the left of the list to increase or decrease, respectively, the item priority. The time
synchroniser will use the time source with the highest priority whose status is “OK” (represented
by a green indicator).
To add a time source to the system, click the “Add Timesource” button, which brings up the dialog
shown in Figure 9.15 with the following fields:
Timesource type
SNTP
Time source retrieving time from an SNTP server.
60 WEB Interface
Figure 9.15 Time Settings - Add time source
Server address
Specify the server IP address here.
TDT TOT or STT

Time source retrieving time from DVB TDT, DVT TOT or ATSC STT time tables on a
port.
Input source
Lists ports that can be used as time sources with the selected time source type
(Figure 9.15. Multiple entries can be selected to add more than one time source.
For switched inputs, you may select the time source to get time from the input
switch group, which will make the time source retrieve the time from the currently
active input in the switch.
To remove time sources, Select them in the list and click the “Remove Timesource” button. Time
sources for dynamic ports such as IP inputs and Switch inputs, are automatically removed if the
dynamic port is removed.
Located below the lists is also a field to define the maximum allowed time interval between updates
from the currently used time source. Exeeding this interval the source is considered “Not OK” and
the synchroniser selects the next source in the prioritised list.
Upon selecting a time source, the Timesource Details box at the bottom right of the page pro-
vides additional details relating to the selected time source. Depending on the type of time source
selected the box may contain some or all of the following parameters:
Active
A checkbox to enable or disable the time source. Disabled time sources are never updated.
Time sources configured and present in the prioritised list must be removed before they can
be disabled.
IP address
Specifies the IP address of an SNTP time server source to poll for updates.
WEB Interface 61
Type
Type of time source selected. The sources are product dependent, but SNTP is always avail-
able.
Last updated time

The most recent time value received from the time source.
State
The current state of the time source.
Reference
Provides the time reference source address of accessed time source.
Reference stratum
Indicates the hierarchy level of the current time source. The master reference is at stratum 0
(highest).
Reference status
Indicates if the time source is currently governed by a time source at a higher stratum.
Reference precision
The expected timing accuracy of the current time source.
9.4.3.1 Daylight saving time

Daylight saving time (DST) can be set in the field below the Manual Adjust Time field. The effect of
having it enabled is that the local time on the unit is adjusted for daylight saving time. The current
time will show the daylight saving adjusted time, with correct UTC offset. This will mainly have
an effect on alarm log entries and reading the time from the GUI. When enabled, there are four
DST modes to choose from:
Europe
Standard European settings. Daylight saving time starts on the last Sunday in March at 1AM
UTC, and ends on the last Sunday in October at 1AM UTC.
USA
Standard USA settings. Daylight saving time starts at 2AM local time on the second Sunday
in March, and ends at 2AM local time on the first Sunday of November. This setting does not
take into account the exceptions where daylight saving time is not observed, such as Arizona,
Hawaii, Puerto Rico, American Samoa, Guam, Northern Mariana Islands and the United
States Virgin Islands. These locations should simply have daylight savings time disabled.
Manual dates
Manual dates which can be inputted in the autumn and spring fields that appear when this
option is chosen. Will only occur on these times, and need to manually be updated in order
to change the following years. If both the manual dates has passed, the time is set to not be
in daylight saving, even if the last date was a spring date. The number of minutes to adjust
the time for daylight savings can be set in the Offset in minutes field.
Manual recurring
Gives drop-down lists to input a rule, such as “First Sunday in February 02:00”. This will
62 WEB Interface
set dates based on the selected input, and happens each year on that day. The number of
minutes to adjust the time for daylight savings can be set in the Offset in minutes field.
If daylight saving is enabled, a status field showing the current time status with daylight savings
appears. If daylight saving is disabled, this field is not visible. The status field shows the following
information:
Current time
The current time as reported by the device.
Currently in summer time

Whether or not the current time is in daylight saving time.
Setting clock in
Countdown to the next time time will be adjusted to or from summer time. If it displays “No
change set to occur”, the mode is likely set to Manual dates, with the two set dates having
passed, or minutes offset being set to 0 minutes.
Minutes DST offset

Number of minutes the clock is set to change by for daylight saving.
Next spring change

The spring date for the next daylight saving change.
Next autumn change

The autumn date for the next daylight saving change.
9.4.4 Network
Figure 9.16 Network status
This page presents status information about network interfaces, including virtual (VLAN) inter-
faces, present on the device. The management interface is always present, and bold characters
indicate the web management interface connection. An interface shown in grey colour means
that the interface is disabled. There may be physical interfaces on the unit that are not shown in
this table as the availability of each interface may vary with the installed software licences and
operational mode.
WEB Interface 63
Interface
A label identifying the interface. If it is a physical interface with virtual interfaces attached to
it an arrow is shown. Clicking this arrow will expand/collapse the list of virtual interfaces.
IP Address
The IP address configured for this interface.
Link Speed
The current link speed detected for this interface. Applicable to physical interfaces only.
Duplex Mode
The duplex mode detected for this interface, half or full duplex. Applicable to physical in-
terfaces only.
TX Bitrate
The bitrate currently transmitted through this interface. Applicable to physical interfaces
only.
RX Bitrate
The bitrate currently received through this interface. Applicable to physical interfaces only.
Enabled
Shows whether the interface is currently enabled.
Data
Shows whether data traffic is currently enabled for this interface.
Management
Shows whether management traffic is currently enabled for this interface.
9.4.4.1 Interfaces
Each available network interface has an entry in the Navigator list. Selecting an interface brings
up pages where it is possible to configure the interface and view its status. Accessible parameters
vary with the interface selected since the functionality of the available interfaces are not necessarily
identical.
9.4.4.1.1 Main
Figure 9.17 Main IP settings
64 WEB Interface
This page provides the main configuration settings for the physical interface.
Caution: Modifying the settings of the interface you are currently using
for the GUI application may cause loss of contact with the unit. Make sure
you will still be able to contact the unit before applying changed settings.
9.4.4.1.2 Interface Settings
Enable interface
Enables/disables the interface. It is not possible to disable the currently used management
interface.
Media Select
Provides a choice between network port Data 2 and the SFP module for the second data
interface. Select RJ-45 to use the data port marked Data for data traffic. Select SFP to use the
SFP module for data traffic.
Speed/duplex mode
The speed and duplex mode of the interface. The Auto setting enables automatic speed and
mode negotiation for the Ethernet link. This option is not available for SFP interfaces.
Note: Modifying the default settings of interface duplex to anything other

than auto can cause unpredictable results unless all peer systems accessing
the port use similar settings. For more technical information regarding auto
negotiation and duplex mismatch, refer to the Wikipedia duplex mismatch article
(http://en.wikipedia.org/wiki/Duplex_mismatch).
Automatic IP address
Enables automatic IP address assignment using DHCP. This option requires that a DHCP
server is present on the network on which the device is connected.
9.4.4.1.3 DHCP Settings
Hostname
The DNS hostname of the interface. This name is sent to the DHCP server with a request to
register it at the DNS server. If the name registers correctly, the fully qualified domain name
of the interface will be the hostname pluss the domain name assigned by the server.
Domain
Optional field where wanted domain name can be specified. Normally the DHCP decides
the domain name for a client, the DHCP server must be set up specifially to allow a client to
select a domain name.
Renew button
Press button to renew address now. Renew is done by sending a request for renewal of lease
of existing parameters, using uni-cast to DHCP server.
WEB Interface 65
Rebind button
Press to rebind address. Rebind is done by broadcasting a request for the same IP address as
previously used.
9.4.4.1.4 DHCP Status
DHCP status
Shows the current state of the DHCP client (RFC2131, Figure 5).
Possible values are:
Disabled
DHCP is not turned on.
Selecting
Client is broadcasting Discover messages and checking for offers from answering DHCP
servers. Normally the client should immediately receive and answer and switch to
bound state.
Bound
Client has received IP settings and is ready for use.
Renewing
Client is uni-casting request to leasing server to renew previous lease.
Rebinding
Client is broadcasting requests to re-bind to previously assigned address.
Checking
Client is evaluating wether offered IP address is already in use on network.
Backing off
Client received a nack from the server.
DHCP server
The IP of the selected server.
IP address
The IP address assigned to this interface by the server.
Subnet mask
The subnet mask assigned to this interface by the server.
Gateway
The IP address of the gateway to use, assigned by the DHCP server.
DNS servers
Prioritized list of DNS servers to use assigned by the DHCP server. See Section 9.4.4.2 for
manual configuration of DNS server addresses.
66 WEB Interface
Note: If the DNS server is not located on a sub-net local to the unit, it
may be required to configure the routing table to route DNS requests to
the correct network interface.
Remaining lease time

Time till the IP address must be renewed.
DHCP status info icon

More details on the DHCP client is available on a tool-tip if you hoover over the info icon
next to the “DHCP status” parameter. The fields here are:
Domain
The domain name assigned by the DHCP server. The fully qualified domain name of
the interface is <hostname>.<domain>
Lease time
The duration of the address lease, specified by the DHCP server.
Renew time/Time to renewal

The renew time specified by the server. Normally the client should transmit a renew
request after this time.
Rebind time/Time to rebind

Time specified by server for re-bind.
Messages transmitted/received
Number of messages sent and received by the DHCP client.
Last transmission ID
ID used on last DHCP message transmitted.
9.4.4.1.5 Manual IP Settings
IP address
IP address of the interface.
Subnet mask
The subnet mask of the interface.
Gateway
The default gateway address for the interface.
9.4.4.1.6 Interface Status
MAC address
The Ethernet Media Access Control (MAC) address of the interface.
Link speed
Speed of current connection.
WEB Interface 67
Duplex mode
Shows duplex of current connection.
9.4.4.1.7 Detect Settings
Detect configuration
Applies to the Control interface, only.
These two boxes enable read and write attributes of the Nevion Detect IP assignment server
module. This server is a stand-alone PC application that can be used to discover Nevion
devices on a local network and assign IP addresses to them.
Enabling the Read option makes the TNS544 visible for the Nevion Detect on the LAN. If the
Write option is enabled the IP address of the TNS544 may be configured using the Nevion
Detect. These options do not affect the operation of the device from the management appli-
cation Nevion Connect.
9.4.4.1.8 Alarms
Alarms related to the interface are listed on the Alarms page. Clicking an alarm opens the field to
configure the alarm. Please see Section 9.4.2 for alarm configuration details.
Figure 9.18 Network interface alarms
At the top of the page two radio buttons are provided to select between displaying error count or
error severity. In addition all alarm counters related to this interface may be reset.
9.4.4.1.9 Advanced
This sub-tab allows configuring advanced IP settings of the interface.
Figure 9.19 Advanced IP settings
68 WEB Interface
Allow ping response

Check this box to filter incoming ICMP messages. If this option is not enabled the device will
not answer ping requests to this port.
Allow management traffic

Tick this box to allow management traffic on this interface. It is not possible to disable this on
the dedicated management interface or on the interface you are currently using for management.
Allow data traffic

Tick this box to allow data traffic on this interface. It is not possible to enable data traffic on the
management interface.
Multicast router
This parameter is not shown in the management interface page.
The IP address of the multicast router. The address here is used in conjunction with the Use
multicast router option in the "IP Output" page, Section 9.6.3.1.
IGMP version
This parameter is not shown in the management interface page.
The preferred IGMP version to use. If fixed is selected the unit will keep trying to use the
selected version even if it is not supported by the network.
9.4.4.1.10 Status
Figure 9.20 Interface Status
This page shows detailed status and error information on the selected physical interface. Different
types of interfaces support different status and error parameters; not all parameters listed will be
shown for all interface types.
The Ethernet Status field:
WEB Interface 69
Link speed
The detected link speed of the interface.
Duplex mode
The detected current duplex mode of the interface. The duplex mode indicates whether data
may flow in one direction (half duplex) or bidirectionally (full duplex).
The following parameters are available for both received and transmitted packets:
bitrate
The total bitrate received/transmitted.
load
Interface load, measured relative to max speed.
Total packets
The total number of IP packets received/transmitted.
Good packets
The number of IP packets received/transmitted containing valid CRCs.
Multicast packets
The number of IP multicast packets received/transmitted by the interface.
Broadcast packets
The number of broadcast packets received/transmitted.
Octets
The number of octets received/transmitted
The Errors field:
CRC errors
Number of packets received with CRC errors.
Alignment errors
Number of packets detected with alignment errors (non-integer number of bytes).
Receive errors
Number of erroneous packets received.
Missed packets
Number of packets missed.
Link symbol errors

Number of link symbol errors detected.
Carrier extension errors

Number of carrier extension errors detected.
Receive length errors

Number of packets with invalid size.
70 WEB Interface
The SFP Info field is only shown if the SFP interface is active. It displays information provided by
the SFP module installed.
9.4.4.1.11 VLAN
Figure 9.21 VLAN configuration
This page is only shown on interfaces with VLAN (virtual interface) support. The page allows
adding, removing and editing virtual interfaces (VLAN) using the selected physical interface.
Current VLANs interfaces are shown in the grid on the left, and parameters for each interface
are edited by selecting the interface in the grid first.
Once editing is finished, clicking the Apply button will commit all the changes. Hitting Refresh
will cancel all changes.
In addition to the Apply and Refresh buttons there are buttons to enable adding and removing
VLANs.
9.4.4.1.12 Main Settings
Enable interface
Enable/disable the virtual interface.
VLAN ID
The VLAN id of this virtual interface. Must be in the range 1-4094. All virtual interfaces on
one physical interface must have a unique id.
VLAN priority
The VLAN priority of this virtual interface. Numers 0 to 7 are valid. For further information
on VLAN priority usage, see reference [7].
Automatic IP address
Enables automatic IP address assignment using DHCP. This option requires that a DHCP
server is present on the network on which the device is connected.
WEB Interface 71
9.4.4.1.13 Manual IP Settings

IP address
The IP address of the virtual interface.
Subnet mask
The subnet mask of the virtual interface.
Gateway
The gateway address to use for the virtual interface.
9.4.4.1.14 Advanced Settings

Enable data traffic
Checked box enables the virtual interface to allow video data traffic. Not shown for dedicated
management interface.
Enable management traffic
Checked box enables the virtual interface to allow management traffic.
Enable ping
Checked box enables the virtual interface to respond to ping messages.
Multicast router
The multicast router for this virtual interface. Only visible if multicast is allowed.
IGMP ver
Provides selection of the IGMP version to use. Not applicable to the "Control" interface.
9.4.4.1.15 DHCP settings and status

Please refer to Section 9.4.4.1.1.2 and Section 9.4.4.1.1.3 for a description of the parameters related
to DHCP, which are identical to the ones on the main tab.
9.4.4.1.16 SFP
The SFP tab is visible for the second network interface if this interface is set to use SFP. How to
enable the SFP is described in section 9.4.7.1 , provided the appropriate licence has been installed
.
Figure 9.22 The Device Info > Network > SFP tab
72 WEB Interface
The SFP tab gives access to three sub-pages: SFP Status, STM-1/OC-3 Config and E3/T3 Config.
The two configuration sub-pages reflect that separate configuration files are used to configure the
different SFP module types. For each module type the TNS544 stores a configuration file that
can be edited “off-line”. These pages are visible only if SFP configuration has been licensed. The
settings will not be committed to the module until writing of the file is expressly initiated.
The SFP Status page, shown in figure Figure 9.23, provides an overview of the module status. The
appearance of the status page and the range of parameters shown depend on the type of module
attached.
Figure 9.23 The SFP status page
The Module General Status field displays the status of the module as seen by the TNS544.
SFP Present
Indicates that the module has been detected by the TNS544.
Vendor
Shows the vendor name.
Revision
Indicates the module revision.
Date
Indicates the revison date.
WEB Interface 73
Part number
The module part number.
Transceiver type
The type of transceiver inside the SFP module. Only a limited range of transceivers is com-
patible with the TNS544.
Connector type
Indicates the network connector type.
Serial number
The serial number of the SFP module.
The Module <type> Configuration field shows the internal functional status as read back from the
module. The field heading will reflect whether a STM-1/OC-3 or an E3/T3 module is installed.
A discussion of the parameters shown is included in the Config pages description.
The Module (type) Alarms field is shown if the STM-1/OC-3 module is present and shows all
link related alarms settings of the module. Red indicates that the alarm has been raised.
TIM-P
Trace ID Mismatch (Path)
LOS
Loss of Signal
AIS_L
Alarm Indication Signal (Line)
RDI_L
Remote Defect Indication (Line)
UNEQ_P
Payload Label Mismatch (Path)
LOF
Loss of Frame
AIS_P
Alarm Indication (Path)
RDI_P
Remote Defect Indication (Path)
EED
Excessive Error Defect
LOP
Loss of Point
SD
Signal Degrade
74 WEB Interface
Refer to product specific documentation for further discussion of these parameters.

The Module (type) Link Status field is shown if the E3/T3 module is present and shows the status
of all link related alarm settings of the module. Red indicates that the alarm has been raised.
BV
Bipolar Violation
LCV
Line Coding Violation
LOS
Loss of Signal
RDI
Remote Detection Indication
WLD
WAN Loop Detected
EZ
Excessive Zeroes
PCV
P-bit Coding Violation
OOF
Out of Frame
LLD
Lan Loop Detected
LOL
LIU Out of Lock
CCV
C-bit Coding Violation
AIS
Alarm Indication Signal
SS
System Status.
Refer to product specific documentation for further discussion of these parameters.

The Module (type) Error Counters field displays errors as they occur, counted during a 15 minute
period. Es = Errored seconds, Ses = Severely errored seconds, Cv = Coding violations, Uas = Line
unavailable seconds
Current
The counter increments every time an error is detected, resetting every second.
WEB Interface 75
15mins
Displays the result of the previous 15 minutes counting interval.
Section
“Section” related error counts
Line
“Line” related error counts
Path
“Path” related error counts
At the page bottom is the Clear Module Statistics button. Clicking this will flush all error counters.
The STM-1/OC-3 Config page.
The STM-1/OC-3 module provides an optical interface for high speed data communications in
SDH or SONET networks. This page provides access to change the configuration settings of the
module. As shown in figure Figure 9.24 the page contains four fields to set operational parameters.
The Alarms and Error counters fields are identical to those described for the SFP Status sub-page.
Editing the configuration settings will alter the SFP configuration file stored in the TNS544, only.
Figure 9.24 The configuration page

for the STM-1/OC-3 SFP module
In the General field the main operational parameters are set.
STM-1/OC-3 present
Indicates if the module has been detected by the TNS544.
76 WEB Interface
Write to module
This box must be checked to allow the configuration file be written to the SFP module. If the
box is not checked the configuration file may still be edited without affecting the module. If
the box is checked the configuration file is written to the module every time the Apply button
is clicked.
Tx clock source
The transmitter clock may be internally generated, or derived from the received data stream.
Frame type
Select SDH or SONET, respectively, according to the accessed network.
Payload FCS (Frame check sequence)

Check this box to enable FCS error detection.
Disable interface
Not available.
Scrambler
Tick this box to enable the module internal scrambler. Must be ticked to successfully receive
scrambled network data.
Ethernet flow control

A tick enables flow control of Ethernet data from the TNS544 to the SFP module. Flow control
prevents data overflow in the SFP module buffer. Buffer overflow leads to data loss that
would go unnoticed until attempting to decode the data at the receiving end.
In the Fault Propagation field check boxes allow to select which network fault(s) shall cause shut-
down of the Ethernet data flow:
LOS
Loss of signal
AIS
Alarm indication signal
RDI_P
Remote defect indication
In the Thresholds field bit error rate measurements indicate an estimate of the network link quality.
The check boxes allow selection of pre-defined threshold BER values to raise alarms. For further
details refer to the vendor SFP user manual.
SOH SD
Section Overhead, degraded Signal Defect
SOH EED
Section Overhead, Excessive Error Defect
POH SD
Path Overhead, degraded Signal Defect
WEB Interface 77
POH EED
Path Overhead, Excessive Error Defect
The Taffic Queues field allows mapping of network traffic queues to VLAN priorities. For infor-
mation on VLAN priority usage refer to [7].
To aid troubleshooting while changing configuration the Module Alarm and Module Error Coun-
ters fields of the status page are replicated here.
At the bottom of the page are three buttons:
Apply
Writes changes to the SFP configuration file. Also initiates writing the configuration file to
the module if the Write to module box has been ticked.
Refresh
Cancels changes that have been entered.
Reset Factory Defaults

Only active if the Write to module box has not been ticked. Clicking this button returns the
module to factory default settings but will not affect the settings of the configuration page.
The status of the SFP module is at all times displayed in the SFP Status sub-page.
The E3/T3 Config page.

The E3T3 module provides an electrical interface for high speed data communications in E3 or
T3 networks. This page provides access to change the configuration settings of the module. As
shown in figure Figure 9.25 the page contains four fields to set operational parameters. Editing
the configuration settings will alter the SFP configuration file stored in the TNS544, only.
E3/T3 present
Indicates if the module has been detected by the TNS544.
Write to module
This box must be checked to allow the configuration file be written to the SFP module. If the
box is not checked the configuration file may still be edited without affecting the module. If
the box is checked the configuration file is written to the module every time the Apply button
is clicked.
Interface type
Click the appropriate button for the network used.
Module protocol
Allows selecting the desired data link protocol for the network; HDLC (High Level Data Link
Control), GFP (Generic Frame Protocol) or cHDLC (Cisco extension to HDLC).
Line type
Line protocol selection. Choices vary according to the interface type and data link protocol
selected.
Tx clock source
The transmitter clock may be internally generated, or derived from the received data stream.
78 WEB Interface
Figure 9.25 The configuration

page for the E3/T3 SFP module
Line code
Must be HDB3 for an E3 interface. Select between B3ZS and AMI for a T3 interface.
Line length
Only applicable for a T3 interface. Allows the output signal to be adjusted according to the
line length to reach the termination point.
FEAC
Far end alarm and control indication. Only applicable for a T3 interface using G.751 line
protocol.
VCAT overhead
Only applicable when using the GFP data link protocol. VCAT allows arbitrary grouping of
VCAT members (STS1 or STS3c timeslots) to accommodate any bandwidth.
Payload FCS (Frame check sequence)

For error detection. Only applicable when using the GFP data link protocol.
Scrambler
Only applicable when using the GFP data link protocol. Tick this box to enable the module
internal scrambler. Must be ticked to successfully receive scrambled network data.
WEB Interface 79
GFP keep alive

If enabled, sends 2-3 keep alive messages per second. Enable this parameter if Loss of Frame
(LOF) indication is frequently encountered. Generally relevant to older equipment types.
Only applicable when using the GFP data link protocol in a T3 interface.
Ethernet flow control

A tick enables flow control of Ethernet data from the TNS544 to the SFP module. Flow control
prevents data overflow in the SFP module buffer. Buffer overflow leads to data loss that
would go unnoticed until attempting to decode the data at the receiving end.
In the Fault Propagation field check boxes allow to select which TDM network fault(s) shall cause
shut-down of the ethernet data flow:
LOS
Loss of signal
AIS
RDI
LOF
Loss of frame
FEAC
Far end alarm and control
Whether or not RDI, LOF and FEAC are applicable depends on Interface type, Module protocol
and Line type settings.
In the Loss of Signal Behaviour field check boxes allow selecting which TDM condition shall send
an LOS indication to the Ethernet interface:
LOS
Loss of signal
LOC
Receive loss of lock
AIS
RDI
The Taffic Queues field allows mapping of network traffic queues to VLAN priorities. For infor-
mation on VLAN priority usage refer [7].
To aid troubleshooting while changing the configuration the Module Alarm and Module Error
Counters fields of the status page are replicated here.
At the bottom of the page are three buttons:
80 WEB Interface
Apply
Writes changes to the SFP configuration file. Also initiates writing the configuration file to
the module if the Write to module box has been ticked.
Refresh
Cancels changes that have been entered.
Reset Factory Defaults

Only active if the Write to module box has not been ticked. Clicking this button returns the
module to factory default settings. This will not affect the settings of the configuration page.
The status of the SFP module is at all times displayed in the SFP Status sub-page.
9.4.4.2 DNS Settings
Figure 9.26 DNS settings
The DNS settings page lets you configure a main and secondary DNS server IP address. The DNS
server is used to map names to IP addresses.
9.4.4.3 IP Routing
Figure 9.27 IP Routing
The IP Routing table lets the user configure IP routing rules for the unit. These rules tell the unit
which interface to send IP traffic to, based on the destination IP address of the traffic.
Destination
The destination IP address to use for matching against this routing rule.
WEB Interface 81
Netmask
The subnet mask to use for matching against this routing rule.
Gateway
The IP destination to send a packet to if the destination address of the packet is on a different
subnet than the destination interface.
Interface
IP packets matching this rule will be sent through this interface.
Metric
The metric of the routing rule. If more than one rule matches a destination address the rule
with the lowest metric will be used.
When an IP packet is sent from the unit the destination address of the packet is matched against
the configured routing rules. If the destination address matches one or more rules the rule with
the lowest metric will be used. The packet will then be forwarded to the interface determined
by this rule. If the destination address is on a different subnet than the configured interface the
packet will be sent to the gateway determined by the rule.
Below the table is a checkbox where the user can Allow IP forwarding. If enabled incoming TCP
packets that are not addressed to the unit will be forwarded to an interface according to the routing
rules. The receiving interface must have management traffic enabled to forward TCP traffic to a
different interface.
Note: Modifying the IP routing rules may cause loss of contact with the
unit. Make sure you will still be able to contact the unit with the new
settings before applying the changes.
9.4.4.4 TXP Settings
Figure 9.28 TXP Settings
TXP is a Nevion proprietary HTTP/XML based protocol designed to retrieve configuration and
status information using WEB/HTTP requests. TXP exists side by side with an SNMP agent and
provides an alternative way to access data in a product. TXP and SNMP therefore complement
each other.
This page contains settings to determine how the unit should respond to TXP queries.
82 WEB Interface
Mode
Controls the mode of the TXP server. If set to Disabled, all TXP accesses are disabled.
Anonymous read
Selects whether read accesses should be allowed without entering user credentials. This may
only be edited if Mode is different from Disabled.
Require HTTP POST for txp_set

Recommended to reduce risk of unwanted configuration changes.
Required level for read

The required user level for TXP read accesses. This may only be edited if Mode is different
from Disabled and Anonymous read is not selected.
Required level for write

The required user level for TXP write accesses. This may only be edited if Mode is set to
Write.
Below follows a simple example of how to get the units uptime.
http://10.0.0.10/txp_get?path=/dev/time|_select:uptimetxt
<response request_id="0" method="txp_get" time_stamp="2012-08-17 11:14:20" version="1.0">

<status status="0" status_text="OK"/>
<data>
<dev>
<time uptimetxt="49 days 21h:56m:09s"/>
</dev>
</data>
</response>
9.4.4.5 SNMP Settings
The Simple Network Management Protocol (SNMP) is used to monitor network-attached devices
for conditions that warrant administrative attention. This page gives access to SNMP settings such
as destination IP addresses of trap receivers and community string. It Also displays a log of the
latest traps sent by the unit.
The Trap Destination table lets the user configure the trap servers that should receive SNMP traps
from the unit. To add a server click the Add new button, enter an IP address, then click the Apply
button. To delete an entry select a server entry from the list and click the Delete button.
The Settings group of parameters configures MIB-2 parameters and SNMP password protection.
The SNMP version to use for traps, version 1 or version 2, may be selected. When selecting to
transmit SNMPv2 traps, two additional options are applicable.
Status change traps

Selecting this causes a trap to be transmitted each time the overall device status changes.
Alarm event forwarding

Configures which alarms to forward as SNMP traps. The drop-down list has the following
options:
WEB Interface 83
Figure 9.29 SNMP Settings
Disabled
No traps are transmitted when alarms appear or disappear. If the Status change traps
check box is checked, device status traps are still transmitted.
Basic
The device forwards alarm events as SNMP traps. If there are several sub-entries only
a single trap is transmitted.
Detailed
The device forwards alarm events as SNMP traps. If there are several sub-entries, an
SNMP trap is transmitted for each sub-entry.
The table at the bottom of the page shows the most recent SNMP traps sent by the device.
For more information about the configuration settings for SNMP, please refer to Section 10.4 in
Chapter 10: SNMP.
9.4.4.6 Tools
The tools menu contains helpfull tools for network debugging.
9.4.4.6.1 Ping
The ping tool can be used to check for connectivity between devices. It is especially useful to ping
the receiving data port from the IP transmitter to see if the receiver can be reached.
IP destination
The IP address of the receiving data port. The ping messages will be routed to the matching
Ethernet port, either data or management, or to the port configured as default management
interface if the specified IP address does not match either of the two sub-nets. Note that if
84 WEB Interface
Figure 9.30 The Ping tool
you are pinging between data interfaces, the Allow ping response option on the network page
Advanced tab (see Section 9.4.4.1.3) must be enabled both in the transmitter and the receiver.
Note: When the IP destination is a multicast address one cannot expect to

receive a response to a ping request. It is recommended to test connectivity
using the device’s actual IP address.
TTL (Time To Live)

Enter the time to live value for the ping messages here. The time to live value is a field in the
IP protocol header that is decremented once for each router that the datagram passes. When
the count reaches 0, the datagram is discarded. You can use this to check the number of
routers between the transmitter and the receiver by starting with a low value and increment
it until ping responses are received. TTL is also specified for each data channel on the IP
transmitter, and must be high enough to reach the receiver. Values range from 1 to 255.
Ping count
The number of ping messages to send. The messages are transmitted with an interval of
about 1 second.
MTU
Maximum Transfer Unit. Specify a length for the ICMP frames to check that frames with
given length pass through the network. The ICMP data payload size is adjusted to yield
Ethernet frames with the specified length. The ping messages are transmitted with the “don’t
fragment” bit set.
Start
Press this button to start the pinging sequence configured above. The status of the ping
sequence is displayed in the status frame. Status values are reset on pressing the start button.
After pressing the start button the label switches to Stop, and the button can be pressed again
to cancel the pinging sequence.
OK responses
The number of ping responses received.
Timeouts
The number of ping requests that were not answered. If the timeout counter is incrementing
while the OK responses counter is zero, there is no contact with the specified IP address.
WEB Interface 85
Last roundtrip
The round trip time measured for the last ping request in units of milliseconds.
Average roundtrip
The average round trip time measured for the ping requests in this session. The value is reset
every time the start button is pressed.
Min roundtrip
The shortest round trip time registered for the ping requests in this session.
Max roundtrip
The longest round trip time measured for the ping requests in this session.
Remaining
The number of remaining ping requests in this session.
9.4.4.6.2 Traceroute
The traceroute tool can be used to debug the network connectivity with a given host by tracking
the router hops between the TNS544 and the host. Traceroute uses ICMP ping messages with
increasing TTL to track the router hops.
Figure 9.31 The Traceroute tool
Settings
IP Destination
The IP address of the host to check. IP routing decides which interface the ICMP mes-
sages are sent on.
86 WEB Interface
Number of hops
This parameter sets a roof to the number of hops that are tracked. Normally this para-
meter can be set fairly low.
MTU
Maximum Transfer Unit. This parameter can be used to transmit messages with a given
length. ICMP messages are transmitted with the don’t fragment bit set to yield errors
when MTU of a link is too small for the frame.
Status
Running
State of tracer.
Current TTL
Increasing for each new hop traced.
Trace
Grid showing routers encountered.
Hop
Hop number.
RTT[ms]
Round trip time measured in milliseconds for message returned from router at this
point in chain.
IP Address
IP address of router at this point.
Hostname
DNS resolved host name for IP Address. For this column to be filled in, DNS must
be supported and a DNS server must have been defined either manually or by DHCP
client.
9.4.5 Clock Regulator

This page lets the user configure synchronisation of the internal 27 MHz clock from an external
source.
9.4.5.1 Main
Figure 9.32 Clock regulator
WEB Interface 87
The reference signal is supplied on a separate connector. This page gives access to selecting how
the reference is used.
The Configuration field:
27 MHz lock mode

Disabled
The internal clock will not make use of an external reference signal.
Lock to external 1 PPS

Configures the internal clock to use the external 1 PPS input connector as reference.
The Clock Regulator Status field:
Regulator state
Idle
External reference signal is disabled.
Waiting
External Reference signal is enabled, but the internal clock has not obtained lock to the
reference
Fine tune
External Reference signal is enabled, and the internal clock has obtained lock to the
reference.
Current phase offset

Phase offset between the internal clock and 1 PPS clock reference given as a multiple of 3.704
ns (one period of 270 MHz)
Current freq. offset

Frequency offset between the internal clock and 1 PPS clock reference.
Current drift
Compensated frequency offset between external and internal reference.
9.4.5.2 Alarms
Figure 9.33 Clock regulator Alarms
88 WEB Interface
These are the Clock regulator specific alarms. Clicking an alarm opens the field to configure the
alarm. Please see Section 9.4.2 for alarm configuration details.
9.4.6 Configuration Manager
The Configuration Manager, shown Figure 9.34 provides an interface for managing the device
configuration as “snapshots”. From here, snapshots of the device configuration settings can be
taken and stored locally, or exported from the device as XML files. Also, configuration files may
be imported and applied.
The device allows for up to 8 configuration snapshots to be stored and managed locally, not in-
cluding the current running configuration.
9.4.6.1 Save/Load Configs
Figure 9.34 Configuration manager
9.4.6.1.1 Save Configuration To File
This is the interface for exporting the current running configuration as an XML file. Clicking the
Save Config button prompts the user with a standard Save as dialogue requesting a location to
store the configuration file. This location can be any place the user has access permissions to write
files.
WEB Interface 89
During the transfer of the file from the device to the user’s system the user has the ability to click the
Cancel button to cancel the transfer. Note that, depending on the web browser used, an incomplete
file may be left on the user’s system after canceling.
Upon completion of the transfer the transfer progress bar will turn green. If an error occurs during
the transfer the progress bar will turn red and display an error message.
Files exported from the device using this option contain a complete device configuration and can
be restored to the device at a later time. Or it may be installed on another device using the Load
Configuration option.
9.4.6.1.2 Load Configuration From file
The Load Configuration From File field of the page provides a mean to directly import a file-
based configuration snapshot as the new running configuration. All options from the snapshot
are loaded and verified before making them active, thereby minimizing the risk of errors in the
file that would render the device in a non-operational state.
Clicking the button marked Browse prompts the administrator with a standard system File Open
dialogue allowing the administrator to select the file of his choice to import. Once selected, clicking
Load Config performs the following actions :
• Transfers the configuration snapshot from the administrator’s PC to the device.
• Validates the configuration to make sure that all the options in the file are compatible with
each other and with the device itself.
• Presents the user with additional information, such as skipped options.
• Activates the configuration.
When an import has been successfully completed the progress bar color turns green and changes
its text to OK. Upon failure at any point the progress bar will turn red, and details of the reason
for the failure will be presented as messages in the Result of last config activation list.
By default, options specific to the device, including device name and management port network
configuration, are disregarded during the import process. This is a convenience feature allowing
configurations to be easily moved from one device to another. It also makes management easier in
that the Web UI will continue to communicate with the device after a new configuration has been
loaded. The default behavior can be changed with the load options, please see Section 9.4.6.1.4
for a description of the options.
Partial configuration files are supported to allow a subset of configuration options to be changed
instead of the entire unit configuration. Partial configuration files are validated as differences from
the current running configuration upon import before being made active.
9.4.6.1.3 Load Configuration from Remote Device
The Load Configuration from Remote Device makes it easy to copy the configuration of another
device to this device. This device will therefore be a clone of the remote device, except for device
specific parameters such as IP addresses and product name. Loading a configuration from Remote
90 WEB Interface
Device is essentially equal to saving the configuration file of another device, and uploading it to
this device.
The configuration field includes the IP address of the remote device. Entering an IP address and
pressing the Contact Device button will check if the connection is valid and display some informa-
tion about the device if successful. If the connection is valid, the Load Config button will become
clickable.
Note: It is possible, but not advisable, to load configuration from other

model types. Even if loading from the same model type, loading a config-
uration might also fail, especially if the two devices have different feature
sets. See Section 9.4.7.1 for a list of features.
Please see next chapter (Section 9.4.6.1.4) for a description of the load options.
9.4.6.1.4 Load options
These options are used to modify the behavior on configuration loading. The options are available
when loading from a file (Section 9.4.6.1.2) and when loading from a remove device (Section
9.4.6.1.3) .
Default action
This parameter modifies the algorithm used when modifying lists (collections) in the config-
uration.
Restore
Modify list to contain exactly the entries specified in the file loaded.
Merge
List entries that are present in the running configuration but not in the file loaded are left
in the list. New entries specified in the file loaded but not in the current configuration
are added. Entries present both in file loaded and in running config are modified.
Update
Only update nodes that are present in running configuration and in file loaded, i.e no
list entries are added or removed.
Overwrite
This parameter is used to modify how specially tagged parameters are handled during file
loading.
Access control parameters

Tick to overwrite SNMP community strings and TXP access parameters.
Device identifier parameters

Tick off his check box to overwrite the device identifiers device name and inventory ID.
Ethernet Interface IP addresses are not overwritten using this option.
WEB Interface 91
9.4.6.2 Boot Log
This page shows the configuration database status log from the configuration loading at last re-
boot. If the configuration is rejected at boot the previous configuration will not be replaced. This
page may then be inspected to find the reason for rejection.
9.4.6.3 Stored Configurations
This tab provides an interface to management of on-device stored configuration snapshots. Up to

8 full system configuration snapshots can be stored.
Figure 9.35 Locally stored configuration files
The table lists the currently stored snapshots, and columns in the table provide information specific
to each snapshot as follows:
Id
Each entry in the table has an id in the range from 0 to 7.
Valid
Indicates if the uploaded configuration is valid. Configuration that are valid may be acti-
vated without errors. A valid configuration is indicated by a green indicator and a invalid
configuration is indicated by a red indicator. A silver indicator in this column signifies that
the slot is empty and available.
Description
A descriptive text can be entered in this field by clicking on the field itself and typing text.
The length of this field is limited to a maximum of 64 characters.
Date saved
Time stamp when the configuration was uploaded to the unit.
92 WEB Interface
File size
Size of the configuration file.
State
Extra information regarding the configuration.
To the right of the table several buttons are provided to perform the following actions:
Activate
Loads the selected snapshot as the active configuration of the device. The administrator will
be prompted to verify the decision as this action will overwrite any unsaved changes on the
device.
Snapshot
Stores the current running configuration as a snapshot in the slot selected in the snapshot
table. This operation will overwrite the configuration file currently stored in that position.
Upload
Imports a configuration file from disk to the selected slot. This operation will overwrite the
configuration file currently stored in that position.
Download
Downloads the selected configuration file to disk.
Delete
Delete the entry selected in the snapshot list.
At the bottom of the page is the Results of last config action field, which will show the result and
a list of errors (if any) of the last action performed.
9.4.7 Maintenance
The Maintenance page centralises information regarding the hardware configuration of the device
and provides a means for updating firmware images and managing software feature licences.
The page gives access to three sub-pages described below.
9.4.7.1 General
The General tab on the maintenance page details the current software, hardware and licence con-
figuration of the device. Note that the items listed vary between devices.
At the top are two buttons for resetting purposes:
Reset Unit
Provides an interface to perform a restart operation on the unit. Following a restart boot
delay the user is prompted to reload the Web UI in the browser.
Restore Factory Defaults

Resets all non-device specific settings to the factory default settings. Settings remaining un-
changed include the device name and the management interface IP configuration.
WEB Interface 93
Figure 9.36 Maintenance
Generate System Report

Generates an status report of the unit in XML format. Please attach this system report when
contacting Nevion Customer Support.
The Product info field provides the following information:
Product name
This is the product model name.
Software version
The version of the firmware image installed in the unit.
Serial number
The manufacturer assigned serial number used for warranty and software licensing.
Installed boards
The name and serial numbers of the circuit boards installed in each of the internal interface
slots of the unit.
Features
A list of features relevant to the device and their state (e.g. true, false or the number of ports
supported).
Name
Name of the feature
Value
State of the feature or number of licenced items
Code
The factory order code used to identify this feature
94 WEB Interface
Hot
Whether the licence can be upgraded without rebooting the device or not. If the field
reads ’yes’, no reboot will be required after loading a licence upgrade file.
The TS Configuration Mode field allows the user to select DVB or ATSC operational mode.
Figure 9.37 TS
Configuration Mode
The choices are:
DVB
DVB transport streams only are accepted.
ATSC+DVB
Both ATSC and DVB streams are accepted.
Caution: When switching mode from DVB to ATSC+DVB (or vice versa),
the unit configuration is set back to factory defaults and it is then rebooted.
if the SFP Module SW licence key is installed, the Operational Modes frame is visible and provides
the option Electrical/SFP as shown in figure 9.38. This option is used to allocate the Data-2 IP
input to operate through the Electrical Ethernet data interface, or through the SFP slot.
Figure 9.38 SFP and Electrical Ether-

net select
When switching mode the unit will automatically reboot. The device configuration is kept but
references to Data-2 will be invalid.
9.4.7.2 Software Upgrade
The Software Upgrade sub-page lets the user upgrade the software of the device. The page con-
tains three buttons and a checkbox:
Browse
Prompts the administrator with a standard system Open file dialogue to specify the new
software image file to install.
Upload
Once an image file is specified by using the Browse button, the Upload button is used to
WEB Interface 95
Figure 9.39 Software Upgrade
transmit the file from the administrator PC to the device. Once the file has been transferred,
it is verified using and internal checksum value and set as the new active firmware image.
If the upload is successful the progress bar turns green and the unit reboots itself loading the
new image, unless the Reboot on success option has been unchecked.
If the upload is unsuccessful the progress bar turns red and an error message is displayed in
the Status field.
Cancel
The Cancel button is enabled during the upload process and can be clicked to cancel the
operation. It is not possible to continue a cancelled upload.
Reboot on success
This checkbox is checked by default but can be unchecked to disable automatic reboot upon
SW loading completion. If this option is not checked the SW will load but will not be activated
before the user performs a manual reboot. Note that this option is not stored on the device,
and Reboot on success will be enabled next time you enter the SW upgrade page.
During SW loading, an alarm SW loading in progress is set with the Details field displaying the
IP address of the machine from which the loading was initiated. The alarm is turned off when the
loading is completed or terminated.
If the Reboot on success option is active the unit will automatically reboot when loading is com-
plete, otherwise an alarm New SW pending is set to indicate that a new SW will be used on next
manual reboot.
After uploading, if the Progress bar shows OK but the web interface does not change to the Waiting
for reset state, allow some time for the device to reset itself and then reload the web UI via the
web browser reload button.
Note: It is recommended to verify the new software version via the “Prod-
uct Info” page (Section 9.4.1) to verify that the update was successful
and the latest software revision is active.
96 WEB Interface
9.4.7.3 Feature Upgrade
Figure 9.40 Feature Upgrade page
The Feature Upgrade sub-page provides an interface to upload new software licences to upgrade
the feature set of the device. The licence key is provided as a text file. Paste the content of file into
the text area and click the Load Key button.
Some features do not require a restart of the device when upgraded, they are marked as “hot” in
the feature list. If you load a licence changing only hot-upgradable keys, you will get a message
back in the load text box telling you that no reboot is required. If any non-hot licence has changed,
the device needs to be restarted to activate the new feature(s).
Reset can be performed from the GUI as explained on the Maintenance > General tab in Section
9.4.7.1.
Note: The entire content of the licence key text file must be copied into
the text box, not just a portion of the file.
9.4.8 Users
The Users page provides a configuration interface for user management. Settings are provided for
configuring a password for each privilege level and for configuring automatic login settings. You
must have administrator previledges to alter the settings.
Auto login
Specifies the user privilege level to use for automatic login to the device. Changing this fea-
ture from the default ("No auto login") to another setting bypasses the initial login screen
(Figure 9.2) encountered by default.
WEB Interface 97
Figure 9.41 Users page
Users
Each user privilege level has an account name and password. The account name is fixed for
each level and therefore cannot be changed. Each privilege level, however, has an adminis-
trator definable password.
To modify the password for a given privilege level select the user name from the list and click
the Set password button. The administrator is then prompted with a dialogue requesting a
new password. Three user privilege levels are available.
guest
Can view configuration information and alarm logs
operator
Can configure the settings on the device, but can not alter passwords
admin
Device administrator, full access to the device.
On the bottom of the page you can see all active GUI session. Note that this does not include
SNMP or TXP accesses. The table includes information about the peer IP address, access level and
duration of the current sessions.
9.4.9 GUI Preferences

The GUI Preferences page contains settings that affect the web interface.
Enable confirmation on Apply

Configures the web UI to prompt users for confirmation before committing changes to the
device configuration. When disabled the Web UI will only prompt for confirmation prior to
performing severe operations such as device reset.
Enable GUI scaling

If enabled, the web interface will be shown with the currently configured GUI scale level.
It also enables the use of CTRL + + and CTRL + - to change scale level. When enabling or
disabling this option the web interface may hang for some seconds as it changes the font
used.
98 WEB Interface
Figure 9.42 GUI Preferences page
GUI scale level

The current scale level for the GUI. This is ignored if GUI scaling is not enabled. A value of
0 means normal size.
Return to current status page on refresh

Check this to return to status page once refreshing the GUI WEB page. If not checked, you
will return to the last visited sub-page when reloading the page.
Enable sound on critical alarm

This option makes the computer play an alarm sound continuously if browser is connected
to unit while it has a critical alarm. Use with care.
Note: Every browser session will play sound independently of each other
if you enable this on multiple devices and/or have multiple open browsers.
Note: ’Enable confirmation on Apply’ is stored on the device, while the

other options are stored as browser cookies and thereby only affect the
local browser and PC.
9.5 Inputs
The Inputs page contains all information and settings that apply to the input ports of the device.
The navigation list to the left lets the user select which input to view, or select Inputs Overview to
view a summary of all the inputs to the device. In addition the list also includes the input switchers
and their corresponding inputs, if configured.
The labelling of the inputs is a combination of the user defined name of the input and the physical
number of the input port.
WEB Interface 99
9.5.1 Inputs Overview
Figure 9.43 Inputs Overview
The Inputs Overview page shows a short table summary of all the inputs of the device. The table
has the following columns:
Enable
This shows whether the input is enabled or not. An input is enabled or disabled by clicking
the check box and hitting Apply.
Input
The name of the input, consisting of the factory defined label with the physical port number
and the user defined name.
Status
Describes status for the input signals and switches. For IP inputs, the status field indicates
which switch they are sourcing as well as whether they are the active input. For the switches,
this field indicates whether they are active or disabled.
Sync
Displays “yes” if the unit has synchronised to this transport stream input.
TS id
The transport id of the transport stream currently received on the input. This parameter
depends on the PAT table of the PSI being present on the input and decoded successfully.
ON id
The Original Network id of the transport stream currently received on the input. The correct-
ness of this parameter depends on the SDT-actual table of the SI being present on the input
and decoded successfully.
100 WEB Interface
Note that in ATSC mode the Original Network id is not applicable.
Total Bitrate
The total bitrate in Mbit/s of the transport stream currently received on the input.
Effective Bitrate
The effective bitrate in Mbit/s (excluding null packets) of the transport stream currently re-
ceived on the input.
Alarm Status
The current alarm status of the input is shown as a coloured indicator, the colour indicating
the highest severity level of the active alarms. If the port is disabled the indicator is grey.
Below the table three values as shown. They are:
Total input rate

The combined total bitrates of all the transport streams of all the input ports.
Total effective input rate

The combined effective bitrates (total, minus null packets) of all the transport streams of all
the input ports.
Total cache used

Number of bytes stored in PSI/SI/PSIP database for all input ports. The sections are stored
in the database in binary format.
The Reset Stats button at the bottom of the page gives access to a dialog box that allows reset of
channel statistics. Figure 9.44 shows the dialog box. Select the statistics items you want to reset
and then press Apply.
Figure 9.44 Reset

statistics dialog box
9.5.1.1 IP Inputs
The page lists IP input streams defined and offers an interface to add or remove input streams.
The table has the following columns:
Enable
This shows whether the IP input is enabled or not. An input is enabled or disabled by clicking
the check box and hitting Apply.
WEB Interface 101
Figure 9.45 Inputs Overview - IP Inputs
IP Input
The name of the IP input, consisting of the factory defined label with the physical port num-
ber and the user defined name. If no user defined label is defined for multicast streams, the
multicast address is displayed.
Interface
The interface that this IP input is configured to receive data through.
Last IP Source
The IP address that this IP input last received data from. If the input has never received any
data the IP address is shown as 0.0.0.0.
Port
The UDP port this IP input is configured to receive data on.
Multicast Address
If the IP input is configured to receive data through a multicast the multicast address is shown
here.
Ethernet Bitrate
The currently received bitrate in Mbit/s, measured at the Ethernet level.
Seq.Err.
The number of RTP sequence errors reported by the input since the last reset of statistics. RTP
sequence error measurements requires the RTP protocol is present in the received stream.
Status
The current alarm status of the input is shown as a coloured indicator; the colour indicating
Below the table four values are shown. The first one is the total Ethernet bitrate received. The last
three are identical to the three values for ASI inputs described in the previous section.
102 WEB Interface
The Add IP and Remove IP buttons at the bottom of the page lets the user add or remove IP inputs.
After clicking the Add IP button the Apply button must be clicked before the channel parameters
can be edited. A new channel is shown with a plus sign in the navigator until it has been edited
(and the edit applied).
9.5.1.2 Copy Inputs

Copy Inputs are virtual inputs that may be used to duplicate data from other inputs. The copy
inputs may eliminate the need for an external Distribution Amplifier. The unit treats the Copy
Inputs the same way as any other input in the system, and the data may thus be changed while
not affecting the original stream. Also, the Copy Inputs has individual settings independent of
the settings of the original stream.
The unit is equppied with up to 8 individual Input Copies, where each Input Copy may be the
copy of any ASI or IP input port. Further it is permitted to make several copies of the same ASI or
IP input port.
This page lists all the currently existing Copy Inputs on the unit, and also allows creation and
deletion of Copy Inputs by using button below the table.
Enable
This shows whether the Copy Input is enabled or not. If disabled no packets will be received
and all input alarms will be cleared.
Copy Input
This column shows the unique name of the Copy Input. The name in the parentheses shows
which input the Input Copy is copied from.
Status
The current alarm status of the input is shown as a coloured indicator; the colour indicating
9.5.2 TS (Transport Stream) Inputs

When a specific input is selected, a page with information about that input is displayed. The
header of the page shows the name and the current alarm status of the input and a list of tabs that
is dependent on what sort of input is selected (ASI, IP,...) and what options are selected.
Figure 9.46 Input header
Holding the mouse cursor over the alarm status indicator brings up a tool tip displaying up to 30
of the current alarms (if any) on this particular input.
Beneath the name of the input is a tab navigator containing different sub pages with information
about the selected input. The choices are:
WEB Interface 103
ASI Input Sections

This page shows a summary of the transport stream currently received on the input, includ-
ing a summary of the running PIDs and services.
Alarms
This page lets the user view the status of all alarms on the input, and override the severity of
these alarms.
IP
This tab is present only if the input selected in the navigator is an IP input. It gives access to
the IP specific features of the input.
Services
This page gives detailed information about the services that are currently running and the
components of those services.
PIDs
This page gives detailed information about the currently present PIDs.
Tables
This page shows which tables are present on the input and allows selecting tables that should
be analysed by the unit.
In all sub-pages, for a selected input, the list of the current alarms for that input is shown at the
bottom of the page. The list is identical to the list displayed in the Current Status view, described
in Section 9.3.1.
9.5.2.1 ASI Input Sections
The ASI Input Sections page is divided into three sections for ASI Inputs (figure Figure 9.47) and
five sections for IP inputs. For IP inputs the two extra sections are the IP RX configuration section
(top left) and the IP RX status section (top right), see figure Figure 9.48.
In the IP RX configuration section the Enable and Input label fields are identical to those described
for the ASI inputs below. The rest of the IP configuration and status parameters are described in
Section 9.5.2.3.
At the bottom of the page the Reset Stats button is located. Clicking this will set all statistics
counters relating to the selected input to zero.
The Transport Stream Details field contains information and some configuration settings for the
incoming transport stream:
Enable input
This shows whether the input is currently enabled. The input is enabled or disabled by click-
ing the check box and then Apply.
Input label
This is the user defined name of the input port, which can be changed by typing a new label
and hitting Apply. It is only used in the WEB GUI to identify the port.
104 WEB Interface
Figure 9.47 ASI Input Sections
TS mode
Transport stream mode, either DVB or ATSC (only available in ATSC+DVB configuration
mode).
TS id
The transport id of the transport stream currently received on the input. The value of this
depends on PAT being present and decoded on the input.
Orig. Network id
The Original network id of the transport stream currently received on the input. The value
of this parameter depends on the SDT actual being present and decoded on the input.
Sync detected
Shows whether the input transport stream has been synchronised.
Total Bitrate
The total bitrate of the transport stream currently received on the input in Mbit/s.
Effective Bitrate
The effective bitrate (excluding null packets) of the transport stream currently received on
the input in Mbit/s.
Packet length
The length of the transport stream packets in bytes.
WEB Interface 105
Figure 9.48 IP Input Sections
Beneath the Transport Stream Details section is the PIDs present section. This shows all the
PIDs that are present on the selected input. The number in parentheses is the total number of
PIDs present. A PCR PID is represented by a number shown in italics. A coloured PID number
provides additional PID status information:
Red
A continuity counter (CC) error alarm is raised.
Blue
Stream is scrambled. The shade of blue represents whether the scrambling mode is odd or
even.
Hovering the mouse pointer over a PID provides detailed information about that PID.
On the right hand side of the page is the Services Present section. This shows a list of all the
services that are currently present on the selected input. The list depends on PAT and PMT being
present and successfully decoded on the input. The service name depends on SDT actual being
present and decoded. The number in parentheses is the total number of services present.
The list has three columns:
Service ID
The program number/service id of the service
106 WEB Interface
Service Name
The name of the service as conveyed by the SDT Actual table. If there is no SDT Actual table
or if the SDT table is not analysed, the name is displayed as Service <SID>.
For ATSC services, the service name displayed is a concatenation of the short channel name,
and the major/minor channel number.
The icon prefixing the service name indicates the alarm status of the service and, if the SDT
table is analysed, the type of service. A list of active alarms (if any) on the service is displayed
by holding the mouse pointer over this icon.
Detailed information about the service is displayed by holding the mouse pointer over the
"I" icon to the right.
Service Bitrate
The current bitrate of the service, i.e. the aggregate bitrate of all the service components.
Double clicking on a service will navigate to the Services page, with the folder for the service at
hand being expanded.
9.5.2.2 Alarms
The Alarms page lets the user configure and view the status of all alarms belonging to the selected
input.
In figure 9.49 the Alarm Config page is shown. Note that the alarms are organised hierarchically
and that only the branches in focus need to be expanded.
Figure 9.49 Input alarm configuration
The following configuration options are available:
Show
The radio buttons Error count and Configured severity allows the user to configure what to
be shown in the input alarm tree (see figure 9.50).
Error count
Display the accumulated number of errors since last alarm counter reset.
WEB Interface 107
Configured severity
Display the configured alarm severity.
Reset Alarm Counters

Reset the alarm counters for all alarms belonging to the selected input.
Copy Settings from Input

This is a convenient way to copy alarm settings for a specific input to the current input. Use
the Input drop-down list to choose from which input to copy the settings. The settings are
copied by hitting the Copy Settings button. This includes all severity and limit overrides both
on alarm level and on PID level.
The input alarm tree is found in the main part of the page. It consists of a tree displaying all alarms.
Figure 9.50 Input alarm tree
The input alarm tree is shown in figure 9.50. By clicking on the alarm nodes in the tree the details
for the selected alarm is shown in the Alarm details section (figure 9.51).
The alarm tree has two types of nodes:
Folder
Corresponds to a group of alarms. The colour of the folder shows the highest severity of all
108 WEB Interface
the alarms belonging to the group. The group is expanded or collapsed by clicking on the
arrow next to the group.
The alarm counters for a specific group are reset by left-clicking an alarm group in the alarm
tree and choosing the Reset Counters option. The counters for the individual alarms are reset
using the same procedure for an alarm node.
Alarm node
These have a coloured indicator showing the alarms current status. In addition, the alarms
configured severity or the current error count is shown in brackets to the right.
The right hand side of the page shows details about a single selected alarm (see figure 9.51). The
frame appears when a particular alarm is clicked. Its content may vary according to the alarm
selected.
Figure 9.51 Alarm details
The alarm details section includes the following information and buttons.
Alarm ID
The internal ID of the selected alarm. A complete list of alarms is found in Table E.3.
Alarm
Name of the alarm.
Description
A short description of the alarm.
Severity
Overrides the default severity for the given alarm. The default severity is in brackets to the
right of the drop down list. The factory default value for the severity is Use global default.
The globally configured alarm severity is then always used.
Max interval (alarm dependent label)

This field is shown for table repetition alarms. The number entered in the box determines
the maximum time (milliseconds) allowed between two occurrences of the same table. The
default value is shown to the right.
Max rate (alarm dependent label)

This field is shown for PID rate alarms. The number entered in the box determines the maxi-
mum rate allowed for a given PID above which an alarm is raised. The default value is shown
to the right.
WEB Interface 109
Min rate (alarm dependent label)

This field is shown for PID rate alarms. The number entered in the box determines the mini-
mum rate allowed for a given PID below which an alarm is raised. The default value is shown
to the right.
Alarm turned on
Number of times the alarm has triggered. If the alarm is filtered this counter will not in-
crease.
Error count
For alarms that are checked continuously, this counter shows the number of times an alarm
condition has been violated. This counter will increase even if the alarm is filtered.
Global setting
This field shows the value configured for this alarm in the global settings. If the alarm severity
level is set to global default in the “Severity” pull-down list, this is the value that will be used.
In addition, if the alarm contains a limit, e.g. max interval, a numeric input at the bottom is dis-
played. This lets the user override the default limit, which is shown in brackets to the right.
Reset counters
This button lets the user reset the "Alarm turned on" and "Error count" counters for this
alarm.
"PID" and "Service"alarms (Figure 9.52) allow overriding of sub items. For such alarms two tables
are shown below the alarm details.
Figure 9.52 Alarm severity per sub-ID (typically Service or PID)
110 WEB Interface
The Service/PID with active alarms table shows all currently active alarms on sub-items for the
selected alarm. The following columns are found in the table.
Service/PID
The id of the sub-item.
Severity
The current severity of the item.
Overridden
Indicates whether the sub item has been overridden.
If no override already exists an override can be added by right-clicking an item. An item already
overridden can be edited or removed.
The Overridden PIDs/Services section shows currently overridden sub items. The following columns
are found in the table:
Service/PID
The id of the Sub item.
New severity
The new severity, i.e. the severity after the sub item has been overridden.
New limit
If the alarm has a configurable limit, also the limit of the sub item can be overridden and that
new limit will also be shown.
An override can be edited or removed by right-clicking on the entry in the list. Alternatively
this can be done by hitting the Edit and Remove button, respectively. An override can also
be added hitting the Add button and manually entering the ID and overridden values.
9.5.2.3 IP
This tab is only visible if an IP input is selected.

The tab contains the sub pages Main, Ping and Regulator. If the IP Forward Error Correction
feature is available the FEC sub page selection is also visible.
The Main sub page is shown in figure 9.53.
This page allows configuration of the IP parameters for the IP input and shows detailed IP status
information for the input.
The IP RX Parameters field:
Enable
This shows whether the input is currently enabled. The input is enabled or disabled by click-
ing the check box and then apply.
Receive port
The UDP port on which this input will listen for data.
WEB Interface 111
Figure 9.53 IP Configuration
Presumed jitter
The maximum amount of jitter you expect on the ip link. This value controls the amount of
buffering that will be applied.
Join multicast
If this box is checked the input will join the multicast configured in the following IP field. If
the box is not checked the input will listen for unicast traffic.
Multicast group addr

This parameter is only used if the “Join multicast” box is checked. This is the multicast group
the input will join.
Multicast source addr

This parameter will only be used if the input is set to join a multicast and the unit is currently
using IGMP v3. If this parameter is set to something different from 255.255.255.255 or 0.0.0.0,
the input will only accept multicast traffic from the IP address specified in this parameter.
Source interface
The interface on which this input will listen for data.
The IP RX Status field:
Locked
“Yes”, when the unit has locked to the input stream and has correctly estimated the bitrate of
the input stream. “No”, when the unit has not been able to receive the input stream correctly.
Last IP source
The source IP address of the last IP stream received by this input. If the input has never
received an IP stream this value is set to 0.0.0.0.
112 WEB Interface
Total rate
The total IP rate received on this input.
Latency
This parameter reflects the network jitter the unit can handle at the moment.
Min/Max latency
This shows the minimum and maximum latency measured since the statistics was last reset.
Protocol
Indicates RTP if the received data contains an RTP header, UDP otherwise.
TS packets per frame

The number of transport stream packets per IP frame and the size of the transport stream
packets in the incoming stream.
RTP sequence errors

A counter showing the number of RTP sequence errors caused by lost packets or packets
received out of order. A value of zero indicates that all packets are received in correct se-
quence.
RTP max jump

The max jump in RTP sequence number between two consecutive packets received.
Duplicated IP frames
The number of received IP frames with RTP sequence numbers which have already been
received.
Lost IP frames
A counter showing the number of IP frames that have been lost, i.e. lost and not corrected by
the unit.
Corrected IP frames
A counter showing the number of IP frames corrected by the FEC engine.
Max burst loss

The maximum number of consecutive packets lost.
Number of resyncs
The number of times the buffer has been re-synchronised. Re-synchronisation causes a dis-
ruption in the picture. The most typical reason for a re-sync is when no data is received and
the buffer runs empty. The reason for re-syncs is tagged in the alarm details for the No Lock
alarm.
9.5.2.3.1 FEC
The FEC sub page is shown in Figure 9.54. This page displays the status of the forward error
correction processing of the IP input.
WEB Interface 113
Figure 9.54 Input FEC configuration
The Configuration field provides a single check box to enable or disable input FEC processing. If
this box is not checked all other fields in this page is greyed out, i.e. not applicable.
The Status“ field shows the overall result of the FEC processing:
Lost IP frames
The number of IP frames lost. I.e. FEC processing has not been able to recover these frames.
Corrected IP frames
The number of IP frames that were successfully regenerated by the FEC processing.
Duplicated IP frames
The number of IP frames that have been regenerated while also being received correctly. This
occurs if the IP frame is received out-of-order with sufficiently long delay (thus regarded as
lost by the FEC processor).
Max Burst Loss Length

The maximum number of consecutive IP frames that have been lost.
Columns(L)
The number of columns used in the FEC matrix of the incoming signal.
Rows(D)
The number of rows used in the FEC matrix of the incoming signal.
Max IP frames delay

The maximum delay of out-of-order IP frames (datagrams).
114 WEB Interface
Latency required
The latency required by the input FEC processor to handle the incoming FEC matrix.
The Column Stream Status and Row Stream Status fields show the status of the IP stream carrying
the column and row FEC IP datagrams, respectively:
UDP port
The UDP ports receiving the column/row FEC data.
Bitrate
The bitrates of the Column and row FEC data.
RTP sequence errors

Shows the number of disruption in the sequence count of the RTP protocol.
For further details of FEC properties and usage, see Appendix C.
9.5.2.3.2 Ping
The Ping sub page is shown in figure 9.55.
Figure 9.55 Ping page
Timeouts in MAC address lookup tables can sometimes cause problems when routing one-way
traffic. The Ping feature is designed to solve this by transmitting a ping message generating two-
way traffic.
The Settings field:
Enable Unicast Peer Ping

Check this box to enable Unicast Peer Ping. This enables regular pinging of the transmitting
device.
Interval
Set the interval in seconds between each Ping.
MTU
Sets the Ethernet frame size to use on ICMP messages transmitted.
The Status field displays the status of the on-going pinging session:
IP destination
The address of the device receiving the Ping requests.
Time to live
This figure indicates the number of routing points the Ping message may encounter before it
is discarded.
WEB Interface 115
OK responses
Indicates how many valid Ping responses have been received.
Timeouts
Indicates how many of the sent Ping messages timed out, i.e. did not provide a valid response
within the allowed time.
Last roundtrip
The time taken from last sending the Ping message until the response is received.
Min roundtrip
The minimum time taken from sending a Ping message until the response is received.
Max roundtrip
The maximum time taken from sending a Ping message until the response is received.
9.5.2.3.3 Regulator
The Regulator sub page is shown if figure 9.56.
Figure 9.56 Regulator page
In the Regulator Settings field it is possible to adjust the settings of an IP input buffer regulator.
Lock to MIP bitrate (SFN)

Enable this to lock the bitrate to DVB-T MIP timestamp if a MIP is found in the stream. This
option will only work over time if both the unit transmitting the MIP and the IP receiver have
locked their 27Mhz clocks to the same 1PPS reference.
Manual bitrate (SFN)

This option lets you configure a bitrate manually on the IP input channel, disabling the buffer
regulator. This method is similar to Lock to MIP bitrate, except that the bitrate is specified
manually, and the mode will only work over time if the transmitter and receiver are locked
to an external 1PPS time reference.
Pref. Init. Rate Mode

From the pull-down list select the preferred algorithm to find the initial bitrate of a received
data stream.
116 WEB Interface
PCR
The default mode is PCR, in which case a number of consecutive TS packets of the first
PCR PID encountered are used to calculate the bitrate. If no PCR PID is found simple
bitrate measurement over a couple of seconds is used.
MIP
This mode may be used for a signal that does not contain any PCR PIDs, but does have
a DVB MIP PID (PID 21) as used in Single Frequency Networks. In MIP mode, two
consecutive MIP packets are used to estimate the bitrate. The input signal must be a
valid DVB-T feed in the sense that the MIP is valid, for this mode to work.
VBR
In this mode the unit attempts to read data from the input buffer at the rate entered in
the Max VBR bitrate input. If the incoming rate is higher than this a buffer overflow
alarm will be triggered.
FAST COARSE
In this mode the units attamps to set up the regulator very fast on the expense of pos-
sible jitter on the output. For ASI output this may initially create jitter outside of the
specification and should only be used when having IP -> IP transmission.
Expected PCR accuracy

The expected clock accuracy of the PCR in the input signal. The configured value affects how
far off the initial bitrate (determined from the incoming PCR) the buffer regulator may adjust
the output bitrate to compensate for input latency. The default value (25ppm) should be
sufficient to handle signals from professional DVB equipment at the same time guaranteeing
that the output bitrate does not deviate beyond 25ppm. If you want to synchronise to streams
coming from sources with less accurate clocks, you may have to configure a wider operation
range to allow the output clock to be tuned further off to avoid buffer over-/underflow.“
Max VBR bitrate

If VBR rate mode is chosen this parameter tells the unit the bitrate to use when reading from
the input buffer.
The Re-sync Conditions field:
Bitrate change
Checking this box will make the unit re-synchronise faster in the case of small bitrate changes.
PCR based bitrate measurements deviating 100ppm or more from the initially determined
bitrate causes immediate buffer re-synchronisation.
Latency limits (rel. to pref.)

Checking this box will make the unit re-synchronise if the measured latency exceeds the
configured limits set in the configured preferred latency.
The Regulator Status field allows inspecting the status of the buffer regulator.
Regulator state
This parameter shows the current state of the buffer regulator. The possible states are Stopped,
Rate Estimation, Coarse and Finetune. When data is received and an initial bitrate estimate
is found the regulator enters the Rate Estimation state, where the signal is analysed to check
WEB Interface 117
if a better estimate of the bitrate can be found. When a better estimate is found the regulator
switches to Coarse mode where the output bitrate is coarsely moved closer to the new rate.
From Coarse mode the regulator enters Finetune mode.
Initial bitrate
Here the exact initial bitrate found is displayed.
Current bitrate
This parameter shows the exact bitrate played out on the ASI port at the moment.
Measured bitrate
This parameter is an input to the regulator in the Rate Estimation and Coarse phases, and
shows the bitrate measured for the data stream since last re-sync. In the first minutes after
a re-sync this measurement depends on IP network jitter and is highly inaccurate. After a
few minutes of operation the value gets more and more accurate and can be compared to the
current bitrate to see how far off the target bitrate the regulator is operating.
Regulator output
Indicates the amount of correction the regulator must apply to the output bitrate, with respect
to the initially measured input bit rate, in order to avoid buffer under-/overflow.
Regulator operation range

Indicates the maximum clock correction (in ppm) that may be applied. This parameter is
affected by the “Expected PCR accuracy” parameter and is typically configured slightly wider
to allow headroom for buffer regulation.
Channel uptime
The elapsed time since last re-synchronisation occurred.
Number of re-synchs
Displays the number of re-synchronisations since the last unit power up, or since the Reset
Stats function was last used (see Section 9.5.2.1).
9.5.2.4 Copy
This tab is only visible if a Copy Input is selected in the Input Navigator.
The Main Configuration contains the following fields:
Enable input
If enabled, the Copy Input will receive packets from the Source Input.
Source input
Select the Source input, from where the packets will be copied. By clicking on the icon to the
right of the field, a list will pop up with all allowed Source inputs on the unit.
Input label
Custom label for the selected input.
The remainder of the page is similar to that of other input types, but lacks any physical properties.
118 WEB Interface
Figure 9.57 Copy Input
9.5.2.5 Services
The Services page displays information relative to each service present in the stream.
9.5.2.5.1 Service List
The Service List tab displays a list of services running in the selected input. Each service type is
represented by a symbol coloured to show the current alarm status of the service (figure 9.58).
Sort by
Selecting the SID or Name radio button sorts the list by service ID or service name, respec-
tively.
Clicking on a service name (folder name) brings up a tab navigator to the right of the list containing
more information about the selected service.
Details tab
The Details tab shows detailed information about the selected service. The service information
may be presented in one or two sections. The first section, Service Details, is always present and
consists of the following parameters:
Service ID
The service id of the selected service.
PMT PID
The program map table PID of the service.
WEB Interface 119
Figure 9.58 Service details overview when service list is not expanded.
PCR PID
The PCR PID of the service.
Total rate
The current bitrate of the service. The service bitrate is the sum of the bitrates of the PIDs
pertaining to the service (PMT, PCR, ECMs and the component PIDs signalled in PMT). If
PIDs are shared between services, the displayed sum of the bitrates of all services may exceed
the total bitrate of the transport stream.
Min rate
The minimum bit rate measured for this service since the last reset. Resets when the PID
rates are reset.
Max rate
The maximum bit rate measured for this service since the last reset. Resets when the PID
rates are reset.
In DVB mode the second section, Service SDT Details, will be present only if the SDT table is
present and analysed. It consists of the following parameters:
Service name
The name of the service.
Service provider
The provider of the service.
Service type
The type of service.
120 WEB Interface
EIT schedule signalled

Whether the EIT schedule information is signalled to be present for this service. This infor-
mation is extracted from SDT actual.
Scrambling signalled
Whether scrambling is signalled for the service. Interpretation of the Free_CA bit in SDT
actual.
EIT P/F signalled

Whether EIT present/following information is signalled to be present for this service. This
information is extracted from SDT actual.
Running status
The running status of the service as signalled in SDT actual.
In ATSC mode the second section is named Channel Details and shows the following parameters
from the VCT table if it is present and analysed:
• Channel name
• Major channel number
• Minor channel number
• Service type
• Modulation mode
• Channel TSID
• Access controlled
• Hidden
• Hide guide
Alarms tab
The Alarms shown in figure 9.59 tab lists all the current alarms related to the selected service. The
following information is provided:
Severity
The severity of the alarm.
Description
Bref description of the alarm.
Alarm ID
The alarm identifier.
Details
Some additional details.
WEB Interface 121
Figure 9.59 Service alarms overview
Descriptors tab
The Descriptors shown in figure 9.60 tab displays the list of the PMT and SDT descriptors of the
service.
Figure 9.60 Service descriptors overview
Component details
To list all components contained within a specific service click the arrow for the given service. The
expanded view is shown in Figure 9.61.
Each component is shown with the following information:
Component type symbol

Symbol showing the kind of component.
Textual description
A text description of the component type.
Type id
The component type id.
122 WEB Interface
Figure 9.61 Service details full component overview
PID
The transport PID number.
Clicking on a component in the left hand list of services and components opens a Components view
on the right hand side. On the top of this view is a toolbar with two buttons to switch between
Table and Rate views.
These views contain almost exactly the same information as the corresponding view on the PIDs
page, Section 9.5.2.6. The only difference is that in grid view a list of descriptors may be displayed
below the Components table when clicking on a component. A tree structure of descriptors is
displayed, if present, in the selected component.
9.5.2.6 PIDs
This page gives detailed information about the PIDs present on the input. Several different PID
views may be selected with buttons on the tool bar at the top of the page.
9.5.2.6.1 PIDs Grid
The Grid button selects a listing of the PIDs in table form, the Rate button selects a bar graph
representation, indicating dynamically the bit rate of each PID.
WEB Interface 123
Figure 9.62 PID Details, table view
The PID table contains the following columns:
Info
This column shows icons describing some aspects of the PID. The significance of the icons is
given below.
Figure 9.63 Status

icons in PID details
1. This icon is shown if there is an active CC error alarm related to the PID.
2. This icon is shown if the PID is a PCR PID.
3. This icon is shown if the PID is scrambled and the scrambling bit is odd.
4. This icon is shown if the PID is scrambled and the scrambling bit is even.
5. This icon is shown if the PIDs priority bit is set.
PID
This is the packet stream id.
Type
This is the packet stream type. Unsignalled PIDs have no type.
124 WEB Interface
Bitrate
This is the current bitrate of the packet stream in Mbit/s.
Min Rate
This is the minimum rate of the packet stream in Mbit/s since the last rate reset.
Max Rate
This is the maximum rate of the packet stream in Mbit/s since the last rate reset.
CCErr Cnt
This is a counter which shows the number of Continuity Count errors on this packet stream
since the last CC error count reset.
Ref. by Service
This is a list of services referencing the PID. If there are too many services to show in the cell,
holding the mouse over the cell will show a tool tip with all the services.
ECM PID(s)
This list the PID’s of the stream that contains Entitlement Control Messages.
Count
Number of packets counted for this packet stream since last counter reset.
Beneath the PID table are three buttons:
Reset CC error counts

This resets the CC error counters for all packet streams.
Reset min/max rates

This button resets the min and max bit rate measurements for all packet streams.
Reset packet counts

This button resets the packet counters for all packet streams.
9.5.2.6.2 PID rates
The PID rates sub-tab is shown in figure 9.64. To the left is the bar chart showing the PIDs and to
the right are some options for configuring the view.
Vertically, the chart displays one bar for each of the packet streams present on the input. Adjacent
to the PIDs the symbols shown in figure 9.63 are shown if relevant.
Horisontally, the bar chart shows the current rate and the minimum and maximum rates measured
for each packet stream. The blue bar shows the current rate. The grey bar shows minimum and
maximum rates. Holding the mouse cursor over a bar shows a tool tip with the rates as a numeric
value.
To the right of the chart, a field of options are provided to configure the view. The Sort by drop-
down menu on top lets the user sort the bar chart by different parameters. The Filtering frame lets
the user choose which PIDs to show. Checking the Hide null PID check box removes the null PID
from the chart. Unchecking any of the other check boxes removes the corresponding PIDs from
WEB Interface 125
Figure 9.64 PID Details, rate view
the chart. Below the Filtering frame the Reset min/max bitrates button is provided. Hitting this
button resets the min and max rates counters of all PIDs.
9.5.2.7 Tables
The Tables page shows detailed information about all the tables that are currently residing in the
input SI/PSIP database of the device. Accessing the related sub pages gives access to table contents
right down to byte level.
Which tables being currently analysed by the device is also displayed.
“Tables” tab
The button switches to a detailed view of the tables present on the input and analysed by the
device.
“Settings” tab
This button switches to a page showing what tables are being analysed.
“Table source settings” tab

This button switches to a page allowing the user to configure non-default source PID of
SI/PSIP tables.
126 WEB Interface
9.5.2.7.1 Tables
Figure 9.65 Table details, overview.
Figure 9.65 shows the table details in list view.

The left hand side of the page contains a tree showing the tables that are present on the input
and analysed by the device. The tables belonging to a specific folder are displayed to the right by
clicking on the folder.
Above the table the following information and buttons can be found:
Shown tables
The number of table that fall into the chosen folder compared to the total number of tables.
Shown sections
The number of PSI/SI/PSIP table sections displayed in the list.
Show ID’s as
Configure to view id’s and keys in hexadecimal or decimal notation.
The right hand side table of the sub page has the following columns:
Table
The type of information table and (in braces, []) the PID containing it.
TID
The table ID.
Primary
The primary extension ID of the table. Hovering the mouse cursor over the value displays a
tool tip describing the meaning of this key in the context of the table.
WEB Interface 127
Secondary
The secondary extension ID of the table. Hovering the mouse cursor over the value displays
a tool tip describing the meaning of the secondary ID in the context of this table.
Tertiary
The tertiary extension ID of the table. Hovering the mouse cursor over the value displays a
tool tip describing the meaning of the key in the context of this table.
Ver
This is the last received version of this table.
Age
The time elapsed since the table was last updated. Selecting a single table from the tree to
the left or double clicking a line within the table opens a view displaying the parameters of
that table. The parameters are the same as are shown in the table view.
9.5.2.7.2 Sources
Figure 9.66 Non-standard table source

PID configuration.
This page allows you to configure non-standard input PID values for the section filtering of indi-
vidual SI/PSIP tables.
The page is shown in figure 9.66 and contains a grid with the following columns:
Table
The table type to configure with its table ID in decimal in brackets.
Source PID
The input PID to use in the section filter for this table ID. Click the grid cell to edit it. Edited
fields are shown in yellow until applied.
128 WEB Interface
Default Src PID

The default PID used for this table type. Use this value if you want to go back to DVB com-
pliant input filtering.
After making the changes in the grid press Apply to activate the changes. You can then go back to
the table listing to see whether the expected tables are received on the new PID value.
Warning: Changing the PID values used in the input filtering must be
performed with care. If you specify a PID that contains a high bandwidth
PID it may cause the unit to malfunction.
9.5.2.7.3 Settings
Figure 9.67 Table analysis configuration.
In this sub page it is possible to select the table types to analyse. Each table type has a correspond-
ing check box. EIT Actual and EIT Other are further configurable as they allow the number of
days worth of data to be configured.
To commit changes to the settings on this page, click the Apply button located at the bottom of the
page. Press Refresh to reload the settings which may have been changed by another user.
Figure 9.67 shows the page as displayed in DVB mode.
In ATSC mode the page looks different, as shown in figure 9.68
WEB Interface 129
Figure 9.68 Table analysis configuration in ATSC mode.
• To be able to see programs and program components you must analyse at least PAT and
PMT.
• To see the service name for the services you have to configure analysis of SDTa (SDT
actual) for DVB services, or TVCT/CVCT for ATSC services
• In general alarms will not be generated for tables that are not configured for analysis.
Turning off analysis can free up CPU power and memory that may be used for other processing.
E.g. if PID 18 is high bandwidth, but is not interesting for analysis, then it could be beneficial
to disable EIT analysis (EITpfa, EITpfo, EITsa, EITso). In the Table Timeout Settings field it is
possible to change the timeouts used when detecting the presence of each table. The values are
specified in number of seconds.
Configuring larger time-out tolerances for tables that are occurring with non-standard repetition
intervals can reduce the number of alarms generated. Right-clicking each timeout parameter and
selecting Set to default resets the original value.
The timeout values are also used to generate Table missing alarms.
9.5.3 Switch
Information about the switches is displayed on a new page to the right by selection a switch. The
top part of that page is common for all sub pages and shows the name and the current alarm
status of the switch. Holding the mouse cursor over the alarm status indicator brings up a tool tip
showing the current alarms on this switch.
Underneath the name of the switch is a tab navigator, which contains three sub pages, Main, Inputs
and Alarms.
Main
This page shows a summary of the switch status, switch statistics and switch configuration.
Inputs
This page shows the switch input status and lets the user configure the switch inputs.
130 WEB Interface
Alarms
This page lets the user view the status of all alarms on the switch, and override the severity
of these alarms.
In all sub-pages for a selected switch a list of current alarms for that switch is shown. The list is
identical to the list displayed in the Current Status view, described in Section 9.3.1.
9.5.3.1 Main
Figure 9.69 Switch - Main
Main tab provides the switch status, switch statistics, switch configuration as well as switch wait
configuration.
Switch status field provides the status figure which shows the inputs/outputs of the switch, se-
lected input and indicates the alarm level. Holding the mouse cursor over the status figure indi-
cator brings up a tool tip displaying detailed information on the switch.
Switch statistics field indicates the number of automatic and manual switching that has been per-
formed beginning from the boot up or the last reset statistics button has been pressed.
The switch configuration field has the following entries:
Enabled
Control enabling/disabling of the switch. When disabled the switch will have no output,
and no matching will be performed.
Label
This is the name of the switch. It is used as alarm source text, and shown in the web interface.
WEB Interface 131
Figure 9.70 Switch Status
Automatic Switch
This sets the switching mode. When enabled, the unit will switch between inputs automat-
ically based on alarm levels per input. Manual switching may be performed regardless of
Automatic Switch enabled or not. Return switch (return to higher priority input automat-
ically) can be configured at ’Switch Input Configuration’ subpage. If disabled the unit will
remember the selected input, even during power loss.
Match Mode
This parameter controls how the internal matching module works. The options are designed
for various stream types. Seamless switching is only possible if an appropriate Match mode
is selected, and the switch has been able to find and lock to the current stream time offset. For
a seamless switch to be possible the streams must have equal symbols in the switch drawing,
and the alarm Seamless switch impossible must not be present. Alarm based and manual
switching between inputs is possible for all modes, except for Diversity mode (see below).
• Disabled: Disable matching logic for non-identical streams. Buffers will be kept at con-
stant level. Useful for non-identical streams, to avoid having alarms that streams are not
equal. Switches will not be seamless.
• Normal: Requires that the streams are bitwise identical, identical packet order and packet
content. Null packets distribution must also be identical. Typically used when a stream
is copied and sent through multiple paths without any rate adaptation.
• Diversity: Variant of Normal mode (i.e. requires bitwise identical streams), but limited
to two inputs. Alarms will still be triggered on each input, but not used for switching.
Manual switching is also disabled. When in Diversity mode, the switch will play out
what it considers the best packet from either input at any time. Basic stream errors like
sync loss, RTP sequence jumps, Transport Error Indicator and CC errors will be handled
seamlessly. CC errors and RTP sequence jumps might not be handled seamlessly in the
other modes, due to delay in alarm triggering. The Diversity mode requires minimal
132 WEB Interface
setup, and is targeted mode for identical signals that only suffer from basic transmission
errors.
• Ignore Null Packets: Variant of Normal mode, but Null packet distribution may be dif-
ferent between the streams. Data packets must still be identical both in packet order and
content, except for packets containing PCR stamps. The input rate may therefore be differ-
ent between the streams, and the output rate might therefore change when performing
a switch between inputs. This mode is useful for scenarios where one or more of the
streams has been subject to rate adaptation.
• Single PID: Special matching mode the switching will protect a single PID. When Single
PID mode is selected a box will be displayed below for configuration of the desired PID.
When a switch is performed the protected PID will not suffer from CC errors. However all
other PIDs might suffer from errors during a switch. Packet content of the configured PID
value must be identical except for PCR stamps, if any. This mode is aimed at applications
where services has been multiplexed, and input streams are not identical, but there is at
least one common service in the streams that are identical. For best performance, select a
video PID of high bitrate.
• MIP: Licensed feature. MIP matching is designed to protect the MIP packet during a
switch to keep DVB-T modulators running. The streams may be different except for the
MIP packets which are used to align the streams correctly. A switch performed in this
mode will be invisible to the DVB-T modulator, but any DVB-T receiver will experience
a short service interrupt. For this mode to work, the MIP packets must be synchronized,
contact Nevion for a list of compatible Nevion DVB-T SFN adapters.
• T2-MI: Licensed feature. Similar to MIP matching mode, but for DVB-T2. The streams
are matched and aligned using the DVB-T2 timestamps contained in the T2-MI timestamp
packets. The T2-MI stream must be synchronized, while the data within the T2-MI stream
may differ. The default PID for T2-MI is 4096, but the switch will auto-detect the PID con-
taining the T2-MI stream as long as PSI signaling is correct. A switch performed in this
mode will be invisible to the DVB-T2 modulator, but any DVB-T2 receiver will experi-
ence a short service interrupt. Contact Nevion for a list of compatible Nevion DVB-T2
Gateways.
Initial Buffering
The purpose of initial buffering is to handle delay variations between the inputs during op-
eration. In case the streams drift apart the buffers must be large enough to compensate for
delay variations. For a new Initial Buffering value to be applied, Reset Delays (see below)
must be initiated.
Max delay
The max delay parameter is used to control the maximum delay through the unit. If either
of the delays through the unit tries to increase beyond the configured Max delay, it will be
truncated to the configured Max delay.
Automatic reset
If either of the delays through the unit tries to increase beyond the configured Max delay the
unit will automatically reset delays to it’s initial value. This is the same operation as pressing
Reset Delays.
WEB Interface 133
Reset Delays
Initiating Reset Delays should be initiated for the following reasons:
• Applying a new Initial Buffering value.
• Restoring initial input buffer values. This will typically be required if during operation
either input has drifted and consumed all of it’s buffer. If this occurs an alarm will be
triggered, and a larger Initial Buffering value should be applied to account for larger drifts.
By initiating Reset Delays, the switch will discard the currently measured delay between the input
streams and find new delays. After a Reset Delays have been initiated the lagging input will be
buffered by the configured Initial Buffering value, while the other inputs will be buffered by the
configured Initial Buffering value plus the delay difference compared to the lagging input.
Note: Resetting of the delay will cause a break in the output signal.
Switch Wait Configuration
The switch wait configuration is used to control the wait time from an alarm condition occurs until
the switch is performed. The alarm settings applies to all inputs in a switch.
The only alarms considered for switching are the input alarms for the inputs of the switch. Generic
device alarms and output alarms will not be considered.
It is possible to configure separate Switch Wait times per alarm level, such that for example an
Critical alarm condition will trigger an immediate switch, while a Major alarm must be present
for at least 20 seconds before a switch is performed.
Note: Many alarms have an off hysteresis to avoid rapid triggering of the
same alarm. The “Off time” is a configurable parameter per alarm that
defines how long an alarm will stay active after the last error condition
have occurred. This must be taken into account when configuring the Switch Wait
Configuration. See section 9.5.2.2 for further details.
Note: It is not possible to configure a shorter wait time for a less critical
alarm. For example Switch Wait for Warning severity must be equal or
higher than Switch Wait for Minor severity.
Note: Switching on Sync Loss is always instant, and independet of alarm

level.
134 WEB Interface
In order to commit the changes to the configuration, press Apply button at the bottom of the page.
The Reset Stats button is used to clear statistics counters for the switches. The Clear Auto sw.
Alarm button is used to clear the automatic switch alarms.
9.5.3.2 Inputs
Switch Input Status field shows an overview of the input streams currently attached to the specific
stream. Figure 9.71 shows the graphical user interface of the switch input page. The following
entries are listed:
Input
Lists the current inputs of the switch.
Alarm
Indicates the alarm state of each input.
Valid
This field indicates that the input stream is Valid. If Valid and not selected the input will be
considered the next time a switch is performed. If not Valid and selected the switch will try
to switch to the highest prioritised input that is Valid. If the input is not valid, a reason will
be stated.
Grp
The Match Group icon indicates which input streams that are equal. Streams that are equal
contains the same TS packets in the same order, and the switch will be able to perform seam-
less switching between inputs belonging to the same Match Group. A seamless switch means
that the output of the switch will be unaffected when the switch is performed. For a switch
with 4 inputs, where 2 and 2 inputs are identical the switch will be able to create 2 match
groups, with 2 inputs in each.
Note: If a switch will be seamless or not will not be considered when

performing a switch. The first Valid input with the highest priority will
always be selected when performing a switch. Instead make sure that
identical inputs are next to each other in the prioritised list of inputs to get a
seamless switch.
Delay
This field presents the applied delay in milliseconds to each input. For inputs belonging to
the same Match Group (Grp) the delays will be set to compensate for the delay difference
between the streams, while also applying the Initial Buffering value to the lagging input.
Note: The Delay of the selected input to the switch will always remain
constant, while the delays of the other inputs will change if the input
streams drifts relative to each other.
WEB Interface 135
Figure 9.71 Switch - Inputs
Switch Input Configuration shows a prioritised list of the switch inputs. This configuration reflects
how the switch operates in Automatic switch mode. At the bottom of this field it is also possible to
add and remove inputs and also to perform manual switches. The following entries are present:
Input
Specifies the input streams to the switch. The top item in this list has the highest priority. On
the right side there are two arrows to control the priority of the inputs of the switch.
Return
Specifies if the switch should try to return to the selected input if the input is considered
valid. The switch will always try to choose the highest prioritised input that is ready and has
the return field enabled.
Max severity
Max severity defines the maximum alarm severity an input can have to make it valid. The
alarm severity in Alarms column under Switch Input Status will be compared against the
Max severity parameter to decide if the input is Valid or not. If the alarm severity is lower
than or equal to the specified severity, the input is considered Valid. For example if the Max
severity is configured to Warning [3], any alarm severity worse (closer to Critical [6]) than
Warning [3] will make this input not Valid as an input source of the switch.
Note: All alarms has a default alarm severity, but it may be reconfigured
for each input. See section 9.5.2.2 for details.
Return wait
Specifies the minimum time to stay away from a previously used input before returning.
For example if Return wait is configured to 20 seconds, and the switch switches away from
the input, the input will not be considered valid again until the input again is valid and 20
seconds have passed. This may be used to avoid rapid switches between inputs.
136 WEB Interface
9.5.3.3 Alarms
The Alarms sub page allows the user to configure the alarms for the input switch. It works identi-
cally to and is described under Device Alarms in section 9.4.2.1.
Figure 9.72 Switch - Alarms
9.6 Outputs
The Outputs page contains all information and settings that apply to the output ports of the device.
The navigation list to the left lets the user select which IP output or Switch output to view, or to
select Outputs Overview to view a summary of all the outputs of the device.
9.6.1 Outputs overview
This page shows a short summary of all the IP Outputs allocated to each ’Switch’.
Figure 9.73 Outputs overview
WEB Interface 137
Enable
This shows whether the output is enabled or not. The output enabled or disabled for an
output by clicking this check box and hitting apply.
Output
The name of the output.
Source
This indicates which switch is sourcing the output port.
Destination
The output destination: IP interface address.
Total Bitrate
The total bitrate of the transport stream currently transmitted on the output in Mbit/s.
Effective Bitrate
The effective bitrate (total minus null packets) of the transport stream currently transmitted
on the output in Mbit/s.
Alarm
The current alarm status of the output is shown as a coloured circle.
9.6.2 (Switch) Output
When selecting an output a new page on the right hand side with information about the selected
output is displayed. The top part shows the name and the current alarm status of the output. See
figure Figure 9.74. All current alarms related to the output are displayed in a tool tip by holding
the mouse cursor over the alarm status indicator.
The tab navigator contains two sub-tabs:
Main
This page lets the user configure several parameters of to the chosen output.
Alarms
This page displays the status of all alarms on the output, and lets the user override the severity
of these alarms.
9.6.2.1 Switch Main
The Switch Main page shows the switch status and lets the user configure the IP destinations for
the switch.
The Switch Status field provides the graphical presentation of the inputs/outputs of the switch,
selected input and the alarm level. Holding the mouse cursor over the status figure indicator
brings up a tool tip displaying detailed information on the switch.
If the units is equipped with ASI connectors there will be a frame showing ASI configuration and
a list of current ASI outputs from the current switch.
The ASI Outputs Configuration field:
138 WEB Interface
Figure 9.74 Output main page
ASI mode
Set transmission format for the ASI output, either Spread or Burst mode.
Packet length
Set TS packet length. 188 or 204 bytes. If using 204 bytes packets and having 188 bytes on the
input, the unit will insert 0xff in the 16 last bytes.
The ASI Outputs field shown in figure 9.75 lists the current ASI outputs of the selected switch.
Figure 9.75 Multiple

ASI destinations
Add ASI output

Add ASI output copies to this switch. In total there are 4 ASI outputs, and it is possible to
assign all outputs to one switch. ASI outputs may however not be chosen entirely freely. An
ASI output can not be the output of a switch if the corresponding ASI input is the source
of another switch. 1.Out is the corresponding output to 1.In and so on. This limitation is
WEB Interface 139
present to ensure that the outputs have a logic output on power loss. If the corresponding
input is not used as a switch source, the corresponding output may be set freely as the output
of any switch.
Set to Passive
Setting an ASI output to passive automatically removes the output from the switch, and sets
the ouput to passive mode. The output will then be directly wired to it’s corresponding input.
For example removing output 4.Out will wire it directly to 4.In. If there is a signal on 4.In,
this signal will be transmitted on 4.Out. This will also be the case even if 4.In is used as a
source for any other switch.
The IP Outputs Configuration field:
TS packets per frame

Sets the number of transport packets that will be included in an Ethernet frame. The maxi-
mum number is 7 to avoid fragmentation of the resulting IP packets.
Figure 9.76 Multiple

IP destinations
The IP Destinations field has a table view ( Figure 9.76 ) containing a tick box to enable or disable
each output in addition to showing the status of each output. Each output is configured in the
dedicated page, reached by double-clicking on the entry in the table.
Removing an IP destination is done by highlighting the output to delete, clicking Remove Destina-
tion and then clicking Yes in the pop-up box. This is exactly the same as selecting the appropriate
IP destination in the navigator list.
9.6.2.2 Alarms
The Alarms page lets the user configure and view the status of all alarms belonging to the selected
output. The page functions exactly like the input alarms page, except it is not possible to copy
settings from a different output. (See Section 9.5.2.2).
9.6.3 Output to IP destination
If an IP destination has been allocated to a ’Switch’ this is shown in the Outputs navigator list.
Clicking the navigator entry opens the page to edit the IP destination settings.
140 WEB Interface
Note: The IP output must be added before configuring it. Refer to

Section 9.6.2.1.
This page consists of the sub tabs Main and Ping. If Forward Error Correction has been enabled
the FEC tab is also visible.
9.6.3.1 Main
This page is shown in Figure 9.77.
Figure 9.77 IP Configuration.
The Basic IP Config field:
Enable
If this box is checked, the generated transport stream will be played out over IP using the
shown parameters.
Destination host
Identifies the destination for the data stream. The identification can be set by entering the
destination IP address directly, or by specifying the machine’s DNS name. Use the button to
the right of the field to toggle between the modes.
If you use IP address mode, the address entered may be either a unicast address or a multicast
address.
If you use host mode, you can enter a local host name or a fully qualifying host name which
includes the domain name. The device will resolve the name to an IP address by asking the
DNS server. The DNS name will be regularly queried, and if the name is not resolving any
more, the data transmission will be stopped.
WEB Interface 141
DNS servers are either configured manually as described in Section 9.4.4.2 or automatically
when using DHCP, see Section 9.4.4.1.1.2.
UDP destination port

Enter the UDP destination port to use when transmitting data over IP. The UDP destination
port is used by the receiver to separate one stream from another. UDP port numbers are in
the range 1-65535.
Warning: Please ensure that there is no conflict in UDP ports in use. Pay
special attention to the fact that FEC data are always sent on UDP ports
two higher than the media port and four higher than the media port, e.g.,
if the UDP destination port is 5510, column FEC UDP port is 5512 and
row FEC UDP port is 5514.
Protocol
Select UDP or RTP transmission mode. See Section 6.1.1 for more information on this.
UDP source port

Enter the UDP source port to be used in the outgoing UDP frames. UDP port numbers are in
the range 1-65535. Note that the receiver unit may not check the source port when receiving
streams. FEC frames are transmitted using the same UDP source port as the media frames.
Packet length
Enter the number of 188 byte MPEG-2 transport stream packets to map into each UDP frame.
Valid values are between 1 and 7. Normally 7 is the best choice to reduce overhead and
Ethernet frame rate. For very low bitrate streams, less than 7 packets per frame may be used
to advantage reducing the delay through the unit.
Type of service (TOS)

Enter Type of Service parameter as a byte value to be set in the Type-of-Service (TOS) field
in the IP header as specified in RFC-791. This parameter is used for Class-of-Service priori-
tisation. Its usefulness depends on routers honouring this field. Please refer to Appendix D
“Quality of service – Setting Packet priority” for further details.
Time to Live (TTL)

Enter Time to Live parameter as a byte value to be set in the Time to Live (TTL) field in the
IP header as specified in RFC-791.
Manual destination interface

If you want to manually set the interface you want the data to be transmitted through, check
the box and select the wanted interface. If you wish to use the IP routing configuration leave
the box unchecked.
The Advanced IP Config field:
Use multicast router

Click this box to enable use of multicast router. The address of the multicast router is the
same for the entire unit and is configured in the Network sub-page of the Device Info page.
When this option is enabled, the MAC address used when configuring a multicast destination
142 WEB Interface
IP address will be resolved to the IP address of the multicast router. If not using the multi-
cast router option, multicast addresses automatically resolve to dedicated multicast MAC
addresses.
Override VLAN priority

Priority is normally configured per VLAN interface. It is possible to override the VLAN
priority field for the output stream by checking this box and entering a new priority value.
Static destination MAC

Static MAC destination address is used to specify a fixed MAC destination address in out-
going streams. This makes it possible to transmit to a destination host over a one-way link.
The static MAC address setting then replaces the normal ARP lookup. To enable static MAC,
check the box and enter a destination MAC address.
Override source IP
Option to use a different IP address than the one on the Ethernet interface when transmitting
IP frames with transport stream data.
Synchronization source ID
Option to control SSRC (Synchronization source) identifier field transmitted in RTP header
of data stream.
Random
Use a random number as suggested in RFC3550 and allowed by SMPTE2022-1. A new
random number is generated every time channel is enabled for transmission. The same
random number is shared between all small-casts. This is the default mode.
Manual
Configure the SSRC ID field to be used manually. Allowed to adapt to any special re-
quirements or get around compatibility issues.
The IP Status field provides real time status information pertaining to the selected output.
Current interface
The interface the IP stream will be transmitted through. If Manual destination interface is en-
abled the configured interface will be shown. If not, the interface depends on the configured
destination address and the configured IP routing entries.
DNS Resolved
If host name mode for destination host parameter, this field shows whether the name has
successfully been resolved to an IP address.
DNS Resolved IP
This field shows the IP address that was found for the specified host name when specifying
destionation by name.
IP Resolved
Yes when the MAC address of the configured IP destination address is resolved. The para-
meter is always Yes when multicast is used without a multicast router. No when the MAC
address is not yet resolved by ARP lookup.
WEB Interface 143
Dest. MAC address

Shows the destination MAC address used for the stream. This may be the MAC address of the
receiving unit, or the gateway if the receiving unit is on another network. If using a multicast
destination IP address without enabling multicast router, the field shows the multicast MAC
address corresponding to the configured multicast group. In the case of multicast router,
the MAC address resolved for the multicast router is shown. When the address is still not
resolved this field displays the value 00:00:00:00:00:00.
Group Ethernet rate

The bitrate of the IP frames containing this MPEG-2 transport stream and any FEC data re-
lated to this stream.
Data Ethernet rate

The bitrate of the MPEG-2 transport stream contained in the IP stream.
Column FEC Ethernet rate

The bitrate of the column FEC contribution to the IP data.
Row FEC Ethernet rate

The bitrate of the row FEC contribution to the IP data.
Ethernet frame rate

Number of ethernet frames transmitted per second.
Synchronization source ID
The currently transmitted SSRC ID in the RTP header.
9.6.3.2 FEC
This page allows configuring and applying forward error correction data to the output IP transport
stream.
Figure 9.78 IP output FEC page
144 WEB Interface
In the FEC Configuration field forward error correction is enabled and configured for each indi-
vidual output:
FEC mode
From the pull-down list select Disabled to not apply FEC, Column only to apply one-dimensional
FEC (i.e. add column FEC datagrams, only), or Column and Row to apply two-dimensional
FEC (i.e. add column and row FEC datagrams).
FEC overhead
Gives an instant check of the overhead resulting from the applied FEC.
Resulting total rate

Shows the actual bit rate of the IP stream including FEC, if applied.
The Common FEC Configuration field allows setting of common parameters that will be applied
to the FEC processor in general:
Number of columns (L)

The number of columns used in generating the Row FEC data.
Number of rows (D)

The number of rows used in generating the Column FEC data.
Skew
Check this box to enable a skewed FEC matrix.
For a detailed description of FEC usage, refer to Appendix C.

The Status field shows the IP status resulting from adding FEC processing:
Group Ethernet rate

The bitrate of the IP frames containing this MPEG-2 transport stream and any FEC data re-
lated to this stream.
Data Ethernet rate

The bitrate of the MPEG-2 transport stream contained in the IP stream.
Column FEC Ethernet rate

The bitrate of the column FEC contribution to the IP data.
Row FEC Ethernet rate

The bitrate of the row FEC contribution to the IP data.
Column UDP port

The UDP port used for column FEC data.
Row UDP port

The UDP port used for row FEC data.
WEB Interface 145
9.6.3.3 Ping
Figure 9.79 Ping page
Ping can be used to resolve network problems, avoid flooding and avoid time-out of MAC address
lookup by the transmitter or a specific network component on the way to the receiver. Ping helps
resolving such issues by sending a short message regularly. This feature also makes it possible for
the receiver to monitor if an active sender is present.
The Settings field:
Enable Unicast Peer Ping

Check this box to enable Unicast Peer Ping. This enables regular pinging of the receiving
device.
Interval
Set the interval in seconds between each Ping.
The Status field displays the status of the on-going pinging session:
IP destination
The address of the device receiving the Ping requests.
Time to live
This figure indicates the number of routing points the Ping message may encounter before it
is discarded.
OK responses
Indicates how many valid Ping responses have been received.
Timeouts
Indicates how many of the sent Ping messages timed out, i.e. did not provide a valid response
within the allowed time.
146 WEB Interface
Last roundtrip
The time taken from last sending the Ping message until the response is received.
Min roundtrip
The minimum time taken from sending a Ping message until the response is received.
Max roundtrip
The maximum time taken from sending a Ping message until the response is received.
Clicking the Clear Statistics button resets the counts in the Status field.
9.6.3.4 RIP-2
The TNS544 is equipped with RIP-2 functionality. If enabled, the TNS544 will transmit RIP-2
messages regularly. The content of the RIP-2 messages is set as specified in this section.
RIP-2 messages are sent with one entry each. The metric of this entry can be set either manually
or automatically based on the current alarm level of the unit. This information may be used by
network routers to select the source with the lowest metric; i.e. in effect automatic redundancy
switchover.
Note: Manual destination interface must be enabled when using RIP-2

and source IP must be overridden to identify each stream individually.
Figure 9.80 shows the layout of the RIP-2 page.
Figure 9.80 RIP-2 page
The Related IP Destination Settings field shows IP destination parameters that RIP-2 depends on.
Manual destination interface

Must be turned on when using RIP2.
Override source IP
Must be enabled and set to a unique source address for each stream transmitted.
The RIPv2 Settings field allow configuring of parameters are as follows:
WEB Interface 147
Mode
Controls the mode of the RIP-2 engine.
Off
No RIP-2 messages are sent.
Auto
RIP-2 messages are sent. The metric in the RIP entry is set according to the current unit
alarm state. If the alarm state is critical, the “Metric on critical” value is used. If the
alarm state is “OK”, the “Metric on clear” value is used.
Alarm
RIP-2 messages are sent. The “Metric on critical” value is used, independently of the
alarm state.
Clear
RIP-2 messages are sent. The “Metric on clear” value is used, independently of the alarm
state.
Metric on clear
The metric number to be used in the RIP-2 messages when there are no active alarms in the
unit.
Metric on critical
The metric number to be used in the RIP-2 messages when there are at least one critical alarm
present.
Destination
The IP destination address to use for the RIP messages.
TTL
Time to live to use in IP header of RIP messages. Default value is 1 since these messages are
normally intended for first router.
Enable manual next hop

If set, the RIP-2 messages will specify the next hop as defined in the “Next hop address”
field.
Next hop address

The address to be used for the next hop.
Route tag
Corresponds to the route tag field in the outgoing RIP-2 messages.
Update interval
Specifies the average update interval for the RIP-2 messages. Note that the TNS544 adds
some random delay to avoid sending messages too regularly.
Hold time
Hysteresis time to keep signaling alarm level metric after alarm level is going from critical to
non-critical, to avoid toggling situations when alarm is turned on and off continuously.
148 WEB Interface
Send PIM Hello

Enable transmission of ’PIM hello’ messages. Messages are transmitted to multicast IP ad-
dress 224.0.0.13. This enables routers to accept IP multicast packets originating from foreign
networks.
The RIPv2 Status field show the following parameters:
RIP-2 message count

The number of RIP-2 messages transmitted.
Current metric
The current metric used in outgoing RIP-2 messages. Will be either the “Metric on clear” or
the “Metric on critical” value.
Next hop
The next hop address.
SNMP 149
10 SNMP
The product supports
SNMP – Simple Network Management Protocol – for remote control and supervision. SNMP uses
an extensible design, where management information bases (MIBs) describe the structure of the
management data of a device subsystem. The primary purpose of SNMP is to export alarm and
status information, but a range of MIBs related to configuration settings are also supported.
10.1 SNMP agent characteristics

The SNMP agent supports the SNMPv2c (Community based SNMPv2) protocol. All custom MIBS
are written in SMIv2 format. The SNMP agent will accept both SNMPv1 and SNMPv2 messages.
The SNMP agent uses the normal UDP sockets for communication and listens for requests at UDP
port 161.
Both legacy SNMPv1 traps and SNMPv2 notifications are supported. It is however recommended
to use the new SNMPv2 notification types for new deployments.
10.2 MIB naming conventions

All custom MIB files start with the prefix VIGW. MIBs that defines data structures that are not con-
nected to one specific product start with VIGW-PLAT. Most MIBs are of generic type and therefore
starts with this prefix.
Some MIB-files are very custom and corresponds to a specific product only. These MIBs start stats
with the prefix VIGW-PROD.
From Nevion you will receive a set of MIB files. There may be more MIB files than the TNS544
support, but the relevant MIB files are listed here.
10.3 MIB overview

This section describes the different MIBs. Detailed description of MIBs is included later on in this
document.
10.3.1 Supported standard MIBs
RFC1213-MIB
MIB-II according to RFC1213.
10.3.2 Custom MIBs
VIGW-TC-MIB
Describes common textual conventions (data types etc.) used throughout the entire MIB set.
For example, definition of alarm status numbers are defined in this MIB.
150 SNMP
VIGW-BASE-MIB
Defines the top level MIB structure including the enterprise specific root node for device
control (1.3.6.1.4.1.22909).
VIGW-UNIT-MIB
This is a generic MIB module that defines parameters supported by all products. It is the
main source for alarm and status related information. The following objects are examples of
contents in this MIB:
• Top level alarm status
• Table of current alarms
• History of last transmitted TRAP messages
• Trap destination list
• Force reset of the unit
• TRAP/NOTIFICATION definitions
• Other, general product information:
− Serial number
− SW version
Note: When setting values in the unitAddressTable it is important to send

all values for one interface in the same request. This is to prevent the unit
from entering an undefined intermediate state.
VIGW-PLAT-PHYSICAL-PORTS-MIB
This MIB contains status and configuration for the physical ports on the unit. Parameters
include:
• Controlling port direction if supported
VIGW-PLAT-TS-MIB
This MIB contains Transport Stream related information for each of the transport stream in-
puts. It is supported by transport stream related products that are able to analyze incoming
transport streams. For each input transport stream, the following information is available:
• Transport stream sync status and total/effective bitrate.
• Present PIDs with information about bit rates and CC errors.
• Present services with information about service name and service ID.
VIGW-PLAT-TSOUT-MIB
This MIB is supported by products that can generate an outgoing transport stream. Parame-
ters include:
SNMP 151
• Control of output bitrate and other ASI parameters (spread/burst mode).
• Control of MIP insertion (if enabled in the product)
− OFDM modulation parameters
− Enable/disable of MIP insertion
• Control of PSI/SI table playout
VIGW-PLAT-TS-INPUTSWITCHING-MIB
MIB containing parameters related to control of second generation input port redundancy
switch with more than 2 sources.
VIGW-PLAT-TS-IPTRANSPORT-MIB
This MIB contain status and control parameters related to the data IP receive and transmit
functionality.
10.4 SNMP related configuration settings

The SNMP related configuration parameters are located on the Device Info/SNMP settings page
in the GUI.
10.4.1 Community strings
The community strings are used to provide simple password protection for SNMP read and write
requests. The strings can be configured from the GUI. It is also possible to configure the commu-
nity strings to be used for trap messages.
10.4.2 Trap destination table
The Trap Destination table lets the user configure the external entities that should receive SNMP
traps from the device. The table is both accessible via VIGW-UNIT-MIB and the product GUI (De-
vice Info/SNMP settings). A maximum of 8 different destinations are supported.
10.4.3 Trap configuration
All supported traps are currently defined in the VIGW-UNIT-MIB. Via the GUI you can control
the trap forwarding. For detailed information about each trap and the corresponding variable
bindings, please see Section 10.5.
Trap version
This parameter controls the TRAPs that will be sent from the device in case of alarm condi-
tions.
SNMPv1 (Legacy)
If this option is selected, the unit will send the traps located under the vigwLegacy-
Traps MIB node. These traps are included mostly for historical reasons and it is not
recommended to use these for new deployments.
152 SNMP
SNMPv2
This is the recommended setting. The traps defined under the node unitNotifica-
tions will be used while the traps under the node vigwLegacyTraps will be disabled.
Status change traps
If enabled, the unit will transmit unitAlarmStatusChanged traps whenever the top level
alarm status is changed for the unit.
Alarm event forwarding

This setting controls how internal alarm event will be forwarded as TRAP messages. Adjust
this value if you want to control the number of traps sent from the unit. The settings are only
used when SNMPv2 is selected as TRAP version. The settings are:
Disabled
No specific event traps are transmitted when alarms are raised or cleared. (The unitA-
larmStatusChanged trap may however be transmitted).
Basic
The device forwards alarms as traps on a basic level. No information about subid3 will
be transmitted.
Detailed
The device forwards alarms as traps. If there are sub-entries that are using the subid3
value, each sub.entry will be transmitted in separate trap messages.
10.5 Alarm/status related SNMP TRAPs

All TRAP messages are defined in VIGW-UNIT-MIB. This section describes each trap message.
10.5.1 The main trap messages

The main (SNMPv2) trap messages are defined under the unitNotifications node in VIGW-
UNIT-MIB. The messages are described briefly in Table 10.1.
10.5.2 Severity indications
All alarm event traps (i.e. all traps defined in Table 10.1 except unitAlarmStatusChanged) con-
tain a severity field which is encoded according to the definition below:
Severity Description
1 Cleared
2 Indeterminate
3 Warning
4 Minor
5 Major
6 Critical
SNMP 153
Table 10.1 List of SNMPv2 traps
unitAlarmStatusChanged This trap is sent when the top level unit alarm status (indicated by the
unitAlarmStatus variable) changes. The trap indicates both the old and new alarm
level. Transmission of this trap type can be enabled/disabled through configuration.
unitAlarmAsserted This trap is sent when an internal alarm is raised. No subid3 information is
included. A corresponding unitAlarmCleared trap is sent when the alarm cause is
cleared.
unitAlarmCleared This trap is sent when an alarm condition previously indicated with
unitAlarmAsserted is cleared.
unitAlarmEvent This trap is sent when an alarm event (with no on/off state) is generated. No
corresponding “cleared” message is expected for these traps. A typical example is an
event like “User logged in”.
unitDetailedAlarmAsserted This trap is a more detailed version of unitAlarmAsserted. subid3 information is
included in addition to the basic parameters defined in unitAlarmAsserted.
unitDetailedAlarmCleared This trap is sent when an alarm condition previously indicated with
unitDetailedAlarmAsserted is cleared.
unitDetailedAlarmEvent This is a more detailed version of unitAlarmEvent. subid3 information is included
in addition to the basic parameters defined in unitAlarmEvent.
10.5.3 Alarm event fields
A description of the fields in the alarm event traps is presented in Table 10.2. Most of the fields
are entries from the unitEventHistoryTable. The instance identifier for each variable binding
corresponds to the index in this table. This index is of kind CircularLog and will wrap around
at 2 32.
Table 10.2.a Variables in SNMPv2 traps and their meanings
Field Description
unitEventSeverity This field indicates the severity of the alarm, 2-6. 1 will never be used, as this condition is
indicated by transmitting a unitAlarmCleared message.
unitEventAlarmType This is an integer that describes the alarm type. Please refer to alarm documentation for
description. From this type, one can extract the actual meaning of the subid1 and subid2
values in the message.
unitEventAlarmId A unique identifier for this alarm type. Refer to alarm documentation in the user manual
for values.
unitEventAlarmName A fixed name corresponding to the alarm id.
unitEventRefNumber This field is provided to easily match asserted/cleared alarms. In the cleared alarm it is set
to the same number as in the asserted alarm.
unitEventSubId1 The first subidentifier to identify the source of the alarm. For products with single base
boards it is typically set to a fixed value (0 or 1) and can be ignored.
154 SNMP
Table 10.2.b Variables in SNMPv2 traps and their meanings
Field Description
unitEventSubId2 This field’s purpose is dependent on the alarm type (alarm id). For some alarms it is not
used and set to zero. For other alarms, it may e.g. indicate the channel/port number for
the entity that generated the alarm.
unitEventSubId3 This field provide an even more detailed description of the alarm source. This field is only
present in the “detailed” type of trap messages (unitDetailedAlarmAsserted,
unitDetailedAlarmEvent). It’s usage is dependent on the alarm ID. For example, in
transport stream related alarms, subid3 is used to indicate the PID value that caused the
alarm.
unitEventSourceText A textual description of the source of the alarm. This is typically a textual description of
the subid1 and subid2 fields. For example, for transport stream related alarms, the text
indicates the name (with label) of the port that generated the alarm.
unitEventSubId3Label This field is fixed and indicates the label (meaning) of the subid3 field, contained in the
unitEventSubId3 variable. It is intended to make it easy to log the alarm.
unitEventDetails This is a generic text string that contains more details related to the alarm event. It’s
usage and content is dependent on the alarm ID.
unitAlarmStatus This variable contains the new, top level alarm status of the unit after the condition
leading to this trap messsage. It may be used to quickly update the top level status for the
device after receiving the trap message.
10.5.4 Matching of on/off traps
As mentioned previously, a unitAlarmCleared message is sent after a unitAlarmAsserted

message and a unitDetailedAlarmCleared message is sent after a unitDetailedAlarmAsserted
message.
The “cleared” event contains exactly the same identifiers as the “asserted” trap. This includes the
alarm ID, subid1, subid2 and subid3 fields. This set of four identifiers uniquely identifies the
source of an alarm.
A more easy way to match the traps is by using the unitEventRefNumber field. This is a simple
integer that is the same in an “asserted” trap and in a “clear” trap.
10.5.5 Legacy trap messages
Note: The information in this section relates to trap definitions that

are marked as deprecated in VIGW-UNIT-MIB. They are included for
backwards compatibility with earlier product versions and should not be
used for new deployments.
The legacy traps are defined under the vigwLegacyTraps node. Transmission of these traps is
specified by selecting “SNMPv1 (Legacy)” for the trap version field. The format of these traps
follow the SNMPv1 trap format.
SNMP 155
In contrast to the SNMPv2 alarm messages, the SNMPv1 messages has its severity implicitly en-
coded in the trap type.
The trap messages are defined in Table 10.3.
Table 10.3 List of legacy (SNMPv1) traps
alarmCleared This trap is sent when an alarm goes off (i.e. is cleared) in the system. The binding
unitTrapHistoryRefNumber matches the corresponding unitTrapHistoryRefNumber in
the “raise” trap message.
alarmIndeterminate This trap is sent when an alarm with severity level “notification” (level 2) is generated.
alarmWarning This trap is sent when an alarm with severity level “warning” is generated.
alarmMinor This trap is sent when an alarm with severity level “minor” is generated.
alarmMajor This trap is sent when an alarm with severity level “major” is generated.
alarmCritical This trap is sent when an alarm with severity level “critical” is generated.
All these trap messages contain variable bindings from the unitTrapHistoryTable. This table
is filled up with historical trap messages, only when SNMPv1 mode is selected.
The fields in these traps are fetched from the unitAlarmTrapHistoryTable. The meaning of
these fields correspond to the fields in the unitEventHistoryTable for SNMPv2 traps and are
not described in more detail here.
10.6 Using net-snmp to access MIB information

Net-SNMP is a useful collection of free command line tools that can be downloaded from http:
//www.net-snmp.org/. The WEB site provides installation packages for several operating sys-
tems, including Windows.
The most important tools that can be utilized in scripts etc. is snmpget for get operations and
snmpset for set operations.
The WEB site and the tools provides extensive usage information. We do however present some
examples in this chapter for convenience.
10.6.1 Reading a parameter with snmpget
The command line tool to read an SNMP parameter is snmpget. The following example shows
how the command is used to read system up time from a device:
snmpget -v 2c -c public <ip-address> sysUpTime.0

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (250792000) 29 days, 0:38:40.00
Note the following parameters used:
-v 2c
This indicates that the version to be used is 2c. This is important as the default value is 3,
which is currently not supported.
156 SNMP
-c public
This is the community string (password) used for the request. It should match the configured
SNMP agent settings. The default value is “public”.
<ip-address>
This is the IP address for the device to read from.
sysUpTime.0
This is the OID for the parameter to read. Since we read a scalar value, we need to add .0 to
the OID from the MIB. Note that it is legal to use a numerical OID in this list; the OID must
match the parameter definition in the MIB file.
10.6.2 Writing a parameter with snmpset
The command line tool to set an SNMP parameter is snmpset. The following example shows how
the command is used to change the system name (sysName) for a device:
snmpset -v 2c -c private <ip-address> sysName.0 s "New name"

SNMPv2-MIB::sysName.0 = STRING: Siggens
Note the following parameters used:
-v 2c
This indicates that the version to be used is 2c. This is important as the default value is 3,
which is currently not supported.
-c private
This is the community string (password) used for the request. It should match the configured
SNMP agent settings. The default value for write access is “private”.
<ip-address>
This is the IP address for the device.
sysName.0
This is the OID for the parameter to change. Since we read a scalar value, we need to add
.0 to the OID from the MIB. Note that it is legal to use a numerical OID in this list; the OID
must match the parameter definition in the MIB file.
s “New name”
This is the parameter type and value. We use “s” to indicate a string and “New name” is the
actual string value. The type should match the type defined in the MIB file.
Examples of Use 157
11 Examples of Use
11.1 Introduction
This chapter offers a small selection of different practical examples of use of the TNS544, with
corresponding recommended configuration steps, pointing to the section in Chapter 9 where the
relevant configuration pages are described.
11.2 Installation in a system

When installing the device in a new environment, there are a few parameters that typically need
to be configured. These steps are the same for all the cases studied below.
1. Set the IP address as described in Section 8.3
2. Assign a name for the device. see Section 9.4.1.
3. If you are unsure of the state of the device, set it back to factory default configuration as
described in Section 9.4.7.1.
4. Configure a time zone and a source for the real time clock, to assure alarm log entries get
correct time stamping. see Section 9.4.3.
5. Configure the alarm settings you wish to use for the inputs. See Section 9.5.2.2.
11.3 Seamless switching for identical signals

The TNS544 TSoIP Switch is able to perform seamless switches between two or more input signals.
A switch is categorized as seamless when it is not possible to detect that a switch has been done,
i.e. no CC errors or other data errors. A requirement for seamless swithing is bitwise identical
input streams, and identical packet order. However, there are hybrid modes, that allow usage of
non-identical streams, but they are not described here.
1. Connect two or more signals to the TNS544 using IP or ASI (if applicable).
2. IP input must be created using the Add IP Input button, see Section 9.5.1.1 on how to do
this.
3. Add the identical inputs to one of the switches, and enable all the inputs and the switch.
Inputs are added either via drag-and-drop, or using the Add button as described in Section
9.5.3.2.
4. Set the switch Match mode to Normal or Diversity, see Section 9.5.3.1. These modes
require bitwise-identical input to function.
5. Configure an appropriate Initial buffering value. This value should typically be larger
than the largest delay offset between the input streams.
158 Examples of Use
6. If the streams are equal, the inputs should have the same icon in the switch drawing.
Identical icons indicates identical signals. Icons are given according to match group, see
Section 9.5.3.2 for details. There should also be no Seamless switch impossible alarm.
7. The buffer on each input will be used to align the streams. The offset in buffer size indi-
cates the actual time delay between the streams. The input with the largest buffer will be
the leading (i.e. first arriving) input, while the input with the smallest buffers will be the
lagging (i.e. last arriving) input.
8. Test seamless switching by performing a manual switch. This may be done, by right-
clicking on the switch drawing, or using the Switch To button descirbed in Section 9.5.3.2.
9. All switches will be logged by the Switch Done alarm (id 504). Check the alarm details of
this alarm in the alarm log, to see if the switch was seamless. The alarm log is described
in Section 9.3.2.
10. If the alarm details says (Seamless), seamless operation is possible. If it says (No seam-
less), check if there are any alarms, and their alarm details. Also, verifying if the streams
are identical (same source, same rate), and that the stream delay is less than one second.
11.4 Seamless SFN for DVB-T Networks

The TNS544 TSoIP Switch is capable of performing seamless switches between different DVB-T
SFN streams coming from SFN Seamless compatible SFN Adapters. Contact Nevion for a list
of compatible Nevion SFN adapters. A seamless SFN switch means that the TNS544 will switch
between streams in such a way that the MIP packets at the output of the TNS544 will be unaffected,
and any modulator should not lose sync. However, the data stream may experience distortions at
the output of TNS544 when performing a switch since a seamless SFN switch only preserves the
MIP stream.
1. The TNS544 must have the Seamless SFN option enabled. This is shown in figure 9.36.
Please contact Nevion, see Section 2.4, for purchasing this option.
2. The SFN Adapters must transmit MIP packets (PID 21), and use the exact same OFDM
settings. The MIP timestamps are used for aligning the streams in TNS544.
3. The SFN Adapters must also be synchronized to the same SNTP and 1PPS sources. The
reader is refered to SFN Adapter User’s Manual for details regarding how to set up SFN
Adapter’s for seamless SFN switching using TNS544.
4. The TNS544 must be set to MIP matching mode, see Section 9.5.3. MIP matching mode
is licenced under the Seamless SFN option.
5. If everything is configured properly all inputs in Figure 9.69 should have the same icon,
and there should be no alarms. If not, check that everything is configured identically in
the SFN Adapter’s and if there are any alarms shown in the bottom of figure 9.69.
6. A quick way to test if the system is set up correctly is to connect the output of the TNS544
to a MIP Analyzer. Then perform a manual switch, and verify that there are no MIP
specific errors. There will however most likely be other errors in the stream.
Examples of Use 159
11.5 Seamless SFN for DVB-T2 Networks

The TNS544 TSoIP Switch is capable of performing seamless switches between different DVB-
T2 SFN streams coming from compatible Nevion DVB-T2 Gateway’s. A seamless SFN for DVB-
T2 switch means that the TNS544 will switch between the streams in such a way that the T2-MI
stream at the output of the TNS544 will be unaffected, hence ensuring that any modulator will not
lose sync. However, the data contained in the T2-MI packet containing BBFrames may experience
distortions at the output of TNS544 when performing a switch since a seamless T2 switch only
preserves the T2-MI stream when switching.
1. The TNS544 must have the Seamless SFN option enabled. This is shown in figure 9.36.
Please contact TNS544, see Section 2.4, for purchasing this option.
2. The DVB-T2 Gateway’s must transmit a valid T2-MI stream, and use the exact same T2
settings to get the same T2 timestamps. The T2 timestamps are used for aligning the
streams in TNS544. Both Relative and Absolute T2 Timestamps are supported.
3. The DVB-T2 Gateway’s must also be synchronized to the same SNTP and 1PPS sources.
The reader is refered to DVB-T2 Gateway User’s Manual for details regarding how to set
up SFN Seamless compatible DVB-T2 Gateway’s for Seamless DVB-T2 switching using
TNS544.
4. The TNS544 must be set to T2-MI matching mode, see Section 9.5.3. T2-MI matching
mode is licenced under the Seamless SFN option.
5. If everything is configured properly all inputs in Figure 9.69 should have the same icon,
and there should be no alarms. If not, check that everything is configured identically in
the DVB-T2 Gateways’s and if there are any alarms shown in the bottom of figure 9.69.
160
Preventive Maintenance and Fault-finding 161
12 Preventive Maintenance and Fault-

finding
This chapter provides the schedules and instructions, where applicable, for routine inspection,
cleaning and maintenance of the TNS544, to be carried out by the operator of the unit.
12.1 Preventive maintenance
12.1.1 Routine inspection
This equipment must never be used unless all the cooling fans are working. They should be
checked when the unit is switched on and periodically thereafter.
12.1.2 Cleaning
• Remove power from the unit.
• Clean the external surfaces of the TNS544 with a soft cloth dampened with a mixture of
mild detergent and water.
• Make sure that the unit is completely dry before reconnecting it to a power source.
12.1.3 Servicing
Warning: Do not attempt to service this product as opening or removing

covers may expose dangerous voltages or other hazards. Refer all servicing
to service personnel who have been authorised by Nevion.
In case of equipment failure unplug the unit from the power and refer servicing to qualified per-
sonnel with information of the failure conditions:
• The power supply cord or plug is damaged
• Liquid has been spilled or objects have fallen into the product
• Product has been exposed to rain or water
• Product does not operate normally when following the operating instructions
• Product has been dropped or has been damaged
• Product exhibits a distinct change in performance
162 Preventive Maintenance and Fault-finding
12.1.4 Warranty
The TNS544 is covered by standard Nevion warranty service for a period of 24 months following
the date of delivery.
The warranty covers the following:
• All defects in material and workmanship (hardware only) under normal use and service.
• All parts and labour charges
• Return of the repaired item to the customer, postage paid.
• Customer assistance through Nevion Customer Service Help Line
The warranty does not cover any engineering visit(s) to the customer premises.
12.2 Fault-finding
The objective of this chapter is to provide sufficient information to enable the operator to rectify
apparent faults or else to identify where the apparent fault might be. It is assumed that fault-
finding has already been performed at a system level, and that the fault cannot be attributed to
other system components.
This manual does not provide any maintenance information or procedures which would require
removal of covers.
Warning: Do not remove the covers of this equipment. Hazardous volt-

ages are present within this equipment and may be exposed if the covers
are removed. Only Nevion trained and approved service engineers are
permitted to service this equipment.
Caution: Unauthorised maintenance or the use of non-approved replace-

ment parts may affect the equipment specification and will invalidate any
warranties.
If the following information fails to clear the abnormal condition, please contact your local reseller
or Nevion customer care.
12.2.1 Preliminary checks
Always investigate the failure symptoms fully, prior to taking remedial action. The operator should
not remove the cover of the equipment to carry out the fault diagnosis. The following fault-finding
tasks can be carried out:
• Check that the PSU LED is lit. If this is not lit, replace external equipment, power source
and cables by substitution to check that these are not defect.
Preventive Maintenance and Fault-finding 163
• Confirm that the equipment hardware configuration is suitable for the purpose and that
the unit has been correctly connected.
• Confirm that inappropriate operator action is not causing the problem, and that the equip-
ment software set-up is capable of performing the required functionality.
• Check that the fans are unobstructed and working correctly.
When the fault condition has been fully investigated, and the symptoms are identified, proceed
to fault-finding according to the observed symptoms. If the fault persists, and cannot be rectified
using the instructions given in this manual, contact Nevion Customer Support. Switch off the
equipment if it becomes unusable, or to protect it from further damage.
12.2.2 PSU LED not lit / power supply problem
Power fault-finding
1. Check the Power LED.
− Is the LED unlit, but the unit still working properly?
Yes
The Power LED itself is probably at fault - Call a Service Engineer.
No
Proceed to next step
2. Check the Power Source.
− Connect a piece of equipment known to work to the power source outlet. Does it
work?
Yes
The problem lies within the TNS544 or the power cable. Proceed to next step.
No
The problem lies with the power source. Check building circuit breakers, fuse
boxes and the source outlet. Do they work? If the problem persists, contact the
electricity supplier.
3. Check Power Cable.
− Unplug the power cable and try it in another piece of equipment. Does it work?
Yes
The problem lies within the TNS544. Call a Service Engineer.
No
The problem lies with the cable. Replace the cable.
The PSU does not have any internal user changeable fuses.
164
12.2.3 Fan(s) not working / unit overheating

This equipment has forced air cooling and must not be operated unless all cooling fans are work-
ing. In the event of overheating problems, refer to the sequence below.
Caution: Failure to ensure a free air flow around the unit may cause
overheating.
Fan fault-finding
1. Check fan rotation.
− Inspect the fans located at the sides of the unit. Are the fans rotating?
Yes
Check that the unit has been installed with sufficient space allowed enclosure for
air flow. If the air is too hot, additional cooling may be required
No
Possible break in the DC supply from the PSU module to the suspect fan(s). Call
a Service Engineer.
12.3 Disposing of this equipment

Dispose of this equipment safely at the end of its life time. Local codes and/or environmental
restrictions may affect its disposal. Regulations, policies and/or environmental restrictions differ
throughout the world; please contact your local jurisdiction or local authority for specific advice
on disposal.
12.4 Returning the unit

Before shipping the TNS544 to Nevion, contact your local Nevion reseller or Nevion directly for
additional advice.
1. Write the following information on a tag and attach it to the TNS544.
− Name and address of the owner
− Model number
− Serial number
− Description of service required or failure indication.
2. Package the TNS544.
− The original shipping containers or other adequate packing containers must be be

used.
3. Seal the shipping container securely, and mark it FRAGILE.
Glossary 165
Appendix A Glossary
1000Base-T
The term for the electrical Gigabit Ethernet interface. This is the most common interface for
Gigabit Ethernet. Most Gigabit-enabled PCs and equipment support this interface.
3G-SDI
3Gbit High Definition - Serial Digital Interface. 3G-SDI, consisting of a single 2.970 Gbit/s
serial link, is standardized in SMPTE 424M that can replace the dual link HD-SDI.
ARP
Address Resolution Protocol. A protocol used to “resolve” IP addresses into underlying Eth-
ernet MAC addresses.
ATSC
Advanced Television Systems Committee. An American organisation working with stan-
dardisation of digital television broadcasts, primarily in the US but also in Asia and other
parts of the world.
DiffServ
Differentiated Services. A mechanism used on layer 3 - e.g. the IP layer - to differentiate
between traffic of various types. DiffServ is based on the ToS field and provides a mechanism
for the network to give e.g. video traffic higher priority than other traffic (for example Internet
traffic).
DVB
Digital Video Broadcasting. The European consortium defining standards for transmission
of digital TV broadcasts, primarily in Europe.
DVB ASI
Digital Video Broadcasting Asynchronous Serial Interface. A common physical interface for
transmission of MPEG2 Transport Streams (i.e. MPEG2-compressed video) over a serial in-
terface, typically coaxial cables.
DWDM
Dense Wavelength Division Multiplexing. A mechanism to increase the bandwidth available
in an optical fiber by adding extra signals using different optical wavelengths (colours).
Ethernet
Originally a 10 Mbit/s shared medium network type developed by Xerox. Later transformed
into an official standard. Nowadays, most Ethernet networks are based on full duplex con-
nections over twisted pair cables. Ethernet switches in the network take care of routing Eth-
ernet frames between nodes. The speeds now supported are 10 Mbit/s, 100 Mbit/s and 1000
Mbit/s. 10Gigabit/s Ethernet networks are now emerging.
FEC
Forward Error Correction. A mechanism to protect data transmission by adding redundant
information. Increasing the amount of redundant data will enable the receiver to correct
more errors (i.e. regenerate lost packets) in case of network data loss.
166 Glossary
HD-SDI
High Definition - Serial Digital Interface. Also known as ANSI/SMPTE SMPTE 292M-1998.
A specification describing how to digitize and transmit uncompressed high definition video
signals. The typical bit rate of an HD-SDI signal is 1485 Mbit/s.
HDTV
High Definition Television. Television standard(s) that provide(s) improved picture resolu-
tion, horisontally and vertically, giving clearer and more detailed TV pictures.
HTTP
HyperText Transfer Protocol. The fundamental protocol used on the Internet for transmission
of WEB pages and other data between servers and PCs.
ICMP
Internet Control Message Protocol. ICMP messages, delivered in IP packets, are used for
out-of-band messages related to network operation.
IGMP
Internet Group Management Protocol. IGMP is a protocol used to manage multicast on the
Internet. For a host (receiver unit) to receive a multicast, it needs to transmit IGMP “join”
messages in the right format. Three versions exist. IGMPv2 is commonly used today, but
IGMPv3 is the next step.
JPEG2000
A wavelet-based image compression standard. It was created by the Joint Photographic Ex-
perts Group committee with the intention to supersede their original discrete cosine transform-
based JPEG standard. JPEG2000 can operate at higher compression ratios without generating
the characteristic ’blocky and blurry’ artifacts of the original DCT-based JPEG standard.
Meta-data
Meta-data is descriptive data that is “tagged” to a movie or audio clip. Meta-data is essential
for the broadcaster.
MPEG-2
Moving Picture Experts Group 2. The compression standard used today on most satellite
and cable TV digital broadcasts. MPEG-2 also includes standardisation of data transport of
video using other compression techniques, and other types of information.
MPLS
Multi-protocol Label Switching. A Quality of Service mechanism for IP networks that al-
lows IP packets to flow along a predefined path in a network, improving the reliability and
robustness of the transmission.
MPTS
Multi Program Transport Stream. MPEG2 transport stream that carry multiple TV/Radio
services.
Multicast
An IP mechanism that allows transmission of data to multiple receivers. A multicast can also
have several transmit sources simultaneously. In video applications, multicast is typically
used to distribute a video signal from a central source to multiple destinations.
Glossary 167
MXF
Material eXchange Format is a container format for professional digital video and audio me-
dia defined by a set of SMPTE standards.
NMS
Network Management System. A system used to supervise elements in an IP network. When
a device reports an alarm, the alarm will be collected by the NMS and reported to the opera-
tor. NMS systems typically collect valuable statistics information about the network perfor-
mance and can provide early warning to the operator of network issues.
PCR
Program Clock Reference. A sampled 27 MHz video clock used in MPEG2 Transport Streams.
The primary purpose of the PCR is clock synchronisation of transmitter and receivers.
PID
Packet Identifier. An 11 bit field in an MPEG2 transport packet defining a logical channel.
8192 unique logical channels may coexist in one network.
PSI/SI
Program Specific Information / Service Information. These are information tables (meta-
data) carried in MPEG2 transport streams in addition to video and audio. The information
carried is typically service/program IDs, program names and conditional access informa-
tion.
QAM
Quadrature Amplitude Modulation. A digital modulation type that is used for transmission
of digital TV signals over cable networks (e.g. DVB-C) or terrestrial networks (e.g. DVB-T).
QoS
Quality of Service. A common term for a set of parameters describing the quality of an IP
network: Throughput, availability, delay, jitter and packet loss.
QPSK
Quadrature Phase-Shift Keying. A modulation type frequently used for transmission of dig-
ital TV signals.
RIP2
Routing Information Protocol v2. A protocol used between network routers to exchange rout-
ing tables and information.
RSVP
ReSerVation Protocol. A Quality-of-service oriented protocol used by network elements to
reserve capacity in an IP network before a transmission session takes place.
RTP
Real-time Transfer Protocol. A protocol designed for transmission of real-time data like video
and audio over IP networks.
SD-SDI
Standard Definition Serial Digital Interface. Also known as ANSI/SMPTE 259M-1997 or ITU-
R BT.656. A specification describing how to digitize and transmit uncompressed standard
definition video signals. The typical bit rate of an SD-SDI signal is 270Mbit/s.
168 Glossary
SDI
Serial Digital Interface. Used to describe both HD-SDI and SD-SDI input and output ports.
SDP
Session Description Protocol. A protocol describing multimedia communication sessions for
the purposes of session announcement, session invitation, and parameter negotiation. SDP
is typically used to describe an ongoing multicast; for example the type of compression used,
IP addresses etc.
SDTI
Serial Data Transport Interface. A mechanism that allows transmission of various types of
data over an SDI signal. This may be one or more compressed video signals or other propri-
etary data types. The advantage of SDTI is that existing SDI transmission infrastructure can
be used to transport other types of data.
SDTV
Standard Definition Television. The normal television standard/resolution in use today.
SFP
Small Form-factor Pluggable module. A standardized mechanism to allow usage of various
electrical or optical interfaces to provide Gigabit Ethernet. Several types of SFP modules exist:
Single mode fiber modules for long-distance transmission and multi mode fiber modules for
shorter distances. SFP is also known as “mini-GBIC”.
SIP
Session Initiation Protocol. The Session Initiation Protocol (SIP) is an IETF-defined signaling
protocol, used for controlling multimedia communication sessions such as voice and video
calls over IP. The protocol can be used to create, modify and terminate unicast or multicast
sessions consisting of one or several media streams.
SNDU
Sub Network Data Unit. Protocol Data Units (PDUs), such as Ethernet Frames, IP datagrams,
or other network-layer packets used for transmission over an MPEG-2 Transport Multiplex,
are passed to an Encapsulator. This formats each PDU into an SNDU by adding an encapsu-
lation header and an integrity check trailer. The SNDUs are fragmented into one or a series
of MPEG-2 Transport Stream (TS) packets and sent over a single TS logical channel.
SNMP
Simple Network Management Protocol. A fundamental and simple protocol for manage-
ment of network elements. Commonly used by Network Management Systems and other
applications.
SNTP
Simple Network Time Protocol is an Internet protocol used to synchronize the system clocks
of computers to a time reference. It is a simplified version of the protocol NTP protocol which
is overcomplicated for many applications.
SPTS
Single Program Transport Stream. MPEG2 Transport Stream that contains a single program/service.
Glossary 169
TCP
Transmission Control Protocol. A “reliable” protocol above the IP layer that provides auto-
matic retransmission of datagrams in case of packet loss, making it very robust and tolerant
against network errors. TCP is the fundamental protocol used in the Internet for WEB traffic
(HTTP protocol). TCP is indented for point-to-point communication; TCP cannot be used for
communication from one node to many others.
TCP/IP
A common term used for the Internet protocol suite, i.e. the set of protocols needed for
fundamental IP network access: TCP, IP, UDP, ARP etc.
ToS
Type of Service. This is a field in the header of IP datagrams to provide various service types.
It has now been “taken over” and reused by DiffServ.
Transport Stream (TS)

The common name for an MPEG2 Transport Stream. A bit stream used to carry a multiplex
of packets, each identified by a unique Packet Identifier (PID) defining a logical channel. A
PID stream typically represents a video or an audio service.
UDP
User Datagram Protocol. An “unreliable” protocol above the IP layer that also provides port
multiplexing. UDP allows transmission of IP data packets to several receiving processes in
the same unit/device. UDP is used in multicast applications.
Unicast
Point-to-point connection. In this mode, a transmit node sends e.g. video data direct to a
unique destination address.
VLAN
Virtual Local Area Network, a network of units that behave as if they are connected to the
same wire even though they may be physically located on different segments of a LAN.
Watermarking
A mechanism to “stamp” video content with unique marks, making it possible to trace the
origin of illegaly distributed content. Watermarks are invisible to the viewer.
XML
eXtensible Markup Language. A common self-describing text-based data format. Used for
many purposes: Meta-data, configuration files, documents, etc. The readability of the format
has made it very popular and is now the basis of many types of WEB services.
170
Technical Specification 171
Appendix B Technical Specification

B.1 Physical details
B.1.1 Half-width version
Height 43 mm, 1U
Width 222 mm excluding fixing brackets. Two units may be sideways mounted behind a common
front panel
Overall width 485 mm including fixing brackets
Depth 320 mm excluding connectors
Overall depth 340 mm including connectors
Approximate weight 2.5 kg
Rack-mount case 19 inch width, 1 U height
B.1.2 Full-width (dual power) version
Height 43 mm, 1U
Width 444 mm excluding fixing brackets
Overall width 485 mm including fixing brackets
Depth 320 mm excluding connectors
Overall depth 340 mm including connectors
Approximate weight 5 kg
Rack-mount case 19 inch width, 1 U height
B.2 Environmental conditions
Table B.1 Environmental specification
Operating temperature 0 to +50 ◦ C

Storage temperature -20 to +70 ◦ C
Relative humidity 5 % to 95 % (non-condensing)
Handling/movement Designed for fixed use when in operation
172 Technical Specification
B.3 Power
B.3.1 AC Mains supply
Table B.2 AC Power

Supply Specification
Rated voltage 100-240 VAC

Voltage tolerance limits 85-264 VAC
Rated frequency 50/60 Hz
Rated current 0.7 A
Power consumption < 50 W
B.3.2 DC supply
Table B.3 DC Power

Supply Specification
Rated voltage 48 VDC

Voltage tolerance limits 36-72 VDC
Power consumption < 60 W
Table B.4 Physical details
Pin Placement Specification

1 top + (positive terminal)
2 middle - (negative terminal)
3 bottom Chassis Ground
B.4 Input/output ports
B.4.1 DVB ASI port
Table B.5 ASI Port Specification
Type ASI-C, Coaxial cable

Connector type BNC 75 Ω socket
Signal Compliant with ETSI EN 50083-9 (DVB A010 rev.1)
Line rate 270 Mbit/s +/- 100 ppm
Data rate 0.1 - 213 Mbit/s
Packet length 188 or 204 bytes
Max cable length (Belden 8281 type) 300 m typical
B.4.2 Ethernet management port
Table B.6 Ethernet Management Port

Specification
Type 10/100Base-T
Connector type RJ45
B.4.3 Ethernet data port
Table B.7 Ethernet

Data Port Specification
Type 10/100/1000Base-T
Connector type RJ45
Table B.8 Optional SFP Ethernet Data Port Specification
Type Gigabit Ethernet

Connector type Small Form-Factor Pluggable (SFP) slot to carry copper or optical SFP, compatible with approved
modules conforming to the Small Form-factor Pluggable Transceiver Multi Source agreements
(Sept. 14, 2000).
B.4.4 Serial USB interface
Table B.9 USB port specification
Type USB 1.1

Compatibility Compatible with USB 2.0
Connector type Mini USB Connector
B.5 Alarm ports
B.5.1 Alarm relay/reset port specification
Table B.10 Alarm Relay and Reset Port

Specification
Connector type 9-pin D-sub Male

Relay rating 0.1 A max, 50 VDC max
Relay minimum load 10 µA at 10 mVDC
Reset activation time 8 seconds
Table B.11 Alarm Relay and Reset

Port Pin Out
PIN Connection
1 Relay 2 - Closed on alarm (NC)
2 Relay 2 Common
3 Relay 2 - Open on alarm (NO)
4 Prepared for +5 V Output
5 Ground
6 Alarm Relay - Closed on alarm (NC)
7 Alarm Relay Common
8 Alarm Relay - Open on alarm (NO)
9 Optional Reset Input
B.6 External reference
B.6.1 10MHz/1 PPS input
Connector type BNC 50 Ω socket
B.7 Compliance
B.7.1 Safety
The equipment has been designed to meet the following safety requirements: Table B.12.
Table B.12 Safety requirements met.
EN60950 (European) Safety of information technology equipment including business equipment.

IEC 60950 (International) Safety of information technology equipment including business equipment.
UL 1950 (USA) Safety of information technology equipment including business equipment.
B.7.2 Electromagnetic compatibility - EMC
The equipment has been designed to meet the following EMC requirements:
EN 55022 and AS/NZS 3548 (European, Australian and New Zealand)

Emission Standards Limits and methods of measurement of radio frequency interference
characteristics of information technology equipment - Class A.
EN 61000-3-2 (European)
Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emis-
sions.
EN 50082-1 (European)
Generic Immunity Standard Part 1: Domestic, commercial and light industry environment.
FCC (USA)
Conducted and radiated emission limits for a Class A digital device, pursuant to the Code
of Federal Regulations (CFR) Title 47-Telecommunications, Part 15: radio frequency devices,
sub part B -Unintentional Radiators.
B.7.3 CE marking
The CE mark indicates compliance with the following directives:

89/336/EEC of 3 May 1989 on the approximation of the laws of the Member States relating to
electromagnetic compatibility.
73/23/EEC of 19 February 1973 on the harmonisation of the laws of the Member States relating
to electrical equipment designed for the use within certain voltage limits.
1999/5/EC of March 1999 on radio equipment and telecommunication terminal equipment and
the mutual recognition of their conformity.
B.7.4 Interface to “public telecommunication system”
The equipment is not constructed for electrical connection directly to a “public telecommunication
system”. None of the signals shall be connected directly from the unit to a “public telecommu-
nication system” leaving the building without using some kind of interface in between such as
a telecom terminal, switch or similar unit. Such kind of buffer is required to achieve a protective
electrical barrier between the “public telecommunication system” and the unit. This electrical bar-
rier is required to achieve protection against lightening or faults in nearby electrical installations.
Forward Error Correction in IP Networks 177
Appendix C Forward Error Correction in

IP Networks
The normal operational mode of the public internet is that IP packets are forwarded using a “best
effort” strategy implying that packets may occasionally be lost due to excessive load. To regulate
the transport rate of an IP session a transmitting host will at session start ramp up the speed until
the receiver starts to loose packets. The receiver will send acknowledgments as it receives packets.
In the case of packet loss the source will re-transmit a packet and slow down transmission rate
to a level where packets are no longer lost. This is inherent in the commonly used protocol TCP
(Transmission Control Protocol).
In an IP network for broadcast signals however, this mode of operation becomes impractical since
packet delay from source to receiver resulting from re-transmission amounts to three times the
normal. It is also impractical for multicast as each individual receiver would need to request re-
transmissions, which in itself inflicts a bandwidth increase in a channel at the edge of overflow.
Accordingly, all broadcast related IP traffic use UDP (User Datagram Protocol). Here no retrans-
mission is included, which means that all data must be delivered in a safe manner at first attempt.
C.1 IP stream distortion

Distortions that influence the performance of an IP video transport system, in addition to packet
loss, are packet delivery time variations (jitter), and packets arriving out of order. It should be
noted that a single bit error occurring within an IP packet will result in the loss of the complete
packet. As IP packets and Ethernet physical link layers normally go hand in hand, IP packets will
be discarded if a single bit error occurs in transmission. The Ethernet link layer is secured with a
cyclic redundancy check (CRC). An Ethernet frame with bit error(s) will be discarded by the first
IP switch or router because the CRC check fails.
Furthermore, multiple packets may be lost during short periods due to congestion. As an IP packet
contains close to 1500 bytes, or about 5% of a video frame for a video stream running at 5 Mbit/s,
a lost IP packet will result in visible impairments.
Figure C.1 Impairments of an IP packet stream
178 Forward Error Correction in IP Networks
In Figure C.1 distortions of an IP stream are visualised. The even stream of packets originating
from the Tx node is modified in traversing the IP network. At the input of the Rx node the IP
stream is distorted in the following ways:
• The packet spacing is no longer even
• The position of packet #6 has been shifted
• Packet #8 is missing
A properly designed IP node will handle the first two within certain limits; the input buffer size
will determine the amount of jitter that can be tolerated and the time to wait for a delayed or out-
of-order packet before it is deemed lost. Lost packets, however, are not recoverable unless special
measures are taken.
C.2 Standardisation
All since streaming of broadcast services in IP networks began the insufficient reliability of IP
links has been an issue, and methods to improve performance have been devised. Due to lack of
standardisation many proprietary implementations and different solutions have been put into use
by equipment manufacturers. The PRO-MPEG organisation has taken the initiative to achieve a
common standard for transport of video over IP. These have been published as Code of Practice
(COP) #3 and #4. COP#3 considers compressed video in the form of MPEG-2 Transport Stream,
while COP#4 considers uncompressed video at 270Mbit/s and higher. The IP protocol stack pro-
posed is RTP/UDP/IP. This work has been taken over by the Video Services Forum (VSF) (http
://www.videoservicesforum.org). VSF has in cooperation with SMPTE successfully brought
the COP#3 and COP#4 further and COP#3 is now finalised as SMPTE 2022-1 [9] and 2022-2 [8].
SMPTE 2022-1 focuses on improving IP packet loss ratio (PLR) performance using forward error
correction techniques.
C.3 FEC matrix

SMPTE 2022-1 specifies a forward error scheme based on the insertion of additional data con-
taining the result of an XOR-operation of packet content across a time window. By reversing the
operation it is possible to reconstruct single lost packets or a burst of lost packets. The degree
of protection may be selected to cover a wide range of link quality from low to heavy loss at the
expense of increased overhead and delay.
SMPTE 2022-2 specifies use of RTP protocols and hence all packets have a sequence number. Thus,
a receiver will be able to determine if a packet has been lost. There should be no cases of packets
arriving containing bit errors as packets with checksum errors are discarded at the Ethernet layer.
A FEC packet containing a simple XOR-sum carried out over a number of packets at the transmitter
allows the receiver to compute one lost packet by redoing the XOR process over the same packets
and comparing the results with the XOR FEC packet. This allows for the regeneration of one lost
packet in an ensemble of N payload packets plus one FEC packet. If two or more packets in the
ensemble are lost it is not possible to regenerate any of them. Packet loss in IP systems have a
tendency to come in bursts (due to congestion). Therefore the FEC XOR calculation is not done on
adjacent packets; rather packets at a fixed distance are used. This can be visualised by arranging
the packets in a two dimensional array and inserting them in rows in the same order as they are
transmitted.
Figure C.2 IP packet FEC calculation matrix
Figure C.2 shows LxD consecutive IP packets arranged in a matrix. The FEC checksum is cal-
culated over the columns, which means that the distance between two packets used in an XOR
calculation is L. An XOR sum is calculated for each bit position of all the packets of a column.
The checksums for all bit positions constitute the FEC checksum, and is inserted in a FEC packet
which is sent in addition to the payload packets. There will be one FEC packet associated with
each column, and it is therefore possible to regenerate as many packets as there are columns in the
matrix.
In the right-most panel of Figure C.2 the case is shown where a packet in the last column position
has been lost. The packet may then be regenerated (shown in red) by performing XOR addition
over all remaining packets in that column, including the FEC packet. This is the default FEC mode
of SMPTE 2022-1.
However, it is not possible to correct more than one error in a column. To increase the error correc-
tion capability the specification gives the option to also include FEC over the rows. By combining
the two FEC calculations it is now possible to handle more complex packet loss distribution pat-
terns and correct up to L+D lost packets.
Figure C.3 Two-dimensional FEC calcula-

tion matrix
Figure C.3 shows this arrangement. Here, checksums are also calculated for the packets in each
row. This gives rise to another D FEC packets, which again means increased overhead.
A drawback with a rectangular matrix arrangement is that all column-FEC packets need to be
transmitted at nearly the same time as all column-FEC packets are generated when the last row of
the matrix is being completed. Thus when transmitting the last row of payload packets the packet
rate must be doubled in order to also send the FEC packets without generating extra payload
packet delay. In itself this may cause temporary network overload with packet loss as a result.
The specification [9] imposes some rules how FEC packets should be interleaved with payload
packets to avoid excessive jitter and ensuring compatibility between equipment from different
manufacturers. One method is to offset the FEC columns, one example is shown in Figure C.4,
which also provides additional advantages.
Figure C.4 FEC matrix

with column offset
Column offset leads to column FEC packets being generated at a more regular rate and it is possible
to transmit packets with a shorter delay than with a rectangular matrix. Offsetting the columns
also increases the capability to regenerate longer bursts of lost packets; the length depending on
the column and row length ratio.
Figure C.5 Offset FEC matrix with miss-

ing packets
Figure C.5 shows an offset matrix with missing packets. The numbered items indicates packets
lost. The figure shows that column offset may increase the capability to correct longer bursts of lost
packets. In this example 9 consecutive packets are lost. Even if the row length is only 7 packets, all
the 9 lost packets are reconstructed. The packets are numbered in the order they can be recovered.
Packets marked 8 and 9 are protected by the same column FEC packet and are recovered by the
row FEC packets after recovery of packets 1 through 7.
If more than one packet is lost in a row or a column of a matrix, the possibility to recover it depends
on packet location. Figure C.6 shows this.
Figure C.6 Uncorrectable error patterns
The red-coloured packets are lost in transmission. The pattern to the left normally results in 4
unrecoverable payload packets. However, if two of the lost packets are FEC packets, then only 2
payload packets will be lost. The pattern to the right will result in one lost payload packet.
The specifications allow several parameter combinations for the FEC stream generation. The FEC
matrix sizes can in principle be chosen at will to suit the operational conditions. Operators may
easily be confused by the number of options, and it is not straightforward to choose the optimal
FEC setting for a given scenario. For compatibility reasons SMPTE 2022-1 specifies that an MPEG-
2 to IP network adapter should handle a minimum matrix size of 100 IP packets, and that row
length or column depth should not exceed 20. Also the shortest column length allowed is 4.
C.4 Transmission aspects

The RTP protocol must be used if FEC shall be added to the IP payload. In order to provide compat-
ibility between equipment handling application layer FEC and equipment without that capability
FEC data is transmitted using UDP port numbers different from that of the payload. Column FEC
is transmitted using port number (IP payload) + 2 and row FEC (if used) is transmitted using port
number (IP payload) + 4.
Introducing FEC for the IP connection obviously leads to additional data overhead and conse-
quently a higher demand on data capacity. The generated FEC packets need to be "squeezed" in
between the payload packets, which will tend to increase the packet jitter experienced by the re-
ceiver. Notably, in a rectangular matrix all column-FEC packets are generated and inserted into
the stream in succession. This leads to a short burst of packets in quick succession, or a consid-
erable delay before the first packet of the next FEC frame can be transmitted (or indeed, some of
each).
Figure C.7 illustrates the relative timing of FEC packets and payload packets. Applying an offset
column structure results in a smoother packet stream. The overall packet rate will be the same in
both schemes, since the same number of FEC packets are generated, but the packets will be more
evenly spread in the IP stream. With larger matrix sizes the smoothing effect of an offset matrix
will even more pronounced. The effect of added overhead and jitter should be considered when
applying FEC to an IP video stream in a heavily loaded network. High instantaneous packet rates
may cause temporary overload resulting in packet loss, defeating the object of introducing FEC in
the first place.
Figure C.7 FEC data transmission
C.5 Quality of service and packet loss in IP networks

One may ask how the FEC strategy relates to an operational IP network. Little information is
available on packet loss patterns. Measurements show that up to 1% of the packets are duplicates
and generated as a result of a retransmission request. Either because the packet has been lost or
it has arrived too late. However, since these results are for TCP connections they merely serve to
indicate an upper level for packet loss rate in an IP/MPLS network. Reported jitter measurements
indicate that 0.01% of the packets were delayed more than 31ms and a fraction of those packets
were delayed more than 100ms. This is also relevant for transmission of video as out-of-order
packets arriving too late will be regarded as lost and must, if possible, be regenerated by FEC.
There are three main factors that cause packet loss:
• Occasional bit errors in the Ethernet frame caused by low noise margin or equipment
fault
• Buffer overflow or packet delay caused by network congestion
• Packet re-routing, to circumvent a node breakdown or network bottlenecks
Some of the packets will arrive late. IP packet latency will vary as a result of variable traffic load
on the network. Packets that do not arrive in time will be handled as lost packets. The FEC process
will thus be able to handle occasional delay increase for a few packets and maintain a satisfactory
Quality of Service. A video gateway should offer a setting for permissible packet delay, which
should be optimised for the operation. If the receiver buffer latency is increased it is possible to
reduce the FEC overhead and still get an error-free video link.
The Packet Loss Ratio (PLR) for an IP network is not a given number. Performance figures are
normally in the order of 1 x 10 -6, but occasionally a link may become degraded showing PLR
figures like 3 x 10 -3. The performance will vary over the day with the lowest performance tending
to occur at about the same time every weekday and lasting for one-half to one hour. The FEC
setting should be set up to handle this peak hour with low residual loss.
The table of Figure C.8 shows the IP network performance figures to meet the quality requirements
of various grades of television services, as given by ITU recommendation Y.1541 [10]. Along these
lines the DVB IPTV standard sets the performance requirement for a 4Mbit/s IPTV service at 1
visible error per hour, which means an IP packet loss ratio of 1x10 -6.
Figure C.8 Recommended error performance (as per ITU)
C.6 Error improvement

So, what does it take to make FEC improve the packet error rate of an IP network link to a level
acceptable for the application? Assuming packet loss occurs at random Figure C.9 shows how the
depth of a one-dimensional FEC matrix affects the error correcting capability.
Figure C.9 Error improvement using column FEC only
It is evident that the smaller the column depth the better error correcting capability. At a network
packet loss rate of 10 -5 adding FEC will provide up to 4 magnitudes of improved error perfor-
mance.
For ease of reference the diagram indicates packet loss rates resulting in one visible impairment
(error hit) per day at transport stream bit rates of 40Mb/s, 270Mb/s and 1,5Gb/s, respectively.
It can be seen that in a network with worst hour packet loss rate of 3x10 -3 it is not possible to
provide distribution of a 3Mb/s transport stream with less than 10 hits per day (i.e. packet loss
rate of 4x10 -7, as recommended in Figure C.8) using column-only FEC. In IP networks of ITU class
6 and 7 however, column-only FEC with reasonably small column depths will perform nicely for
bit rates up to 270Mb/s.
Distributing video transport streams over high packet loss rate networks demand use of two-
dimensional FEC. As explained earlier this increases the added overhead and thus the required
network bandwidth.
Figure C.10 Error improvement using two-dimensional FEC
Figure C.10 shows how adding row FEC dramatically increases performance in high packet loss
networks. Reverting to the previous case, a 3Mbit/s video transport stream in an IP network with
worst hour PLR of 3x10 -3, a service with less than 10 error hits per day may be provided using
any of the matrix sizes shown. In less error-prone networks however, using two-dimensional FEC
schemes may be overkill and generate unnecessary FEC overhead.
C.7 Latency and overhead

Latency is increased when FEC is applied. The latency that can be accepted in a particular appli-
cation may vary, and should be considered when setting FEC parameters.
FEC packet calculation in the transmitter is done on-the-fly and adds little to the latency. In a
rectangular matrix, however, all FEC packets are generated nearly at the same time, as indicated
in Figure C.7. FEC packets should be spread in transmission to avoid introducing extra jitter. This
also contributes to latency in error packet recovery. In the receiver all packets involved in the FEC
calculation must be collected before a missing packet can be recovered. Figure C.11 shows how
different matrix sizes result in different latencies and required buffer sizes, using column-only FEC
processing.
Figure C.11 FEC latency and buffer size
Also shown is the resulting overhead and the number of packets that can be corrected. In column-
only FEC there is one FEC packet per column, resulting in a 1/D increase in transmission overhead,
D being the matrix column depth. I.e. in a 10 row matrix (D=10) the added overhead is 10%. The
minimum allowable column depth of 4 will produce 25% overhead.
In two-dimensional FEC there will be D+L FEC packets in a DxL matrix (L being the row length).
Thus the added overhead is D+L/DxL, which for a 10 by 10 matrix amounts to 20%.
Adding row-FEC will increase the error correcting capability without significantly increasing the
latency or buffer size requirement. Applying row- and column-FEC also enables use of iterative
FEC calculations to recover more missing packets. The equipment manufacturer is at liberty to
determine the algorithm used in error recovery as long as the requirements and limitations of the
specification are respected.
186
Quality of Service, Setting Packet Priority 187
Appendix D Quality of Service, Setting

Packet Priority
Normal IP routing is by best effort. This does not work well for broadcast television as the video
and audio components need to be transported as a continuous flow of packets without interference
from other traffic over the internet. There are different techniques to improve quality-of-service.
The main ones are:
• MPLS (Multi Protocol Label Switching)
• Layer 3 routing priority
• Layer 2 routing priority
D.1 MPLS
In networks running MPLS, the packets are forwarded along a predefined path from an ingress
router to an egress router. Packet switching is then done according to the label and packets will be
switched expediently. The MPLS label is added to the IP packet by the ingress router and removed
by the egress router. The labelling is done on the basis of packet classification.
D.2 Layer 3 routing

An alternative technique to improve QoS is to use layer 3 routing and give video content packets
higher priority than other data. IP packets are put into queues according to their priority. Packets
with high priority are forwarded expediently and have a lower probability of being discarded due
to buffer overflow.
There are two ways to prioritise IP packets; using Differentiated services (Diff-serve) or precedence
bits (TOS). Both these methods use the same bits in the IP header and both of them are in common
use.
IP precedence values range from 0 to 7. Diff-serve code point (DSCP) values range from 0 to 63.
Figure D.1 Differentiated services (Diff-serve) and precedence bits (TOS)
Layer 3 prioritisation may also be combined with MPLS where layer 3 routing is used in the aggre-
gation network and MPLS in the core network. The DSCP priority setting may be used for MPLS
tagging.
188 Quality of Service, Setting Packet Priority
D.2.1 TNS544 configuration
The number entered into the Type of service (TOS) field in TNS544 IP TX configuration menu
defines all 8 bits. The value used should be in accordance with traffic engineering policy of the
network and should be in the range from 0 to 255.
D.3 Layer 2 priority

Prioritisation can also be supported in layer 2 using VLAN tags. The 802.1q VLAN tag has 3 bits
for setting the Class of Service (COS). The operation is further defined in [7]. The COS bits will
be handled the same ways as Diff-serve or precedence bits regarding packet classification in the
network.
D.3.1 TNS544 configuration
The COS priority is entered in the VLAN configuration page in the TNS544 IP TX configuration
menu, in the field named VLAN Priority. A value in the range from 0 to 7 should be inserted. This
value will be directly transferred to 3 user priority bits in the VLAN header.
More information on quality of service issues and configuration can be found in the literature, e.g.
router configuration guides.
Alarms 189
Appendix E Alarms
The TNS544 indicates alarm or failure status to the user in four ways:
• WEB interface
• Alarm LED on the front and on the rear
• SNMP trap messages to Network Management System
• Alarm relay
The user can define the severity level of the different alarm events. There are five levels, and each
level is also indicated by a colour on the alarm severity indicator:
Table E.1 Alarm severity levels
Severity Level Colour

Notification 2 Blue
Warning 3 Yellow
Minor 4 Amber
Major 5 Orange
Critical 6 Red
In addition it is possible to set an alarm to filtered, so that there will be no alarm events generated
for this alarm.
The WEB interface gives the most detailed alarm information as all active alarms and warnings
are listed with time of occurrence
The unit sends an SNMP trap message to all registered trap receivers when an alarm condition
arises. A critical alarm will have severity level 6 and a Notification will have severity level 2. When
the alarm is cleared, a new message is sent to indicate that the alarm condition is cleared.
Finally, the red alarm LED will be lit when an unmasked critical alarm condition arises. At the
same time the alarm relay will be set to alarm state.
Table E.3 shows the possible alarms that can be signalled by the TNS544. For each alarm type,
essential information is presented. The different fields are described in Table E.2.
190 Alarms
Table E.2 Fields in the alarm description table
Field Description
Alarm ID Unique identifier (number) for this alarm. There are no duplicates in the table, e.g. a specific alarm
number always maps to a specific alarm.
Text A short text describing the alarm
Description A longer text describing the cause of the alarm
Def. severity The default severity of the alarm
Type Alarms are grouped together into different types. This field contains a textual description of the type.
Type ID Each alarm type has a corresponding number (ID).
Clear event Set to Yes if an “off/cleared” alarm is expected after an “asserted” alarm. In most cases the value is
Yes. For “stateless” alarms, e.g. the event that a user has logged into the system, no explicit clear
events are expected.
Subid2 This field is present if the Subid2 value of the alarm type is used. The text in the table describes the
usage of the Subid2 value.
Subid3 This field is present if the Subid3 value of the alarm type is used. The text in the table describes the
usage of the Subid3 value.
Alarms 191
Table E.3.a Alarms
Alarm ID Text Def. severity Details
106 Unable to transmit Critical Description: Channel not able to transmit any data, or only part of the data is transmitted.
Type: Port
Clear event: Yes
Subid3: “IP Dest”
107 Output parameter conflict Critical Description:
Type: Port
Clear event: Yes
130 Ethernet link down Critical Description: No link on Ethernet layer.
Type: Port
Clear event: Yes
131 Ethernet output overflow Critical Description: The total bitrate of the streams to transmit is too high compared to the
available ethernet bitrate.
Type: Port
Clear event: Yes
133 Generic SFP alarm Critical Description: Generic SFP alarm for Mipot and SFF-8472 based modules.
Type: Undetermined
Clear event: Yes
134 Ethernet link problem Critical Description: Problem on the ethernet link
Type: Undetermined
Clear event: Yes
140 IP address unresolved Warning Description: IP address is not resolved into physical MAC address.
Type: Port
Clear event: Yes
148 No FEC Column received Major Description: No FEC Column packets received on Ethernet input for stream. If FEC engine
enabled it expects to find FEC Column on Data UDP port+2.
Type: Port
Clear event: Yes
149 No FEC Row received Ok Description: No FEC Row packets received on Ethernet input for stream. If FEC engine
enabled it expects to find FEC Row on Data UDP port+4.
Type: Port
Clear event: Yes
150 RTP sequence error Warning Description: Network error. Analysis of the sequence number of the RTP layer indicates
that IP frames have been lost or that they have been received out of order.
The alarm details field shows the actual jumps in the RTP sequence number
field.
Type: Port
Clear event: Yes
Subid3: “IP Flow”
151 No data received Major Description: No data received on Ethernet input for stream. See details field on alarm for
description.
Type: Port
Clear event: Yes
Subid3: “IP Flow”
192 Alarms
Table E.3.b Alarms
153 Ethernet input overflow Critical Description: The total bitrate of the IP input streams is too high.
Type: Undetermined
Clear event: Yes
154 Data lost Critical Description: The data stream received for a channel is incomplete or packets were received
out of order and the buffer was not large enough. Also, if running FEC, the
FEC engine was not able to recover all the lost frames.
Type: Port
Clear event: Yes
155 No lock Critical Description: The incoming packet stream is absent or incompatible with the expected
format.
Type: Port
Clear event: Yes
157 Receive buffer too small for FEC Warning Description: The receive buffer size is set lower than the buffer required to fully utilize the
current FEC. Increase Receive buffer size to resolve.
Type: Port
Clear event: Yes
158 SFN mode config error Warning Description: Lock to MIP bitrate mode requires configuration and locking to an external
1PPS source (Device Info-Clock Regulator).
Type: Port
Clear event: Yes
160 SNTP server unreachable Warning Description: The unit is not receiving answers from the SNTP server.
Type: System
Clear event: Yes
161 Too high temperature Warning Description: Internal temperature of unit is too high.
Type: System
Clear event: Yes
162 Defective fan Warning Description: One or more fans are not spinning.
Type: System
Clear event: Yes
163 Time reference unreachable Warning Description: No selected timesources are OK.
Type: System
Clear event: Yes
164 Illegal board configuration detected Critical Description: A board configuration that is incompatible with this product has been
detected.
Type: System
Clear event: Yes
165 Time source not OK Note Description: One or more time sources are not OK.
Type: System
Clear event: Yes
166 Time source switch Note Description: Device started using a new time source.
Type: System
Clear event: No
167 Time adjusted Note Description: The real time clock of the device was adjusted significantly.
Type: System
Clear event: No
Alarms 193
Table E.3.c Alarms
168 Power failed Warning Description: One or more power supplies have failed, or are out of regulation.
Type: System
Clear event: Yes
Subid3: “Power supply ID”
169 Virtual alarm relay activated Note Description: A virtual alarm relay has been activated.
Type: System
Clear event: Yes
Subid3: “Relay ID”
200 No GPS 1PPS ref. signal Critical Description: The 1PPS reference signal is lost (The regulator has however not lost
synchronization).
Type: System
Clear event: Yes
201 Lost GPS 1PPS sync. Critical Description: The clock synchronization mechanism has been resynchronized due to too
large phase error.
Type: System
Clear event: Yes
210 Emergency switch active Note Description: A user has activated the remote emergency switch.
Type: System
Clear event: Yes
211 Emergency switch unreachable Warning Description: The device is not able to communicate with the remote emergency switch.
Type: System
Clear event: Yes
212 Emergency switch rule config error Warning Description: An error has been detected in the configuration of the emergency switch.
Type: System
Clear event: Yes
220 Time adjusted for DST Note Description: Device local time adjusted due to daylight saving.
Type: System
Clear event: No
501 User logged in Note Description: This event is generated when a user logs on to the system.
Type: System
Clear event: No
502 User logged out Note Description: This event is generated when a user logs out from the system.
Type: System
Clear event: No
503 System started Note Description: The system has booted.
Type: System
Clear event: No
504 Switch done Note Description: The input relay has switched position.
Type: Undetermined
Clear event: No
505 Config changed Note Description: A modification has been made to the configuration of the device.
Type: System
Clear event: No
194 Alarms
Table E.3.d Alarms
506 Unable to switch Major Description: The relay controller is unable to switch because the spare input is not
sufficiently good.
Type: Undetermined
Clear event: Yes
507 Auto switching disabled Warning Description: Enabled when auto switching is turned off.
Type: Undetermined
Clear event: Yes
508 Auto switch performed Ok Description: Automatic switch is performed. This alarm will stay on until it is manually
confirmed by the operator (see chapter on switch config).
Type: Undetermined
Clear event: Yes
517 Alarm log cleared Note Description: Alarm log was cleared, user in details
Type: System
Clear event: No
518 System is starting up Critical Description: This alarm is set when the system is starting. Once booted correctly, the
alarm is cleared.
Type: System
Clear event: Yes
519 Forced reset initiated Note Description: A reset of the device was forced by the operator.
Type: System
Clear event: No
520 SW loading in progress Note Description: Loading of an embedded SW image is in progress
Type: System
Clear event: Yes
521 New SW pending Note Description: A SW image has been successfully loaded, but manual reboot is needed for
SW to be activated.
Type: System
Clear event: Yes
524 Simultaneous users Note Description: Multiple users with administrator or operator access level are logged in.
Type: System
Clear event: Yes
526 Action performed Note Description: Action performed by user. Used to log generic important events, see details
field on each alarm event for additional information.
Type: System
Clear event: No
527 New SW license pending Note Description: New SW licenses have been loaded but requires a re-boot to be activated.
Type: System
Clear event: Yes
528 New SW license installed Note Description: New SW licenses have been loaded and installed without requiring reboot.
Type: System
Clear event: Yes
535 Alarm log fill Note Description: Alarm log filling high. Overwrite of older alarms will take place when
completely full
Type: System
Clear event: Yes
Alarms 195
Table E.3.e Alarms
536 Heartbeat trap Note Description: Heartbeat to signal the system is still functional
Type: System
Clear event: No
705 Delay too high for seamless switching Warning Description: The configured delay is too high compared to the current bitrate. Seamless
switching is not possible.
Type: Undetermined
Clear event: Yes
710 Seamless switch impossible Major Description: Seamless switch to port not possible. This can be due to delay problems or
mismatching streams.
Type: Undetermined
Clear event: Yes
1100 Sync unstable Major Description: Two separate sync-losses in 10s.
Type: Port
Clear event: Yes
1101 TS unstable Minor Description: Lots of PIDs appearing/disappearing or CC errors. Threshold is set in
percentage of present PIDs that can have an event (sum of detected and
disappeared, or number of C errors) before alarm is set. Other detailed alarms
such as CC errors are filtered while TS unstable is active. Alarm is also set if
too many PIDs are present.
Type: Port
Clear event: Yes
1110 No sync Critical Description: No valid transport stream detected. See test 1.1 in ETSI TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1120 Sync byte error Warning Description: Sync byte not equal to 0x47. See test 1.2 in ETSI TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1131 PAT repetition interval Warning Description: Measured interval between each PAT is greater than the configured limit.
ETR290 specifies limit to 500 ms. Part of test 1.3 in ETSI TR 101 290
v1.2.1.
Type: Port
Clear event: Yes
1132 PAT invalid table ID Warning Description: Unable to find section with table_id 0x00 on PID 0. Part of test 1.3 in ETSI
TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1133 PAT scrambled Warning Description: Scrambling control field set for PID 0. Part of test 1.3 in ETSI TR 101 290
v1.2.1.
Type: Port
Clear event: Yes
1134 PAT missing Warning Description: PAT not found in transport stream. The PAT is required to do any further
PSI decoding.
Type: Port
Clear event: Yes
196 Alarms
Table E.3.f Alarms
1140 CC error Warning Description: The Continuity Counter in the TS header was not as expected. Should
increase by 1 for each packet with the Payload bit set, and not increase if not.
Typically caused by lost TS packets. See test 1.4 in ETSI TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
Subid3: “PID”
1151 PMT repetition interval Warning Description: Measured interval between each PMT on a specific PID referenced in the PAT
is greater than the configured limit. ETR290 specifies limit to 500 ms. Part
of test 1.5 in ETSI TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1152 PMT scrambled Warning Description: Scrambling control field set for any PID carrying table_id 0x02, i.e. a PMT.
Part of test 1.5 in ETSI TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1153 PMT missing Warning Description: PMT referenced in the PAT, but not found in transport stream.
Type: Port
Clear event: Yes
Subid3: “Service”
1160 PID error Warning Description: PID referred in a PSI table, but not found within the configured period. The
period is configured using the PIDs disappeared alarm. See test 1.6 in ETSI
TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
Subid3: “PID”
1161 PIDs disappeared Ok Description: This alarm is set when PIDs are timed out. The timeout can be specified per
PID. Timeouts specified affect the PID Error alarm also.
Type: Port
Clear event: No
Subid3: “PID”
1210 Transport error Warning Description: Transport Error Indicator (TEI) set in the TS header. See test 2.1 in ETSI
TR 101 290 v1.2.1.
Type: Port
Clear event: Yes
1523 Status Input connector Ok Description: Alarm representing external alarm relays, labeled Status Input
Type: Port
Clear event: Yes
1524 MIP PID not present Warning Description: The MIP PID is not present.
Type: Port
Clear event: Yes
1525 MIP CRC error Critical Description: A CRC error has been detected in the MIP.
Type: Port
Clear event: Yes
Alarms 197
Table E.3.g Alarms
1526 MIP new parameters Note Description: An update has been detected in the parameters contained in MIP (TPS field
or maximum delay field).
Type: Port
Clear event: Yes
1527 MIP CC error Warning Description: TS packet header CC error has been detected on the MIP PID.
Type: Port
Clear event: Yes
1528 MIP STS range error Warning Description: The STS field indicates a value larger than a second.
Type: Port
Clear event: Yes
1529 MIP pointer error Warning Description: The number of TS packets in the megaframe does not match the parameters
in MIP.
Type: Port
Clear event: Yes
1530 MIP timing error Warning Description: STS values in consecutive MIPs have wrong timing values.
Type: Port
Clear event: Yes
1531 Extra MIP Warning Description: An extra MIP has been detected within a megaframe.
Type: Port
Clear event: Yes
1532 Missing MIP Warning Description: No MIP is detected.
Type: Port
Clear event: Yes
1533 MIP periodicity error Warning Description: The MIP periodicity is not correct.
Type: Port
Clear event: Yes
1534 MIP ts rate error Warning Description: The rate of the transport stream does not match the rate signaled in the MIP.
Type: Port
Clear event: Yes
1535 MIP network delay too high Ok Description: Measured Network delay higher than configured maximum delay. Network
delay is the time elapsed since the SFN adapter. Important: Both the
monitor and the SFN adapter must be locked to the same external reference.
Type: Port
Clear event: Yes
1536 MIP network delay too low Ok Description: Measured Network lower higher than configured maximum delay. Network
delay is the time elapsed since the SFN adapter. Important: Both the
monitor and the SFN adapter must be locked to the same external reference.
Type: Port
Clear event: Yes
1542 MIP size error Warning Description: There is not enough space in the MIP packet for all configured transmitter
function loops.
Type: Port
Clear event: Yes
198 Alarms
Table E.3.h Alarms
1543 MIP Inserter time reference problem Warning Description: MIP Inserter time reference problem.
Type: Port
Clear event: Yes
1801 TS-ID incorrect Ok Description: The TS-ID of the incoming stream does not match the TS-ID of the
configured CSI section. For modes where the input TS-ID is not known, the
TS-ID expected must be configured manually.
Type: Port
Clear event: Yes
1802 PID rate too high Ok Description: PID bitrate is higher than set limit. Only PIDs added to override list are
monitored, and the marate must be set per PID.
Type: Port
Clear event: Yes
Subid3: “PID”
1803 PID rate too low Ok Description: PID bitrate is lower than set limit. Only PIDs added to override list are
monitored, and the min rate must be set per PID.
Type: Port
Clear event: Yes
Subid3: “PID”
1804 Static scrambling bits Ok Description: Scrambling bits are static (not changing between odd and even) within the
user defined interval.
Type: Port
Clear event: Yes
Subid3: “PID”
1805 Service missing Ok Description: A service is missing from the stream (according to configured expected value)
Type: Port
Clear event: Yes
Subid3: “Service”
1806 PID scrambled Ok Description: Define list of PIDs which should NOT be scrambled. Alarm will be triggered
if PID is scrambled
Type: Port
Clear event: Yes
Subid3: “PID”
1807 PID not scrambled Ok Description: Define list of PIDs which should be scrambled. Alarm will be triggered if PID
is NOT scrambled
Type: Port
Clear event: Yes
Subid3: “PID”
1812 TS rate too high Ok Description: TS bitrate is higher than set limit.
Type: Port
Clear event: Yes
1813 TS rate too low Ok Description: TS bitrate is lower than set limit.
Type: Port
Clear event: Yes
Alarms 199
Table E.3.i Alarms
1814 CA system ID missing Ok Description: A specified CA system ID is missing in CAT

Type: Port
Clear event: Yes
Subid3: “CAID”
200
References 201
Appendix F References
[1]
ISO13818-1, 2 and 3; MPEG-2 Video and Audio and Systems
[2]
ETSI EN 300 468: Digital Video Broadcasting (DVB); Specification for Service Information
(SI) in DVB Systems.
[3]
ETSI TR 101 211: Digital Video Broadcasting (DVB); Guidelines on Implementation and Us-
age of Service Information.
[4]
ETSI EN 300 744. Digital Video Broadcasting (DVB); Framing structure, channel coding and
modulation for digital terrestrial television.
[5]
ETSI TS 101 191. Digital Video Broadcasting (DVB); DVB mega-frame for Single Frequency
Network (SFN) synchronisation.
[6]
ETR 154 Digital Video Broadcasting (DVB); Implementation Guidelines for the Use of MPEG-
2 Systems, Video and Audio in Satellite and Cable Broadcasting Applications. ETSI Technical
Report ETR 154, European Telecommunications Standards Institute ETSI.
[7]
IEEE 802.1Q-2005 802.1QTM, Standards for Local and metropolitan area networks, Virtual
Bridged Local Area Networks
[8]
SMPTE 2022-2-2007: Unidirectional Transport of Constant Bit-Rate MPEG-2 Transport Streams
on IP Networks
[9]
SMPTE 2022-1-2007: Forward Error Correction for Real-time Video/Audio Transport over IP
Networks
[10]
ITU-T Y.1541 (02/2006) Series Y: Global Information Infrastructure, Internet Protocol Aspects
and Next-Generation Networks: Internet protocol aspects; Quality of service and network
performance. Network performance objectives for IP-based Services
[11]
Pro-MPEG Forum: Pro-MPEG Code of Practice #3 release 2, July 2004: Transmission of Pro-
fessional MPEG-2 Transport Streams over IP Networks
202
[12]
Pro-MPEG Forum: Pro-MPEG Code of Practice #4 release 1, July 2004: Transmission of High
Bit Rate Studio Streams over IP Networks
[13]
J. Rosenberg, H. Schulzrinne, IETF RFC2733, December 1999: An RTP Payload Format for
Generic Forward Error Correction

Nevion TNS-544

Uploaded by

Copyright:

Available Formats

Nevion TNS-544

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nevion TNS-544

Uploaded by

Copyright:

Available Formats

TNS544

Valid for SW version 2.6.4 and newer

3 Short Product Description 13

3.1 Summary of features 13

4.1 Configure the management interface 17

5 Installing the Equipment 21

5.1 Inspect the package content 21

6.1 Input and output 28

7.1 ASI ports 33

8 Operating the Equipment 39

8.1 Accessing the graphical user interface 39

10.1 SNMP agent characteristics 149

11 Examples of Use 157

11.1 Introduction 157

12 Preventive Maintenance and Fault-finding 161

12.1 Preventive maintenance 161

B Technical Specification 171

B.1 Physical details 171

C Forward Error Correction in IP Networks 177

C.1 IP stream distortion 177

D Quality of Service, Setting Packet Priority 187

D.1 MPLS 187

Revision Date Comments

2.6 November 2014 – Added description of new Switch modes.

2.0 February 2012 – Added description of new parameters on Switch page.

• WEB interface description

• Preventive maintenance and fault finding

2.2 Warnings, cautions and notes

Warning: This is a warning. Warnings give information, which if strictly

Caution: This is a caution. Cautions give information, which if strictly

Note: Notes provide supplementary information. They are highlighted for

2.3 Heed warnings

• All operating and usage instructions should be followed.

2.4 Contact information

3 Short Product Description

3.1 Summary of features

• Intelligent Transport Stream switching

− Automatic/manual seamless switching

− Automatic network delay compensation

• High density and flexible switch configuration

− Up to 4 independent switches in 1RU half-width 19“

− Configurable number of inputs per switch (2-4 inputs)

− 4 secured ASI outputs on power loss

− Fully configurable alarm based switching criteria

• TS monitoring and error detection

− Simultaneous monitoring of all input MPEG Transport Streams

• Industry-leading support for IP video technologies

− Two Gigabit Ethernet interfaces for TS over IP

− IP multicast, unicast and multiple unicast support

− Optional support for Ethernet over Sonet OC-3 / SDH STM-1

− IP wrapping of Transport Streams using SMPTE 2022-2

− Forward Error Correction according to SMPTE 2022-1

− Support for multiple VLANs (IEEE 802.1Q)

− TOS/COS field support for traffic prioritisation

• User-friendly configuration and control

− WEB/XML based remote control

− Easy access to unit from any WEB browser

− Easy integration to NMS systems with SNMP Trap support

− Equipment monitoring from Nevion Connect