Documente Academic
Documente Profesional
Documente Cultură
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
5 Options .............................................................................................................. 10
6 Feedback ........................................................................................................... 14
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
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
12 SNMP ............................................................................................................... 51
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
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
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
Table of Contents MCX7000 Multi-Carrier Satellite Gateway
Confidentiality: Unrestricted
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
2 EU Compliancy Statements
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.
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium.
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49
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.
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49
Newtec Cy N.V.
Laarstraat 5
B-9100 Sint-Niklaas
Belgium.
Tel: +32 3 780 65 00
Fax: +32 3 780 65 49
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.
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:
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.
• 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.
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.
5 Options
Newtec MCX7000 Ordering nr.
Select 1 option
Select 1 option
Select 1 option
Select 1 option
Select 1 option
Select 1 option
Additional Options
Category
Services Category
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.
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
A hint message indicates information for the proper operation of your equipment,
including helpful hints, shortcuts or important reminders.
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.
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.
Power Supply
• PS-01
Modulator Demodulator
• HS-01 • HS-02
• HS-04
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.
Use the following pin connections to create a crossover cable between the MCX7000
Multi-Carrier Satellite Gateway and the managing device.
1 Not connected
4 Not connected
6 Not connected
7 Not connected
8 Not connected
9 Not connected
The following figure shows how to connect the alarm cables in a 1+1 redundancy system.
The following table describes the buttons displayed in the previous figure.
Name/Symbol Description
Arrow UP Navigate to the upper item.
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:
» 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).
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.
Scroll bar
Indicates that more than one line exists under this selection.
» Navigate through this pane by using the up/down arrow of the navigation buttons.
TEST Green Indicates that the internal PRBS generator is activated on the
device.
10.6.1 Modulator
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Transmit
Proceed as follows:
» Select Configuration
» Navigate to Transmit
» Click OK
» Select On/Off
» Click OK
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Output Frequency
Proceed as follows:
» Select Configuration
» Click OK
» Click OK
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Output Level
Proceed as follows:
» Select Configuration
» Click OK
» Use the Soft Buttons, to step up or down until the correct output level is reached
» Click OK
Navigate to:
MCX7000 >> Modulator >> Configuration >> Configuration Table >> Symbol Rate
Proceed as follows:
» Select Configuration
» Click OK
» Click OK
10.6.2 Management
Navigate to:
Proceed as follows:
» Select IP Address
» Click OK
» Click OK
Navigate to:
Proceed as follows:
» Select Gateway
» Select IP Address
» Click OK
» Click OK
Proceed as follows:
» Navigate to Frontpanel
» Click OK
» Click OK
or
» Select the Number (Soft button) corresponding to the displayed access levels
10.6.3 Configurations
Navigate to:
Proceed as follows:
» Click OK
» Click OK
(The front panel displays: processing.)
Navigate to:
Proceed as follows:
» 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.
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:
» 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 .
» Password: expertexpert
For Example:
[MCX7000] # demodulator
[MCX7000] demodulator#
or
» ..
For Example:
For Example:
11.8.1 Show
The show command is used to display the different commands, branches or leaves that exist in a
branch.
For Example:
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 )
[MCX7000] modulator# c?
configtable/
Key Combinations
CTRL+C Flush the current line ignoring the contents and start a new
line.
CTRL+K Delete from the current cursor position to the end of line.
CTRL+U Delete from the current cursor position to the beginning of the
line.
When entering a new value (without specifying a scale) the default unit scaling is
applied.
For example:
Get
» Type the location and the parameter name to readout the requested parameter value.
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!
Make sure that the resolution of the display is wide enough. When this is not the case
the column indication becomes unclear.
For example:
MCX7000 Mgmt interface link# showtable
For example:
MCX7000 datainterface link# showtable
12 SNMP
SNMPv2c is used in the device. The MIBs as supported by the device can be
downloaded from the GUI Device Tasks Pane.
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.
For more information on the use of the SNMP interface refer to the System
Integration Guide.
» Click Documentation
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 .....
» 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).
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.
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
» Click Switch User to change the user profile. (The Login window is displayed.)
The default User Name and password for the operator profile is as follows:
– User Name: operator
– Password: operatoroperator
The default User Name and password for the expert profile is as follows:
– User Name: expert
– Password: expertexpert
» Enter the Current Password and then the New Password. Also confirm the new password.
The following table describes the sections numbered in the previous figure.
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).
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
• Toolbox • Documentation
– 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.
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.
Click on the corresponding functional block to open the detailed page, making it
possible to monitor, and/or reconfigure the parameters.
Input
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.
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.
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
• 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.
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:
B Displays the sub branches or the details on the parameters (leafs) that exist under a
selected branch.
Pane Description
» 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
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
ASI Green The interface is enabled and activity is monitored during the last
second.
Red One of the active demodulators cannot lock to the incoming carrier.
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.
» 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.
Edit
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 .
Table
Functional group
Enable/Disable
button
Enabled
(indication)
Disabled
(indication)
Reset button
Open Detailed
View
Click this icon to open the detailed view, zooming in on the parameters
of the specific block.
Delete
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)
The following figure shows an example of the behavior of the GUI when you try to enter an invalid
value.
14 Device Security
» Click Switch User to change the user profile. (The Login window is displayed.)
The default User Name and password for the operator profile is as follows:
– User Name: operator
– Password: operatoroperator
The default User Name and password for the expert profile is as follows:
– User Name: expert
– Password: expertexpert
Login as expert user and navigate to the following locations to enable or disable these settings.
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).
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.
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.
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.
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.
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.
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.
» 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
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
Location
Configure
Enter the Geo Coordinates to indicate the current position of the modulator.
Location
Configure
Parameter Description
Location
Configure or Check
Parameter Description
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.
Hardware Revision The hardware revision of the MCX7000. Indicating the hardware
configuration of the device.
Software Version This indicates the installed software version installed on the
MCX7000.
This is useful for upgrades or fault debugging when necessary.
License Remaining Time Displays the remaining time of the temporary license.
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!
Location
Location
» Log in as expert.
The following sections explain the different blocks displayed in the previous figure.
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
Parameter Description
MAC Address Indicates the MAC address for the Ethernet management
interface.
» Click Update
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.
Preferred Interface Select either Interface A or Interface B to be the interface with most
priority.
» Click Update.
Location
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).
Parameter Description
» Click Update.
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.
Parameter Description
Gateway Enter the IP address of the outgoing gateway. Make sure that this
gateway is connected with the subnet to be reached.
» Click Update.
The following sections explain the different blocks displayed in the previous figure.
Configure
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
Location
Configure
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
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.
Parameter Description
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
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
Location
Configure
Parameter Description
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.
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
Parameter Description
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
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.
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 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
Parameter Description
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.
» Click Update.
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.
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.
Parameter Description
Gateway Enter the IP address of the outgoing gateway. Make sure that this
gateway is connected with the subnet to be reached.
» Click Update.
Location
Configure
» Click Update.
Location
Configure
» Click Update.
Location
Configure
» Log in as expert
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.
» Click Update.
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.
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
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
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.
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.
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.
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.
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.
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).
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.
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.
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).
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”
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.
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.
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.
• 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.
Input Interfaces
Name Description
Connections
Name Description
Output Interfaces
Name Description
Parameter Description
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.
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.
The monitoring table indicates the input rate and the operational state.
500 kbps > Bitrate >= 250 kbps Maximum 3 TS packets/UDP frame.
250 kbps > Bitrate >= 100 kbps Maximum 2 TS packet/UDP frame.
Configuration
Parameter Description
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
Failed: A problem exists on the Check the alarm status table and
TSoIP input interface. also the corresponding monitoring
parameters to troubleshoot the
failure.
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.
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.
Red: The de-jitter buffer runs out of • Check input rate setting and
packets. increase buffer delay, if needed.
Configure
» Click Add
Parameter Description
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
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.
For example
• Connect the TS Redundancy block with the Modulator Output.
Parameter Description
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.
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:
Option 2:
» Click on the icon in front of the Name to display the stream overview.
Result
The following warning is displayed: Are you sure you want to delete this entry?
18.2.5 Modulator
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.
Parameter Description
Mode Select the modulation mode DVB-S, DVB-S2 or DVB-S2X.
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:
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
Parameter Description
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
ACM Mode Select between ACM and CCM. (Adaptive Code Modulation and
Constant Code Modulation.)
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.
Depending on the chosen modulation mode the DVB-S or DVB-S2, DVB-S2X a different
configuration table is displayed.
Parameter Description
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.
Parameter Description
• 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.
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.
The transmission control parameters allow you to alter the default behavior of the transmitter.
Parameter Description
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
The following picture shows the parameters impacted by the parameter Allow Changes While TX
On.
Disabled Enabled
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 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.
Location
Navigate to the following location to configure the correct DSNG profiles.
Level 4 Extended
RF Coding DVB-S2X
FEC 13/18
Occupied Bandwidth 9
(MHz)
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:
• The Global Unique ID is a device unique identifier that is based on the MAC address of the
modulator.
To enter the geo coordinates and the operator identification parameters (telephone number) open
the device management functional block.
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.
» 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.
Red: The input data buffer to the • Check the input bit rate and the
modulator is empty. configured bit rate in the
modulator.
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.
Input Interfaces
Name Description
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
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.
Parameter Description
Enable By setting the Enable parameter either "off" or "on" you activate or de-activate
the demodulator.
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.
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.
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).
Parameter Description
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.
• Frequency 1 • Frequency 1
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.
Location
Setting Description
Enable Use this to arm the switch between the main input frequency
and the backup carrier input frequency.
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.
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:
Parameter Description
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.
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.
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 >.
Parameter Description
Dummy PL Displays the amount of dummy physical layer frames that are transmitted
Frame Counter over the satellite link.
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.
Parameter Description
10 Hz -27 -32.9
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 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.
Parameter Description
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.
Parameter Description
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
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 .
Parameter Description
» Click on the functional block TS over IP output and then click Show All.
Parameter Description
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.
• 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.
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.
Parameter Description
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.
» Delete a TS over IP Output interface by clicking on the "X" icon in front of this output interface.
The following warning is displayed: Are you sure you want to delete this entry?
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.
Parameter Description
Name Enter a logical name.
(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
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:
Option 2:
» Click on the icon in front of the Name to display the stream overview.
Result:
TS Redundancy
This block 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.
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.
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.
Parameter Description
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.
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.
The monitoring table indicates the input rate and the operational state.
500 kbps > Bitrate >= 250 kbps Maximum 3 TS packets/UDP frame.
250 kbps > Bitrate >= 100 kbps Maximum 2 TS packet/UDP frame.
Configuration
Parameter Description
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
Failed: A problem exists on the Check the alarm status table and
TSoIP input interface. also the corresponding monitoring
parameters to troubleshoot the
failure.
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.
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.
Red: The de-jitter buffer runs out of • Check input rate setting and
packets. increase buffer delay, if needed.
Configure
» Click Add
Parameter Description
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
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.
» Click Add
Parameter Description
Name Enter a logical name.
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.
Once the stream is created, it is possible to configure the specific settings per stream.
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
Parameter Description
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.
Parameter Description
Parameter Description
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.
• 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.
Destination UDP Define the destination UDP port.
Port
Destination IP The destination IP Address can be unicast or multicast.
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
Once the TS over IP Output interfaces are configured it is possible to make a connection between
the available input and TS over IP Output interfaces.
Parameter Description
Output Rate Displays the output rate on this TS over IP output interface.
Parameter Description
» Delete a TS over IP Output interface by clicking on the "X" icon in front of this output interface.
The following warning is displayed: Are you sure you want to delete this entry?
18.4.8 TS Connections
This functional block allows you to configure the connections between the input interfaces and the
output interfaces.
Parameter Description
Name » Enter a logical Name.
From Type From which functional block do we take in the stream.
From Name Select the input that needs to be connected.
To Type Define on what interface you want to make the transport 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.
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.
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:
Option 2:
» Click on the icon in front of the Name to display the stream overview.
Result:
The following warning is displayed: Are you sure you want to delete this entry?
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
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
» 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.
Parameter Description
ISI Enter the ISI value you want to extract corresponding to the ISI value
that is used on the sending site.
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:
Appendix - Configuring the Output Rate Mode on page 366
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:
Option 2:
» Click on the icon in front of the name to display the configuration parameters.
Result:
» 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?
Parameter Description
TS Error Counter Displays the amount of packets in the stream containing an error.
BBF Frames Displays the total amount of baseband frames per extracted transport
Counter stream.
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.
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
Appendix - Configuring the Output Rate Mode on page 366
Parameter Description
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".
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.
Parameter Description
Parameter Description
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.
• 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.
Destination UDP Define the destination UDP port.
Port
Destination IP The destination IP Address can be unicast or multicast.
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
Once the TS over IP Output interfaces are configured it is possible to make a connection between
the available input and TS over IP Output interfaces.
Parameter Description
Output Rate Displays the output rate on this TS over IP output interface.
Parameter Description
» Delete a TS over IP Output interface by clicking on the "X" icon in front of this output interface.
The following warning is displayed: Are you sure you want to delete this entry?
Parameter Description
Name » Enter a logical Name.
From Type From which functional block do we take in the stream.
– Multistream TS Input.
From Name Select the input that needs to be connected.
To Type Define on what interface you want to make the transport 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.
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.
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:
Option 2:
» Click on the icon in front of the Name to display the stream overview.
Result:
The following warning is displayed: Are you sure you want to delete this entry?
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)
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
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
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
» Log in as expert.
» Click TS Generator.
» Click Add.
Parameter Description
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).
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.
The MDM6100 has the possibility to perform in-band remote management using MPE
Encapsulation and Decapsulation.
Parameter Description
Select TS Select one of the available transport streams, where MPE can be
extracted from.
» Click Update.
Parameter Description
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.
This must be the same as the one used by the transmitter.
Config Select one of the available TSs defined in the configuration table.
» Click Update
Parameter Description
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.
» Click Update
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.
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.
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.
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.
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.
Parameter Description
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.
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..
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.
Parameter Description
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
Parameter Description
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.
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.
All session words or IDs used are in hexadecimal. For the algorithms, they are
represented with the most significant byte (bit) first.
» Click Add
Name Description
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 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!)
» Click Add;
Name Description
» Click Update.
Note: Maximum two BISS scrambler instances are allowed in the current version.
• 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.
» Log in as expert.
» 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.
Alarm Description
BISS PAT Error When the CRC of the PAT is not valid then this alarm is raised.
BISS CAT Error When the CRC of the CAT is not valid then this alarm is raised.
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).
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).
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.
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).
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.
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.
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.
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.
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.
• 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
» Log in as expert
To modify the Setup ID, click and enter the new value.
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.
• 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.
Location
Configure
Parameter Description
» Click Update.
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
Parameter Description
» Click Update.
» Click Add;
Parameter Description
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.
» Click Update.
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.
» Log in as expert
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.
Use this block to define on which incoming transport stream MPE data needs to be inserted.
Parameter Description
Select TS Select one of the available transport streams, where MPE can be
inserted.
» Click Update.
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.
1 1001 30 Video
1002 Audio
1005 Teletext
2 1501 31 Video
1502 Audio
3 2001 Video
2002 Audio 1
2003 Audio 2
» Click Add
Parameter Description
Program Number Assign a unique program number into the program table.
PMT PID Assign a unique Program Map Table Packet Identifier to the program.
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.
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
Parameter Description
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.
» Click Update.
The following figure illustrates how the classified traffic is shaped by the traffic shaper.
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
Parameter Description
CIR Enter the Committed Information Rate for this Shaping Node.
PIR Enter the Peak Information Rate for this Shaping Node.
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).
» Click Update
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.
The following sections explain how to configure the MPE encapsulator (sending site) and the MPE
decapsulator (receving site).
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.
» 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)
» Add a Mgmt channel configuring a specific MAC Address and selecting the Management Virtual
Network (capturing traffic arriving on one of the Mgmt ports).
» 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"
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.
» 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)
» 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).
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.
Measurements Description
PCR Interval Measured interval time (in ms) between two consecutive PCR packets.
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.
PCR Rate Displays the current rate calculated from the PCR values in the
corresponding PID.
Information Description
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.
Information Description
1_2 Sync_byte_error The correct sync byte (0x47) does not appear after 188 or 204 bytes.
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.3a Time interval between two consecutive PCR values is more than 40
PCR_repetition_error ms.
Location
Configure
» Click Add.
Information Description
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.
23 Tasks
23.1.1 Configurations
» Log in as Operator or Expert (Refer to section: Switch User Profile on page 55)
» Click Device
» Click Configurations
• Load a configuration
• Export a configuration
• Delete a configuration
• Make a configuration.bootable
MCX7000>>Actions
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.
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.
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.
» Click Device
When parameters are changed, they are not directly saved into the active configuration.
» Click Device
» Click Configurations
» Click Save…
» Click Device
» Click Configurations
» 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.
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 Configurations
» Click Device
» Click Configurations
» Click Export to export the XML file to a default folder (GUI) or to the FTP server (CLI)
» Click Device
» Click Configurations
» Click Delete…
» Click Device
» Click Configurations
» 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 .
» Click Device
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
» 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.
» Click Device
» 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.
» Click Device
» Click DSNG profiles export to export the current configuration file to a default folder (GUI) or to
the FTP server (CLI)
» Log in as expert
Before enabling this parameter it is advised to make a backup file. This allows to
roll-back to the previous configuration.
23.2 Toolbox
» Click Toolbox
23.3 Maintenance
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.
» Click Maintenance
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.
» Navigate to Maintenance
» Click Upgrade
» After the upgrade, a message is displayed that the upgrade was performed successfully
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
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
» Click Logs
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.
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
Location
» Click Documentation
The SNMP MIBs are also delivered on CD-ROM together with the device.
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
» Log in as expert.
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:
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
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.
• 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.
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.
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.
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.
Parameter Description
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.
26 Appendix - Specifications
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
• 188 or 204 byte mode
• Rate adapter
• MPTS or SPTS according to ISO/IEC 13818
26.3 IP Encapsulation
• Optional 4 MPE Encapsulators
• Max aggregate 70 Mbps
26.4 IP Decapsulation
• 4 MPE Decapsulators
• Max aggregate 70 Mbps
• DVB-S
Outer/Inner FEC: Reed Solomon / Viterbi MODCODs:
• DVB-DSNG
Outer/Inner FEC: Reed Solomon / Viterbi MODCODs:
• DVB-S2X Standard
Outer/Inner FEC: BCH/ LDPC
53 MODCODs (normal frames):
32APSK-L 2/3
64APSK-L 32/45
256APSK-L 256APSK-L
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
EQUALINK ® 3
• Linear and Non-Linear predistortion for all MODCODs
• Maximum rate 72 Mbaud
Spurious performance
Better than - 65 dBc/4kHz @ +5 dBm output level and > 256 kbaud
Non-signal related: < - 80 dBc @ +5 dBm output
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
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
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
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.
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.
Occupied 3 3 3 3
Bandwidth
(MHz)
Occupied 4 4 4 4
Bandwidth
(MHz)
Occupied 6 6 6 6
Bandwidth
(MHz)
Occupied 9 9 9 9 9
Bandwidth
(MHz)
29 Appendix - IP Handling
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.
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.
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.
VI-01
31 Appendix - Acronyms
Acronym Definition
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
Twitter.com/Newtec_Satcom
Linkedin.com/company/newtec
Youtube.com/NewtecSatcom
Slideshare.net/newtec_satcom