Demodulator-UMN - MCX7000 Multi-Carrier Satellite Gateway - R1.0 - v1.0 PDF

MCX7000
User Manual
MCX7000 Multi-Carrier Satellite Gateway
R1.0
V1.0
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Table of Contents
1 Copyright ............................................................................................................. 1
2 EU Compliancy Statements ............................................................................... 2

2.1 Radio and Telecommunications Terminal Equipment (R&TTE) Directive 1999/5/EC ................................. 2
2.2 EMC Information .......................................................................................................................................... 3
2.3 Restriction of Hazardous Substances Directive (RoHS) (Directive 2011/65/EU) ....................................... 3
2.4 Registration, Evaluation and Authorization of Chemicals (REACH) ............................................................ 4
2.5 WEEE – Waste Electrical and Electronic Equipment Directive ................................................................... 5
3 Care Packs .......................................................................................................... 6
4 Safety Regulations ............................................................................................. 7

4.1 Environmental ............................................................................................................................................. 9
4.2 Rack Mounting Instructions ......................................................................................................................... 9
5 Options .............................................................................................................. 10
6 Feedback ........................................................................................................... 14
7 About this Manual ............................................................................................ 15

7.1 Cautions and Symbols .............................................................................................................................. 17
7.2 Version History and Applicability ............................................................................................................... 18
7.3 Related Documentation ............................................................................................................................. 18
8 Introduction ....................................................................................................... 19
8.1 Delivering the Highest Uptime for Vital Links ............................................................................................. 19
8.2 Get the Best Performance and Lower Your Costs ..................................................................................... 19
8.3 Evolve Towards Tomorrow's Technology .................................................................................................. 20
9 Back Panel Description .................................................................................... 21

9.1 Power Connector ....................................................................................................................................... 22
9.2 Craft Interface ............................................................................................................................................ 23
9.3 Alarm Interface .......................................................................................................................................... 25
10 How to Use the Front Panel ........................................................................... 27

10.1 Navigating Through the Display .............................................................................................................. 27
10.2 Front Panel Buttons Description .............................................................................................................. 28
10.3 Root Menu Pane ...................................................................................................................................... 29
Newtec Proprietary V1.0
Confidentiality: Unrestricted
10.4 Tree Menu Pane ...................................................................................................................................... 30

10.5 LED Status Indicators .............................................................................................................................. 31
10.6 Commonly Used Parameters ................................................................................................................... 32
10.6.1 Modulator ........................................................................................................................................... 32
10.6.1.1 Transmit On/Off ........................................................................................................................... 32
10.6.1.2 Set the Output Frequency ........................................................................................................... 32
10.6.1.3 Set Output Level ......................................................................................................................... 33
10.6.1.4 Set the Symbol Rate (Tx) ............................................................................................................ 33
10.6.2 Management ...................................................................................................................................... 34
10.6.2.1 Set the Management IP Address ................................................................................................ 34
10.6.2.2 Set the Gateway IP Address ....................................................................................................... 34
10.6.2.3 Change the Access Level ........................................................................................................... 35
10.6.3 Configurations .................................................................................................................................... 36
10.6.3.1 Load a Configuration ................................................................................................................... 36
10.6.3.2 Save a Configuration ................................................................................................................... 36
10.6.4 Check the Alarms ............................................................................................................................... 37
11 How to Use the Command Line Interface (CLI) ........................................... 38

11.1 How to Access the CLI ............................................................................................................................. 38
11.2 Open the CLI Using a Terminal Emulator ................................................................................................. 40
11.3 Log In as Expert ...................................................................................................................................... 41
11.4 Navigate Through the Branches of the Device ....................................................................................... 41
11.5 Go into a Branch ...................................................................................................................................... 41
11.6 Move Up One Level ................................................................................................................................. 42
11.7 Return to the Main Branch ....................................................................................................................... 42
11.8 Show, Help and Context Sensitive Help .................................................................................................. 43
11.8.1 Show .................................................................................................................................................. 43
11.8.2 Help .................................................................................................................................................... 44
11.8.3 Context Sensitive Help "?" ................................................................................................................. 44
11.9 Supported Key Presses in the CLI ........................................................................................................... 45
11.10 Displayed Units ..................................................................................................................................... 47
11.11 Get and Set Parameter Values ............................................................................................................. 47
11.12 Software Upgrade (CLI) ......................................................................................................................... 48
11.13 Dynamic Tables ..................................................................................................................................... 48
11.13.1 Show Tables .................................................................................................................................... 49
11.13.2 Change Parameters in a Table ........................................................................................................ 49
11.13.3 Add a New Row to a Table ............................................................................................................... 49
11.13.4 Delete a Row from a Table ............................................................................................................... 50
12 SNMP ............................................................................................................... 51
13 How to Use the Graphical User Interface ..................................................... 52

13.1 Opening the GUI ..................................................................................................................................... 52
13.2 User Profiles ............................................................................................................................................ 54
13.2.1 Guest Profile ...................................................................................................................................... 54
13.2.2 Operator Profile ................................................................................................................................. 54
13.2.3 Expert Profile ..................................................................................................................................... 54
13.2.4 Switch User Profile ............................................................................................................................. 55
13.3 Change a Password ................................................................................................................................ 56
13.4 GUI Pane Description .............................................................................................................................. 57
13.4.1 Banner ............................................................................................................................................... 59
13.4.2 Overview Tab ..................................................................................................................................... 61
13.4.3 Tree View ........................................................................................................................................... 64
13.4.4 Alarms Pane ....................................................................................................................................... 65
13.4.5 Status Bar .......................................................................................................................................... 66
13.5 Colors Used in the GUI ............................................................................................................................ 67
13.6 Parameters in the GUI ............................................................................................................................. 69
13.7 Update or Configure Parameters in a Table ............................................................................................ 71
13.8 Invalid Values .......................................................................................................................................... 72
14 Device Security ............................................................................................... 73

14.1 Switch User Profile .................................................................................................................................. 73
14.2 Access Control ......................................................................................................................................... 74
15 General Configuration Principles ................................................................. 76

15.1 Introduction .............................................................................................................................................. 76
15.2 Device Data Path ..................................................................................................................................... 76
15.3 Data Handling Blocks and Instances ....................................................................................................... 78
15.4 Viewing Instances ................................................................................................................................... 78
15.5 Creating and Deleting Instances ............................................................................................................. 79
15.6 Instance Naming ...................................................................................................................................... 80
15.7 Connecting Instances to Form the Data Path .......................................................................................... 80
15.8 TS Connections and Stream Path ........................................................................................................... 81
15.9 Full Data Path .......................................................................................................................................... 81
16 Configure the Physical Interfaces ................................................................. 82

16.1 Device Management ............................................................................................................................... 82
16.1.1 Configure Device Redundancy .......................................................................................................... 83
16.1.2 Configure the Device Location ........................................................................................................... 85
16.1.3 Check the Operator Identification ...................................................................................................... 86
16.1.4 Device Identification ........................................................................................................................... 87
16.1.4.1 License Type ............................................................................................................................... 89

16.1.4.2 Check the Installed Device Options ............................................................................................ 92
16.1.5 Reference Clock ................................................................................................................................ 93
16.2 Configure the Management Interfaces .................................................................................................... 95
16.2.1 Management Ethernet Physical Link ................................................................................................. 96
16.2.2 Ethernet Link Redundancy ................................................................................................................. 99
16.2.3 Alarm Status Tables ......................................................................................................................... 102
16.2.4 Management IP Connectivity ........................................................................................................... 103
16.2.4.1 Configure the Mgmt Routing Table ........................................................................................... 105
16.3 Configure the Data Interfaces ................................................................................................................ 107
16.3.1 Physical Link .................................................................................................................................... 108
16.3.2 Data Ethernet Link Redundancy ...................................................................................................... 110
16.3.3 VLAN Link ........................................................................................................................................ 112
16.3.4 Statistics ........................................................................................................................................... 114
16.3.5 Data IP Connectivity ......................................................................................................................... 114
16.3.5.1 Data IP Address ........................................................................................................................ 114
16.3.5.2 Virtual IP Address ..................................................................................................................... 116
16.3.5.3 IGMP Version ............................................................................................................................ 118
16.3.5.4 Configure the Multicast IP Address ........................................................................................... 119
16.3.5.5 Configure the Routing Table ..................................................................................................... 121
16.4 Configure the ASI Interfaces ................................................................................................................. 125
16.5 Configure the Modulator Interfaces ....................................................................................................... 126
16.5.1 Configure the 10 MHz BUC Reference ............................................................................................ 126
16.5.2 Configure the Converter ................................................................................................................... 127
16.6 Select the Demodulator Connectors ..................................................................................................... 129
16.6.1 Configure the Demodulator Connectors .......................................................................................... 129
16.6.2 Configure the Demodulator Converter ............................................................................................. 131
17 Quick Configuration Templates .................................................................. 133

17.1 Introduction ............................................................................................................................................ 133
17.2 Template A1. Single Stream Modulator - ASI ........................................................................................ 134
17.3 Template A2. Single Stream Modulator TS over IP ............................................................................... 136
17.4 Template B Single Stream Demodulator ............................................................................................... 137
17.5 Template C1. Single Stream Modem ASI .............................................................................................. 139
17.6 Template C2. Single Stream Modem TSoIP .......................................................................................... 140
17.7 Template D1. Multistream Modulator ASI .............................................................................................. 140
17.8 Template D2. Multistream Modulator TSoIP .......................................................................................... 142
17.9 Template E. Multistream Demodulator .................................................................................................. 142
17.10 Template F1. Multistream Modem ASI ................................................................................................ 143
17.11 Template F2. Multistream Modem TSoIP ............................................................................................ 144
17.12 Template G. Single Stream Multi-Demodulator ................................................................................... 145

17.13 Template H. Multistream Multi-Demodulator ....................................................................................... 146
17.14 Template I. Single Stream 1M2D ......................................................................................................... 146
18 Configure the Functional Blocks ................................................................ 147

18.1 Introduction ............................................................................................................................................ 147
18.2 Block Diagram Single Stream Modulator ............................................................................................... 149
18.2.1 Configure the ASI Input Streams ..................................................................................................... 150
18.2.1.1 ASI Monitoring Table ................................................................................................................. 153
18.2.1.2 Alarm Status Table ................................................................................................................... 153
18.2.2 Configure TS over IP Input Streams ................................................................................................ 154
18.2.2.1 Add a TS over IP Input Stream .................................................................................................. 156
18.2.2.2 Monitoring Table ....................................................................................................................... 158
18.2.2.3 TS over IP In Alarm Status Table ............................................................................................. 159
18.2.3 Configure TS Redundancy ............................................................................................................... 160
18.2.4 Configure the TS Connections ......................................................................................................... 164
18.2.4.1 TS Stream Overview ................................................................................................................. 166
18.2.4.2 Delete a Connection .................................................................................................................. 167
18.2.5 Modulator ......................................................................................................................................... 168
18.2.5.1 Modulator ConfigurationTable ................................................................................................... 168
18.2.5.2 DVB-S Specific Settings ........................................................................................................... 171
18.2.5.2.1 Modulation and Coding ...................................................................................................... 171
18.2.5.3 DVB-S2 / S2 Extensions Specific Settings ................................................................................ 172
18.2.5.4 Transmit Control ........................................................................................................................ 174
18.2.5.5 DSNG Profiles Configuration Table ........................................................................................... 176
18.2.5.6 DVB-CID Configuration Table ................................................................................................... 179
18.2.5.6.1 Device Global Unique ID ..................................................................................................... 179
18.2.5.6.2 Device Variable Parameters ............................................................................................... 179
18.2.5.6.3 How does it Work? .............................................................................................................. 180
18.2.5.6.4 What to do when Interference is Detected? ........................................................................ 181
18.2.5.7 Modulator Alarms Status Table ................................................................................................. 182
18.3 Block Diagram Single Stream Demodulator ........................................................................................... 184
18.3.1 Demodulator .................................................................................................................................... 186
18.3.1.1 Demodulator Configuration Table ............................................................................................. 188
18.3.1.2 Backup Carrier .......................................................................................................................... 190
18.3.1.2.1 Configure the Backup Carrier ............................................................................................. 192
18.3.1.2.2 Make the Backup Carrier Permanent .................................................................................. 193
18.3.1.3 Demodulator Monitoring ............................................................................................................ 194
18.3.1.3.1 Monitoring Parameters ....................................................................................................... 194
18.3.1.3.2 DVB-S2 Monitoring Table ................................................................................................... 196
18.3.1.3.3 MODCOD Statistics ............................................................................................................ 198

18.3.1.4 Demodulator Alarm Status Table .............................................................................................. 200
18.3.2 TS Redundancy ............................................................................................................................... 201
18.3.3 Configure the ASI Output Interfaces ................................................................................................ 201
18.3.3.1 Monitoring the ASI Output Interfaces ........................................................................................ 202
18.3.3.2 ASI Output Alarm Status Table ................................................................................................. 202
18.3.4 Configure the TS over IP Out Interfaces .......................................................................................... 203
18.3.4.1 Add a TS over IP Output Interface ............................................................................................. 204
18.3.4.2 TS over IP Output Monitoring Table .......................................................................................... 206
18.3.4.3 TS over IP Output Alarm Status Table ...................................................................................... 207
18.3.4.4 Delete a TS over IP Output Interface ......................................................................................... 207
18.3.5 Connections ..................................................................................................................................... 207
18.4 Block Diagram Multistream Modulator ................................................................................................... 214
18.4.1 Configure the ASI Input Streams ..................................................................................................... 217
18.4.1.1 ASI Monitoring Table ................................................................................................................. 220
18.4.1.2 Alarm Status Table ................................................................................................................... 220
18.4.2 Configure TS over IP Input Streams ................................................................................................ 221
18.4.2.1 Add a TS over IP Input Stream .................................................................................................. 223
18.4.2.2 Monitoring Table ....................................................................................................................... 225
18.4.2.3 TS over IP In Alarm Status Table ............................................................................................. 226
18.4.3 Configure TS Redundancy ............................................................................................................... 227
18.4.4 Configure the Modulator ................................................................................................................... 231
18.4.5 Configure the Multistream Output .................................................................................................... 231
18.4.5.1 Configure the DVB-S2 Parameters per Stream ......................................................................... 233
18.4.5.2 Multistream Output Alarm Status Table .................................................................................... 234
18.4.7 Configure the TS over IP Output Interfaces ..................................................................................... 237
18.4.7.3 TS over IP Output Alarms ......................................................................................................... 241
18.4.8 TS Connections ............................................................................................................................... 242
18.4.8.1 Configure the TS Connections .................................................................................................. 242
18.4.8.1.1 Add a Connection ............................................................................................................... 243
18.4.8.1.2 TS Stream Overview ........................................................................................................... 244
18.4.8.1.3 Delete a Connection ........................................................................................................... 246
18.5 Block Diagram Multistream Demodulator .............................................................................................. 247

18.5.1 Demodulator .................................................................................................................................... 249
18.5.2 Multistream Input ............................................................................................................................. 249
18.5.2.1 Multistream Configuration Table ............................................................................................... 249
18.5.2.1.1 Add a New Input Stream ..................................................................................................... 249
18.5.2.1.2 View the Configuration Parameters per Input Stream ........................................................ 251
18.5.2.1.3 Delete an Input Stream ....................................................................................................... 254
18.5.2.2 Monitoring the Inputs ................................................................................................................. 254
18.5.2.3 Multistream Input Alarm Status Table ....................................................................................... 256
18.5.4 Configure the TS over IP Output Interfaces ..................................................................................... 259
18.5.4.3 TS over IP Output Alarms ......................................................................................................... 263
18.5.5 Configure the TS Connections ......................................................................................................... 264
18.5.5.1 Add a Connection ...................................................................................................................... 265
18.6 Block Diagram Multistream and Multicarrier Setup ............................................................................... 269
19 Configure the Input Processing Blocks ..................................................... 271

19.1 TS Generator ......................................................................................................................................... 271
19.2 MPE Decapsulation ............................................................................................................................... 274
19.2.1 Configure MPE Decapsulation ......................................................................................................... 274
19.2.2 Select the TS to Extract MPE Data .................................................................................................. 276
19.2.3 Select the Programs ......................................................................................................................... 277
19.2.4 Select the Channels ......................................................................................................................... 278
20 Configure the Output Processing Blocks .................................................. 279

20.1 Basic Interoperable Scrambling System (BISS) .................................................................................... 279
20.1.1 Content Scrambling Modes ............................................................................................................. 279
20.1.1.1 Standard Mode ......................................................................................................................... 279
20.1.1.2 Raw Mode ................................................................................................................................. 280
20.1.2 Key Management System ................................................................................................................ 280
20.1.2.1 Odd/Even key ............................................................................................................................ 280
20.1.2.2 Key Management System Structure ......................................................................................... 281
20.1.2.3 Distribution of Clear Session Words over a Secure Channel .................................................... 281
20.1.2.4 Distribution of Encrypted Session Words over a Non-Secure Channel ..................................... 283
20.1.2.5 Compute Encrypted Session Words ......................................................................................... 285
20.1.3 Defining BISS Keys .......................................................................................................................... 287
20.1.4 Creating a BISS Scrambler .............................................................................................................. 290
20.1.5 Changing BISS Scrambling Parameters .......................................................................................... 291
20.1.6 Deleting Keys ................................................................................................................................... 292
20.1.7 Viewing the Buried Identifier ............................................................................................................ 293
20.1.8 Seamless Key (Session Word) Change ........................................................................................... 293
20.1.9 Scrambling Monitoring Parameters .................................................................................................. 294
20.1.10 Possible Alarms ............................................................................................................................. 294
20.1.11 Operation of BISS .......................................................................................................................... 295
20.1.11.1 Setting a Key for Transmission ............................................................................................... 295
20.1.11.2 Setting an Encrypted Session Word for Transmission ............................................................ 295
20.1.11.3 Changing Keys Seamlessly ..................................................................................................... 296
20.1.11.4 Removing a Receiver from the Network .................................................................................. 296
20.1.11.5 Setting up a Secure BISS Network ......................................................................................... 296
20.1.11.6 Creating Groups of Receivers ................................................................................................. 296
20.1.12 Keys and Redundancy, Backup or Import ..................................................................................... 297
20.1.12.1 BISS and Redundancy ........................................................................................................... 297
20.1.12.2 Backup a Configuration ........................................................................................................... 297
20.1.12.3 Import a Configuration ............................................................................................................. 298
20.1.12.4 Editing the Setup ID ................................................................................................................ 298
20.1.12.5 Erasing the SetupID ................................................................................................................ 299
20.2 Rate Adapter ......................................................................................................................................... 300
20.3 NIT Carrier ID ........................................................................................................................................ 304
20.4 Program-Specific Information (PSI-SI) Insertion .................................................................................... 306
20.4.1 Configuration Table ......................................................................................................................... 307
20.4.2 Alarm Status Table .......................................................................................................................... 308
20.5 MPE Encapsulation ............................................................................................................................... 309
20.5.1 Configure MPE Encapsulation ......................................................................................................... 310
20.5.1.1 Select the TS to add MPE Data ................................................................................................ 312
20.5.1.2 Configure the Programs Table .................................................................................................. 313
20.5.1.3 Configure the Channels Table .................................................................................................. 315
20.5.1.4 Traffic Shaping .......................................................................................................................... 316
21 Configure the Remote In-band Management Feature ............................... 319

21.1 Remote In-band Management Setup .................................................................................................... 320
21.2 Encapsulate the Mgmt IP Traffic ........................................................................................................... 321
21.3 Decapsulate the Mgmt IP Traffic ........................................................................................................... 322
22 Configure the Probes ................................................................................... 323

22.1 TS Analyzer ........................................................................................................................................... 323
22.1.1 Error PID Table ................................................................................................................................ 325
22.1.2 PCR PID Table ................................................................................................................................. 326
22.1.3 PID Table ......................................................................................................................................... 327
22.1.4 NIT Carrier ID Table ......................................................................................................................... 328
22.1.5 TS Analyzer Alarms Status Overview .............................................................................................. 328
22.2 PRBS Probe .......................................................................................................................................... 330
23 Tasks .............................................................................................................. 333

23.1 Device Tasks ......................................................................................................................................... 333
23.1.1 Configurations .................................................................................................................................. 333
23.1.1.1 Configuration File ...................................................................................................................... 334
23.1.1.2 Active Configuration .................................................................................................................. 336
23.1.1.3 Saved Configuration ................................................................................................................. 336
23.1.1.4 Save a Configuration ................................................................................................................. 337
23.1.1.5 Import a Configuration ............................................................................................................... 337
23.1.1.6 Load a Configuration ................................................................................................................. 338
23.1.1.7 Export a Configuration ............................................................................................................... 339
23.1.1.8 Delete a Configuration ............................................................................................................... 340
23.1.1.9 Make a Configuration File Bootable .......................................................................................... 341
23.1.2 Configuration Templates .................................................................................................................. 342
23.1.3 Reset the Device ............................................................................................................................. 343
23.1.4 DSNG Profiles .................................................................................................................................. 344
23.1.4.1 DSNG Profiles Import ................................................................................................................ 344
23.1.4.2 DSNG Profiles Export ................................................................................................................ 344
23.1.5 Auto Save Configuration .................................................................................................................. 345
23.2 Toolbox .................................................................................................................................................. 346
23.2.1 Diagnostics Report ........................................................................................................................... 346
23.3 Maintenance .......................................................................................................................................... 348
23.3.1 Software Upgrade ............................................................................................................................ 348
23.3.1.1 Software Upgrade Procedure ................................................................................................... 348
23.3.2 License File ..................................................................................................................................... 350
23.3.2.1 License Upgrade ....................................................................................................................... 350
23.4 Logging .................................................................................................................................................. 352
23.4.1 Syslog Filter ..................................................................................................................................... 354
23.4.2 Export or Clear Logging ................................................................................................................... 355
23.4.3 Interpretation of a Device Log File ................................................................................................... 356
23.5 Equalink® 3 ........................................................................................................................................... 357
23.6 Documentation ...................................................................................................................................... 359
23.6.1 Open the Reference Manual ............................................................................................................ 359

23.6.2 Download the SNMP MIB Files ........................................................................................................ 360
24 Alarm Handling ............................................................................................. 361

24.1 Alarm Masking ....................................................................................................................................... 362
24.2 Alarm Configuration ............................................................................................................................... 364
24.3 Clear Alarm Counters ............................................................................................................................ 365
25 Appendix - Configuring the Output Rate Mode ......................................... 366

25.1 Output Rate Mode Auto (ISSY) ............................................................................................................. 366
25.1.1 ISSY for Transport Stream Bitrate Recovery ................................................................................... 366
25.2 Output Rate Mode User Defined ............................................................................................................ 367
25.2.1 Output Rate Type - User Defined ..................................................................................................... 367
25.2.2 Control Loop Type [None, NTC, DVB] ............................................................................................. 368
25.2.3 Buffer Delay and Maximum Buffer Delay ......................................................................................... 369
25.2.4 Buffer Alarms ................................................................................................................................... 370
26 Appendix - Specifications ............................................................................ 371

26.1 Data Interfaces ...................................................................................................................................... 371
26.2 Content Encryption and Protection ....................................................................................................... 371
26.3 IP Encapsulation ................................................................................................................................... 371
26.4 IP Decapsulation ................................................................................................................................... 372
26.5 Modulation and Demodulation .............................................................................................................. 372
26.6 Modulation Interfaces ............................................................................................................................ 375
26.7 Demodulation Interfaces ....................................................................................................................... 377
26.8 Internal 10 MHz Reference Frequency ................................................................................................. 377
26.9 Generic .................................................................................................................................................. 378
26.10 Physical ............................................................................................................................................... 378
26.11 Demodulation Performances ............................................................................................................... 379
26.11.1 DVB-S2 Performance .................................................................................................................... 379
26.11.1.1 DVB-S2 Performance (FER<1E-5) Normal Frames/Pilots Off ................................................ 379
26.11.1.2 DVB-S2 Performance (FER<1E-5) Normal Frames/Pilots On ................................................ 380
26.11.1.3 DVB-S2 Performance (FER<1E-5) Short Frames/Pilots Off ................................................... 381
26.11.1.4 DVB-S2 Performance (FER<1E-5) Short Frames/Pilots On ................................................... 382
26.11.2 DVB-S2X Performance .................................................................................................................. 383
26.11.2.1 DVB-S2X Performance (FER<1E-5) Normal Frames/Pilots Off .............................................. 383
26.11.2.2 DVB-S2X Performance (FER<1E-5) Normal Frames/Pilots On .............................................. 386
26.11.2.3 DVB-S2X Performance (FER<1E-5) Short Frames/Pilots Off ................................................ 389
26.11.2.4 DVB-S2X Performance (FER<1E-5) Short Frames/Pilots On ................................................ 391
27 Appendix - Classification Expressions ...................................................... 393

27.1 Example Expressions ............................................................................................................................ 395
28 Appendix - DSNG Profiles Preconfigured Settings ................................... 396

28.1 DSNG Profiles Preconfigured Settings .................................................................................................. 396
28.2 ISOG-News3 Profile .............................................................................................................................. 396
29 Appendix - IP Handling ................................................................................ 400

29.1 IP Packet Reception on an Interface ..................................................................................................... 400
30 Appendix - Back Panel Combinations ........................................................ 401

30.1 Example Combinations ......................................................................................................................... 403
30.1.1 Single TSoIP Modulator ................................................................................................................... 403
30.1.2 Single ASI Modulator ....................................................................................................................... 403
30.1.3 Single TSoIP Modem ....................................................................................................................... 404
30.1.4 Single ASI Modem ........................................................................................................................... 404
30.1.5 Modulator and Dual ASI Demodulator ............................................................................................. 405
30.1.6 Modem + Dual TSoIP Demodulator ................................................................................................. 405
30.1.7 Multi Demodulator ............................................................................................................................ 406
31 Appendix - Acronyms ................................................................................... 407
Copyright MCX7000 Multi-Carrier Satellite Gateway
1 Copyright
© October 8, 2015
The material contained in this document is confidential and intended for use only by parties
authorized by Newtec Cy N.V.
All Rights Reserved. No part of this document may be photocopied, reproduced, stored in a retrieval
system, or transmitted, in any form or by any means whether, electronic, mechanical, or otherwise
without the prior written permission of:
Newtec Cy N.V.
Laarstraat 5
9100 Sint-Niklaas, Belgium
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49
www.newtec.eu
sales@newtec.eu
Confidentiality: Unrestricted 1/409

EU Compliancy Statements MCX7000 Multi-Carrier Satellite Gateway
2 EU Compliancy Statements
2.1 Radio and Telecommunications Terminal Equipment

(R&TTE) Directive 1999/5/EC
We,
Declare that the following product:

• Product number: MCX7000
• Type identifier: NTC/2353
to which this declaration relates is in conformity with the essential requirements of European Union
Directive 1999/5/EC Radio and Telecommunication Terminal Equipment Directive Essential
Requirement 3.1(a), 3.1 (b), 3.2.
Done at St-Niklaas, on October 8, 2015.
Serge Van Herck,

CEO
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium.
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49

2.2 EMC Information

Relevant EMC information (to FCC rules)
This equipment has been tested and was found to comply with the limits for a class A digital device,
pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and radiates radio frequency energy. If not installed and used in
accordance with the instruction manual, it may cause harmful interference to radio communications.
Note that, if coaxial cables are connected to the ASI-type interfaces, these cables
must be double shielded in order to keep the installation compliant with FCC rules.
Do not operate this equipment in a residential area, as it is likely to cause harmful interference.
When this is the case, you will be required to correct the interference at your own expense.
2.3 Restriction of Hazardous Substances Directive (RoHS)

(Directive 2011/65/EU)
The undersigned hereby confirms the following statement:
We hereby declare that this equipment is compliant to the RoHS Directive 2011/65/EU.
Done at St-Niklaas, on October 8, 2015 .
Serge Van Herck,

CEO
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49

2.4 Registration, Evaluation and Authorization of Chemicals

(REACH)
European Regulation N°1907/2006 "REACH" (Registration, Evaluation, and Authorization of
Chemicals), came into force on June 1st, 2007. It aims at regulating the use of the chemical
substances within the European Union.
We are committed to meeting our legal obligations under REACH, as a manufacturer of articles and
as a downstream user of chemicals products.
In order to comply with the REACH regulation, Newtec Cy N.V. has put into place processes and
procedures to ensure implementation and compliance with the regulation, especially the assessment
of the presence of Substances of Very High Concern (SVHC's) and communication along the supply
chain to both suppliers and customers.
All products manufactured by Newtec Cy N.V. fall under the category of Articles within the REACH
Regulation and none of them present the notion of intentional release of SVHC's, therefore no
obligation of registration applies.
Serge Van Herck,

CEO
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49

2.5 WEEE – Waste Electrical and Electronic Equipment

Directive
The undersigned hereby confirms the following statement:
We hereby declare that this equipment is compliant to the WEEE Directive 2012/19/EU.
Serge Van Herck,

CEO
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium.
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49

Care Packs MCX7000 Multi-Carrier Satellite Gateway
3 Care Packs
Newtec Care Pack support services package protects your Newtec equipment during a three year
period, compared to the standard one year warranty period. This extended warranty covers
hardware repair services at Newtec factory and grants you access to Newtec technical support as
well as maintenance software releases.
Care Pack Basic is the good choice for basic support of non-critical systems or systems designed
with full redundancy giving you priority access to technical support from Newtec regional support
centers during local business hours. Care Pack Basic covers hardware repair services at Newtec
factory and maintenance software releases.
Care Pack Enhanced includes access to the major software releases (including non-licensed new
features) and assistance for software upgrade. Care Pack Enhanced is advised for optimizing
system performance and extending equipment lifecycle but also for supporting systems where
technical support response and factory repair turnaround need to be sharp.
Care Pack is proposed as a default service option. However you can opt for customized
maintenance and support services with the Framework Support Agreement adapted to your
Business needs.
When not opting for any Care Pack, the equipment will be granted a standard warranty and the
support requests related to this equipment will be handled on a reasonable effort basis.
To register your care pack, refer to http://www.newtec.eu/support/care-pack/.
Use the Newtec Service Desk tool to receive more information.

> Browse to https://customersupport.newtec.eu.
> Fill in your Username and Password
> Create a ticket
As response of your request you will receive appropriate feedback from our support
team.
In case you don't have a Username and Password yet for the Newtec Service Desk
tool: request a login to customersupport@newtec.eu.

Safety Regulations MCX7000 Multi-Carrier Satellite Gateway
4 Safety Regulations
Please read this chapter before you install and use this equipment.
To ensure your safety, the equipment has been designed to comply with the following safety
standards:
Safety of Information Technology Equipment.

• IEC 60950-1:2006/A11:2009/A1:2010/A12:2011
• EN 60950-1:2006/A11:2009/A1:2010/A12:2011
• UL 60950-1, Second Edition
• CSA C22.2 N°. 60950-1-07.Second Edition
Before you start to install and operate the device, please make sure you observe the following
points:
• The equipment described in this manual is designed to be used by properly trained personnel
only. Only qualified personnel who are aware of hazards involved may adjust, maintain and repair
the exposed equipment.
No operator serviceable parts inside. Refer servicing to qualified personnel.

To prevent electrical shock, do not remove covers.
• To use the equipment correctly and safely, it is essential that both operating and servicing
personnel follow generally accepted safety procedures in addition to the safety precautions
specified in this manual. Warning and caution statements and/or symbols are marked on the
equipment when necessary. Whenever it is likely that safety protection is impaired, immediately
switch off the equipment and secure it against unintended operation. Inform the appropriate
servicing authority about the problem. For example, safety is likely to be impaired if the
equipment fails to perform the intended measurements or shows visible damage.
• The only way to shut down the device is to disconnect the power cable from the power
connector. Therefore make sure that the power cable is accessible and not obstructed when the
device is operational. For more information please refer to section: Power Connector.

Additional safety requirements for Finland, Norway and Sweden

Telecommunication connections and cable distribution system.
Special conditions apply to the use of this equipment in Finland, Sweden and Norway
due to different earthing arrangements in these countries. Therefore it is essential that
the installation is done by authorized personnel and according to the national
requirements only.
This equipment is specified for use in a restricted access location only, where
equipotential bonding has been applied and which has provision for a permanently
connected protective earthing conductor.
A protective earthing conductor must be installed by a Service Person.
Additional safety requirements for Norway and Sweden

Equipment connected to the protective earthing of the building installation through the
mains connection or through other equipment with a connection to protective earthing
- and to a cable distribution system using coaxial cable, may in some circumstances
create a fire hazard. Connection to a cable distribution system has therefore to be
provided through a device providing electrical isolation below a certain frequency
range (galvanic isolator, see EN 60728-11)."
NOTE: In Norway, due to regulation for installations of cable distribution systems, and
in Sweden, a galvanic isolator shall provide electrical insulation below 5 MHz. The
insulation shall withstand a dielectric strength of 1,5 kV r.m.s., 50 Hz or 60 Hz, for 1
min.
Translation to Norwegian:
Utstyr som er koplet til beskyttelsesjord via nettplugg og/eller via annet jordtilkoplet
utstyr - og er tilkoplet et kabel-TV nett, kan forårsake brannfare. For å unngå dette
skal det ved tilkopling av utstyret til kabel-TV nettet installeres en galvanisk isolator
mellom utstyret og kabel-TV nettet.
Translation to Swedish:
"Utrustning som är kopplad till skyddsjord via jordat vägguttag och/eller via annan
utrustning och samtidigt är kopplad till kabel-TV nät kan i vissa fall medfõra risk fõr
brand. Fõr att undvika detta skall vid anslutning av utrustningen till kabel-TV nät
galvanisk isolator finnas mellan utrustningen och kabel-TV nätet."

4.1 Environmental
Operating the equipment in an environment other than that stated in the specifications also
invalidates the safety compliance.
Do not use the equipment in an environment in which the unit is exposed to:
• Unpressurized altitudes higher than 2000 meters
• Extreme temperatures outside the stated operating range operating
temperature range 0 to + 50°C
• Excessive dust
• Moist or humid atmosphere above 85% RH
• Excessive vibration
• Flammable gases
• Corrosive or explosive atmospheres
• Direct sunlight
Use a slightly damp cloth to clean the casing of the equipment. Do not use any
cleaning liquids containing alcohol, methylated spirit or ammonia, etc.
4.2 Rack Mounting Instructions

• Elevated Operating ambient - If installed in a closed or multi-unit rack assembly, the operating
ambient temperature of the rack environment may be greater than room ambient. Therefore,
consideration should be given to installing the equipment in an environment compatible with the
maximum ambient temperature (Tma) specified by the manufacturer. 50°C.
• Reduced Air Flow - Installation of the equipment in a rack should be such that the amount of air
flow required for safe operation of the equipment is not compromized.
• Mechanical Loading - Mounting of the equipment in the rack should be such that a hazardous
condition is not achieved due to uneven mechanical loading.
• Circuit Overloading - Consideration should be given to the connection of the equipment to the
supply circuit and the effect that overloading of the circuits might have on overcurrent protection
and supply wiring. Appropriate consideration of equipment nameplate ratings should be used
when addressing this concern.
• Reliable earthing - Reliable earthing of rack-mounted equipment should be maintained. Particular
attention should be given to supply connections other than direct connections to the branch
circuit (e.g. use of power strips).

Options MCX7000 Multi-Carrier Satellite Gateway
5 Options
Newtec MCX7000 Ordering nr.
Configuration Options MCX7000

Category
Select 1 option
Hardware Platform Chassis Type 05 (7000) CH-05
Select 1 option
Operating Software MCX7000 Major Software R1.0* MS-10
Select 1 option
Mains Power Supply PSU Single AC 110/240V PS-00

Unit
PSU Dual Redundant AC 110/240 V PS-01
Select 1 option
Data/Video Video TS, Carrier-ID(NIT), TS Analyzer* VP-01

Package
Video TS, Demod only* VP-02
Select 1 option
Video Interface GbE TSoIP, SMPTE-2022 DEC (req. VI-01

VP-01/VP-02)*
GbE TSoIP + ASI(6) (req. VP-01/VP-02 and VI-02

HS-05)
ASI (6 connectors) (req. VP-01/VP-02 and HS-05) AS-02
select max. 1 option
Slot 1 Demodulator Cl.3 HS-02
Slot 2 Demodulator Cl.3 HS-04
Slot 3 ASI board HS-05
Demodulator Cl.3 HS-07

Modulator licenses No modulator license ML-00
One modulator license ML-01
No demodulator board license DL-00

Demodulator
One demodulator board license DL-01
board licenses
Two demodulator board licenses DL-02
Three demodulator board licenses DL-03
For a modem or modulator, select 1 option
L-band with switchable 10 MHz output* OU-00

Modulator Output
Interface IF (50-180 MHz)* OU-01
IF+ L-band with switchable 10 MHz out* OU-02
DVB-S Q/8PSK* SC-01
Modulation Standard DVB-S/S2 QPSK* SC-02

and Coding
DVB-S/S2/S2X Q/8PSK* SC-03
(includes
multistream support) DVB-S/S2/S2X Q/8PSK 16QAM 16APSK* SC-04
DVB-S/S2/S2X Q/8PSK 16QAM 16/32APSK* SC-05
DVB-S/S2/S2X Q/8PSK 16QAM 16/32/64/128/256* SC-06
Modulation Symbol Rate 5 Mbaud* SR-01

Modulation
Maximum Modulation Symbol Rate 36 Mbaud* SR-03
Symbol Rates
Modulation Symbol Rate 133 MBaud* SR-06

For a modem or demodulator, select max 1 option
Demodulator DVB-S/S2/S2X Q/8PSK 16QAM 16/32APSK* DC-01

Standard and Coding
(includes DVB-S/S2/S2X up to 256PSK*
DC-02
multistream
support)
For a modem or demodulator, select 1 option
Demodulation DVB-S/S2/S2X Q/8PSK 16QAM 16/32APSK* DR-01

Maximum Symbol
Rates DVB-S/S2/S2X up to 256PSK* DR-02
Select 1 option
Internal Reference Standard 10 MHz IR-00

Clock
Very High Stability 10 MHz IR-02
Additional Options
Category
Max. 1 option per category
Reference Clock 10 MHz Reference Output (BNC) RO-01

Output
Pre-distortion Equalink® 3 * (1 license) AE-01
MPE Insertion MPE Data insertion in TS (req. VP-01)* VM-01
Encryption BISS (0-1-E) Single TS (Req. VP-01)* CA-01
Services Category
Support Care Pack 3 Basic GA-08
Care Pack 3 Enhanced GA-09
(*) Selectable via license key

Please contact your sales representative for details.

sales@newtec.eu

Feedback MCX7000 Multi-Carrier Satellite Gateway
6 Feedback
Newtec encourages your comments concerning this document. We are committed to providing
documentation that meets your needs.
Please send any comments by contacting us at documentation@newtec.eu.
You can access myNewtec from the Newtec website: http://www.newtec.eu/
Simply click on the Login button available on the toolbar at the top right-hand side of your screen
and enter your login credentials.
Please include document and any comment, error found or suggestion for improvement you have
regarding this document.

About this Manual MCX7000 Multi-Carrier Satellite Gateway
7 About this Manual

This document is intended to help you to:
• Understand the possibilities of the MCX7000.
• Understand the features of the MCX7000.
• Find your way connecting and configuring the MCX7000.
The manual is built up around the graphical user interface and the major blocks that are displayed in
there.
You may scroll through the manual in chronological order when configuring the device.
• Install the hardware (back panel).
• Set the management IP Address (via the front panel).
• Get familiar with the user interface and the principles of device configurations.
• Configure the physical interfaces so that the MCX7000 can communicate with source and
receiving devices such as video MUX, Encoders, on ASI level and IP Level.
• Use the available configuration templates to perform a quick configuration.
• Configure the Functional Blocks, the sections in this chapter zoom in on the basic setups that
can be configured with this device.
The setups are displayed by a block diagram and then explained step by step.
Establish links between inputs and outputs.
• Once a basic setup is created, configure the input and output processing blocks.
Configure BISS, Rate Adaptation, PSI/SI insertion, activation NIT Carrier ID and MPE
Encapsulation and Decapsulation, if applicable.
• Configure the transport stream analyzer to detect possible problems that exist in the transport
stream.
This feature allows the user to troubleshoot the problem and take immediate action (for example
by contacting the head end).
• Use the tasks pane to manage the configurations, to perform maintenance and device logging
and create diagnostics reports.
More advanced users can start Equalink calibration and download the MIBs for SNMP
configuration.
The manual informs when parameters or configuration blocks are only visible for expert users, see
chapter User Profiles on page 54 for more information.
This is done in two ways:
• Mentioned explicitly, Log In as Expert.
• In a table the parameters are indicated in Italic.
(For Example, in the following table: Auto Negotiation, Advertised Speeds and MTU are only
visible when logged in as expert user).

Parameter Description
Interface Indicates the name of the physical interface.
Enable Enable or disable the interface.
MAC Address Indicates the MAC address for the Ethernet

management interface.
Auto Negotiation Enable or disable the auto negotiation.

It is recommended to enable this setting.
When disabled, the management device must be
configured with the same advertised speed. (If this is not
the case the communication is not guaranteed.)
Advertised Speeds • All, this is the default value and recommended in

combination with auto negotiation.
• Select a forced speed incase of auto negotiation is
disabled.
Link State Indicates the currently used speed to perform the

communication or link down when the link is inactive.
MTU Enter the Maximum Transmission Unit.

By default this is 1500.
The maximum value is 9582 which allows to use jumbo
frames.
Newtec recommends to use the operator profile when configuring or maintaining a

device.
Log in as expert when fine tuning of the MCX7000 is needed.

7.1 Cautions and Symbols

The following symbols appear in this manual:
A caution message indicates a hazardous situation that, if not avoided, may result in
minor or moderate injury. It may also refer to a procedure or practice that, if not
correctly followed, could result in equipment damage or destruction.
A hint message indicates information for the proper operation of your equipment,
including helpful hints, shortcuts or important reminders.
A reference message is used to direct to a location in a document with related document

or a web-link.

7.2 Version History and Applicability
Document Date Subject Comment

Version
1.0 October 2015 MCX7000 Initial version
7.3 Related Documentation

• The MCX7000 Reference Manual describes the parameters available in the device.
• Device leaflet containing the specifications (We refer to http://www.newtec.eu).
• The System Integration Guide for MCX7000 describes how to integrate the device into a network
management environment.

Introduction MCX7000 Multi-Carrier Satellite Gateway
8 Introduction
Building upon the MDM6100 Broadcast Satellite Modem software suite, the enhanced hardware
platform of the MCX7000 extends the modem capabilities beyond single carrier support. In a first
release, three 133 Mbaud carriers can be demodulated, next to modulation of a 133 Mbaud signal
with full support of the DVB satellite standards up to DVB-S2X. Each and every transport stream
embedded in one of the received carriers can be output on one of the six (optional) ASI or dual
Ethernet ports. The same data interfaces can be used as input ports for the modulator.
Transmodulation of a received stream is also an option. Its remote in-band management and
software upgradeability makes it the receiver equipment of choice for remote unattended towers and
headends. Subsequent releases of this future-proof DVB-S2X platform guarantee, by simple
software upgrade, even increased functionality and higher density.
8.1 Delivering the Highest Uptime for Vital Links

Uptime and reliability are essential in the design of the Multicarrier gateway, taking a vital role in the
satellite network. Input source redundancy and the shortest redundancy switch-over times, operating
both in 1+1 and N+1 topologies, are setting the standard in our industry.
Advanced capabilities are built in such as a MPEG Transport Stream analyzer, support of SMPTE
2022 FEC at the GbE inputs (for distributed IP headends), and native support of Carrier ID according
to the new DVB standard as well as in the transport stream NIT Table. Special care was taken to
cope with jittery transport stream over IP inputs.
The 6 ASI ports are programmable as inputs or outputs allowing for monitoring as well as operational
ASI ports.
8.2 Get the Best Performance and Lower Your Costs

The MCX7000 Multicarrier Satellite Gateway performs among the best, offering unmatched
bandwidth efficiency optimization options, thereby lowering overall Total Cost of Ownership. The fully
automated operation of Newtec´s field-proven Equalink 3 predistortion technology is now available
for any satellite transmission application providing up to 15% bandwidth gain in DVB-S2(X) 8PSK
mode in single carrier per transponder constellations. Clean Channel Technology, in combination
with DVB-S2X, improve satellite efficiency by up to 15%, thereby enabling much smaller carrier
spacing. Maximum symbol rates up to 133 Mbaud and modulations up to 256APSK (DVB-S2X
standard) combined with VCM (Variable Coding and Modulation) allow for maximum throughput in
large contribution links. Up to 8 transport streams are supported in both directions over the
redundant GbE ports. On top of this, another 6 transport streams can be routed in either direction
over the optional 6 ASI ports. The streams received from up to 3 satellite carriers can be sent to any
of the ASI or GbE ports. The MCX7000 Multicarrier Satellite Gateway can be easily monitored and
controlled via a comprehensive front panel menu, advanced web GUI as well as via SNMP protocol.
This enables easy integration into any industry-standard EMS/NMS system. Its bidirectional remote
in-band management and software upgradeability makes it the receiver equipment of choice for
remote unattended towers and headends.

Introduction MCX7000 Multi-Carrier Satellite Gateway
8.3 Evolve Towards Tomorrow's Technology

Built upon flexible and latest generation programmable technology, the MCX7000 Multicarrier
Satellite Gateway is a future-proof building block that lets any satellite network evolve to the next
level of capabilities. A scalable, pay-as-you-grow, licensing and software upgrade mechanism
facilitates the launch of new services, or last minute network design changes, without rebuilding the
entire network infrastructure. Migration from ASI to GbE and IF to L-band is facilitated by simple
in-field installation of license keys. Migration of standard distribution links towards the new DVB-S2X
standard can be as simple as inserting an MCX7000 Multicarrier Satellite Gateway in the head-ends
while keeping the installed base of IRDs. Featured modulator technologies such as Equalink® 3
linear and non-linear predistortion and Clean Channel Technology bring best in-class output
spectrum, enhancing the satellite link margin and throughput to its optimum. The non-linear post
compensation in the receivers brings extra link margin when in uplink limited Multicarrier per
transponder constellation.

Back Panel Description MCX7000 Multi-Carrier Satellite Gateway
9 Back Panel Description

The following figure shows the possible connections on the MCX7000. The back panel connections
available depend on the specific hardware configuration of your device.
The maximum force that may be used to fix the SMA (L-Band monitor OUT) connector
is restricted to 1.2Nm! The maximum force for the other connectors is restricted to
1Nm!
When one of these limits is exceeded, the connectors can be damaged and the
correct functioning of the connectors cannot be guaranteed.
The following figure serves as an example to get an overview on the specifications of

the connectors.
The combination of connectors and modules displayed might deviate from your
particular combination.
Please refer to Appendix - Back Panel Combinations on page 401 to get an overview on
the possible back panel combinations.
The following back panel applies to a configuration with ordering options:
Power Supply
• PS-01
Modulator Demodulator
• HS-01 • HS-02
• HS-04
ASI Connectors Reference Clock Output

• AS-02 • RO-01

9.1 Power Connector

This connector has a protective earthing incorporated.
Insert the mains plug only in a socket that has a protective earth contact.
Any interruption of the protective conductor inside or outside the device causes
hazards or electrical shocks.
The only way to shut down the device is to disconnect the power cable from the
power connector. Therefore, make sure that the power cable is accessible and not
obstructed when the device is operational.
The power supply has the following specifications: 90-130 & 180-260 Vac, 260 VA, 47-63 Hz.
To have power redundancy, a dual power supply can be ordered (sales option:. PS-01).
• It is advisable to connect the two mains plugs to two different power circuits, so the device
remains operational if one of these circuits fails (for example: fuse blown).
The equipment with redundant power supply has more than one power supply cord.
To reduce the risk of electric shock, disconnect two power supply cords before
servicing.

9.2 Craft Interface

The craft interface is a SUBD 9 pin connector interface that can be used to manage the device using
the command line interface (CLI). For more information please refer to section:
How to Use the Command Line Interface (CLI) on page 38.
It is used to control the device over RS232.

The line settings for the craft interface are:
• Speed 115200 baud
• Eight data bits
• No parity bit
• One stop bit
Use the following pin connections to create a crossover cable between the MCX7000
Multi-Carrier Satellite Gateway and the managing device.
Pin Name Function
1 Not connected
2 Rx-D Receive Data
3 Tx-D Transmit Data
4 Not connected
5 GND Shield ground
6 Not connected
7 Not connected
8 Not connected
9 Not connected

The following figure shows the craft interface connection.

9.3 Alarm Interface

The alarm interface can be used to build up device redundancy switching systems.
When using a Universal Redundancy Switch it is not mandatory to use alarm

contacts. The Universal Redundancy Switch can also gather the alarm status from the
different pieces of equipment in the setup over the management interface. To enable
device redundancy please refer to section: Configure Device Redundancy on page 83 .
Connect the alarm interfaces.

The contacts are normally closed to insure that an alarm is generated when the alarm cables are
removed.
Refer to the following figures for the pin layout:
Pin Layout Technical Representation of the Pin Layout

The following figure shows how to connect the alarm cables in a 1+1 redundancy system.

How to Use the Front Panel MCX7000 Multi-Carrier Satellite Gateway
10 How to Use the Front Panel

This section explains how the devices can be configured using the front panel.
The following figure shows the navigation buttons, indicators and connectors to the front panel.
10.1 Navigating Through the Display

The display is divided horizontally into two regions in a matrix:
• Root Menu Pane: Displays the branches of the device.

• Menu Tree Pane: Displays the current location, the sub branches and/or parameters that exist
under the selected branch or sub branch.

10.2 Front Panel Buttons Description

The following figure displays the different control buttons of the front panel.
The following table describes the buttons displayed in the previous figure.
Name/Symbol Description
Arrow UP Navigate to the upper item.
Arrow DOWN Navigate to the lower item.
Arrow LEFT Fold an expanded branch or a leaf sub item.
Arrow RIGHT Unfold a collapsed branch.
OK Depending on the position it has the following function:

• Branch: Expand
• Leaf: Open a parameter
• Confirm a new value
ESC • Fold an expanded branch

• Discard a new value
Soft Buttons • Navigate through the root menu (arrows)

• Select a main branch from the root menu

10.3 Root Menu Pane

This pane represents a list of the available branches.
It is presented at the bottom of the display in a horizontal way.
For example the following main menus:
• Mgmt Itf
• Dataitf
• TSoIPin
• TSoIPout
A branch is associated with one (or more) soft-button(s). This depends on the size and the position
relative to the soft buttons.
When more than one branch is available the first and last soft button are used as arrows.
Refer to the following figure:
To select or navigate in the root menu it is possible to do one of the following:
» Press the soft button that is associated with the required menu.
» Use these arrows (soft buttons) to navigate to the required menu and press OK
(on the navigation button).

10.4 Tree Menu Pane

• The first row of the tree menu indicates the current location in the device.
For example:
MCX7000 > Device> Identification
• A selectable item in the tree menu pane is visualized with a dark background.
The following table describes the icons that are used by the tree menu pane.
Icons Description
Indicates a branch that contains no sub branches.
All parameters exist directly under this branch.
Folded mode.
Unfolded mode.
Indicates an action. (For example: Save).
Scroll bar
Indicates that more than one line exists under this selection.
Indicates a read only parameter.
In this pane, the parameters are listed vertically.
» Navigate through this pane by using the up/down arrow of the navigation buttons.
» Unfold a branch by using the right arrow or pressing OK.
» Fold a branch by using the left arrow or pressing ESC.

10.5 LED Status Indicators
LED LED Color Description
Red A general device or interface alarm is present on the device.

ACT Yellow Alarms other than the general device alarm or interface alarm are
ALARM present on the device.
Green There are no alarms present on the device.
MEM Yellow A memorized alarm is present on the device.

ALARM
Off Indicates that all alarms are cleared, no memorized alarm is present
on the device.
TEST Green Indicates that the internal PRBS generator is activated on the
device.
Off The internal PRBS generator is not activated on the device.
Tx ON Green The device is transmitting.
Off The transmission is disabled.
Rx LOCK Green All demodulators are fully locked.
Yellow At least one of the active demodulators is in PL lock (Physical Layer

lock).
• Physical layer headers are decoded properly.
• An Es/No estimation is available.
• Equalizer is operational.
But no decodable BB frame was received.
Red At least one of the active demodulators cannot lock.
Off All available demodulators are disabled.
DATA Green The incoming or outgoing data signal is valid.

(ASI and
Yellow The incoming / outgoing data is configured but there is no activity
Ethernet
monitored during the last second.
Interfaces)
Red Indicates an interface alarm.
Off The input and output interfaces are not enabled.

10.6 Commonly Used Parameters
10.6.1 Modulator
10.6.1.1 Transmit On/Off
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Transmit
Proceed as follows:
» Select Modulator using the corresponding Soft Button
» Select Configuration
» Select Configuration Table
» Navigate to Transmit
» Click OK
» Select On/Off
» Click OK
10.6.1.2 Set the Output Frequency
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Output Frequency
Proceed as follows:
» Navigate to Output Frequency
» Click OK
New value is displayed, indicating the current position by a blinking number.
» Insert the new value using the corresponding Soft Buttons
» Click OK
» The new value is displayed on the front panel

10.6.1.3 Set Output Level
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Output Level
Proceed as follows:
» Navigate to Output Level
» Click OK
» Use the Soft Buttons, to step up or down until the correct output level is reached
» Click OK
10.6.1.4 Set the Symbol Rate (Tx)
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Symbol Rate
Proceed as follows:
» Navigate to Symbol Rate
» Click OK
» Click OK

10.6.2 Management
10.6.2.1 Set the Management IP Address
Navigate to:
MCX7000 >>Mgmt Itf >> Mgmt (x) >> IP Address
Proceed as follows:
» Select Mgmt Itf using the corresponding Soft button

» Select Mgmt (x)
» Select IP Address
» Click OK
» Click OK
10.6.2.2 Set the Gateway IP Address
Navigate to:
MCX7000 >>Mgmt Itf >> Gateway >> IP Address
Proceed as follows:
» Select Mgmt Itf using the corresponding Soft button
» Select Gateway
» Select IP Address
» Click OK
» Click OK

10.6.2.3 Change the Access Level
Change the access level/user profile in the front panel.

Navigate to:
MCX7000 >> Device >> Frontpanel >> Access Level
Proceed as follows:
» Select Device using the corresponding Soft button
» Navigate to Frontpanel
» Click OK (to unfold the branch)
» Navigate to Access Level
» Click OK
» Navigate to the access level of your choice

– Read Only
– Operator
– Expert
» Click OK
or
» Select the Number (Soft button) corresponding to the displayed access levels

10.6.3 Configurations
10.6.3.1 Load a Configuration
Navigate to:
MCX7000 >>Actions >> Device configuration load
Proceed as follows:
» Select Actions using the corresponding Soft button
» Select Device configuration load
» Click OK
» Select the appropriate configuration from the list
» Click OK
(The front panel displays: processing.)
10.6.3.2 Save a Configuration
Navigate to:
MCX7000 >>Actions >> Configuration >>Device configuration save
Proceed as follows:
» Select Actions using the corresponding Soft button
» Select Device Configuration Save
» Select a configuration that is available
» Click OK to save to update the selected configuration
It is not possible to create a new configuration.

10.6.4 Check the Alarms

» Select Alarm using the corresponding Soft Button
(Use the soft button arrows to navigate through the root menu.)
» Navigate to Active Alarms or Memorized Alarms
» Click OK
» Navigate through the tree menu to see the active or Memorized alarms
It is possible to clear the Memorized Alarms by pressing the OK button during three
seconds.

How to Use the Command Line Interface (CLI) MCX7000 Multi-Carrier Satellite Gateway
11 How to Use the Command Line Interface (CLI)

This sections describes how the device can be managed using the CLI.
The commands and how they can be applied are described in the following sections.
11.1 How to Access the CLI

Access the CLI via an Ethernet management interface or via the craft interface by using a RS232
serial cable.
Management Interface
To access the CLI via the management interface do the following:
» Configure the IP Address of the management interface using the front panel.
Make sure that the IP address of the MCX7000 Multi-Carrier Satellite Gateway is in
the same range as the IP Address of the managing device or that a default gateway is
configured.
» Make an Ethernet connection between the managing device and the MCX7000.

Craft Interface
To access the CLI via the craft interface do the following:
» Configure the line settings of the serial port as follows:

• Speed 115200 baud
• Eight data bits
• No parity bit
• One stop bit
» Make an connection between the managing device and the MCX7000 Multi-Carrier Satellite
Gateway.
For more information please refer to section: Craft Interface on page 23 .

11.2 Open the CLI Using a Terminal Emulator

A terminal emulator is an application that can act as a client for the SSH (Secure Shell) computing
protocol and as a serial console client. In this user manual PuTTY is used as terminal emulator.
Go to the following website http://www.putty.org/ to find the download page for PuTTY.
When opening PuTTY the following window is displayed.
» Insert the Management IP address of the device.

By default 10.0.0.2/24.
» Click Open. The Login Screen is displayed.

11.3 Log In as Expert
The CLI interface can only be accessed by the expert user.
» To login as expert type the following:
» Login as: expert
» Password: expertexpert
» The following window is displayed:
The Label is displayed between brackets.
11.4 Navigate Through the Branches of the Device

Use the following commands to navigate through the different branches of the device.
In this manual the commands are presented as follows:

The input message is displayed as follows:
Command input
The return message is displayed as follows:

Command output
11.5 Go into a Branch

» Type in the branch name and press Enter.
For Example:
[MCX7000] # demodulator
[MCX7000] demodulator#

11.6 Move Up One Level

» Type one of the following commands:
exit
or
» ..
For Example:
[MCX7000] demodulator# exit

[MCX7000] #
or
[MCX7000] demodulator#..
[MCX7000] #
11.7 Return to the Main Branch

» Type one of the following commands: exitall/[ CTRL-Z] (key combination).
For Example:
[MCX7000] device# exitall

[MCX7000]#
or
[MCX7000] device1# /
[MCX7000]#
or
[MCX7000] device# [CTRL-Z]
[MCX7000]#

11.8 Show, Help and Context Sensitive Help

These commands make it possible to request information on certain commands or parameters.
11.8.1 Show
The show command is used to display the different commands, branches or leaves that exist in a
branch.
For Example:
[MCX7000] device# show

log/
diagnostics/
identification/
location/
operatoridentification/
frontpanel/
snmp/
cli/
gui/
ftp/
or
[MCX7000] demodulator# show
configtable/
alarmstatetable
monitoringtable
statisticstable

11.8.2 Help
The help command is used to provide information on a command or parameter.
Always type help at the end.
For example:
[MCX7000] device # reset help
reset the device
Mandatory parameters:
* {enum}: Reset (default value = software) (possible enums are: hardware
software factory )
11.8.3 Context Sensitive Help "?"

This is used to provide possible completions.
When context sensitive help is used in a branch it displays all the possible commands, sub
branches, parameters and possible values.
Context sensitive help provides all possible completions when typing a command.
The question mark (?) is not shown in the interface.

The (?) can be replaced by pressing two times the TAB key.
For example display possible parameters:
[MCX7000] modulator# c?
configtable/
For example display possible values:
[MCX7000] modulator# rolloff set ?

set RollOff
Mandatory parameters:
* {enum}: Transmit filter roll-off factor. (default value = rolloff15) (possible
enums are: rolloff5 rolloff10 rolloff15 rolloff20 rolloff25 rolloff35 )

11.9 Supported Key Presses in the CLI

The CLI supports the following input characters:
Directly from the keyboard
• All printable characters • Delete

• Arrows • Tab: used to perform command completion
• Enter • "?": used to get help on the current input
context
• Backspace
• Double Tab: this has the same function as
the previous command "?"

Key Combinations
Key Combination Description
CTRL+A Go to beginning of the line.
CTRL+B Move the cursor backwards.
CTRL+C Flush the current line ignoring the contents and start a new
line.
CTRL+D Exit the CLI session.
CTRL+E Move the cursor to the end of the line.
CTRL+F Move the cursor forward.
CTRL+H Delete to the left.
CTRL+K Delete from the current cursor position to the end of line.
CTRL+P Recall the previous line in history.
CTRL+M Carriage return.
CTRL+N Go to the next line in history.
CTRL+U Delete from the current cursor position to the beginning of the
line.
CTRL+S Suspend asynchronous tracing, use this to pause the

information stream.
CTRL+Q Resume asynchronous tracing, use this to resume the

information stream.
CTRL+Z Return to the main branch.

11.10 Displayed Units

Some variables are by default scaled to a more readable unit.
For example:
• Symbol rate in Mbaud
• Bit rate in Mbps
• Frequencies in MHz
When entering a new value (without specifying a scale) the default unit scaling is
applied.
For example:
[MCX7000] demodulator configtable demod_1# inputfrequency get

1550.000000 MHz
11.11 Get and Set Parameter Values

Use these commands to read out and set parameter values.
It is not mandatory to navigate to the specific branch to execute a command. It is

possible to request or set a value from the main branch.
When in a sub branch it is possible to get/set a value from another sub branch. Do
this by entering a prefix "/" to indicate that the navigation starts from the main branch.
Get
» Type the location and the parameter name to readout the requested parameter value.

11.12 Software Upgrade (CLI)
Make sure that the upgrade file (installer.bin) is uploaded to your MCX7000.
To do this use the FTP to upload the installer.bin file.
When the upgrade file is available use the CLI to perform the software upgrade.
» Login as expert
MCX7000]# device
MCX7000 device]# softwareupgrade filename=installer_MCX7000_1.x.bin reboot=yes
***hardware reset requested***
OK
Make sure that to use the correct filename, the previous is just an example!
11.13 Dynamic Tables

The data model of the MCX7000 Multi-Carrier Satellite Gateway uses a lot of tables. These tables
are used to keep related information together.
The CLI allows to display these tables. Furthermore it is possible to access and change values of a
parameter in a specific row and column, this makes the tables dynamic.
The command "showtable" displays the entire table including column headers.
The following figure shows the layout of a table in the CLI.
Make sure that the resolution of the display is wide enough. When this is not the case
the column indication becomes unclear.

11.13.1 Show Tables

Use the following command to show a table in the CLI.
"showtable"
For example:
MCX7000 Mgmt interface link# showtable
11.13.2 Change Parameters in a Table

To access or change a specific row, type its row key and enter or specify the parameter you want to
access or change.
For example:
MCX7000 datainterface link# showtable
MCX7000 datainterface link# data2 set enable=on

OK
11.13.3 Add a New Row to a Table

In case of empty tables, the command showtable only shows the column headers.
This indicates the different parameters that can be defined for a row in this table.
To create a new row, use the command "new".
For example:

[Modem]tsoveripouts configuration configurationtable# showtable
[Modem] tsoveripouts configuration configurationtable# new TSoIP_Out_1

Ok
[Modem] tsoveripouts configuration configurationtable# showtable
[Modem] tsoveripouts configuration configurationtable# TSoIP_Out_1 set

destinationudpport=1000
OK
[Modem] tsoveripouts configuration configurationtable# TSoIP_Out_1 set Enable=On

OK
[Modem] tsoveripouts configuration configurationtable# alarm TS over IP Outs No Output:
ON
[Modem] tsoveripouts configuration configurationtable# showtable
11.13.4 Delete a Row from a Table

Use the command "delete " to remove a row from the table.
For Example:
[Modem] tsoveripouts configuration configurationtable# delete TSoIP_Out_xxxx

OK

SNMP MCX7000 Multi-Carrier Satellite Gateway
12 SNMP
SNMPv2c is used in the device. The MIBs as supported by the device can be
downloaded from the GUI Device Tasks Pane.
MCX7000 >> Device Setup >> Access Control >> SNMP
SNMP (Simple Network Management Protocol) is used when the customer wants to control the
device (or a complete system) through a NMS (Network Management System).
The following parameters must be set:
• Authentication (SNMP Communities)
An SNMP community is a relationship between an SNMP managed device and a set of SNMP
managers that defines authentication, access control, and proxy characteristics. The community
must be set on the local device/managed device. The NMS must include the correct community
string in its messages in order to get or set the different parameters of the device.
Define the following communities:
– Read Only Community: This string is always sent along with each SNMP Get action. The
received string must be recognized by the managed device in order to allow or deny access
to the device.
– Read Write Community: This string must be sent along with each SNMP Set action. The
string must be recognized by the device before a parameter can be set.
• Notification
– Set the destination IP Address where SNMP traps must be sent to. SNMP traps are
messages indicating a specific state of the device.
– Also a trap community must be configured for each trap destination.
The SNMP service is activated by default.

It is recommended to disable the SNMP service when the service is not used to
manage the device. Do this to avoid unauthorized people accessing the device.
For more information on the use of the SNMP interface refer to the System
Integration Guide.
The SNMP MIBs can be downloaded using the GUI interface.
» Navigate to the Tasks Pane (GUI)
» Click Documentation
» Click SNMP MIBs

A mibs.zip file is downloaded and stored on the default folder of the management device.

How to Use the Graphical User Interface MCX7000 Multi-Carrier Satellite Gateway
13 How to Use the Graphical User Interface

The graphical user interface is a web application that gives remote access to the MCX7000. It allows
the user to:
• Manage the device.
• Create or change configurations.
• Monitor the status of the MCX7000 through alarms.
The GUI is optimized for displays with a screen resolution of 1024 x 768 or higher.
Newtec advises to use the latest version of the Firefox or Google Chrome as standard
browser.
Note that the GUI can also run on the latest version of other compatible browsers like
Internet Explorer, Safari .....
13.1 Opening the GUI

Proceed as follows to open the GUI on a computer in the network:
» Open a web browser.
» Type the IP address of the device in the address bar of the browser. The default IP address is
10.0.0.1/24.
Make sure that the management PC has access to this IP Address or it belongs to this
IP range. If needed it is possible to configure the Mgmt Gateway.
» Press Enter.
The following graphical user interface is displayed. (see next page).


13.2 User Profiles

The three possible user profiles are described in the following sections.
For security reasons it is recommended to change the default passwords of the user
profiles. For more information please refer to section: Change a Password on page 56
For detailed information on the access rights of the user profiles refer to the reference
manual.
13.2.1 Guest Profile

The user has read-only access to the typical configuration and monitoring options.
This is the default profile when logging in.
There is no password defined for this profile.
13.2.2 Operator Profile
Newtec recommends using this profile when configuring or maintaining a device.
The operator profile is developed in such a way that the user is not overloaded with all possible
parameters.This is done to keep the configuration and maintenance of the device light and easy.
The user has read-write access to the typical configuration and monitoring options.
The default User Name and password for the operator profile is as follows:
• User Name: operator
• Password: operatoroperator
13.2.3 Expert Profile

This profile has read-write access to all configuration parameters.
The expert profile can be used to configure specific features where the user needs more
background of the different possibilities.
The default User Name and password for the expert profile is as follows:
• User Name: expert
• Password: expertexpert

13.2.4 Switch User Profile

» Click logged in as guest/operator/expert (The User options window is displayed.)
» Click Switch User to change the user profile. (The Login window is displayed.)
– User Name: operator
– Password: operatoroperator
– User Name: expert
– Password: expertexpert

13.3 Change a Password

» In the user options window click Change Password.
» Enter the Current Password and then the New Password. Also confirm the new password.
» Click Change Password to confirm the New Password.

13.4 GUI Pane Description

The following screen displays the general layout of the graphical user interface. The different panes
are numbered clockwise and described in the pane description table.
The following table describes the sections numbered in the previous figure.
Pane Pane name Function

No.
1 Banner The top row of the banner displays the official device description
and type.
The top right row displays the current user profile. (To change
the user profile, refer to Switch User Profile on page 55)
The bottom left row of the banner is editable and can be used to
assign a unique identifier to the device. Do this by clicking on the
label. (In the previous figure, the label is marked:
Documentation).
This name is also shown in the tab of the web

browser making it easier to identify different
devices.

Pane Pane name Function

No.
2 Alarms list pane The alarm list displays the alarms generated by the device.
Alarms are sorted first by their activity and then by their severity
(from critical alarms to warnings).It is possible to:
• Filter Active, Memorized or All Alarms
• Clear the memorized alarms counter
• View details of the generated alarm. (State, History)
3 Function controls This pane displays by default the overview tab.

pane
The overview tab is the home page of the device.
• It is the starting page to perform configurations and do trouble
shooting.
• It displays the current status of the active blocks in the device.
• It displays the signal flow trough the device.
4 Status bar The status bar informs on:

• On-going interaction with the device via the status field on the
left.
• Refresh button, the status of the device gets refreshed.
Click the arrow to configure the time interval of refreshing the
status of the device.
5 Tasks pane The tasks pane provides an overview of different tasks that are
possible on following levels:
• Device • Equalink ® 3
– Configurations – Satellite Link Analyzer
– Configuration – Automated Linear
Templates – Manual Linear
– Reset – Automated Non-Linear
– DSNG Profiles Import
– Manual Non-Linear
– DSNG Profiles Export
– Linear File Import
• Logs
– Device Log
– Clear Device Log
• Toolbox • Documentation
– Diagnostics Report – Download the Reference Manual
• Maintenance – Download the SNMP MIBs
– Software Upgrade
– License Upgrade

13.4.1 Banner
The banner is split up in four parts.
1. Newtec Logo.
2. Device identification, the top row is fixed, the bottom row is editable (the text used here is also used in the
tab of the banner).
(In the previous figure, the label is marked: Documentation).
3. Device/Connectors Management (for a short introduction on these blocks please refer to following table).
(See table below).
4. Displays the current user profile (To change the user profile, refer to Switch User Profile on page 55).
The top right row displays the current user profile.
The bottom left row of the banner is editable and can be used to assign a unique identifier to the device. Do
this by clicking on the label. (In the previous figure, the label is marked: MCX7000).

Functional Description
Block
Device This functional block allows you to configure the device redundancy
Management status, the operator identification parameters and furthermore you can
check the following parameters:
• Device Label (note that it is possible to update this field, to
represent a logical name of the device in the network setup).
• Device Serial number and its Unique ID.
• Product number and the Device Description.
• The software ID and Software Version.
• The device options table indicate all licenses that are activated in
your device.
Note:These parameters are helpful when it is needed to perform a
software upgrade, a license upgrade or when you need to contact
our customer support center for more information.
Management This functional block allows you to configure the management

Interfaces interfaces of the device.
Configure the Ethernet and IP Connectivity of the Mgmt1, Mgmt2 and
the Mgmt Front panel interfaces.
Configure Link Redundancy (bonding) of the management interfaces.
Data Interfaces This functional block allows you to configure the data interfaces of the
device.
Configure the Ethernet and IP Connectivity of the data interfaces.
Configure the link redundancy settings of the data interfaces.
ASI Interfaces This functional block allows you to configure the direction (input or
output) of the ASI interfaces.
By default all ASI interfaces are configured as output interfaces.
It is recommended to make a convention within your
company, defining which ASI interfaces are used as
input/output interfaces.
Modulator This functional block allows you to configure a:

• 10 MHz reference clock for a BUC multiplexed on the L-band
interface.
• Enter the local oscillator frequency of the external frequency
converter. The MCX7000 calculates the RF output frequency.
(RF Frequency = L-band + LO).
Demodulator This functional block allows you to configure:

• The Input Selection per connector.
• Apply a LNB power supply connector.

13.4.2 Overview Tab

The Overview tab contains a schematic representation of the data flow in the device.
The signal passes different functional blocks and each block contains a function name, basic
settings and counters.
The blocks are connected with arrows that illustrate the data flow.
Click on the corresponding functional block to open the detailed page, making it
possible to monitor, and/or reconfigure the parameters.
The status of a functional block is displayed by means of a LED indicator.

For more information on the colors used in the GUI please refer to section:
Colors Used in the GUI. on page 67

Input
Functional Block Description
Demodulator This block allows you to configure the input parameters of the
demodulator in order to lock onto a carrier (RX Lock).
From this functional block it is also possible to monitor the incoming
signal. These monitoring parameters can help to optimize or to perform
debugging on the link.
When the demodulator is locked on the carrier, the signal is forwarded
to one of the following functional blocks:
1. Single Stream mode: the carrier contains only one transport stream; this
transport stream is send to the connections block.
2. Multistream mode: the carrier contains multiple transport streams and the
correct transport stream must be filtered out of the carrier before the
transport streams are send to the connections block.
Multistream Input The functional block allows you to configure the ISI filters.
ASI (Inputs) This functional block allows you to configure the ASI Input interfaces.
Next to enabling the input interface it is possible to select the Input
Framing (188 or 204) and to enable/disable the In-line Splitter.
TS over IP (Inputs) This functional block allows you to configure the TS over IP input
interfaces.
TS Generator This functional block allows you to configure up to two PRBS (Pseudo
Random Bit Sequence) generators.
The PRBS (Pseudo Random Bit Sequence) generator is used to
perform basic tests on the device or to get an indication on the satellite
link quality.
TS Redundancy TS redundancy allows to create active/standby redundancy scenarios.

In this case one stream serves as backup for the other stream.
Input Processing When transport streams contain MPE data this data is filtered out in this
MPE decapsulation block.
Filter on the transport stream, the program specifications and the
correct channel.

Probes and Connections
PRBS Use the PRBS detector to monitor an incoming PRBS stream.
TSA The transport stream analyzer makes it possible to monitor the

transport streams on different locations in the device.
TS Connections This functional block allows you to configure the connections between
any available input and output interface.
This configuration is done by creating a rule that defines which input
interface needs to be linked with which output interface.
For example:
• Demodulator (TS) <-------> TSoIP (Output)
• TS over IP (Input) <-------> Modulator (Output)
• PRBS Generator (Input) <--------> Modulator (Output)
Output
Output Processing The following processing blocks are available:

• BISS Scrambler on page 279
• Rate Adapter on page 300
• NIT Carrier ID on page 304
• PSI/SI on page 306
• MPE Encap. on page 309
ASI (Output) This functional block allows you to configure (Enable/Disable) the ASI
output interfaces.
TS over IP (Output) This functional block allows you to configure the TS over IP output
interfaces. Enter the destination IP Address, its UDP port and the
required encapsulation protocol.
Multistream Output This functional block allows you to configure the ISI streams and
MODCODs (for Multistream transmission).
Modulator This functional block that allows you to configure and monitor the
modulation of the data. For example set the output frequency, select
the standard operating mode (DVB-S, DVB-S2, DVB-S2X or S2
Extensions) and accordingly select the appropriate MODCOD.

13.4.3 Tree View

The tree view shows all device parameters arranged in a tree structure consisting of branches, sub
branches and leaves.
The following pane is displayed:
The tree view, divides the Function Control Pane in to two extra panes, they are called A and B in
the previous figure:
The following table describes the extra panes of the tree view:
Pane Description
A Displays the menu tree structure.
Click on a branch or sub branch to navigate through the device.
The menu tree structure uses the following icons:
• : This is a branch icon; it can contain sub branches or

leaves/configuration parameters.
• This is a sub branch icon; it contains leaves/configuration

parameters.
B Displays the sub branches or the details on the parameters (leafs) that exist under a
selected branch.

13.4.4 Alarms Pane

The alarms pane shows the alarms generated by the device.
Alarms are sorted first by their activity and then by their severity (from critical alarms to warnings.)
The alarm list pane contains the following information:
Pane Description
A This pane displays the alarms.

It is possible to filter on the following alarm information:
• Active
• Active and Memorized
• All Alarms (this displays the complete overview of all possible alarms)
B This pane displays the details on the selected alarm:

• How many times did the alarm occur since the last clear
• When was the last activation
• When was the alarm cleared for the last time
» Click Clear Counters to clear the number of times an alarm was generated.
(Active alarms can be cleared but remain active, the last clear time is updated).
To perform alarm masking, refer to section: Alarm Handling on page 361

13.4.5 Status Bar

The status bar informs on the following:
Cfg saved is red when the active configuration is modified but not saved.
To save the configuration, refer to section: Save a Configuration. on page 337
The following table describes the available LEDs.
LED LED Description

Color
Ethernet Green There is no Ethernet interface alarm (data 1 and 2) detected.

(Data Red Indicates a data interface alarm.
interfaces
are In case of data bond, both Ethernet interfaces must be in alarm.
monitored) Off Both data Ethernet interfaces are disabled.
ASI Green The interface is enabled and activity is monitored during the last
second.
Red The ASI interface is enabled but there is no activity monitored

during the last second.
Off The ASI interface is not enabled.

(Input selection = None)
Green All active demodulators are fully locked.

RX Lock
This means that there is Physical Layer Lock and Base band frame
Lock.
Yellow One of the active demodulators is in PL lock (Physical Layer lock).

• Physical layer headers are decoded properly.
• An Es/No estimation is available.
• Equalizer is operational.
But no decodable BB frame was received.
Red One of the active demodulators cannot lock to the incoming carrier.
Off The demodulator is disabled.

LED LED Description

Color
Data Green The incoming / outgoing data signal over the data Ethernet and ASI
interfaces is valid.
(ASI and
Data Yellow The incoming / outgoing interfaces are configured but there is no
Ethernet activity monitored during the last second.
interfaces)
Off The data interfaces are disabled.
TX On Green The device is transmitting.
Off The transmission is disabled.
Green Indicates that the active configuration is saved.

Cfg saved
Red Indicates that the active configuration is modified but not saved.
Auto Save Green The auto save functionality is activated.

For more information on the auto save functionality please
refer to section: Auto Save Configuration on page 345 .
Off The auto save functionality is disabled.
Select the drop-down menu to define the GUI Refresh Time.

Refresh
When working over a slow/long-delay link (like a satellite link)
slowing down this refresh time could be useful to improve the
responsiveness of the GUI.
13.5 Colors Used in the GUI

In the schematic overview, colored LEDs are used per functional block to provide the status of the
device. The traffic flow is also indicated between the functional blocks by arrows.
The following LED colors are used in the functional blocks.
• Green: The device is working as expected.
• Orange:
– Device Management: Device redundancy is active and the device is in standby mode
– RX Lock: At least one of the active demodulators is in PL lock (Physical Layer lock).
• Grey: This functional block is not active in the current configuration.
• Red: An alarm is present on the functional block.
» Click on the LED Indicator to see on what "instance" the alarm is triggered.

The following colors are used for the process flow arrows:
• Black: Indicates a connection.
• Light Blue: Indicates the flow of Transport Streams.
• Dark Blue: Indicates the flow of Baseband Frames.

13.6 Parameters in the GUI

The GUI contains different types of parameter dialogue boxes to configure all parameters.
Dialogue box Example

Type
Drop-down-list-box
Edit
This pencil icon indicates that it is possible to edit the parameter
Lock
The lock icon indicates that it is not possible to edit the parameter.
Data field
Check box
• To apply a setting use the following icon .
• To cancel a setting use the following icon .
Table
Functional group
Enable/Disable
button
Enabled
(indication)
Disabled
(indication)
Reset button

Dialogue box Example

Type
Show All
Click this dialog box to open the functional block.
Open Detailed
View
Click this icon to open the detailed view, zooming in on the parameters
of the specific block.
Delete
Click this icon to delete a connection.
Hovering over a parameter shows more details about it.

13.7 Update or Configure Parameters in a Table

The GUI uses popup windows to update or configure the parameters that belong to a table.
For example:
» Click the pencil icon in front of the parameter row you want to update or configure.
Or double click on the the row to update or configure.
(A new window pops up)
» Select and/or enter all parameters according to the network requirements.
» Click Update to confirm the new settings.

13.8 Invalid Values

The GUI does not allow the input of invalid values. While typing a value this value is validated.
The user interface has several features that help to insert valid parameters:
• When typing an invalid value for a parameter, the edges of the parameter field turn red and a tool
tip displays the reason why the value is invalid.
• It is not possible to save values outside the defined ranges for the device.
The following figure shows an example of the behavior of the GUI when you try to enter an invalid
value.

Device Security MCX7000 Multi-Carrier Satellite Gateway
14 Device Security
14.1 Switch User Profile

» Click logged in as guest/operator/expert (The User options window is displayed.)
» Click Switch User to change the user profile. (The Login window is displayed.)
– User Name: operator
– Password: operatoroperator
– User Name: expert
– Password: expertexpert

14.2 Access Control

Before using the device into a network it is recommended to consider which management channels
need to be enabled.
It is recommended to disable unused services to prevent unauthorized access to the

device. By default SNMP, CLI and FTP are enabled.
Login as expert user and navigate to the following locations to enable or disable these settings.
MCX7000 >> Device >> SNMP
MCX7000 >> Device >> CLI
MCX7000 >> Device >> FTP
MCX7000 >> Device >> Frontpanel

Once the frontpanel is put into read-only mode it can only be changed back to
read-write mode via one of the other available interfaces.
For example via the GUI using an Ethernet connection or via the CLI interface using
the craft interface.
(This is useful when the management IP address has changed and the device is
unreachable through IP connectivity).

General Configuration Principles MCX7000 Multi-Carrier Satellite Gateway
15 General Configuration Principles
15.1 Introduction
The device you have acquired is a very flexible device that can support a wide range of applications.
The user can define the data path, the number of streams that go through the device and their
routing.
The goal of this section is to explain to the advanced user the underlying principles on which the
device and its user interface is based so that a user can configure the device from scratch to meet its
desired functionality.
15.2 Device Data Path

As the synoptic view shows, the device is based on a data path split between an input and an output
part.


The input part takes in all the inputs and possibly decomposes the signal into constituting streams.
At the bottom right of the input path, all the individual streams are going out.
In the input part, some processing such as TS Redundancy and MPE decapsulation may be done.
The output part takes in the available streams, processes them, possibly aggregates them and
sends them to the relevant output.
In-between the input path and the output part, a TS connectivity block makes the connections
between the two parts.
The probes "TSA" and "PRBS" provide expert users an analyzing of the streams at the block
interfaces. They allow analyzing any signal at the output of a block in the input path or at the input of
a block in the output path.
15.3 Data Handling Blocks and Instances

The various blocks in the synoptic view are data handling blocks: data input blocks, processing
blocks, routing blocks or data output blocks. Each block represents one or several instances.
For example, the ASI block in the input part represents the various ASI inputs of the device.
15.4 Viewing Instances

Instances can be viewed by clicking on a data handling block.
If no instance exists, there is no arrow on the right of the LED. Clicking on the block in that case
opens the window where instances can be created.
If only one instance is possible in the device (for example only one modulator), then clicking on a
block sends the user to a tab with all the parameters of that single instance.
The LED color only displays the state of the instance(s).
The two first examples show a list of available instances when clicking on the arrow.
The third example on the right displays two blocks where no instance exists.

15.5 Creating and Deleting Instances

Unless in some specific cases (modulator, demodulator, ASI In and outputs), instances can be
created and deleted. This is done by clicking on the drop down list of a block and select the “Show
All” field or by clicking on the block itself if no drop-down arrow is visible.
This opens a tab with a table summarizing all instances of this type created. A new instance is
created by clicking the “Add” button (it will be grayed out if the maximum number of instances is
reached). An instance can be deleted by clicking on the “x” on its line.
The following figure shows an example:
Creating an instance opens a window where the instance parameters can be defined.
It usually contains:
• A name. Always use meaningful names , so that you know what signal this instance is
processing.
See below for more details on how to name instances.
• An “Enable” field allowing to have inactive instances without having to delete them.
Do not forget to enable the instance you want to use. Inactive instances have a grayed LED
attached to it.
• Two fields (with names like “From”, “To”, “Select”, “Input”, “Output”) and associated with “Type”
and “Name” defining which signal to process or where to send the output to.

15.6 Instance Naming

As explained in previous sections: Names are important to help having a good view on the product.
Meaningless names will make complex configurations difficult to use. Two instances of different
types can have the same name. Newtec recommends the following naming schemes. Please select
the one that best fits your application:
• Scheme based on streams: Instances have names based on the stream content they process:
All instances processing the same stream could be named the same as “MyTVChannel”.
Example: all instances processing the first stream can be called”BBC”, the ones handling the
second stream “RAI1”. TS connections should have the name of the stream too.
• Scheme based on instance type: If the content is not known or may change, it is
recommended to use names reflecting the instance type, extended with a number or label.
Example “TSoIPin 1”, “TSoIPin 2”, “BISS scrambler 1”, etc.
TS connections are named “TS1”, “TS2”, … , or are named based on the link they implement
like “ASI1->Modulator”.
The second is less recommended as if another input is selected, a new connection has to be
created.
Configuration templates (see Quick Configuration Templates on page 133) use the second scheme as
the content is not known a priori. Nothing prevents to use the first scheme, if the configuration is
built from scratch.
Physical instances like the ASI connectors or the modulator have a fixed name.
Instances created cannot be renamed.
15.7 Connecting Instances to Form the Data Path

Most instances contain as parameters a set of “From type” / ”From name” and/or “To type” / “To
Name” (names as “Input Type”, “Input Name”, “Output Type”, “Output Name” are also used). Those
fields specify what signal is taken as input and to which instances the signal is sent to.
“From type” / ”From name” (or equivalent) is used in the Input Path. “To type” / “To Name” (or
equivalent) is used in the Output Path.
By defining where the signal comes from and where it is sent to, the data path is created. The Input
Path and Output Path are connected together at the level of the “TS” connections block.
The value “None” exists for the source or destination of the signal. This value is used in one of the
following cases:
• A user deletes an instance that is connected to others. Connections pointing to the deleted
instance will be set to “None”.
• A user has created an instance but does not want to connect it yet: the input/output can be set to
“None”.
Input (or Output) Processing blocks are an exception: they are applied on a signal and have a
“Select TS” field to choose the right stream in the TS Connections.

15.8 TS Connections and Stream Path

The “TS” block is a special block that connects the input path and the output path together. It allows
also identifying streams in the device. Instance of this block define a stream. By clicking on an
instance, you open the “Stream View” for that stream, showing where this stream comes from and
where it goes to. Several tabs for several streams can be open at the same time.
Note: In case of a routing change, it is best to close the Stream View tab and reopen it from the
“Overview tab”. Otherwise the Stream View tab will not be redrawn.
15.9 Full Data Path

The device is very flexible regarding its data path and the connectivity possibilities, so that it can
fulfill a large range of use cases. An overview of the full data path is presented below:
The previous figure shows that:

• All inputs are handled in the same way, irrespective of their origin.
• Probes and outputs can take signals on various points of the device.
• Processing blocks like TS Redundancy, BISS scrambler, rate adapter can be used or by-passed.
The order of processing is however imposed.
• Signals can be duplicated by defining more connections that use the same source.

Configure the Physical Interfaces MCX7000 Multi-Carrier Satellite Gateway
16 Configure the Physical Interfaces
16.1 Device Management

The device management is done under the Device/Connectors Management block.
» Click Device.
The following sections explain the different blocks displayed in the previous figure.
• Device Redundancy
• Device Location
• Operator Identification
• Device Identification
– Installed Device Options

16.1.1 Configure Device Redundancy

Device redundancy is very important as a single failure of the MCX7000 affects many services at the
same time.
Reliable operation of the MCX7000 in a satellite network is of key importance. The MCX7000 works
seamlessly together with the Newtec USS202/USS0212 redundancy switches to provide
best-in-class system uptime.
Refer to the user manual of the USS0202/USS0212 Universal Switching System.
The following figures shows a 1+1 protection scheme for a modulator built up with the USS0212
switch, one in normal operation and one in redundant operation.
Normal Operation
Redundant Operation

Location
To Enable or Disable device redundancy go to the following location:
Configure
By default, device redundancy is disabled.

Log in as expert user.
Enable or disable the device redundancy.

Configure the Initial State:
• Standby (default value): This means when the device starts up and redundancy is enabled, the
initial state of the redundancy is standby.
Typically:
– The modulator output is disabled.
– The virtual IP Address on the data interface is ignored.
– The status LED of the device block is orange.
• Active.
– The modulator output is enabled.
– The virtual IP Address is available on the data interface.
– The status LED of the device block is green.
The Operational State displays the current state of the device.

16.1.2 Configure the Device Location

It is possible to enter the geo coordinates, to indicate the current position of the modulator.
The Geo Coordinates (the latitude and longitude information) are added to DVB Carrier ID and NIT
Carrier ID when these parameters are enabled.
Please refer to the following sections: DVB-CID Configuration Table on page 179 and
NIT Carrier ID . on page 304
Location
Configure
Enter the Geo Coordinates to indicate the current position of the modulator.
Configure the Geo Coordinates only in appropriate situations.

16.1.3 Check the Operator Identification

This information is used by the DVB Carrier ID and NIT Carrier ID.
Please refer to the following sections: DVB-CID Configuration Table on page 179 and
NIT Carrier ID . on page 304
Location
Configure
Carrier Identification Enter the name of the carrier company.

Note: the amount of characters is restricted to five to fit in
the NIT Carrier ID.
Telephone Number The telephone number makes it easier for satellite

operators to contact you in case of "emergency"
For example: +32 3 780 65 00
Telephone Extensions Number It is possible to enter the extension number of the

department or person that is responsible for the system
configuration.
For example: 2323

16.1.4 Device Identification

This menu provides an overview of the general device identification.
Use this part to enter a logical device label and to check device information such as the serial
number and software version.
Location

Configure or Check
Label Enter a logical device label for easy recognition of the device in a
system setup.
The label is displayed in the banner of the device and in the
browser tab.
In the previous figure the label is indicated as Documentation.
Serial Number This is the device serial number as it produced in the factory.
Unique ID This is the unique device ID, additionally assigned after the
production of the device.
Product The official Newtec product name of the device.
Device Description This the official name of the MCX7000.
Type ID This is the Newtec internal ID of the MCX7000.
Hardware Revision The hardware revision of the MCX7000. Indicating the hardware
configuration of the device.
Software ID This is the Newtec internal ID of the software installed on the

MCX7000.
Software Version This indicates the installed software version installed on the
MCX7000.
This is useful for upgrades or fault debugging when necessary.
License Type Permanent license or temporary license.

For more information please refer to section:
License Type on page 89.
License Remaining Time Displays the remaining time of the temporary license.

16.1.4.1 License Type
There are four license types available for the device.

• Permanent License
• Temporary license with a fixed end date
• Temporary license with an operational time span (time credit)
• Temporary license with an operational time span (time credit),
but only consumed when the device is the active one in a redundancy setup.
Location
Permanent License
This license type is the most common type and contains the "feature" set that is ordered.
The license is fixed and can only be updated after ordering a new license.

Temporary Licenses
An Expire Alarm is triggered 15 days (remaining time) before the license effectively
expires!
Save the "standard" configuration before performing a license upgrade to a temporary

license.
• Please refer to section: Save a Configuration on page 337 .
• Please refer to section: License Upgrade, on page 350 to see how to perform a
license upgrade.
For example, a customer requests a temporary license to test Equalink 3.

When this request is granted, the customer receives one of the following temporary license files.
Temporary license with a fixed end date.

• In this case it is possible to test the Equalink 3 settings until the day specified.
• The license expires that day, meaning that the device falls back to the permanent installed
license or when no permanent license was installed, the device goes into blocked mode.
This blocked mode only allows the following actions: setting the Mgmt IP address, import a
license and perform a firmware upgrade.
The following picture shows an example of a license which is about to expire.

Temporary License with an operational time span

• In this case it is possible to test with the Equalink settings during this trail period.
• The countdown is triggered when the device is active.
Temporary License with an operational time span on a redundant device.

• The countdown is triggered when the device is the master in the redundancy setup.

16.1.4.2 Check the Installed Device Options
This menu displays the currently installed options of the device.

Use it to see whether or not a certain license is installed or not.
Location
For more information on the options please refer to section: Options on page 10

16.1.5 Reference Clock

Configure the reference clock.
This reference signal can be used for various operations.
For example: as a reference signal for an outdoor BUC. At this time the signal is multiplexed on the
L-band Tx interface see Configure the 10 MHz BUC Reference on page 126.
A reference clock can be generated internally (default) or slave on an external source.
The internal reference clock is 10 MHz.
The clock reference has the following specifications:
10 MHz Ref Specifications
Internal clock reference Stability ± 2000 ppb over 0 to 70°C

Ageing ± 1000 ppb/year
Very High Stability (optional) Stability ±2x10e-9 over 0°C to 65°C

Ageing: ± 0.5 ppb/day
± 500 ppb/10 year
When an external source is selected, the following frequencies can be inserted.

1 MHz, 2 MHz, 5 MHz, 10 MHz or 20 MHz.
Select the external clock reference for synchronization with other devices to have a higher stability
than the internal default stability.
Location
» Log in as expert.
» Navigate using the tree view to configure the reference clock.


16.2 Configure the Management Interfaces

The device management is done under the Device/Connectors Management block.
• Physical Link • IP Connectivity

• Ethernet Link Redundancy – Configure the IP Addresses:
• VLAN Link • mgmt IP Addresses
• Statistics • Virtual IP Address
• Physical Link Alarm Status – Routing

16.2.1 Management Ethernet Physical Link

The MCX7000 has three management Ethernet interfaces that can be used to configure and
maintain the MCX7000.
The following figure shows the location of the interfaces on the device.
Management interface 1 (MGMT 1) is activated by default.

The default IP address is 10.0.0.1/24.
Location

Configure
Enable the interface or interfaces that must be available for configuration and/or maintenance.
• MGMT 1 (This the top port on the back panel indicated as MGMT 1)
• MGMT 2 (This the bottom port on the back panel indicated as MGMT 2)
• MGMT Front panel (This is the Ethernet port that is found on the front panel)
Do not disable the (all) active management interface(s) because this makes the
device unreachable over the Ethernet interfaces.
(When this occurred by accident, the management interface can be enabled again
using the front panel buttons).
When link redundancy is used, MGMT 1 and MGMT 2 must be enabled and auto
negotiation must be on. To enable link redundancy, refer to
Ethernet Link Redundancy on page 99
» Click on the Mgmt interface.

The following window opens.

Interface Indicates the name of the physical interface.
Enable Enable or disable the interface.
MAC Address Indicates the MAC address for the Ethernet management
interface.
Auto Negotiation Enable or disable the auto negotiation.

It is recommended to enable this setting.
When disabled, the management device must be configured
with the same advertised speed. (If this is not the case the
communication is not guaranteed.)
Advertised Speeds • All, this is the default value and recommended in

combination with auto negotiation.
• Select a forced speed incase auto negotiation is
disabled.
Link State Indicates the currently used speed to perform the

communication or link down when the link is inactive.

By default this is 1500.
The maximum value is 9582 which allows to use jumbo
frames.
» Click Update

16.2.2 Ethernet Link Redundancy

It is possible to enable link redundancy (also known as bonding) on the management Ethernet
interfaces. Link redundancy is used to eliminate downtime as much as possible in the system setup.
This increases the reliability of the system.
When link redundancy is enabled, two interfaces will behave as one virtual interface (interface
bonding): only one of the two physical interfaces is active at a time.
When the link state of the active interface goes down (physically broken connection), the other
interface takes over the operation.
Refer to the following figures: Note that the same principle is used for the data interfaces.

Location
Configure
When link redundancy is activated, the bond interface must be configured. This bond
interface has an IP Address that is used as destination address by the source.
To have link redundancy (bonding) working properly make sure to configure the
switch/router in such a way that the spanning tree is not blocking the fast switchover
between ports.
In a typical Cisco switch configured using rapid spanning tree this is achieved by
setting the ports in PortFast mode.

» Click Link Redundancy and select one of the following options.
Protection Mode Descriptions
Name Indicates the name of the interface.
Enable Enable or Disable link redundancy.

By default this is 1500 (recommended value).
The maximum value is 9582 which allows to use jumbo frames.
Protection Mode Select one of the following options:

• Revertive: Select this when one of the interfaces (A and B) has
priority. This means when the preferred interface returns to
normal mode, the data will be taken in on this interface.
• Non-revertive: Select this when no priority between the
interfaces
(A and B) is required.
In this case when an interface returns to normal mode there will
be no "switch" to the other interface.
Interface A Select one of the two mgmt interfaces to be Interface A.
Interface B Select one of the two mgmt interfaces to be Interface B.

Note it is not possible to select the same mgmt interface to be
Interface A and Interface B. This will result in an error message.
Preferred Interface Select either Interface A or Interface B to be the interface with most
priority.
» Click Update.

16.2.3 Alarm Status Tables

The alarm status tables provide a direct view on the status of the physical link and the redundancy
link.
Location

16.2.4 Management IP Connectivity

Use this menu to configure the MCX7000 management IP address and subnet mask. The
management IP address is used by external applications to access and control the MCX7000.
Once the IP address is configured it is possible to perform management using the HTTP (Web
Interface the GUI), Telnet (CLI) or SNMP interfaces.
Use a network drawing to define the IP addresses of the management interfaces:
The following figure is an example of a setup:
Location
Configure
• Mgmt interfaces: Configure at least one Mgmt interface to perform basic management using the
GUI, CLI or SNMP.
– Mgmt1, by default this IP address is: 10.0.0.1/24
– Mgmt2
– Mgmt Front panel
– Mgmt: This is the management bond interface. The interface is only displayed when Link
Redundancy is enabled, refer to the next section. (This interface is used to perform link
redundancy, effectively combining Mgmt1 and Mgmt2 into one new virtual interface).

» Click on the relevant Mgmt interface.
Mgmt Interface Indicates the name of the physical interface.
IP Address/Prefix Configure the management IP address to perform basic

management using the GUI, CLI or SNMP.
Make sure that the source device and the MCX7000 belong
to the same IP range or the content is routed to the correct
Mgmt IP address.
Virtual IP Address/Prefix Configure the virtual IP address in case device

management redundancy is required.
(This principle is also explained in the following section:
Virtual IP Address.) on page 116
State Indicates if the IP connection is up or down.
» Click Update.

16.2.4.1 Configure the Mgmt Routing Table
The routing table allows to statically route different subnets to different next hop points. In this way,
you can route the different networks towards different hosts in the network. Next to configuring the
default gateway to reach a subnet it is also possible to create a specific gateway to route the data
directly to the next hop. The routing table configuration parameters define the exact destination of
the Mgmt traffic.
The default gateway is the access point for the data ports of the device.
The following figure shows the principle of the default gateway.
Enter the default gateway IP address. The interface selection is automatically resolved.
Make sure that the default gateway IP address belongs to the subnet of the corresponding Mgmt IP
address. When this is not the case the following message is displayed:
Gateway in Route table is not routable.
The device makes it possible to create more gateways making it possible to reach devices in
another subnet passing the next hop.
Please refer to the following figure, Principle of Routing Table,to see the working principle of the
routing table.

Location
Configure
Note: The default gateway cannot be deleted.
» Click Add to create more gateways, this makes it possible to reach devices in another subnet
passing the next hop.
Name Enter a logical name for the new route.

For example the destination IP Address.
Subnet Enter the subnet to be reached.
Interface Connect the routing to an available interface. This can be a "physical"

(data1, data2) or a logical interface (I.e. VLAN).
Gateway Enter the IP address of the outgoing gateway. Make sure that this
gateway is connected with the subnet to be reached.
State This indicates the operational state of the route.
» Click Update.

16.3 Configure the Data Interfaces

The data interfaces configuration is done under the Device/Connectors Management block.

• Physical Link • IP Connectivity

• Ethernet Link Redundancy – Configure the IP Address:
• VLAN Link • Data IP Address
• Statistics • Virtual IP Address

• IGMP Version
– Configure Multicast
– Routing
16.3.1 Physical Link

The data interfaces are bidirectional Ethernet interfaces that connect the customers "data terminal
equipment" with the MCX7000 (data communications equipment).
Location
» Click on Data functional block.
Configure
» Click on the data interface to enable/configure.

– data1 (This port is the top port on the back panel indicated as DATA 1)
– data2 (This port is the bottom port on the back panel indicated as DATA 2)

When link redundancy is needed, data1 and data2 must be enabled and auto
negation must be on. To enable link redundancy, refer to section:
Data Ethernet Link Redundancy. on page 110
Per interface, the following information is displayed.
• Interface; (read only) • Auto Negotiation (On/Off)

It is recommended to enable this.
• Enabled (On/Off)
• Advertised Speeds
• MTU
(Maximum Transmission Unit, by default • Forced Speed
this is 1500, the maximum value is 9582 This is not applicable incase of auto
which allows to use jumbo frames.) negotiation.
• MAC address • Link State.

16.3.2 Data Ethernet Link Redundancy

It is possible to enable Ethernet link redundancy (also known as bonding) on the management and
data Ethernet interfaces. Link redundancy is used to eliminate downtime as much as possible in the
system setup. This to increase the reliability of the system.
When link redundancy is enabled, two interfaces behave as one virtual interface (bond interface):
only one of the two physical interfaces is active at a time. When the link state of the active interface
goes down (physically broken connection), the other interface takes over the operation. (Note that a
gratuitous ARP reply is sent.)
Location

The following window is displayed:

Configure
» Click on the data interface to enable or configure the link redundancy.
Name Indicates the name of the interface.
Enable Enable or Disable link redundancy.

By default this is 1500 (recommended value).
The maximum value is 9582 which allows to use jumbo frames.
Protection Mode Select one of the following options:

• Revertive: Select this when one of the interfaces (A and B) has
priority. This means when the preferred interface returns to
normal mode, the data will be taken in on this interface.
• Non-revertive: Select this when no priority between the
interfaces (A and B) is required.
In this case when an interface returns to normal mode there will
be no "switch" to the other interface.
Interface A Select one of the two data interfaces to be Interface A.
Interface B Select one of the two data interfaces to be Interface B.

Note it is not possible to select the same data interface to be
Interface A and Interface B. This will result in an error message.
Preferred Interface Select either Interface A or Interface B to be the interface with most
priority.
» Click Update
To configure the IP Address of the data interface (bond interface), refer to section:
IP Connectivity. on page 114

16.3.3 VLAN Link

Virtual LAN, commonly known as a VLAN, is a group of hosts with a common set of requirements
that communicate as if they were attached to the same broadcast domain, regardless of their
physical location. A VLAN has the same attributes as a physical LAN, but it allows for end stations to
be grouped together even if they are not located on the same network switch. Network
reconfiguration can be done through software instead of physically relocating devices.
The received and transmitted data traffic can have a VLAN tag (trunk port) attached to it, allowing for
an easy separation of different traffic flows on the connection between the MCX7000 and any
Ethernet switch or other networking device. These VLAN tags are stripped off by the MCX7000.
The following figure shows a system setup where the MCX7000 belongs to the following VLAN's,
VLAN 10, VLAN 20 and VLAN 40.
In the figure we want to link VLAN 10, VLAN 20 and VLAN 40 on the MCX7000.
Once a VLAN ID is added (and enabled) to the MCX7000 the device is part of this VLAN.
In the figure we see that the device receives the IP streams that exist on the VLAN 10, VLAN 20 and
VLAN 40.
Once received, the VLAN information is stripped off.
The further processing in the MCX7000 depends on the received data, TSoIP or IP packets that
need to be MPE encapsulated.

• TSoIP: IP overhead is removed and the MPEG packets are recovered from the payload. Those
MPEG packets are handled as a transport stream.
• MPE: IP overhead is removed and the data is forwarded to the MPE encapsulator when this
processing block is configured. (please refer to section:Configure MPE Encapsulation). on page 310
(Adding an ISI (Input Stream Identifier) to a stream is done under the Multistream TS Output, please
refer to section: Configure the Multistream Output on page 231).
This way the remote sites can filter on the ISI to receive the required information.
Location
Configure
Proceed as follows to link the MCX7000 to the appropriate VLANs in the network.
» Click Add (And complete the following parameters.)
Name Enter a logical name for the VLAN.
Enable Enable the VLAN.
MTU Maximum Transmission Unit
Parent Indicate to which physical interface this virtual LAN is linked.

Interface Select data1, data2 or data in case of link redundancy.
VLAN ID Enter the VLAN ID. This VLAN ID indicates what VLANs are linked by the
MCX7000.
» Click Update
Once a VLAN link is added, the data IP addresses table is automatically updated with
the new interface. Please refer to section: Data IP Address. on page 114

16.3.4 Statistics
This table provides an overview of the traffic that is passing over the different Ethernet ports and
VLAN links.
Location
» Log in as expert to view these statistics.
» Click on Data functional block (Banner of the GUI).

The following parameters are displayed:
• Input Bytes • Output Bytes

• Input Packets • Output Packets
• Input Dropped • Output Dropped
• Input Errors • Output Errors
16.3.5 Data IP Connectivity
16.3.5.1 Data IP Address
Data IP connectivity is important to make Ethernet connections between the customer data terminal
equipment and the MCX7000 data communication equipment.
Use a network drawing to define the IP addresses of data interfaces. The following figure is an
example of a setup:
Make sure that the source device and the MCX7000 belong to the same IP range or the content is
routed to the correct Data IP address.
By default, the data IP addresses are 0.0.0.0/24:
• data1
• data2
• Data (or data bond), always corresponds with the currently active data IP interface. The currently
active Data IP interface can be checked in the Link Redundancy part. Please refer to section:
Data Ethernet Link Redundancy on page 110
It is recommended to configure the connected switch/router-ports in portfast-mode.

Otherwise a spanning tree protocol event could cause a blocked port towards the
MCX7000.
In a typical Cisco switch configured using rapid spanning tree this is achieved by
setting the ports in portfast mode.

Location
Configure
» Click on in front of the data interface to be configured.
Interface Displays the name of the interface.

(Read only).
IP Configure the IP Address according to the network drawing.

Address/Prefix
Virtual IP Use a virtual IP Addresses when working with device redundancy and a USS
Address/Prefix (Newtec's Universal Switching System).
State This monitoring Parameter displays if the data interface is operational or not.
» Click Update.

16.3.5.2 Virtual IP Address
Use virtual IP Addresses when working with device redundancy and a USS (Newtec's Universal
Switching System).
The virtual IP Addresses are configured on the main device. These are automatically synchronized
to the stand-by (spare) device. The moment the main device goes into alarm the Stand-by device
inherits the IP address of the main device. A gratuitous ARP (Address Resolution Protocol) Reply is
sent to the Ethernet switch in order to update it's MAC table and reroute the traffic to the correct port.
Location

Configuration
» Click on of the data interface to be configured.
Interface Displays the name of the interface.

(Read only).
IP Configure the IP address according to the network drawing.

Address/Prefix
Virtual IP Use virtual IP Addresses when working with device redundancy and a USS
Address/Prefix (Newtec's Universal Switching System).
Configure the virtual IP address(es) on the main device.
State This monitoring Parameter displays if the data interface is operational or not.
» Click Update

16.3.5.3 IGMP Version
Multicasting allows one computer on the Internet to send content to multiple other computers that
have identified themselves as interested in receiving the originating "computer's" content.
Internet Group Management Protocol (IGMP) is an Internet protocol that provides a way for an
Internet computer to report its Multicast group membership to adjacent routers.
IGMP registers dynamically individual hosts in a multicast group on a particular LAN segment.
Location
Configuration
Selection Description
IGMP v2 Provides the basic query response mechanism that allows the multicast router to
determine which multicast groups are active and other processes that enable
hosts to join and leave a multicast group.
Furthermore it provides such capabilities as the IGMP leaves process,
group-specific queries and an explicit maximum response time field.
IGMPv2 also adds the capability for routers to elect the IGMP querier without
dependence on the multicast protocol to perform this task.
Please refer to RFC 2236 document that defines the IGMPv2.
IGMP v3 Provides for source filtering, which enables a multicast receiver host to signal to a
router which groups it wants to receive multicast traffic from, and from which
sources this traffic is expected. In addition, IGMPv3 supports the link local
address 224.0.0.22, which is the destination IP address for IGMPv3 membership
reports; all IGMPv3-capable multicast routers must listen to this address.
Please refer to RFC 3376 document that defines the IGMPv3.

16.3.5.4 Configure the Multicast IP Address
Multicast is used to perform a single transmission destined for a group of devices. Data is transmitted
to a single multicast IP address and received by any device that needs to obtain the transmission.
A device that needs to obtain the transmission uses the Internet Group Management Protocol to join
or leave a multicast host group.
Group membership information is exchanged between a specific host and the nearest multicast
router/switch.
The following figure shows a multicast group.
The devices that want to receive information from the source device need to join the multicast
group. A join message is transmitted towards the switch or multicast router. The router accepts the
join message and creates an entry in a local group database. This database tracks the group
membership of router's directly attached hosts. The routers regularly send an IGMP query message
to all it's members. Each host that still wants to be a member of a group sends a reply.
In the figure above the MCX7000 sends a join message towards the switch.
When the multicast IP address is recognized by the switch the MCX7000 is entered in the local
group database of the switch. From this moment the switch/multicast router will add an entry in its
database indicating on which port he should forward the multicast information.
The switch or multicast router sends query messages to verify the group membership. Hosts that
don't answer to the query messages are deleted from the local group database.

Location
Configure
» Click Add
Name Enter a logical name for the multicast connection.
Interface Select to what interface the multicast connection is linked.

A physical interface or a VLAN interface.
Multicast Address Define what multicast group the MCX7000 wants to join.
Source Address A Configure the source address to indicate from which source data is
expected. This allows the router to forward data from only those sources
from which the receivers requested the data.(Note this is only applicable
when the IGMP version 3.0 is selected, refer to section:
IGMP Version on page 118.)
Source Address B Source A and Source B allow to configure device redundancy on multicast
level.
State Indicates if the multicast connection is operational or not.

In case the connection is not operational, check the following:
• Check if the IP Address is enabled.
• Check the Physical link state.
» Click Update.

16.3.5.5 Configure the Routing Table
The routing table allows to statically route different subnets to different next hop points. In this way,
you can route the different networks towards different hosts in the network.Next to configuring the
default gateway to reach a subnet it is also possible to create a specific gateway to route the data
directly to the next hop. The routing table configuration parameters in combination with the TS over
IP output interfaces configuration parameters define the exact destination of the data.
The default gateway is the access point for the data ports of the device.
The following figure shows the principle of the default gateway.
Enter the default gateway IP address. The interface selection is automatically resolved.
Make sure that the default gateway IP address belongs to the subnet of the corresponding data IP
address. When this is not the case the following message is displayed:
Gateway in Route table is not routable.
The device makes it possible to create more gateways making it possible to reach devices in
another subnet passing the next hop.
To reach a device in the next hop, it is needed to configure the routing table, defining
a specific subnet together with its gateway. Next to this configure the corresponding
TS over IP output destination IP address. Please refer to section:
Add a TS over IP Output Interface on page 204.
The MCX7000 checks its routing table and when a corresponding subnet is available
the data is forwarded to this gateway.
The following figure shows the principle of the routing table.

TSoIP Output 1 (The flow is indicated by the dashed line)

Steps to follow:
1. Destination IP Address = 172.16.1.2
2. Check in the routing table if subnet 172.16.1.0/24 exists?
3. This subnet does not exit.
4. Send the data towards the default gateway = 10.10.10.21 (Router1).
5. Router 1 checks if this IP address is recognized.
6. The IP address is recognized and forwarded to the destination device, Laptop=172.16.1.2 .

TSoIP Output 2 (The flow is indicated by the green dash/dot line)

Steps to follow:
2. Check in the routing table if the subnet 162.15.1.0/24 exists?
3. This subnet exists.
4. Send the data towards the configured gateway = 10.10.10.22 (Router2).
6. The IP address is recognized and forwarded to the destination device, Laptop = 162.15.1.2.
TSoIP Output 3 (The flow is indicated by the yellow line).

Steps to follow:
2. Check in the routing table if the subnet 192.168.1.0/24 exists?
3. This subnet exists.
4. Send the data towards the configured gateway = 10.10.10.23 (Router3).
6. The IP address is recognized and forwarded to the destination device, Laptop = 192.168.1.2.
Location

Configure
Note: The default gateway cannot be deleted.
» Click Add to create more gateways, this makes it possible to reach devices in another subnet
passing the next hop.
Name Enter a logical name for the new route.

For example the destination IP Address.
Subnet Enter the subnet to be reached.
Interface Connect the routing to an available interface. This can be a "physical"

(data1, data2) or a logical interface (I.e. VLAN).
Gateway Enter the IP address of the outgoing gateway. Make sure that this
gateway is connected with the subnet to be reached.
State This indicates the operational state of the route.
» Click Update.

16.4 Configure the ASI Interfaces

There are six ASI interfaces available on the back panel.
By default all ASI interfaces are configured as output interfaces.
In this block it is possible to configure the direction of the ASI interfaces either as input or output
interfaces.
Further configuration or monitoring information of the ASI interfaces is located either on the input
interfaces or output interfaces.
For the ASI input interfaces one can configure an In-line splitter and the input framing, please refer to
section ASI Input interfaces. on page 150
Location
Configure
» Click the ASI input interface and select its direction.
» Click Update.
It is recommended to make a convention within your company, defining which ASI

interfaces are used as input/output interfaces.

16.5 Configure the Modulator Interfaces
16.5.1 Configure the 10 MHz BUC Reference

This reference signal for an outdoor BUC can be multiplexed on the L-band Tx interface.
The reference clock is taken from the reference clock.
(Refer to the previous section: Reference Clock on page 93)
Location

Configure
» Click the Connector-1 to enable or disable the 10 MHz BUC Reference.
» Click Update.
16.5.2 Configure the Converter

By defining here the Local Oscillator of the external frequency converter and whether or not it
applies spectrum inversion, the RF Frequency is displayed in the Modulator GUI parameter list.
Location
Configure
» Log in as expert
» Click Converter Connector-1

Name Indicates the name of the interface. (Read only).
Enable Enable or Disable the converter calculator.
LO Frequency Enter the local oscillator frequency of the external frequency

converter.
The local oscillator frequency is used to provide the actual RF
frequency range. This is reflected in the modulator parameter
settings ranges overview.
Direct Spectrum
This is displayed in the following screenshot.
It displays the IF - band (when applicable for your device) and L-band
ranges and RF bands:
• [IF-bandmin + LO and IF-bandmax]
and
• [L-bandmin + LO and L-bandmax]
Inverted Spectrum
This is displayed in the following screenshot.
Spectrum Inversion Select direct spectrum or inverted spectrum depending on the

external converter settings.
» Click Update.

16.6 Select the Demodulator Connectors
16.6.1 Configure the Demodulator Connectors

The number of demodulator connectors depend on the number of demod boards ordered for slots 1,
2 and 3 and on the number of demod board licenses (0 to 3). There are 4 L-band inputs per board,
combined in groups of two.
• Board 1 has connector group 1 (connectors "L-BAND Rx A1" and "L-BAND Rx B1") and
connector group 2 (connectors "L-BAND Rx A2" and "L-BAND Rx B2").
• Board 2 has connector groups 3 and 4.
• Board 3 has connector groups 5 and 6.
Connectors groups 1, 3 and 5 are active in release R1.
Please refer to section Options on page 10 and Appendix - Back Panel Combinations on page 401 to get

an overview on the different possibilities.
Per connector group one can select between L-BAND Rx A or L-BAND Rx-B.
Furthermore the MCX7000 Multi-Carrier Satellite Gateway provides the possibility to add DC power
and frequency band selection signals (on the L-BAND RX A connectors.) compatible with most
professional and commercial LNBs.
• 13V/0 kHz
• 13V/22 kHz
• 18V/0 kHz
• 18V/22 kHz
If LNB power is enabled, devices that do not tolerate a DC-voltage at their input can
be damaged (e.g. spectrum analyzers). In this case it is advised to use a DC-block at
the input of the device.

Location
The following figure shows how the GUI configuration relates to the back panel.
(Note that the back panel layout depends on the ordered options. To get an overview on the different
back panel combinations please refer to Appendix - Back Panel Combinations on page 401.)
Configure
» Click a connector group and select input and, if applicable, the appropriate LNB Power Supply.

» Click Update.
16.6.2 Configure the Demodulator Converter

This feature allows the user to see the actual RF input frequency.
Depending on the spectral inversion the L-band Input Frequency is calculated as explained in the
following examples.
Changing and enabling the values in the demodulator convertor affects the displayed
Input Frequency in the corresponding demodulator view.
The parameter Input Frequency is automatically changed to RF Frequency.
Please refer to section, Demodulator Configuration Table on page 188.
Direct Spectrum
Input Frequency = RF Frequency - LO Frequency
For example
Note, the data used in this example is taken from a standard LNB.
• When using a Ku-band LNB with LO = 10 GHz and a receive band of 10.95 to 11.80 GHz, the
resulting L-band frequency (noted as the demod's "Input Frequency") will be in the range of 11.8
GHz - 10.0 GHz = 1800 MHz and 10.95 - 10.0 GHz = 950 MHz
In this case the:
Input Frequency = RF Frequency - LO Frequency and the spectrum will be direct (as the LO is
lower in frequency than the received frequency).
Inverted Spectrum
Input Frequency = LO Frequency - RF Frequency
For example
Note, the data used in this example is taken from a standard LNB.
• When using a C-band LNB with LO = 5.75 GHz and a receive band of 3.6 to 4.8 GHz, the
resulting L-band frequency (noted as the demod's "Input Frequency") will be in the range of 5.75
GHz - 3.6 GHz = 2150 MHz and 5.75 GHz - 4.8 GHz = 950 MHz
In this case:
Input Frequency = LO Frequency - RF Frequency and the spectrum will be inverted (as the LO is
higher in frequency than the received frequency).

Location
Configure
» Click Demodulator in the Device/Connector Management group.
» Select a Connector Group
» Enter the LO Frequency of the used LNB.
» Select Spectral Inversion if applicable.

This results in the following input frequency ranges:

Quick Configuration Templates MCX7000 Multi-Carrier Satellite Gateway
17 Quick Configuration Templates
17.1 Introduction
Devices are provided to you with a set of configuration templates that pre-configure the device for
some most-used situations.
For example, a DTH modulator can be made operational in two steps:
Loading the “DTH modulator – ASI” template and editing the modulator parameters.
A template is equivalent to a standard device configuration, except that a template cannot be
overwritten. Templates can however be modified and saved as a device configuration
To select a template
» Log in as operator (Default login/password is “operator”/”operatoroperator”).
» Navigate to the tasks pane and select Configurations Templates.
The following sections describe each template.

Drawing conventions for the configuration templates.
• Greyed blocks are not active by default. Actual blocks present depend on the device license.
Configuration templates load on all device. They may however not be functional if the device
license does not allow some features. For example, there is no issue in using a template with
TSoIP blocks if the device has no TSoIP license. Those will be ignored.
• Templates always have the modulator turned off to avoid broadcasting on an undesired
frequency. The same is true for any TSoIP output.
• Configurations also include blocks that are created but are disabled or are not connected. They
are there to allow easy modification of the existing use case. They do not affect performances.
• Templates do not restrict you to that use case. It is always possible to add/remove elements or
change the connectivity to support any other use case starting from any template or from
scratch.
If you need a pre-defined configuration for a specific use case, you can either create it
yourself and save it as a standard configuration or you can also contact Newtec to
help you generate the proper configuration that can be imported (as a standard
configuration) on your device.
Use the Newtec Service Desk tool to receive more information.

> Create a ticket
As response of your request you will receive appropriate feedback from our support
team.

17.2 Template A1. Single Stream Modulator - ASI

This template is deemed for any single-stream modulator applications like DTH (Direct to Home) or
contribution. The block diagram is as follows:
The pre-defined datapath is: ASI1 input connected to the modulator with a loopback on ASI6.
To make the modulator operational, you need to click on the “Modulator” block to edit modulation
parameters (frequency, symbol rate, MODCOD, etc). Do not forget to enable the modulator output
when all parameters are fine (set the “Transmit” parameter to active)!
You can then easily add the following functions:
Rate Adaptation
Click on “Output Processing” block, then on “Rate Adapter”. Edit the rate and set the flag to “enable”.
BISS scrambler
Click on “Output Processing” block, then on “BISS scrambler”. Edit the key values in the first table
“Keys”, then the BISS scrambler parameters by editing the second part of the screen.

When modifying keys, enter either the Clear Session Words pair (odd and even), OR
the Encrypted Session Words pair (odd and even), based on your application. Never
enter both pairs at the same time.
NIT Carrier ID
Click on “Output Processing” block, then on “NIT Carrier ID”. Edit the NIT carrier ID value and
enable the function.
TS redundancy between two ASI

TS Redundancy is already active in the template (with ASI1 and ASI2 as inputs), but as only one
input is enabled, this block behaves as a pass-through. Enabling the second ASI input will enable
automatically the TS redundancy between the two inputs.
To enable ASI2, click on the “ASI” block in the top part of the Overview screen. Select “ASI 2”.
Enable the ASI 2 input.
Activating the TS Analyzer

Click on the “TSA” block, then on “TS Analyzer”. Enable the function and it will work.
You can change the signal analyzed by changing the “From type”, “From Name” fields by setting
which type on input or output you want to see and which instance.
Note: on the input path (top of the window), the TSA will point to signals going out of blocks, while
on the output path (bottom part), it will point to a signal entering a block. Example: you can select the
output of the “TS Redundancy” block, or the input of the “Modulator” block.
Enabling a TSoIP input

To activate a TSoIP input, you first need to make the proper Ethernet interface(s) active.
To enable “Data 1”and/or “Data 2” Ethernet interface: Click on the “Data” button on the top of the
screen (banner area). Enable “data 1” and/or “data 2” in the “Physical Link” table (first table). Make
sure also that the IP address of the enabled interface is correct (“IP Address” table).
You can then activate the TSoIP input: Click on “TS over IP” block in the input path and select
“TSoIPin 1”. You can edit in the table “multicast” the multicast address to listen to (and possibly the
interface on which the TSoIP input comes in). In the second part of the screen, you can edit the port
addressed and other TSoIP input parameters. Enable the input to make it active.
Default values are: TSoIPin1 on multicast 239.0.0.1, port 1231 (entering on data 1), TSoIPin2 on
multicast 239.0.0.2, port 1232 (entering on data 2). For Unicast : just specify the port on which the
signal is sent (no other changes needed).You need now to make sure that the TS Redundancy
block uses this TsoIP input. For that click on “TS Redundancy” block and Select “TS Redundancy”.
Change the “Input A Type” to point to “TS Over IP In” and the “Input A Name” to point to “TSoIPin 1”.
If you do not want redundancy to be enabled, make sure the second input does not point to an active
input (point to a disabled input or to “None”). An alternative is to edit the “TS” connection so that it
takes as input the right signal directly, by-passing the TS redundancy block.

Note1: This shows that a template can be used to support use cases beyond its initial
scope: here an ASI modulator can be easily turned into a TSoIP modulator without
changing templates.
Note2: Another way to use TSoIp inputs is to load the “A2. Single-stream modulator –
TSoIP” template. In this template, all IP settings and interfaces are activated already.
Getting TSoIP input redundancy requires doing the same with “TSoIPin 2” (and enabling data 2) and
setting it as Input B of the TS redundancy block.
Enabling the TSoIP output

TSoIP output is by default disabled to avoid sending traffic on an undesired address.
To enable “Data 1” Ethernet interface (if not done yet): Click on the “Data” button on the top of the
screen (banner area). Enable “data 1” and/or “data 2” in the “Physical Link” table (first table).
To enable the TSoIP output , click on the “TS over IP” block and select “TSoIP out”. Edit the
parameters and enable the output.
Default values are: TSoIPout on multicast 239.0.1.1, port 1241, on data 1.
If you change the multicast IP address, you have to tell the device on which interface to send the
signal to:
Click on the “Data” button on the top of the screen (banner area). The output interface for each
multicast address can be changed in the “Routing” table.
For unicast address, the device will distinguish the interfaces if the subnet they are in are different. If
it is the same subnet, a routing rule should be added.
17.3 Template A2. Single Stream Modulator TS over IP

This template is the same as the previous one, except that the TSoIP inputs are by default routed to
the TS redundancy block. This template works best for modulators where no ASI input exist, so that
the device is operational by only editing TSoIP input parameters and modulator parameters.
The ASI loopback is still enabled. The TSoIP loopback is not active to avoid sending data on an
unwanted IP address.
See the “A1. Single-stream modulator – ASI” template description to know how to configure or adjust
the device parameters. Everything is identical, except that “data 1” and “TSoIPin 1” is enabled and
both TSoIP inputs are already connected to the TS Redundancy block.

17.4 Template B Single Stream Demodulator

This template implements a single-stream demodulator with ASI and/or TSoIP outputs.
By default, the output of the demodulator is sent directly to the ASI 4 output.
To make the demodulator operational, you need to click in the “Overview” window on the
“Demodulator” block. It will open a tab where you can edit the demodulator parameters.You can get
variations on that use case as described below.
Enabling the Second ASI Output

Additional ASI outputs are disabled to avoid reporting unnecessary errors. ASI-5 can be made
operational by activating it: Simply click on the “ASI-5” block in the output path of the “Overview” tab.
Enable the output. The ASI-5 will produce the same signal as ASI-4.
Note: it is possible to make ASI-5 outputting another signal, but for that you need to create another
Connection between the inputs and the ASI-5 output. See the “General Configuration Principles”***
section on how to do that.

Enabling the TSoIP Output

TSoIP output is by default disabled to avoid sending traffic on an undesired address.
To enable the TSoIP output , click on the “TS over IP” block and select “TSoIP out”. Edit the
parameters and enable the output.
Default values are: TSoIPout on multicast 239.0.1.1, port 1241, on data 1.
If you change the multicast IP address, you have to tell the device on which interface to send the
signal to:
• Click on the “Data” button on the top of the screen (banner area). The output interface for each
multicast address can be changed in the “Routing” table.
• For unicast address, the device will distinguish the interfaces if the subnet they are in are
different. If it is the same subnet, a routing rule should be added.
• If you send the output on “Data 2” interface, you have to enable it too: In the same tab, Enable
“data 1” and/or “data 2” in the “Physical Link” table (first table).
Activating the TS Analyzer

Click on the “TSA” block, then on “TS Analyzer”. Enable the function and it will work.
You can change the signal analyzed by changing the “From type”, “From Name” fields by setting
which type on input or output you want to see and which instance.
Note: on the input path (top of the window), the TSA will point to signals going out of blocks, while
on the output path (bottom part), it will point to a signal entering a block. Example: You can select
the output of the “TS Redundancy” block, or the input of the “Modulator” block.
TS redundancy between the Demodulator and a second ASI Input

TS Redundancy is already active (with “Demodulator 1” and “ASI 3” as inputs), but as only one input
is enabled, this block behaves as a pass-through. Enabling the ASI-3 input will enable automatically
the TS redundancy between the two inputs.
To enable “ASI-3”, click on the “ASI” block in the top part of the Overview screen. Select “ASI-3”.
Enable the ASI 3 input.
TS redundancy between the Demodulator and a TSoIP Input

To activate a TSoIP input, you first need to set the proper parameters and enable it.
Click on “TS over IP” block in the input path and select “TSoIPin”. You can edit in the table
“multicast” the multicast address to listen to (and possibly the interface on which the TSoIP input
comes in). In the second part of the screen, you can edit the port addressed and other TSoIP input
parameters. Enable the input to make it active.
Default values are: TSoIPin1 on multicast 239.0.0.1, port 1231 (entering on data 1). For Unicast :
just specify the port on which the signal is sent (no other changes needed).
You need now to make sure that the TS Redundancy block uses this TsoIP input. For that click on
“TS Redundancy” block and Select “TS Redundancy”. Change the “Input B Type” to point to “TS
Over IP In” and the “Input B Name” to point to “TSoIPin”. Note: This shows that a template can be
used to support use cases beyond its initial scope: here an ASI modulator can be easily turned into
a TSoIP modulator without changing templates.

17.5 Template C1. Single Stream Modem ASI

This template is for a single-stream modem with ASI inputs and outputs.
This template combines the template A1. Single-stream Modulator ASI and B. Single-stream
Demodulator in one device. The only difference is the naming of some TSoIP inputs/outputs and
the existence of two TS analyzer, one for the modulation path and one for the demodulation path.
Note: In this logical view, the two data paths are depicted separately. In the device overview, the two
data paths are overlapping as the ASi input and the demod inputs are considered as equivalent
inputs. As a consequence, the TS redundancy blocks of the Mod and Demod are both listed under
the “TS redundancy” block, as two different instances working independently.
Operations to make this template operational are the same as in A1 and B.Note: it is possible to use
this template in far more use cases. Transmodulation for example is possible by selecting as
modulator input the demodulator output. To do that, click in the “Overview” tab on the “TS
Redundancy” block and select “TS Mod Redundancy*”. Change “Input A Type” to “Demodulator” and
“Input A Name” to “Demodulator 1” and you are done (assuming the mod and demod parameters
match or that the rate adapter is active).

17.6 Template C2. Single Stream Modem TSoIP

This template is for a single-stream modem with TSoIP inputs and outputs.
It is identical to C1, except that” ASI1” is disabled, “TSoIPin 1” is enabled and and both TSoIP inputs
are by default feeding the TS Redundancy block of the modulator.
17.7 Template D1. Multistream Modulator ASI

This template is for a multistream modulator with ASI inputs.
By default, this template routes 2 ASI inputs to two ISI channels that are sent to the modulator. ASI 1
is looped back to ASI 6.
The template allow for easy extension to 5 ASI inputs or TSoIP inputs or a mix of both.
To make the device operational, you need to:
• Edit the ISI channels parameters by clicking on the “Multistream Output” block and select a
stream “TS i ”.
Edit its parameters.
• Edit the Modulator parameters by clicking on “Modulator” and edit the parameters.
Do not forget to enable the modulator output to get it working.

To add an additional ASI input

To add a 3 rd , 4 th or 5 th ASI input, you need to (we assume as example that ASI-3 has to be
added):
1. Enable the input: Click on “ASI” block in the input path and select “ASI-3”. Enable the input.
2. Enable the ISI stream: click on “Multistream Output” block and select “TS3”. Enable the stream and edit its
parameters in the two tables.
3. Edit the modulator parameters if needed: click on “Modulator” block and edit the parameters.
To add an additional TSoIP input

To activate a TSoIP input, you first need to make the proper Ethernet interface(s) active.
To enable “Data 1” Ethernet interface: Click on the “Data” button on the top of the screen (banner
area). Enable “data 1” in the “Physical Link” table (first table).
You can then activate the TSoIP input(s): Click on “TS over IP” block in the input path and select
“TSoIPin 1”. You can edit in the table “Multicast” the multicast address to listen to (and possibly the
interface on which the TSoIP input comes in). In the second part of the screen, you can edit the port
addressed and other TSoIP input parameters. Enable the input to make it active. Do the same for
the other inputs if needed.
Default values are: TSoIPin1 on multicast 239.0.0.1, port 1231, TSoIPin2 on multicast 239.0.0.2,
port 1232, …, TSoIPin5 on multicast 239.0.0.5, port 1235. All signals come in on “data 1” interface.
For Unicast: Just specify the port on which the signal is sent (no other changes needed).
Then you can associate one of the TS defined to this TSoIP input : Let assume TS3 is to be fed with
TSoIPin 1. What you need to do is connect “TSoIPin 1” to the third multistream output, by editing the
TS Connections. All you need to do is click on “TS” block and select “Show All”. You will see the
various streams processed in the device.
Edit the “TS3” line by clicking on the pencil and change “From Type” to “TS Over IP In” and “From
Name” to “TSoIPin1”. Click update to validate the change.
Enable the ISI stream TS3: Click on “Multistream Output” block and select “TS3”. Enable the stream
and edit its parameters in the two tables.Note: It is also possible to add TS connections for TSoIP
inputs to link them to additional ISI streams, but this goes beyond this user manual scope.

17.8 Template D2. Multistream Modulator TSoIP

This template is for a multistream modulator with TSoIP inputs.
It is identical to D1, except that the “data 1” interface is already enabled, TSoIP inputs are already
connected to ISI streams and the two first are already enabled.
To make the device operational, you need to define the TSoIp input parameters (if needed), then
follow the same steps as in D1.Default values are: TSoIPin1 on multicast 239.0.0.1, port 1231,
TSoIPin2 on multicast 239.0.0.2, port 1232, …, TSoIPin2 on multicast 239.0.0.5, port 1235, all
coming in on “data 1” For Unicast : just specify the port on which the signal is sent (no other
changes needed).
17.9 Template E. Multistream Demodulator

This template is for a multistream Demodulator.
By default, the demodulator output is filtered based on ISI and two streams are sent to two ASI
outputs. All the other ASI are configured as outputs (but disabled) and TSoIP output instances are
defined.
To make the device operational, you need to:
• Edit the Demodulator parameters by clicking on the “Demodulator” block and edit the
demodulator parameters.
• Edit the ISI values on which to filter by clicking on “Multistream Input” block and select the
relevant TS instance “TS i ”.
• Edit the ISI value.
To enable ASI outputs or TSoIP outputs, please refer to the “B. Single-stream Demodulator”
template.Default values are: TSoIPout1 on multicast 239.0.1.1, port 1241, TSoIPout2 on multicast
239.0.1.2, port 1242, …, TSoIPout6 on multicast 239.0.1.6, port 1246, all coming out on “data 1”

17.10 Template F1. Multistream Modem ASI

This template is for a multistream modem with ASI inputs and outputs.
This template combines the template D1. Multistream Modulator ASI and E. Multistream
Demodulator in one device, with 3 streams for each. The only difference is the naming of some
TSoIP inputs/outputs and the existence of two TS analyzers, one for the modulation path and one for
the demodulation path.
Note: This logical view, the two data paths are depicted separately. In the device overview, the two
data path are overlapping as the ASi input and the demod inputs are considered as equivalent inputs.
As a consequence, the TS redundancy blocks of the Mod and Demod are both listed under the “TS
redundancy” block, as two different instances working independently. Configuration is the same as
for D1 and E templates.

17.11 Template F2. Multistream Modem TSoIP

This template is for a multistream modem with TSoIP inputs and outputs.
It is the same as F1, except that “data 1” interface is enabled, TSoIP inputs are connected by default
to the ISI streams and the two first TSoIP inputs are enabled.Configuration is the same as for D2
and E templates.

17.12 Template G. Single Stream Multi-Demodulator

This template is for a multi-demodulator where each demodulator works in single stream mode.
The first demodulator is connected to the TS redundancy block. Redundancy between the demod
input and another ASI or TSoIP input is possible. It is also possible to get redundancy between, two
demodulators by connecting the “B” input of the TS redundancy block to “Demodulator 2” or
“Demodulator 3”.
The two other demodulators are directly connected to the output (TSoIP and ASI if available).

17.13 Template H. Multistream Multi-Demodulator

This template is for a multi-demodulator where each demodulator works in multistream.
By default, the each demodulator output is filtered based on ISI and two streams are sent to two
TSoIP outputs.
17.14 Template I. Single Stream 1M2D

This template is for a device encompassing one modulator and two demodulators (all working in
single streammode).
This template is the equivalent to the “C2. Single stream modem – TsoIP” template, with one extra
demodulator.

Configure the Functional Blocks MCX7000 Multi-Carrier Satellite Gateway
18 Configure the Functional Blocks
18.1 Introduction
This chapter explains in detail how the functional blocks in the GUI are connected to one another.
The block diagrams and the configuration procedure of the following use cases are displayed:
• Single Stream Modulator (DTH Modulator)
• Single Stream Demodulator (DTH Demodulator)
• Multistream Modulator
• Multistream Demodulator
• Multistream / Multicarrier Demodulator
In this scenario, use the same procedure as for the multistream demodulator and repeat it for
every available demodulator.
See Block Diagram Multistream and Multicarrier Setup on page 269.
The screenshots used and the parameter description tables cover all parameters
including the expert parameters.
To get the device up and running it is sufficient to log in as operator.
At that moment the expert parameters are hidden.
In this chapter we assume the following:

• The direction of the individual ASI interfaces, being an input or an output, has already been
configured.
• IP data interfaces are already configured.
Recommendations and Tips

During the configuration of the different blocks the following recommendations should be
considered:
• When you define a name, use a logical name.
This to keep an overview during the configuration and monitoring of the device.
• Use the same or similar naming during the configuration of the device.
Note that it is not possible to rename an "instance" once it is created.

• It is possible to create "instances" in advance, allowing you to create future proof setups.
For example:
Today your satellite setup exists out of two ASI input interfaces to perform a broadcast. But in the
future you are planning to integrate some new hardware capable of forwarding TS over IP
towards the MCX7000.
With the MCX7000 you have the possibility to preconfigure the TS over IP input interfaces.
Allowing you to test the interfaces before the arrival and integration of the new hardware. When
the tests are fine you can disable the TS over IP input until the integration of the new hardware is
finished. When the integration is finished simply enabling the TS over IP input is required to get
the processing started.
The following figure shows the example between the situation today and the future situation.

18.2 Block Diagram Single Stream Modulator

The block diagram shows the data flow through the device from the different possible inputs to the
different possible outputs.
» Click DTH Modulator:

The following window is displayed (when logged in as expert):
Input Interfaces
Name Description
ASI Use this block to configure the incoming transport streams

over ASI.
It is possible to:
• Enable or disable the ASI input interfaces.
• Select the appropriate framing (188 or 204).
• Indicate if an in-line splitter is used (3 dB or 6 dB
attenuation).
TS over IP It is possible to configure the incoming transport streams via

the IP network.
TS Generator Please refer to TS Generator. on page 271
TS Redundancy It is possible to add a redundant input stream to an incoming

stream; it is recommended to do it in order to eliminate the
downtime as much as possible.

Connections
Name Description
TS Use this block to make a connection between the ASI input

interface and the modulator output block.
Note: This connections block allows to make connections
between any available input and output interface.
Output Interfaces
Name Description
Modulator Use this block to configure the RF parameters of the

modulator according to the system setup.
Define the output frequency, the symbol rate, the roll-off
factor and select the MODCOD that is needed for
transmission.
18.2.1 Configure the ASI Input Streams

» In the overview pane click on ASI.
Note: When no entries are available, configure the ASI Interfaces Direction first, see:
Configure the ASI Interfaces. on page 125
» Click Show All (to view all ASI input interfaces).

» Click to configure the ASI incoming streams.

Name Displays the name of the ASI interface.

(Read Only).
Enable Enable or disable the ASI interface.
In-line Splitter Use this parameter to compensate for an attenuation that is present due to the
use of an external passive splitter. It is possible to compensate for 3 dB or 6
dB attenuation.
When a passive splitter is used and this compensation is not enabled, the
incoming signal might be degraded too much so that a correct modulation
cannot be guaranteed.
Input Framing The incoming packets can be:

• TS188 (transport stream with 188-byte packets).
• TS204 (transport stream with 204-byte packets, 188 bytes with 16 bytes
for error correction).
The 16 bytes for error correction (overhead) are removed

before the actual modulation takes place.
When the incoming packets are not corresponding to the configured framing
type, the following alarm is generated: ASI IN No Input Signal ASI 1.
» Click Update.

18.2.1.1 ASI Monitoring Table
The monitoring table indicates the input rate and the operational state.
18.2.1.2 Alarm Status Table
Parameter Description Action

Input Green: The ASI interface is physically
Signal connected.
Red: The ASI interface is not Check the cabling.
connected.
Input Data Green: Data is received on this
interface.
Red: No data is received on this Check if the source device (encoder,
interface. multiplexor, ...) is activated.
Data Error Green: Data received is in the correct
format.
Red: • No data is received, please check
one of the previous causes.
• No data is receive.
• Check the input framing.
• Data is received but not in the
correct format.

18.2.2 Configure TS over IP Input Streams

This functional block allows you to configure up to eight input streams but in case of a single stream
modulator very often one input stream and maybe a redundant stream will be configured here.
The physical data ports used by the input streams are the Ethernet interfaces data1 and data2.
Next to enabling the logical interfaces, it is required to define the UDP port where the data is
received.
Furthermore select the encapsulation protocol and configure the input rate mode parameters in such
a way:
• That the TS is streamed to the output at the exact rate to avoid any misalignment between the
original transport stream and the outgoing transport stream.
• That jitter will be minimized, i.e. output rate is virtually constant and jitter from the IP network is
eliminated.
TSoIP input recommendation:

TSoIP can transport up to 7 transport stream packets in 1 UDP frame. This can
introduce high levels of jitter when bitrates are low. To avoid excessive jitter on the
TSoIP inputs, the number of TS packets/UDP frame should be lowered when using
low bitrates.
The following table provides an overview of the recommended settings to use:
Bit Rate Recommended Number of TS Packets
>= 500 kbps Up to 7 TS packets/UDP frame (less is allowed).
500 kbps > Bitrate >= 250 kbps Maximum 3 TS packets/UDP frame.
250 kbps > Bitrate >= 100 kbps Maximum 2 TS packet/UDP frame.
Bitrate <= 100 kbps Maximum 1 TS packet/UDP frame.
Configuration
» Click on the functional block and then click Show All.

When no TSoIPs are available see Add a TS over IP Input Interface. on page 156


18.2.2.1 Add a TS over IP Input Stream
» Click Add to insert a new TS over IP on the Ethernet Input Interface.

The following table is displayed:

Name Enter a logical name for this incoming transport stream.
Enable Enable or disable the input streaming.
TS Encapsulation Select the encapsulation protocol that was used by the source device.
Protocol
• UDP: It is advised to use the UDP protocol only in simple IP networks
where jitter, packet loss or packet reordering is low.
• RTP: This protocol is based on UDP but uses extra header
information such as sequence numbers and timestamp. This to
compensate for jitter and packet reordering.
It is advised to use RTP in more complex networks.
• RTP FEC: This is the RTP protocol with additional Forward Error
Correction, to make the transmission even more robust.
UDP Port Define the UDP port for reception of the data.
Data can enter the device via any interface specified in the network
configuration.
Unicast and multicast are possible. Please refer to section
Data IP Connectivity. on page 114
In case of multicast refer to section:

Configure the Multicast IP Address. on page 119
Buffer Delay Indicate the amount of jitter to be absorbed by the device.
Input Rate Type Select one of the following:
User Defined: The user enters the input rate manually. The bitrate
should be correct within 30 ppm for proper behavior of the control loops
(NTC and DVB).
PCR: The device will use the PCR values to determine the input bitrate.
If the PCR values have a good precision, this rate estimation will be
adequate to start the control loops.
Input Bit Rate Enter the bit rate, this value should be correct within 30 ppm for proper
behavior of the control loops ( NTC and DVB).
Auto PCR Detection The device looks randomly for a PCR stream that gives consistent rate
values.
Control Loop Type This parameter allows the user to define how the device will minimize the
TS jitter on its inputs. See Control Loop Type [None, NTC, DVB] on page 368.
Bind Mode Select one of the following:
Unbound: No binding is created for this UDP Port. In this mode every
UDP port must be unique.
Bound On Multicast: Bind an UDP port with a specific multicast IP
Address. This mode, provides the possibility to receive different
multicast IP streams on the same UDP port.
Bound Address Select the appropriate multicast IP instance to link the input stream.
To configure a multicast IP instance please refer to section:
Configure the Multicast IP Address on page 119 .
» Click Update to save the TS over IP input stream settings.

18.2.2.2 Monitoring Table
Name Displays the TSoIP input stream

name that is being monitored.
Operational Operational: The TSoIP input

State interface is receiving data as
expected.
Failed: A problem exists on the Check the alarm status table and
TSoIP input interface. also the corresponding monitoring
parameters to troubleshoot the
failure.
TS Input Bit Displays the current input bit rate.

Rate
Offset Indicates the difference between the When the offset becomes to large, a
incoming and the configured bit rate buffer underflow or overflow will be
in ppm. detected.
Buffer Indicates the amount of jitter that is

Delay currently absorbed by the device.
Minimum The minimum buffer delay measured

Buffer value over a time interval.
Delay
Maximum The maximum buffer delay When the buffer cannot compensate
Buffer measured value over a time interval. for the incoming jitter the maximum
Delay buffer delay ramps up and at a
certain point generates a buffer
overflow alarm.
Source Info Displays the IP and UDP port of the

source device that is streaming the
transport stream.
RTP FEC Indicates the FEC scheme applied

Scheme on the incoming transport stream.
TS Drop Displays the number of dropped

Count Transport Stream packets.
RTP Drop Displays the number of dropped RTP

Count Packets.
RTP Repair Displays the number of repaired RTP

Count packets by using the FEC
information.
Active PCR Displays the active PCR PID.

PID

18.2.2.3 TS over IP In Alarm Status Table
Input Data Green: Data traffic is detected on this

input interface
Red: No data is detected on this • Check if the UDP port is

input interface. configured correctly.
• Check if the source device is
sending any data traffic towards
this TSoIP input interface.
Buffer Green: The de-jitter buffer does not

Underflow run out of packets.
Red: The de-jitter buffer runs out of • Check input rate setting and
packets. increase buffer delay, if needed.
Buffer Overflow Green: The de-jitter buffer is not

overloaded with packets.
Red: A packet overflow is detected in • Check input rate setting and

the de-jitter buffer. increase buffer delay, if needed.
No RTP Sync Green: Valid RTP input data is

received.
Red: No valid RTP input data is • Check the configuration of the

received. source device.
Buffer Delay Green: There are no problems with

too High the throughput towards the next
functional block in the device.
Red: The value for the Buffer Delay,

when translated into a number of TS
packets, leads to a value larger than
the physical buffer available. This
can occur at high bitrates or at high
Buffer Delay values.

18.2.3 Configure TS Redundancy

TS redundancy allows to create active/standby redundancy scenarios. In this case one stream
serves as backup for the other stream.
In case an alarm is detected on the active stream and no alarm is detected on the backup stream, a
redundancy switch is performed to the backup stream.
Configure
» In the overview pane click TS Redundancy.

» Click Add

Name Enter a logical name.

For example ASI1 <--> ASI2, expressing that ASI1 and ASI2 are used to
create a redundant link.
Enable Enable or disable the redundant link.
Input A Type Select from which functional block we take in the first stream:
– ASI IN: The transport stream is received on an ASI input interface.
Input A Name Select the exact input interface that is used as the first stream.
– ASI-1
Input B Type Select from which functional block we take in the second stream:
– ASI-IN: The transport stream is received on an ASI input interface.
Input B Name Select the exact input interface that is used as the first second stream.
– ASI-2
Switching Mode Select the correct switching mode.

• Automatic: This is the preferred method.
• Manual:
– During configuration of the system setup, this avoids continuous
switching between the two streams.
– During maintenance.
– In case the system setup is controlled by a Network Management
System via SNMP.
Protection • Revertive: Select this when one of the inputs (A and B) has priority. This
Mode means when the preferred input returns to normal mode, the data will be
taken in on this interface.
• Non-revertive: Select this when no priority between the inputs (A and B) is
required.
In this case, when an input returns to normal mode there will be no
"switch" to the other interface.
Preferred TS Select either Input A or Input B to be the input with highest priority.
Input

» Click Update.
Note that it is possible to create TS active/standby scenarios between different input

types. This allows to create TS redundancy between two ASI input interfaces,
between two TS over IP input interfaces but also between an ASI input interface and a
TS over IP input interface.
Make sure to create TS Redundancy using correct input streams!
» Click Update to save the new redundancy rule.

18.2.4 Configure the TS Connections

Use this functional block to configure the connections between the available input and output
interfaces.
The configuration is done by creating a connection rule, connecting input interfaces with output
interfaces. Any available input interface can be connect to any available output interface, this way
lots of flexibility is created. The available possible combinations are displayed by the device as a
guidance during configuration.
For example
• Connect the TS Redundancy block with the Modulator Output.
» Click on TS in the "Connections" functional block.
» Click Add to configure a new connection.

Name" Enter a logical name.
From Type Select from which functional block we take in the stream:
– TS Redundancy: The transport stream is received on the TS
Redundancy block.
From Name Select the exact input interface that needs to be connected.
– Protect-1
To Type Select on what output interface you want to make the transport stream
available.
– Modulator: The transport stream is forwarded to the modulator.
Here the data is modulated according to the system
requirements. Defining the output frequency, modulation mode
and accordingly the available MODCOD.
To Name The available modulator is directly entered.
» Click Update to save the new connection.

18.2.4.1 TS Stream Overview
Once a connection for a particular stream is configured, the Connections functional block allows to
display the complete flow of the transport stream through the device.
The functional block "Connections" allows two options to display the TS Stream Overview.
Option 1:
» In the overview pane click on TS in the Connections block.
» Select the connection to be displayed.
Option 2:
» In the overview pane click on TS in the Connections functional block.
» Select Show All (to view all available transport streams).
» Click on the icon in front of the Name to display the stream overview.

Result
18.2.4.2 Delete a Connection
» Delete a connection by clicking on the "X" icon in front of this connection.
The following warning is displayed: Are you sure you want to delete this entry?
» Click Delete to confirm the deletion.
» Click Cancel to ignore the deletion.

18.2.5 Modulator
18.2.5.1 Modulator ConfigurationTable
The modulator functional block is used to perform the modulation of the incoming data received on
an input interface.
Configure the parameters of the modulator in such a way that all transmission parameters are
according to the system setup requirements.
» Click on the functional block to open and configure the parameters in this functional block.

MCX7000 >> Modulator >>

Mode Select the modulation mode DVB-S, DVB-S2 or DVB-S2X.
Stream Mode Select the appropriate stream mode.

• Single Stream
• Multistream
Transmit This is the modulator output transmission.
Enable transmit when the complete configuration is done according to
the system requirements.
A warning is displayed when it is not allowed to change a

parameter when transmit is enabled.
This will be the case with parameters that influence the
transmitted signal and its spectrum.
Output Frequency Set the output frequency of the modulator. The output frequency must
and Output Band be in-line with the device capabilities (L-band or IF band) and the
system requirements.
• L-band: 950 MHz to 2150 MHz
• IF-band: 50 MHz to 180 MHz
The device performs a check whether the inserted frequency is within
the allowed frequency range.
Roll-off Select the appropriate roll-off factor:
• 35% (DVB-S only) • 15% (Clean Channel Technology®)

• 25% • 10% (Clean Channel Technology®)
By lowering the roll-off factor and accordingly increasing the symbol rate,
the throughput can be increased while maintaining the same occupied
(leased) bandwidth.
Occupied bandwidth = Symbol Rate*(1 + roll-off factor).
Spectrum Polarity Spectrum inversion can be enabled in case an inverting up converter is
used. As a general rule transmissions on satellite need to be direct.
Output Level Modulator output level setting in dBm.
Adjustable in steps of 0.1 dBm.
Carrier Modulation This command controls the carrier modulation:
• On (Operational modulated carrier signal)
• Pure Carrier
The pure carrier is used during line-up and to perform

cross polarization tests with the satellite operator.
• Test modulation settings are used for calibration and/or verification of

the spectrum polarity.

Amplitude Slope An amplitude slope in the up-converter or in the high power amplifier
Equalizer can be compensated by using this equalizer.
The equalizer has a maximum range of ± 2 dB/50 MHz.
The compensation can be set in the range between -7 and +7.
Rate Priority Define the rate priority.
• Symbol Rate
• Bit Rate
Rate Priority is not displayed when the selection of the

Stream mode = multistream.
Symbol Rate Set the symbol rate in Mbaud.

This parameter can only be set if the setting Rate Priority = Symbol
Rate.
Bit Rate Set the bit rate in bps (bits per second).
This parameter can only be set if the setting Rate Priority = Bit Rate.
When using the PRBS generator (and no rate adaptation

is applied) the PRBS generator automatically slaves to
the resulting bit rate of the modulator output.
(The rate can thus not be set.)
ACM Mode Select between ACM and CCM. (Adaptive Code Modulation and
Constant Code Modulation.)
Do not forget to enable Transmit when all parameters are set.
18.2.5.2 DVB-S Specific Settings
18.2.5.2.1 Modulation and Coding
Define the MODCOD and FEC that can be used.
In case the stream mode = multistream than a MODCOD and FEC is selected in the
multistream output block. Please refer to the
Configure the Multistream Output on page 231.

18.2.5.3 DVB-S2 / S2 Extensions Specific Settings
Depending on the chosen modulation mode the DVB-S or DVB-S2, DVB-S2X a different
configuration table is displayed.
MCX7000 >> Modulator >>
Frame Type • Normal Frames (64800 bits)

• Short Frames (16200)
DVB-S2 and DVB-S2X applies the error correction coding and the modulation
to large frames of data called baseband frames. A baseband frame is either
16200 bit (short frames) or 64800 bits (normal frames). The content of a
frame can be a section of a transport stream or any type of data, framed or
unframed (Generic Stream°.
MODCOD Define the MODCOD and FEC that can be used.
Pilots Define if it is needed to insert pilots or not.

• Use pilots to increase the reliability of the receiver synchronization.
(Increasing the performance and robustness of the demodulator).
• Pilots reduce the influence of phase noise in the system.
Typically the LNB on the receiving side is the main source of phase noise.
• Use pilots at low data rates.
• Use pilots when distortion is present on the signal, for example due to
non-linearity.
Dummy PL When bursty traffic (like IP) is transported, the physical layer can run out of
Scrambler Mode data to transmit. In that case dummy physical layer frames are transmitted in
order to keep the receiver locked.
There are two possible modes to perform scrambling of the dummy physical
layer frames.
• DVB-S2 Standardized Reset (reinitialized):
In this mode the randomization sequence is reinitialized at the end of
each dummy physical layer frame header.

• Continuous:
In this mode there is no re-initialization at the end of each dummy
physical layer frame header.
This is done to achieve more randomness in the dummy physical layer
frames (carrier data) as desirable for bandwidth cancellation. The
bandwidth canceller needs randomization in order to measure the time
delay between the transmitted and the returned signal.
This Continuous mode is only valid for the dummy physical

layer frames!
The Continuous mode is not DVB compliant.

As a consequence it is possible that some non-Newtec
demodulators are not capable of working with this mode.
Physical Layer In case of broadcasting services, the PL Scrambler Signature = 0 shall be

Scrambler used as default sequence, this to avoid manual receiver setting or
Signature synchronization delays.
Roll-Off • Standard : (2 bits : "10") roll-off signaling value is used for roll-off <= 20%;
Signaling
• Reserved : (2 bits: "11") roll-off signaling value is "reserved" (11) is used
for roll-off < 20%.
Some DVB-S2 receivers can use the received roll-off bits state '11' for
selecting a 15% roll-off filter.
In this case, it is favorable to choose the setting "reserved".In all other cases,
it is recommended to use the setting "standard" as this will guarantee
compatibility with DVB-S2 receiving equipment.
For more information on Physical Layer Scrambling, refer to the DVB-S2 standard:
ETSI EN 302 307.

18.2.5.4 Transmit Control
The transmission control parameters allow you to alter the default behavior of the transmitter.
Be careful when changing the default settings.

General Device Alarm Define the impact of this alarm on the transmission.
• Disable Transmit (default value)
• No Impact
General Interface Alarm Define the impact of this alarm on the transmission.
• Disable Transmit (default value)
• No Impact
Allow Changes while TX On • Disabled (default value):

It is not possible to change modulator settings until the
current transmission is disabled.
• Enable:
it is possible to change modulator settings while the
modulator is transmitting.
The following picture shows the parameters impacted by the parameter Allow Changes While TX
On.
Disabled Enabled

18.2.5.5 DSNG Profiles Configuration Table
The MCX7000 Multi-Carrier Satellite Gateway has preconfigured parameters defined that can easily
be set. The preconfigurations are aligned with the DSNG profiles that are designed and proposed by
the WBU-ISOG (World Broadcasting Unions) (International Satellite Operations Group).
The profiles are designed to provide a faster acquisition in the field by minimizing the number of
parameters that both uplink and downlink operators have to agree on prior to transmission.-
The profiles include:

• All parameters required for RF signal acquisition and to ensure a full lock at the MPEG-2
transport stream level.
• The support for one video and four pairs of audio.
The following figures show the difference between the amount of communications required to
establish a DSNG link:
• Without use of the DSNG profiles. In this case there is a need of about 16 communications.
With use of the DSNG profiles the amount of communication steps is reduced to about 4.

Please refer to Appendix - DSNG Profiles Preconfigured Settings on page 396 to get an

overview of all preconfigured parameters.
Location
Navigate to the following location to configure the correct DSNG profiles.
MCX7000 >> Modulator >> DSNG Profiles Configuration Table

For example, select News9 and Level Extended:
Profile Name News9
Level 4 Extended
RF Coding DVB-S2X
Order of Modulation 16APSK-L
FEC 13/18
Symbol Rate (Mbaud) 8.571
Pilots Symbol Yes
Frame Length Normal
Resulting Transport 23.967

Rate (Mb/s)
Occupied Bandwidth 9
(MHz)
Roll-off Factor 1.05
Receiver Threshold 9.70

(Es/No)
C/N allocated 9.50

bandwidth

18.2.5.6 DVB-CID Configuration Table
The DVB carrier identification standard is used to reduce RFI (Radio Frequency Interference). The
DVB carrier identification allows the satellite operators to identify and contact the source of
interference quickly.
The DVB-CID exists of a device global unique parameter and device variable parameters.
Via the overview page:
» Click on the Modulator functional block.
» Scroll Down to DVB-CID Configuration Table.
18.2.5.6.1 Device Global Unique ID
• The Global Unique ID is a device unique identifier that is based on the MAC address of the
modulator.
18.2.5.6.2 Device Variable Parameters
The device variable parameters can be adjusted by the operator.

The geo coordinates indicates the current position of the modulator.
When "Use Geo Coordinates" is enabled On, the latitude and longitude information is added to
ETSI Carrier ID.
The telephone number makes it easier for satellite operators to contact you in case of emergency. It
is possible to enter the extension number of the department or person that is responsible for the
system configuration.
For example: +32 3 780 65 00 ext. xxxx. (With xxxx the correct extension number.)

To enter the geo coordinates and the operator identification parameters (telephone number) open
the device management functional block.
Be aware that ext. is case sensitive.

The user data can be used to enter free text, it is possible to enter up to 24 characters.
For example: Enter the name of the company that is responsible for the uplink.
ETSI Carrier ID Format: At this moment only one format exists and by default the parameter setting
is 1.
18.2.5.6.3 How does it Work?
The ETSI Carrier ID is transmitted within the uplink RF carrier as a spread spectrum signal below the
the carrier.
The ETSI Carrier ID information is independent of the payload of the carrier being identified.

18.2.5.6.4 What to do when Interference is Detected?
» Contact your satellite operator.
» The satellite operator has the right equipment to filter out the Carrier ID Information.
» Your satellite operator identifies who is responsible for the interference and takes contact with
the other satellite operator to alert them of the interference.

18.2.5.7 Modulator Alarms Status Table
Input Green: An input signal is detected.

Signal
Red: No input signal is detected at • Check if a connection is created
the input of the modulator. between the modulator and one of
the following:
– TS Connections
(single stream)
– Multistream output
Buffer Green: No buffer underflow

Underflow detected.
Red: The input data buffer to the • Check the input bit rate and the
modulator is empty. configured bit rate in the
modulator.
Buffer Green: No buffer overflow detected.

Overflow
Red: The input data buffer of the • Check the input bit rate and the
modulator is full. configured bit rate in the
modulator.
Input Green:Input frames are in sync.

Frame
Sync Red: Indicates loss of input framing This can be triggered by a buffer
on the incoming data of the underflow or overflow alarm.
modulator.
Calibration Green: Calibration data is valid.

Data

Red: There is no calibration data Please contact the customer support

available in the modulator. center.
Potentially this overcompensates the
transmit output level.
Invalid TS Green: The measured input TS bit

Bit Rate rate and the configured bit rate is
within 30 ppm.
Red: The difference between the • Check the input bit rate and the
measured input TS bit rate and the configured bit rate.
configured bit rate is higher than 30
ppm.
Internal Green: No failure detected.

Failure
Red: An internal failure is detected Please contact customer support
on the modulator board. center.

18.3 Block Diagram Single Stream Demodulator

The block diagram shows the data flow through the device when a single stream is received by the
demodulator.
» Click DTH Demodulator:

The following window is displayed.
Input Interfaces
Name Description
Demodulator Configure the RF parameters of the demodulator to get an Rx Lock on the RF

carrier that you want to receive.
Once the receiver is locked to the incoming signal, the Rx Lock LED at the
bottom right of the GUI is checked. The BBFs are directly forwarded to the
Connections functional block.
TS Generator Please refer to TS Generator. on page 271

Output Interfaces
Name Description
ASI Determine on which ASI output interfaces the transport streams should be
sent out.
To configure the direction (input/output) of the ASI interfaces please refer to
section ASI Interfaces on page 125
TS over IP Add and configure the logical output interfaces that are required for your
setup.
Configure the encapsulation protocol, the destination IP address and the
destination UDP port.
Connections
Name Description
TS Configure this functional block to make a connection between one of the

available input interfaces and one of the available output interfaces.
It is possible to create redundant outputs by connecting the incoming
transport stream to different output interfaces (modulator, ASI Out and/or
TSoIP out).
Note that the TS over IP logical output interfaces must be created first before it is
possible to make a connection between the incoming transport stream and the TS
over IP logical output interfaces.

18.3.1 Demodulator
The demodulator functional block is used to perform the demodulation of the incoming RF signal.
Configure the parameters of the demodulator in such a way that RX Lock is achieved.
» Click on the functional block to open and configure the parameters.

(Select the demodulator that must be configured.)

The following window is displayed:

18.3.1.1 Demodulator Configuration Table
Enable By setting the Enable parameter either "off" or "on" you activate or de-activate
the demodulator.
Mode Set the demodulation mode:

• DVB-S • DVB-S2X
• DVB-S2
Stream Mode • Single stream

• Multistream
Input Set the input frequency of the demodulator. The input frequency must be
Frequency in-line with the device capabilities and the system requirements.
• L-band: 950 MHz to 2150 MHz
The device performs a check whether the entered frequency is within the
allowed frequency range.
Symbol Rate Define the symbol rate in Mbaud.
Acquisition Define the amount of frequency uncertainty the demodulator will search over
Range in order to find and lock to an incoming carrier.
Interface Rate Displays the measured bit rate on the input interface.
Roll-Off The possibilities are:

• Auto: The demodulator automatically selects the appropriate roll-off factor.
The selected roll-off factor is displayed in the monitoring table.
• 25% • 10% (Clean Channel Technology)
• 20% • 5% (Clean Channel Technology)
By lowering the roll-off factor and accordingly increasing the symbol rate, the
throughput can be increased while maintaining the same occupied (leased)
bandwidth.
Occupied bandwidth = Symbol Rate*(1+Roll-Off factor).
Spectral Define if spectral inversion is detected automatically or set manually.

Inversion When spectral inversion is known, it is advised to set it manually as (re)lock
time will decrease.
PL Scrambler The following information about the Physical Scrambler

Signature Signature is taken from the DVB-S2 standard. Refer to the
following document, ETSI EN 302 307.
In case of broadcasting services, the PL Scrambler Signature = 0 shall be

used as default sequence, this to avoid manual receiver setting or
synchronization delays.

The PL Scrambler Signature, assuming values in the range 0 to 262 141,

indicates the spreading sequence number. The use of different PL Scrambling
sequences allows a reduction of interference correlation between different
services. For the same purpose, it is possible to reuse a shifted version of the
same sequence in different satellite beams. Furthermore, the PL Scrambler
Signature can be associated to each satellite operator, satellite, or
transponder, thus permitting identification of an interfering signal via the PL
Scrambling "signature" detection. There is no explicit signaling method to
convey the PL Scrambling signature value to the receiver.

18.3.1.2 Backup Carrier
These settings are implemented to migrate a system setup from frequency 1 and symbol rate 1
(current) to a new frequency 2 and symbol rate 2 (new).
Configure these settings on the demodulator/modem of the remote sites when the modulator/modem
on the hub site has to change to a new carrier.
When this new carrier becomes active, the complete network is switched to this backup carrier
configuration.

The following procedure is performed in the network.
Time HUB Remote Site(s)
Start Transmit on: The remote site is locked on:

• Frequency 1 • Frequency 1
• Symbol rate 1 • Symbol Rate 1
Preconfiguration Transmit on: The remote site is locked on:
• Frequency 1 • Frequency 1
• Symbol rate 1 • Symbol Rate 1
Pre configure the remote site as follows:
» Backup Carrier Enable: Enable (arm the switchover);

» Configure the backup carrier input frequency =
Frequency 2
» Configure the Carrier Symbol Rate = Symbol Rate 2

» Configure the Carrier Switch Timeout
Carrier switch Transmit on: 1. The remote site loses lock (Demod alarms are not visible
during Carrier Switch Time).
• Frequency 2
2. The remote site tries to connect with the Back carrier
• Symbol rate 2 input frequency (Frequency 2, symbol rate 2).
3. The remote site is locked on frequency 2, symbol rate 2.
The network is Transmit on: 1. The remote site is locked on frequency 2, symbol rate 2.
stable
• Frequency 2 2. Disable the Backup Carrier Enable setting.
• Symbol rate 2 Disabling the Backup Carrier Enable

Saves the Backup Carrier Input
Frequency to the demodulator Input
Frequency.

18.3.1.2.1 Configure the Backup Carrier
Location
Setting Description
Enable Use this to arm the switch between the main input frequency
and the backup carrier input frequency.
Input Frequency Preconfigured RF input frequency.

The demodulator tries to lock onto this frequency when a
Demodulator No PL Lock alarm is generated.
Symbol Rate Preconfigured nominal symbol rate.

The demodulator tries to lock with the preconfigured symbol rate
when a Demodulator No PL Lock alarm is generated.
Switch Timeout This is the time interval (in seconds) between consecutive
demodulator carrier switch operations.
When this time is to short the device is unable to
connect to the other frequency and can result in
permanent loss of satellite link connection.
By default this is 60 seconds.
The next sequence is followed on the remote site.

When the demodulator/modem on the remote site looses connection (unlock) with the current
frequency a switch is performed to the other frequency.
When the demodulator is not locked within the Carrier Switch Timeout the second frequency is tried.
This sequence continues until the demodulator is locked.

18.3.1.2.2 Make the Backup Carrier Permanent
Once the system setup is in a stable situation and the migration to the new frequency is (backup
frequency) is performed
Once the system setup is migrated to the new frequency (backup frequency) it is possible to make
the backup frequency permanent. This means that it becomes the main frequency. To do this:
» Disable the Backup Carrier Enable setting.

The backup carrier input frequency value is written to the input frequency.
» Save the configuration (please refer to section: Save a Configuration on page 337 .

18.3.1.3 Demodulator Monitoring
18.3.1.3.1 Monitoring Parameters
The monitoring parameters provide a global overview of the incoming signal.

L-Band Input This indicates the power level measured over the total input range in dBm.
Level
Carrier Input This indicates the measured power level of the carrier. When the carrier uses
Level a part of the transponder, the measured level is smaller than the value
measured for the total input range.
No linearity This value gives an indication of the non-linearity of the carrier.

Indication
Symbol Rate Displays the symbol rate measured on the input interface.
Carrier Offset Displays the frequency offset between the actual (tracked) frequency and the
set frequency.
Operational Displays the actual operational state of the demodulator.

State • Operational: The demodulator is in use.
• Failed: One or more alarms are present which effect the proper
functioning of the demodulator.
Roll-off Displays the selected roll-off factor, this is use full when auto roll-off selection
is used.
Spectral
Inversion
Link Margin This monitoring parameter indicates how much the C/N or Es/No (including
the distortion) is above the decoding threshold.
It is a measure for the number of dBs of fading that is possible on the satellite
link before the demodulator is not able to decode the received signal
anymore.
Clipping will happen if the Es/N 0 of the stream is too high, this is indicated with
the following symbol >.

18.3.1.3.2 DVB-S2 Monitoring Table
Es/No Header Signal to noise ratio of the satellite link.
Phase Noise Phase noise indication (expressed in degrees).

Indication
Offset To please refer to the Offset to Reference Mask on page 197.

Reference
Mask
Frame Counter Displays the amount of incoming frames.
Dummy PL Displays the amount of dummy physical layer frames that are transmitted
Frame Counter over the satellite link.
Errored Frame Displays the amount of incorrect frames.

Counter
It indicates that the link margin is too low, that channel distortions due to
saturation or non-linearity caused the decoder to be unable to correctly
decode frames.
Cycle Slip A cycle slip occurs when the symbol phase tracking loop fails.
Frame Counter Cycle slips indicate that system phase noise affects performance.
Phase discontinuities due to local oscillator stability issues will also be
reflected in cycle slips.

Last The most recently seen MODCOD.

non-dummy
MODCOD
The following is formula is applied:

Integrated Phase Noise (degr) / Reference Mask Phase Noise (degr).
This monitoring parameter compares the 'Integrated Phase Noise' estimator
with a reference phase noise mask. The mask is considered as what can be
achieved for a professional grade system.
The reference used is :
Frequency Phase Noise level [dBc/Hz]
Worst Case Reference Target Value
10 Hz -27 -32.9
100 Hz -45 -61.9
1 kHz -65 -78.7
10 kHz -75 -88.7
100 kHz -89 -94.8
1 MHz -102 -105.7
10 MHz -112 115.74
> 50 MHz -117.7
The reference phase noise is integrated within the correct bandwidth (the
bandwidth used by the phase noise estimator). The Phase noise estimator is
compared to the reference and the difference is expressed in dB.
The target value is about -4 to -14 dB better than the

reference.

18.3.1.3.3 MODCOD Statistics
The following figure shows the overview of the MODCOD Statistics in the graphical user interface.

The previous figure shows the MODCOD Statistics linked to a Spectrum Analyzer Measurement.
MODCOD This monitoring parameter displays the detected modulation and FEC used
for each of the DVB-S2(X) streams in the received carrier.
Frame Counter This monitoring parameter displays the number of baseband frames that are
decoded by the demodulator board for each of the DVB-S2 or DVB-S2X
streams in the received carrier.
Errored Frame This monitoring parameter displays the number of uncorrected baseband
Counter frames by the demodulator board for each of the DVB-S2 or DVB-S2X
streams in the received carrier.
It indicates that the link margin is too low, that channel distortions due to
saturation or non-linearity caused the decoder to be unable to correctly
decode frames.
Cycle Slip A cycle slip occurs when the symbol phase tracking loop fails.
Counter Cycles slips gives the indication that system phase noise affects
performance.
Phase discontinuities due to local oscillator stability issues will also be
reflected in cycle slips.
Packet Error This parameter displays the packet error ratio of the received or DVB-S2X
Ratio streams.
Link Margin This monitoring parameter indicates how much the C/N or Es/No (including
the distortion) is above the decoding threshold.
It is a measure for the number of dBs of fading that is possible on the satellite
link before the demodulator is not able to decode the received signal
anymore.
Clipping will happen if the Es/N 0 of the stream is too high, this is indicated
with the following symbol >.
C/N C/N or Carrier-to-Noise ratio.
This value (in dB) is a measure of the received carrier strength relative to the
strength of the received noise.
C/D C/D or Carrier-to-Distortion.
This value (in dB) is a measure for the distortion due to linear and non-linear
degradation that is present in each of the DVB-S2 or DVB-S2X streams in
the received carrier.
C/ND C/ND stands for Carrier-to-noise + distortion.
The actual carrier to noise level by taking into account the effect of distortion
(C/D).
This value (in dB) is a measure of the received carrier strength relative to the
strength of the received noise with distortion added.
This measurement reflects the channel quality.
The link margin clipping will indicate "<" or ">" when the link margin value is too low
or too high to be accurately determined. In case it is too low, the link margin might be
too low in order for the detector to operate correctly. With the link margin too high,
there might not be enough decoding errors in order for the detector to display a
meaningful value.

18.3.1.4 Demodulator Alarm Status Table
In the following table the available alarms are explained.
Internal Error This alarm is raised when there is an internal error demodulator alarm.
L-band Input This alarm indicates that the L-band input power is too high.
saturation
Physical Layer The demodulator cannot lock to the physical layer headers.
Lock
Lock The demodulator cannot lock onto the received carrier.
LNB power This alarm is raised when an error occurs in the LNB power supply.
supply
For example when a short circuit is present on the output connector with the
LNB power supply. Verify the connection to the LNB power supply.
Decoder This alarm is raised when the decoder of the demodulator is overloaded.
overloaded

18.3.2 TS Redundancy
Please refer to section TS Redundancy on page 160 .
18.3.3 Configure the ASI Output Interfaces

This functional block allows you to enable the available ASI output interfaces.
To configure this functional block:
» Click on the functional block and then click Show All:

Note: When no entries are available, configure the ASI Interfaces Direction, please see section:
» Select Enable On, to activate the output interface.
» Click Update to enable the output interface.

18.3.3.1 Monitoring the ASI Output Interfaces
Use the monitoring table to perform troubleshooting on the output streams.
Name The name represents the corresponding physical ASI interface.
Output Rate Displays the output rate on this ASI interface.
Operational State Displays if the output interface is active or not.
18.3.3.2 ASI Output Alarm Status Table
No Output Green: The signal is available on

the output.
Red: This alarm is triggered if Check if a connection rule is

there is no signal is sent to the defined between the input and
output of the device, while the this ASI output interface.
output is enabled.
Output Green: There is no overflow

Overflow detected on this output interface.
Red: This alarm is raised when Decrease the bit rate.

the bit rate send out is higher than
the maximum possible (213
Mbps).

18.3.4 Configure the TS over IP Out Interfaces

This functional block allows you to configure up to eight logical output interfaces.
A logical output interface is used to forward the transport streams over IP. The physical data ports
used by the logical interfaces are the Ethernet interfaces Data1 and/or Data2.
Next to enabling the logical interfaces, it is required to select the encapsulation protocol, to configure
the destination UDP port and the destination IP Address.
Furthermore it is possible to define how much TS packets can be inserted into the UDP frame.
To configure this block:
» Click on the functional block TS over IP output and then click Show All.

18.3.4.1 Add a TS over IP Output Interface
» Click Add to insert a new TS over IP Output Interface.
Name Enter a logical name for this interface.
Enable Select On to activate this logical output interface.
Encapsulation • UDP: It is advised to use the UDP protocol only in simple IP
Protocol networks where jitter, packet loss or packet reordering is low.
Destination UDP Define the destination UDP port.
Port
Destination IP The destination IP Address can be unicast or multicast.
Address
In case the destination IP Address does not belong to a directly
connected subnet, the device doesn't know to which output (data 1/2)
the signal must be forwarded. Configure the routing table to define which
data interface to use. See Data IP Connectivity on page 114
Note:When using multicast the routing table always needs be
configured to express the proper interface to be used.
Multicast TTL In case of a multicast IP address define the time to live. The Time to live
value informs a network router if an IP packet is in the network too long.
Every time the packet passes a network router the value is subtracted
with one. When the count reaches zero, the router detecting it discards
the IP packet and sends an Internet Control Message.
TS Packets in UDP The packing of transport stream packets into one IP packet is restricted
Frame to a maximum of seven TS packets.

» Click Update to save the new TS over IP Output interface.

Once the TS over IP Output interfaces are configured it is possible to make a connection between
the input and TS over IP output interfaces.

18.3.4.2 TS over IP Output Monitoring Table
Name This is fixed and represents the corresponding logical TS over IP output
interface.
Output Bit Rate Displays the output rate on this TS over IP output interface.
Drop Counter Displays the amount of dropped TS packets.

18.3.4.3 TS over IP Output Alarm Status Table
No Output Green: The TS over IP interface is

active.
Red: This alarm is triggered if there • Check the IP connectivity.

are no packets sent to the destination
device, while the output is enabled.
Output Green: There is no overflow detected

Overflow on the output interface.
Red: Indicates a buffer overflow on

the output interface.
18.3.4.4 Delete a TS over IP Output Interface
» Delete a TS over IP Output interface by clicking on the "X" icon in front of this output interface.
18.3.5 Connections
This functional block allows you to configure the connections between the available input interfaces
and output interfaces.
For example:
• The demodulated incoming streams and the TS over IP output interfaces.
• The demodulated incoming streams and the ASI output interfaces.

» Click Add the following window is displayed:

(For example: Demod <--> ASI4 , expressing the following rule, this
connection takes in the demodulated stream and connects it with the
ASI4 output interface.)
From Type From which functional block do we take in the stream:
– Demodulator: The transport stream is directly forwarded by the
demodulator functional block.
From Name Select the input that needs to be connected.
(For example: Demod-1)
To Type Define on what interface you want to make the transport stream
available.
– ASI OUT: The transport stream is forwarded to ASI output
interfaces.
(Note, other available output interface types are also displayed.)
(Note incase you want to make a connection to a TSoIP output interface
this TSoIP Output must be created first. Please refer to previous
section.)
To Name Select one of the available ASI output interfaces.
The table dynamically shows the available inputs corresponding with the
Type Name that is selected in the previous parameter.
» Click Update

Option 1:

Option 2:

Result:



18.4 Block Diagram Multistream Modulator

The block diagram shows the data flow through the MCX7000 when you want to create a
multistream Modulator.
ASI Input Interfaces

Use this block to configure the ASI input interfaces.
It is possible to:
• Enable or disable the ASI input interfaces.
• Select the appropriate framing. (188 or 204).
• Indicate if an in-line splitter is used (3 dB or 6 dB attenuation).

TS over IP Input Interfaces

The MCX7000 has two physical data interfaces where it is possible to create logical input and output
interfaces.
Add and configure the logical input interfaces that are required for your setup.
received.
Furthermore select the encapsulation protocol and configure the input rate mode parameters.
Jitter will be minimized, i.e. output rate is virtually constant and jitter from the IP network is
eliminated.
TS Redundancy
This block allows to create active/standby redundancy scenarios. In this case one stream serves as
backup for the other stream.
Multistream Output
Configure the parameters in this block to create a multistream carrier.
To do this configure each incoming transport stream with a unique input stream identifier (ISI).
Once the ISI is assigned to the transport stream the data is processed in separate baseband
frames. Each stream can be modulated with its own set of parameters.
These base band frames are time-multiplexed to create the multistream carrier.
Furthermore the multistream output block allows to enable the ISSY (Input Stream Synchronizer).
When enabled, the ISSY insertion provides a means to regenerate the clock of the transport
streams in order to guarantee end-to-end constant bit rates and delays.
Also Null packet deletion can be enabled, this is frequently done to save bandwidth. When enabled
the MPEG null packets are deleted and replaced by a tag that indicates the number of null packets
that have been deleted. The tag is used by the receiver to reproduce the same amount of null
packets, this in order to keep bit rates and the end-to-end delay constant.
Once these parameters are configured it is possible to define the output type and output name of the
multistream.
By default, the Output type is, modulator and the output name is modulator-1.
The MCX7000 allows to configure up to maximum eight streams.

Connections
Configure this functional block to make connections between the available input interfaces and one
of the available outputs interfaces.
For example:
• ASI Input to Multistream Output
• TS over IP Input to Multistream Output
• ASI Input to TS over IP Output (do this for example to monitor the incoming ASI stream)
Note that the output interfaces must exist before it is possible to make a connection
between the input and output interfaces.
Make sure that the required, multistream output, ASI output and TS over IP output
interfaces are configured.
Modulator
Configure the RF parameters of the modulator according to the system setup.
Define the output frequency, the symbol rate, the roll off factor and output level of the modulator.
When this is done and the transmit parameter is enabled, the TX On LED (bottom right of the GUI)
should light up green.

18.4.1 Configure the ASI Input Streams

» In the overview pane click on ASI.
Note: When no entries are available, configure the ASI Interfaces Direction first, see:
» Click Show All (to view all ASI input interfaces).

» Click to configure the ASI incoming streams.

Name Displays the name of the ASI interface.

(Read Only).
Enable Enable or disable the ASI interface.
In-line Splitter Use this parameter to compensate for an attenuation that is present due to the
use of an external passive splitter. It is possible to compensate for 3 dB or 6
dB attenuation.
When a passive splitter is used and this compensation is not enabled, the
incoming signal might be degraded too much so that a correct modulation
cannot be guaranteed.
Input Framing The incoming packets can be:

• TS188 (transport stream with 188-byte packets).
• TS204 (transport stream with 204-byte packets, 188 bytes with 16 bytes
for error correction).
The 16 bytes for error correction (overhead) are removed

before the actual modulation takes place.
When the incoming packets are not corresponding to the configured framing
type, the following alarm is generated: ASI IN No Input Signal ASI 1.
» Click Update.

18.4.1.1 ASI Monitoring Table
The monitoring table indicates the input rate and the operational state.
18.4.1.2 Alarm Status Table

Input Green: The ASI interface is physically
Signal connected.
Red: The ASI interface is not Check the cabling.
connected.
Input Data Green: Data is received on this
interface.
Red: No data is received on this Check if the source device (encoder,
interface. multiplexor, ...) is activated.
Data Error Green: Data received is in the correct
format.
Red: • No data is received, please check
one of the previous causes.
• No data is receive.
• Check the input framing.
• Data is received but not in the
correct format.

18.4.2 Configure TS over IP Input Streams

This functional block allows you to configure up to eight input streams but in case of a single stream
modulator very often one input stream and maybe a redundant stream will be configured here.
The physical data ports used by the input streams are the Ethernet interfaces data1 and data2.
received.
Furthermore select the encapsulation protocol and configure the input rate mode parameters in such
a way:
eliminated.
TSoIP input recommendation:

TSoIP can transport up to 7 transport stream packets in 1 UDP frame. This can
introduce high levels of jitter when bitrates are low. To avoid excessive jitter on the
TSoIP inputs, the number of TS packets/UDP frame should be lowered when using
low bitrates.
The following table provides an overview of the recommended settings to use:
Bit Rate Recommended Number of TS Packets
>= 500 kbps Up to 7 TS packets/UDP frame (less is allowed).
500 kbps > Bitrate >= 250 kbps Maximum 3 TS packets/UDP frame.
250 kbps > Bitrate >= 100 kbps Maximum 2 TS packet/UDP frame.
Bitrate <= 100 kbps Maximum 1 TS packet/UDP frame.
Configuration
» Click on the functional block and then click Show All.

When no TSoIPs are available see Add a TS over IP Input Interface. on page 156


18.4.2.1 Add a TS over IP Input Stream
» Click Add to insert a new TS over IP on the Ethernet Input Interface.


Name Enter a logical name for this incoming transport stream.
Enable Enable or disable the input streaming.
TS Encapsulation Select the encapsulation protocol that was used by the source device.
Protocol
• UDP: It is advised to use the UDP protocol only in simple IP networks
where jitter, packet loss or packet reordering is low.
• RTP FEC: This is the RTP protocol with additional Forward Error
Correction, to make the transmission even more robust.
UDP Port Define the UDP port for reception of the data.
Data can enter the device via any interface specified in the network
configuration.
Unicast and multicast are possible. Please refer to section
Data IP Connectivity. on page 114
In case of multicast refer to section:

Configure the Multicast IP Address. on page 119
Buffer Delay Indicate the amount of jitter to be absorbed by the device.
Input Rate Type Select one of the following:
User Defined: The user enters the input rate manually. The bitrate
should be correct within 30 ppm for proper behavior of the control loops
(NTC and DVB).
PCR: The device will use the PCR values to determine the input bitrate.
If the PCR values have a good precision, this rate estimation will be
adequate to start the control loops.
Input Bit Rate Enter the bit rate, this value should be correct within 30 ppm for proper
behavior of the control loops ( NTC and DVB).
Auto PCR Detection The device looks randomly for a PCR stream that gives consistent rate
values.
Control Loop Type This parameter allows the user to define how the device will minimize the
TS jitter on its inputs. See Control Loop Type [None, NTC, DVB] on page 368.
Bind Mode Select one of the following:
Unbound: No binding is created for this UDP Port. In this mode every
UDP port must be unique.
Bound On Multicast: Bind an UDP port with a specific multicast IP
Address. This mode, provides the possibility to receive different
multicast IP streams on the same UDP port.
Bound Address Select the appropriate multicast IP instance to link the input stream.
To configure a multicast IP instance please refer to section:
Configure the Multicast IP Address on page 119 .
» Click Update to save the TS over IP input stream settings.

18.4.2.2 Monitoring Table
Name Displays the TSoIP input stream

name that is being monitored.
Operational Operational: The TSoIP input

State interface is receiving data as
expected.
Failed: A problem exists on the Check the alarm status table and
TSoIP input interface. also the corresponding monitoring
parameters to troubleshoot the
failure.
TS Input Bit Displays the current input bit rate.

Rate
Offset Indicates the difference between the When the offset becomes to large, a
incoming and the configured bit rate buffer underflow or overflow will be
in ppm. detected.
Buffer Indicates the amount of jitter that is

Delay currently absorbed by the device.
Minimum The minimum buffer delay measured

Buffer value over a time interval.
Delay
Maximum The maximum buffer delay When the buffer cannot compensate
Buffer measured value over a time interval. for the incoming jitter the maximum
Delay buffer delay ramps up and at a
certain point generates a buffer
overflow alarm.
Source Info Displays the IP and UDP port of the

source device that is streaming the
transport stream.
RTP FEC Indicates the FEC scheme applied

Scheme on the incoming transport stream.
TS Drop Displays the number of dropped

Count Transport Stream packets.
RTP Drop Displays the number of dropped RTP

Count Packets.
RTP Repair Displays the number of repaired RTP

Count packets by using the FEC
information.
Active PCR Displays the active PCR PID.

PID

18.4.2.3 TS over IP In Alarm Status Table
Input Data Green: Data traffic is detected on this

input interface
Red: No data is detected on this • Check if the UDP port is

input interface. configured correctly.
• Check if the source device is
sending any data traffic towards
this TSoIP input interface.
Buffer Green: The de-jitter buffer does not

Underflow run out of packets.
Red: The de-jitter buffer runs out of • Check input rate setting and
packets. increase buffer delay, if needed.
Buffer Overflow Green: The de-jitter buffer is not

overloaded with packets.
Red: A packet overflow is detected in • Check input rate setting and

the de-jitter buffer. increase buffer delay, if needed.
No RTP Sync Green: Valid RTP input data is

received.
Red: No valid RTP input data is • Check the configuration of the

received. source device.
Buffer Delay Green: There are no problems with

too High the throughput towards the next
functional block in the device.
Red: The value for the Buffer Delay,

when translated into a number of TS
packets, leads to a value larger than
the physical buffer available. This
can occur at high bitrates or at high
Buffer Delay values.

18.4.3 Configure TS Redundancy

TS redundancy allows to create active/standby redundancy scenarios. In this case one stream
serves as backup for the other stream.
Configure
» In the overview pane click TS Redundancy.

» Click Add


For example ASI1 <--> ASI2, expressing that ASI1 and ASI2 are used to
create a redundant link.
Enable Enable or disable the redundant link.
Input A Type Select from which functional block we take in the first stream:
– ASI IN: The transport stream is received on an ASI input interface.
Input A Name Select the exact input interface that is used as the first stream.
– ASI-1
Input B Type Select from which functional block we take in the second stream:
– ASI-IN: The transport stream is received on an ASI input interface.
Input B Name Select the exact input interface that is used as the first second stream.
– ASI-2
Switching Mode Select the correct switching mode.

• Automatic: This is the preferred method.
• Manual:
– During configuration of the system setup, this to avoid continuous
switching between the two streams.
– During maintenance.
– Incase the system setup is controlled by a Network Management
System via SNMP.
Protection • Revertive: Select this when one of the inputs (A and B) has priority. This
Mode means when the preferred input returns to normal mode, the data will be
taken in on this interface.
• Non-revertive: Select this when no priority between the inputs (A and B) is
required.
In this case, when an input returns to normal mode there will be no
"switch" to the other interface.
Preferred TS Select either Input A or Input B to be the input with highest priority.
Input

» Click Update.
Note that it is possible to create TS active/standby scenarios between different input

types. Meaning that it is possible to create TS redundancy between two ASI input
interfaces, between two TS over IP input interfaces but also between an ASI input
interface and a TS over IP input interface.
Make sure to create TS Redundancy using correct input streams!
» Click Update to save the new redundancy rule.

18.4.4 Configure the Modulator

To configure the modulator please refer to section Modulator. on page 168
18.4.5 Configure the Multistream Output

» Click Multistream Output
» Click Add

Enable Enable or disable this stream.
ISI Enter an input stream identifier. This identifier is used by the receiver to
extract the appropriate stream.
ISSY ISSY insertion provides a means to regenerate the clock of the
transport streams in order to guarantee end-to-end constant bit rates
and delays.
ISSY Format Long: 22 bits are used.
Short: 15 bits are used.
Null Packet Deletion Enable this to save bandwidth.
When enabled the MPEG null packets are deleted and replaced by a tag
that indicates the number of null packets that have been deleted. The tag
is used by the receiver to reproduce the same amount of null packets,
this in order to keep bit rates and the end-to-end delay constant
Output Type By default Modulator.
Output Name By default Modulator-1.
» Click Update.

18.4.5.1 Configure the DVB-S2 Parameters per Stream
Once the stream is created, it is possible to configure the specific settings per stream.
» Select the appropriate MODCOD.
» Enable or disable the use of pilots.
» Select the frame type to use.
Please note that the title of the table does not change between DVB-S2 and
DVB-S2X.
If both frame types (short/normal) are used for the streams, then it is advised to limit
the symbol rate of the modulator to 30 Mbaud. If the symbol rate of the modulator is
higher than 30 Mbaud, only use one frame type (short or normal) for all streams.
To set the symbol rate, see section Modulator. on page 168

18.4.5.2 Multistream Output Alarm Status Table
Output Buffer Green: There is no overflow detected on this output interface.

Overflow
Red: An overflow is detected on this output interface.
The overflow mechanism is started on this interface.
About the overflow mechanism.
The order of definition sets the priority of the stream, the first configured stream has
the highest priority, the last configured stream has the lowest priority.
For example:
1. Six streams are configured.
2. The bit rate of stream 3 increases in such a way that the RF channel cannot transmit all data
anymore.
The Output Buffer Overflow alarm is triggered on stream number 6 (lowest priority stream).
(Data from this stream is being dropped.)
3. The bit rate of stream 3 increases further.
The Output Buffer Overflow alarm is also triggered on stream number 5 now.
(Data from this stream is also being dropped.)
(Note, at this moment the data of stream 6 is completely dropped.





the output.

output is enabled.


Mbps).

18.4.7 Configure the TS over IP Output Interfaces

This functional block allows you to configure up to eight logical output interfaces. A logical interface
is a unicast or multicast IP address used to forward the transport streams. The physical data ports
used by the unicast or multicast streams are the Ethernet interfaces data1 and data2.
the destination UDP port and the destination IP address.
» Click on the functional block.

» Click Add to insert a new TS over IP Output Interface .
Port
Address
In case of multicast an explicit routing table must be provided to indicate
which IP interface must be used for this multicast stream.
For more information please refer to:
Configure the Routing Table. on page 121
Please also refer to the following Add TS over IP on page 239

Multicast TTL Incase of a multicast IP address define the time to live. The Time to live
the IP packet and sends an Internet Control Message
» Click Update to to save the new TS over IP Output interface.

the available input and TS over IP Output interfaces.
» Click open detailed view of the specific TS over IP output.

Output Rate Displays the output rate on this TS over IP output interface.
Operational State Current state.

18.4.7.3 TS over IP Output Alarms
No Output Green: The TS over IP interface is active.

Red: This alarm is triggered if there is no packet sent to the output of
the device, while the output is enabled.
Check if a connection rule is created between the input and output
interfaces.
Check the IP routing table. The subnet and gateway should be
reachable.
Output Overflow Green: No overflow detected.

Red: Overflow detected on this output interface.
» Click OK to confirm the deletion.

18.4.8 TS Connections
18.4.8.1 Configure the TS Connections
This functional block allows you to configure the connections between the input interfaces and the
output interfaces.
This configuration is done by creating a connection rule.

The connection rule defines which type of "input" needs to be connected with which output block.

18.4.8.1.1 Add a Connection
The following configuration table is displayed:
» Click Add to add a new connection rule;
Name » Enter a logical Name.
From Type From which functional block do we take in the stream.
available.
– ASI Out: The transport stream is forwarded to an ASI output
interface.
– TS Over IP Out: The transport stream is forwarded to a TS over
IP output interface.
This type is only selectable when a TSoIP output interface is
created.
– Multistream Output: The Transport Stream is forwarded to the
multistream output block where an ISI and an appropriate
MODCOD is selected.
To Name Select one of the available ASI, TS over IP or the multistream output
interfaces.
The table dynamically shows the available interfaces corresponding with
the Type Name that is selected in the previous parameter.
» Click Update to save the new Input.
Note, that it is possible to forward the same transport stream to different output
interfaces. This way it is possible to create a redundant signal.

18.4.8.1.2 TS Stream Overview
Option 1:

Option 2:
Result:

18.4.8.1.3 Delete a Connection

18.5 Block Diagram Multistream Demodulator

The block diagram shows the data flow through the device when a multistream carrier is received by
the MCX7000.
Demodulator
Configure the RF parameters of the demodulator to get an Rx Lock on the RF carrier that you want
to receive.
The MCX7000 supports two stream modes: single stream and multistream.
1. To receive a multistream select Multistream for stream mode.
When this configuration is done, the Rx Lock LED (bottom right of the GUI) should light up green.
The BBFs are forwarded to the Multistream Input functional block.
2. When stream mode is set to single stream the transport stream is directly forwarded to the TS Connections
block, for more information please refer to section: Block Diagram Single Stream Demodulator. on page 184
Multistream Input
Configure the parameters in this functional block to extract the transport streams from the incoming
BBFs.
It is possible to configure up to eight different ISI values that need to be extracted from the incoming
BBFs.
It is possible to individually enable or disable the streams. Only enabled streams are sent to the TS
Connections.

In expert mode it is also possible to configure the output rate mode and the related parameters.
The output rate modes can be used to produce clean outputs and eliminate the jitter created by the
satellite transmission.
For more information on the different output rate modes please refer to
Appendix - Configuring the Output Rate Mode on page 366
ASI Output Interfaces

Determine on which ASI output interfaces the transport streams should be sent out.
In expert mode it is possible to configure the output rate mode and the related parameters.
TS over IP Output Interfaces

Add and configure the logical output interfaces that are required for your setup.
Configure the encapsulation protocol, the destination IP address and the destination UDP port.
Connections
Configure this functional block to make an interconnection between the extracted transport streams
and the ASI physical output interfaces and/or to the TSoIP logical output interfaces.
It is possible to create redundant outputs by connecting an incoming transport stream to different
output interfaces (ASI and/or TSoIP).
This way it is possible to send out transport streams on six ASI interfaces and on eight TS over IP
logical output interfaces.
Note that the TS over IP logical output interfaces must be created first before it is
possible to make a connection between the incoming transport streams and the TS
over IP logical output interfaces.

18.5.1 Demodulator
Please refer to section Demodulator. on page 186
18.5.2 Multistream Input

This functional block allows to extract different transport streams from the multistream carrier. The
selection of a given transport stream is based on the ISI-value present in the headers of the
incoming baseband frames (multistream).
» Click on the functional block and then select Show All to configure and monitor the multistream
inputs.
The following sections explain how to add, view and delete input streams.
Furthermore the different parameters of the multistream Input functional block are explained.
18.5.2.1 Multistream Configuration Table
18.5.2.1.1 Add a New Input Stream
» Click Add to add a new input stream.
Maximum eight streams can be configured.

Name Enter a logical name for this filter.
Enable Enable or disable.
ISI Enter the ISI value you want to extract corresponding to the ISI value
that is used on the sending site.
Input Name Demodulator
Input Type Select the demodulator from which to receive transport streams.
Note: In expert mode it is also possible to configure the output rate mode and the related
parameters.
» Select the Output Rate Mode, this is the rate smoothing method that you want to use.
– Auto (ISSY): If the ISSY timestamps are present, the device will output transport stream
packets as they arrived at the input of the modulator.
Otherwise, it will reproduce the transport stream as received via its inputs (including rate and
jitter) on the ASI output.
For more information please refer to section:
ISSY for Transport Stream bitrate Recovery. on page 366
– User Defined: If the user wants to have manual control on the output, the User Defined choice
can be selected. In this case the user can specify the output rate and select the appropriate
control loop.

Note, keep the default values to get the stream working during initial configuration.
Fine tuning the output rate can be done when the configuration is stable.
For more information on the rate smoothing methods we refer to section:
18.5.2.1.2 View the Configuration Parameters per Input Stream
Next to viewing the parameters in this overall configuration table (Show All), it is also possible to
view these parameters per created input stream.
The functional block "Multistream Input" allows two options to display the configuration parameters
per input stream.
Option 1:
» In the overview pane click on the "Multistream Input" functional block.
» Select the Input Stream to be displayed.

Option 2:
» In the overview pane click on the "Multistream Input" functional block.
» Select Show All (to view all available input streams).
» Click on the icon in front of the name to display the configuration parameters.

Result:

18.5.2.1.3 Delete an Input Stream
» Delete an input stream by clicking on the "X" icon in front of this stream.
The following warning is displayed:
Are you sure you want to delete this entry?
18.5.2.2 Monitoring the Inputs
The monitoring parameters provide an overview of the incoming signal.
The monitoring table allows you to perform detailed troubleshooting.

Per input stream the following parameters are monitored:
TS Error Counter Displays the amount of packets in the stream containing an error.
Note: After enabling/activating the instance it is possible that some

packet errors are displayed due to synchronizing the incoming stream.
BBF Frames Displays the total amount of baseband frames per extracted transport
Counter stream.
BBF Frame Rate Displays the baseband frame rate.
ISSY Detected Indicates if Input Stream Synchronization time stamps are present in the
transport stream.
When an ISSY is detected, it is recommended to use this synchronizer
to regenerate the clock of the Transport Stream at the modulator site.
This in order to guarantee end-to-end constant bit rates and delays.
TS Bitrate Displays the bit rate in Mbps.

The bit rate should match the bit rate that is set on the sending site.
Operational State Indicates whether the input is operational or not.

When not operational, please check the following:
• Is the input enabled?
• Is the ISI value entered still valid?
• Is there an RX Lock in the demodulator functional block?
• Is multistream mode selected in the demodulator functional block?
MODCODs not Number of baseband frames which are dropped because the received
licensed MODCOD is not licensed in the demodulator.
In expert mode it is also possible to monitor the statistics linked to the selected output
rate mode.
(The monitoring parameters are: Buffer Delay, Buffer Filling Level, Minimum and
Maximum Buffer Filling Level, Active PCR PID).
For more information on these monitoring parameters please refer to

18.5.2.3 Multistream Input Alarm Status Table
This table indicates if alarms are present per input.
TS Errors Green: The incoming Transport Stream is received correctly

Red: No Transport Stream is received.
No Output Green: The Transport Stream is forwarded to the next functional block
"TS Connections".
Red: No Transport Stream is forwarded to the next functional block "TS
Connections".
MODCOD not Green: All MODCODs received are licensed.

Licensed
Red: The received MODCOD of a specific baseband frame stream is not
licensed in this demodulator.
Buffer Overflow The Maximum Buffer Level is achieved. Packets will be dropped in the
device. If this alarm occurs, the device will try to recover from the
situation by resetting the buffer (i.e. it is emptied), and start again
generating the outputs.
Buffer Underflow The output buffer is empty and the device needs to send packets to
guarantee a constant bit rate. Jitter will in that case appear on the
output. This alarm can occur only with the Auto (ISSY) output mode and
with the Control Loop Type NTC or DVB.
Buffer Delay Too The value for the Buffer Delay, when translated into a number of bytes,
High leads to a value larger than the physical buffer available. This occurs at
high rates for high buffer delay values.





the output.

output is enabled.


Mbps).

18.5.4 Configure the TS over IP Output Interfaces

This functional block allows you to configure up to eight logical output interfaces. A logical interface
is a unicast or multicast IP address used to forward the transport streams. The physical data ports
used by the unicast or multicast streams are the Ethernet interfaces data1 and data2.
the destination UDP port and the destination IP address.
» Click on the functional block.

» Click Add to insert a new TS over IP Output Interface .
Port
Address
In case of multicast an explicit routing table must be provided to indicate
which IP interface must be used for this multicast stream.
For more information please refer to:
Configure the Routing Table. on page 121
Please also refer to the following Add TS over IP on page 239

Multicast TTL Incase of a multicast IP address define the time to live. The Time to live
the IP packet and sends an Internet Control Message
» Click Update to to save the new TS over IP Output interface.

the available input and TS over IP Output interfaces.
» Click open detailed view of the specific TS over IP output.

Output Rate Displays the output rate on this TS over IP output interface.
Operational State Current state.

18.5.4.3 TS over IP Output Alarms
No Output Green: The TS over IP interface is active.

Red: This alarm is triggered if there is no packet sent to the output of
the device, while the output is enabled.
Check if a connection rule is created between the input and output
interfaces.
Check the IP routing table. The subnet and gateway should be
reachable.
Output Overflow Green: No overflow detected.

Red: Overflow detected on this output interface.

18.5.5 Configure the TS Connections

This functional block allows you to configure the connections between the input interfaces and the
output interfaces.
This configuration is done by creating a connection rule.

The connection rule defines which type of "input interface" needs to be connected with which kind of
"output interface".

18.5.5.1 Add a Connection
» Click Add to add a new connection rule.
Name » Enter a logical Name.
From Type From which functional block do we take in the stream.
– Multistream TS Input.
available.
– ASI Out: The transport stream is forwarded to an ASI output
interface.
– TS Over IP Out: The transport stream is forwarded to a TS over
IP output interface.
This type is only selectable when a TSoIP output interface is
created.
– Multistream Output: The Transport Stream is forwarded to the
multistream output block where an ISI and an appropriate
MODCOD is selected.
To Name Select one of the available ASI, TS over IP or the multistream output
interfaces.
The table dynamically shows the available interfaces corresponding with
the Type Name that is selected in the previous parameter.
Note, that it is possible to forward the same transport stream to different output
interfaces. This way it is possible to create a redundant signal.

Option 1:

Option 2:
Result:


18.6 Block Diagram Multistream and Multicarrier Setup

To configure this setup, the same steps must be applied as explained in the previous
sections. In this case we need to configure two or more separate modulators and
configure the demodulators on the receiving site.
The following figure shows an example setup.
Transmission
In this example we transmit two carriers that contain a multistream. Two modems are used to
transmit on carrier 1 and carrier 2. Per modem we aggregate two transport streams. The aggregation
of the transport streams is done in the multistream output block of the MCX7000. In this block an ISI
is assigned per TS.
The previous figure shows that we aggregate two transport streams received on the ASI 1 and ASI 2
input interfaces on modem 1.
On modem 2 we also aggregate two transport streams but now received on the TSoIP 1 and TSoIP
2 input interfaces.
In total we transmit four transport streams.
Receiving
On the receiving site we use an MCX7000 with multiple demodulator slots to receive both carriers.
Once a stable lock is established on both carriers the streams are forwarded towards the
multistream input block. In this block we extract the ISI streams.
In this example we assume that:
• The management plane is configured.
• The ASI input interfaces are connected.
• The data Ethernet interfaces are connected.
• The needed IP addressing is know to the operator.
(The IP addresses visible in the video are used as an example only)
Check out the following video to get a step by step configuration.

Configure Modem 1
Activate the ASI Input Interfaces.mp4
Configure the Multistream Output Block.mp4
Add Connections Between the Input and Output Interfaces.mp4
Configure the Modulator.mp4
Check the Parameters.mp4
Configure Modem 2
Add a TS Over IP Input Interface.mp4
Add an Output Stream.mp4
Create TS Connections.mp4
Configure the Modulator.mp4
Configure the Demodulator

Configure the Demodulator1.mp4
Enable Demodulator3.mp4
Configure the Multistream Input.mp4
Enable and Configure the Data Interfaces Block.mp4
Add a TS over IP Output Interface.mp4
Add Connections Between the Input and Output Interfaces.mp4
Save a Configuration
Save a Configuration.mp4

Configure the Input Processing Blocks MCX7000 Multi-Carrier Satellite Gateway
19 Configure the Input Processing Blocks
19.1 TS Generator
The TS generator is used to perform basic tests on the device or to get an indication on the satellite
link quality.
• Generate a PRBS (Pseudo Random Bit Sequence).
• Enable a Counter.
• Generate Null Packets Only.
• When using the PRBS generator check that the NIT Carrier ID and Rate Adapter
are disabled. Note: The randomness of the signal is not guaranteed when these
settings are enabled.
• When using the PRBS generator (and no rate adaption is applied) the PRBS
generator automatically slaves to the resulting bit rate of the modulator output.
(The rate can thus not be set.)
Location

Configure
» Click TS Generator.
» Click Add.

Enable Enable or disable the generator.
TS Bit Rate Enter a TS Bit Rate in bps that must be generated.
Type Define what kind of test signal to use:

• PRBS: Configures the test generator to generate transport stream
packets containing PRBS data. The generated PRBS complies with
HP3764 Compatible 2^23-1 PRBS sequence as specified in CCITT
Rec. 0.151.
• Counter: Configures the test generator to generate transport stream
packets containing 8-bit counter values as data. This counter data
cannot be analyzed by the test detector. It can only be used for
manual verification by an external analyzer.
• Generate Null Packets Only: Use this to create a stream that will be
used for MPE.
The null packets will be replaced with MPE data that is inserted in the
output processing block.
PID Handling Configuration of the test generator to generate transport stream packets
with a valid transport stream header. The configured PID (Packet
Identifier) is inserted in the transport stream header and the continuity
counter is incrementing. Possible settings:
• Off: Transport stream packets are generated without a valid transport
stream header. In this case, a 0x47 sync marker followed by 187 test
bytes are generated.
• On: The transport stream packets are generated with a PID value
that is inserted in the first two bytes following the sync marker
(byte 1 and byte 2) of each data packet. It is used for proper error
detection when the rate of the generator is lower than the interface
rate of the modulator board or when the test generator is configured
to create a burst of transport packets (data packets combined with
null packets).
PID Value Configure the PRBS generator PID value.
Number Data Configure the number of data packets per burst that the test generator
Packets has to generate. The baseband source can generate alternating bursts
of data packets and null packets. Once the burst is finished, it starts over
repetitively. This is controlled by setting the number of data packets and
null packets. This command controls the number of data packets per
burst. The continuity counter is not reset when the next burst starts. A
maximum of 255 data packets per burst is possible.
Number Null Packets Configuration of the number of null packets per burst that have to be
generated.
» Click Update.

19.2 MPE Decapsulation

In Multistreamthe received baseband frames are forwarded to the Multistream Input block. In the this
block, the transport streams are extracted based on the ISI. When MPE encapsulated data is
present in one of the transport streams this stream is forwarded to the MPE Decapsulation block.
This block is part of the Input Processing block.
Configure this MPE Decapsulation block.
The MDM6100 has the possibility to perform in-band remote management using MPE
Encapsulation and Decapsulation.
19.2.1 Configure MPE Decapsulation

» Click Input Processing
» Click MPE Decapsulation

From this window it is possible to configure the following:

• Configuration table
• Programs table
• Channels table
Next to configuring the MPE decapsulation parameters it is also possible to monitor the forward bit
rate and dropped packets per transport stream and per program.

19.2.2 Select the TS to Extract MPE Data

Use this block to define from which incoming transport stream the MPE data needs to be extracted.
» Click Add to extract MPE data from an available transport stream.
Name Enter a logical name for this encapsulation rule.
Enable Enable or disable the decapsulation rule.
Select TS Select one of the available transport streams, where MPE can be
extracted from.
» Click Update.

19.2.3 Select the Programs

» Click Add
Program Name Enter a logical program name.
Enable Enable or disable the program table.
Program Number Enter the program number you want to receive.
Data PID Enter the Data Packet Identifier you want to receive.
This must be the same as the one used by the transmitter.
PMT PID Enter the PMT Packet Identifier you want to receive.
Config Select one of the available TSs defined in the configuration table.
» Click Update

19.2.4 Select the Channels

» Click Add
Channel Name Enter a logical channel name.
Enable Enable or disable the channel.
MAC Assign a MAC Address to filter out the correct channel.

When 00:00:00:00:00:00 is used then the decapsulator will check for
any MAC address used. When a MAC address is available this will be
used.
Virtual Network Select a virtual network according to the type of traffic received.
• Traffic, forwarding the data traffic towards interface data1 or data2.
• Management, forwarding the Mgmt traffic towards interface mgmt1 or
mgmt2.
Program Link the channel to an available program.
» Click Update

Configure the Output Processing Blocks MCX7000 Multi-Carrier Satellite Gateway
20 Configure the Output Processing Blocks
20.1 Basic Interoperable Scrambling System (BISS)
20.1.1 Content Scrambling Modes

The BISS application on the MCX7000 protects the content of a MPTS (multi-program transport
stream) during transmission.
BISS uses a Session Word as a scrambling key. The same key is used to scramble all programs.
The MCX7000 supports two different encryption modes with different scrambling behavior: standard
mode or raw mode.
20.1.1.1 Standard Mode
The Standard Mode is fully DVB-compliant. In this mode, the payload of all packets is scrambled,
except for the PSI/SI tables (PIDs<0x1F and PMT tables).
The scrambling starts when a valid PAT table is found and all existing PMT tables are identified.
When no PAT is detected within 1 second, the scrambling is however started in raw
mode.
Each PMT table is updated with a proper CA descriptor (Conditional Access descriptor) if the
descriptor is not yet available. The scrambler also inserts a CAT when no CAT is present in the
transport stream.
In case of CRC error on the PAT or PMT, or if the incoming stream appears to be scrambled (CA
descriptor in the incoming PMT), the scrambling is stopped to avoid making the signal
unrecoverable. This behavior can be overruled with the “Scrambling Suppression” parameter.
Scrambling Suppression (for Standard Mode)

When operating in the standard mode, the scrambling by default stops in case of CRC errors on
the PAT or a PMT or if a PMT already contains a CA descriptor. The reason is that the risk to
scramble PMTs, or erase previous scrambling information would make the stream unrecoverable by
an IRD.
It is possible to overrule this behavior, if the protection of the stream is more important than its
decodability in case of errors. Do this by disabling the “Scrambling Suppression” parameter.
Keep this suppression enabled when the TS has high priority and getting the TS to the receiving
end has more priority than scrambling the TS.

20.1.1.2 Raw Mode
In this mode the payload of all packets is scrambled except for the PID<0x1F. In this mode it is
possible to overwrite the default 0x1F value in order to define the range of unscrambled PIDs (from
0x00 to a user-given value). Use the following parameters to define this range, Min RAW
Unscrambled PID and Max Raw Unscrambled PID.
The scrambling starts immediately as this mode does not perform a check if a valid PAT is available
in the TS.
Furthermore, this mode scrambles all PMTs (if any) and it does not insert a CAT in the transport
stream.
This encryption mode guarantees SFN (Single Frequency Networks) integrity.
It can also be used to encrypt proprietary MPEG streams.
20.1.2 Key Management System
20.1.2.1 Odd/Even key
The BISS specification is based on the use of two scrambling keys: the odd key and the even key.
One key is the active one, used to scramble the packets, while the other key is the future key to use.
This allows to enter in devices the next key to use in advance and later activate at the chosen
moment.
On the scrambling side (the modulator), the operator defines which key shall be used. On the
descrambling side, the devices automatically detect which key to use.
Note that only the Even key should be used for BISS for interoperability with 3rd party
receivers.

20.1.2.2 Key Management System Structure
The following figure details the structure of the BISS Key management system that is implemented.
The key management structure can be split up into two parts, distribution of clear session words
over a secure channel (bottom part) and distribution of Encrypted session words over a non-secure
channel (top + bottom part). Both distribution methods are explained in the following sections.
20.1.2.3 Distribution of Clear Session Words over a Secure Channel
When the distribution of a session word can be performed over a secure channel (trusted manual
operator, secured e-mail or any other trusted means), it is possible to enter the clear session word
directly without extra protection.

Odd/Even Session This setting allows the user to set the odd or even clear session word.
word The entered clear session word is used by the scrambler as the real
encryption key. The key parity defines if the odd or even key will be
used by the scrambler.
Interface used
The clear session words are entered by the user through any interface
(For example: Frontpanel, GUI, CLI, SNMP).
It is not possible to read back the session words by any interface.
Hexadecimal
A session word exists out of 12 digits and is in hexadecimal format.
When entering the session word, enter the most significant digit
(nibble) first (reading from left to right).
For example, 0xA13DBC42908F would be entered in the following
sequence:
A,1,3,D,B,C,4,2,9,0,8,F
The clear session word must be distributed to all parties that are
allowed to descramble the received data.
Key Parity Key Parity Selection on the Modulator

The user on the transmitting site selects whether to use the odd or the
even session word.
Note: When the Key Parity is set to odd, setting the even session word
has no direct impact on the scrambled output and the other way
around. The “new” session word becomes active when the key parity is
switched on the scrambler.
Setting Clear Session Words
Starting Point: The odd session word is used by the scrambler. This is indicated in the
header of the transport stream packet.
• Entering an even session word does not affect the scrambled output.
• The even session word is stored in the device.
• Switch Key Parity (to Even).
• The output is now scrambled with the even session word. The header of the transport stream
packet indicates that the even session word is used. The descrambler of the receiver reads out
the header information and decrypts with the correct key.
Entering new session words is limited by the BISS specification to 10 times within a 5
minute period and there must be a minimum of 10 seconds between two changes.

It is also possible to edit the active session word directly (the odd session word in the example here).
It will then be directly used in the scrambling. The new session word has to be entered also on the
descrambler side to allow proper descrambling. As a consequence, editing the active session word
often creates a descrambling interruption on the receiver side. Changing the active session word on
the scrambler side shall thus only be done if non-valuable content is being transmitted at that time.
Otherwise, it is best to edit the inactive session word and then switch to it. The descrambler should
automatically follow the changes, as described in the aforementioned procedure.
Changing the key parity on a scrambler will not interrupt the stream. It is thus a
seamless operation, if the descrambler is properly configured on the receive side..
20.1.2.4 Distribution of Encrypted Session Words over a Non-Secure Channel
When the distribution of a session word cannot be performed over a secure channel it is advised to
add extra protection to the clear session word.
Adding extra protection is done to avoid that non authorized parties have access to the clear session
word and at the same time to the scrambled content.
The encryption key of the Session Word is called a device identifier. Two identifiers are defined in
BISS:
• A group identifier (the Injected ID), common for several units. This identifier is secret and cannot
be read by an operator. It is used when an organization has several devices part of the same
network. The Injected ID is entered in all devices of the same network. The same Encrypted
Session Word can then be used on all devices to protect a transmission. This Encrypted Session
Word cannot be used on any other device that does not have this Injected ID.
• A buried identifier (the Buried ID), unique for each unit. This identifier can be read on the front
panel. It is not fully secret. Its use is to protect a Session Word that has to be sent to that unit
specifically. The operator will read the buried ID and communicate it to the Session Word owner,
so that this person can send back the Encrypted Session Word. This Encrypted Session Word
can only be used by that device.

Odd/Even Encrypted This setting allows the user to set the odd or even encrypted session
Session word word.
An encrypted session word is computed by using the injected Id or
buried Id and the clear session word. (To compute an Encrypted
session word, refer to
section Compute Encrypted Session Words on page 285).
Interface used
These encrypted session words can be entered by the user through
any interface. (For example: Frontpanel, GUI, CLI, SNMP).
It is not possible to read back the session words by any interface.
Hexadecimall
An encrypted session word exists out of 16 digits and is entered in
hexadecimal format.
For example, if the encrypted session word is
0xF76EE249BE01A286, enter it in the following sequence:
• F,7,6,E,E,2,4,9,B,E,0,1,A,2,8 and 6.
Injected Id The injected Id can be used to decrypt the encrypted session words.
Interface used
This Id can be entered by the user through any interface and is
stored in the device. (For example: Frontpanel, GUI, CLI, SNMP). It
is not possible to read back the injected Id by any interface.
Hexadecimal
The Injected Id exists out of 14 digits and is in hexadecimal format.
When to use an injected Id?
An injected Id can be entered (injected) on a single device or it can
be entered on a group of devices.
Buried Id The buried Id can be used to decrypt the encrypted session words.
The buried Id is a fixed key that is unique per device.
Interface used
The buried Id is read only and can only be read by the expert user.
It can be readout through any interface.
(For example: Frontpanel, GUI, CLI, SNMP).
Hexadecimal
The buried Id exists out of 14 digits and is in hexadecimal format.
When to use a buried Id?
Use this Id to compute a device unique encrypted session word.
Encryption Mode This parameter allows the user to select the way encrypted clear
session words are decrypted. This can be done by using the buried
Id or the injected Id. Setting this mode has no direct impact on the

scrambled output. This because it is only used when entering a new

encrypted session word.
Session Word The decrypter computes the clear session word from the injected or
Decryptor buried Id and the encrypted session word.
The computed clear session word is used by the scrambler as the
(real) clear session word.
20.1.2.5 Compute Encrypted Session Words
Computing Encrypted Session Word before their distribution to devices shall be done off-line by an
external tool.
The following figure shows how an encrypted session word is calculated.
Compute an Encrypted Session Word.
Newtec distributes a simple web-based java script to compute encrypted session

words for a specific device. Use the Newtec Service Desk tool to receive a copy:
> Browse to http://customersupport.newtec.eu . > Fill in your Username and
Password > Create a ticket
As response of your request you will receive the script from our support team.
All session words or IDs used are in hexadecimal. For the algorithms, they are
represented with the most significant byte (bit) first.

The following figure is an Excerpt of the web-based java script tool. .

20.1.3 Defining BISS Keys

The device can contain now several BISS scramblers. Those scramblers can share keys or use
their own keys. For that reason, the device separately defines a set of BISS keys and a set of BISS
scramblers. This section explains how to define a set of keys.
To define set of BISS keys, access the key table by clicking in the “Overview” tab on “Output
Processing” block. Select “BISS scrambler”. If some BISS scrambler instances already exist, select
“Show All” in the drop down list.
» Click Add


Name Description
Name Give the key set a name, for example “Keys1”.
Clear Even SW When the distribution of session words is done over a secure
channel:
Clear Odd SW
Enter the Clear Session Words (Odd and Even)
Encrypted Even SW When the distribution of session words is done over a

non-secure channel:
Encrypted Odd SW
Enter the encrypted session Words (Odd and Even).
Do not enter Clear session words and

Encrypted session words at the same time!
Otherwise the receiver won't be able to
unscramble the content!
Encrypted Mode When using Encrypted Session Words, specify if if the are
protected using the Buried ID or the Injected ID.
» Click Update
To modify BISS keys in a key set, click on the relevant line in the table and edit the values.
(Always fill the Clear Session Words OR the Encrypted Session Words, Never both pairs!)

20.1.4 Creating a BISS Scrambler

To scrambler a signal, you need to create a BISS scrambler instance.
» Click Add;
Name Description
Name Enter the name of the instance.
Scrambling Enable or disable scrambling.
Scrambling Mode Select the appropriate scrambling mode standard or raw.

Please refer to section: Content Scrambling Modes. on page 279
Key Parity Select to use the Even or the Odd key.
Scrambling Suppression When enabled, the scrambling is suppressed when a PAT or

a PMT error occurs.
Keys Select on of the available key sets.
Select TS Define which signal this scrambler should process.

(Select one of the available transport streams as defined in
the "TS" connection block.
Note: If set to "None", no processing is performed.
» Click Update.
Note: Maximum two BISS scrambler instances are allowed in the current version.

20.1.5 Changing BISS Scrambling Parameters

When a BISS scrambler instance has been created, it can be edited.
» Click on the “Overview Tab".
» Click on the "Output Processing” block.
» Select “BISS scrambler”.
» Select the BISS scrambler instance in the drop down list.

• The top of the window also contain the “Key Configuration Table”, so that you can also edit the
BISS keys directly, should you need it.Warning: if several BISS scramblers use the same keys,
changing keys for one scrambler will also affect the other scramblers as they use the same keys.
If this is not desirable, create one key set for each scrambler;
• The bottom part of the window is used to change the BISS scrambling parameters.

20.1.6 Deleting Keys

Keys can be deleted by erasing the key set line in the “Key Configuration Table”.
However, their trace will remain in the device.
Proceed as follows to remove all key information from the device.
» Navigate to the Keys Configuration Table.
» Select Clear Keys. It erases a default value in all keys of that key set, so that the old value
cannot be traced back in the MCX7000. The key set is still defined as it can be part of a
pre-stored configuration.

20.1.7 Viewing the Buried Identifier

» Log in as expert
» Click Output Processing
» Click Show All
The buried Identifier is displayed on the top of the window.
20.1.8 Seamless Key (Session Word) Change

The BISS key management system is designed to allow the change of a session word (odd/even)
during a transmission without interrupting the stream. The scrambler adds information into the
header to indicate whether the odd or even parity session word is used.
The demodulators/receivers can detect which key (odd or even key) is currently in use. When the
modulator switches from one key to another, the demodulator/receiver automatically detects the
change and switches to the other key in a synchronous way. This way, the demodulator always uses
the proper session word to descramble the transport streams. No interruption or glitch appears at
the output of the demodulator/receiver.
By changing the unused session word on the modulator, it is possible to switch again the key in the
network.

20.1.9 Scrambling Monitoring Parameters

Here you get an overview of the current scrambling state and when the session word was last
changed:
• Scrambling State: Continuously reads out whether the TS is scrambled or not. It is possible that
scrambling is enabled but that due to PAT, PMT alarms and/or when a CA descriptor already
exist, the scrambling is not allowed (in this case the parameter scrambling suppression is
enabled). For more information on scrambling suppression refer to Standard Mode. on page 279
• Session Word Changed: This parameter informs when the session word was changed for the
last time. Each time a new session word is entered, the timestamp is written to this parameter. It
helps the user to identify the user if the session word stored in the configuration is the right one
or not.
20.1.10 Possible Alarms
Alarm Description
BISS PAT Error When the CRC of the PAT is not valid then this alarm is raised.
BISS PMT Error BISS PMT Error.
BISS CAT Error When the CRC of the CAT is not valid then this alarm is raised.
BISS Program If a packet of a program to be scrambled is already scrambled (indicated

Already Scrambled by the scrambling bits), then this alarm is raised. The packet shall not be
scrambled in that case, but scrambling continues for other packets.
BISS CA-Descriptor If a PMT already contains a CA descriptor then this alarm is raised.
found on Input
BISS Scrambling This alarm is raised due to errors happening in the scrambling core
Error (FPGA).

20.1.11 Operation of BISS
20.1.11.1 Setting a Key for Transmission
Starting point: the scrambler sends clear data to the descrambler. Both have their scrambling mode
set to “Standard”, but scrambling is disabled.
Steps:
• The Session Word is entered in the descrambler (odd key).
• Enable scrambling on the descrambler.
• The Session Word is entered in the scrambler (odd key).
• Enable Scrambling on the scrambler (select ON).
20.1.11.2 Setting an Encrypted Session Word for Transmission
Starting Point: Scrambling is not enabled. Clear TS is send towards the receiver.
Steps:
If Injected ID is used:
• Enter the Injected Id in the device, if it is not yet done (normally, the injected ID shall be
defined earlier)
• Select the encryption mode of your choice:
• Injected ID
• Buried ID
• Enter the encrypted odd session word in the decryptor.
• The odd session word is computed by the decryptor and available for use.
• Select the scrambling Mode (could be done at any step before):
• Standard
• Raw
• Enable Scrambling (select ON)
• The scrambler uses the odd session word.

20.1.11.3 Changing Keys Seamlessly
Starting Point: Scrambling is enabled and sends scrambled transport streams to the receiver. The
odd session word is active.
Steps:
• Enter the encrypted even session word in the decryptor.
• The even session word is computed by the decryptor and available for use.
• Set the key parity to even.
• The scrambler uses the even session word (this is indicated in the header of the TS packets, this
to inform the receiver of the switchover).
20.1.11.4 Removing a Receiver from the Network
Starting point: the scrambler sends scrambled data to the descramblers. The odd key is active. All
have their scrambling mode set to “Scramble/descramble” mode.
Steps:
1. Define a new Session Word.
2. The Session Word is entered in the descramblers (even key), except the one removed from the network.
3. The Session Word is entered in the scrambler (even key).
4. The scrambler is asked to switch to the even key.
20.1.11.5 Setting up a Secure BISS Network
Starting point: A scrambler and a set of descramblers in a secured facility (or in secured facilities).
Steps:
1. Define an Injected ID.
2. Insert the Injected ID in all devices by a trusted person/system.
3. Deploy the devices.
4. Sets the key for a transmission, sending Encrypted Session Words rather than Clear Session Words.
20.1.11.6 Creating Groups of Receivers
Groups of receivers, mutually exclusive, are created by inserting different Injected IDs in those
receivers and in the related sender. This way, another group of receivers cannot use Encrypted
Session Words sent to a group of receivers.

20.1.12 Keys and Redundancy, Backup or Import

A solution based on BISS should combine security, but also guarantee operations. BISS Session
Words cannot be copied from one device to another or exported, except in some cases:
• Redundancy
• Export of a configuration for backup purposes
• Import of a configuration pre-generated
20.1.12.1 BISS and Redundancy
The BISS implementation allows copying a session word during a redundancy switch.
To ensure the security of the key, a Setup Identifier is used. A Setup Identifier is the equivalent of
the Injected ID: it is used to encrypt session words when copied from one device to another, using
the Newtec USS 0202 switch.
The setup ID is typically the same for all devices in a redundancy bank. It is recommended that this
setup ID is unique for each redundancy setup.
Setup IDs all have the same default value, so that redundancy always works for devices coming from
factory.
In that case, the session word is not secured, as it can be copied to any other device during a
switch. It is thus recommended to define the setup ID when deploying a redundant setup using
BISS.
20.1.12.2 Backup a Configuration
It is possible to export and import device configurations. The Session Word is exported in an
encrypted manner, as well as the Injected ID, so that they can be recovered after an import on the
SAME device. If this configuration is imported on another device, the Injected ID will be ignored.
If this configuration is imported on a device with the same Setup ID, the Session Word will however
be loaded.
The default value of the setupID is the same for all devices. By default, exporting and
importing a configuration on another device will allow the copy of the BISS SW. To
avoid that, define the setup ID to a secret value.
An alternative is to set the setup ID of the device to zero. This will allow backup of
configuration, but will prevent the import of that configuration on any other device.
The keys are then fully protected.

20.1.12.3 Import a Configuration
• It is possible to edit an exported configuration file and define a new Session Word or a new
Injected ID in this file. When the changes are done, import the new configuration file into the
device(s).
Please refer to section: Basic Interoperable Scrambling System (BISS) on page 279
20.1.12.4 Editing the Setup ID
» Log in as expert
» Click Show All
The Injected ID is specific for each Key set.
To modify the Setup ID, click and enter the new value.

20.1.12.5 Erasing the SetupID
To erase the setup ID, it is possible to enter a zero value. This will result in the fact that a unique
setup ID is generated for that device. It will prevent copying any BISS key from that device to another
device. Backup of configuration on the same device is still possible through import/export of
configuration.
Trying to copy a configuration to or from a device with a setup ID equal to 0 will result in an error,
unless it is the same device.
Should the device be used in a redundancy setup, a new setup ID has to be entered.
Should users want to go back to the situation out of factory where BISS keys can be copied between
devices, it is necessary to perform a config reset.
Config reset can be done via the GUI when going to the TAB Device/Configurations. All config
parameters are lost, but the device will behave again as out of factory.

20.2 Rate Adapter

In principle, a one to one relationship exists between the input bit rate and the symbol rate of the
device. With rate adaptation this is no longer true. It is possible to set one variable independent of
the other.
When activated, the on-board Rate Adapter will delete and insert MPEG null packets as required to
obtain a fixed transmit symbol clock and uninterrupted service, even if the net input transport rate is
variable. (in single stream mode)
The Rate Adapter re-calculates MPEG PCR (Program Clock Reference) time stamps as required by
MPEG rules (PCR re-stamping if the PCR Restamping status is selected).
When the Rate Adapter is disabled, the device transmit clock is slaved to the interface (TS) clock
rate.
• When the rate adapter is disabled: the modulator symbol rate slaves on the input
bit rate. In TS over IP this is only possible when the CBR traffic profile is selected.
E.g. when using a locally generated PRBS, the PRBS rate slaves to the input bit
rate. (The rate can thus not be set.)
• When the rate adapter is enabled the modulator symbol rate can differ from the
input bit rate.

The following figure shows the rate adapter functionality.

Location
Configure
» Click Add to configure the rate adapter.

Enable Enable or disable the rate adapter.
Bit Rate Enter the required bit rate.
• In single stream: The modulator bit rate must be set to

the highest bit rate.
• In Multi stream: It is possible to create two rate
adapters.
This means that for two incoming TS streams a rate
adaptation can be defined.
The overflow mechanism in the Multi stream TS
Output block handles the output stream priority.
Null Packets Enable or disable null packet deletion.

Deletion
If enabled, this block deletes all Null packets (PID = 0x1FFF)
independent whether the output bit rate will be higher or lower than the
incoming bit rate. The TS packet generator will generate new Null
packets when needed.
Select TS Select the TS where to apply the rate adaptation.
» Click Update.

20.3 NIT Carrier ID

The carrier identification is used to reduce RFI (Radio Frequency Interference). The NIT carrier ID
allows the satellite operators to identify and contact the source of interference quickly. The carrier ID
is implemented in the Network Information Table (NIT) of the TS, more specifically into the network
descriptors set of the NIT. This information is readable by any MPEG analyzer system, which makes
it easy to track the source of the carrier. The carrier ID contains the following information:
• Fixed identification of the source:
– Modulator Manufacturer
– Serial number of the modulator
– MAC address of the modulator
• User configurable data:
– Descriptor Tag, this tag describes the carrier ID information in the NIT
– Carrier Identifier, insert a logical name for the carrier ID
– Telephone number
– Geo Coordinates
When using both DVB-CID and NIT-CID, make sure that the Geo Coordinates entered
are the same.
Use Geo Coordinates only in appropriate situations.
– User Information.
In case the incoming TS does not contain a NIT, a NIT will be generated except when
no null packets are available in the TS to insert the NIT.
Make sure that enough null packets are available in the TS to insert the NIT.
The configurable carrier data is inserted into the NIT when this functionality is
enabled. This means that the carrier ID of the incoming TS is replaced with the
information entered in the MCX7000.

Location
Configure
» Click Add
Enable Enable or disable the NIT Carrier ID.
User Information For example the company name.
Select TS Select the TS where to apply the
» Click Update.

20.4 Program-Specific Information (PSI-SI) Insertion

When no signaling is present in the received TS, use the following settings to insert signaling when
applicable.
• PMT Repetition Rate: Program Map Table repetition rate in ms (log in as expert).
• PAT Repetition Rate: Program allocation table repetition rate in ms.
• SDT Repetition Rate: Service descriptor table repetition rate in ms.

20.4.1 Configuration Table

In this table it is possible to assign an original network identifier and transport stream identifier to an
incoming transport stream.
» Click Add;
Enable Enable or disable the insertion of an original Network Id and

Transport Stream Identifier.
Original Network ID The main use is in the unique identification of a service through
the path.
Transport Stream Identifier The main use is in the unique identification of a service through
the path.
Select TS Select the TS to apply the original network ID and Transport

Stream ID.
» Click Update.

20.4.2 Alarm Status Table
Signaling Green: No overflow detected.

Buffer
Overflow Red: Overflow detected. For example: Add null packets
There are not enough null packets using the rate adapter.
available in the stream to insert the
signaling.
Local PID Green:

on Input The PID is inserted into the TS.
Red: A local generated packet is The incoming transport stream

using a PID that is already already contains all this
available on the input of the information. In this case it is not
device. needed to add signaling.
Check if the correct transport is
selected.

20.5 MPE Encapsulation

Multiprotocol Encapsulation is used to take in Ethernet data and insert it into a TS.
MPE is a data link layer protocol defined by DVB and published as: ETSI EN 301 192.
Using MPE makes it possible to transmit data along with the video transport stream.
This data can contain for example: software image files for DTH set-top boxes, Multi Home Platform
information or general low bit rate data for distribution in private networks.
The encapsulator replaces null-packets in the TS with useful payload of data packets. This
optimizes the use of the available bandwidth by using opportunistic data insertion. The user just
needs to define the bitrate of the carrier to something matching both streams at maximum load.
The TS will automatically be rate-adapted to the carrier rate and the MPE is inserted in it.
This feature works with any MPE capable receiver or IRD.
Input bit rates on the MPE input upto 70 Mbps are supported.
The MCX7000 supports up to 4 MPE Encapsulators.

It is possible to insert signaling and perform shaping on this data.

20.5.1 Configure MPE Encapsulation

Use this block to configure the multi protocol encapsulation settings.
» Log in as expert
» Click MPE Encapsulation

From this window it is possible to configure the following:

• Configuration table
• Programs table
• Channels table
• Nodes table (traffic shaping nodes)
Next to configuring the Multi protocol Encapsulation parameters it is also possible to monitor the
forward bit rate and dropped packets per transport stream and per program.

20.5.1.1 Select the TS to add MPE Data
Use this block to define on which incoming transport stream MPE data needs to be inserted.
» Click Add to insert MPE data into an available transport stream.
Name Enter a logical name for this encapsulation rule.
Enable Enable or disable the encapsulation rule.
Select TS Select one of the available transport streams, where MPE can be
inserted.
» Click Update.

20.5.1.2 Configure the Programs Table
The programs table holds the metadata about a program and is part of the MPEG TS.
The receiving device uses the metadata to identify the properties of the stream.
This information is added to the PAT (Program Association Table) and to the PMT (Program Map
Table).
The PAT lists all programs available in the transport stream. A program number can identify these
listed programs. Each of the programs listed in the PAT has a PID (Packet Identifier) for its PMT.
The program map table contains detailed information about the programs added to the TS. For each
program there is one PMT defined.
The following table is an example of a PAT containing MPE data.
Program Nr. PMT PID Content PID Content Type
1 1001 30 Video
1002 Audio
1005 Teletext
2 1501 31 Video
1502 Audio
3 2001 Video
2002 Audio 1
2003 Audio 2
15 4500 3500 MPE
» Click Add

Program Name Enter a logical program name.
Enable Enable or disable the program table.
Program Number Assign a unique program number into the program table.
Data PID Assign a unique Data Packet Identifier to the program.
PMT PID Assign a unique Program Map Table Packet Identifier to the program.
Config Select one of the available configuration rules (encapsulation rule).
When the Data and/or PMT PID value(s) already exist in the incoming transport
stream, a Signal Table Processing alarm is triggered.
» Click Update.

20.5.1.3 Configure the Channels Table
Channels are logical pipes that are used to transport shaped traffic. It is possible to combine traffic
coming from several traffic shaping nodes and insert them into one channel.
On the receiving end it is possible to filter on the different channels/AIR MAC Addresses.
Configure the receiver(s) to filter out the correct AIR MAC Address.
» Click Add
Channel Name Enter a logical channel name.
Enable Enable or disable the channel.
MAC Address The MAC Address typically identifies the remote receiver.
Assign a MAC Address to the channel.
Configure the receivers to filter out the correct (AIR) MAC Address.
Virtual Network Select the virtual network to capture traffic from the data ports or mgmt
ports.
• Traffic, capture traffic from the data interfaces.
(This is the default value!).
• Management,capture traffic from the mgmt interfaces.
Program Link the channel to an available program.
» Click Update.

20.5.1.4 Traffic Shaping
The following figure illustrates how the classified traffic is shaped by the traffic shaper.
Per classified traffic node, traffic shaping can be performed.
Classification rules must always be attached to the most specific shaping node in a
shaping tree.
Traffic shaping makes it possible to restrict the maximum given PIR (Peak Information Rate) in a
flexible way. Next to the PIR a CIR (Committed Information Rate) is used for the distribution of the
total available rate.
The traffic shaping software also allows the distribution of the available rate among services in order
to e.g. higher prioritize time critical VoIP traffic and to throttle certain downloads.
As shown in the next figure, a Parent Node can contain more sub nodes. These sub nodes inherit
the settings of the previous node and are then again divided in a PIR and CIR.

This is used to ensure that the available data rate is distributed in the most appropriate manner
among the users of the satellite network.
The traffic shaper provides adaptive traffic shaping, which makes it easy for shaping the traffic of
networks where the throughput of the link is varying over time.
Once the shaping is performed, the traffic is MPE encapsulated into transport streams and
forwarded to the correct output channel.

» Click Add
Node Name Enter a logical name for the shaping node.
Enable Enable or disable the shaping node.

This must be enabled (On), otherwise the node is not recognized and the
data cannot be encapsulated.
CIR Enter the Committed Information Rate for this Shaping Node.
PIR Enter the Peak Information Rate for this Shaping Node.
Priority Enter a priority for this shaping Node.

Use this setting to prioritize the shaped traffic
(for example: voice= 5, video=10)
(The lower the value that is entered, the higher the priority.)
Max Queue Define a queue time per shaping node.

time This is a buffer based on the FIFO (First In First Out) principle. The buffer
provides the possibility to store an amount of data in a shaping node. When
the queue time is exceeded, data will be dropped.
Classification It is possible to define an expression to classify/filter out specific traffic.

Expression This expression can be standalone or combined with the Network Address
Note that the syntax of the expression is being checked while typing.
Refer to Appendix - Classification Expressions on page 393 to get an overview of
the possible expressions.
Some examples are:
• ip4 dst net x.x.x.x/xx (this is layer 3)
• Filter out all icmp traffic with a rule like this:
(ip4 dst net xxx) and (icmp type echo-request)
• Give priority to same traffic for one specific host: ip4 dst host 10.10.20.5
• All (Layer 2 Forwarding Mode)
Matching Order The matching order defines the order in which packets are processed by the
classification rules. This is important for disambiguation when multiple
classification rules match the same packet.
The order ranges from 1 (match first) to 99 (match last).
Destination Select a channel where the traffic must be sent to.

Channel
One channel can have several nodes and shaping rules.
» Click Update

Configure the Remote In-band Management Feature MCX7000 Multi-Carrier Satellite Gateway
21 Configure the Remote In-band Management

Feature
The remote In-band management feature is integrated into the MCX7000 to make it possible to
remotely control a device. A bidirectional link is required between two operational MCX7000 for the
management forward and return link (this can be done over a terrestrial line). The receiving device is
capable of handling all routing functionality internally. This way the device does not require an extra
loopback connection between the data and management interface.
The feature makes use of the MPE encapsulation and decapsulation processing blocks to transport
the management traffic. This mechanism is explained by using an example in the following sections.
Use the In-band management feature to:

• Manage the remote MCX7000 and perform firmware upgrades, license upgrades, monitoring and
configuring this device.
• Manage a device that is connected to one of the management interfaces of the receiving
MCX7000 via a switch or a router.
• Manage several remote networks.

21.1 Remote In-band Management Setup

The following figure shows an example setup between two MCX7000 devices. Transport streams
are modulated and broadcasted over the satellite link.
The remote in-band management feature only works in a Layer 3 setup!

(The data traffic plane can be in Layer 2 or Layer 3.)
The data traffic and management traffic are in a different subnet and this way
completely separated from one another!
In this case we assume:

• That the data traffic plane is already up and running.
Note: The data traffic and management plane are in a different subnet and this way completely
separated from one another!
• Enough null packets exist in the TS stream to do MPE encapsulation (to insert the Mgmt traffic).
• That the carrier settings are configured correctly (RX Lock).
The following sections explain how to configure the MPE encapsulator (sending site) and the MPE
decapsulator (receving site).

21.2 Encapsulate the Mgmt IP Traffic

The following figure shows how the Mgmt traffic is encapsulated into a TS to set up the remote
management link.
Have a look at the following video to see how to configure the MPE encapsulator output processing
block.
MPE Encapsulation.mp4
The following figure shows the MPE encapsulation mechanism in a static way.
This drawing is also used in the video to illustrate' the mechanism of the
encapsulation process. The drawing is not part of the GUI itself.
The following actions are performed:
» Make a Mgmt IP connection between the Mgmt PC and the MCX7000.
» Make sure that the Mgmt PC can reach the next hop (routing tables should be configured
correctly on the Mgmt pc).
Refer to section: Management IP Connectivity on page 103
» Configure the MPE Encapsulation block (Available as expert under the Output Processing block)
» Enable MPE Encapsulation
» Add and enable a Mgmt Program in the programs table.
» Add a Mgmt channel configuring a specific MAC Address and selecting the Management Virtual
Network (capturing traffic arriving on one of the Mgmt ports).
» Do not forget to make a coupling with the Mgmt Program.
» Configure the traffic Node, including the traffic classification rule!
» Add a classification rule to filter the Mgmt IP packets for 10.253.2.64/24 (destination device on
the remote site).
» The classification rule looks as follows "ip dst host 10.253.2.64" or ip dst net 10.253.2.0/24"

21.3 Decapsulate the Mgmt IP Traffic

The following figure shows how the Mgmt traffic is decapsulated from the TS.
Have a look at the following video to see how you can configure the remote management link.
Decapsulation.mp4
The following figure shows the MPE decapsulation mechanism in a static way.
Note: This drawing is also used in the video to illustrate' the mechanism of the
decapsulation process. The drawing is not part of the GUI itself.
The following actions are performed:
» Make a Mgmt IP connection between the Mgmt PC and the MCX7000.
» Make sure that the Mgmt PC can reach the next hop (routing tables should be configured
correctly on the Mgmt PC).
Refer to section: Management IP Connectivity on page 103
» Configure the MPE Decapsulation block (Available as expert under the Output Processing block)
» Enable MPE Decapsulation.
» Add and an enable a Mgmt Program in the programs table.
» Add a Mgmt channel configuring a specific MAC Address and selecting the Management Virtual
Network (capturing management traffic and forwarding it to one of the Mgmt ports).

Configure the Probes MCX7000 Multi-Carrier Satellite Gateway
22 Configure the Probes
22.1 TS Analyzer
The transport stream analyzer makes it possible to monitor the transport streams on different
locations in the device. The purpose of this feature is to help determine if a problem seen at the
output of a satellite receiver is due to a problem on the satellite link or to a problem in the head-end
before the MCX7000.
Consequently, it provides the possibility to identify the root cause of service outages that happened
in the video head-end, or on the transmission path between the video MUX and the satellite
modulator. Because the analyzer is built into the MCX7000, inserting it does not change the
behavior of the signal or the topology of the network, making the troubleshooting easier. This leads
to a shorter defect resolution time.
The following figure shows an example where the TSA probes (maximum two) can be inserted.

Location
Configure
» Click Add

» Click Update
It is possible to create two TS analyzers.
This way it is possible to monitor transport streams on different locations in the device.
• The TS analyzer can be enabled at any time.
• It is possible to reset the TS analyzer to restart an analysis of the incoming transport stream.
When the user enables or resets the TS analyzer the following alarms are reported:
• Pat_error
• Sync_byte_error
• TS_sync_loss
These alarms should disappear after five seconds. When these alarms do not
disappear after five seconds it is needed to check the transport stream that is being
analyzed.
Monitoring Table
Variations in the Transport Stream bit rate may indicate errors in the video processing head-end
preceding the satellite modem, in video source losses, still pictures, failing video encoder etc.
The measured bit rate is accurate to the nearest entirely loaded packet.
For example: for an incoming bit rate of 2250000 bps or 149,6 TS packets/s. The actual
measurement should be 149,6 packets/s but this value is rounded off to 149 packets/s.
This translates into a measured bit rate = 149 x 188 x 8= 224096 bps.
In case of TSoIP input, measurement is done after some jitter removal, but before the full rate
smoothing performed just before the modulation stage. Jitter on the incoming signal may thus affect
this measurement.
While not being a full-fledged TS analyzer, this feature provides most of the
measurements needed for a good tracking of the origin of issues seen in a typical
head-end.
22.1.1 Error PID Table

This table summarizes the PIDs for which a PCR error was detected and displays the PID type. The
table also indicates any continuity count error and transport error.

22.1.2 PCR PID Table

This table lists all the PIDs that contain a PCR (Program Clock Reference) and the related
measurements.
The PCR PID table is available in combination with the CBR traffic profile. With the VBR traffic
profile, this table is not populated.
The following values are provided:
Measurements Description
PCR Interval Measured interval time (in ms) between two consecutive PCR packets.
Repetition Error PCR repetition error.
Accuracy Error PCR Accuracy Error.
Min PCR_AC Minimum value of PCR accuracy value (nanoseconds) over the last
second.
Max PCR_AC Maximum PCR_accuracy value detected over the last second.
Min Peak PCR_AC Lowest PCR_accuracy value detected since last reset (with an initial
wait time of a few second).
Max Peak PCR_AC Highest PCR_accuracy value detected since last reset (with an initial
wait time of a few second).
Rate Offset Offset in ppm between the rate computed from the PCR values and the
actual rate. The actual rate is the measured rate in case of ASI inputs, or
the user-defined rate in case of TSoIP input.
Note: as the device clock has a precision of around 1

ppm, the rate offset is also an indication of the clock
offset between the source device (encoder or
multiplexor) and a true reference (with 1 ppm precision).
The rate offset is thus also an indicative measurement of
the PCR clock offset, while not being a formal
measurement of this value as defined in the standard.
PCR Rate Displays the current rate calculated from the PCR values in the
corresponding PID.

22.1.3 PID Table

This table lists all the PIDs that are present in the stream.
The following information is displayed in the table.
Information Description
PID Displays the PIDs that are present in the stream.
Type The PID type that is detected.
PID Rate Displays the PID rate.
Continuity Count Indicates if a continuity count error is detected.

Error
Transport Error Indicates if a transport error is detected.

22.1.4 NIT Carrier ID Table

This table lists the NIT Carrier parameters.
For more information on the parameters please refer to section: NIT Carrier Identification. on page 304
22.1.5 TS Analyzer Alarms Status Overview

The detection of the following MPEG errors status overview:
Note these Errors are defined in the following standard: TR101 290.
(The error explanations in this manual are kept short and intuitive.)
• All the errors trigger the corresponding alarm. These alarms are also displayed in
the alarms pane of the GUI.
• The TS analyzer errors are associated with an interface alarm and they can be
used for redundancy purpose.

1_1 Sync_loss Absence of two or more SYNC bytes regularly spaced.
1_2 Sync_byte_error The correct sync byte (0x47) does not appear after 188 or 204 bytes.
1_3 PAT_error No valid PAT detected.
1_4 This error is usually caused by a disorder of the packets, by the loss of
Continuity_count_error a packet or by the duplication of a packet.
2_1 Transport_error Transport_error: A Transport_error_indicator flag is set in the

TS-Header of a packet.
2.3a Time interval between two consecutive PCR values is more than 40
PCR_repetition_error ms.
2.3b The difference between two consecutive PCR values (PCRi+1 –

PCR_discontinuity_ PCRi) is outside the range of 0...100 ms without the discontinuity_
indicator_error indicator set.
2.4 The PCR accuracy of a program is not within ±500 ns.

PCR_accuracy_error
The PCR_accuracy is measured using the MGF3
filter profile. Please refer to the TR101 290
standard for more information on this filter profile.

22.2 PRBS Probe

Use the PRBS detector to monitor an incoming PRBS stream.
The following figure shows an example where it is possible to enter a PRBS probe.
Log in as expert.

Location
Configure
» Click Add.

Enable Enable or disable the probe.
From Type Select on what type of interface to insert the probe.

Most commonly this is done on the demodulator.
From Name Select the exact position of the probe.

(If there is only one demodulator, the default is Demod-1).
PID Handling Enable PID handling in case a PID is inserted by the PRBS generator.
PID Value The PID value must match the PID value inserted on the PRBS
generator.
When this is not the case the PRBS stream will not be detected by the
probe causing an unsync state in the monitoring table.

Tasks MCX7000 Multi-Carrier Satellite Gateway
23 Tasks
23.1 Device Tasks
23.1.1 Configurations
» Log in as Operator or Expert (Refer to section: Switch User Profile on page 55)
» Navigate to the Tasks Pane
» Click Device
» Click Configurations
From this menu it is possible to manage the configurations of the device.

Use the menu to perform the following tasks:
Directly from this menu:

• Save the current configuration (in bold in the list)
• Import a configuration
From the Actions Menu (click on the following icon )
• Load a configuration
• Export a configuration
• Delete a configuration
• Make a configuration.bootable

On the front panel it is possible to perform the following actions:

• Device Reset
• Device Configuration Load
• Device Configuration Save
MCX7000>>Actions
23.1.1.1 Configuration File
There are two kinds of configuration sets stored on the device:

• Configuration files with device specific parameters.
• Configuration files with application specific parameters.
Device Specific Parameters
These parameters are used to set up device specific settings and they are excluded from the
imported/exported configuration files. This is done to avoid losing connectivity with the device after
loading a new configuration file or after a redundancy switch-over. The device specific parameters
are:
– Mgmt Gateway IP Address
– Mgmt Interface IP Addresses
– Data Interface IP Addresses
– Device Identification Label
– Link Redundancy priority (None, Mgmt1 or Mgmt2, Mgmt1 before Mgmt2, …);
– Device Redundancy state (Enable, Initial State, Operational State)
The device specific parameters cannot be consulted or exported to an XML file.

Application Specific Parameters

These parameters are specific to the application settings.
All these settings are stored in an XML file. The following figure is an extract of such an XML file.
The XML or configuration file provides the possibility to import or export the device application
specific parameters.
This configuration file can be useful as a back-up file, to debug or configure the device offline.
It is possible to store up to 48 different configuration files.
To view or download a configuration file, see section: Export a Configuration. on page 339
Configurations can be reused among devices in case the same licenses are
applicable.

23.1.1.2 Active Configuration
The active configuration is the configuration that is currently used on the device.
This configuration is in bold in the configurations list.
The active configuration is not necessarily a configuration that is saved on the device.
When a configuration is completed, it is recommended to save this configuration onto
the device.
Check the LED Cfg saved in the status bar to see if the active configuration is currently saved or
not.
23.1.1.3 Saved Configuration
A saved configuration is a configuration that can be recalled at any time by an operator to modify the
device behavior according to pre-defined settings.
For example: perform tests or prepare a migration of the device settings.
» Navigate to the Tasks Pane (GUI) to check the available configurations
» Click Device
» Click Configurations. (The available configurations are listed.)

The active configuration is indicated in bold.
The boot configuration is loaded on the device during a reboot. (The boot configuration is recognized
by a boot BOOT.-flag)

23.1.1.4 Save a Configuration
When parameters are changed, they are not directly saved into the active configuration.
» Navigate to the Tasks Pane to check the available configurations
» Click Device
» Click Save…
» Enter a Name or select a configuration using the drop down list.

Use this menu to Save the current configuration.
Saving the current configuration makes it the default configuration.
This does not mean that it becomes the boot configuration.
By default, the selected configuration is overwritten upon saving. Enter a name to

save the configuration under a new configuration file.
23.1.1.5 Import a Configuration
Import a configuration file that can be used as a new configuration.
» Click Device
» Click Import
» Browse to the correct folder and select the correct config.xml file
Please note that after an import of a configuration, the configuration is not loaded automatically.
This requires an additional load step, refer to Load a Configuration. on page 338
The configuration file must comply with the available configuration options and
activated licences on the device.

23.1.1.6 Load a Configuration
Use this procedure to load a configuration file that is available in the configuration list.
The loaded configuration becomes the active configuration.
» Click Device
» Click the Config Name you want to load
» Click the following icon
» Click Load Config…

23.1.1.7 Export a Configuration
Use this to export a configuration file.

Depending on the management interface GUI or CLI the following is done:
– GUI: The file is downloaded by the browser
– CLI: The file is available on the FTP server.
» Click Device
» Click the in front of the Config Name you want Export
» Click Export to export the XML file to a default folder (GUI) or to the FTP server (CLI)
The exported file can be:

• Used as a backup file
• Edited offline and reused on another device In this case.
– Make sure that the configured options and activated licences are the same on
both devices.
• Forwarded for debugging purposes.

23.1.1.8 Delete a Configuration
Delete a configuration file from the device when it becomes obsolete.
» Click Device
» Click the Config Name you want delete
» Click Delete…
Deleting a boot configuration causes a factory reset of this boot configuration!

All application specific parameters are reset to their default values.
Traffic can be impacted.

23.1.1.9 Make a Configuration File Bootable
» Click Device
» Click the Config Name you want make the boot configuration
» Click Make Boot to make the selected configuration the boot configuration.
– The boot configuration is indicated as BOOT.
A boot configuration is used to set all parameters to their correct value at boot time.
This implies that the management parameters (for example redundancy settings),
Input / Output parameters are set according to the network requirements.
Once you have configured the device it is recommended to save the configuration and
make the configuration bootable.
This is mandatory in order to keep the configuration after a power interruption.
Refer to section: Save a Configuration on page 337 .

23.1.2 Configuration Templates

Import a configuration template. (For more information see section:
Quick Configuration trough Templates). on page 133
» Click Device
» Click Configuration Templates
» Click Load Template
» Browse to the correct folder and select the correct template
Please note that after an import of a configuration template, the current configuration settings are
overwritten.
An explicit save action is needed to save the new settings.
To save this configuration please refer to section: Save a Configuration. on page 337

23.1.3 Reset the Device
Resetting the device causes data loss on an active link!

When a user wants to perform a reset using the front panel or CLI, no caution
message is displayed!
The device can be reset when needed.
» Click Device
» Click Reset
Different reset types are possible:
• Hardware: Resets the software and the hardware (=reboot).
• Software: Resets the software.
• Configs: Resets the application specific parameters of all existing configurations.
For connectivity reasons, the device specific parameters are excluded from this reset. For more
information please refer to section: Configuration File on page 334
• Factory: Resets all parameters to their default values.
This action is only possible via the CLI interface.
A factory reset removes all stored configurations.

All IP settings are reset to their default values, meaning that the device may become
unreachable!

23.1.4 DSNG Profiles
23.1.4.1 DSNG Profiles Import
Import a configuration file that can be used as a new configuration.
» Click Device
» Click DSNG profiles import...
» Browse to the correct folder and select the correct DSNG config.xml file
» Click Update
Please note that after an import of a configuration, the configuration is not loaded automatically.
This requires an additional load step, refer to Load a Configuration. on page 338
The configuration file must comply with the available configuration options and
activated licences on the device.
23.1.4.2 DSNG Profiles Export
Use this to export a configuration file.

Depending on the management interface GUI or CLI the following is done:
– GUI: The file is downloaded by the browser.
– CLI: The file is available on the FTP server.
» Click Device
» Click DSNG profiles export to export the current configuration file to a default folder (GUI) or to
the FTP server (CLI)

23.1.5 Auto Save Configuration

When enabled, any change made to a configuration setting is automatically saved to the active
configuration file.
» Log in as expert
» Navigate to the following location to enable this parameter
Before enabling this parameter it is advised to make a backup file. This allows to
roll-back to the previous configuration.

23.2 Toolbox
23.2.1 Diagnostics Report

Use this to get an overview of the complete configuration and get debugging information of the
device. This report can be requested by the Customer Service department to perform debugging on
the device. In most cases it is advised to let the Customer Service department analyze this report.
The document can be viewed using the GUI or downloaded as a text file.
Proceed as follows:
» Click Toolbox
» Click Diagnostic Report
» Select one of the following:

– View: Opens the report in a separate browser window.
– Download: Downloads a diagnostics.txt file.
– Download (Debug): This downloads an encrypted diagnostics report file and is only for use
by the Newtec the Customer Service department.
The following figure is an extract of a diagnostics report:


23.3 Maintenance
23.3.1 Software Upgrade

A software upgrade is needed:
• To provide bug fixes and/or software enhancements.
• To activate a new functionality in the device.
The upgrade procedure is explained on the next page.
This activation/upgrade can require a license update as well.

Refer to section: Licence File on page 350
Depending on the ordered Care Pack the customer will be informed when a new
software release is available. For more information on Care Pack we refer to section:
Care Packs on page 6.
23.3.1.1 Software Upgrade Procedure
Use the applicable software upgrade file (installer.bin).

Proceed as follows to perform a software upgrade:
» Log in as operator or expert
» Click Maintenance
» Click Software Upgrade....

The following window opens:
» Browse to the folder where the "installer.bin file" is stored

» Select the file and click Open

The following message is displayed:
Software Upgrade:
This operation will reboot your device!
Are you sure, you want to upgrade the device firmware with the content of
"installer.bin"?
» Click Upgrade
Refresh the browser after about 40 seconds.
To perform a software upgrade using the CLI please refer to section:

Software Upgrade (CLI) on page 48
To perform a software upgrade via the USB port on the front panel refer to section:
Using the USB Port.

23.3.2 License File

A license file contains the information about all the features/options that are enabled or disabled on
the device.
A license file is device dependent.

When the license file is not valid, the device has limited functions.
The only possible actions are configuring the management interfaces and updating the
license.
23.3.2.1 License Upgrade
Importing a license file is done when a new functionality needs to be activated.
Save your boot configuration before performing a license upgrade to a temporary

license.
• Please refer to section: Save a Configuration on page 337 .
• Please refer to section: License Type on page 89 for more information on the
possible license types.
» Log in as Expert (Refer to section: Switch User Profile on page 55)
» Navigate to Maintenance
» Select License Upgrade
» Browse to the folder where the new license.ini file is stored
» Select the licence.ini file and Click Open
The following message is displayed:

Importing / upgrading a licence file reboots the device!

After the upgrade, the device reboots:

• Using the boot configuration (if the settings are compatible).
• Using the initial configuration or factory default (if the settings are incompatible).
» Click Upgrade
» After the upgrade, a message is displayed that the upgrade was performed successfully
» Verify if the new functionality is active

23.4 Logging
Enable or disable logging.
Logging can be performed on the following levels:
• Local device logging.
Log files can be exported or cleared, refer to Export or Clear Logging. on page 355
• Remote logging using a remote syslog server (Syslog is a standardized mechanism for logging in
computer systems.).
When remote logging is enabled and a remote IP address is inserted all logging information is
forwarded to this address. The logging messages are packed in UDP (User Datagram Protocol) and
sent to a specific UDP port (514 according to the syslog standard).

Location

23.4.1 Syslog Filter

It is possible to assign up to nine different log levels to the following facilities.
Facility Log Description
Alarms An alarm is detected on the device.
Configuration Configuration changes on the device.
System System changes on the device.
Internal error An internal error is detected on the device.
Authentication User logged in.
Networking Everything related to network interfaces.
The default log level (info) is hard coded. The lower the filter level, the more entries
appear in the log file which may adversely impact the performance of the device.
Level Description
Emergency The system is unusable.
Alert Action must be taken immediately.
Error Critical conditions.
Warn Normal but significant condition.
Notice Notification messages.
Info Informational messages.
Debug Debug level messages.
Trace Debug level messages.
Off No logging is performed.

23.4.2 Export or Clear Logging

» Click Logs
» Click Device Log

Use this menu to View or Download the local board logging.
• When a view is requested, the log file is opened in a separate browser.
• When a download is requested, a text file is downloaded.
• When a Clear Device Log is requested, the logging information is removed.
A new log file is started. This can be useful to perform debugging.

23.4.3 Interpretation of a Device Log File

A standard log file looks as follows:
[configuration-INFO][2012-12-16 10:27:53] writeValue
/Root/SystemAlarm/Log/Source=GeneralInterface
[alarms-INFO][2012-12-16 10:27:54] alarm General Interface: OFF
Facility Log Level Time Extra information

Stamp about the action taken
[configuration - INFO] [2012-12-16 writeValue

10:27:53] /Root/SystemAlarm/Log
/Source=GeneralInterfa
ce
[alarms -INFO] [2012-12-16 alarm General

10:27:54] Interface: OFF

23.5 Equalink® 3
Predistortion is applicable for a single carrier per transponder scenario.
As shown on the figure above, a satellite payload contains an input multiplexing (IMUX), a traveling
wave tube amplifier (TWTA), and an output multiplexing (OMUX) filter. The IMUX filter selects the
input frequency band of your transponder (which is often a bit wider than your carrier). The TWTA
amplifies your signal. A side effect of this amplification is frequency components generated outside
the initial signal bandwidth.. Therefore, the OMUX filter cuts away unwanted frequencies to avoid
interference in other frequency bands. Because the average power of the signal arriving at the
TWTA varies (e.g. due to rain in the uplink), a pre-gain stage is included in most payloads,
performing automatic level control (ALC) which keeps the drive level of the TWTA constant.
The goal of Newtec's Equalink 3 technology is to achieve the most efficient communication. At first,
efficient communication implies bandwidth efficient communication. To get most out of your
transponder, your carrier bandwidth should approach the bandwidth of the IMUX/OMUX filters.
Because these filters operate at very high frequencies in extreme conditions, imperfections in the
filter response introduce linear distortion into your signal.
Linear Equalink 3 will compensate for this linear distortion so that you can extend your carrier
bandwidth.
Secondly, efficient communication implies power efficient communication. To get most out of your
transponder, your carrier signal should get amplified as much as possible by the TWTA, which is
achieved by increasing the drive level of the TWTA., Equalink 3 can compensate for the Non-Linear
distortion that is introduced by the Non-Linear amplification, so that you can extend the drive level.
Summarizing, Equalink 3 optimizes the satellite link performance by counteracting distortion effects
(linear and non-linear distortion) in a satellite link.
The performance of Equalink 3 depends on many factors (the type of TWTA and its drive level, the
characteristics of the IMUX and OMUX filters, the uplink and downlink noise, the characteristics of
your signal, ...).

The Automated Equalink 3 calibration procedure is designed to automatically take into account all
these factors to configure Equalink 3 in the best possible way with minimal user interaction.
A detailed document describing the automated Equalink 3 calibration procedure can

be delivered upon request.
Please use the Newtec Service Desk tool to receive more information.
> Create a ticket
In response to your request you will receive the document from our support team.
In order to do a complete Equalink 3 calibration, the following procedures are typically performed in
the presented order:
• Satellite Link Analysis (to verify the present conditions, such as the TWTA drive level, and uplink
and downlink noise level).
• Automated Linear Equalink 3 Calibration (run and enable afterwards).
• Automated Non-Linear Equalink 3 Calibration (run and enable afterwards).
• Satellite Link Analysis
(to verify the link optimality and to give an overview of the gain of Equalink 3).
For broadcast or distribution links that are using a single carrier per transponder, both linear and
Non-Linear pre-distortion can give much link margin gain.

23.6 Documentation
23.6.1 Open the Reference Manual

From this menu it is possible to open the GUI reference manual with a browser.
The reference manual displays the location of the different parameters in the data model.
Use the reference manual to:
• Check the location of the parameters in the data model, this data model is reflected in the Tree
View.
• Check the default values of the parameters.
• Check which profiles have Read/Write Access.
• A small description of the parameter is also included.
Location
» Log in as operator or expert
» Click Reference Manual

The reference manual is opened in a new browser window.

23.6.2 Download the SNMP MIB Files

The SNMP MIBs can be downloaded using the GUI interface.
» Navigate to the Tasks Pane (GUI)
» Click Documentation
» Click SNMP MIBs

A mibs.zip file is downloaded and stored on the default folder of the management device.
The SNMP MIBs are also delivered on CD-ROM together with the device.

Alarm Handling MCX7000 Multi-Carrier Satellite Gateway
24 Alarm Handling
Alarm handling allows you to configure and manage the behavior of the different alarms in the
device.
Meaning that it is possible to
• Mask (hide) alarms.
• Assign alarms to a general interface or general device alarm.
Newtec Redundancy Switching Units use these two alarms in their switching logic.
Location
» Navigate to the following location to perform alarm handling.
List of Alarms
The alarms that can occur are explained in the relevant sections.
For example:
• When a modulator alarm occurs, refer to section Modulator Alarms Status Table on page 182 for
more information.
• When an TS over IP Input alarm occurs refer to section.
This function is available via the GUI, CLI and SNMP but not through the front panel:

24.1 Alarm Masking

You can mask individually selected alarms. This means that you can hide alarms.
Be careful when configuring this, as a masked alarm is not recognized anymore by the
MCX7000.
Alarm masking can also impact device redundancy, this because the alarm is not propagated
into a general device or a general interface alarm.
For more information please refer to section: Alarm Configuration. on page 364
Example on the behavior of a masked alarm.

Eth Data2 Link Failure: Alarm Mask = Off
1. No active alarms are present (normal behavior of the MCX7000).
2. The Ethernet cable of Eth Data2 is removed.
3. The Eth Data2 Link Failure alarm is raised.
– On the front panel the active alarm LED lights up according to the alarm that is present.
– On the overview page of the GUI the Data2 arrow turns red.
– The Alarm Pane shows the following:

Eth Data2 Link Failure: Alarm Mask = On

1. No active alarms are present.
2. The Ethernet cable of Eth Data2 is removed.
3. The "Eth Data2 Link Failure" alarm is masked so no alarms are triggered!

24.2 Alarm Configuration

The alarm configuration provides the flexibility to define per Alarm, whether or not the alarm is
linked to a General Interface and/or General Device alarm.
This way the customer is able to define whether or not this specific alarm triggers a redundancy
switch over as the redundancy system bases a switch over on one of these two alarms.
Be careful when changing the alarm configuration, as the general interface and general alarms
help to protect your device in critical situations.
For example, the "Temperature alarm", by default generates a general device alarm. The
general device alarm switches off the main functional blocks of the MCX7000, to reduce the
CPU load of the device.
In case the default setting is overruled and the general device alarm is not triggered, the device
can become overheated.
The alarms are still recognized by the MCX7000 meaning that the alarm is displayed in the alarm
pane and that the related functional block/arrow in the GUI changes color (turn red).
For example:
We want that the "Eth. Mgmt Itf Link Failure" alarm triggers a General Interface Alarm.
(The reason could be that this alarm must trigger a switchover to a redundant device).
Note that a "Mgmt Itf Failure" by default does not trigger the alarm switches. To change this behavior
you have to assign the "Mgmt Itf Failure" alarm to a General Interface or General Device alarm.
(Whether to choose the General Interface or General Device alarm depends on the configuration of
the Newtec USS (Universal Redundancy Switch).
The following figure shows the configuration of the "Eth Mgmt Itf Failure" alarm.
The next time when the Eth Mgmt Itf Failure alarm is present, a General Interface alarm is triggered.

The Alarms pane looks like:
24.3 Clear Alarm Counters

Alarm counters are present in the Alarms Pane on page 65 of the GUI and can be cleared all at once.

Appendix - Configuring the Output Rate Mode MCX7000 Multi-Carrier Satellite Gateway
25 Appendix - Configuring the Output Rate Mode
25.1 Output Rate Mode Auto (ISSY)
25.1.1 ISSY for Transport Stream Bitrate Recovery

The ISSY implementation uses a de-jitter buffer to store the transport stream packets contained
within the baseband frames.
The user has the flexibility to control the filling level used by this de-jitter buffer. The filling level is
expressed in a number of transport stream packets.
Because the filling level is a certain number of transport stream packets, the delay introduced by this
de-jitter buffer becomes bit rate dependent.
A filling level of 1500 transport stream packets for example (default value) results in a delay of ~2250
ms @ 1 Mbps, ~225 ms @ 10 Mbps and ~75.2 ms @ 30 Mbps.
Depending on the delay requirements for the receive chain, the correct filling level should be chosen
by the user if the default value is not suited.
The filling level for the ISSY de-jitter buffer accepts a wide range of values. There is a minimum value
to guarantee proper behavior.
General rule of thumb is to use low filling levels for low bitrates and increase the filling level when
the bitrate is higher.
A good practice is to target for a delay of ~100 ms, use following formula to calculate the filling level:
(bitrate [bits/sec] * desired_delay [sec]) / 1504.
When the transport stream bitrate is low (<10 Mbps), short frames are most suited to keep the delay
under control.
Nevertheless the setting may be dependent on your application and your desired demodulation
delay.

25.2 Output Rate Mode User Defined

Transport streams (TS) received by the device can be sent to the TSoIP outputs.
When send to the TSoIP outputs, the device output rate mode settings will ensure:
eliminated.
For this reason, the device incorporates methods (referred to as control loop) that produce very
clean outputs and eliminate the jitter created by TSoIP inputs or the satellite transmission:
• OutputRateType [UserDefined]
• ControlLoopType [None, NTC, DVB]
In DVB-S or in DVB-S2 single stream, the input rate is always derived from the
symbol rate and the satellite transmission does not introduce significant jitter.
25.2.1 Output Rate Type - User Defined

UserDefined: The user enters the output bitrate manually. The bitrate should be correct within ± 30
ppm for proper behavior of the control loops ( NTC and DVB ).

25.2.2 Control Loop Type [None, NTC, DVB]

The ControlLoopType allows the user to define how the device will minimize the TS jitter on its
outputs.
• None:
There is no control loop: the TS is simply sent at the a given bitrate
(see Input Rate Type - User Defined) on page 367), if TS packets are available in the transmit buffer.
If the actual TS bitrate is lower, this will generate some jitter. If the actual TS bitrate is higher, this
will result in packet loss, after some time, due to transmit buffer overflow. This method is very
convenient for simple applications where jitter control is not important (for example if the device
using the signal compensates for it), or if the actual TS bitrate cannot be known with precision
(or is actually unstable). Best practice is to set the bitrate high enough, so that transmit buffer
overflow will not occur.
• NTC:
With this method, the device adjusts the output bitrate to make sure that the actual rate of the TS
is tracked, even if that rate varies (or is imprecise) due to clock drifts (or offsets) in the system.
This automatic compensation is limited to ± 30 ppm maximum. In regime, this method provides
full DVB compliance, but will introduce higher jitter in case of perturbations (or at startup), in
order to recover in the fastest way.This is the recommended method. It works in most situations.
• DVB:
This method is similar to the NTC control loop, but it ensures that the output bitrate never varies
more than what is allowed by the DVB specification, making sure that PCR jitter is lower than
500 ns and PCR drift lower than 10 ppm/hour. The signal is thus most of the time DVB-compliant,
but the drawback is that the control loop is far slower and will compensate for errors far more
slowly. It is thus to be used only where DVB-compliance of PCRs has to be guaranteed at all
time. This method is recommended for setups with good PCR information and where jitter is
under control. But in case of perturbation, it will converge back to a stable situation in a far longer
time.
The default selection of this parameter is DVB.
On the TSoIP output, this parameter is not visible, because the None method is
always used. It is precise enough compared to the jitter of IP networks. The other
methods do not bring additional value.

25.2.3 Buffer Delay and Maximum Buffer Delay

The device will receive TS packets on its TSoIP in bursts. In order to generate clean and constant
bit rates, the TS packets have to be buffered. These buffers absorb thus any bit rate variations due
to clock drifts and IP transmission jitter.
In the output rate mode UserDefined (manual mode), the buffer control parameters are:
• Buffer Delay [ms] indicates amount of jitter that can be absorbed by the device. This will be
equivalent to the average latency introduced by the device. The device will try to keep the buffer
filled at this level.
• Maximum Buffer Delay [ms]: Maximum size the buffer is allowed to reach:
Typically, it is twice the Buffer Delay value.
The device will generate an alarm as soon as the Maximum Buffer Delay is reached, this to
detect an overflow problem.
For the ControlLoopType = None the buffer delay is close to zero.

25.2.4 Buffer Alarms
Buffer Overflow The Maximum Buffer Delay is reached. Packets will be dropped in the
device. If this alarm occurs, the device will try to recover from the
situation by resetting the buffer (i.e. it is emptied), and restart
transmitting TS packets.
Buffer Underflow The input buffer is empty and the device can't send TS packets to
guarantee a constant bit rate. Jitter will in that case appear on the
output. This alarm can occur only with the ControlLoopType set to NTC
or DVB.
Buffer Delay Too The value for the Buffer Delay, when translated into a number of TS
High packets, leads to a value larger than the physical buffer available. This
can occur at high bitrates or at high Buffer Delay values.
No output This alarm is triggered if there is no packet sent to the output of the
device for a longer period of time, while the output is enabled.

Appendix - Specifications MCX7000 Multi-Carrier Satellite Gateway
26 Appendix - Specifications
26.1 Data Interfaces

ASI INTERFACE (OPTIONAL)
Single stream mode
• 2 selectable ASI inputs on BNC (F) – 75 Ohm (coax)
• 2 x ASI output on BNC (F) – 75 Ohm (coax)
• 188 or 204 byte mode
• Rate adapter
• MPTS or SPTS according to ISO/IEC 13818
Multi stream mode

• 6 BNC(F) - 75 Ohm (coax) connectors individually configurable as input or output or as 3
redundant TS inputs with auto switching
• Rate adapter
ETH INTERFACE
• Auto switching 10/100/1000 Base-T Ethernet interface
• Transport stream over IP interface (UDP/RTP)
• Forward Error Correction SMPTE 2022-1 and -2
• Rate adapter
26.2 Content Encryption and Protection

BISS ENCRYPTION (OPTIONAL)
• Support for BISS-0, BISS-1 and BISS-E
• On one single TS (SPTS or MPTS)
26.3 IP Encapsulation
• Optional 4 MPE Encapsulators
• Max aggregate 70 Mbps

26.4 IP Decapsulation
• 4 MPE Decapsulators
• Max aggregate 70 Mbps
26.5 Modulation and Demodulation

SUPPORTED MODULATION SCHEMES AND FEC
• DVB-S
Outer/Inner FEC: Reed Solomon / Viterbi MODCODs:
QPSK 1/2, 2/3, 3/4, 5/6, 7/8
• DVB-DSNG
Outer/Inner FEC: Reed Solomon / Viterbi MODCODs:
8PSK 2/3, 5/6, 8/9
16QAM 3/4, 7/8
• DVB-S2 (acc. ETSI EN 302 307 v1.2.1 for DVB-S2)

Outer/Inner FEC: BCH/ LDPC
52 MODCODS (short & normal frames):
QPSK From 1/4 to 9/10
8PSK From 3/5 to 9/10
16APSK From 2/3 to 9/10

• DVB-S2X Standard
Outer/Inner FEC: BCH/ LDPC
53 MODCODs (normal frames):
QPSK From 1/4 to 9/10
8PSK From 3/5 to 9/10
16APSK From 26/145 to 9/10
128APSK 3/4; 7/9
256APSK 32/45; 3/4
13 Linear MODCODs (normal frame):
8APSK-L 5/9; 26/45
16APSK-L From 1/2 to 2/3
32APSK-L 2/3
64APSK-L 32/45
256APSK-L 256APSK-L
41 MODCODs (short frames):
QPSK: From 11/45 to 8/9
8PSK: From 11/45 to 8/9
8PSK: From 11/45 to 8/9
32APSK: From 2/3 to 8/9
• Support of DVB-S2 VCM mode (on modulator and demodulators)

SYMBOL RATE RANGE

Modulator
• DVB-S2, DVB-S2X 256 kbaud - 133 Mbaud
• DVB-S & DVB-DSNG 1 - 45 Mbaud
Demodulator
• DVB-S2, DVB-S2X 256 kbaud - 133 Mbaud
• DVB-S & DVB-DSNG 1 - 45 Mbaud
FRAME LENGTH
• DVB-S & DVB-DSNG 188 bytes
• DVB-S2 & DVB-S2X Short Frames 16200 bits
• DVB-S2, DVB-S2X & Newtec S2 Extensions Normal Frames 64800 bits
CLEAN CHANNEL TECHNOLOGY

• Roll-off : 5% -10% -15% -20% - 25% - 35%
• Optimum carrier spacing
• Advanced filter technology
EQUALINK ® 3
• Linear and Non-Linear predistortion for all MODCODs
• Maximum rate 72 Mbaud
CARRIER INTERFERENCE REDUCTION

• DVB RF Carrier ID (DVB-CID)
– Spread Spectrum Modulator (BPSK)
– Supports User Data
– Compliant to ETSI 103 129 v1.1.1 (2013-05)
• Carrier ID NIT Table

26.6 Modulation Interfaces

L-BAND (CONFIGURATION OPTION)
Connector SMA(F), 50 Ohm
Frequency 950 - 2150 MHz (10 Hz steps)
Level -35/+7 dBm (+/- 2 dB)
Return loss > 14 dB
Switchable 10 MHz Reference
Spurious performance
Better than - 65 dBc/4kHz @ +5 dBm output level and > 256 kbaud
Non-signal related: < - 80 dBc @ +5 dBm output
IF-BAND (CONFIGURATION OPTION)
Connector BNC(F) - 75 Ohm

(intermateable with 50 ohm)
Frequency 50 - 180 MHz (10 Hz steps)
Level -35/+10 dBm (± 2 dB)
Return loss 50 Ohm : > 14 dB

75 Ohm : > 20 dB
Spurious performance
Better than - 65 dBc/4kHz @ +5 dBm output level and > 256 kbaud
Non-signal related:< - 80 dBc @ +5 dBm output
L-BAND MONITORING
Connector SMA(F), 50 ohms
Frequency Same as L-Band output frequency or

1050 MHz in case of IF output option
only
Level -45 dBm
Return loss > 10 dB

10 MHZ REFERENCE INPUT
Connector BNC (F), 50 Ohm
Input level -3 dBm up to + 7 dBm
Frequencies 1, 2, 5, 10, 20 MHz
10 MHZ REFERENCE OUTPUT (OPTIONAL)
Connector BNC(F), 50 Ohm
Input level +3 dBm (+/- 2dB)

26.7 Demodulation Interfaces

DUAL L-BAND INPUT (QTY: 0-3)
Connector 2 x F-type (F), 75 Ohm
Return loss > 7 dB (75 Ohm – F(F))
Maximum total input power -10 dBm
Maximum input signal power (-30 +10log(f))dBm where f=baud

rate in Mbaud
Minimum input signal power (-80+Es/No(thr)+10log(f))dBm where

f=baud rate in Mbaud and
Es/No(thr)= Es/No value in dB for
QEF reception
Frequency 950 - 2150 MHz
Adjacent signal < (Co+7) dBm/Hz with Co = signal level density
LNB POWER AND CONTROL (ON 1 L-BAND INPUT/DEMOD)

• Max. current 350 mA
• Voltage
11,5 -14 V (Vertical polarization)
16 -19 V (Horizontal polarization) & additional
22 kHz +/- 4KHz (band selection according to universal LNB for Astra satellites & DiSEqC
command transmission)
26.8 Internal 10 MHz Reference Frequency

STANDARD STABILITY
Stability +/- 2000 ppb over 0 to 70° C
Ageing +/- 1000 ppb/year
VERY HIGH STABILITY (optional)
Stability +/- 2 ppb over 0 to 65°C
Ageing +/- 500 ppb/10 year

26.9 Generic
MONITOR AND CONTROL INTERFACES
• Web server GUI (HTTP) via web browser
• M&C connectivity via separate Ethernet links
• Diagnostics report, alarm log (HTTP)
• SNMP v2c
ALARM INTERFACE
• Electrical dual contact closure alarm contacts
• Connector 9-pin sub-D (F)
• Logical interface and general device alarm
26.10 Physical
• Height 1RU, width: 19”, depth 51 cm, 5.8 kg
• Power supply:
90-130 & 180-260 Vac,
260 VA, 47-63 Hz
• Temperature:
Operational: 0°C to +50°C / +32°F to +122°F
Storage: -40° to +70°C / -40°F to +158°F
• Humidity: 5% to 85% non-condensing
• CE label and UL

26.11 Demodulation Performances
26.11.1 DVB-S2 Performance
26.11.1.1 DVB-S2 Performance (FER<1E-5) Normal Frames/Pilots Off
MODCOD Thresh Es/No Thresh Es/No Thresh Es/No

10 Mbaud dB 36 Mbaud dB 72 Mbaud dB
QPSK 1/4 -2.79 -2.85 -2.86
QPSK 1/3 -1.51 -1.55 -1.56
QPSK 2/5 -0.47 -0.50 -0.50
QPSK 1/2 0.93 0.90 0.91
QPSK 3/5 2.19 2.15 2.15
QPSK 2/3 3.04 3.00 3.00
QPSK 3/4 4.02 3.98 3.98
QPSK 4/5 4.65 4.62 4.62
QPSK 5/6 5.17 5.13 5.13
QPSK 8/9 6.22 6.18 6.17
QPSK 9/10 6.43 6.40 6.39
8PSK 3/5 5.54 5.52 5.54
8PSK 2/3 6.54 6.48 6.49
8PSK 3/4 7.86 7.81 7.82
8PSK 5/6 9.29 9.27 9.28
8PSK 8/9 10.69 10.67 10.68
8PSK9/10 10.97 10.94 10.95
16APSK 2/3 9.00 8.97 8.99
16APSK 3/4 10.21 10.19 10.22
16APSK 4/5 11.03 11.02 11.02
16APSK 5/6 11.61 11.59 11.60
16APSK 8/9 12.93 12.92 12.92
16APSK 9/10 13.17 13.14 13.17
32APSK 3/4 12.75 12.74 12.78
32APSK 4/5 13.69 13.70 13.68
32APSK 5/6 14.26 14.30 14.27
32APSK 8/9 15.71 15.71 15.73
32APSK 9/10 16.02 16.00 16.17

26.11.1.2 DVB-S2 Performance (FER<1E-5) Normal Frames/Pilots On
Thresh Es/No Thresh Es/No Thresh Es/No

MODCOD 10 Mbaud 36 Mbaud 72 Mbaud
dB dB dB
QPSK 1/4 -2.74 -2.80 -2.80
QPSK 1/3 -1.41 -1.46 -1.46
QPSK 2/5 -0.38 -0.42 -0.42
QPSK 1/2 1.01 0.98 0.98
QPSK 3/5 2..24 2.21 2.21
QPSK 2/3 3.09 3.05 3.06
QPSK 3/4 4.05 4.02 4.02
QPSK 4/5 4.68 4.65 4.65
QPSK 5/6 5.19 5.15 5.16
QPSK 8/9 6.24 6.21 6.20
QPSK 9/10 6.45 6.41 6.41
8PSK 3/5 5.53 5.51 5.52
8PSK 2/3 6.57 6.54 6.56
8PSK 3/4 7.90 7.88 7.88
8PSK 5/6 9.32 9.31 9.32
8PSK 8/9 10.71 10.68 10.68
8PSK9/10 10.98 10.95 10.95
16APSK 2/3 8.98 8.96 8.98
16APSK 3/4 10.25 10.25 10.26
16APSK 4/5 11.06 11.05 11.05
16APSK 5/6 11.64 11.62 11.62
16APSK 8/9 12.94 12.95 12.95
16APSK 9/10 13.19 13.17 13.17
32APSK 3/4 12.79 12.82 12.85
32APSK 4/5 13.73 13.69 13.73
32APSK 5/6 14.29 14.27 14.35
32APSK 8/9 15.73 15.70 15.72
32APSK 9/10 16.03 15.99 16.04

26.11.1.3 DVB-S2 Performance (FER<1E-5) Short Frames/Pilots Off

MODCOD
10 Mbaud 36 Mbaud 72 Mbaud
dB dB dB
QPSK 1/4 -3.16 -3.26 -3.19

QPSK 1/3 -1.27 -1.31 -1.29
QPSK 2/5 -0.28 -0.33 -0.31
QPSK 1/2 0.50 0.47 0.47
QPSK 3/5 2.34 2.31 2.32
QPSK 2/3 3.20 3.17 3.19
QPSK 3/4 4.15 4.13 4.14
QPSK 4/5 4.77 4.74 4.74
QPSK 5/6 5.31 5.29 5.29
QPSK 8/9 6.38 6.37 6.36
8PSK 3/5 5.75 5.75 5.80
8PSK 2/3 6.74 6.68 6.73
8PSK 3/4 8.05 8.03 8.05
8PSK 5/6 9.55 9.54 9.55
8PSK 8/9 10.88 10.88 10.88
16APSK 2/3 9.19 9.18 9.25
16APSK 3/4 10.40 10.40 10.42
16APSK 4/5 11.16 11.15 11.18
16APSK 5/6 11.84 11.86 11.88
16APSK 8/9 13.11 13.16 13.16
32APSK 3/4 13.09 13.16 13.19
32APSK 4/5 13.93 14.04 14.03
32APSK 5/6 14.58 14.69 14.70
32APSK 8/9 15.91 16.12 16.12

26.11.1.4 DVB-S2 Performance (FER<1E-5) Short Frames/Pilots On

MODCOD
dB dB dB
QPSK 1/4 -3.36 -3.42 -3.39

QPSK 1/3 -1.19 -1.24 -1.21
QPSK 2/5 -0.24 -0.26 -0.24
QPSK 1/2 0.56 0.52 0.52
QPSK 3/5 2.38 2.34 2.36
QPSK 2/3 3.24 3.20 3.21
QPSK 3/4 4.17 4.15 4.15
QPSK 4/5 4.77 4.75 4.75
QPSK 5/6 5.33 5.30 5.30
QPSK 8/9 6.40 6.37 6.37
8PSK 3/5 5.71 5.71 5.76
8PSK 2/3 6.77 6.74 6.77
8PSK 3/4 8.09 8.07 8.08
8PSK 5/6 9.57 9.57 9.57
8PSK 8/9 10.89 10.89 10.91
16APSK 2/3 9.16 9.15 9.21
16APSK 3/4 10.43 10.43 10.44
16APSK 4/5 11.17 11.20 11.20
16APSK 5/6 11.85 11.88 11.89
16APSK 8/9 13.13 13.18 13.18
32APSK 3/4 13.11 13.17 13.19
32APSK 4/5 13.94 14.04 14.05
32APSK 5/6 14.58 14.77 14.77
32APSK 8/9 15.93 16.15 16.14

26.11.2 DVB-S2X Performance
26.11.2.1 DVB-S2X Performance (FER<1E-5) Normal Frames/Pilots Off

MODCOD
dB dB dB
QPSK 1/4 -2.79 -2.85 -2.86

QPSK 1/3 -1.51 -1.55 -1.56
QPSK 2/5 -0.47 -0.50 -0.50
QPSK 1/2 0.93 0.90 0.91
QPSK 3/5 2.19 2.15 2.15
QPSK 2/3 3.04 3.00 3.00
QPSK 3/4 4.02 3.98 3.98
QPSK 4/5 4.65 4.62 4.62
QPSK 5/6 5.17 5.13 5.13
QPSK 8/9 6.22 6.18 6.17
QPSK 9/10 6.43 6.40 6.39
8PSK 3/5 5.54 5.52 5.54
8PSK 2/3 6.54 6.48 6.49
8PSK 3/4 7.86 7.81 7.82
8PSK 5/6 9.29 9.27 9.28
8PSK 8/9 10.69 10.67 10.68
8PSK9/10 10.97 10.94 10.95
16APSK 2/3 9.00 8.97 8.99
16APSK 3/4 10.21 10.19 10.22
16APSK 4/5 11.03 11.02 11.02
16APSK 5/6 11.61 11.59 11.60
16APSK 8/9 12.93 12.92 12.92
16APSK 9/10 13.17 13.14 13.17
32APSK 3/4 12.75 12.74 12.78
32APSK 4/5 13.69 13.70 13.68
32APSK 5/6 14.26 14.30 14.27
32APSK 8/9 15.71 15.71 15.73
32APSK 9/10 16.02 16.00 16.17


MODCOD
dB dB dB
QPSK 13/45 -2.09 -2.14 -2.14

QPSK 9/20 0.13 0.08 0.08
QPSK 11/20 1.39 1.35 1.35
8PSK 23/36 6.19 6.15 6.16
8PSK 25/36 7.06 6.99 7.01
8PSK 13/18 7.50 7.45 7.46
16APSK 26/45 7.47 7.44 7.49
16APSK 3/5 7.95 7.92 7.93
16APSK 28/45 8.19 8.16 8.18
16APSK 23/36 8.39 8.34 8.37
16APSK 25/36 9.29 9.25 9.27
16APSK 13/18 9.78 9.71 9.72
16APSK 7/9 10.69 10.62 10.64
16APSK 77/90 12.02 11.96 11.98
32APSK 32/45 11.82 11.76 11.80
32APSK 11/15 12.22 12.16 12.19
32APSK 7/9 13.14 13.07 13.09
64APSK 11/15 15.04 14.99 15.06
64APSK 7/9 15.57 15.48 15.53
64APSK 4/5 16.00 15.91 15.94
64APSK 5/6 16.64 16.55 16.60
128APSK 3/4 19.13 19.09 19.34
128APSK 7/9 19.07 19.07 19.20
256APSK 32/45 18.84 18.76 18.85
256APSK 3/4 19.83 19.73 19.84


MODCOD
dB dB dB
8APSK 5/9-L 4.69 4.65 4.66

8APSK 26/45-L 5.12 5.08 5.08
16APSK 1/2-L 5.90 5.85 5.89
16APSK 8/15-L 6.54 6.50 6.52
16APSK 5/9-L 6.80 6.77 6.79
16APSK 3/5-L 7.32 7.28 7.34
16APSK 2/3-L 8.36 8.32 8.36
32APSK 2/3-L 11.21 11.11 11.14
64APSK 32/45-L 14.02 13.97 14.02
256APSK 29/45-L 17.02 16.97 17.16
256APSK 2/3-L 17.36 17.28 17.46
256APSK 31/45-L 18.31 18.21 18.30
256APSK 11/15-L 19.06 18.96 19.09

26.11.2.2 DVB-S2X Performance (FER<1E-5) Normal Frames/Pilots On

MODCOD
dB dB dB
QPSK 1/4 -2.74 -2.80 -2.80

QPSK 1/3 -1.41 -1.46 -1.46
QPSK 2/5 -0.38 -0.42 -0.42
QPSK 1/2 1.01 0.98 0.98
QPSK 3/5 2.24 2.21 2.21
QPSK 2/3 3.09 3.05 3.06
QPSK 3/4 4.05 4.02 4.02
QPSK 4/5 4.68 4.65 4.65
QPSK 5/6 5.19 5.15 5.16
QPSK 8/9 6.24 6.21 6.20
QPSK 9/10 6.45 6.41 6.41
8PSK 3/5 5.53 5.51 5.52
8PSK 2/3 6.57 6.54 6.56
8PSK 3/4 7.90 7.88 7.88
8PSK 5/6 9.32 9.31 9.32
8PSK 8/9 10.71 10.68 10.68
8PSK9/10 10.98 10.95 10.95
16APSK 2/3 8.98 8.96 8.98
16APSK 3/4 10.25 10.25 10.26
16APSK 4/5 11.06 11.05 11.05
16APSK 5/6 11.64 11.62 11.62
16APSK 8/9 12.94 12.95 12.95
16APSK 9/10 13.19 13.17 13.17
32APSK 3/4 12.79 12.82 12.85
32APSK 4/5 13.73 13.69 13.73
32APSK 5/6 14.29 14.27 14.35
32APSK 8/9 15.73 15.70 15.72
32APSK 9/10 16.03 15.99 16.04


MODCOD
dB dB dB
QPSK 13/45 -1.98 -2.03 -2.04

QPSK 9/20 0.23 0.20 0.20
QPSK 11/20 1.47 1.45 1.45
8PSK 23/36 6.21 6.18 6.19
8PSK 25/36 7.11 7.07 7.08
8PSK 13/18 7.58 7.54 7.55
16APSK 26/45 7.44 7.40 7.44
16APSK 3/5 7.89 7.85 7.87
16APSK 28/45 8.17 8.13 8.14
16APSK 23/36 8.39 8.34 8.37
16APSK 25/36 9.30 9.26 9.28
16APSK 13/18 9.81 9.76 9.77
16APSK 7/9 10.75 10.70 10.71
16APSK 77/90 12.11 12.05 12.06
32APSK 32/45 11.86 11.81 11.85
32APSK 11/15 12.27 12.22 12.25
32APSK 7/9 13.19 13.13 13.15
64APSK 11/15 14.97 14.91 14.96
64APSK 7/9 15.61 15.54 15.58
64APSK 4/5 16.07 15.97 16.00
64APSK 5/6 16.68 16.61 16.65
128APSK 3/4 17.96 17.90 17.97
128APSK 7/9 18.87 18.78 18.82
256APSK 32/45 18.95 18.84 18.92
256APSK 3/4 19.92 19.81 19.91


MODCOD
dB dB dB
8APSK 5/9-L 4.74 4.71 4.72

8APSK 26/45-L 5.16 5.13 5.14
16APSK 1/2-L 5.93 5.91 5.94
16APSK 8/15-L 6.60 6.56 6.59
16APSK 5/9-L 6.86 6.82 6.84
16APSK 3/5-L 7.38 7.34 7.39
16APSK 2/3-L 8.41 8.36 8.40
32APSK 2/3-L 11.20 11.15 11.17
64APSK 32/45-L 14.07 14.00 14.06
256APSK 29/45-L 17.08 17.00 17.20
256APSK 2/3-L 17.40 17.32 17.51
256APSK 31/45-L 18.38 18.30 18.36
256APSK 11/15-L 19.12 19.03 19.14

26.11.2.3 DVB-S2X Performance (FER<1E-5) Short Frames/Pilots Off
Normal Frames and Pilots Off

MODCOD
dB dB dB
QPSK 1/4 -3.16 -3.26 -3.19

QPSK 1/3 -1.27 -1.31 -1.29
QPSK 2/5 -0.28 -0.33 -0.31
QPSK 1/2 0.50 0.47 0.47
QPSK 3/5 2.34 2.31 2.32
QPSK 2/3 3.20 3.17 3.19
QPSK 3/4 4.15 4.13 4.14
QPSK 4/5 4.77 4.74 4.74
QPSK 5/6 5.31 5.29 5.29
QPSK 8/9 6.38 6.37 6.36
8PSK 3/5 5.75 5.75 5.80
8PSK 2/3 6.74 6.68 6.73
8PSK 3/4 8.05 8.03 8.05
8PSK 5/6 9.55 9.54 9.55
8PSK 8/9 10.88 10.88 10.88
16APSK 2/3 9.19 9.18 9.25
16APSK 3/4 10.40 10.40 10.42
16APSK 4/5 11.16 11.15 11.18
16APSK 5/6 11.84 11.86 11.88
16APSK 8/9 13.11 13.16 13.16
32APSK 3/4 13.09 13.16 13.19
32APSK 4/5 13.93 14.04 14.03
32APSK 5/6 14.58 14.69 14.70
32APSK 8/9 15.91 16.12 16.12


MODCOD
dB dB dB
QPSK 11/45 -2.53 -2.57 -2.58

QPSK 4/15 -2.21 -2.23 -2.23
QPSK 14/45 -1.57 -1.60 -1.59
QPSK 7/15 0.56 0.51 0.54
QPSK 8/15 1.43 1.39 1.40
QPSK 32/45 3.57 3.54 3.54
8PSK 7/15 3.92 3.92 4.06
8PSK 8/15 4.72 4.71 4.74
8PSK 26/45 5.50 5.46 5.49
8PSK 32/45 7.49 7.45 7.47
16APSK 7/15 6.85 6.88 6.97
16APSK 8/15 7.05 7.05 7.14
16APSK 26/45 7.64 7.61 7.67
16APSK 3/5 8.10 8.11 8.17
16APSK 32/45 9.80 9.72 9.73
32APSK 2/3 11.40 11.32 11.41
32APSK 32/45 12.11 12.06 12.10

26.11.2.4 DVB-S2X Performance (FER<1E-5) Short Frames/Pilots On

MODCOD
dB dB dB
QPSK 1/4 -3.36 -3.42 -3.39

QPSK 1/3 -1.19 -1.24 -1.21
QPSK 2/5 -0.24 -0.26 -0.24
QPSK 1/2 0.56 0.52 0.52
QPSK 3/5 2.38 2.34 2.36
QPSK 2/3 3.24 3.20 3.21
QPSK 3/4 4.17 4.15 4.15
QPSK 4/5 4.77 4.75 4.75
QPSK 5/6 5.33 5.30 5.30
QPSK 8/9 6.40 6.37 6.37
8PSK 3/5 5.71 5.71 5.76
8PSK 2/3 6.77 6.74 6.77
8PSK 3/4 8.09 8.07 8.08
8PSK 5/6 9.57 9.57 9.57
8PSK 8/9 10.89 10.89 10.91
16APSK 2/3 9.16 9.15 9.21
16APSK 3/4 10.43 10.43 10.44
16APSK 4/5 11.17 11.20 11.20
16APSK 5/6 11.85 11.88 11.89
16APSK 8/9 13.13 13.18 13.18
32APSK 3/4 13.11 13.17 13.19
32APSK 4/5 13.94 14.04 14.05
32APSK 5/6 15.58 14.77 14.77
32APSK 8/9 15.93 16.15 16.14


MODCOD
dB dB dB
QPSK 11/45 -2.50 -2.54 -2.55

QPSK 4/15 -2.13 -2.16 -2.16
QPSK 14/45 -1.47 -1.50 -1.49
QPSK 7/15 0.64 0.60 0.64
QPSK 8/15 1.51 1.48 1.48
QPSK 32/45 3.65 3.62 3.62
8PSK 7/15 3.74 3.75 3.84
8PSK 8/15 - 4.66 4.65 4.67
8PSK 26/45 5.42 5.39 5.41
8PSK 32/45 7.59 7.55 7.56
16APSK 7/15 5.94 5.94 6.14
16APSK 8/15 6.90 6.89 6.95
16APSK 26/45 7.60 7.58 7.63
16APSK 3/5 8.07 8.06 8.12
16APSK 32/45 9.81 9.76 9.78
32APSK 2/3 11.38 11.36 11.44
32APSK 32/45 12.18 12.11 12.15

Appendix - Classification Expressions MCX7000 Multi-Carrier Satellite Gateway
27 Appendix - Classification Expressions

Filter all incoming packets based on expressions that match any field of an incoming packet
• * IP addresses, TOS byte, protocol, etc.
Expressions can be ANDed (&&), ORed (||), negated (!), brackets can be used to group different
expressions.
expression=expression and expression expression=(expression) expression=protocol

expression=expression && expression
expression=field value expression=protocol field
expression=expression or expression
value expression=always expression=never
expression=expression || expression
expression=not expression
expression=!expression

ARP
arp operation <operation>
arp src ether <mac>
arp dst ether <mac>
arp src host <ip4address>
arp src net <ip4address>-<ip4address>
arp src net <ip4address> mask <ip4netmask>
arp src net <ip4address>/<ip4bits>
arp dst host <ip4address>
arp dst net <ip4address>-<ip4address>
arp dst net <ip4address> mask <ip4netmask>
arp dst net <ip4address>/<ip4bits>
IPv4
ip4 tos <tos>
ip4 dscp <dscp>
ip4 protocol <protocol>
ip4 src host <ip4address>
ip4 src net <ip4address>-<ip4address>
ip4 src net <ip4address> mask <ip4netmask>
ip4 src net <ip4address>/<ip4bits>
ip4 dst host <ip4address>
ip4 dst net <ip4address>-<ip4address>
ip4 dst net <ip4address> mask <ip4netmask>
ip4 dst net <ip4address>/<ip4bits>
ip4 unicast
ip4 multicast
ip4 broadcast
ip4 ah
ip4 esp
IGMP UDP
igmp type <igmptype> udp src port <port>

igmp host <ip4address> udp src port <port>-<port>
igmp net <ip4address>-<ip4address> udp dst port <port>
igmp net <ip4address> mask <ip4netmask> udp dst port <port>-<port>
igmp net <ip4address>/<ip4bits> udp rtp-detection <rtpdetect>
TCP
tcp src port <port>
tcp src port <port>-<port>
tcp dst port <port>
tcp dst port <port>-<port>
ICMP4
icmp4 type <icmp4type>
icmp4 code <icmp4code>
ICMP6
icmp6 type <icmp6type>
icmp6 code <icmp6code>
icmp6-neighbor-solicitation target
<ip6address>
icmp6-neighbor-advertisement target
<ip6address>

27.1 Example Expressions
Rule Expression to be used on the NOP1760
A regular route towards dst net 192.168.2.0/24

network 192.168.2.0/24.
All Ping messages icmp type echo-request
All encrypted Ipsec (ip4 esp) and dst host 192.1.2.4

packets towards
192.168.2.4
All IPv4 multicast towards (ip4 multicast) and (udp dst port 6001)
udp destination port 6001
Forward Ethernet frames (ethernet vlan 300) and ( ethernet vlan 301)
based on vlan tags 300
and 301.

Appendix - DSNG Profiles Preconfigured Settings MCX7000 Multi-Carrier Satellite Gateway
28 Appendix - DSNG Profiles Preconfigured

Settings
28.1 DSNG Profiles Preconfigured Settings

The following tables list the predefined parameters for the ISOG-News profiles.
The parameters listed in the following tables are copied from the WBU and ISOG
document.
WBU-ISOG Operational Profiles to Streamline DSNG Operations version January
2014.
28.2 ISOG-News3 Profile

Profile Name News3 News3 News3 News3
Level 1 Legacy 2 Midrange 3 Efficient 3 Efficient
RF Coding DVB-S DVB-S2 DVB-S2 DVB-S2X
Order of QPSK QPSK 8PSK 16APSK

Modulation
FEC 3/4 3/4 5/6 2/3
Symbol Rate 2,220 2,500 2,500 2,857

(Mbaud)
Pilots Symbol NA Yes Yes Yes
Frame Length NA Normal Normal Normal
Resulting 3,069 3,630 6,056 7,387

Transport Rate
(Mbps)
Occupied 3 3 3 3
Bandwidth
(MHz)
Roll-off Factor 1,35 1,2 1,2 1,05
Receiver 6,9 4,03 9,35 8,88

Threshold
(Es/No)
C/N allocated 5,60 3,24 8,56 8,68

bandwidth



Modulation
FEC 3/4 3/4 5/6 2/3
Symbol Rate 2,963 3,333 3,333 3,810

(Mbaud)
Resulting 4,095 4,840 8,073 8.917

Transport Rate
(Mbps)
Occupied 4 4 4 4
Bandwidth
(MHz)
Roll-off Factor 1,35 1,2 1,2 1,05
Receiver 6,9 4,03 9,35 8,88

Threshold
(Es/No)
C/N allocated 5,60 3,24 8,56 8,68

bandwidth



Modulation
FEC 3/4 3/4 5/6 2/3
Symbol Rate 4,444 5,000 5,000 5,714

(Mbaud)
Resulting 6,143 7,260 12,111 14,774

Transport Rate
(Mbps)
Occupied 6 6 6 6
Bandwidth
(MHz)
Roll-off Factor 1,35 1,2 1,2 1,05
Receiver 6,9 4,03 9,35 8,88

Threshold
(Es/No)
C/N allocated 5,60 3,24 8,56 8,68

bandwidth


Profile News9 News9 News9 News9 News9
Name
Level 1 Legacy 2 Mid-range 3 Efficient 4 High 4 High

Efficiency Efficiency
RF Coding DVBS DVBS2 DVBS2 DVB-S2 DVB-S2X
Order of QPSK QPSK 8PSK 16APSK 16APSK-L

Modulation
FEC 3/4 3/4 5/6 3/4 13/18
Symbol Rate 6,667 7500,000 7500,000 7500,000 8,571

(Mbaud)
Pilots Symbol NA Yes Yes Yes Yes
Frame NA Normal Normal Normal Normal

Length
Resulting 9,216 10,891,571 18,167,072 24,163970 23,967

Transport
Rate (Mbps)
Occupied 9 9 9 9 9
Bandwidth
(MHz)
Roll-off 1,35 1,2 1,2 1,2 1,05

Factor
Receiver 6,9 4,03 9,35 10,21 9,70

Threshold
(Es/No)
C/N allocated 5,60 3,24 8,56 9,42 9,50

bandwidth

Appendix - IP Handling MCX7000 Multi-Carrier Satellite Gateway
29 Appendix - IP Handling
29.1 IP Packet Reception on an Interface

The following figure shows the two possible IP processing modes:
TS over IP In
1. An IP packet arrives on data1 or one of the VLAN interfaces.
2. The destination IP address matches a local MDM6100 address.
3. Is the UDP port correct in one of the available TS over IP Input interfaces?
– If yes the IP header is stripped off and the available transport stream can be forwarded to the
following block in the MDM6100.
– If no the IP packet is dropped.
IP Data In for MPE

1. An IP packet arrives on data1 or one of the VLAN interfaces.
2. The destination IP address does not match a local MDM6100 address.
3. Are there Valid Classification rules present for the incoming IP packets?
– If yes then the IP packets are shaped and MPE encapsulated.
– If no the IP packets are dropped.

Appendix - Back Panel Combinations MCX7000 Multi-Carrier Satellite Gateway
30 Appendix - Back Panel Combinations

This appendix gives an overview of the possible back panel combinations for the MDM6100.
The back panel is split up into four modules,as shown here:
Module 1
This module holds the power supply.
Module 2
This module holds demodulator and modulator connectors. Depending on the ordered configuration
the module holds demodulator connectors only, a combination of demodulator and modulator
connectors or modulator connectors only.
Note: An empty module is also possible when a single modulator configuration is

ordered.
Module 3
This module can hold modulator, ASI and demodulator connectors.
Depending on the ordered configuration the module holds:
• Modulator connectors only
• A combination of modulator and ASI connectors
• A combination of modulator and demodulator connectors
• Or demodulator connectors
Module 2 and 3
As mentioned, module 2 and 3 can have "overlap" between modulator and demodulator connectors.
When an overlap of connectors is needed the following rule is applied:
Demodulator connectors are always added from left to right as displayed in the following figure.
The numbering is also done from left to right.

Modulator connectors are always added from right to left as displayed in the following figure.
The modulator connectors are indicated with a number in a circle as indicated in the following
drawing.
Module 3 Module 3
Modulator Only Modulator and ASI connectors.
Module 4
This module holds the default MGMT and Data Ethernet ports, the craft interface and the alarm
interface. Furthermore it holds the Reference clock input and the optional 10 MHz reference output
interface.

30.1 Example Combinations
30.1.1 Single TSoIP Modulator
Ordering Nr. Ordering Nr. Ordering Nr. Ordering Nr.

Module 1 Module 2 Module 3 Module 4
PS-01 ------ OU-00 Default

+
or
RO-01
OU-01
or
VI-01
OU-02
30.1.2 Single ASI Modulator

PS-01 ------ OU-00 Default

+
or
RO-01
OU-01
or
VI-01
OU-02
and
HS-05

30.1.3 Single TSoIP Modem

PS-01 HS-02 OU-00 Default

+
or
RO-01
OU-01
or
VI-01
OU-02
30.1.4 Single ASI Modem


+
or
RO-01
OU-01
or
VI-01
OU-02
and
HS-05

30.1.5 Modulator and Dual ASI Demodulator


+
and or
RO-01
HS-04< OU-01
or
VI-01
OU-02
and
HS-05
30.1.6 Modem + Dual TSoIP Demodulator


+
and or
RO-01
HS-03 OU-01
or
VI-01
OU-02

30.1.7 Multi Demodulator

PS-01 HS-02 HS-07 Default

+
and
RO-01
HS-03
VI-01

Appendix - Acronyms MCX7000 Multi-Carrier Satellite Gateway
31 Appendix - Acronyms
Acronym Definition
ACM Adaptive Coding Modulation

APSK Amplitude and Phase Shift Keying
ASI Asynchronous Serial Interface
BCH Chaudhuri and Hocquengham
BER Bit Error Rate/Ratio
BISS Basic Interoperable Scrambling System
BNC Bayonet (Neill Concelman) Connector (for coaxial cable)
BUC Block Up Converter
CBR Constant Bit Rate
CCITT Comite Consultatif International Télégraphique et Téléphonique
(known today as the ITU-T)
CCM Constant Coding and Modulation
CD Compact Disc (digital audio recordings)
CD-ROM Compact Disc Read Only Memory (in computer systems)
CEC Canadian Electrical Code
CIR Committed Information Rate
CLI Command Line Interface
CPU Central Processing Unit
CTRL Control
DSNG Digital Satellite News Gathering
DTH Direct to Home
DVB-S Digital Video Broadcasting-Satellite
EMC ElectroMagnetic Compatibility
ETH Ethernet
ETSI European Telecommunication Standards Institute
FCC Federal Communications Commission
FEC Forward Error Correction (in data transmission systems)
FTP File Transfer Protocol (computer networks & systems)
GND Ground (connection in equipment or circuits)
GPS Global Positioning System
GUI Graphical User Interface
HTTP Hypertext Transfer Protocol
ID Identifier
IEC International Electrotechnical Commission

Acronym Definition
IF Intermediate Frequency
IP Internet Protocol
IRD Integrated Receiver Decoder
LCD Liquid Crystal Display
LDPC Low-density Parity-check code
LED Light Emitting Diode
LNB Low Noise Block Converter
MAC Medium Access Control
MHP Multimedia Home Platform
MIB Management Information Base
MODCOD Modulation and Coding
MPE Multiprotocol Encapsulation
MPEG Motion Picture Experts Group
MPTS Multiple Program Transport Stream
MTU Maximum Transmission Unit
MUX Multiplex communications transmissions
NEC National Electrical Code
NIT Network Information Table
NMS Network Management System
NTP Network Time Protocol
PAT (MPEG2) Programme Association Table
PC Personal Computer
PCR Program Clock Reference
PER Packet Error Rate
PID Packet Identification
PIR Peak Information Rate
PMT (MPEG 2) Program Map Table
PRBS Pseudo Random Binary Sequence
QPSK Quadrature Phase Shift Keying
REACH Evaluation and Authorization of Chemicals
RF Radio Frequency
RFI Radio Frequency Interference
RH Restriction of Hazardous
RS Reed Solomon
RTP Real-time Transmission Protocol
SDT Service Description Table

Acronym Definition
SFN Single Frequency Network

SMA SubMiniature version A
SMPTE Society of Motion Picture & Television Engineers
SNMP Simple Network Management Protocol
SPTS Single Program Transport Stream
SSH Secure Shell
SVHC Substances of Very High Concern
TS Transport Stream
UDP User Datagram Protocol
UL Underwriters Laboratory
UTC Universal Coordinated Time (replaced GMT)
VA Volt-Ampere
VBR Variable Bit Rate
XML Extensible Markup Language

Get More Out of Your Equipment
The understanding of your application in combination with our product leads to reliable
and cost-efficient solutions.
Visit: www.newtec.eu/applications for our full application range.
Feedback on this document?

Please provide any comment, error found or suggestion for
improvement, you may have about this document to
documentation@newtec.eu
Twitter.com/Newtec_Satcom
Linkedin.com/company/newtec
Youtube.com/NewtecSatcom
Slideshare.net/newtec_satcom
Visit our website: www.newtec.eu

Demodulator-UMN - MCX7000 Multi-Carrier Satellite Gateway - R1.0 - v1.0 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Demodulator-UMN - MCX7000 Multi-Carrier Satellite Gateway - R1.0 - v1.0 PDF

Uploaded by

Copyright:

Available Formats

MCX7000

2 EU Compliancy Statements ............................................................................... 2

3 Care Packs .......................................................................................................... 6

4 Safety Regulations ............................................................................................. 7

7 About this Manual ............................................................................................ 15

9 Back Panel Description .................................................................................... 21

10 How to Use the Front Panel ........................................................................... 27

Newtec Proprietary V1.0

10.4 Tree Menu Pane ...................................................................................................................................... 30

11 How to Use the Command Line Interface (CLI) ........................................... 38

Newtec Proprietary V1.0

13 How to Use the Graphical User Interface ..................................................... 52

14 Device Security ............................................................................................... 73

15 General Configuration Principles ................................................................. 76

16 Configure the Physical Interfaces ................................................................. 82

Newtec Proprietary V1.0

16.1.4.1 License Type ............................................................................................................................... 89

17 Quick Configuration Templates .................................................................. 133

Newtec Proprietary V1.0

17.12 Template G. Single Stream Multi-Demodulator ................................................................................... 145

18 Configure the Functional Blocks ................................................................ 147

Newtec Proprietary V1.0

18.3.1.3.3 MODCOD Statistics ............................................................................................................ 198

Newtec Proprietary V1.0

18.5 Block Diagram Multistream Demodulator .............................................................................................. 247

19 Configure the Input Processing Blocks ..................................................... 271

20 Configure the Output Processing Blocks .................................................. 279

Newtec Proprietary V1.0

21 Configure the Remote In-band Management Feature ............................... 319

Newtec Proprietary V1.0

22 Configure the Probes ................................................................................... 323

23 Tasks .............................................................................................................. 333

Newtec Proprietary V1.0

23.6.1 Open the Reference Manual ............................................................................................................ 359

24 Alarm Handling ............................................................................................. 361

25 Appendix - Configuring the Output Rate Mode ......................................... 366

26 Appendix - Specifications ............................................................................ 371

Newtec Proprietary V1.0

27 Appendix - Classification Expressions ...................................................... 393

28 Appendix - DSNG Profiles Preconfigured Settings ................................... 396

29 Appendix - IP Handling ................................................................................ 400

30 Appendix - Back Panel Combinations ........................................................ 401

31 Appendix - Acronyms ................................................................................... 407

Newtec Proprietary V1.0

Newtec Proprietary V1.0

Confidentiality: Unrestricted 1/409

2.1 Radio and Telecommunications Terminal Equipment

Declare that the following product:

Done at St-Niklaas, on October 8, 2015.

Serge Van Herck,

Newtec Proprietary V1.0

Confidentiality: Unrestricted 2/409

2.2 EMC Information

2.3 Restriction of Hazardous Substances Directive (RoHS)

Serge Van Herck,

Newtec Proprietary V1.0

Confidentiality: Unrestricted 3/409

2.4 Registration, Evaluation and Authorization of Chemicals

Serge Van Herck,

Newtec Proprietary V1.0

Confidentiality: Unrestricted 4/409

2.5 WEEE – Waste Electrical and Electronic Equipment

Serge Van Herck,