CP560 DVB-T2 Gateway User's Manual · 2020. 3. 4. · E ValidationofDVB-T2Parameters 193 E.1...

nevion.com

CP560 DVB-T2 GatewayUser’s ManualRevision: 2.2.B (5008)

2016-05-03

Valid for SW version 2.2.0 and newer

Contents1 History 9

2 Introduction 11

2.1 Scope 112.2 Warnings, cautions and notes 112.3 Heed warnings 122.4 Contact information 12

3 Short Product Description 13

3.1 Summary of Features 133.2 Software options 15

4 Installing the Equipment 17

4.1 Inspect the package content 174.2 Installation Environment 174.3 Equipment installation 184.4 Ventilation 184.5 Power supply 19

4.5.1 AC power supply 194.5.1.1 AC power cable 194.5.1.2 Protective Earth/technical Earth 204.5.1.3 Connecting to the AC power supply 20

4.5.2 DC power supply 214.5.2.1 DC power cable 21

4.5.3 Powering up/down 21

5 Functional Description 23

5.1 Introduction 235.2 TS inputs 235.3 TS output 235.4 SFN adapter 235.5 Video over IP 23

5.5.1 Input and output 245.5.2 Protocol mapping 25

5.6 T2-gateway module 255.7 Management sub-system 26

5.7.1 Graphical user interface 265.7.2 Configuration database 265.7.3 Alarm manager 27

5.8 Time synchronisation 28

6 Physical Description 29

6.1 Connecting the CP560 296.1.1 Physical description overview 296.1.2 ASI ports 296.1.3 ASI input ports 306.1.4 ASI output ports 316.1.5 1 PPS Input 316.1.6 Ethernet Data Ports 316.1.7 SFP port 326.1.8 Power Supply 326.1.9 Ethernet Management Port 326.1.10 Technical Earth 326.1.11 Alarm/Reset 326.1.12 Serial USB interface 33

7 Operating the Equipment 35

7.1 Accessing the graphical user interface 357.2 Password protection 35

7.2.1 Resetting the password list 367.3 Changing the IP address of the unit 36

7.3.1 Changing IP address via the Web GUI 367.3.2 Changing the management port IP address via terminal interface 377.3.3 Detecting the management port IP address 38

7.3.3.1 USB Interface 387.3.3.2 Nevion Detect 38

8 WEB Interface 41

8.1 Login 418.2 Status header 428.3 Status 43

8.3.1 Current Status 438.3.2 Alarm log 45

8.4 Device Info 468.4.1 Product info 468.4.2 Alarms 49

8.4.2.1 Device alarms 498.4.2.2 Global configuration 508.4.2.3 Relays and LED 518.4.2.4 Alarm log settings 53

8.4.3 Port Mappings 548.4.4 Time Settings 558.4.5 Network 58

8.4.5.1 Interfaces 598.4.5.1.1 Main 598.4.5.1.2 Interface Settings 59

8.4.5.1.3 Manual IP Settings 608.4.5.1.4 Interface Status 608.4.5.1.5 Detect Settings 608.4.5.1.6 Alarms 618.4.5.1.7 Advanced 618.4.5.1.8 Status 628.4.5.1.9 VLAN 638.4.5.1.10 Main Settings 648.4.5.1.11 Manual IP Settings 648.4.5.1.12 Advanced Settings 648.4.5.1.13 SFP 658.4.5.2 IP Routing 738.4.5.3 TXP Settings 748.4.5.4 SNMP Settings 758.4.5.5 Tools 778.4.5.5.1 Ping 778.4.5.5.2 Traceroute 78

8.4.6 Clock Regulator 808.4.6.1 Main 808.4.6.2 Alarms 81

8.4.7 Configuration Manager 818.4.7.1 Save/Load Configs 818.4.7.1.1 Save Configuration To File 818.4.7.1.2 Load Configuration From file 828.4.7.1.3 Load Configuration from Remote Device 838.4.7.1.4 Load options 838.4.7.2 Boot Log 848.4.7.3 Stored Configurations 848.4.7.4 Emergency Switch 85

8.4.8 Maintenance 888.4.8.1 General 888.4.8.2 Software Upgrade 908.4.8.3 Feature Upgrade 91

8.4.9 Users 928.4.10 GUI Preferences 93

8.5 Inputs 948.5.1 Inputs Overview 94

8.5.1.1 IP Inputs 968.5.1.2 Switch Inputs 97

8.5.2 Input 988.5.2.1 Main 998.5.2.2 Alarms 1018.5.2.3 IP 1068.5.2.3.1 IP Configuration 1068.5.2.3.2 FEC 1088.5.2.3.3 Ping 1098.5.2.3.4 Regulator 1108.5.2.4 Services 112

8.5.2.4.1 Service List 1128.5.2.5 PIDs 1168.5.2.5.1 PIDs Grid 1168.5.2.5.2 PID rates 1188.5.2.6 Tables 1198.5.2.6.1 Tables 1198.5.2.6.2 Sources 1218.5.2.6.3 Settings 122

8.5.3 Switch 1238.5.3.1 Main 1238.5.3.2 Alarms 125

8.6 Outputs 1258.6.1 Outputs Overview 1258.6.2 T2-MI Output 1268.6.3 Main 1278.6.4 DVB-T2 128

8.6.4.1 Main configuration 1288.6.4.2 SFN Configuration 1318.6.4.3 PLP configuration 1338.6.4.3.1 Source bit rate control settings 1388.6.4.4 Modulation interface configuration 1398.6.4.5 Individual addressing configuration 1408.6.4.6 Future Extension Frames configuration 142

8.6.5 IP 1428.6.6 TS-OUT -> IP Destination 143

8.6.6.1 Main 1438.6.6.2 FEC 1468.6.6.3 Ping 148

8.6.7 Alarms 149

9 SNMP 151

9.1 SNMP agent characteristics 1519.2 MIB naming conventions 1519.3 MIB overview 151

9.3.1 Supported standard MIBs 1519.3.2 Custom MIBs 151

9.4 SNMP related configuration settings 1539.4.1 Community strings 1539.4.2 Trap destination table 1539.4.3 Trap configuration 154

9.5 Alarm/status related SNMP TRAPs 1549.5.1 The main trap messages 1549.5.2 Severity indications 1559.5.3 Alarm event fields 1559.5.4 Matching of on/off traps 1569.5.5 Legacy trap messages 157

9.6 Using net-snmp to access MIB information 1579.6.1 Reading a parameter with snmpget 1589.6.2 Writing a parameter with snmpset 158

10 Examples of Use 159

10.1 Intro 15910.2 Installation in a system 15910.3 Single PLP at 40MBit/s 15910.4 SFN operation 16110.5 Seamless SFN operation 16110.6 Redundant system with TNS541 TS Seamless Switch 162

10.6.1 Signal empty PLPs 163

11 Preventive Maintenance and Fault-finding 165

11.1 Preventive maintenance 16511.1.1 Routine inspection 16511.1.2 Cleaning 16511.1.3 Servicing 16511.1.4 Warranty 166

11.2 Fault-finding 16611.2.1 Preliminary checks 16611.2.2 PSU LED not lit / power supply problem 16711.2.3 Fan(s) not working / unit overheating 168

11.3 Disposing of this equipment 16811.4 Returning the unit 168

A Glossary 169

B Technical Specification 175

B.1 Physical details 175B.1.1 Half-width version 175

B.2 Environmental conditions 175B.3 Power 175

B.3.1 AC Mains supply 175B.3.2 DC supply 176

B.4 Input/output ports 176B.4.1 DVB ASI port 176B.4.2 Ethernet management port 176B.4.3 Ethernet data port 177B.4.4 Serial USB interface 177

B.5 Alarm ports 177B.5.1 Alarm relay/reset port specification 177

B.6 External reference 178B.6.1 10MHz/1 PPS input 178

B.7 Compliance 178B.7.1 Safety 178B.7.2 Electromagnetic compatibility - EMC 178B.7.3 CE marking 179B.7.4 Interface to “public telecommunication system” 179

C Forward Error Correction in IP Networks 181

C.1 IP stream distortion 181C.2 Standardisation 182C.3 FEC matrix 182C.4 Transmission aspects 185C.5 Quality of service and packet loss in IP networks 186C.6 Error improvement 187C.7 Latency and overhead 188

D Quality of Service, Setting Packet Priority 191

D.1 MPLS 191D.2 Layer 3 routing 191

D.2.1 CP560 configuration 192D.3 Layer 2 priority 192

D.3.1 CP560 configuration 192

E Validation of DVB-T2 Parameters 193

E.1 T2-Frame 193E.1.1 T2-Base 193E.1.2 T2-Lite 194

E.2 Physical Layer Pipe 194

F Estimated Transmission Time 195

F.1 How the CP560 uses the configured ETT value 195F.1.1 Example with 2 modulators 195

F.2 Implications of adjusting ETT 195F.3 How to set ETT 196

G Alarms 197

H References 207

History 9

ID: um_t2gateway CP560 DVB-T2 Gateway User’s Manual Rev. 2.2.B (5008)

1 History

Revision Date Comments

2.2 2012-03-09 – Added Input Switching feature description– Added T2 parameter validation tables in appendix E– Added DVB-T2 estimated transmission time description in appendix F– General updates to reflect changes in GUI, in particular DVB-T2 settings in chapter 8.6.4

2.0 2011-07-08 – Added FEC feature description– Added Transmitter Signature feature description– Added Reed-Solomon ASI FEC feature description– Added DVB-T2 MIP feature description– Added individual addressing functions description– Updated screenshots of the GUI

1.12.0 2011-02-02 – Added Joint bit rate control feature description– Added Port mapping feature description– Updated screenshots of the GUI

1.8.0 2010-10-21 – Added IP input feature description– Added SFP feature description– Added multiple PLP feature description– Added Leap Second handling feature description

1.6.4 2010-09-27 – Added 10 ASI card (2020) adjustments– Updated screenshots of the GUI (status/input)

1.6.0 2010-07-20 – Revised version including new features– Added IP output feature– Added individual addressing feature– Updated GUI screenshots

1.0 2009-11-17 – First version

10

CP560 DVB-T2 Gateway User’s Manual Rev. 2.2.B (5008) ID: um_t2gateway

Introduction 11


2 Introduction

2.1 ScopeThis manual is written for operators and users of the CP560 DVB-T2 Gateway and provides neces-sary information for installation, operation and day-to-day maintenance of the unit. The manualcovers the functionality of the software version 2.2.0 or later, and continues to be relevant to subse-quent software versions where the functionality of the equipment has not been changed. When anew software version changes the functionality of the product, an updated version of this manualwill 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 notesThroughout this manual warnings, cautions and notes are highlighted as shown below:

Warning: This is a warning. Warnings give information, which if strictlyobserved, will prevent personal injury and death, or damage to personalproperty or the environment.

Caution: This is a caution. Cautions give information, which if strictlyfollowed, will prevent damage to equipment or other goods.

Note: Notes provide supplementary information. They are highlighted foremphasis, as in this example, and are placed immediately after the relevanttext.

12 Introduction


2.3 Heed warnings

• All warnings marked on the product and in this manual should be adhered to. Themanufacturer 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 installedand operated.

• All operating and usage instructions should be followed.

• The safety and operating instructions should be retained for future reference.

2.4 Contact informationOur primary goal is to provide first class customer care tailored to your specific business andoperational requirements.

Please contact us at:

Telephone +47 22 88 97 50Fax +47 22 88 97 51E-mail [email protected] http://www.nevion.com

Mail and visiting address NevionNils Hansens vei 2NO-0667 OsloNorway

Short Product Description 13


3 Short Product DescriptionThe CP560 is part of the Nevion cProcessor product family for processing and handling of MPEGtransport streams. The cProcessor family represents a line of compact and powerful, yet cost-effective, products designed for advanced modification of MPEG Transport Streams.

The CP560 is a DVB-T2 gateway that uses the advanced capabilities of the cProcessor family torearrange the transport stream (TS) into the DVB-T2 modulator interface (T2-MI). In addition tothe data, this T2-MI interface contains signalling, control and timing information for the DVB-T2modulators.

3.1 Summary of FeaturesFeatures of the CP560 include:

• Transport Stream (TS) encapsulation in T2-MI packets

− Single or Multiple Physical Layer Pipe (PLP)

− Null packet deletion

− Input Stream Synchronisation (ISSY) support (short/long)

− Normal and high efficiency transmission mode

− Time interleaving support

• L1-Signalling

− Bandwidth selection (1.7MHz, 5MHz, 6MHz, 7MHz, 8MHz, 10MHz)

− Configurable signalling of the of the DVB-T2 frames

− Modulation up to 256-QAM

• SFN adaptation

− DVB-T2 timestamp for SFN networks (relative/absolute)

− 1 PPS timing reference input

− SNTP support for Absolute timestamps

• Individual addressing

− Multiple Input SingleOutput (MISO)/ Single Input SingleOutput (SISO) transmissionmode support for individual modulators

− Individual PAPR parameters for individual modulators

14 Short Product Description


• Transport stream monitoring

− TR 101 290 Priority 1 monitoring: Sync loss, CC error

− Monitoring of min/max bitrate for individual PIDs

− Output PID monitoring (CC errors)

• Flexible alarm configuration options

− Alarm levels freely configurable individually for each channel

− Individual setting of alarm levels based on PID values

• Compact, cost-effective solution

• 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

• Transmission of T2-MI transport stream over Gigabit Ethernet

• Reception of transport stream over Gigabit Ethernet

• IP transport stream Forward Error Correction (Rx and Tx)

• Several T2-MI output copies

− ASI ports may be configured as input or output copies

− Supports up to 8 IP output copies, each to any destination

• SFP (Small Form-Factor Pluggable) interface option

• Input Switching

− An input switch may be set as the source of a PLP

− An input switch may switches between 2 or more inputs

Short Product Description 15


3.2 Software optionsThe CP560 functionality depends on the software licences installed. The following table describesthe features available as software options. Please refer to Section 8.4.8.3 for more information howto obtain and enable feature upgrades.

Table 3.1 Functionality enabled through software licences

Functionality Code Maxvalue

Description

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.Number of PLPs activated PLPX 8 Maximum number of PLPs (Physical Layer Pipes).Number of inputports activated

TSIX 16 Controls the number of simultaneously activated transport stream inputs.

Joint bit rate control JBRC - Controls if the Joint Bit Rate Control feature is activated for sending PLPbitrate over SNMP to other devices.

Input switching ISW - Enables creation of input switching groups.Forward Error Correction FEC - Controls availability of the FEC feature for IP outputs and IP inputs.Ethernet data interface IP - Controls whether carriage of MPEG transport streams on Ethernet is made

available.DVB-T2 SFN T2SFN - Enables SFN synchronisation for T2 systems.Allow ASI inputs ASIN - Enables use of ASI input ports. Without this key the device can be used

with IP input only.Emergency switchsupport

ESW - Enables support for external switch panel to switch between pre-loadedconfigurations.

Connect control TCON - Enables supervision of the unit through the Connect Software.

16


Installing the Equipment 17


4 Installing the Equipment

Caution: The CP560 must be handled carefully to prevent safety hazardsand equipment damage. Ensure that the personnel designated to installthe unit have the required skill and knowledge. Follow the instructionsfor installation and use only installation accessories recommended by the

manufacturers.

4.1 Inspect the package content

• Inspect the shipping container for damage. Keep the shipping container and cushioningmaterial until you have inspected the contents of the shipment for completeness and havechecked that the CP560 is mechanically and electrically in order.

• Verify that you received the following items:

− CP560 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 PowerD-SUB male connector for soldering to the supply leads is supplied.

4.2 Installation EnvironmentAswith any electronic device, the CP560 should be placedwhere it will not be subjected to extremetemperatures, humidity, or electromagnetic interference. Specifically, the selected site shouldmeetthe 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 unitin 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 CP560.

• 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. Thisprevents damage to the product due to lightning and power-line surges.

Warning: If the CP560 has been subject to a lightning strike or a powersurge which has stopped it working, disconnect the power immediately.Do not re-apply power until it has been checked for safety. If in doubtcontact Nevion.

4.3 Equipment installationThe CP560 is designed for stationary use in a standard 19" rack. When installing please observethe 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 CP560 has all connectors at the rear. When mounting the unit, ensure that the instal-lation 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 holeson each side of the CP560.

4.4 VentilationOpenings in the cabinet are provided for ventilation to protect it from overheating and ensurereliable 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 throughopenings as they may touch dangerous voltage points or create shorts thatcould result in a fire or electric shock. Never spill liquid of any kind on orinto the product.

• This product should never be placed near or over a radiator or heat register. Do not placein a built-in installation (e.g. a rack) unless proper ventilation is provided in accordancewith the device airflow design as depicted in Figure 4.1 .

• The CP560may be vertically stacked in 19" racks without intermediate ventilation panels.In systems with stacked units forced-air cooling may be required to reduce the operatingambient temperature.

Figure 4.1 shows the air path through the unit, where cool air is taken from the left handside, seen from the front.



CP541

Cool

Air In

Warm

Air Out

Figure 4.1 Air path through the unit

4.5 Power supplyThe CP560 may be delivered rated for AC or DC operation, respectively.

Warning: This product should be operated only from the type of powersource indicated on the marking label. Please consult a qualified electricalengineer or your local power company if you are not sure of the powersupplied at your premises.

4.5.1 AC power supply

The CP560 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.

4.5.1.1 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 likelyto be trod on or pinched by items placed upon or against them. Payparticular attention to cords at plugs and convenience receptacles.

The unit is supplied with a two meter detachable mains supply cable equipped with a mouldedplug suitable for Europe, UK or USA, as appropriate. The wires in the mains cable are colouredin accordance with the wire colour code shown in Table 4.1.

Table 4.1 Supply cable wiring colours

Wire UK (BS 1363) EUROPE (CEE 7/7) USA (NEMA 5-15P)

Earth Green-and yellow Green-and yellow GreenNeutral Blue Blue White

Live Brown Brown Black



4.5.1.2 Protective Earth/technical Earth

To achieve protection against earth faults in the installation introduced by connecting signal cablesetc., the equipment should always be connected to protective earth. If the mains supply cable isdisconnected while signal cables are connected to the equipment, an earth connection should beensured using the Technical Earth connection terminal on the rear panel of the unit.

Warning: This unit must be correctly earthed through the moulded plugsupplied. If the local mains supply does not provide an earth connectiondo 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 isnot 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 suitablepoint 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 longpozidrive pan head. Using a longer screw may imply a safety hazard.

4.5.1.3 Connecting to the AC power supply

Warning: Do not overload wall outlets and extension cords as this canresult in fire hazard or electrical shock. The unit is not equipped with anon/off switch. Ensure that the outlet socket is installed near the equipmentso 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 CP560 mainsinput connector(s) and then to the local mains supply.



4.5.2 DC power supply

The CP560 can be delivered with a 48 VDC power supply for use in environments where thisis required. The DC power supply accepts an input voltage range of 36-72 VDC. Please refer toAppendix B for detailed specification of the power supply.

4.5.2.1 DC power cable

Units delivered with DC power supply have a 3-pin male D-SUB power connector instead of thestandard mains power connector. Also a female 3-pin D-SUB connector is supplied. The pin as-signment is shown in Table 4.2. The power cable itself is not supplied.

Table 4.2 DC power connector pinassignment

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 femaleD-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 CP560 power inputconnector.

4.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 hasfinished the start-up procedure, the fans will run at normal speed. Please check that all coolingfans 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.

22


Functional Description 23


5 Functional Description

5.1 IntroductionThe CP560 is a DVB-T2 gateway designed for the encapsulation of Transport Streams (TS) in T2-MI frames. The product offers an easy-to use WEB based user interface, a flexible and powerfulT2-MI encapsulation module and integration with network management systems via the SNMPinterface.

This chapter gives a brief description of the CP560 inner structure, allowing a better understandingof the device’s functionality, its operation mode and its applications.

Figure 5.1 shows a functional block diagram of the main components inside the CP560. A detaileddescription of the different blocks is provided in following sections.

5.2 TS inputsThe CP560 can include up to 10 ASI ports, 8 of them can be used as input ports and 2 as outputports.

The number of simultaneous TS inputs that can be enabled is limited by a software licence key.The default configuration includes only one input port and two output ports. If needed, furtherinputs can be enabled with the software licence key.

5.3 TS outputThe CP560 generates a T2-MI output. When using ASI output,the transport stream is presentedon at least one ASI output port. In addition one port is programmed to carry the same signal, asdescribed in Section 6.1.2.

The output is always re-clocked, configuring a wanted bitrate for the output stream.

The CP560 can transmit the same transport stream over IP via the extra physical Ethernet dataconnector(s) or via an SFP module inserted in the SFP slot.

5.4 SFN adapterThe product is fitted with an SFN adapter that generates an accurate DVB-T2 timestamp. Thisenables synchronisation of the output clock to the Network Time Protocol (NTP) or a 1PPS signalfor operation in SFN networks. The 1 PPS signal can be taken from an external source.

5.5 Video over IP



Figure 5.1 Product block diagram

5.5.1 Input and output

The CP560 supportsMPEG transport streams over IP, the functionality is protectedwith a separateSW licence.

The CP560 has 8 IP inputs, these are modelled to have the same functionality as the ASI inputports, and content received will be available to the DVB-T2 Gateway generating the output. Theinput streams can be either SPTS or MPTS and streams with or without RTP layer are accepted.

The DVB-T2 Gateway can generate one output and the operator chooses whether to transmit thisstream over IP or not.



TwoEthernet interfaces can be used simultaneously for video carriage, the interfaces are bi-directional.When using the SFP slot, one of the Electrical interfaces will be disabled.

5.5.2 Protocol mapping

Ethernet

14 bytes

[IEEE 802.3/802.3u]

IP

20 bytes

[RFC 769]

Optional

VLAN

4 bytes

[802.1q]

UDP

8 bytes

(RFC 768)

RTP

12 bytes

(RFC 1889)

1-7 MPEG TS packets

188 – 1316 bytes

[ISO/IEC 13818-1]

Figure 5.2 Protocol mapping

When transmitting T2-MI streams over IP, the protocol mapping is according to figure 5.2. TheVLAN framing and RTP encapsulation are optional.The RTP layer is important for diagnosing network related problems, since it contains a sequencenumber that can be used for packet loss detection.The maximum transfer unit (MTU) for Ethernet is usually 1500 bytes. This limits the number oftransport stream packets to embed into the outgoing Ethernet/IP frames to be between 1 and 7.

5.6 T2-gateway module

TSBBFRAMEBUILDER

TS Packetizer

Clock & Time

base

T2MI TS

T2

config

Scheduler

config

Rate Control

1PPS

Time stamp

L1 signaling

Figure 5.3 DVB-T2 Gateway module

The DVB-T2 Gateway module illustrated in figure 5.3 is the main module of the CP560, it en-capsulates TS-input packets in Baseband frames, generates an accurate timestamp and generatesL1-signalling frames. The resulting T2-MI frames are packetized and encapsulated again in TSpackets to be transported over a network.According to the DVB-T2 frame structure, T2-MI frames carrying user data are sent first followedby a timestamp frame and a L1-frame. The time stamp frames and L1-frames are generated ac-cordingly to the settings defined in the user interface.The DVB-T2 packet bitrate is kept constant by the time source or the 1PPS signal, this prevent theoverflowing of the buffer on the modulator side when the unit and the modulator uses the sametime source.



5.7 Management sub-systemThe management subsystem is a set of modules that handles all the interfaces to monitor andcontrol the operation of the CP560.

The management subsystem communicates with the users, both humans and machines, via thefollowing 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

Themanagement subsystem communicates with other internal modules tomake the unit performthe wanted operations.

5.7.1 Graphical user interface

Operatorsmonitor and control the CP560mainly via theAdobe FlashGUI application served fromthe device’s WEB server. The GUI application is accessed via a WEB browser that communicateswith the configuration framework through an HTTP/XML based protocol.

The device exposes extensive status information to the web GUI providing detailed reports andreal-time monitoring displays to the device administrator.

All the device configuration parameters available on the CP560 can be controlled from the webGUI.

5.7.2 Configuration database

The management subsystem processes configuration changes as transactions. All configurationchanges 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 thatmay 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 toanother.



Configurations exported via thewebGUI are formatted as human readable/modifiable XML files.These files can be viewed or altered using any standard text or XML editor such as WindowsNotepad.

To simplify cloning of devices, certain exported parameters within the XML file are tagged asdevice 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

• ASI Port mappings

• On-device stored configurations

5.7.3 Alarm manager

TheCP560 contains an integrated alarmmanager responsible for consistently displaying the alarmstatus 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 indexingscheme. These are classified as “System Alarms”.

Alarms are graphically represented in a tree structure optimized for simplified individual viewingand configuration. The “Device Alarm” tree is available from the “Device Info” page. The alarmtree 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. Alarmconfiguration 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 CP560 supports so-called Virtual Alarm Relays.These are highly programmable items that can be customised to react to virtually any given alarmevent or combination of alarm events. The status of each virtual alarm relay can be viewed in theGUI and can also be exported using SNMP. Details on configuring the virtual alarm relays can befound in the WEB interface section.



5.8 Time synchronisationThe CP560 contains an internal real-time clock that is used for internal timestamps and the gener-ation of DVB-T2 timestamps for SFN operation.

In order to generate precises SFN timestamps, the CP560 needs to be connected to both a NTPtimesource (for absolute time in seconds) and 1PPS (for subsecond time).

The internal time can be synchronised as follows:

• From NTP servers using SNTP protocol. Up to four NTP servers can be configured forNTP server redundancy (see section 8.4.4).

• Connect 1 PPS signal to the CP560 (see section 6.1.1) and enable 1 PPS synchronisation(see section 8.4.6).

• Then Resync the internal time of the CP560 (see section 8.6.4.1).

Physical Description 29


6 Physical Description6.1 Connecting the CP560

6.1.1 Physical description overview

The front panel provides two LEDs per CP560. The meaning of each LED indicator is shown intable 6.1.

Table 6.1 Front panel LED descriptions

Indicator Colour Description

Power Green This LED is lit when power is on and initialization is complete

Alarm Red This LED is lit when a failure is detected by the unit

These LEDs are also replicated on the rear panel, which is shown in figure 6.1.

Inputs

GND

OP

TIC

AL

USB

1PPS/

10MHz

ALARMPSU

ALARM / RESET

CONTROL

AC100-240V

0,7A 50-60Hz

ASI IN

ACTIVE

ASI 1 ASI 2 ASI 3 ASI 4

ASI IN

ACTIVE

ASI 5 ASI 6 ASI 7 ASI 8

DATA 2DATA SFP DATA 1

USB

Main output port

SFP Port

USB Port

Ethernet

Data Ports

Alarm / Reset

Interface1PPS

Input

Mains Power

Connector

Technical

Earth

output copy

Ethernet

Management Port

LED replica of

front panel

Figure 6.1 Rear panel on 2 ASI card variant

Remove mains supply before moving or installing the equipment. Ensure ESD precautions areobserved while interconnecting equipment.

6.1.2 ASI ports

The CP560 can be shipped with one ASI card with 10 ASI connectors as shown in 6.2. Anotherconfiguration includes 8 ASI connectors on the back panel as shown in figure 6.1.When the CP560 is used with ASI output, one port is reserved for the single supported TS output.A number of the ports are reserved for input, while the remaining ones can be configured either asinputs or copies of the main ASI output port. Switching of the direction on a port does not requirea re-boot, and can be performed while the other ports are in service.

30 Physical Description


The available options for each port are shown in table 6.2 for the 2 ASI card and 1 ASI card con-figuration.(X) means valid option, (-) means not valid.

Table 6.3 Port direction options onthe 10 connector variant

ASI port Input Output Copy Output

1 X X -2 X X -3 X X -4 X X -5 X X -6 X X -7 X - -8 X - -9 - X -

10 - - X

GND

OP

TIC

AL

USB

1PPS/

10MHz

ALARMPSU

ALARM / RESET

CONTROL

AC100-240V

0,7A 50-60Hz

DATA 2DATA SFP DATA 1

USB

Inputs/Ouputs Mains Power

Connector

Technical

Earth1PPS

Input

(For optional

SFN operation)

Alarm / Reset

Interface

LED replica of

front panel

Ethernet

Management Port

Ethernet

Data PortsUSB Port

SFP Port

1 2 3 4 5 6 7 8 9 10

Inputs Outputs

Figure 6.2 Rear panel with 10 ASI connectors

6.1.3 ASI input ports

All physical input ports can be available for usage, but the number of simultaneously enabledports is limited by the licence key Number of ASI ports activated.In the eight ports configuration, each ASI input port has two LEDs associated with it. The yellowLED indicates active input and the green LED indicates that sync is detected.



Table 6.2 Port direction options on 2ASI card variant

ASI port Input Output Copy Output

1 X X -2 X X -3 X X -4 X X -5 X X -6 X X -7 - X -

8 - - X

Table 6.4 ASI Input LED description

LED Colour Description

Upper yellow Lit when input is enabled, unlit otherwise.

Lower green Lit when input is in sync, unlit if not in sync.

6.1.4 ASI output ports

The CP560 can transmit 1 T2-MI ASI stream. The rightmost connector is used as the principle ASIoutput. Some of the other ports can be configured as copies of the principle output as shown inSection 6.1.2.

One LED is used for each ASI output port: A green LED is lit whenever the output is enabled.

6.1.5 1 PPS Input

The CP560 comes with a 1 PPS input. Activating the port is a software option that enables thedevice to operate as a MIP inserter in SFN networks.

The 1 PPS port is mounted to the right, below the output ports.

1 PPS inputBNC female 50 ohms

6.1.6 Ethernet Data Ports

The CP560 comes with two Ethernet data ports. These data ports can be used to carry MPEGtransports streams if the licence key Ethernet data interface is installed.These ports can also be used for management of the device.

32 Physical Description


Table 6.5 ASI Output LED description

LED Colour Description

Lower green Lit when output is enabled, unlit otherwise.

Upper Not in use for outputs

6.1.7 SFP port

The CP560 has one slot for SFP modules.

When using the SFP slot, the DATA-2 Electrical Ethernet data port is turned off. This is done onthe ’Device Info->Maintainance’ page.

To use the SFP slot, the licence key SFP modulemust be installed.

6.1.8 Power Supply

Section 4.5 provides details of the power supply, protective earth and security. Read all theseinstructions, prior to connecting the units power cable.

6.1.9 Ethernet Management Port

The CP560 provides one Ethernet port for control and management. Connect the managementport to the management network. The LEDs for the management port are used as follows:

6.1.10 Technical Earth

Connect the Technical earth to a suitable earth point.

6.1.11 Alarm/Reset

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 orwhen the unit is not powered. Please refer to section 8.4.2.3 for a description of how to programthe relays.

The pin out of the connector is shown in table 6.7.

When there is a critical (level 6) alarm in the unit, unit is not powered or any other programmedcondition for relay 1 is satisfied, there will be a connection between pin 6 and pin 7. When theabove 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 functionhas been enabled. The connection must be held for 0.5 seconds in order to active the reset. Thiscan be used to force a hard reset of the unit from an external control system. This pin can also beused as a general purpose input (GPI).



Table 6.6 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

Table 6.7 Alarm/Resetconnector pin out

Pin Function

1. Relay 2 - Closed on alarm (NC)2. Relay 2 Common3. Relay 2 - Open on alarm (NO)4. Prepared for +5V Output5. Ground6. Alarm Relay - Closed on alarm (NC)7. Alarm Relay Common8. Alarm Relay - Open on alarm (NO)

9. Optional Reset Input / GPI

For more details regarding the alarm relay, please refer to Appendix on Technical SpecificationsB.

6.1.12 Serial USB interface

USB interface:

• USB 1.1

• Mini USB connector

The USB interface requires a special COM port driver on the PC that shall communicate with thedevice. This driver is provided on the product CD shipped with the device. The USB interface isintended for initial IP address setup.

34


Operating the Equipment 35


7 Operating the EquipmentThe CP560 is configured and controlled locally and remotely through a Flash-basedWeb interface.The only application required on the computer to use this interface is aWebbrowser and theAdobeFlash Player.

Note: Adobe Flash Player 9.0 or newer is required to use the Web interfaceof the CP560. As a general rule it is recommended to always use the latestofficial 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 withthe device. Alternatively, the latest Adobe Flash Player can be downloaded free ofcharge from http://www.adobe.com.

Note: When using Microsoft Internet Explorer, version 6.0 or higher isrequired. It is however recommended to upgrade to version 8.0 or newerfor best performance.

7.1 Accessing the graphical user interfaceThe default IP address of the CP560 will most probably not be suitable for the network where theunit will operate. Therefore the user should change the IP address of the management interfaceso that access may be gained from the network.The CP560 offers two options to alter the user interface IP address; through an Ethernet connectionor using a USB terminal interface. If yourmanagement computer allows setting a fixed IP address,change the IP address using the Ethernet option described in Section 7.3.1.If a static address cannot be configured on your management computer, Section 7.3.2 gives theprocedure to initially configure device network parameters (IP, netmask, etc...) using the USBterminal interface.Configuring the device functionality according to operational needs is done using the Web inter-face, see Chapter 8.

7.2 Password protectionRemote access to the device is controlled by password protection. If you access the CP560 usingthe 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 deviceoperator natal Configure setting, cannot alter passwords

guest guest View configuration and alarm logs

http://www.adobe.com






36 Operating the Equipment


The passwords can later be changed, either from the Web GUI or via the terminal.

7.2.1 Resetting the password list

If a password is lost, the password list can be reset to factory defaults via the local USB terminalinterface. 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 terminalvia the local USB interface. In remote terminal sessions with a Telnet

client, administrator privileges are required to run the same command.

7.3 Changing the IP address of the unitThe CP560 is supplied with a dedicated management Ethernet port, labeled Control. The defaultIP configuration (IP address and netmask) of the port is 10.0.0.10/255.255.255.0.

7.3.1 Changing IP address via the Web GUI

Changing the default IP address using theWeb interface requires that yourmanagement computermay be configured with a static IP address.

Note: Avoid connecting through a network at this stage, as this may giveunpredictable results due to possible IP address conflicts.

1. Connect an Ethernet cable directly between the PC and the Ethernet control port of theCP560. Configure the PC to be on the same sub net as the CP560. See Figure 7.2.

2. Open yourweb browser and type http://10.0.0.10 in the address field of the browser. Loginto the GUI with username admin and password salvador.

3. Browse to Device Info -> Network -> Control in the GUI, and set the correct IP addresssettings. Click apply to activate the new parameters. Figure 7.1 shows this GUI screen.

Note: Contact with the unit’s GUI will be lost. Please type http://<yournew IP address> in your browser to reconnect to the unit.

Windows XP exampleThe screen-shot in Figure 7.2 shows how to configure the network interface in Windows XPto communicate with the CP560 with factory default settings. The IP address/netmask is set



Figure 7.1 Configuring network settings via the Web GUI

Figure 7.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 CP560, and does not conflictwith the IP address of the device.

Note: If several new devices are accessed, one after another, the ARPcache of the computer from which the devices are being accessed mayhave 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 commandline typing the command ’arp -d *’

7.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 beomitted if the driver has already been installed.)

38 Operating the Equipment


2. Connect your computer USB port to the CP560 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 onyour 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 >appprompt 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.0and the default gateway to 10.40.80.1.

Note: The product CD shipped with the CP560 contains a USB driverto use for serial communication with the device on the USB port. TheMS 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 portnumber to use on the PC. Drivers retrieved from http://www.ftdichip.com will alsowork, but these may not have the same COM port number mapping.

7.3.3 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 optionsavailable. The simplest solution is connecting through the USB interface.

7.3.3.1 USB Interface

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

7.3.3.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 contactingNevion Support (see Section 2.4). An User’s Manual is also included.

The Nevion Detect software detects devices by sending broadcast messages that the CP560 andotherNevion deviceswill recognize and reply towith some essential information. The PC running



Nevion Detect may be on a totally different subnet than the CP560, such that the device will bediscovered regardless of IP addresses and IP submasks.

Warning: Some Ethernet equipment might block broadcast traffic. Con-nect your PC directly to the CP560 to avoid this.

Note: It is possible to avoid that the CP560 is detected by the NevionDetect software. See Section 8.4.5.1.1 for details on how to do this.

40


WEB Interface 41


8 WEB InterfaceThe CP560 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 functionalityand 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 CP560 and get status infor-mation.

8.1 LoginAccess the CP560 by entering its IP address in the address field of your favourite browser. Whenaccessing the CP560 the first time, the progress bar (Figure 8.1) should appear while the Flashapplication is loading from the device.

Figure 8.1 Flash application loading

When the loading of the Flash application is finished, the login window (see Figure 8.2) is dis-played. Type the username and password to enter the GUI application. The default passwordsare listed in Section 7.2.

Figure 8.2 GUI login window

The login dialogue has an option “Save password”, which makes the browser store the usernameand password in a cookie and use them as default values at next login.

42 WEB Interface


8.2 Status header

After successful login the start page is shown. The top part of the page (shown in Figure 8.3) iscalled the status header.

Figure 8.3 The status header

In the status header the product name is shown on the left hand side, along with the Nevion logo.The status bar displays an indicator showing the overall alarm status of the device. The colour ofthe indicator shows the highest level alarm currently active in the unit. It is green if no alarm isactive. Other possible colours are described in Appendix G.Several items are presented in the right corner/section of the header. Starting from the left:

• The user defined device name, if entered.

• A button to log out from the GUI.

• A button to switch current user level.

• A text showing the current user name.

• The local device time.

• A button for minimising the header. Using this hides a lot of the header information andgives more space for the rest of the page.

• An activity indicator.

Note: The activity indicator shows one box for each request beingprocessed 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 withthe communication between the device and the computer, or the device may bebusy. If the device has not responded to a request within 20 seconds, the indicatorturns yellow. If no response has been received after 40 seconds, it turns red.

A tab bar is located beneath the status header. The exact number of tabs and tab labelling dependson the units operational mode and licences. Clicking a tab will open the corresponding page witha navigation pane to the left as shown in Figure 8.4. This pane is used to navigate between sub-pages of the tab.

Figure 8.4 Status navigator

WEB Interface 43


Note: The navigator can be collapsed to economise on screen space. Clickthe vertical grey line with two small arrows to the left of the navigator.

8.3 StatusThe status page presents an overview of the device operational status as well as a log of alarmevents.There are two sub-pages within the status page.

Current StatusIndicates the running status of the device.

Alarm LogPresents the device alarm log and provides operations for clearing the log or exporting it asa comma separated value file (.CSV).

8.3.1 Current Status

Figure 8.5 Current status

This page displays the current status of the device. It consists of a block diagram illustrating thedevice with its input and output ports, an overview of the currently active network interfaces anda list of currently active alarms.

Block DiagramThe 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 variousseverities and colours used are described in Appendix G.

44 WEB Interface


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 theport. 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 blockin front of aMUX 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 configurationpage 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 whichinformation to clear.

Current AlarmsThe bottom part of the page shows the currently active alarms. Some alarms may containseveral 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 aLED). The colour of the indicator represents the severity level configured for the specifiedalarm. The various severities and colours used are described in Appendix G.

The Current Alarms table contains six columns:

DescriptionDescription of the alarm condition.

For sub-entries, the extended index is shown in brackets. To the left is an indicator visualisingthe severity of the alarm. The indicator has a tool-tip providing a textual description of thealarm severity.

On TimeThe time when the alarm was raised.

Alarm typeCategory of the alarm, i.e. Port, System, Switch etc.

SourceThis identifies the source of the alarm. For port alarms, this is a reference to the specificport raising the alarm. This field has a tool-tip showing the subid1 and subid2 values for thealarm.

Subid1Reserved for future use in multi-slot chassis and is always set to 1 in the CP560.

Subid2The device or port to which the alarm relates. The value is zero for alarms that arerelated to the device rather than to a specific port. Values of 1 and up reference specificports.

Alarm IDEach alarm condition has an associated numerical alarm ID.

WEB Interface 45


DetailsAn optional string to provide more alarm information in human readable form. The formatof this string depends on the alarm type. Hovering the mouse over this field produces atool-tip displaying the full text.

A detailed overview of alarm conditions is given in Appendix G.

8.3.2 Alarm log

Figure 8.6 Alarm log

The alarm log shows every alarm that has been triggered since the last time the alarm log wascleared.

The table consists of the same columns as the Current Alarms table, but does not show details bydefault. You can change which columns to show, including the details column, in Section 8.4.2.4.Additionally a column named Off Time shows the time the alarm condition was cleared. Rowswill 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 therow. The tool-tip entries are:

Sequence #A number identifying this specific alarm instance. This number is incremented each time analarm condition is raised.

SubID 1The primary numerical index of the alarm instance. This index is reserved for future use andis always set to 1 in the CP560.

SubID 2The secondary numerical index of the alarm instance. When the alarm is of type Port alarmthis index contains the port number for which the alarm was raised. Other types of alarmsmay use this index to identify a sub module, but normally it is set to 0.

46 WEB Interface


SubID 3The tertiary numerical index of the alarm instance. The use of SubID 3 depends on the typeof alarm. Some of the Port type alarms use this index to signal the PID value or Service IDfor which the alarm was raised. For example, if the CC Error of a PID is raised then the PIDvalue is given by SubID 3.

DetailsAn 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 alarmlog.

To the right of the table are three buttons and a check box.

Clear Alarm LogClears all alarms from the alarm log.

Export to FileSaves the alarm log to a comma-separated value (.CSV) file. The button opens a file dialoguewhere the user can choose the destination to save the file on the computer.

Export to BrowserOpens 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 updatesThis check box can be unchecked to stop the log from scrolling if new alarms are triggeredwhile watching the log.

The alarm log is stored in non-volatile memory, so the content is kept even if the unit is rebooted.

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.

8.4 Device InfoThe device info page contains all the information and settings that are not related to a single inputor output port. It is divided into multiple sub pages accessed via the navigation list to the left. Inthe list of physical interfaces in the navigation list, the currently active interface is shown in bold.See Figure 8.7.

The exact layout of the navigator depends on the resources and features currently available in thedevice.

8.4.1 Product info

The product info page contains general device information.

NameConfigures the current user defined name of the unit. This parameter, together with the

WEB Interface 47


Figure 8.7 Device Info navigator

Figure 8.8 Product Information

management network parameters are used as device identifiers and remain untouched if theunit configuration is changed by loading a different configuration file. See Section 8.4.7.The device name is shown in the web GUI status header (see Section 8.3.1), and in the webbrowser title bar to facilitate identification of each device.

Inventory IDConfigures the current user defined inventory ID of the unit. This parameter, together withthe management network parameters are used as device identifiers and remain untouchedif the unit configuration is modified. It is only intended as a label/tag and will not affect theoperation of the unit.

Configuration IDConfigure a user defined name for the current configuration of the unit. This name will, ifgiven, be displayed in brackets after the unit name in the status header as shown in Figure8.3. The Configuration ID does not, as opposed to the Name and Inventory ID fields, remainuntouched when loading a new unit configuration. Loading a new unit configuration willchange the Configuration ID. See Section 8.4.7 on how to load a new configuration.

48 WEB Interface


Product nameDisplays the name of the product as designated by Nevion.

Serial numberThe serial number of the device.

Software versionThe version of the software currently installed on the device. The software version is givenby the following syntax:

<major_version>.<minor_version>.<patch_version>

The convention for the SW version numbering is as follows:

major_versionIncremented for significant SW changes.

minor_versionIncremented for minor changes. The minor version number is even for official retailreleases and odd for beta releases.

patch_versionIf minor_version is even, patch_version gives the patch level of that version. A patchlevel of zero means the SW is built on the latest code base, an even patch_versionmeansthis is a released SW patch on a previous release. An odd patch_versionmeans that thisis a test version. If minor is odd, this is a beta version, and the patch_version simplygives the build number.

Software build timeReports the time of which the current release image was built.

Device up timeThe amount of time that has passed since the device was last reset.

Internal temperatureThis shows the current internal temperature of the unit in degrees Celsius and Fahrenheit.

Fan speedThis bar chart shows the current speed of the device fans relative to full speed.

Flash Power LED buttonThe 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 ofthe button extends the blinking period by five seconds up to a maximum of about 30 secondsof blinking.

WEB Interface 49


8.4.2 Alarms

The Alarms page is shown in Figure 8.9:

Figure 8.9 Alarm configuration

This page displays the status of all system alarms and allows the user to program the severityof these alarms. Global alarm configuration is performed on this page, as well as alarm relayconfiguration and alarm log configuration.

It gives access to the following sub pages:

• Device Alarms

• Global configuration

• Relay and LED configuration

• Alarm Log Settings

8.4.2.1 Device alarms

The page shown in Figure 8.9 provides the administrator with an interface to view the status andconfigure the behaviour of all alarms related to the system. At the top the Reset Alarm Countersbutton 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 ofthe folder icon and the specific indicator represents the current status of the alarm. The text to theright 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 IDThe internal numerical ID of the selected alarm.

50 WEB Interface


AlarmTitle of the alarm.

DescriptionBrief description of the condition of the alarm.

SeverityA configurable option defining the severity of the alarm. Options in the pull-down box rangebetween Filtered (meaning ignored) to Critical. The text in brackets represents the defaultsetting.

Alarm turned onThe number of times the alarm has transitioned from off to on since last reset of the alarmcounter.

Error countNot used.

’Reset Counters’ buttonWhen 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 ofall the alarms in the Device Info tree.

8.4.2.2 Global configuration

Figure 8.10 Global alarm configuration

This page provides an interface to configure globally the behaviour of all alarms. By default portsuse 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 omittedfrom the alarm log and trap transmission.

WEB Interface 51


Edited rows are highlighted until changes have been applied.

Tip: For the Log and Send Trap columns, you can quickly select/deselectall items by right-clicking on the header fields in the columns.

8.4.2.3 Relays and LED

This page lets the user configure the alarm severity level that shall turn the relays and alarm LEDon. The behaviour of Alarm relay 1 and Alarm relay 2, and the Alarm LED may be configuredindividually for each alarm severity level. Note that the Alarm relay 1 and the Alarm LED willalways be enabled for alarm severity level Critical, as indicated by the disabled check boxes in theRelay and LED level triggers field. The current state of the relays and LED is indicated inside theassociated brackets.

Figure 8.11 Relays and LED configuration

For further details on the physical relays refer to Section B.5.1.The Virtual Relays field shown in Figure 8.11 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 youmaywant to enable a relay in case a specific alarm ID turns up. In anothercase you may want to enable a relay if a specific alarm turns up on a given port.Each relay status are exported on SNMP. Activation of a virtual relay also generates a specificalarm, named "Virtual alarm relay activated" (ID=169).The key element in the settings of the virtual relays is the Expression value. The expression isvery close to SQL in syntax and specifies when the relay should be activated. The behaviour is asfollows for each virtual relay:

52 WEB Interface


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 timesee 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 isactivated.

The expressions are validated before they are accepted by the unit. Table 8.1 shows the fieldvalues you may enter in an expression.

Table 8.1 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

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 withthe supported list of operators this gives great flexibility in constructing advanced “match” pat-terns.

Table 8.2 summarises the operator types you are allowed to use. Please note that the examplesbelow are used for illustration purposes only. For example, the plus and minus operators may notbe very useful in practise, but they are included in this table for completeness.

Table 8.2.a 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

WEB Interface 53


Table 8.2.b Legal operators to use in expressions

Operator Description Sample

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

Table 8.3 Expression examples

Task Expression Count threshold value

To generate an alarm when any alarm withID = 200 turns up (independent on source)

id = 200 1

To generate an alarm when alarm with ID =200 turns up on port with ID = 1 (subid2 =1)

(id = 200) AND (port = 1) 1

To generate an alarm when alarm with ID =200 turns up on both port 1 AND port 2

(id = 200) AND ((port = 1) OR (port= 2))

2

Note the last example in the table: Here the count threshold value must be set to 2 to get theexpected 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 alarmlist.

8.4.2.4 Alarm log settings

This page is used to set alarm log properties.

Figure 8.12 Configuring the alarm log

54 WEB Interface


Log delimiterThis 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-importingof the exported file into your favourite tool used to inspect the file content.

ColumnsEach of the columns in the alarm log table has a checkbox. Columns that are selected areshown on the alarm log page.

8.4.3 Port Mappings

Figure 8.13 ASIport direction control

This page offers an interface to configure the direction of the installed ASI ports. The valid optionsare visible as selectable radio buttons for each port.

The number of ports shown in the portmap grid corresponds to the number of physical connectorsinstalled in the chassis and the meaning of the different choices are:

ModeDirection of the port, with two choices:

InputUse the port as anASI input to themultiplexer. All input ports can be used, but the num-ber of inputs that can be enabled simultaneously is limited by the licence key Numberof input ports activated.

Output-CopyUse the port as an ASI output, transmitting the multiplex generated by the unit.

The valid selections are also documented in Section 6.1.2.

WEB Interface 55


PLPIf an ASI port is currently being used as input source for a PLP, the PLP id will be listed in thePLP column. ASI inputs used as source for a PLP may not be port mapped to ASI outputsuntil it has been removed as source for the specified PLP. This must be done as shown inSection 8.6.4.3.

Configure the mapping that best matches your needs and press apply to activate the new matrix.Re-configuration does not require re-booting. The choices made will be reflected in the logicalblock diagram of the device on the status screen (see also Section 8.3.1)

Note: The port map settings are tagged to follow the device (see Section5.7.2, and even though the parameters are exported in the configurationfile format, they are not overwritten when loading a configuration file via

the GUI to another device.

8.4.4 Time Settings

Figure 8.14 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 clocksynchronisation. The main use of the device time is stamping the entries of the alarm log.

The page consists of several parts. Top left is theGeneral box, containing the following parameters:

Current timeThe current time as reported by the device.

56 WEB Interface


Time zoneDrop-down list to configure the time zone of the unit.

StatusThe status of the time synchroniser.

ActiveThe time source currently in use by the time synchroniser.

TheManual Adjust Time field allows the operator to set the time. The manually configured timewill 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. Disabledtime sources are greyed out. Enabled time sources are shownwith an indication of the time sourcestatus. 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, andback again by using the arrow-right button. Time sources in the left hand list are used by the timesynchroniser 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 ordown arrows to the left of the list to increase or decrease, respectively, the item priority. The timesynchroniser will use the time source with the highest priority whose status is “OK” (representedby a green indicator).

Figure 8.15 Time Settings - Add time source

To add a time source to the system, click the “Add Timesource” button, which brings up the dialogshown in Figure 8.15 with the following fields:

Timesource type

SNTPTime source retrieving time from an SNTP server.

Server addressSpecify the server IP address here.

WEB Interface 57


TDT TOT or STTTime source retrieving time from DVB TDT, DVT TOT or ATSC STT time tables on aport.

Input sourceLists ports that can be used as time sources with the selected time source type(Figure 8.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 inputswitch group, whichwill make the time source retrieve the time from the currentlyactive input in the switch.

To remove time sources, Select them in the list and click the “Remove Timesource” button. Timesources for dynamic ports such as IP inputs and Switch inputs, are automatically removed if thedynamic port is removed.Located below the lists is also a field to define themaximumallowed time interval betweenupdatesfrom the currently used time source. Exeeding this interval the source is considered “Not OK” andthe 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 sourceselected the box may contain some or all of the following parameters:

ActiveA 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 canbe disabled.

IP addressSpecifies the IP address of an SNTP time server source to poll for updates.

TypeType of time source selected. The sources are product dependent, but SNTP is always avail-able.

Last updated timeThe most recent time value received from the time source.

StateThe current state of the time source.

ReferenceProvides the time reference source address of accessed time source.

Reference stratumIndicates the hierarchy level of the current time source. The master reference is at stratum 0(highest).

Reference statusIndicates if the time source is currently governed by a time source at a higher stratum.

Reference precisionThe expected timing accuracy of the current time source.

58 WEB Interface


8.4.5 Network

Figure 8.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 charactersindicate the web management interface connection. An interface shown in grey colour meansthat the interface is disabled. There may be physical interfaces on the unit that are not shown inthis table as the availability of each interface may vary with the installed software licences andoperational mode.

InterfaceA label identifying the interface. If it is a physical interface with virtual interfaces attached toit an arrow is shown. Clicking this arrow will expand/collapse the list of virtual interfaces.

IP AddressThe IP address configured for this interface.

Link SpeedThe current link speed detected for this interface. Applicable to physical interfaces only.

Duplex ModeThe duplex mode detected for this interface, half or full duplex. Applicable to physical in-terfaces only.

TX BitrateThe bitrate currently transmitted through this interface. Applicable to physical interfacesonly.

RX BitrateThe bitrate currently received through this interface. Applicable to physical interfaces only.

EnabledShows whether the interface is currently enabled.

DataShows whether data traffic is currently enabled for this interface.

WEB Interface 59


ManagementShows whether management traffic is currently enabled for this interface.

8.4.5.1 Interfaces

Each available network interface has an entry in the Navigator list. Selecting an interface bringsup pages where it is possible to configure the interface and view its status. Accessible parametersvarywith the interface selected since the functionality of the available interfaces are not necessarilyidentical.

8.4.5.1.1 Main

Figure 8.17 Main IP settings

This page provides the main configuration settings for the physical interface.

Caution: Modifying the settings of the interface you are currently usingfor the GUI application may cause loss of contact with the unit. Make sureyou will still be able to contact the unit before applying changed settings.

8.4.5.1.2 Interface Settings

Enable interfaceEnables/disables the interface. It is not possible to disable the currently used managementinterface.

Media SelectProvides a choice between network port Data 2 and the SFP module for the second datainterface. Select RJ-45 to use the data port marked Data for data traffic. Select SFP to use theSFP module for data traffic.

Speed/duplex modeThe speed and duplex mode of the interface. The Auto setting enables automatic speed andmode negotiation for the Ethernet link. This option is not available for SFP interfaces.

60 WEB Interface


Note: Modifying the default settings of interface duplex to anything otherthan auto can cause unpredictable results unless all peer systems accessingthe port use similar settings. For more technical information regarding auto

negotiation and duplex mismatch, refer to theWikipedia duplex mismatch article(http://en.wikipedia.org/wiki/Duplex_mismatch).

8.4.5.1.3 Manual IP Settings

IP addressIP address of the interface.

Subnet maskThe subnet mask of the interface.

GatewayThe default gateway address for the interface.

8.4.5.1.4 Interface Status

MAC addressThe Ethernet Media Access Control (MAC) address of the interface.

Link speedSpeed of current connection.

Duplex modeShows duplex of current connection.

8.4.5.1.5 Detect Settings

Detect configurationApplies to the Control interface, only.These two boxes enable read and write attributes of the Nevion Detect IP assignment servermodule. This server is a stand-alone PC application that can be used to discover Neviondevices on a local network and assign IP addresses to them.

Enabling the Read option makes the CP560 visible for the Nevion Detect on the LAN. If theWrite option is enabled the IP address of the CP560 may be configured using the Nevion De-tect. These options do not affect the operation of the device from themanagement applicationNevion Connect.

http://en.wikipedia.org/wiki/Duplex_mismatch




WEB Interface 61


8.4.5.1.6 Alarms

Alarms related to the interface are listed on the Alarms page. Clicking an alarm opens the field toconfigure the alarm. Please see Section 8.4.2 for alarm configuration details.

Figure 8.18 Network interface alarms

At the top of the page two radio buttons are provided to select between displaying error count orerror severity. In addition all alarm counters related to this interface may be reset.

8.4.5.1.7 Advanced

This sub-tab allows configuring advanced IP settings of the interface.

Figure 8.19 Advanced IP settings

Allow ping responseCheck this box to filter incoming ICMPmessages. If this option is not enabled the device willnot answer ping requests to this port.

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

Allow data trafficTick this box to allow data traffic on this interface. It is not possible to enable data traffic on themanagement interface.

Multicast routerThis 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 Usemulticast router option in the "IP Output" page, Section 8.6.6.1.

62 WEB Interface


IGMP versionThis 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 theselected version even if it is not supported by the network.

8.4.5.1.8 Status

Figure 8.20 Interface Status

This page shows detailed status and error information on the selected physical interface. Differenttypes of interfaces support different status and error parameters; not all parameters listed will beshown for all interface types.

The Ethernet Status field:

Link speedThe detected link speed of the interface.

Duplex modeThe detected current duplex mode of the interface. The duplex mode indicates whether datamay flow in one direction (half duplex) or bidirectionally (full duplex).

The following parameters are available for both received and transmitted packets:

bitrateThe total bitrate received/transmitted.

loadInterface load, measured relative to max speed.

Total packetsThe total number of IP packets received/transmitted.

WEB Interface 63


Good packetsThe number of IP packets received/transmitted containing valid CRCs.

Multicast packetsThe number of IP multicast packets received/transmitted by the interface.

Broadcast packetsThe number of broadcast packets received/transmitted.

OctetsThe number of octets received/transmitted

The Errors field:

CRC errorsNumber of packets received with CRC errors.

Alignment errorsNumber of packets detected with alignment errors (non-integer number of bytes).

Receive errorsNumber of erroneous packets received.

Missed packetsNumber of packets missed.

Link symbol errorsNumber of link symbol errors detected.

Carrier extension errorsNumber of carrier extension errors detected.

Receive length errorsNumber of packets with invalid size.

The SFP Info field is only shown if the SFP interface is active. It displays information provided bythe SFP module installed.

8.4.5.1.9 VLAN

This page is only shown on interfaces with VLAN (virtual interface) support. The page allowsadding, 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 interfaceare edited by selecting the interface in the grid first.

Once editing is finished, clicking the Apply button will commit all the changes. Hitting Refreshwill cancel all changes.

In addition to the Apply and Refresh buttons there are buttons to enable adding and removingVLANs.

64 WEB Interface


Figure 8.21 VLAN configuration

8.4.5.1.10 Main Settings

Enable interfaceEnable/disable the virtual interface.

VLAN IDThe VLAN id of this virtual interface. Must be in the range 1-4094. All virtual interfaces onone physical interface must have a unique id.

VLAN priorityThe VLAN priority of this virtual interface. Numers 0 to 7 are valid. For further informationon VLAN priority usage, see reference [7].

8.4.5.1.11 Manual IP Settings

IP addressThe IP address of the virtual interface.

Subnet maskThe subnet mask of the virtual interface.

GatewayThe gateway address to use for the virtual interface.

8.4.5.1.12 Advanced Settings

Enable data trafficChecked box enables the virtual interface to allow video data traffic. Not shown for dedicatedmanagement interface.

WEB Interface 65


Enable management trafficChecked box enables the virtual interface to allow management traffic.

Enable pingChecked box enables the virtual interface to respond to ping messages.

Multicast routerThe multicast router for this virtual interface. Only visible if multicast is allowed.

IGMP verProvides selection of the IGMP version to use. Not applicable to the "Control" interface.

8.4.5.1.13 SFP

The SFP tab is visible for the second network interface if this interface is set to use SFP. How toenable the SFP is described in section 8.4.8.1 , provided the appropriate licence has been installed.

Figure 8.22 The Device Info > Network > SFP tab

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 thedifferent SFPmodule types. For eachmodule type the CP560 stores a configuration file that can beedited “off-line”. These pages are visible only if SFP configuration has been licensed. The settingswill not be committed to the module until writing of the file is expressly initiated.

The SFP Status page, shown in figure Figure 8.23, provides an overview of themodule status. Theappearance of the status page and the range of parameters shown depend on the type of moduleattached.

TheModule General Status field displays the status of the module as seen by the CP560.

SFP PresentIndicates that the module has been detected by the CP560.

VendorShows the vendor name.

RevisionIndicates the module revision.

66 WEB Interface


Figure 8.23 The SFP status page

DateIndicates the revison date.

Part numberThe module part number.

Transceiver typeThe type of transceiver inside the SFP module. Only a limited range of transceivers is com-patible with the CP560.

Connector typeIndicates the network connector type.

Serial numberThe serial number of the SFP module.

TheModule <type> Configuration field shows the internal functional status as read back from themodule. 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 alllink related alarms settings of the module. Red indicates that the alarm has been raised.

TIM-PTrace ID Mismatch (Path)

WEB Interface 67


LOSLoss of Signal

AIS_LAlarm Indication Signal (Line)

RDI_LRemote Defect Indication (Line)

UNEQ_PPayload Label Mismatch (Path)

LOFLoss of Frame

AIS_PAlarm Indication (Path)

RDI_PRemote Defect Indication (Path)

EEDExcessive Error Defect

LOPLoss of Point

SDSignal Degrade

Refer to product specific documentation for further discussion of these parameters.

TheModule (type) Link Status field is shown if the E3/T3module is present and shows the statusof all link related alarm settings of the module. Red indicates that the alarm has been raised.

BVBipolar Violation

LCVLine Coding Violation

LOSLoss of Signal

RDIRemote Detection Indication

WLDWAN Loop Detected

EZExcessive Zeroes

68 WEB Interface


PCVP-bit Coding Violation

OOFOut of Frame

LLDLan Loop Detected

LOLLIU Out of Lock

CCVC-bit Coding Violation

AISAlarm Indication Signal

SSSystem Status.

Refer to product specific documentation for further discussion of these parameters.

TheModule (type) Error Counters field displays errors as they occur, counted during a 15 minuteperiod. Es = Errored seconds, Ses = Severely errored seconds, Cv = Coding violations, Uas = Lineunavailable seconds

CurrentThe counter increments every time an error is detected, resetting every second.

15minsDisplays 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 theClear 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 inSDH or SONET networks. This page provides access to change the configuration settings of themodule. As shown in figure Figure 8.24 the page contains four fields to set operational parameters.TheAlarms 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 CP560, only.

WEB Interface 69


Figure 8.24 The configuration pagefor the STM-1/OC-3 SFP module

In the General field the main operational parameters are set.

STM-1/OC-3 presentIndicates if the module has been detected by the CP560.

Write to moduleThis box must be checked to allow the configuration file be written to the SFP module. If thebox is not checked the configuration file may still be edited without affecting the module. Ifthe box is checked the configuration file is written to the module every time theApply buttonis clicked.

Tx clock sourceThe transmitter clockmay be internally generated, or derived from the received data stream.

Frame typeSelect SDH or SONET, respectively, according to the accessed network.

Payload FCS (Frame check sequence)Check this box to enable FCS error detection.

Disable interfaceNot available.

ScramblerTick this box to enable the module internal scrambler. Must be ticked to successfully receivescrambled network data.

70 WEB Interface


Ethernet flow controlA tick enables flow control of Ethernet data from the CP560 to the SFP module. Flow controlprevents data overflow in the SFP module buffer. Buffer overflow leads to data loss thatwould 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:

LOSLoss of signal

AISAlarm indication signal

RDI_PRemote defect indication

In theThresholds field bit error ratemeasurements indicate an estimate of the network link quality.The check boxes allow selection of pre-defined threshold BER values to raise alarms. For furtherdetails refer to the vendor SFP user manual.

SOH SDSection Overhead, degraded Signal Defect

SOH EEDSection Overhead, Excessive Error Defect

POH SDPath Overhead, degraded Signal Defect

POH EEDPath 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 theModule Alarm andModule Error Coun-ters fields of the status page are replicated here.

At the bottom of the page are three buttons:

ApplyWrites changes to the SFP configuration file. Also initiates writing the configuration file tothe module if theWrite to module box has been ticked.

RefreshCancels changes that have been entered.

Reset Factory DefaultsOnly active if the Write to module box has not been ticked. Clicking this button returns themodule 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.

WEB Interface 71


The E3/T3 Config page.

The E3T3 module provides an electrical interface for high speed data communications in E3 orT3 networks. This page provides access to change the configuration settings of the module. Asshown in figure Figure 8.25 the page contains four fields to set operational parameters. Editingthe configuration settings will alter the SFP configuration file stored in the CP560, only.

Figure 8.25 The configurationpage for the E3/T3 SFP module

E3/T3 presentIndicates if the module has been detected by the CP560.

Write to moduleThis box must be checked to allow the configuration file be written to the SFP module. If thebox is not checked the configuration file may still be edited without affecting the module. Ifthe box is checked the configuration file is written to the module every time theApply buttonis clicked.

Interface typeClick the appropriate button for the network used.

Module protocolAllows selecting the desired data link protocol for the network; HDLC (High Level Data LinkControl), GFP (Generic Frame Protocol) or cHDLC (Cisco extension to HDLC).

72 WEB Interface


Line typeLine protocol selection. Choices vary according to the interface type and data link protocolselected.

Tx clock sourceThe transmitter clockmay be internally generated, or derived from the received data stream.

Line codeMust be HDB3 for an E3 interface. Select between B3ZS and AMI for a T3 interface.

Line lengthOnly applicable for a T3 interface. Allows the output signal to be adjusted according to theline length to reach the termination point.

FEACFar end alarm and control indication. Only applicable for a T3 interface using G.751 lineprotocol.

VCAT overheadOnly applicable when using the GFP data link protocol. VCAT allows arbitrary grouping ofVCAT 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.

ScramblerOnly applicable when using the GFP data link protocol. Tick this box to enable the moduleinternal scrambler. Must be ticked to successfully receive scrambled network data.

GFP keep aliveIf 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 controlA tick enables flow control of Ethernet data from the CP560 to the SFP module. Flow controlprevents data overflow in the SFP module buffer. Buffer overflow leads to data loss thatwould 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 causeshut-down of the ethernet data flow:

LOSLoss of signal


RDIRemote defect indication

WEB Interface 73


LOFLoss of frame

FEACFar end alarm and control

Whether or not RDI, LOF and FEAC are applicable depends on Interface type, Module protocoland Line type settings.In the Loss of Signal Behaviour field check boxes allow selecting which TDM condition shall sendan LOS indication to the Ethernet interface:

LOSLoss of signal

LOCReceive loss of lock


RDIRemote defect indication

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 ErrorCounters fields of the status page are replicated here.

At the bottom of the page are three buttons:

ApplyWrites changes to the SFP configuration file. Also initiates writing the configuration file tothe module if theWrite to module box has been ticked.

RefreshCancels changes that have been entered.

Reset Factory DefaultsOnly active if the Write to module box has not been ticked. Clicking this button returns themodule 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.

8.4.5.2 IP Routing

The IP Routing table lets the user configure IP routing rules for the unit. These rules tell the unitwhich interface to send IP traffic to, based on the destination IP address of the traffic.

DestinationThe destination IP address to use for matching against this routing rule.

74 WEB Interface


Figure 8.26 IP Routing

NetmaskThe subnet mask to use for matching against this routing rule.

GatewayThe IP destination to send a packet to if the destination address of the packet is on a differentsubnet than the destination interface.

InterfaceIP packets matching this rule will be sent through this interface.

MetricThe metric of the routing rule. If more than one rule matches a destination address the rulewith the lowest metric will be used.

When an IP packet is sent from the unit the destination address of the packet is matched againstthe configured routing rules. If the destination address matches one or more rules the rule withthe lowest metric will be used. The packet will then be forwarded to the interface determinedby this rule. If the destination address is on a different subnet than the configured interface thepacket 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 TCPpackets that are not addressed to the unit will be forwarded to an interface according to the routingrules. The receiving interface must have management traffic enabled to forward TCP traffic to adifferent interface.

Note: Modifying the IP routing rules may cause loss of contact with theunit. Make sure you will still be able to contact the unit with the newsettings before applying the changes.

8.4.5.3 TXP Settings

TXP is a Nevion proprietary HTTP/XML based protocol designed to retrieve configuration andstatus information using WEB/HTTP requests. TXP exists side by side with an SNMP agent andprovides an alternative way to access data in a product. TXP and SNMP therefore complementeach other.

WEB Interface 75


Figure 8.27 TXP Settings

This page contains settings to determine how the unit should respond to TXP queries.

ModeControls the mode of the TXP server. If set to Disabled, all TXP accesses are disabled.

Anonymous readSelects whether read accesses should be allowedwithout entering user credentials. This mayonly be edited ifMode is different from Disabled.

Require HTTP POST for txp_setRecommended to reduce risk of unwanted configuration changes.

Required level for readThe required user level for TXP read accesses. This may only be edited if Mode is differentfrom Disabled and Anonymous read is not selected.

Required level for writeThe required user level for TXP write accesses. This may only be edited if Mode is set toWrite.

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>

8.4.5.4 SNMP Settings

The Simple Network Management Protocol (SNMP) is used to monitor network-attached devicesfor conditions that warrant administrative attention. This page gives access to SNMP settings suchas destination IP addresses of trap receivers and community string. It Also displays a log of thelatest traps sent by the unit.

76 WEB Interface


Figure 8.28 SNMP Settings

TheTrap Destination table lets the user configure the trap servers that should receive SNMP trapsfrom the unit. To add a server click the Add new button, enter an IP address, then click the Applybutton. 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 totransmit SNMPv2 traps, two additional options are applicable.

Status change trapsSelecting this causes a trap to be transmitted each time the overall device status changes.

Alarm event forwardingConfigures which alarms to forward as SNMP traps. The drop-down list has the followingoptions:

DisabledNo traps are transmitted when alarms appear or disappear. If the Status change trapscheck box is checked, device status traps are still transmitted.

BasicThe device forwards alarm events as SNMP traps. If there are several sub-entries onlya single trap is transmitted.

DetailedThe device forwards alarm events as SNMP traps. If there are several sub-entries, anSNMP 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 9.4 inChapter 9: SNMP.

WEB Interface 77


8.4.5.5 Tools

The tools menu contains helpfull tools for network debugging.

8.4.5.5.1 Ping

The ping tool can be used to check for connectivity between devices. It is especially useful to pingthe receiving data port from the IP transmitter to see if the receiver can be reached.

Figure 8.29 The Ping tool

IP destinationThe IP address of the receiving data port. The ping messages will be routed to the matchingEthernet port, either data or management, or to the port configured as default managementinterface if the specified IP address does not match either of the two sub-nets. Note that ifyou are pinging between data interfaces, theAllow ping response option on the network pageAdvanced tab (see Section 8.4.5.1.3) must be enabled both in the transmitter and the receiver.

Note: When the IP destination is a multicast address one cannot expect toreceive a response to a ping request. It is recommended to test connectivityusing 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 theIP protocol header that is decremented once for each router that the datagram passes. Whenthe count reaches 0, the datagram is discarded. You can use this to check the number ofrouters between the transmitter and the receiver by starting with a low value and incrementit until ping responses are received. TTL is also specified for each data channel on the IPtransmitter, and must be high enough to reach the receiver. Values range from 1 to 255.

Ping countThe number of ping messages to send. The messages are transmitted with an interval ofabout 1 second.

MTUMaximum Transfer Unit. Specify a length for the ICMP frames to check that frames withgiven length pass through the network. The ICMP data payload size is adjusted to yieldEthernet frameswith the specified length. The pingmessages are transmittedwith the “don’tfragment” bit set.

78 WEB Interface


StartPress this button to start the pinging sequence configured above. The status of the pingsequence 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 againto cancel the pinging sequence.

OK responsesThe number of ping responses received.

TimeoutsThe number of ping requests that were not answered. If the timeout counter is incrementingwhile the OK responses counter is zero, there is no contact with the specified IP address.

Last roundtripThe round trip time measured for the last ping request in units of milliseconds.

Average roundtripThe average round trip timemeasured for the ping requests in this session. The value is resetevery time the start button is pressed.

Min roundtripThe shortest round trip time registered for the ping requests in this session.

Max roundtripThe longest round trip time measured for the ping requests in this session.

RemainingThe number of remaining ping requests in this session.

8.4.5.5.2 Traceroute

The traceroute tool can be used to debug the network connectivitywith a given host by tracking therouter hops between the CP560 and the host. Traceroute uses ICMPpingmessageswith increasingTTL to track the router hops.

Settings

IP DestinationThe IP address of the host to check. IP routing decides which interface the ICMP mes-sages are sent on.

Number of hopsThis parameter sets a roof to the number of hops that are tracked. Normally this para-meter can be set fairly low.

MTUMaximum Transfer Unit. This parameter can be used to transmit messages with a givenlength. ICMP messages are transmitted with the don’t fragment bit set to yield errorswhen MTU of a link is too small for the frame.

Status

WEB Interface 79


Figure 8.30 The Traceroute tool

RunningState of tracer.

Current TTLIncreasing for each new hop traced.

TraceGrid showing routers encountered.

HopHop number.

RTT[ms]Round trip time measured in milliseconds for message returned from router at thispoint in chain.

IP AddressIP address of router at this point.

HostnameDNS resolved host name for IP Address. For this column to be filled in, DNS mustbe supported and a DNS server must have been defined either manually or by DHCPclient.

80 WEB Interface


8.4.6 Clock Regulator

This page lets the user configure synchronisation of the internal 27 MHz clock from an externalsource.

8.4.6.1 Main

Figure 8.31 Clock regulator

The reference signal is supplied on a separate connector. This page gives access to selecting howthe reference is used.

The Configuration field:

27 MHz lock mode

DisabledThe internal clock will not make use of an external reference signal.

Lock to external 1 PPSConfigures the internal clock to use the external 1 PPS input connector as reference.

The Clock Regulator Status field:

Regulator state

IdleExternal reference signal is disabled.

WaitingExternal Reference signal is enabled, but the internal clock has not obtained lock to thereference

Fine tuneExternal Reference signal is enabled, and the internal clock has obtained lock to thereference.

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

Current freq. offsetFrequency offset between the internal clock and 1 PPS clock reference.

WEB Interface 81


Current driftCompensated frequency offset between external and internal reference.

8.4.6.2 Alarms

Figure 8.32 Clock regulator Alarms

These are the Clock regulator specific alarms. Clicking an alarm opens the field to configure thealarm. Please see Section 8.4.2 for alarm configuration details.

8.4.7 Configuration Manager

The Configuration Manager, shown Figure 8.33 provides an interface for managing the deviceconfiguration as “snapshots”. From here, snapshots of the device configuration settings can betaken and stored locally, or exported from the device as XML files. Also, configuration files maybe 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.

8.4.7.1 Save/Load Configs

8.4.7.1.1 Save Configuration To File

This is the interface for exporting the current running configuration as an XML file. Clicking theSave Config button prompts the user with a standard Save as dialogue requesting a location tostore the configuration file. This location can be any place the user has access permissions to writefiles.During the transfer of the file from the device to the user’s system the user has the ability to click theCancel button to cancel the transfer. Note that, depending on theweb browser used, an incompletefile 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 duringthe 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 canbe restored to the device at a later time. Or it may be installed on another device using the LoadConfiguration option.

82 WEB Interface


Figure 8.33 Configuration manager

8.4.7.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 snapshotare loaded and verified before making them active, thereby minimizing the risk of errors in thefile that would render the device in a non-operational state.

Clicking the button marked Browse prompts the administrator with a standard system File Opendialogue allowing the administrator to select the file of his choice to import. Once selected, clickingLoad Config performs the following actions :

• Transfers the configuration snapshot from the administrator’s PC to the device.

• Validates the configuration tomake sure that all the options in the file are compatiblewitheach 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 changesits text to OK. Upon failure at any point the progress bar will turn red, and details of the reasonfor 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 networkconfiguration, are disregarded during the import process. This is a convenience feature allowingconfigurations to be easily moved from one device to another. It also makes management easier in

WEB Interface 83


that the Web UI will continue to communicate with the device after a new configuration has beenloaded. The default behavior can be changed with the load options, please see Section 8.4.7.1.4for a description of the options.

Partial configuration files are supported to allow a subset of configuration options to be changedinstead of the entire unit configuration. Partial configuration files are validated as differences fromthe current running configuration upon import before being made active.

8.4.7.1.3 Load Configuration from Remote Device

The Load Configuration from Remote Device makes it easy to copy the configuration of anotherdevice to this device. This device will therefore be a clone of the remote device, except for devicespecific parameters such as IP addresses and product name. Loading a configuration fromRemoteDevice is essentially equal to saving the configuration file of another device, and uploading it tothis device.

The configuration field includes the IP address of the remote device. Entering an IP address andpressing theContact Device buttonwill 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 becomeclickable.

Note: It is possible, but not advisable, to load configuration from othermodel 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 8.4.8.1 for a list of features.

Please see next chapter (Section 8.4.7.1.4) for a description of the load options.

8.4.7.1.4 Load options

These options are used tomodify the behavior on configuration loading. The options are availablewhen loading from a file (Section 8.4.7.1.2) and when loading from a remove device (Section8.4.7.1.3) .

Default actionThis parameter modifies the algorithm used when modifying lists (collections) in the config-uration.

RestoreModify list to contain exactly the entries specified in the file loaded.

MergeList entries that are present in the running configuration but not in the file loaded are leftin the list. New entries specified in the file loaded but not in the current configurationare added. Entries present both in file loaded and in running config are modified.

UpdateOnly update nodes that are present in running configuration and in file loaded, i.e nolist entries are added or removed.

84 WEB Interface


OverwriteThis parameter is used to modify how specially tagged parameters are handled during fileloading.

Access control parametersTick to overwrite SNMP community strings and TXP access parameters.

Device identifier parametersTick off his check box to overwrite the device identifiers device name and inventory ID.Ethernet Interface IP addresses are not overwritten using this option.

8.4.7.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. Thispage may then be inspected to find the reason for rejection.

8.4.7.3 Stored Configurations

This tab provides an interface to management of on-device stored configuration snapshots. Up to8 full system configuration snapshots can be stored.

Figure 8.34 Locally stored configuration files

The table lists the currently stored snapshots, and columns in the table provide information specificto each snapshot as follows:

IdEach entry in the table has an id in the range from 0 to 7.

WEB Interface 85


ValidIndicates 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 invalidconfiguration is indicated by a red indicator. A silver indicator in this column signifies thatthe slot is empty and available.

DescriptionA 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 savedTime stamp when the configuration was uploaded to the unit.

File sizeSize of the configuration file.

StateExtra information regarding the configuration.

To the right of the table several buttons are provided to perform the following actions:

ActivateLoads the selected snapshot as the active configuration of the device. The administrator willbe prompted to verify the decision as this action will overwrite any unsaved changes on thedevice.

SnapshotStores the current running configuration as a snapshot in the slot selected in the snapshottable. This operation will overwrite the configuration file currently stored in that position.

UploadImports a configuration file from disk to the selected slot. This operation will overwrite theconfiguration file currently stored in that position.

DownloadDownloads the selected configuration file to disk.

DeleteDelete 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 anda list of errors (if any) of the last action performed.

8.4.7.4 Emergency Switch

This feature allows the CP560 to communicate with a central emergency switch unit. The emer-gency switch unit is designed to facilitate simultaneous configuration switching of all units underits supervision. In this way the operational mode of a comprehensive system may be changed atthe press of a single button. Contact Nevion for further information on the emergency switch unit.Communicationwith the emergency switch is IP based using theUDPprotocol. Each unit enabledfor emergency switch control polls the emergency switch repetitively to determine the switch po-sition. The Emergency Switch tab provides the means to configure the behaviour of the CP560under emergency switch control.

86 WEB Interface


Figure 8.35 Emergency switch

The table lists the rules that have been set up for the emergency switch. Several rules may beconfigured, albeit only one should be enabled at any one time.

RuleThe list position.

Status

• Green if the rule is enabled and connection to the switch unit is ok.

• Red if the rule is enabled and the connection to the switch is down.

• Grey if the rule is not enabled.

IpThe IP address of the Emergency Switch unit.

ActiveThe ID of the configuration that shall be applied when the switch is in the active state.

InactiveThe ID of the configuration that shall be applied when the switch is in the inactive state.

To the right of the table, buttons are provided to set up the switching rule(s):

Add RuleOpens the configuration pane to configure a new switching rule, see Figure 8.36.

Edit RuleOpens the configuration pane for the selected switching rule. See Figure 8.36.

Delete RuleDeletes the selected switching rule.

RefreshRefreshes the list display.

Configure Emergency Switch rule

WEB Interface 87


Figure 8.36 Configuring the emergency switch

TheMain settings field has the following parameters:

EnabledA tick in the box enables this rule.

DescriptionUser defined description of the rule.

IpThe IP address of the emergency switch unit.

Active configurationThe ID of the configuration that shall be applied when the emergency switch is active. ThisID must be the ID of a valid configuration from the Stored Configurations list.

Inactive configurationThe ID of the configuration that shall be applied when the emergency switch is inactive. ThisID must be the ID of a valid configuration from the Stored Configurations list.

The Advanced settings field has the following parameters

Digital inputFor future use.

Digital outputFor future use.

Refresh intervalThe time between each poll of the emergency switch state.

TimeoutMaximum time to wait for a return message from the emergency switch unit.

Connection hysteresisNumber of timouts allowed before the connection to the emergency switch unit is consideredbroken.

88 WEB Interface


FallbackIf this box is ticked the Inactive configuration is applied if the connection with the emer-gency switch is broken. Othewise the currently applied configuration will remain when theconnection is broken.

Block userIf this box is ticked no user may change the configuration of this unit if the emergency switchis in the active state.

At the bottom of the pane theApply button is used to confirm and apply changes made; theCancelbutton is used to discard changes and close the pane.

8.4.8 Maintenance

TheMaintenance page centralises information regarding the hardware configuration of the deviceand provides a means for updating firmware images and managing software feature licences.

The page gives access to three sub-pages described below.

8.4.8.1 General

Figure 8.37 Maintenance

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:

WEB Interface 89


Reset UnitProvides an interface to perform a restart operation on the unit. Following a restart bootdelay the user is prompted to reload the Web UI in the browser.

Restore Factory DefaultsResets all non-device specific settings to the factory default settings. Settings remaining un-changed include the device name and the management interface IP configuration.

Generate System ReportGenerates an status report of the unit in XML format. Please attach this system report whencontacting Nevion Customer Support.

The Product info field provides the following information:

Product nameThis is the product model name.

Software versionThe version of the firmware image installed in the unit.

Serial numberThe manufacturer assigned serial number used for warranty and software licensing.

Installed boardsThe name and serial numbers of the circuit boards installed in each of the internal interfaceslots of the unit.

FeaturesA list of features relevant to the device and their state (e.g. true, false or the number of portssupported).

NameName of the feature

ValueState of the feature or number of licenced items

CodeThe factory order code used to identify this feature

HotWhether the licence can be upgraded without rebooting the device or not. If the fieldreads ’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 8.38 TSConfiguration Mode

90 WEB Interface


The choices are:

DVBDVB transport streams only are accepted.

ATSC+DVBBoth 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, theOperational Modes frame is visible and providesthe option Electrical/SFP as shown in figure 8.39. This option is used to allocate the Data-2 IPinput to operate through the Electrical Ethernet data interface, or through the SFP slot.

Figure 8.39 SFP and Electrical Ether-net select

When switching mode the unit will automatically reboot. The device configuration is kept butreferences to Data-2will be invalid.

8.4.8.2 Software Upgrade

Figure 8.40 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:

BrowsePrompts the administrator with a standard system Open file dialogue to specify the newsoftware image file to install.

UploadOnce an image file is specified by using the Browse button, the Upload button is used to

WEB Interface 91


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 thenew 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 inthe Status field.

CancelThe Cancel button is enabled during the upload process and can be clicked to cancel theoperation. It is not possible to continue a cancelled upload.

Reboot on successThis checkbox is checked by default but can be unchecked to disable automatic reboot uponSW loading completion. If this option is not checked the SWwill load butwill not be activatedbefore the user performs a manual reboot. Note that this option is not stored on the device,and Reboot on successwill 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 theIP address of the machine fromwhich the loading was initiated. The alarm is turned off when theloading 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 nextmanual reboot.

After uploading, if the Progress bar showsOKbut theweb interface does not change to theWaitingfor reset state, allow some time for the device to reset itself and then reload the web UI via theweb browser reload button.

Note: It is recommended to verify the new software version via the “Prod-uct Info” page (Section 8.4.1) to verify that the update was successfuland the latest software revision is active.

8.4.8.3 Feature Upgrade

The Feature Upgrade sub-page provides an interface to upload new software licences to upgradethe feature set of the device. The licence key is provided as a text file. Paste the content of file intothe 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” inthe feature list. If you load a licence changing only hot-upgradable keys, you will get a messageback 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 Section8.4.8.1.

92 WEB Interface


Figure 8.41 Feature Upgrade page

Figure 8.42 Users page

Note: The entire content of the licence key text file must be copied intothe text box, not just a portion of the file.

8.4.9 Users

TheUsers page provides a configuration interface for user management. Settings are provided forconfiguring a password for each privilege level and for configuring automatic login settings. Youmust have administrator previledges to alter the settings.

WEB Interface 93


Auto loginSpecifies 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 8.2) encountered by default.

UsersEach user privilege level has an account name and password. The account name is fixed foreach level and therefore cannot be changed. Each privilege level, however, has an adminis-trator definable password.

Tomodify the password for a given privilege level select the user name from the list and clickthe Set password button. The administrator is then prompted with a dialogue requesting anew password.

Three user privilege levels are available.

guestCan view configuration information and alarm logs

operatorCan configure the settings on the device, but can not alter passwords

adminDevice administrator, full access to the device.

On the bottom of the page you can see all active GUI session. Note that this does not includeSNMP or TXP accesses. The table includes information about the peer IP address, access level andduration of the current sessions.

8.4.10 GUI Preferences

Figure 8.43 GUI Preferences page

The GUI Preferences page contains settings that affect the web interface.

Enable confirmation on ApplyConfigures the web UI to prompt users for confirmation before committing changes to the

94 WEB Interface


device configuration. When disabled the Web UI will only prompt for confirmation prior toperforming severe operations such as device reset.

Enable GUI scalingIf 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 ordisabling this option the web interface may hang for some seconds as it changes the fontused.

GUI scale levelThe current scale level for the GUI. This is ignored if GUI scaling is not enabled. A value of0 means normal size.

Return to current status page on refreshCheck this to return to status page once refreshing the GUI WEB page. If not checked, youwill return to the last visited sub-page when reloading the page.

Enable sound on critical alarmThis option makes the computer play an alarm sound continuously if browser is connectedto unit while it has a critical alarm. Use with care.

Note: Every browser session will play sound independently of each otherif you enable this on multiple devices and/or have multiple open browsers.

Note: ’Enable confirmation on Apply’ is stored on the device, while theother options are stored as browser cookies and thereby only affect thelocal browser and PC.

8.5 InputsThe 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 toview a summary of all the inputs to the device. In addition the list also includes the input switchersand their corresponding inputs, if configured.

The labelling of the inputs is a combination of the user defined name of the input and the physicalnumber of the input port.

8.5.1 Inputs Overview

The Inputs Overview page shows a short table summary of all the inputs of the device. The tablehas the following columns:

EnableThis shows whether the input is enabled or not. An input is enabled or disabled by clickingthe check box and hitting Apply.

WEB Interface 95


Figure 8.44 Inputs Overview

InputThe name of the input, consisting of the factory defined label with the physical port numberand the user defined name.

SyncDisplays “yes” if the unit has synchronised to this transport stream input.

Total BitrateThe total bitrate in Mbit/s of the transport stream currently received on the input.

Effective BitrateThe effective bitrate in Mbit/s (excluding null packets) of the transport stream currently re-ceived on the input.

Alarm StatusThe current alarm status of the input is shown as a coloured indicator, the colour indicatingthe 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 rateThe combined total bitrates of all the transport streams of all the input ports.

Total effective input rateThe combined effective bitrates (total, minus null packets) of all the transport streams of allthe input ports.

The Reset Stats button at the bottom of the page gives access to a dialog box that allows reset ofchannel statistics. Figure 8.45 shows the dialog box. Select the statistics items you want to resetand then press Apply.

96 WEB Interface


Figure 8.45 Resetstatistics dialog box

8.5.1.1 IP Inputs

If the unit has the “Ethernet data interface” feature enabled the IP Inputs tab is shown on theInputs Overview page.

Figure 8.46 Inputs Overview - 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:

EnableThis showswhether the IP input is enabled or not. An input is enabled or disabled by clickingthe check box and hitting Apply.

IP InputThe 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, themulticast address is displayed.

WEB Interface 97


InterfaceThe interface that this IP input is configured to receive data through.

Last IP SourceThe IP address that this IP input last received data from. If the input has never received anydata the IP address is shown as 0.0.0.0.

PortThe UDP port this IP input is configured to receive data on.

Multicast AddressIf the IP input is configured to receive data through amulticast themulticast address is shownhere.

Ethernet BitrateThe 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. RTPsequence error measurements requires the RTP protocol is present in the received stream.

StatusThe current alarm status of the input is shown as a coloured indicator; the colour indicatingthe highest severity level of the active alarms. If the port is disabled the indicator is grey.

Below the table four values are shown. The first one is the total Ethernet bitrate received. The lastthree are identical to the three values for ASI inputs described in the previous section.TheAdd IP andRemove 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 parameterscan be edited. A new channel is shown with a plus sign in the navigator until it has been edited(and the edit applied).

8.5.1.2 Switch Inputs

If the unit is equipped with the Input switching feature, the Switch Inputs tab is shown on theInputs Overview page. The page lists the defined input switches and offers controls to add andremove switch inputs.Columns in the grid are:

EnableThis shows whether the switch input is enabled or not. An input is enabled or disabled byclicking the check box and hitting Apply.

Input SwitchThe name of the switch input, consisting of the factory defined label with the logical portnumber and the user defined name. The port numbers for switch inputs start at 64.

Switch StatusStatus text from the switch state machine. In the normal state, this shows active state and thetime the switch has been in this state.

98 WEB Interface


Figure 8.47 Inputs Overview - Switch Inputs

Selected InputShows the currently selected physical port

StatusShows alarm status on the switch input. This is not the same as the status on the currentlyselected physical port.

To add a switch press the Add Input Switch button and press Apply to commit. When a switch isadded, it appears in the left hand side navigator with an adjacent pluss sign. Selecting the switchwill take you to the configuration page for the switch.Removing a switch is accomplished by selecting the switch to remove in the datagrid and pressthe Remove Input Switch button.The Reset Stats button is used to clear statistics counters for the switches.

8.5.2 Input

When a specific input is selected, a page with information about that input is displayed. Theheader of the page shows the name and the current alarm status of the input and a list of tabs thatis dependant on what sort of input is selcted (ASI, IP,...) and what options are selected.

Figure 8.48 Input header

WEB Interface 99


Holding the mouse cursor over the alarm status indicator brings up a tool tip displaying up to 30of the current alarms (if any) on this particular input.

Beneath the name of the input is a tab navigator containing different sub pages with informationabout the selected input. The choices are:

MainThis page shows a summary of the transport stream currently received on the input, includ-ing a summary of the running PIDs and services.

AlarmsThis page lets the user view the status of all alarms on the input, and override the severity ofthese alarms.

IPThis tab is present only if the input selected in the navigator is an IP input. It gives access tothe IP specific features of the input.

ServicesThis page gives detailed information about the services that are currently running and thecomponents of those services.

PIDsThis page gives detailed information about the currently present PIDs.

TablesThis page showswhich tables are present on the input and allows selecting tables that shouldbe analysed by the unit.

In all sub-pages, for a selected input, the list of the current alarms for that input is shown at thebottom of the page. The list is identical to the list displayed in the Current Status view, describedin Section 8.3.1.

8.5.2.1 Main

The Main page is divided into three sections, the first one being the Transport Stream Detailsfield. This field contains information and some configuration parameters concerning the transportstream:

Enable inputThis shows whether the input is currently enabled. The input is enabled or disabled by click-ing the check box and then Apply.

Input labelThis is the user defined name of the input port, which can be changed by typing a new labeland hitting Apply. It is only used in the WEB GUI to identify the port.

TS idThe transport id of the transport stream currently received on the input. The value of thisdepends on PAT being present and decoded on the input.

100 WEB Interface


Figure 8.49 Main

Orig. Network idThe Original network id of the transport stream currently received on the input. The valueof this parameter depends on the SDT actual being present and decoded on the input.

Sync detectedShows whether the input transport stream has been synchronised.

Bitrate limitThe maximum bitrate to accept on this input. If the ASI input stream exceeds this bitrate,data will be discarded from this port and an input overflow alarm will be raised.

Total BitrateThe total bitrate of the transport stream currently received on the input in Mbit/s.

Effective BitrateThe effective bitrate (excluding null packets) of the transport stream currently received onthe input in Mbit/s.

Maximum burst rateThe maximum burst bitrate measured by the bitrate limiter. This value is based on 188 byteTS packet length.

Packet lengthThe length of the transport stream packets in bytes.

Beneath the Transport Stream Details section is the PIDs present section. This shows all thePIDs that are present on the selected input. The number in parentheses is the total number ofPIDs present. A PCR PID is represented by a number shown in italics. A coloured PID numberprovides additional PID status information:

WEB Interface 101


RedA continuity counter (CC) error alarm is raised.

BlueStream is scrambled. The shade of blue represents whether the scrambling mode is odd oreven.

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 theservices that are currently present on the selected input. The list depends on PAT and PMT beingpresent and successfully decoded on the input. The service name depends on SDT actual beingpresent and decoded. The number in parentheses is the total number of services present.The list has three columns:

Service IDThe program number/service id of the service

Service NameThe name of the service as conveyed by the SDT Actual table. If there is no SDT Actual tableor 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 SDTtable is analysed, the type of service. A list of active alarms (if any) on the service is displayedby 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 BitrateThe 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 athand being expanded.

8.5.2.2 Alarms

The Alarms page lets the user configure and view the status of all alarms belonging to the selectedinput.In figure 8.50 the Alarm Config page is shown. Note that the alarms are organised hierarchicallyand that only the branches in focus need to be expanded.The following configuration options are available:

ShowThe radio buttons Error count and Configured severity allows the user to configure what tobe shown in the input alarm tree (see figure 8.51).

Error countDisplay the accumulated number of errors since last alarm counter reset.

102 WEB Interface


Figure 8.50 Input alarm configuration

Configured severityDisplay the configured alarm severity.

Reset Alarm CountersReset the alarm counters for all alarms belonging to the selected input.

Copy Settings from InputThis is a convenient way to copy alarm settings for a specific input to the current input. Usethe Input drop-down list to choose from which input to copy the settings. The settings arecopied by hitting theCopy Settings button. This includes all severity and limit overrides bothon alarm level and on PID level.

The input alarm tree is found in themain part of the page. It consists of a tree displaying all alarms.

The input alarm tree is shown in figure 8.51. By clicking on the alarm nodes in the tree the detailsfor the selected alarm is shown in the Alarm details section (figure 8.52).

The alarm tree has two types of nodes:

FolderCorresponds to a group of alarms. The colour of the folder shows the highest severity of allthe alarms belonging to the group. The group is expanded or collapsed by clicking on thearrow next to the group.

The alarm counters for a specific group are reset by left-clicking an alarm group in the alarmtree and choosing theReset Counters option. The counters for the individual alarms are resetusing the same procedure for an alarm node.

WEB Interface 103


Figure 8.51 Input alarm tree

Alarm nodeThese have a coloured indicator showing the alarms current status. In addition, the alarmsconfigured 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 8.52). Theframe appears when a particular alarm is clicked. Its content may vary according to the alarmselected.

Figure 8.52 Alarm details

The alarm details section includes the following information and buttons.

Alarm IDThe internal ID of the selected alarm. A complete list of alarms is found in Table G.3.

AlarmName of the alarm.

104 WEB Interface


DescriptionA short description of the alarm.

SeverityOverrides the default severity for the given alarm. The default severity is in brackets to theright 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 determinesthe maximum time (milliseconds) allowed between two occurrences of the same table. Thedefault 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 abovewhich an alarm is raised. The default value is shownto the right.

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 belowwhich an alarm is raised. The default value is shownto the right.

Alarm turned onNumber of times the alarm has triggered. If the alarm is filtered this counter will not in-crease.

Error countFor alarms that are checked continuously, this counter shows the number of times an alarmcondition has been violated. This counter will increase even if the alarm is filtered.

Global settingThis field shows the value configured for this alarm in the global settings. If the alarm severitylevel 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 countersThis button lets the user reset the "Alarm turned on" and "Error count" counters for thisalarm.

"PID" and "Service"alarms (Figure 8.53) allow overriding of sub items. For such alarms two tablesare shown below the alarm details.

The Service/PID with active alarms table shows all currently active alarms on sub-items for theselected alarm. The following columns are found in the table.

Service/PIDThe id of the sub-item.

WEB Interface 105


Figure 8.53 Alarm severity per sub-ID (typically Service or PID)

SeverityThe current severity of the item.

OverriddenIndicates whether the sub item has been overridden.

If no override already exists an override can be added by right-clicking an item. An item alreadyoverridden can be edited or removed.

TheOverridden PIDs/Services section shows currently overridden sub items. The following columnsare found in the table:

Service/PIDThe id of the Sub item.

New severityThe new severity, i.e. the severity after the sub item has been overridden.

New limitIf the alarm has a configurable limit, also the limit of the sub item can be overridden and thatnew limit will also be shown.

An override can be edited or removed by right-clicking on the entry in the list. Alternativelythis can be done by hitting the Edit and Remove button, respectively. An override can alsobe added hitting the Add button and manually entering the ID and overridden values.

106 WEB Interface


8.5.2.3 IP

This tab is only visible if an IP input is selected.

8.5.2.3.1 IP Configuration

The tab contains three sub pages: IP Configuration, Ping and Regulator.

Figure 8.54 IP Configuration

This page allows configuration of the IP parameters for the IP input and shows detailed IP statusinformation for the input.

The IP RX Parameters field:

EnableThis shows whether the input is currently enabled. The input is enabled or disabled by click-ing the check box and then apply.

Receive portThe UDP port on which this input will listen for data.

Presumed jitterThe maximum amount of jitter you expect on the ip link. This value controls the amount ofbuffering that will be applied.

Join multicastIf this box is checked the input will join the multicast configured in the following IP field. Ifthe box is not checked the input will listen for unicast traffic.

Multicast group addrThis parameter is only used if the “Joinmulticast” box is checked. This is themulticast groupthe input will join.

Multicast source addrThis parameter will only be used if the input is set to join a multicast and the unit is currently

WEB Interface 107


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 interfaceThe 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 ofthe input stream. “No”, when the unit has not been able to receive the input stream correctly.

Last IP sourceThe source IP address of the last IP stream received by this input. If the input has neverreceived an IP stream this value is set to 0.0.0.0.

Total rateThe total IP rate received on this input.

LatencyThis parameter reflects the network jitter the unit can handle at the moment.

Min/Max latencyThis shows the minimum andmaximum latency measured since the statistics was last reset.

ProtocolIndicates RTP if the received data contains an RTP header, UDP otherwise.

TS packets per frameThe number of transport stream packets per IP frame and the size of the transport streampackets in the incoming stream.

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

RTP max jumpThe max jump in RTP sequence number between two consecutive packets received.

Duplicated IP framesThe number of received IP frames with RTP sequence numbers which have already beenreceived.

Lost IP framesA counter showing the number of IP frames that have been lost, i.e. lost and not corrected bythe unit.

Corrected IP framesA counter showing the number of IP frames corrected by the FEC engine.

108 WEB Interface


Max burst lossThe maximum number of consecutive packets lost.

Number of resyncsThe 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 andthe buffer runs empty. The reason for re-syncs is tagged in the alarm details for the No Lockalarm.

8.5.2.3.2 FEC

The FEC sub page is shown in Figure 8.55. This page displays the status of the forward errorcorrection processing of the IP input.

Figure 8.55 Input FEC configuration

The Configuration field provides a single check box to enable or disable input FEC processing. Ifthis 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 framesThe number of IP frames lost. I.e. FEC processing has not been able to recover these frames.

Corrected IP framesThe number of IP frames that were successfully regenerated by the FEC processing.

Duplicated IP framesThe number of IP frames that have been regeneratedwhile also being received correctly. This

WEB Interface 109


occurs if the IP frame is received out-of-order with sufficiently long delay (thus regarded aslost by the FEC processor).

Max Burst Loss LengthThe 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 delayThe maximum delay of out-of-order IP frames (datagrams).

Latency requiredThe latency required by the input FEC processor to handle the incoming FEC matrix.

TheColumn Stream Status andRow Stream Statusfields show the status of the IP stream carryingthe column and row FEC IP datagrams, respectively:

UDP portThe UDP ports receiving the column/row FEC data.

BitrateThe bitrates of the Column and row FEC data.

RTP sequence errorsShows the number of disruption in the sequence count of the RTP protocol.

For further details of FEC properties and usage, see Appendix C.

8.5.2.3.3 Ping

The Ping sub page is shown in figure 8.56.

Figure 8.56 Ping page

Timeouts in MAC address lookup tables can sometimes cause problems when routing one-waytraffic. The Ping feature is designed to solve this by transmitting a ping message generating two-way traffic.The Settings field:

Enable Unicast Peer PingCheck this box to enable Unicast Peer Ping. This enables regular pinging of the transmittingdevice.

110 WEB Interface


IntervalSet the interval in seconds between each Ping.

MTUSets the Ethernet frame size to use on ICMP messages transmitted.

The Status field displays the status of the on-going pinging session:

IP destinationThe address of the device receiving the Ping requests.

Time to liveThis figure indicates the number of routing points the Ping message may encounter before itis discarded.

OK responsesIndicates how many valid Ping responses have been received.

TimeoutsIndicates howmany of the sent Pingmessages timed out, i.e. did not provide a valid responsewithin the allowed time.

Last roundtripThe time taken from last sending the Ping message until the response is received.

Min roundtripThe minimum time taken from sending a Ping message until the response is received.

Max roundtripThe maximum time taken from sending a Ping message until the response is received.

8.5.2.3.4 Regulator

The Regulator sub page is shown if figure 8.57.

Figure 8.57 Regulator page

In the Regulator Settings field it is possible to adjust the settings of an IP input buffer regulator.

WEB Interface 111


Pref. Init. Rate ModeFrom the pull-down list select the preferred algorithm to find the initial bitrate of a receiveddata stream.

PCRThe default mode is PCR, in which case a number of consecutive TS packets of the firstPCR PID encountered are used to calculate the bitrate. If no PCR PID is found simplebitrate measurement over a couple of seconds is used.

MIPThis mode may be used for a signal that does not contain any PCR PIDs, but does havea DVB MIP PID (PID 21) as used in Single Frequency Networks. In MIP mode, twoconsecutive MIP packets are used to estimate the bitrate. The input signal must be avalid DVB-T feed in the sense that the MIP is valid, for this mode to work.

VBRIn this mode the unit attempts to read data from the input buffer at the rate entered inthe Max VBR bitrate input. If the incoming rate is higher than this a buffer overflowalarm will be triggered.

FAST COARSEIn 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 thespecification and should only be used when having IP -> IP transmission.

Expected PCR accuracyThe expected clock accuracy of the PCR in the input signal. The configured value affects howfar off the initial bitrate (determined from the incoming PCR) the buffer regulator may adjustthe output bitrate to compensate for input latency. The default value (25ppm) should besufficient to handle signals from professional DVB equipment at the same time guaranteeingthat the output bitrate does not deviate beyond 25ppm. If youwant to synchronise to streamscoming from sources with less accurate clocks, you may have to configure a wider operationrange to allow the output clock to be tuned further off to avoid buffer over-/underflow.“

Max VBR bitrateIf VBR rate mode is chosen this parameter tells the unit the bitrate to use when reading fromthe input buffer.

The Re-sync Conditions field:

Bitrate changeChecking this boxwillmake the unit re-synchronise faster in the case of small bitrate changes.PCR based bitrate measurements deviating 100ppm or more from the initially determinedbitrate causes immediate buffer re-synchronisation.

Latency limits (rel. to pref.)Checking this box will make the unit re-synchronise if the measured latency exceeds theconfigured limits set in the configured preferred latency.

The Regulator Status field allows inspecting the status of the buffer regulator.

112 WEB Interface


Regulator stateThis parameter shows the current state of the buffer regulator. The possible states areStopped,Rate Estimation, Coarse and Finetune. When data is received and an initial bitrate estimateis found the regulator enters the Rate Estimation state, where the signal is analysed to checkif a better estimate of the bitrate can be found. When a better estimate is found the regulatorswitches to Coarse mode where the output bitrate is coarsely moved closer to the new rate.From Coarsemode the regulator enters Finetunemode.

Initial bitrateHere the exact initial bitrate found is displayed.

Current bitrateThis parameter shows the exact bitrate played out on the ASI port at the moment.

Measured bitrateThis parameter is an input to the regulator in the Rate Estimation and Coarse phases, andshows the bitrate measured for the data stream since last re-sync. In the first minutes aftera re-sync this measurement depends on IP network jitter and is highly inaccurate. After afewminutes of operation the value gets more and more accurate and can be compared to thecurrent bitrate to see how far off the target bitrate the regulator is operating.

Regulator outputIndicates the amount of correction the regulatormust apply to the output bitrate, with respectto the initially measured input bit rate, in order to avoid buffer under-/overflow.

Regulator operation rangeIndicates the maximum clock correction (in ppm) that may be applied. This parameter isaffected by the “Expected PCRaccuracy” parameter and is typically configured slightlywiderto allow headroom for buffer regulation.

Channel uptimeThe elapsed time since last re-synchronisation occurred.

Number of re-synchsDisplays the number of re-synchronisations since the last unit power up, or since the ResetStats function was last used (see Section 8.5.2.1).

8.5.2.4 Services

The Services page displays information relative to each service present in the stream.

8.5.2.4.1 Service List

The Service List tab displays a list of services running in the selected input. Each service type isrepresented by a symbol coloured to show the current alarm status of the service (figure 8.58).

Sort bySelecting the SID or Name radio button sorts the list by service ID or service name, respec-tively.

WEB Interface 113


Figure 8.58 Service details overview when service list is not expanded.

Clicking on a service name (folder name) brings up a tab navigator to the right of the list containingmore information about the selected service.

Details tab

The Details tab shows detailed information about the selected service. The service informationmay be presented in one or two sections. The first section, Service Details, is always present andconsists of the following parameters:

Service IDThe service id of the selected service.

PMT PIDThe program map table PID of the service.

PCR PIDThe PCR PID of the service.

Total rateThe current bitrate of the service. The service bitrate is the sum of the bitrates of the PIDspertaining to the service (PMT, PCR, ECMs and the component PIDs signalled in PMT). IfPIDs are shared between services, the displayed sum of the bitrates of all servicesmay exceedthe total bitrate of the transport stream.

Min rateThe minimum bit rate measured for this service since the last reset. Resets when the PIDrates are reset.

Max rateThe maximum bit rate measured for this service since the last reset. Resets when the PIDrates are reset.

In DVB mode the second section, Service SDT Details, will be present only if the SDT table ispresent and analysed. It consists of the following parameters:

Service nameThe name of the service.

114 WEB Interface


Service providerThe provider of the service.

Service typeThe type of service.

EIT schedule signalledWhether the EIT schedule information is signalled to be present for this service. This infor-mation is extracted from SDT actual.

Scrambling signalledWhether scrambling is signalled for the service. Interpretation of the Free_CA bit in SDTactual.

EIT P/F signalledWhether EIT present/following information is signalled to be present for this service. Thisinformation is extracted from SDT actual.

Running statusThe running status of the service as signalled in SDT actual.

In ATSC mode the second section is named Channel Details and shows the following parametersfrom 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 tabThe Alarms shown in figure 8.59 tab lists all the current alarms related to the selected service. Thefollowing information is provided:

SeverityThe severity of the alarm.

DescriptionBref description of the alarm.

Alarm IDThe alarm identifier.

DetailsSome additional details.

WEB Interface 115


Figure 8.59 Service alarms overview

Descriptors tab

The Descriptors shown in figure 8.60 tab displays the list of the PMT and SDT descriptors of theservice.

Figure 8.60 Service descriptors overview

Component details

To list all components contained within a specific service click the arrow for the given service. Theexpanded view is shown in Figure 8.61.

Each component is shown with the following information:

Component type symbolSymbol showing the kind of component.

Textual descriptionA text description of the component type.

Type idThe component type id.

116 WEB Interface


Figure 8.61 Service details full component overview

PIDThe transport PID number.

Clicking on a component in the left hand list of services and components opens aComponentsviewon the right hand side. On the top of this view is a toolbar with two buttons to switch betweenTable and Rate views.

These views contain almost exactly the same information as the corresponding view on the PIDspage, Section 8.5.2.5. The only difference is that in grid view a list of descriptors may be displayedbelow the Components table when clicking on a component. A tree structure of descriptors isdisplayed, if present, in the selected component.

8.5.2.5 PIDs

This page gives detailed information about the PIDs present on the input. Several different PIDviews may be selected with buttons on the tool bar at the top of the page.

8.5.2.5.1 PIDs Grid

The Grid button selects a listing of the PIDs in table form, the Rate button selects a bar graphrepresentation, indicating dynamically the bit rate of each PID.

The PID table contains the following columns:

InfoThis column shows icons describing some aspects of the PID. The significance of the icons isgiven below.

WEB Interface 117


Figure 8.62 PID Details, table view

Figure 8.63 Statusicons 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.

PIDThis is the packet stream id.

TypeThis is the packet stream type. Unsignalled PIDs have no type.

BitrateThis is the current bitrate of the packet stream in Mbit/s.

Min RateThis is the minimum rate of the packet stream in Mbit/s since the last rate reset.

Max RateThis is the maximum rate of the packet stream in Mbit/s since the last rate reset.

118 WEB Interface


CCErr CntThis is a counter which shows the number of Continuity Count errors on this packet streamsince the last CC error count reset.

Ref. by ServiceThis 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.

CountNumber of packets counted for this packet stream since last couter reset.

Beneath the PID table are three buttons:

Reset CC error countsThis resets the CC error counters for all packet streams.

Reset min/max ratesThis button resets the min and max bit rate measurements for all packet streams.

Reset packet countsThis button resets the packet counters for all packet streams.

8.5.2.5.2 PID rates

The PID rates sub-tab is shown in figure 8.64. To the left is the bar chart showing the PIDs and tothe right are some options for configuring the view.

Figure 8.64 PID Details, rate view

WEB Interface 119


Vertically, the chart displays one bar for each of the packet streams present on the input. Adjacentto the PIDs the symbols shown in figure 8.63 are shown if relevant.Horisontally, the bar chart shows the current rate and theminimumandmaximum ratesmeasuredfor each packet stream. The blue bar shows the current rate. The grey bar shows minimum andmaximum rates. Holding the mouse cursor over a bar shows a tool tip with the rates as a numericvalue.To the right of the chart, a field of options are provided to configure the view. The Sort by drop-downmenu on top lets the user sort the bar chart by different parameters. The Filtering frame letsthe user choose which PIDs to show. Checking the Hide null PID check box removes the null PIDfrom the chart. Unchecking any of the other check boxes removes the corresponding PIDs fromthe chart. Below the Filtering frame the Reset min/max bitrates button is provided. Hitting thisbutton resets the min and max rates counters of all PIDs.

8.5.2.6 Tables

The Tables page shows detailed information about all the tables that are currently residing in theinput SI/PSIP database of the device. Accessing the related sub pages gives access to table contentsright down to byte level.Which tables being currently analysed by the device is also displayed.

“Tables” tabThe button switches to a detailed view of the tables present on the input and analysed by thedevice.

“Settings” tabThis button switches to a page showing what tables are being analysed.

“Table source settings” tabThis button switches to a page allowing the user to configure non-default source PID ofSI/PSIP tables.

8.5.2.6.1 Tables

Figure 8.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 inputand analysed by the device. The tables belonging to a specific folder are displayed to the right byclicking on the folder.Above the table the following information and buttons can be found:

Shown tablesThe number of table that fall into the chosen folder compared to the total number of tables.

Shown sizeThe size(in bytes) of the tables that fall into the chosen folder compared to the total size ofthe tables.

Show ID’s asConfigure to view id’s and keys in hexadecimal or decimal notation.

120 WEB Interface


Figure 8.65 Table details, overview.

The right hand side table of the sub page has the following columns:

TableThe type of information table and (in braces, []) the PID containing it.

TIDThe table ID.

PrimaryThe primary extension ID of the table. Hovering the mouse cursor over the value displays atool tip describing the meaning of this key in the context of the table.

SecondaryThe secondary extension ID of the table. Hovering the mouse cursor over the value displaysa tool tip describing the meaning of the secondary ID in the context of this table.

TertiaryThe tertiary extension ID of the table. Hovering the mouse cursor over the value displays atool tip describing the meaning of the key in the context of this table.

VerThis is the last received version of this table.

AgeThe time elapsed since the table was last updated. Selecting a single table from the tree tothe left or double clicking a line within the table opens a view displaying the parameters ofthat table. The parameters are the same as are shown in the table view.

WEB Interface 121


8.5.2.6.2 Sources

Figure 8.66 Non-standard table sourcePID 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 8.66 and contains a grid with the following columns:

TableThe table type to configure with its table ID in decimal in brackets.

Source PIDThe input PID to use in the section filter for this table ID. Click the grid cell to edit it. Editedfields are shown in yellow until applied.

Default Src PIDThe 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 tothe 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 beperformed with care. If you specify a PID that contains a high bandwidthPID it may cause the unit to malfunction.

122 WEB Interface


8.5.2.6.3 Settings

Figure 8.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 ofdays worth of data to be configured.

To commit changes to the settings on this page, click the Apply button located at the bottom of thepage. Press Refresh to reload the settings which may have been changed by another user.

Figure 8.67 shows the page as displayed in DVB mode.

In ATSC mode the page looks different, as shown in figure 8.68

• To be able to see programs and program components you must analyse at least PAT andPMT.

• To see the service name for the services you have to configure analysis of SDTa (SDTactual) 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 beneficialto disable EIT analysis (EITpfa, EITpfo, EITsa, EITso). In the Table Timeout Settings field it ispossible to change the timeouts used when detecting the presence of each table. The values arespecified in number of seconds.

WEB Interface 123


Figure 8.68 Table analysis configuration in ATSC mode.

Configuring larger time-out tolerances for tables that are occurring with non-standard repetitionintervals can reduce the number of alarms generated. Right-clicking each timeout parameter andselecting Set to default resets the original value.The timeout values are also used to generate Table missing alarms.

8.5.3 Switch

This page has two sub-tabs;Main and Alarms. In all sub-pages for a switch a list of current alarmsis shown. This list is identical to the list displayed in the Current Status view, and described inSection 8.3.1.

8.5.3.1 Main

Figure 8.69 Input switch configuration

TheMain sub page is used to configure input switching of a group of inputs. The page is accessedby selecting a switch in the left hand side navigator on the Inputs tab, or by double clicking theswitch entry on the Inputs Overview > Switch Inputs page. See Section 8.5.1.2 for instructionshow to create a switch input.

124 WEB Interface


The availability of input switching is determined by the SW licence key Input switching.Ports can be added to the switch in two ways.

1. Drag physical ports in the left hand side navigator, dropping them into the switch groupat the wanted priority position.

2. Select the wanted port in the drop down in the Input switch configuration and press theAdd button. Press Apply to commit.

A physical port can only be used in one switch group. When a physical port is used in a switchgroup, it cannot be used directly as a physical port when configuring services and PIDs.

Switch configuration

EnableEnable/Disable the switch as a source. When disabling the switch, no datawill be forwardedto the output from the switched input.

LabelA user spesified name for this switch.

Automatic switchEnable/disable auto-switching. If turned on, automatical switching will happen accordingto switching rules. The switch will always select the highest prioritized input that is valid.Valid input are in sync and does not have a Critical alarm condition. If disabled, switchingis only done manually by selecting port and pressing Switch To. If disabled, the alarm Autoswitching disabled will be set to warn that no auto-switching will happen. If disabled theunit will remember the selected input, even during power loss.

Switch waitTime towait before switching, in case switching condition disappears. Given in secondswithdecimals, but resolution is currently 0.5 seconds. Set this to 0 for fastest possible switching.

Return waitReturn wait activated when switching away from a port. It will not be possible to return toa port before Return wait seconds has passed. The return wait is a state for each input, so itwill be possible to auto-switch to other ports that has not recently been switching away from.The return wait period can be used to avoid frequent switching between inputs.

StatusShows current state, Idle, Active,Wait or Holdwith some timing information.

Selected inputThe currently selected input.

Automatic switchesNumber of automatic switches performed since Reset Stats was last activated. When aswitch has been done, an alarm event can be found in the alarm log.

Manual switchesNumber of manual switches performed since Reset Statswas last activated. When a switchhas been done, an alarm event can be found in the alarm log.

WEB Interface 125


Switch Input ConfigurationList of inputs pertaining to the switch group. Columns are:

InputName of the input port

StatusInput alarm status

ValidStatus of input saying if the input will be considered as valid when performing an au-tomatic switch. If not Valid and selected the switch will try to switch to the highestprioritised input that is Valid.

ReturnWhether to automatically return to this port if is valid, even when the currently selectedport is valid. Will only return to higher prioritized sources.

Add port by selecting the port in the drop-down list and pressing Add.Remove a port by selecting the port in the grid and pressing Remove.Switch manually to a port by selecting it in the grid and pressing Switch To.

Note: When doing manual switches in Automatic switch mode, the switchmight automatically switch away from the selected input after the ReturnWait time has passed.

8.5.3.2 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 8.4.2.1.

8.6 OutputsThe Outputs page contains all information and settings that apply to the output ports on the de-vice. The navigation list on the left side lets the user select which output to view, or to select’Outputs Overview’ to view a summary of all the outputs on the device.The labelling of the outputs is a combination of the user defined name of the output and thephysical number of the output port.

8.6.1 Outputs Overview

Figure 8.70 Outputs Overview

126 WEB Interface


The Outputs Overview page shows a short summary of all the logical TS outputs on the device.

The table has the following columns:

EnableThis shows whether the output is enabled or not. The output enabled or disabled for anoutput by clicking this check box and hitting apply.

OutputThe name of the output, consisting of the user defined name combinedwith the physical portnumber.

Total BitrateThe total bitrate of the transport stream currently transmitted on the output in Mbit/s.

Effective BitrateThe effective bitrate (total minus null packets) of the transport stream currently transmittedon the output in Mbit/s.

Alarm StatusThe current alarm status of the output is shown as a coloured circle.

8.6.2 T2-MI Output

Figure 8.71 Output header

When selecting an output a new page on the right hand side with information about the selectedoutput is displayed. The top part of that page is common for all sub pages and is divided into twomain sections. The left section shows the name and the current alarm status of the output.

All current alarms on this output are displayed in a tool tip by holding the mouse cursor over thealarm status indicator.

The right section consists of a utilisation bar and a number showing the total rate that is currentlybeing transmitted on this output. The utilisation bar shows how much of the total rate is filledwith data. A tool-tip on the utilisation bar shows the current effective bitrate.

Underneath the name of the output is a tab navigator, which contains the different sub pages withinformation about the selected output. The choices are:

MainThis page includes information on theASI output, the user canmonitor and configure severalparameters of the chosen output.

DVB-T2This page displays information and settings related to the DVB-T2 system. Included areL1-signalling, SFN, PLP configuration, individual addressing and modulation interface set-tings.

WEB Interface 127


AlarmsThis page displays the status of all output related alarms, and lets the user override the sever-ity of these alarms.

OutgoingThis page shows a detailed view of the PIDs being currently transmitted.

8.6.3 Main

Figure 8.72 Output Configuration.

The Main page lets the user configure port level parameters on the selected Output.

The page is shown in figure 8.72 for manual bitrate config mode.

The Main Configuration section lets the user configure the following parameters:

Enable outputEnable or disable the output.

Output labelThis lets the user type in a label for the selected output. The label is only used for presenta-tional purposes.

Bitrate settingThis lets the user to manually enter a bitrate or let it be set automatically by the unit. Ifautomatic mode is selected the CP560 will always select the minimum bitrate needed for theT2-MI stream, thus reducing the number of stuffing packets (PID: 8191) to zero.

Set output bitrateThis field sets the desired ASI output bitrate for the selected port.

Current bitrateThis shows the current measured total bitrate being transmitted on this output. This valuemay vary slightly from the configured value due to measurement errors.

128 WEB Interface


Effective bitrateThis shows the effective bitrate being transmitted on this output.

Forced stuffingThis parameter is used to guarantee a minimum amount of null packets (PID 8191) in theoutput stream, When enabled, the parameter specifies the maximum number of non-nullpackets to transmit before inserting a null packet. The bitrate resulting from the configuredvalue and the corresponding percentage of the total stream is displayed to the right and isvisible before pressing apply. The range of the parameter is 1-65565. Typing 1 would meantransmitting a null packet at every second packet position, typing 99 would guarantee 1%stuffing.

Stuffing packetsThis status parameter shows the number of stuffing packets transmitted on the output. Thevalue can be cleared with the R button next to it.

ASI modeThis lets the user choose how to transmit the transport stream packets on this output, burstmode or spread mode.

Packet lengthThis lets the user configure the output to transmit 188 or 204 byte transport stream packets.

Reed-Solomon FECThis field enables Reed-Solomon ASI FEC. To enable this functionality set the packet lengthto 204 bytes. The unit will send Reed-Solomon FEC packets (16 Bytes).

8.6.4 DVB-T2

This tab contains the DVB-T2 settings for the CP560.

8.6.4.1 Main configuration

This page displays information about the DVB-T2 signal and includes the main settings for theT2-Framing. There are several under the hood validations of the various DVB-T2 parameters. Theallowed settings can be found in [8]: ETSI EN 302 755, and some of them are shown in appendixE.

T2-ProfileSelect which T2-Profile to use. The standard profile is T2-Base, while T2-Lite has been in-troduced in T2 version 1.3.1. T2-Lite is intended for mobile applications. The T2-Base-Liteoption is the intersection between T2-Base and T2-Lite, i.e. a signal that is valid for bothT2-Base and T2-Lite profiles. The T2-Base-Lite profile will be signalled as a normal T2-Basesignal, but with the T2_BASE_LITE flag set in the L1-Pre signaling.

BandwidthThis field allows the setting of the bandwidth of the transmission channel. Possible values are1.7MHz, 5MHz, 6MHz, 7MHz, 8MHz, 10MHz. 10Mhz is only intended for test applications.

WEB Interface 129


Figure 8.73 DVB-T2 Main Config

Cell IDThis field identifies a geographic cell in a DVB-T2 network.

Network IDThis field identifies the current DVB-T2 network.

T2 System IDThis field identifies the DVB-T2 system within the DVB-T2 network.

T2 versionThis field selects the version of the DVB-T2 specification. Changing from version 1.1.1 to 1.2.1or 1.3.1 makes the CP560 signal High Efficiency and Normal Mode in the L1-signalling. Italso gives a different selection of PAPR techniques.

The following settings define the structure of the T2-Frame.

Preamble formatThe preamble is a DVB-T2 preamble that indicates whether the P2 part should be transmittedin MISO (Multiple Input Single Output) or SISO (Single Input Single Output)format.

Extended carrier modeThe extended carrier mode allows an optimum use of the channel bandwidth together withthe higher FFT sizes (supported for 8K, 16K and 32K FFT).

FFT sizeThis field indicates the nominal FFT size of the symbols. Possible values are 1K, 2K, 4K, 8K,16K, 32K.

130 WEB Interface


Guard intervalGuard intervals are used to ensure that distinct transmissions do not interfere with one an-other. It can be seen as a hard limit to the channel extent that can be tolerated by the system.The choice of the guard interval requires consideration of the FFT size.

PAPR reductionTwo Peak-to-average power ratio (PAPR) reduction techniques are supported in DVB-T2:

• for DVB-T2 version 1.1.1 supported techniques are Active Constellation Extension(ACE) and Tone Reservation (TR). The two techniques are not mutually exclusiveand a combination of them can be used.

• for DVB-T2 version 1.2.1 supported techniques are L1-ACE/P2-TR, L1-ACE/ACE-PAPR, L1-ACE/TR-PAPR, L1-ACE/ACE and TR

Pilot patternPilot patterns are used by the receiver to estimate changes in channel response in both timeand frequency dimensions. There are eight patterns available.

Num T2 framesThe number of DVB-T2 frames within a DVB-T2 super-frame.

Num OFDM symbolsThe number of OFDM symbols a DVB-T2 frame is mapped to. This number includes the P2symbols, such that to get the number of Data symbols one has to subtract the number of P2symbols. THe number of P2 symbols is automatically calculated and displayed in the Statusframe.

RF FrequenciesDefines a list of used RF frequencies. Typically only one entry is required. Note that somemodulators override this setting.

L1-modulationThis field indicates the used modulation for the L1 signalling. Possible values are:

• Binary Phase Shift Keying (BPSK)

• Quadrature Phase Shift Keying (QPSK)

• 16 Quadrature Amplitude Modulation (16-QAM)


L1-Post scramblingEnabled scrambling of the L1-Post signaling. Uses same scrambling sequence as BBFrames.For version 1.3.1 and newer.

WEB Interface 131


8.6.4.2 SFN Configuration

The SFN Configuration page is only visible if the SFN feature is available.

Figure 8.74 SFN Configuration

Timestamp typeThis field indicates the type of the time stamp to be sent to the modulator. Possible valuesare:

• Null: Seconds and subsecond field set to 1’s. For MFN networks.

• Relative: Seconds field set to 0’s, while subsecond field locked to 1PPS. For SFNnetworks.

• Absolute: Seconds field locked to SNTP, subsecond field locked to 1PPS. For SFNnetworks. Allows delays from T2-Gateway to modulators of more than 1 second.

ResyncPressing this button resynchronizes the T2 transmission with SNTP and external PPS. Thisis required when changing the SNTP server.

Warning: Resyncing may disrupt the T2 signal, which in turn might causethe modulator to lose sync.

Resyncing causes the T2 Gateway to synchronize it’s timestamp to the highest prioritized SNTPserver, see section 8.4.4. Resyncing might also cause the output TS rate to drop temporarily, whilethe T2-Gateway is waiting for the next superframe boundary. When synced the T2-Timestampseconds field will be based on the SNTP time, while the subsecond field will be synchronized tothe external PPS.

132 WEB Interface


Note: Please wait a few seconds for the resync to take effect.

Timestamp sync.Status field stating which SNTP server is used for the initial synchronisation and the statusof the Clock regulator.

Estimated Transmission TimeThis field indicates the time (in ms) the DVB-T2 frames are sent ahead of the transmissiontime. Relevant for Relative and Absolute Timestamps. This value should take into accountall delays (buffers) from the CP560 to the transmission time in the modulator. See appendixF for details regarding the Estimated Transmission Time.

DVB-T2 MIP insertionThis feature enable the insertion of DVB-T2 MIP packets (according to ) into the incomingTransport Stream (input). This feature is usefullwhen performing “over-air” synchronizationusing re-transmitters. The PID for the MIP packets is 21 (hex 15).

Note: This functionality is only active when SFN (Time Stamp Frame) isactive.

Timestamp typeThis field indicates the type of the time stamp to be sent to the modulator. Possible valuesare:

• Null: Seconds and subsecond field set to 1’s. For MFN networks.

• Relative: Seconds field set to 0’s, while subsecond field locked to 1PPS.

• Absolute: Seconds field locked to SNTP, subsecond field locked to 1PPS.

Estimated transmission timeThis field indicates the time (in ms) the DVB-T2 frames are sent ahead of the transmissiontime. Relevant for Relative and Absolute Timestamps. This value should take into accountall delays (buffers) from the CP560 to the transmission time in the modulator.

If using Absolute timestamp or using the CP560 in a Seamless SFN system leap seconds must behandled. If not, leap seconds may be ignored.

Leap seconds since 2000This is the current amount of leap seconds accounted for since 2000. This value will be up-dated when a new leap second is added. The number of leap seconds is persistent, such thatif the units reboots after a leap second have been added, it will boot with the new amount ofleap seconds. Press Refresh to update the current number of leap seconds. Per August 2012the current number of leap seconds is 3. Leap seconds increased from 2 to 3 on June 30, 2012at 23:59:60 UTC.

WEB Interface 133


Warning: Manually changing the amount of leap seconds runtime willaffect the internal packet scheduling and may cause glitches in the outgoingstream.

Leap second transitionThe amount of leap seconds to adjust with when the Transition Date expires. Allowed valuesare +1 and -1. If set to none, leap second handling is effectively disabled.

Transition Date [UTC]Set the date for when to add the next leap second. Transition time and increment is deter-mined and announced by the International Earth Rotation and Reference Systems Service(IERS)1.

Note: Leap seconds are entered in UTC+00 time format. To get theactual time of day this will be added for your local time you need tosubtract your time zone.

Leap Second StatusStatus field for the leap second handling. Will state the number of days, hours, minutes andseconds until the configured leap second will be added.

Note: An notification will be given when the leap seconds is added. Thisnotification can be seen in the alarm log, see section 8.3.2.

8.6.4.3 PLP configuration

The PLP configuration page has all the PLP configuration parameters. The list on the left hand sideshows the current number of PLPs in the system. It is possible to have from 1 up to the licencednumber of PLPs.

PLPs Common Config lists configuration parameters that apply to all the PLPs.

Override Capacity validationThis option lets you have less cell occupancy than 50% in a T2-Frame. This is not a validsignal, and is only intended for PLP Replacement systems.

Automatic SubslicesIf using PLPs of Type 2, select if the number of subslices should be calculated automatically,or set manually. If automatically the CP560 will find the highest valid number of subslices.

Source portSelect which source you want to use for each PLP. The source may be either ASI, IP or anInput Switch. IP and Input Switch are licenced features.

http://www.iers.org1

http://www.iers.org

http://www.iers.org

http://www.iers.org

http://www.iers.org

http://www.iers.org

http://www.iers.org

134 WEB Interface


Figure 8.75 PLP Config

Note: Setting Input port to None disables the PLP, but keeps it’s configstored.

PLP idSet the PLP id for each PLP. Must be a unique number among all PLPs.

Requested bitrate (Multi PLP)Specify the desired bitrate for this PLP. When pressing Apply the CP560 will find the min-imum number of FEC blocks needed to allocate this rate. For most practical applications aslightly larger bit-rate than requested will be allocated due to requirement of whole numberof FEC blocks. This given bitrate is shown below. The CP560 might not be able to allocatethe desired bitrate if the sum of the bitrates for all PLPs exceed the total capacity of the T2-Frame. If so, a warning will be given when pressing Apply. If so the Requested bitrate mustbe decreased, or the number of bits per symbol increased or the total T2-Frame capacity mustbe incread.

PLP bitrateThe actual bitrate for given the PLP based on the requested bitrate. The PLP bitrate willalways be greater than or equal to the Requested bitrate, because the CP560 will allocate theminimum number of whole FEC blocks to accomodate the requested bitrate. If only usingone PLP, the PLP bitrate will be maximized to use the whole capacity and will thus ignorethe requested bitrate parameter.

TypeThis field indicates the type of the Physical Layer Pipe (PLP).There are 3 types of PLPs:

WEB Interface 135


• Common PLPs carry data that is shared between several services.

• Type 1 data PLP carry services that require good power saving and should be carriedafter the common PLPs.

• Type 2 data PLPs are carried inmultiple sub-slices per DVB-T2 frame in the DVB-T2-frames in which they occur. Choosing Type 2 PLP for one or more PLPs will makethe CP560 find the largest number of subslices and split the data accordingly.

Payload typeThis field indicates the type of the payload data carried by the associated PLP. Supportedtypes are:

• Transport Stream (TS)

• Generic Encapsulated Stream (GSE)

• Generic Continuous Stream (GCS)

• Generic Fixed-length Packetized Stream (GFPS)

PLP modeThis field sets the transmission mode. Two modes are available:

• Normal Mode (NM), where the Input Stream Synchronisation (ISSY) Field is ap-pended to user packets for packetized streams.

• High EfficiencyMode (HEM),where a single ISSY field is transmitted per BBFRAMEin the BBHEADER. Higher throughput than Normal Mode.

Group IDThis field identifies with which PLP group within the DVB-T2 system the current PLP isassociated.

ModulationThis field indicates the used constellation for the PLP signaling. Possible values are:

• Quadrature Phase Shift Keying (QPSK)




Rotated constellationThis feature improve the avoidence of potential problems in selective channels. This featureis only applyable for QAM constellations.

FEC TypeForward Error Correction (FEC) is a mechanism to add extra data to a transmission in orderto protect it. Dependent on the amount of extra data added, the receiverwill be able to correct

136 WEB Interface


errors (i.e. regenerate lost packets) in case of network packet loss. The two supported typesare:

• 16 K Low density parity check (LDPC)

• 64 K Low density parity check (LDPC)

Code rateThis field sets the value of the code rate, it sets the fraction of useful data in the FEC block.Possible values are 1/2, 3/5, 2/3, 3/4, 4/5, 5/6 for T2-Base and 1/3, 2/5, 1/2, 3/5, 2/3, 3/4for T2-Lite. Values closer to 1 gives less protection but more data bits throughput.

Time interleaving typeThis field indicates the type of time-interleaving.

Time interleaving lengthThis field indicates the length of the time interleaving:

• If the Time interleaving type is set to “Several T2-frame”, this field indicates thenumber of T2 frames to which each Interleaving Frame is mapped.

• If the Time interleaving type is set to “One T2-frame” this field indicates the numberof TI-blocks per Interleaving Frame. One T2-Frame corresponds to one Interleavingframe.

Null packet deletionThis feature allows to drop null packets and is only valid for Transport Stream (TS) payloadtype. Dropped null packets are restored in the receiver.

ISSYThis field enables the Input Stream Synchronisation (ISSY). Two modes are supported:

• ISSY short (Only for Normal Mode)

• ISSY long

BUFSBUFS defines the maximum size of the requested receiver buffer to compensate delay varia-tions. Maximum size of 2 Mbits. Only available when using ISSY.

Design delaySet delay through receiver buffer to handle dejitter and deinterleaving. Only available whenusing ISSY. Settings this value slightly larger than the T2-Frame duration should handlemostcases. Alternatively setting this value to 0 forces the T2 receiver to handle the delay dynam-ically.

In-band Signaling AIn-band signalingA carries L1 update information and co-scheduled information for the nextInterleaving Frame. Mandatory unless using Several T2-Frame Interleaving. Sent in the firstBBFrame of each Interleaving frame, thus reducing PLP throughput slightly. Possible to dis-able this setting for backwards config compatibility.

WEB Interface 137


In-band Signaling BIn-band signaling B carries additional information related to the Input Processing to enablefaster initial acquisition. In-band signaling B is optional. Sent in the first BBFrame of eachInterleaving frame, thus reducing PLP throughput slightly.

The list in figure 8.75 shows all current PLPs. PLPs with port set to None are disabled, whichmeans these PLPs are not transmitted in any way. The PLP lists has a few columns showing someimportant information.

IDThe PLP Id for each PLP.

SourceThe Input Port for each PLP.

PLP fillThis parameter represents the average fill level of a given PLP, i.e. the percentage of FEC blockbits used for data compared to the total bits available for data. This value should ideally beclose to 100.0% to not waste capacity on air. To increase this value, either input a TransportStream with highter bitrate or change the PLP settings.

PLP bitrateThe actual bitrate for given the PLP based on the requested bitrate. The PLP bitrate willalways be greater than or equal to the requested bitrate, because the CP560 will allocate theminimum number of whole FEC blocks to accomodate the requested bitrate. If only usingone PLP, the PLP bitrate will bemaximized to use thewhole capacity andwill thus ignore therequested bitrate parameter. To see the amount of FEC blocks, cells and subslices allocatedfor each PLP, hover the mouse pointer over this field to get a tool tip as shown in figure 8.76.

Figure 8.76 DVB-T2PLP Allocations

At the bottom right of figure 8.75 there are some additional status parameters, as well as aAllocateMax button.

Total rateDisplays the total rate usable for tranmission of TS packets on the output. This is the rateused by the modulator when transmitting. The total input rate for all PLPs must be lowerthan this value, or else packets will be dropped.

138 WEB Interface


Used capacityDisplays the percentage of the total rate actually usable for data. Usually below 100% becausethe number of data cells is not a whole number of cells per FEC block. By hovering themouse pointer over this parameter, you will get a detailed description of how the cells of oneT2-Frame has been allocated.

Allocate MaxPressing theAllocate Max buttonwill give the selected PLP the remaining T2-Frame capacity(if any). If running in Single PLP mode, the PLP will automatically be allocated the fullcapacity of the T2 Frame.

8.6.4.3.1 Source bit rate control settings

This feature (optional) allows the DVB-T2 Gateway to control the bit rate of its source. Each PLPwill send a request to it’s source device to adjust the bitrate. This feature is meant to avoid inputoverflow situations in the Gateway.A request is sent to the source device after every configuration change that may cause a bit ratechange.

EnableThis check box enables/ disables sending of bit rate requests to the source device.

IP addressThe IP address of the source device (e.g. CP525 cMux).

OIDThe SNMP OID describing the bit rate parameter on the source device.

Note: This field should include the OID and the instance num-ber appended. If the bit rate OID is 1.3.6.1.4.1.22909.1.3.2.1.1.1.7and the instance is 7, this field must contain the string 1.3.6.1.4.1.22909.1.3.2.1.1.1.7.7.

OID typeThe data type of the OID.

Read community stringThe string required to read data from the source device.

Write community stringThe string needed to write data to the source device.

Remote packet lengthThe length of the TS packets coming from the source device. The bit rate is automaticallyscaled to fit the selected packet length.

Note: It is recommended to verify the bit rate on the source device afterusing the joint bit rate control feature.

WEB Interface 139


8.6.4.4 Modulation interface configuration

This section contains configuration parameters for the outer TS layer carrying the T2-MI.

Figure 8.77 DVB-T2Modulation Inter-face Config

TS PIDThis field indicates the PID of the outgoing transport stream that carries the T2-MI packets.

Transmit PATThis field defines whether the Program Allocation Table (PAT) should be sent or not.

Transport stream IDThis field indicates the Transport Stream (TS) ID that should be transmitted in the PAT.

Transmit PMTThis field defines whether the Program Mapping Table (PMT) should be sent or not.

PMT program IDThis field indicates the program ID carried in the PMT.

PMT PIDThis field indicates the PID of the PMT.

Transmit PCRThis field defines whether PCR packets should be inserted into the outer TS layer or not.

PCR PIDThis field indicates the PID of the inserted PCR packets

PCR intervalThis field indicates the distance between two PCR packets in ms. The maximum value is 40ms.

140 WEB Interface


Reduce efficiencyEnabling this feature causes the CP560 to not have more than one T2-MI packet in one TSpacket when creating the outer TS layer. This results in more stuffing thus giving a higherTS output bitrate. This may improve T2-MI seamless switching.

Enable ETR290 Pri 2 errorEnabling this feature causes the CP560 to set the Transport Error Indicator bit of the outgoingT2-MI PID if any of the PLPs are output without any payload. This could be used as a triggerfor other units later in the chain.

8.6.4.5 Individual addressing configuration

Figure 8.78 Individual Addressing Config

On this page the user can set up sending of Individual Addressing frames 8.6.3 according to [9]:ETSI EN 102 773 and [5]: DVB mega-frame for SFN synchronisation.

The user is able to select which parameters to send to the individual modulators.

EnableThis check box enables/ disables sending of the Individual Addressing frame.

Adding settings for a modulator is done by first pressing the Add button to add a newmodulator.Every modulator has different settings that are possible to edit. The PAPR parameters (ACE, TRand L1-ACE) are not mandatory and the user may specify which to send. The values entered foreach of the Individual Addressing parameters are sent without any modifications. See [9]: ETSIEN 102 773 for further description of the parameters. Each modulator must be configured with aModulato/Transmitter Id which matches the Modulator ID in the Indivuidual Addressing list.

WEB Interface 141


Modulator IDUnique ID of the modulator to be individually addressed.

Note: Modulator ID “0” is reserved as broadcast, i.e. all modulator willapply the configuration for Modulator ID “0”.

MISO groupEnable sending of MISO group parameter. Used to group the modulators into MISO group1 or 2.

TX-Freq OffsetSelect if individual addressing frame with Transmitter Frequency Offset is to be sent. Usermust specify Frequency Offset.

TX-Time OffsetSelect individual addressing frame with Transmitter Time Offset is to be sent. User mustspecify Time Offset.

TX-PowerSelect if individual addressing frame with Transmitter Power is to be sent. User must specifyPower .

Private DataSelect if individual addressing framewith Private Data is to be sent. Usermust specifyPrivateData as hexadecimal string.

Cell IdSet the Cell Id of the transmitter.

L1-ACE PAPRSelect if individual addressing frame with ACE (Active Constellation Extension) parameterfor the L1-signaling is to be sent. User must specify value of Max correction.

ACE PAPRSelect if individual addressing frame with ACE (Active Constellation Extension) parameteris to be sent. User must specify Gain,Max Extension and Clipping threshold.

Tone ReservationSelect if individual addressing frame with Tone Reservation parameter is to be sent. Usermust specify Clipping threshold and Number of iterations.

TX-SIG FEF streamSelect if the transmitter ID using FEF frames is to be sent. User must specify TX-SIG 1 andTX-SIG 2.

142 WEB Interface


8.6.4.6 Future Extension Frames configuration

On this page the user can set up sending of Future Extension Frames in the DVB-T2 signal accord-ing to [9]: ETSI EN 102 773 and [10]: DVB Document A150. Currently the implementation onlysupport FEF part Composite with FEF sub-part TX-SIG. This must be used in conjunction withIndividual Addressing with TX-SIG 1 and TX-SIG 2. See section 8.6.4.5.

Figure 8.79 FutureExtension Frames Config

EnableEnable FEF part insertion in the T2 stream.

IntervalNumber of T2-Frames between each FEF part. This interval must be such that a whole num-ber of FEFpartswill be inserted. This parameterwill be validated against theNum T2 Framesparameters under the Main settings, section 8.6.4.1.

TypeThe CP560 currently only supports FEF Composite part with FEF sub-part of type TX-SIG.

Transmitter IdWhich transmitter Id the FEF part should be valid for. 0 means broadcast, i.e. all transmit-ters.

Other use periodIf desired, the duration of the FEF subpart TX-SIG may be extended by setting the this fieldto a value greater than zero. The unit is in Elementary Periods, T. See [10]: DVB DocumentA150 for further details.

8.6.5 IP

This page provides an overview of the current IP output interfaces, enables adding new inter-faces and removing existing interfaces. Each output may be individually enabled or disabled bychecking or unchecking the appropriate Enable box.To add a new IP interface click theAdd IP Dest button and clickApply. This creates a new entry inthe table. To configure the parameters of the new entry, or edit parameters of an existing interface,double click on the appropriate line in the table. This opens the configuration page, which mayalso be directly accessed by clicking on the IP output interface entry in the navigator field (Figure8.70). This is described in detail in Section 8.6.6.1.

WEB Interface 143


Figure 8.80 IP output interface overview.

Removing an IP output interface is accomplished by highlighting the appropriate line in the tableand clicking the Remove IP Dest button followed by Apply.

8.6.6 TS-OUT -> IP Destination

This page allows configuration of the IP output port. This page consists of the sub tabsMain andPing. If Forward Error Correction has been enabled the FEC tab is also visible.

8.6.6.1 Main

This page is shown in Figure 8.81.

Figure 8.81 IP Configuration.

The Basic IP Config field:

144 WEB Interface


EnableIf this box is checked, the generated transport stream will be played out over IP using theshown parameters.

IP destination addrEnter the destination IP address to use when transmitting data over IP. The address may beeither a unicast address or a multicast address.

ProtocolSelect UDP or RTP transmission mode. See Section 5.5.2 for more information on this.

UDP destination portEnter the UDP destination port to use when transmitting data over IP. The UDP destinationport is used by the receiver to separate one stream from another. UDP port numbers are inthe range 1-65535.

Warning: Please ensure that there is no conflict in UDP ports in use. Payspecial attention to the fact that FEC data are always sent on UDP portstwo 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.

UDP source portEnter the UDP source port to be used in the outgoing UDP frames. UDP port numbers are inthe range 1-65535. Note that the receiver unit may not check the source port when receivingstreams. FEC frames are transmitted using the same UDP source port as the media frames.

TS packets per frameEnter the number of 188 byteMPEG-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 andEthernet frame rate. For very low bitrate streams, less than 7 packets per frame may be usedto 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) fieldin 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 theIP header as specified in RFC-791.

Manual destination interfaceIf you want to manually set the interface you want the data to be transmitted through, checkthe box and select the wanted interface. If you wish to use the IP routing configuration leavethe box unchecked.

The Advanced IP Config field:

WEB Interface 145


Use multicast routerClick this box to forward the multicast stream to an external multicast router. The unicastIP address to the multicast router can be configured for each Ethernet or SFP interface andalso for each VLAN. This IP address must be within the sub-net range. When this option isenabled the multicast MAC destination address will be replaced with a unicast MAC desti-nation address. The unicast MAC destination address is detected by resolving the unicast IPaddress of the multicast router using ARP. If the ARP request fails, the multicast transmis-sion will not start (or will be stopped). If this option is disabled then the standard multicastdestination MAC address will be selected.

Override VLAN priorityPriority is normally configured per VLAN interface. It is possible to override the VLANpriority field for the output stream by checking this box and entering a new priority value.

Static destination MACStatic 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 IPOption to use a different IP address than the one on the Ethernet interface when transmittingIP frames with transport stream data.

SSRC ModeOption to control SSRC (Synchronization source) identifier field transmitted in RTP headerof data stream.

RandomUse a random number as suggested in RFC3550 and allowed by SMPTE2022-1. A newrandom number is generated every time channel is enabled for transmission. The samerandom number is shared between all small-casts. This is the default mode.

ManualConfigure 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 interfaceThe interface the IP streamwill be transmitted through. IfManual destination interface is en-abled the configured interface will be shown. If not, the interface depends on the configureddestination address and the configured IP routing entries.

ResolvedYes 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 MACaddress is not yet resolved by ARP lookup.

Dest. MAC addressShows the destinationMACaddress used for the stream. Thismay be theMACaddress of the

146 WEB Interface


receiving unit, or the gateway if the receiving unit is on another network. If using a multicastdestination IP address without enabling multicast router, the field shows the multicast MACaddress 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 notresolved this field displays the value 00:00:00:00:00:00.

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

Data Ethernet rateThe bitrate of the MPEG-2 transport stream contained in the IP stream.

Column FEC Ethernet rateThe bitrate of the column FEC contribution to the IP data.

Row FEC Ethernet rateThe bitrate of the row FEC contribution to the IP data.

8.6.6.2 FEC

This page allows configuring and applying forward error correction data to the output IP transportstream.

Figure 8.82 IP output FEC page

In the FEC Configuration field forward error correction is enabled and configured for each indi-vidual output:

FEC modeFrom thepull-down list selectDisabled to not apply FEC,Column only to apply one-dimensionalFEC (i.e. add column FEC datagrams, only), or Column and Row to apply two-dimensionalFEC (i.e. add column and row FEC datagrams).

SSRC ModeOption to control SSRC (Synchronization source) identifier field transmitted in RTP header

WEB Interface 147


of data stream. Normally this parameter should be left at its default setting, but in case ofspecial requirements or compatibility issues, it can be used.

ManualConfigure the SSRC ID field to be used manually. Allowed to adapt to any special re-quirements or get around compatibility issues.

0 (SMPTE 2022-1)Transmit the value 0 as specified in SMPTE2022-1 andCop3. This is the default setting.

Follow data streamUse same value as used on data stream protected by the FEC. If data stream is config-ured with the default value, Random, the same random number is used on the FECstream(s).

FEC overheadGives an instant check of the overhead resulting from the applied FEC.

Resulting total rateShows 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 appliedto 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.

SkewCheck 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 rateThe bitrate of the IP frames containing this MPEG-2 transport stream and any FEC data re-lated to this stream.

Data Ethernet rateThe bitrate of the MPEG-2 transport stream contained in the IP stream.

Column FEC Ethernet rateThe bitrate of the column FEC contribution to the IP data.

Row FEC Ethernet rateThe bitrate of the row FEC contribution to the IP data.

Column UDP portThe UDP port used for column FEC data.

148 WEB Interface


Row UDP portThe UDP port used for row FEC data.

8.6.6.3 Ping

Figure 8.83 Ping page

Ping can be used to resolve network problems, avoid flooding and avoid time-out of MAC addresslookup by the transmitter or a specific network component on the way to the receiver. Ping helpsresolving such issues by sending a short message regularly. This feature also makes it possible forthe receiver to monitor if an active sender is present.

The Ping Settings field:

Enable Unicast Peer PingCheck this box to enable Unicast Peer Ping. This enables regular pinging of the receivingdevice.

IntervalSet the interval in seconds between each Ping.

The Ping Status field displays the status of the on-going pinging session:

IP destinationThe address of the device receiving the Ping requests.

Time to liveThis figure indicates the number of routing points the Ping message may encounter before itis discarded.

OK responsesIndicates how many valid Ping responses have been received.

TimeoutsIndicates howmany of the sent Pingmessages timed out, i.e. did not provide a valid responsewithin the allowed time.

WEB Interface 149


Last roundtripThe time taken from last sending the Ping message until the response is received.

Min roundtripThe minimum time taken from sending a Ping message until the response is received.

Max roundtripThe 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.The Traceroute field enables debugging of network connection with unicast remote host.

See Section 8.4.5.5.2 for a description of trace route. The IP used is the same as the destinationconfigured for the stream, and the routing follows the interface settings for the stream, so that amanual interface selection overrides the IP routing table.

8.6.7 Alarms

The Alarms page lets the user configure and view the status of all alarms belonging to the selectedoutput.

The page functions exactly like the input alarms page, except it is not possible to copy settingsfrom a different output. (See section 8.5.2.2).

150


SNMP 151


9 SNMPThe product supports

SNMP – Simple NetworkManagement Protocol – for remote control and supervision. SNMP usesan extensible design, where management information bases (MIBs) describe the structure of themanagement data of a device subsystem. The primary purpose of SNMP is to export alarm andstatus information, but a range of MIBs related to configuration settings are also supported.

9.1 SNMP agent characteristicsThe SNMP agent supports the SNMPv2c (Community based SNMPv2) protocol. All customMIBSare 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 UDPport 161.

Both legacy SNMPv1 traps and SNMPv2 notifications are supported. It is however recommendedto use the new SNMPv2 notification types for new deployments.

9.2 MIB naming conventionsAll customMIB 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 thereforestarts with this prefix.

SomeMIB-files are very custom and corresponds to a specific product only. These MIBs start statswith the prefix VIGW-PROD.

From Nevion you will receive a set of MIB files. There may be more MIB files than the CP560support, but the relevant MIB files are listed here.

9.3 MIB overviewThis section describes the different MIBs. Detailed description of MIBs is included later on in thisdocument.

9.3.1 Supported standard MIBs

RFC1213-MIBMIB-II according to RFC1213.

9.3.2 Custom MIBs

VIGW-TC-MIBDescribes common textual conventions (data types etc.) used throughout the entire MIB set.For example, definition of alarm status numbers are defined in this MIB.

152 SNMP


VIGW-BASE-MIBDefines the top level MIB structure including the enterprise specific root node for devicecontrol (1.3.6.1.4.1.22909).

VIGW-UNIT-MIBThis is a generic MIB module that defines parameters supported by all products. It is themain source for alarm and status related information. The following objects are examples ofcontents 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 sendall values for one interface in the same request. This is to prevent the unitfrom entering an undefined intermediate state.

VIGW-PLAT-PHYSICAL-PORTS-MIBThis MIB contains status and configuration for the physical ports on the unit. Parametersinclude:

• Controlling port direction if supported

VIGW-PLAT-TS-MIBThis 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 incomingtransport 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-MIBThis MIB is supported by products that can generate an outgoing transport stream. Parame-ters include:

SNMP 153


• Control of output bitrate and other ASI parameters (spread/burst mode).

• Control of MIP insertion (if enabled in the product)

− OFDMmodulation parameters

− Enable/disable of MIP insertion

• Control of PSI/SI table playout

VIGW-PLAT-TS-INPUTSWITCHING-MIBMIB containing parameters related to control of second generation input port redundancyswitch with more than 2 sources.

VIGW-PLAT-TS-IPTRANSPORT-MIBThis MIB contain status and control parameters related to the data IP receive and transmitfunctionality.

VIGW-PLAT-T2-MIBThis MIB contains tables and settings to configure DVB-T2 Gateway specific parameters. Pa-rameters include:

• T2-Frame and L1 settings

• PLP configuration

• T2-MI layer configuration

9.4 SNMP related configuration settingsThe SNMP related configuration parameters are located on the Device Info/SNMP settings pagein the GUI.

9.4.1 Community strings

The community strings are used to provide simple password protection for SNMP read and writerequests. The strings can be configured from the GUI. It is also possible to configure the commu-nity strings to be used for trap messages.

9.4.2 Trap destination table

The Trap Destination table lets the user configure the external entities that should receive SNMPtraps 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.

154 SNMP


9.4.3 Trap configuration

All supported traps are currently defined in the VIGW-UNIT-MIB. Via the GUI you can controlthe trap forwarding. For detailed information about each trap and the corresponding variablebindings, please see Section 9.5.

Trap versionThis 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 notrecommended to use these for new deployments.

SNMPv2This is the recommended setting. The traps defined under the node unitNotifica-tionswill be usedwhile the traps under the node vigwLegacyTrapswill be disabled.

Status change trapsIf enabled, the unit will transmit unitAlarmStatusChanged traps whenever the top levelalarm status is changed for the unit.

Alarm event forwardingThis setting controls how internal alarm event will be forwarded as TRAP messages. Adjustthis value if you want to control the number of traps sent from the unit. The settings are onlyused when SNMPv2 is selected as TRAP version. The settings are:

DisabledNo specific event traps are transmitted when alarms are raised or cleared. (The unitA-larmStatusChanged trap may however be transmitted).

BasicThe device forwards alarms as traps on a basic level. No information about subid3willbe transmitted.

DetailedThe device forwards alarms as traps. If there are sub-entries that are using the subid3value, each sub.entry will be transmitted in separate trap messages.

9.5 Alarm/status related SNMP TRAPsAll TRAP messages are defined in VIGW-UNIT-MIB. This section describes each trap message.

9.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 9.1.

SNMP 155


Table 9.1 List of SNMPv2 traps

unitAlarmStatusChanged This trap is sent when the top level unit alarm status (indicated by theunitAlarmStatus variable) changes. The trap indicates both the old and new alarmlevel. 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 isincluded. A corresponding unitAlarmCleared trap is sent when the alarm cause iscleared.

unitAlarmCleared This trap is sent when an alarm condition previously indicated withunitAlarmAsserted is cleared.

unitAlarmEvent This trap is sent when an alarm event (with no on/off state) is generated. Nocorresponding “cleared” message is expected for these traps. A typical example is anevent like “User logged in”.

unitDetailedAlarmAsserted This trap is a more detailed version of unitAlarmAsserted. subid3 information isincluded in addition to the basic parameters defined in unitAlarmAsserted.

unitDetailedAlarmCleared This trap is sent when an alarm condition previously indicated withunitDetailedAlarmAsserted is cleared.

unitDetailedAlarmEvent This is a more detailed version of unitAlarmEvent. subid3 information is includedin addition to the basic parameters defined in unitAlarmEvent.

9.5.2 Severity indications

All alarm event traps (i.e. all traps defined inTable 9.1 except unitAlarmStatusChanged) containa severity field which is encoded according to the definition below:

Severity Description

1 Cleared2 Indeterminate3 Warning4 Minor5 Major

6 Critical

9.5.3 Alarm event fields

A description of the fields in the alarm event traps is presented in Table 9.2. Most of the fieldsare entries from the unitEventHistoryTable. The instance identifier for each variable bindingcorresponds to the index in this table. This index is of kind CircularLog and will wrap aroundat 232.

156 SNMP


Table 9.2 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 isindicated by transmitting a unitAlarmCleared message.

unitEventAlarmType This is an integer that describes the alarm type. Please refer to alarm documentation fordescription. From this type, one can extract the actual meaning of the subid1 and subid2values in the message.

unitEventAlarmId A unique identifier for this alarm type. Refer to alarm documentation in the user manualfor 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.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 forthe entity that generated the alarm.

unitEventSubId3 This field provide an even more detailed description of the alarm source. This field is onlypresent in the “detailed” type of trap messages (unitDetailedAlarmAsserted,unitDetailedAlarmEvent). It’s usage is dependent on the alarm ID. For example, intransport stream related alarms, subid3 is used to indicate the PID value that caused thealarm.

unitEventSourceText A textual description of the source of the alarm. This is typically a textual description ofthe subid1 and subid2 fields. For example, for transport stream related alarms, the textindicates 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 theunitEventSubId3 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’susage and content is dependent on the alarm ID.

unitAlarmStatus This variable contains the new, top level alarm status of the unit after the conditionleading to this trap messsage. It may be used to quickly update the top level status for thedevice after receiving the trap message.

9.5.4 Matching of on/off traps

As mentioned previously, a unitAlarmCleared message is sent after a unitAlarmAssertedmessage and aunitDetailedAlarmClearedmessage is sent after aunitDetailedAlarmAssertedmessage.

The “cleared” event contains exactly the same identifiers as the “asserted” trap. This includes thealarm ID, subid1, subid2 and subid3 fields. This set of four identifiers uniquely identifies thesource of an alarm.

A more easy way to match the traps is by using the unitEventRefNumber field. This is a simpleinteger that is the same in an “asserted” trap and in a “clear” trap.

SNMP 157


9.5.5 Legacy trap messages

Note: The information in this section relates to trap definitions thatare marked as deprecated in VIGW-UNIT-MIB. They are included forbackwards 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 isspecified by selecting “SNMPv1 (Legacy)” for the trap version field. The format of these trapsfollow the SNMPv1 trap format.

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

Table 9.3 List of legacy (SNMPv1) traps

alarmCleared This trap is sent when an alarm goes off (i.e. is cleared) in the system. The bindingunitTrapHistoryRefNumber matches the corresponding unitTrapHistoryRefNumber inthe “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 tableis filled up with historical trap messages, only when SNMPv1 mode is selected.

The fields in these traps are fetched from the unitAlarmTrapHistoryTable. The meaning ofthese fields correspond to the fields in the unitEventHistoryTable for SNMPv2 traps and arenot described in more detail here.

9.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 andsnmpset for set operations.

The WEB site and the tools provides extensive usage information. We do however present someexamples in this chapter for convenience.

http://www.net-snmp.org/








158 SNMP


9.6.1 Reading a parameter with snmpget

The command line tool to read an SNMP parameter is snmpget. The following example showshow the command is used to read system up time from a device:

snmpget -v 2c -c public <ip-address> sysUpTime.0DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (250792000) 29 days, 0:38:40.00

Note the following parameters used:

-v 2cThis indicates that the version to be used is 2c. This is important as the default value is 3,which is currently not supported.

-c publicThis is the community string (password) used for the request. It shouldmatch the configuredSNMP agent settings. The default value is “public”.

<ip-address>This is the IP address for the device to read from.

sysUpTime.0This is the OID for the parameter to read. Since we read a scalar value, we need to add .0 tothe OID from the MIB. Note that it is legal to use a numerical OID in this list; the OID mustmatch the parameter definition in the MIB file.

9.6.2 Writing a parameter with snmpset

The command line tool to set an SNMP parameter is snmpset. The following example shows howthe 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 2cThis indicates that the version to be used is 2c. This is important as the default value is 3,which is currently not supported.

-c privateThis is the community string (password) used for the request. It shouldmatch the configuredSNMP agent settings. The default value for write access is “private”.

<ip-address>This is the IP address for the device.

sysName.0This 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 OIDmust 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 theactual string value. The type should match the type defined in the MIB file.

Examples of Use 159


10 Examples of Use10.1 IntroThis chapter offers a small selection of different practical examples of use of the CP560, with corre-sponding recommended configuration steps, pointing to section in Chapter 8 where the relevantconfiguration pages are described.

10.2 Installation in a systemWhen installing the device in a new environment, there are a few parameters that typically needto be configured. These steps are the same for all the cases studied below.

1. Set the IP address as described in section 7.3

2. Assign a name for the device. See section 8.4.1.

3. If you are unsure of the state of the device, set it back to factory default configuration asdescribed in section 8.4.8.1.

4. Configure a time zone and a source for the real time clock, to assure alarm log entries getcorrect time stamping. See section 8.4.4.

5. Connect the input signal to the 1 PPS input.

6. On the "Clock Regulator" tab. Set the "27 MHz lock mode" to the external 1PPS. This isshow in section 8.4.6.

7. Check the "Regulator state" it will changes to "Finetune" when ready.

8. Enable the input ports to use and disable the ones that will not be used (see section 8.5.1).

9. Enable the output and configure the wanted output T2-MI nullpacket bitrate. The outputbitrate should exceed the maximum configurable TS rate, but no larger then 72MBit/s.Refer to section 8.6.3.

10.3 Single PLP at 40MBit/sThemost basic way of using the CP560 is to encapsulate oneDVB-TS stream into one PLP. By usingthe VV500 (V&V 500, T2-MI test case) profile, the TS transmission bitrate will be 40.214 MBit/s.This is the default configuration for the CP560 and has the following parameters.Main configuration

• System

− Bandwidth: 8MHz

• L1

− Modulation: 64-QAM

160 Examples of Use


• DVB-T2 Frame

− Preamble format: SISO

− Extended carrier mode: Enabled

− FFT size: 32K

− Guard interval: 1/128

− PAPR reduction: None

− Pilot pattern: PP7

− Num DVB-T2 frames: 2

− Num OFDM symbols: 60

• Timestamp

− Timestamp type: Null

− Estimated transmission time: 1000

PLP configuration

• PLP Settings

− Input port: ASI 1

− Payload type: TS

− PLP mode: High Efficiency

− Group id: 0

− Modulation: 256-QAM

− Rotated constellation: Enabled

− FEC type: 64K LDPC

− Code rate: 2/3

− Time interleaving type: One DVB-T2 Frame

− Time interleaving length: 3

− ISSY: Disabled

− Null packet deletion: Disabled

The input TS stream will now be encapsulated and sent over the T2-MI interface to a modulatorwhich will transmit this on air.

Examples of Use 161


10.4 SFN operation

DVB-T2

Gateway

DVB-TS

T2-MI

(ASI or IP)

DVB-T2

Modulator

T2-MI network

ASI, IP or a combination T2-MI

(ASI or IP)

DVB-T2

Modulator

T2-MI

(ASI or IP)

Figure 10.1 Distribution via DVB-T2Gateway and T2-MI interface

This example briefly gives needed configurations related to SFN operation.

1. Connect 1PPS and enable Clock Regulator if not already enabled.

2. Under the "DVB-T2", "Main configuration" set the "Timestamp type" to a Relative or Ab-solute timestamp type.

− Selecting "Relative" will make the gateway stamp the DVB-T2 superframes with atransmission time, specifying only the sub second part.

− Selecting "Absloute" makes the timestamps contain both sub seconds and a secondcount.

3. Specify a "Estimated transition time" in milliseconds. This value should take into accountall delays (buffers) from the CP560 to the transmission time in the modulator. Currentsuggestion, 500 ms. (150 ms modulator processing time + 250 ms network delay + 100 msextra buffering)

Now connect two ormoremodulators to the sameCP560ASI or IP output, and have them transmitin a SFN.

10.5 Seamless SFN operationThe CP560 DVB-T2 Gateway may synchronise it’s T2-Timestamp and internal packet schedulingsuch that two different CP560’s will generate identical T2-Timestamps at the same time, giventhat they are synchronised properly. There is no need for any direct communication betweenthe units for this to function, but the units must use the same SNTP and 1PPS references. Thissynchronisation is essential when using CP560 in a Seamless SFN systemwith the T-VIPS TNS541TS Seamless Switch. See figure 10.2 for an overview of a Seamless SFN system.Perform these steps on both CP560 units in order to operate in a Seamless SFN environment forDVB-T2.

1. Connect 1PPS and enable Clock Regulator if not already enabled. This is shown in section8.4.6.

2. Set up a SNTP Time Source, see section 8.4.4. TDT and TOT may be configured, but willonly be used for alarm log and GUI time. SNTP servers are the only valid time source forthe internal time synchronization.

162 Examples of Use


DVB-T2

Gateway T2-MI

(ASI)

DVB-T2

ModulatorT2-MI

(ASI)

DVB-T2

Gateway

T2-MI

(ASI)

TNS541 TS

Seamless Switch

SNTP & 1PPS

TS

Figure 10.2 Seamless SFN system

3. Enable the output of the unit, see section 8.6.3.

4. Set the Bitrate setting to Automatic mode. This is used to reduce the number of nullpackets in the T2-MI stream to a minimum. This is required for seamless switching in theT-VIPS TNS541 TS Seamless Switch, as null packets could affect the seamless switchingoperation.

5. Disable PCR insertion, see section 8.6.4.4. Also required for seamless operation in theT-VIPS TNS541 where the PCR packets could affect the seamless switching operation.

6. Use Relative or Absolute DVB-T2 Timestamps, see section 8.6.4.1.

7. Make sure that the field Timestamp sync in section 8.6.4.1 reflects your time settings. Ifnot press the Resync button.

8. Configure your desired T2-Settings.

9. Ensure that the settings are identical on both units.

10. The reader is referred to the T-VIPS TNS541 TS Seamless Switch User’s Manual for howto set the TNS541 to T2-MI mode.

11. Connect both CP560 to the same switch on the TNS541.

Tip: Once you have configured one CP560, store you configuration file todisk and upload it to the other CP560 to ensure that they have the samesettings. See section 8.4.7 for how to do this.

10.6 Redundant system with TNS541 TS Seamless SwitchHaving connected 2 CP560’s to a TNS541, the TNS541 will select the best input. The best input isdetermined from the alarm status of each input. For example if the TNS541 loses input sync it willswitch to the other input.

Examples of Use 163


10.6.1 Signal empty PLPs

If however a CP560 loses input sync, the TNS541will not detect this in anyway. The reason for thisis that the rate of T2-MI layer is independent of the input bitrate. If a PLP is empty, i.e. containsno payload data, the T2-MI stream will therefore be unaffected.

The CP560 has an option to set the Transport Error Indicator in the Transport Stream header of theT2-MI PID if any of the PLPs are empty. If this flag is set, the TNS541 will be able to detect thisimmediately and switch away from that input. This is not however the default configuration ofthe TNS541, and the reader is referred to the TNS541 User’s Manual on how to set up switchingon Transport Error Indicator.

The option for setting the Transport Error Indicator in the CP560 is by default turned off. Seesection 8.6.4.4 for how to enable this feature.

164


Preventive Maintenance and Fault-finding 165


11 Preventive Maintenance and Fault-finding

This chapter provides the schedules and instructions, where applicable, for routine inspection,cleaning and maintenance of the CP560, to be carried out by the operator of the unit.

11.1 Preventive maintenance

11.1.1 Routine inspection

This equipment must never be used unless all the cooling fans are working. They should bechecked when the unit is switched on and periodically thereafter.

11.1.2 Cleaning

• Remove power from the unit.

• Clean the external surfaces of the CP560 with a soft cloth dampened with a mixture ofmild detergent and water.

• Make sure that the unit is completely dry before reconnecting it to a power source.

11.1.3 Servicing

Warning: Do not attempt to service this product as opening or removingcovers may expose dangerous voltages or other hazards. Refer all servicingto 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

166 Preventive Maintenance and Fault-finding


11.1.4 Warranty

The CP560 is covered by standard Nevion warranty service for a period of 24 months followingthe 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.

11.2 Fault-findingThe objective of this chapter is to provide sufficient information to enable the operator to rectifyapparent 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 toother system components.

This manual does not provide any maintenance information or procedures which would requireremoval 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 coversare removed. Only Nevion trained and approved service engineers arepermitted to service this equipment.

Caution: Unauthorised maintenance or the use of non-approved replace-ment parts may affect the equipment specification and will invalidate anywarranties.

If the following information fails to clear the abnormal condition, please contact your local reselleror Nevion customer care.

11.2.1 Preliminary checks

Always investigate the failure symptoms fully, prior to taking remedial action. The operator shouldnot remove the cover of the equipment to carry out the fault diagnosis. The following fault-findingtasks can be carried out:

• Check that the PSU LED is lit. If this is not lit, replace external equipment, power sourceand cables by substitution to check that these are not defect.

Preventive Maintenance and Fault-finding 167


• Confirm that the equipment hardware configuration is suitable for the purpose and thatthe 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, proceedto fault-finding according to the observed symptoms. If the fault persists, and cannot be rectifiedusing the instructions given in this manual, contact Nevion Customer Support. Switch off theequipment if it becomes unusable, or to protect it from further damage.

11.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?

YesThe Power LED itself is probably at fault - Call a Service Engineer.

NoProceed to next step

2. Check the Power Source.

− Connect a piece of equipment known to work to the power source outlet. Does itwork?

YesThe problem lies within the CP560 or the power cable. Proceed to next step.

NoThe problem lies with the power source. Check building circuit breakers, fuseboxes and the source outlet. Do they work? If the problem persists, contact theelectricity supplier.

3. Check Power Cable.

− Unplug the power cable and try it in another piece of equipment. Does it work?

YesThe problem lies within the CP560. Call a Service Engineer.

NoThe problem lies with the cable. Replace the cable.

The PSU does not have any internal user changeable fuses.

168


11.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 causeoverheating.

Fan fault-finding

1. Check fan rotation.

− Inspect the fans located at the sides of the unit. Are the fans rotating?

YesCheck that the unit has been installed with sufficient space allowed enclosure forair flow. If the air is too hot, additional cooling may be required

NoPossible break in the DC supply from the PSUmodule to the suspect fan(s). Calla Service Engineer.

11.3 Disposing of this equipmentDispose of this equipment safely at the end of its life time. Local codes and/or environmentalrestrictions may affect its disposal. Regulations, policies and/or environmental restrictions differthroughout the world; please contact your local jurisdiction or local authority for specific adviceon disposal.

11.4 Returning the unitBefore shipping the CP560 to Nevion, contact your local Nevion reseller or Nevion directly foradditional advice.

1. Write the following information on a tag and attach it to the CP560.

− Name and address of the owner

− Model number

− Serial number

− Description of service required or failure indication.

2. Package the CP560.

− The original shipping containers or other adequate packing containers must be beused.

3. Seal the shipping container securely, and mark it FRAGILE.

Glossary 169


Appendix A Glossary1000Base-T

The term for the electrical Gigabit Ethernet interface. This is the most common interface forGigabit Ethernet. Most Gigabit-enabled PCs and equipment support this interface.

3G-SDI3Gbit High Definition - Serial Digital Interface. 3G-SDI, consisting of a single 2.970 Gbit/sserial link, is standardized in SMPTE 424M that can replace the dual link HD-SDI.

ARPAddress Resolution Protocol. A protocol used to “resolve” IP addresses into underlying Eth-ernet MAC addresses.

ATSCAdvanced Television Systems Committee. An American organisation working with stan-dardisation of digital television broadcasts, primarily in the US but also in Asia and otherparts of the world.

DiffServDifferentiated Services. A mechanism used on layer 3 - e.g. the IP layer - to differentiatebetween traffic of various types. DiffServ is based on the ToS field and provides amechanismfor the network to give e.g. video traffic higher priority than other traffic (for example Internettraffic).

DVBDigital Video Broadcasting. The European consortium defining standards for transmissionof digital TV broadcasts, primarily in Europe.

DVB ASIDigital Video Broadcasting Asynchronous Serial Interface. A common physical interface fortransmission of MPEG2 Transport Streams (i.e. MPEG2-compressed video) over a serial in-terface, typically coaxial cables.

DWDMDenseWavelength DivisionMultiplexing. Amechanism to increase the bandwidth availablein an optical fiber by adding extra signals using different optical wavelengths (colours).

EthernetOriginally a 10Mbit/s sharedmedium network type developed by Xerox. Later transformedinto 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 1000Mbit/s. 10Gigabit/s Ethernet networks are now emerging.

FECForward Error Correction. A mechanism to protect data transmission by adding redundantinformation. Increasing the amount of redundant data will enable the receiver to correctmore errors (i.e. regenerate lost packets) in case of network data loss.

170 Glossary


HD-SDIHigh Definition - Serial Digital Interface. Also known as ANSI/SMPTE SMPTE 292M-1998.A specification describing how to digitize and transmit uncompressed high definition videosignals. The typical bit rate of an HD-SDI signal is 1485 Mbit/s.

HDTVHigh Definition Television. Television standard(s) that provide(s) improved picture resolu-tion, horisontally and vertically, giving clearer and more detailed TV pictures.

HTTPHyperText Transfer Protocol. The fundamental protocol used on the Internet for transmissionof WEB pages and other data between servers and PCs.

ICMPInternet Control Message Protocol. ICMP messages, delivered in IP packets, are used forout-of-band messages related to network operation.

IGMPInternet Group Management Protocol. IGMP is a protocol used to manage multicast on theInternet. 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, butIGMPv3 is the next step.

JPEG2000A wavelet-based image compression standard. It was created by the Joint Photographic Ex-pertsGroup committeewith the intention to supersede their original discrete cosine transform-based JPEG standard. JPEG2000 can operate at higher compression ratioswithout generatingthe characteristic ’blocky and blurry’ artifacts of the original DCT-based JPEG standard.

Meta-dataMeta-data is descriptive data that is “tagged” to a movie or audio clip. Meta-data is essentialfor the broadcaster.

MPEG-2Moving Picture Experts Group 2. The compression standard used today on most satelliteand cable TV digital broadcasts. MPEG-2 also includes standardisation of data transport ofvideo using other compression techniques, and other types of information.

MPLSMulti-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 androbustness of the transmission.

MPTSMulti Program Transport Stream. MPEG2 transport stream that carry multiple TV/Radioservices.

MulticastAn IPmechanism that allows transmission of data to multiple receivers. Amulticast can alsohave several transmit sources simultaneously. In video applications, multicast is typicallyused to distribute a video signal from a central source to multiple destinations.

Glossary 171


MXFMaterial eXchange Format is a container format for professional digital video and audio me-dia defined by a set of SMPTE standards.

NMSNetworkManagement System. A system used to supervise elements in an IP network. Whena 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.

PCRProgramClockReference. A sampled 27MHzvideo clock used inMPEG2Transport Streams.The primary purpose of the PCR is clock synchronisation of transmitter and receivers.

PIDPacket Identifier. An 11 bit field in an MPEG2 transport packet defining a logical channel.8192 unique logical channels may coexist in one network.

PSI/SIProgram Specific Information / Service Information. These are information tables (meta-data) carried in MPEG2 transport streams in addition to video and audio. The informationcarried is typically service/program IDs, program names and conditional access informa-tion.

QAMQuadrature Amplitude Modulation. A digital modulation type that is used for transmissionof digital TV signals over cable networks (e.g. DVB-C) or terrestrial networks (e.g. DVB-T).

QoSQuality of Service. A common term for a set of parameters describing the quality of an IPnetwork: Throughput, availability, delay, jitter and packet loss.

QPSKQuadrature Phase-Shift Keying. A modulation type frequently used for transmission of dig-ital TV signals.

RIP2Routing Information Protocol v2. A protocol used between network routers to exchange rout-ing tables and information.

RSVPReSerVation Protocol. A Quality-of-service oriented protocol used by network elements toreserve capacity in an IP network before a transmission session takes place.

RTPReal-time Transfer Protocol. A protocol designed for transmission of real-time data like videoand audio over IP networks.

SD-SDIStandardDefinition Serial Digital Interface. Also known asANSI/SMPTE 259M-1997 or ITU-R BT.656. A specification describing how to digitize and transmit uncompressed standarddefinition video signals. The typical bit rate of an SD-SDI signal is 270Mbit/s.

172 Glossary


SDISerial Digital Interface. Used to describe both HD-SDI and SD-SDI input and output ports.

SDPSession Description Protocol. A protocol describing multimedia communication sessions forthe purposes of session announcement, session invitation, and parameter negotiation. SDPis typically used to describe an ongoingmulticast; for example the type of compression used,IP addresses etc.

SDTISerial Data Transport Interface. A mechanism that allows transmission of various types ofdata 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 canbe used to transport other types of data.

SDTVStandard Definition Television. The normal television standard/resolution in use today.

SFPSmall Form-factor Pluggable module. A standardized mechanism to allow usage of variouselectrical or optical interfaces to provideGigabit Ethernet. Several types of SFPmodules exist:Single mode fiber modules for long-distance transmission and multi mode fiber modules forshorter distances. SFP is also known as “mini-GBIC”.

SIPSession Initiation Protocol. The Session Initiation Protocol (SIP) is an IETF-defined signalingprotocol, used for controlling multimedia communication sessions such as voice and videocalls over IP. The protocol can be used to create, modify and terminate unicast or multicastsessions consisting of one or several media streams.

SNDUSubNetwork 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 seriesof MPEG-2 Transport Stream (TS) packets and sent over a single TS logical channel.

SNMPSimple Network Management Protocol. A fundamental and simple protocol for manage-ment of network elements. Commonly used by Network Management Systems and otherapplications.

SNTPSimple Network Time Protocol is an Internet protocol used to synchronize the system clocksof computers to a time reference. It is a simplified version of the protocol NTP protocol whichis overcomplicated for many applications.

SPTSSingle ProgramTransport Stream. MPEG2Transport Stream that contains a single program/service.

Glossary 173


TCPTransmission 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 tolerantagainst network errors. TCP is the fundamental protocol used in the Internet for WEB traffic(HTTP protocol). TCP is indented for point-to-point pcommunication; TCP cannot be usedfor communication from one node to many others.

TCP/IPA common term used for the Internet protocol suite, i.e. the set of protocols needed forfundamental IP network access: TCP, IP, UDP, ARP etc.

ToSType 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 multiplexof packets, each identified by a unique Packet Identifier (PID) defining a logical channel. APID stream typically represents a video or an audio service.

UDPUser Datagram Protocol. An “unreliable” protocol above the IP layer that also provides portmultiplexing. UDP allows transmission of IP data packets to several receiving processes inthe same unit/device. UDP is used in multicast applications.

UnicastPoint-to-point connection. In this mode, a transmit node sends e.g. video data direct to aunique destination address.

VLANVirtual Local Area Network, a network of units that behave as if they are connected to thesame wire even though they may be physically located on different segments of a LAN.

WatermarkingA mechanism to “stamp” video content with unique marks, making it possible to trace theorigin of illegaly distributed content. Watermarks are invisible to the viewer.

XMLeXtensible Markup Language. A common self-describing text-based data format. Used formany purposes: Meta-data, configuration files, documents, etc. The readability of the formathas made it very popular and is now the basis of many types of WEB services.

174


Technical Specification 175


Appendix B Technical Specification

B.1 Physical details

B.1.1 Half-width version

Height 43 mm, 1UWidth 222 mm excluding fixing brackets. Two units may be sideways mounted behind a common

front panelOverall width 485 mm including fixing bracketsDepth 320 mm excluding connectorsOverall depth 340 mm including connectorsApproximate weight 2.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 CStorage temperature -20 to +70 CRelative humidity 5 % to 95 % (non-condensing)

Handling/movement Designed for fixed use when in operation

B.3 Power

B.3.1 AC Mains supply

Table B.2 AC PowerSupply Specification

Rated voltage 100-240 VACVoltage tolerance limits 85-264 VACRated frequency 50/60 HzRated current 0.7 A

Power consumption < 50 W

176 Technical Specification


B.3.2 DC supply

Table B.3 DC PowerSupply Specification

Rated voltage 48 VDCVoltage 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 cableConnector type BNC 75 Ω socketSignal Compliant with ETSI EN 50083-9 (DVB A010 rev.1)Line rate 270 Mbit/s +/- 100 ppmData rate 0.1 - 213 Mbit/sPacket length 188 or 204 bytes

Max cable length (Belden 8281 type) 300 m typical

B.4.2 Ethernet management port

Table B.6 EthernetManagement PortSpecification

Type 10/100Base-T

Connector type RJ45



B.4.3 Ethernet data port

Table B.7 EthernetData 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 approvedmodules 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.1Compatibility 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 PortSpecification

Connector type 9-pin D-sub MaleRelay rating 0.1 A max, 50 VDC maxRelay minimum load 10 µA at 10 mVDC

Reset activation time 8 seconds

178 Technical Specification


Table B.11 Alarm Relay and ResetPort Pin Out

PIN Connection

1 Relay 2 - Closed on alarm (NC)2 Relay 2 Common3 Relay 2 - Open on alarm (NO)4 Prepared for +5 V Output5 Ground6 Alarm Relay - Closed on alarm (NC)7 Alarm Relay Common8 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 interferencecharacteristics 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 Codeof 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 toelectromagnetic compatibility.

73/23/EEC of 19 February 1973 on the harmonisation of the laws of the Member States relatingto electrical equipment designed for the use within certain voltage limits.

1999/5/EC of March 1999 on radio equipment and telecommunication terminal equipment andthe 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 telecommunicationsystem”. 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 asa telecom terminal, switch or similar unit. Such kind of buffer is required to achieve a protectiveelectrical 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.

180


Forward Error Correction in IP Networks 181


Appendix C Forward Error Correction inIP Networks

The normal operational mode of the public internet is that IP packets are forwarded using a “besteffort” strategy implying that packets may occasionally be lost due to excessive load. To regulatethe transport rate of an IP session a transmitting host will at session start ramp up the speed untilthe 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 rateto 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 sincepacket delay from source to receiver resulting from re-transmission amounts to three times thenormal. 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 distortionDistortions that influence the performance of an IP video transport system, in addition to packetloss, are packet delivery time variations (jitter), and packets arriving out of order. It should benoted that a single bit error occurring within an IP packet will result in the loss of the completepacket. As IP packets and Ethernet physical link layers normally go hand in hand, IP packets willbe discarded if a single bit error occurs in transmission. The Ethernet link layer is secured with acyclic redundancy check (CRC). An Ethernet frame with bit error(s) will be discarded by the firstIP switch or router because the CRC check fails.Furthermore, multiple packetsmay be lost during short periods due to congestion. As an IP packetcontains 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

182 Forward Error Correction in IP Networks


In Figure C.1 distortions of an IP stream are visualised. The even stream of packets originatingfrom the Tx node is modified in traversing the IP network. At the input of the Rx node the IPstream 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 sizewill 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 specialmeasures are taken.

C.2 StandardisationAll since streaming of broadcast services in IP networks began the insufficient reliability of IPlinks has been an issue, and methods to improve performance have been devised. Due to lack ofstandardisation many proprietary implementations and different solutions have been put into useby equipment manufacturers. The PRO-MPEG organisation has taken the initiative to achieve acommon 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 broughtthe COP#3 and COP#4 further and COP#3 is now finalised as SMPTE 2022-1 [12] and 2022-2 [11].SMPTE 2022-1 focuses on improving IP packet loss ratio (PLR) performance using forward errorcorrection techniques.

C.3 FEC matrixSMPTE 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 theoperation it is possible to reconstruct single lost packets or a burst of lost packets. The degreeof protection may be selected to cover a wide range of link quality from low to heavy loss at theexpense 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 packetsarriving containing bit errors as packets with checksum errors are discarded at the Ethernet layer.A FECpacket containing a simple XOR-sum carried out over a number of packets at the transmitterallows the receiver to compute one lost packet by redoing the XOR process over the same packetsand comparing the results with the XOR FEC packet. This allows for the regeneration of one lostpacket in an ensemble of N payload packets plus one FEC packet. If two or more packets in theensemble are lost it is not possible to regenerate any of them. Packet loss in IP systems have atendency to come in bursts (due to congestion). Therefore the FEC XOR calculation is not done onadjacent packets; rather packets at a fixed distance are used. This can be visualised by arrangingthe packets in a two dimensional array and inserting them in rows in the same order as they aretransmitted.

http://www.videoservicesforum.org








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 XORcalculation 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 packetwhich is sent in addition to the payload packets. There will be one FEC packet associated witheach column, and it is therefore possible to regenerate as many packets as there are columns in thematrix.

In the right-most panel of Figure C.2 the case is shown where a packet in the last column positionhas been lost. The packet may then be regenerated (shown in red) by performing XOR additionover all remaining packets in that column, including the FEC packet. This is the default FECmodeof 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 combiningthe 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 eachrow. 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 betransmitted at nearly the same time as all column-FEC packets are generated when the last row ofthe matrix is being completed. Thus when transmitting the last row of payload packets the packetrate must be doubled in order to also send the FEC packets without generating extra payloadpacket delay. In itself this may cause temporary network overload with packet loss as a result.The specification [12] imposes some rules how FEC packets should be interleaved with payloadpackets to avoid excessive jitter and ensuring compatibility between equipment from differentmanufacturers. 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 matrixwith column offset

Columnoffset leads to columnFECpackets being generated at amore regular rate and it is possibleto transmit packets with a shorter delay than with a rectangular matrix. Offsetting the columnsalso increases the capability to regenerate longer bursts of lost packets; the length depending onthe 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 indicats packetslost. The figure shows that column offsetmay increase the capability to correct longer bursts of lostpackets. In this example 9 consecutive packets are lost. Even if the row length is only 7 packets, allthe 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 therow FEC packets after recovery of packets 1 through 7.



If more than one packet is lost in a row or a column of amatrix, the possibility to recover it dependson 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 4unrecoverable payload packets. However, if two of the lost packets are FEC packets, then only 2payload 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 FECmatrix sizes can in principle be chosen at will to suit the operational conditions. Operators mayeasily be confused by the number of options, and it is not straightforward to choose the optimalFEC setting for a given scenario. For compatibility reasons SMPTE 2022-1 specifies that anMPEG-2 to IP network adapter should handle a minimum matrix size of 100 IP packets, and that rowlength or column depth should not exceed 20. Also the shortest column length allowed is 4.

C.4 Transmission aspectsTheRTPprotocolmust 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 capabilityFEC data is transmitted using UDP port numbers different from that of the payload. Column FECis transmitted using port number (IP payload) + 2 and row FEC (if used) is transmitted using portnumber (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" inbetween 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 intothe 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 ofeach).

Figure C.7 illustrates the relative timing of FEC packets and payload packets. Applying an offsetcolumn structure results in a smoother packet stream. The overall packet rate will be the same inboth schemes, since the same number of FEC packets are generated, but the packets will be moreevenly spread in the IP stream. With larger matrix sizes the smoothing effect of an offset matrixwill even more pronounced. The effect of added overhead and jitter should be considered whenapplying FEC to an IP video stream in a heavily loaded network. High instantaneous packet ratesmay cause temporary overload resulting in packet loss, defeating the object of introducing FEC inthe first place.



Figure C.7 FEC data transmission

C.5 Quality of service and packet loss in IP networksOne may ask how the FEC strategy relates to an operational IP network. Little information isavailable on packet loss patterns. Measurements show that up to 1% of the packets are duplicatesand generated as a result of a retransmission request. Either because the packet has been lost orit has arrived too late. However, since these results are for TCP connections they merely serve toindicate an upper level for packet loss rate in an IP/MPLS network. Reported jitter measurementsindicate that 0.01% of the packets were delayed more than 31ms and a fraction of those packetswere delayed more than 100ms. This is also relevant for transmission of video as out-of-orderpackets 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 equipmentfault

• 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 loadon the network. Packets that do not arrive in timewill be handled as lost packets. The FEC processwill thus be able to handle occasional delay increase for a few packets and maintain a satisfactoryQuality of Service. A video gateway should offer a setting for permissible packet delay, whichshould be optimised for the operation. If the receiver buffer latency is increased it is possible toreduce 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 arenormally in the order of 1 x 10-6, but occasionally a link may become degraded showing PLRfigures like 3 x 10-3. The performance will vary over the day with the lowest performance tendingto occur at about the same time every weekday and lasting for one-half to one hour. The FECsetting should be set up to handle this peak hour with low residual loss.



The table of FigureC.8 shows the IP network performance figures tomeet the quality requirementsof various grades of television services, as given by ITU recommendation Y.1541 [13]. Along theselines the DVB IPTV standard sets the performance requirement for a 4Mbit/s IPTV service at 1visible 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 improvementSo, what does it take to make FEC improve the packet error rate of an IP network link to a levelacceptable for the application? Assuming packet loss occurs at random Figure C.9 shows how thedepth 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 networkpacket 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 toprovide distribution of a 3Mb/s transport stream with less that 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 class6 and 7 however, column-only FEC with reasonably small column depths will perform nicely forbit 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 requirednetwork bandwidth.

Figure C.10 Error improvement using two-dimensional FEC

Figure C.10 shows how adding row FEC dramatically increases performance in high packet lossnetworks. Reverting to the previous case, a 3Mbit/s video transport stream in an IP network withworst hour PLR of 3x10-3, a service with less than 10 error hits per day may be provided usingany of the matrix sizes shown. In less error-prone networks however, using two-dimensional FECschemes may be overkill and generate unneccessary FEC overhead.

C.7 Latency and overheadLatency 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 arectangular matrix, however, all FEC packets are generated nearly at the same time, as indicatedin Figure C.7. FEC packets should be spread in transmission to avoid introducing extra jitter. Thisalso contributes to latency in error packet recovery. In the receiver all packets involved in the FECcalculation must be collected before a missing packet can be recovered. Figure C.11 shows howdifferentmatrix sizes result in different latencies and required buffer sizes, using column-only FECprocessing.



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 FECpacket 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%. Theminimum 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 thelatency or buffer size requirement. Applying row- and column-FEC also enables use of iterativeFEC calculations to recover more missing packets. The equipment manufacturer is at liberty todetermine the algorithm used in error recovery as long as the requirements and limitations of thespecification are respected.

190


Quality of Service, Setting Packet Priority 191


Appendix D Quality of Service, SettingPacket Priority

Normal IP routing is by best effort. This does not work well for broadcast television as the videoand audio components need to be transported as a continuous flowof packetswithout interferencefrom 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 MPLSIn networks running MPLS, the packets are forwarded along a predefined path from an ingressrouter to an egress router. Packet switching is then done according to the label and packets will beswitched expediently. TheMPLS label is added to the IP packet by the ingress router and removedby the egress router. The labelling is done on the basis of packet classification.

D.2 Layer 3 routingAn alternative technique to improve QoS is to use layer 3 routing and give video content packetshigher priority than other data. IP packets are put into queues according to their priority. Packetswith high priority are forwarded expediently and have a lower probability of being discarded dueto buffer overflow.There are twoways to prioritise IP packets; usingDifferentiated services (Diff-serve) or precedencebits (TOS). Both these methods use the same bits in the IP header and both of them are in commonuse.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 prioritisationmay also be combinedwithMPLSwhere layer 3 routing is used in the aggre-gation network and MPLS in the core network. The DSCP priority setting may be used for MPLStagging.

192 Quality of Service, Setting Packet Priority


D.2.1 CP560 configuration

The number entered into the Type of service (TOS) field in CP560 IP TX configuration menudefines all 8 bits. The value used should be in accordance with traffic engineering policy of thenetwork and should be in the range from 0 to 255.

D.3 Layer 2 priorityPrioritisation can also be supported in layer 2 using VLAN tags. The 802.1q VLAN tag has 3 bitsfor setting the Class of Service (COS). The operation is further defined in [7]. The COS bits willbe handled the same ways as Diff-serve or precedence bits regarding packet classification in thenetwork.

D.3.1 CP560 configuration

The COS priority is entered in the VLAN configuration page in the CP560 IP TX configurationmenu, in the field named VLAN Priority. A value in the range from 0 to 7 should be inserted. Thisvalue 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.

Validation of DVB-T2 Parameters 193


Appendix E Validation of DVB-T2 Para-meters

This chapter lists data used for DVB-T2 parameter validations.

E.1 T2-FrameThe following validations applies to the T2-Frame structure.

E.1.1 T2-Base

Tables E.1 and E.2 shows which Pilot Patterns that are allowed for a given combination of FFT andGuard Interval. For table cells without any Pilot Patterns, the combination of FFT size and Guardinterval is not allowed.

Table E.1 SISO: Valid Pilot Patterns for combinations of FFT size and Guard Interval

1/32 1/16 1/8 1/4 1/128 19/128 19/256

32k PP4,PP6 PP2,PP4,PP8 PP2,PP8 PP7 PP2,PP8 PP2,PP4,PP816k PP4,PP6,PP7 PP2,PP4,PP5,PP8 PP2,PP3,PP8 PP1,PP8 PP7 PP2,PP3,PP8 PP2,PP4,PP5,PP88k PP4,PP7 PP4,PP5,PP8 PP2,PP3,PP8 PP1 PP7 PP2,PP3,PP8 PP4,PP5,PP84k PP4,PP7 PP4,PP5 PP2,PP3 PP12k PP4,PP7 PP4,PP5 PP2,PP3 PP1

1k PP4,PP5 PP2,PP3 PP1

Table E.2 MISO: Valid Pilot Patterns for combinations of FFT sizeand Guard Interval

1/32 1/16 1/8 1/4 1/128 19/128 19/256

32k PP4,PP8 PP2,PP8 PP4,PP6,PP8 PP2,PP816k PP4,PP5,PP8 PP3,PP8 PP1,PP8 PP4,PP5,PP8 PP1,PP8 PP3,PP88k PP4,PP5,PP8 PP3,PP8 PP1 PP4,PP5,PP8 PP1,PP8 PP3,PP84k PP4,PP5 PP3 PP12k PP4,PP5 PP3 PP1

1k PP3 PP1

194 Validation of DVB-T2 Parameters


E.1.2 T2-Lite

Tables E.3 and E.4 shows which Pilot Patterns that are allowed for a given combination of FFT andGuard Interval. For table cells without any Pilot Patterns, the combination of FFT size and Guardinterval is not allowed.For T2-Lite FFT sizes 32k and 1k is not allowed, and thus have no allowed Pilot Patterns. Also,Pilot Pattern 8 is not allowed for any mode.

Table E.3 SISO: Valid Pilot Patterns for combinations of FFTsize and Guard Interval

1/32 1/16 1/8 1/4 1/128 19/128 19/256

32k16k PP6,PP7 PP4,PP5 PP2,PP3 PP1 PP7 PP2,PP3 PP2,PP4,PP58k PP4,PP7 PP4,PP5 PP2,PP3 PP1 PP7 PP2,PP3 PP4,PP54k PP4,PP7 PP4,PP5 PP2,PP3 PP12k PP4,PP7 PP4,PP5 PP2,PP3 PP1

1k

Table E.4 MISO: Valid Pilot Patterns for combina-tions of FFT size and Guard Interval

1/32 1/16 1/8 1/4 1/128 19/128 19/256

32k16k PP4 PP3 PP1 PP4,PP5 PP1 PP38k PP4,PP5 PP3 PP1 PP4,PP5 PP1 PP34k PP4,PP5 PP3 PP12k PP4,PP5 PP3 PP1

1k

E.2 Physical Layer PipeThe following validations applies to each Physical Layer Pipe (PLP).The availability of FEC Code Rates for each PLP depends of the selection of the T2-Base or T2-Liteprofile as follows. An xmarks a valid mode.

Table E.5 Valid FECCode Rates for each PLP

1/3 2/5 1/2 3/5 2/3 3/4 4/5 5/6

T2-Base X X X X X X

T2-Lite X X X X X X

Estimated Transmission Time 195


Appendix F Estimated Transmission TimeThe value input in the Estimated Transmission Time (ETT) field in the T2-Gateway defines an up-per limit for the transmission delay in the whole network. The transmission delay is defined fromthe CP560 output until the signal is emitted on air. The ETT therefore needs to be large enough toaccount for the network delay between the CP560 and the T2-modulator and the processing delayrequired in the modulator. For an SFNwith several modulators the ETT needs to be set accordingto the largest network delay. Keep in mind that IP networks will jitter, and worse case jitter alsoneeds to be accounted for in the Estimated Transmission Time.

The CP560 generates a T2-MI stream which carries a DVB-T2 timestamp. The DVB-T2 timestampdefines the transmission time for when the first bit of the T2 Super Frame of the pertaining T2-signal is to be emitted. The modulator then needs to compare the DVB-T2 timestamp with itsexternal reference to calculate the remaining time until the signal is to be emitted on air. For moreinformation on the DVB-T2 timestamp, have a look at chapter 5.2.7 of [9]: ETSI EN 102 773.

F.1 How the CP560 uses the configured ETT valueWhen the CP560 starts building a T2 Super Frame, it samples and stores the phase of the currentexternal reference (1PPS). The ETT is then added to this value, and then entered into the DVB-T2timestamp. The ETT has no other implications in the CP560 besides being added to the currenttime.

F.1.1 Example with 2 modulators

1. CP560 starts building a T2 Super Frame. External 1PPS is sampled at T2 Super Framestart to 200 ms.

2. ETT is defined by the user to 450 ms.

3. DVB-T2 timestamp set to 200+450 = 650 ms for the T2-Super Frame

4. T2-MI signal transmitted to Modulator1 over a link with a total delay of 350 ms. Mod-ulator1 compares the DVB-T2 timestamp (650 ms) with the external reference (currently200+350 ms) and finds that the given signal should be emitted in 100 ms.

5. T2-MI signal transmitted to Modulator2 over a link with a total delay of 300 ms. Mod-ulator2 compares the DVB-T2 timestamp (650 ms) with the external reference (currently200+300 ms) and finds that the given signal should be emitted in 150 ms.

F.2 Implications of adjusting ETTIf the ETT is set larger than the actual network delay the modulators needs to buffer the T2-MIstream until the transmission time. The signal is delayed more than necessary.

If the ETT is set less than the actual network delay there is an error, and the outcomes are as follows:

196 Estimated Transmission Time


• Absolute timestamp: The modulator will not transmit since the transmission time is inthe past.

• Relative timestamp: The modulator will not notice that the transmission time is in thepast since the Relative timestampwraps every second. Themodulator will transmit if stillwithin buffer requirements, and destroy the SFN if any of the other modulator receivedthe signal prior to transmission time.

F.3 How to set ETT

1. Estimate the total network delay from the CP560 to each modulator in an SFN region. Re-member to account for possible jitter in your network, especially if using IP transmission.

2. Find the required processing delay for each modulator. Should be stated somewhere bythe modulator manufacturers.

3. Calculate required transmission delay for each network and modulator.

4. Set ETT to the highest transmission delay found under point 3, and add some extra delayfor safety.

Alternatively a more practical approach may be applied:

1. Start with a high ETT, and reduce this number until the first modulator breaks down.This will be the largest transmission delay for your SFN region.

2. Set ETT to the highest transmission delay found under point 1, and add some extra delayfor safety.

Alarms 197


Appendix G AlarmsThe CP560 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 eachlevel is also indicated by a colour on the alarm severity indicator:

Table G.1 Alarm severity levels

Severity Level Colour

Notification 2 BlueWarning 3 YellowMinor 4 AmberMajor 5 Orange

Critical 6 Red

In addition it is possible to set an alarm to filtered, so that there will be no alarm events generatedfor this alarm.

The WEB interface gives the most detailed alarm information as all active alarms and warningsare listed with time of occurrence

The unit sends an SNMP trap message to all registered trap receivers when an alarm conditionarises. A critical alarmwill have severity level 6 and aNotification will have severity level 2. Whenthe 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 thesame time the alarm relay will be set to alarm state.

Table G.3 shows the possible alarms that can be signalled by the CP560. For each alarm type,essential information is presented. The different fields are described in Table G.2.

198 Alarms


Table G.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 alarmnumber always maps to a specific alarm.

Text A short text describing the alarmDescription A longer text describing the cause of the alarmDef. severity The default severity of the alarmType 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 clearevents are expected.

Subid2 This field is present if the Subid2 value of the alarm type is used. The text in the table describes theusage 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 theusage of the Subid3 value.

Alarms 199


Table G.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 istransmitted.

Type: Port

Clear event: Yes

Subid3: “IP Dest”

108 Destination hostname unresolved Warning Description: Unable to DNS resolve hostname specified as destination.

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 theavailable 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 FECengine 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 engineenabled 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 indicatesthat 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 numberfield.

Type: Port

Clear event: Yes

151 No data received Critical Description: No data received on Ethernet input for stream. See details field on alarm fordescription.

Type: Port

Clear event: Yes

200 Alarms


Table G.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 receivedout of order and the buffer was not large enough. Also, if running FEC, theFEC 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 expectedformat.

Type: Port

Clear event: Yes

157 Too low latency for FEC Warning Description: The preferred latency is set lower than the latency required to fully utilize thecurrent FEC. Increase Receive buffer size to resolve.

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

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 201


Table G.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 lostsynchronization).

Type: System

Clear event: Yes

201 Lost GPS 1PPS sync. Critical Description: The clock synchronization mechanism has been resynchronized due to toolarge 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: Yes

505 Config changed Note Description: A modification has been made to the configuration of the device.

Type: System

Clear event: No

202 Alarms


Table G.3.d Alarms


506 Unable to switch Warning Description: The relay controller is unable to switch because the spare input is notsufficiently 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 manuallyconfirmed 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, thealarm 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 forSW 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 detailsfield 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

529 Timesync error Major Description: Not able to synchronize internal time to external time references.

Type: System

Clear event: Yes

Alarms 203


Table G.3.e Alarms


530 Leap second changed Note Description: Leap second changed

Type: System

Clear event: No

531 JBRC SNMP manager creation failed Warning Description: Joint bit rate controller failed to create an SNMP manager

Type: Undetermined

Clear event: Yes

532 JBRC setting rate mode failed Warning Description: Joint bit rate controller failed to select manual bit rate mode on source device

Type: Undetermined

Clear event: Yes

533 JBRC setting bit rate failed Warning Description: Joint bit rate controller failed to setbit rate mode on source device

Type: Undetermined

Clear event: Yes

534 JBRC bit rate set on source device Note Description: Joint bit rate controller successfuly set the bit rate on the source device

Type: Undetermined

Clear event: Yes

535 Alarm log almost full Note Description: Alarm log almost full, overwrite of older alarms will take place

Type: System

Clear event: No

536 Heartbeat trap Note Description: Heartbeat to signal the system is still functional

Type: System

Clear event: No

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 inpercentage of present PIDs that can have an event (sum of detected anddisappeared, or number of C errors) before alarm is set. Other detailed alarmssuch as CC errors are filtered while TS unstable is active. Alarm is also set iftoo many PIDs are present.

Type: Port

Clear event: Yes

1110 No sync Critical Description: No valid ASI 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 290v1.2.1.

Type: Port

Clear event: Yes

204 Alarms


Table G.3.f Alarms


1132 PAT invalid table ID Warning Description: Unable to find section with table_id 0x00 on PID 0. Part of test 1.3 in ETSITR 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 290v1.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 furtherPSI decoding.

Type: Port

Clear event: Yes

1140 CC error Warning Description: The Continuity Counter in the TS header was not as expected. Shouldincrease by 1 for each packet with the Payload bit set, and not increase ifnot. Typically caused by lost TS packets. See test 1.4 in ETSI TR 101 290v1.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 thePAT 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. Theperiod is configured using the PID Event alarm. See test 1.6 in ETSI TR 101290 v1.2.1.

Type: Port

Clear event: Yes

Subid3: “PID”

1161 PIDs disappeared Note Description: This alarm is set when PIDs are timed out. The timeout can be specified perPID. Timeouts specified affec the PID Error alarm also.

Type: Port

Clear event: No

Subid3: “PID”

Alarms 205


Table G.3.g Alarms


1508 TS packets dropped Major Description: Incoming TS Packets are dropped.

Type: Port

Clear event: Yes

Subid3: “Idx”

1509 Output muted Warning Description: The output has been shut down by the output mute controller based onconfigured criterias.

Type: Port

Clear event: Yes

1510 Output overflow Critical Description: The total bit rate of the ASI input stream is too high.

Type: Port

Clear event: Yes

1542 MIP size error Warning Description: There is not enough space in the MIP packet for all configured transmitterfunction loops.

Type: Port

Clear event: Yes

1543 MIP Inserter time reference problem Warning Description: MIP Inserter time reference problem.

Type: Port

Clear event: Yes

1544 ETR 290 Pri 2 error Warning Description: Setting Transport Error Indicator in PAT to trigger ETR290 Pri 2 error.

Type: Port

Clear event: Yes

1545 Empty PLP Major Description: PLP is not receiving data. Empty PLP being output.

Type: Port

Clear event: Yes

Subid3: “Idx”

1801 TS-ID incorrect Ok Description: The TS-ID of the incoming stream does not match the TS-ID of theconfigured CSI section. For modes where the input TS-ID is not known, theTS-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 aremonitored, 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 aremonitored, and the min rate must be set per PID.

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

206 Alarms


Table G.3.h Alarms


1813 TS rate too low Ok Description: TS bitrate is lower than set limit.

Type: Port

Clear event: Yes

References 207


Appendix H 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 andmodulation for digital terrestrial television.

[5]ETSI TS 101 191. Digital Video Broadcasting (DVB); DVB mega-frame for Single FrequencyNetwork (SFN) synchronisation.

[6]ETR 154Digital Video Broadcasting (DVB); ImplementationGuidelines for theUse ofMPEG-2 Systems, Video andAudio in Satellite and Cable BroadcastingApplications. ETSI TechnicalReport ETR 154, European Telecommunications Standards Institute ETSI.

[7]IEEE 802.1Q-2005 802.1QTM, Standards for Local and metropolitan area networks, VirtualBridged Local Area Networks

[8]Draft ETSI EN 302 755; Digital Video Broadcasting (DVB); Frame structure channel codingand modulation for a second generation digital terrestrial television broadcasting system(DVB-T2)

[9]Draft ETSI EN 102 773; Digital Video Broadcasting (DVB); Modulator Interface (T2-MI) for asecond generation digital terrestrial television broadcasting system (DVB-T2)

[10]DVB Document A150; Digital Video Broadcasting (DVB); Structure and modulation of op-tional transmitter signatures (T2-TX-SIG) for use with the DVB-T2 second generation digitalterrestrial television broadcasting system

[11]SMPTE2022-2-2007: Unidirectional Transport of Constant Bit-RateMPEG-2Transport Streamson IP Networks

208


[12]SMPTE 2022-1-2007: Forward Error Correction for Real-time Video/Audio Transport over IPNetworks

[13]ITU-T Y.1541 (02/2006) Series Y: Global Information Infrastructure, Internet Protocol Aspectsand Next-Generation Networks: Internet protocol aspects; Quality of service and networkperformance. Network performance objectives for IP-based Services

[14]Pro-MPEG Forum: Pro-MPEG Code of Practice #3 release 2, July 2004: Transmission of Pro-fessional MPEG-2 Transport Streams over IP Networks

[15]Pro-MPEG Forum: Pro-MPEG Code of Practice #4 release 1, July 2004: Transmission of HighBit Rate Studio Streams over IP Networks

[16]J. Rosenberg, H. Schulzrinne, IETF RFC2733, December 1999: An RTP Payload Format forGeneric Forward Error Correction

Date post:	22-Mar-2021
Category:	Documents
Upload:	others
View:	9 times
Download:	1 times

CP560 DVB-T2 Gateway User's Manual · 2020. 3. 4. · E ValidationofDVB-T2Parameters 193 E.1...

Documents