Professional Documents
Culture Documents
Seamless IP Switch
User Manual
Revision: 2.5
www.enensys.com
Contents
1 Introduction .................................................................................................................................... 4
1.1 Product Overview............................................................................................................................. 4
1.2 Related Documents .......................................................................................................................... 5
1.3 Requirements................................................................................................................................... 5
2 Features .......................................................................................................................................... 6
2.1 Switching criteria.............................................................................................................................. 6
2.2 Switching mode................................................................................................................................ 6
2.3 Seamless DVB-T2 switch-over ......................................................................................................... 6
2.4 Seamless RTP ................................................................................................................................... 7
2.5 Streams resynchronization ............................................................................................................... 8
2.6 FEC Management ............................................................................................................................. 8
2.7 Switching conditions ........................................................................................................................ 8
2.7.1 Switching conditions for TS streams .......................................................................................... 8
2.7.2 Switching conditions for RTP streams ....................................................................................... 9
2.7.3 Switching conditions for STL streams .......................................................................................10
2.8 Input priorities ................................................................................................................................10
2.9 Output mode ..................................................................................................................................10
2.10 Passthru Mechanism .......................................................................................................................11
2.11 Daisy chain mode ............................................................................................................................11
2.12 Monitoring and Supervision ............................................................................................................11
2.13 Peering mode ..................................................................................................................................13
2.13.1 Presentation ........................................................................................................................13
2.13.2 Normal behavior ..................................................................................................................13
2.13.3 Conflict management...........................................................................................................14
3 Walk Around ..................................................................................................................................16
3.1 Front Panel......................................................................................................................................16
3.1.1 Navigation ...............................................................................................................................17
3.1.2 Key Settings .............................................................................................................................17
3.1.3 Available Information ..............................................................................................................18
3.2 Rear Panel .......................................................................................................................................18
3.3 HDc-Multi........................................................................................................................................19
4 Installation.....................................................................................................................................20
4.1 Before Starting ................................................................................................................................20
4.2 Installing the IPGuardV2 ..................................................................................................................20
www.enensys.com
4.3 Accessing the IPGuardV2 Graphical User Interface ..........................................................................20
4.4 Connecting the IPGuardV2 to the IP Networks ................................................................................22
5 Operating the Product ...................................................................................................................23
5.1 HTTP / Web Interface ......................................................................................................................23
5.1.1 Main menu ..............................................................................................................................24
5.1.2 Configuration/Monitoring........................................................................................................24
5.1.3 Status Area ..............................................................................................................................25
5.2 Status ..............................................................................................................................................26
5.2.1 Alarms Display .........................................................................................................................26
5.2.2 Alarm Settings .........................................................................................................................31
5.3 Settings ...........................................................................................................................................31
5.3.1 General....................................................................................................................................32
5.3.2 TS Streams ...............................................................................................................................35
5.3.3 RTP streams.............................................................................................................................39
5.3.4 IP Streams ...............................................................................................................................41
5.3.5 Summary .................................................................................................................................42
5.4 Monitoring ......................................................................................................................................44
5.4.1 General statistics .....................................................................................................................44
5.4.2 Streams statistics .....................................................................................................................45
5.4.3 Logs .........................................................................................................................................47
5.5 System ............................................................................................................................................48
5.5.1 General....................................................................................................................................48
5.5.2 Admin......................................................................................................................................49
5.5.3 Network ..................................................................................................................................50
5.6 About ..............................................................................................................................................50
5.7 Example: Set up seamless switching between 2 T2MI streams.........................................................52
6 Upgrading the Product...................................................................................................................53
6.1 Getting Information on the Current Release ....................................................................................53
6.2 Installing an Upgrade Firmware .......................................................................................................53
7 Getting General Information .........................................................................................................54
8 Regulatory and Statutory Notices ..................................................................................................55
8.1 EMC and Safety Declaration ............................................................................................................55
8.2 Environment Specifications .............................................................................................................55
9 Technical Data ...............................................................................................................................56
9.1 Interfaces Specifications ..................................................................................................................56
9.1.1 IP Data Interfaces ....................................................................................................................56
www.enensys.com
9.1.2 Fault Relay Alarm.....................................................................................................................56
10 Application note: Peering mode ....................................................................................................57
11 Troubleshooting ............................................................................................................................61
11.1 Focus onto IGMP with IPGuardV2....................................................................................................61
12 Equipment Return for Repair .........................................................................................................62
13 Upgrades and Privileged Area ........................................................................................................63
14 List of Acronyms ............................................................................................................................64
15 Contact Information ......................................................................................................................66
www.enensys.com
IPGuardV2 is the new generation of ENENSYS seamless IP switch that provides an automatic 1+1
redundancy mechanism for:
- any equipment IP based equipments
- any IP networks
Regarding IP based equipment, it enables the 1+1 redundancy of DVB, ATSC or ISDB multiplexers, DVB-T2
Gateways or any T2-MI streams, Video over IP Gateways that deliver MPEG- 2 TS over IP network. Also, it
can offer the 1+1 automatic redundancy of data servers, EPG servers, ESG servers that delivers IP based
services.
IPGuardV2 performs the automatic changeover between two IP Streams upon IP stream missing loss,
upon advanced IP drawbacks, upon detection of ETR 290 level 1, 2, 3 errors, upon detection of T2-
MI errors, or upon advanced MPEG-2 TS errors.
- a DVB-T2 seamless switch-over when used with ENENSYS' DVB-T2Gateway including T2guard
option
- an ATSC3.0 seamless switch-over when used with ENENSYS' ATSCheduler including STLGuard
option
- An ISDB-T seamless switch-over when used with ENENSYS' TbGateway including Tbguard option.
- A RTP based seamless switch-over between 2 identical RTP streams
The whole solution offers a unique DVB-T/T2 or ISDB-T or ATSC3.0 seamless switch-over over IP (in SFN and
MFN broadcasting) that prevents for any TV blackout due to the switching operation.
IPGuardV2 is also able to resynchronize the same MPEG-2 transport stream distributed over different
network IP paths with different delays so that it can seamlessly switch-over from one IP network to the
other one. It is also capable to resynchronize identical RTP streams to perform seamless switch-over
(SMPTE2022-7).
In case of power failure or equipment breakdown, IPGuardV2 maintains service continuity and outputs the
input IP signals as they are.
www.enensys.com
[1] ETSI TS 102 034 Digital Video Broadcasting (DVB); Transport of DVB
Services over IP"
[2] ETSI TR 102 033 "Digital Video Broadcasting (DVB); Architectural framework
for the delivery of DVB services over IP-based networks"
[4] ETSI TS 101 154 “Digital Video Broadcasting (DVB); Implementation guidelines
for the use of MPEG-2 Systems, Video and Audio in satellite,
cable and terrestrial broad-casting applications."
[5] ETSI TS 101 290 “Digital Video Broadcasting (DVB); Measurement guidelines
for DVB systems."
[6] ETSI TR 101 191 “Digital Video Broadcasting (DVB); DVB megaframe for Single
Frequency Network (SFN) Synchronization"
[7] ETSI EN 300 468 “Digital Video Broadcasting (DVB); Specification for Service
Information (SI) in DVB systems. (DVB-SI)”
IPGuardV2 embeds a Web server that provides a friendly and intuitive Graphical User Interface. This
interface is based on HTML5: a recent web browser (Internet Explorer, Firefox, Chrome…) is required.
www.enensys.com
The IPGuardV2 contains 2 main modes: TS/T2-MI and RTP. According to the environment, you must
configure the IPGuardV2 to the right mode.
- TS/T2-MI: this mode must be used if you want to perform seamless and/or near-seamless
switching between TS/T2-MI streams (MPEG2-TS). This mode allows to trigger a switch-over based
on ETR290 1/2/3 conditions and advanced audio/video criteria.
- RTP: this mode must be used if you want to perform seamless switching between identical RTP
streams. The RTP streams do not need to contain MPEG2-TS, it can be any IP data as long as it is
encapsulated into RTP packets. That mode must also be used for ATSC3.0 environment.
In both modes a pool of up to 60 IP switches is available to perform switching based on basic IP criteria.
- “1+1 port”: as soon as one error is detected in the set of monitored streams on the currently used
input data port, then the IPGuardV2 switches automatically to the other input data port.
- “1+1 stream”: as soon as one error is detected in one of the monitored stream, then the IPGuardV2
will replace it by the stream associated to this one on the backup port.
Likewise the seamless SFN switch-over mode, the IPGuardV2 can offer a seamless DVB-T2 switch-over
solution between two DVB-T2 Gateways when broadcasting over IP in SFN and MFN DVB-T2 networks.
The combination of the ENENSYS DVB-T2 Gateway with T2Guard option and the IPGuardV2 secures any
SFN and MFN DVB-T2 transmission during DVB-T2 Gateway change-over operations.
www.enensys.com
The comprehensive solution prevents DVB-T2 transmitters to re-synchronize themselves due to wrong SFN
synchronization information or T2 Frame desynchronization. Otherwise, DVB-T2 transmitters mute their
transmission waiting for consistent information after a certain period of time.
Once consistent, the DVB-T2 transmitter increases its power amplification step by step before outputting
any signal. The DVB-T2 signal becomes again on air after several seconds.
Thus, it is really important to secure the DVB-T2 Gateway switching operation so that it is transparent for
DVB-T2 transmitters.
The exact same architecture can be used: for ISDB-T/ATSC3.0 infrastructures by using
TbGateway/ATSCheduler and TbGuard/STLGuard technologies
The IPGuardV2 can be used to perform seamless switching between 2 identical RTP streams coming from 2
different network paths. RTP streams can contain any IP data.
If a RTP packet is missing on the output of one distribution network the IPGuardV2 will switch seamlessly to
the backup network path. Furthermore, the IPGuardV2 is able to resynchronize the streams coming from
the 2 different network paths as the propagation delay in the network links are different.
www.enensys.com
The IPGuardV2 is able to re-align two identical MPEG-2 transport streams, or T2-MI streams or RTP streams
(including STL) stemming from different IP paths with different delays.
According to the switching mode used, it performs an automatic switch-over either from one IP input to the
other IP input or from one IP stream to other IP stream seamlessly, so that it is completely transparent for
any transmitter and decoder.
This powerful feature saves operators configuration time by avoiding any fine tuning of the switching
condition parameters or any computation of some complicated or hazardous hysteresis on those
parameters. Operators simply select the switching conditions to trigger the switch-over, IPGuardV2
changes from the faulty IP input to the other one without degrading the output stream(s).
For TSoIP streams delivered over RTP, the IPGuardV2 supports Forward Error Correction based on ProMPEG
CoP#3 standard to correct IP packet loss.
The IPGuardV2 detects automatically the FEC streams which are delivered at port + 2 and port + 4 of the IP
stream data. If FEC decoding is enabled, it performs automatically the correction of one IP data packet lost.
By default, it also forwards the same FEC configuration at the output to enable other appliances to correct
packet loss after the IPGuardV2. However, the FEC configuration on the output can be customized (refer to
5.3.2.5)
IP link loss;
IP stream presence;
IP stream minimum bit rate;
RTP packet losses
ETR 290 level 1 alarms
o TS sync byte not equal to '0x47';
o PAT error (repetition, presence);
o PID missing
o Continuity counter error (incorrect packet order, lost packet) with possibility to alter on
specific tables;
www.enensys.com
ETR 290 level 2 alarms
o PCR error (discontinuity, repetition);
o CRC error on specific tables;
o Transport stream error;
ETR 290 level 3 alarms
o NIT error (wrong table reference, repetition);
MIP errors
o MIP timing;
o MIP periodicity;
o MIP structure;
o MIP presence;
o MIP pointer;
o MIP TS rate;
T2MI errors
o TS data piping presence
o TS data piping validity
o DVB-T2 signal consistency
o Packet counter
o CRC
o Packet type
o Packet payload
o Payload
Advanced errors
o Too high stuffing
o PID error
o Scrambling error
o Audio silence detection
o Minimum video bit rate
o Minimum audio bit rate
Switching conditions can be enabled and disabled upon operators’ choice/preference.
www.enensys.com
2.7.3 Switching conditions for STL streams
The following conditions are available for switch-over between STL streams:
IPGuardV2 supports different switching possibilities allowing to add priority on one input. The following
modes are available:
No priority: IPGuardV2 switches from one input to another one whenever one of the switching
conditions is reached.
Priority on IP1: IPGuardV2 selects first IP input as soon as this input is available and without any
error.
Priority on IP2: IPGuardV2 selects second IP input as soon as this input is available and without
any error.
Manual: operator can select one of both inputs. IPGuardV2 will output the selected IP input in
both outputs.
For TSoIP and RTP streams, it is possible to set the priority independantely for each stream.
www.enensys.com
- Daisy chain mode: specific mode allowing to gather processing power of several IPGuardV2 to
manage higher number of streams.
It offers a basic bypass mechanism where each input is duplicated to its equivalent output (IP1->IP3; IP2-
>IP4).
It can also output only the IP streams from one the data IP ports when the advanced passthru mechanism is
enabled.
For applications where a high number of streams needs to be monitored, IPGuardV2 offers a specific mode
called “Daisy chain”.
This mode allows to serialize several IPGuardV2 in order to increase the whole processing capability of the
system. By selecting this mode on one IPGuardV2 you indicate to the unit that some of the streams will be
processed by another IPGuardV2.
IPGuardV2 is fully compliant with the SNMP v2 protocol. It can be completely configured and monitored
through standard SNMP requests (Get, Set and Trap). Any command performed from the GUI or the LCD
uses SNMP requests meaning that MIB files are tested and verified.
Thanks to its FPGA-based architecture, the IPGuardV2 includes a large range of monitoring information for
each channel:
www.enensys.com
As IPGuardV2 is fully compliant with SNMP v2 protocol, it can be easily integrated into any NMS. The
IPGuardV2 is already managed into ENENSYS’ NMS solution based on DataMiner product. MIB files are
available on request. MIB Browser from iReasoning may be used to assess and test IPGuardV2 SNMP
features. It can be used for monitoring (Get and Trap) as well as for the control (Set).
www.enensys.com
2.13.1 Presentation
In order to cope with specifics use-cases, it is possible to peer several IPGuards together, so that they use
the streams coming from the same input at the same time.
- two or more IPGuard are peered using an IP proprieraty protocol exchanged on their IP control
port. Peering messages are sent over multicast.
- they have the same signals on their input as shown below:
IPGuardV2 #1
Peering
IPGuardV2 #2
When one error is detected on the used input of one of the IPGuard, it informs the other(s) peer(s) as
shown below:
IPGuardV2 #1
Peering
IPGuardV2 #2
The peers switch the stream in error to the other input as shown below:
IPGuardV2 #1
Peering
IPGuardV2 #2
www.enensys.com
Some important information about peering:
- When peering mode is enabled and seamless mode is enabled, any input change on IPGuards will
still be performed in either a seamless TS or a seamless T2-MI mode on both IPGuards
- When one IPGuardV2 detects an error on its selected input, it will:
o First switch automatically and seamlessly to the other input informs the other IPGuardV2 to
switch as well
- So during a small period of time (from error detection on the first IPGuardV2, to the switch-over on
the 2nd IPGuardV2) the two IPGuards does not use the same stream
- When switch-over has been performed on the 2nd IPGuardV2, system works properly
- When a unit is startup with the peering feature enabled, it will stay muted until it receives peering
message indicating which input should be used. If after 1 minute no message has been received
then the unit unmute.
www.enensys.com
Switch is performed from input 1 to input 2 on IPGuardV2 #2
4. Switch is performed
IPGuardV2 #1
Peering
IPGuardV2 #2
www.enensys.com
The IPGuardV2 offers a front panel that displays current settings and allows key settings such as network
configuration.
The STATUS green LED is visible when the IPGuardV2 operates properly without any alarm.
The STATUS LED turns orange or red to inform of a problem occurring on the ASIIPGuard:
LED turns orange if at least one alarm with Warning level has risen.
LED turns red if at least one alarm with Critical level has risen.
Note: the alarm severity can be defined for each alarm from the Status panel in the GUI.
www.enensys.com
Status Temperature
Ctrl IP address
Version number
About Name
Options
When the keypad is not used for 30 seconds, the display turns to standby mode (displaying Equipment type
and IP address).
Note: The USB port on the front panel is only used for ENENSYS internal maintenance purpose.
Do not try to use it to communicate with the IPGuardV2.
3.1.1 Navigation
To navigate into the IPGuardV2’s menu, use the touch buttons on the right side of the LCD:
www.enensys.com
As an example, here is the step by step procedure to change the IP address for the Control Eth. interface:
1. Press ’DOWN’ until the arrow (left side) is displayed next to Network.
2. Press ’RIGHT’ to go inside the Network menu.
3. Press ’DOWN’ to select the CTRL IP Address menu.
4. Press ’RIGHT’ to go inside the CTRL IP Address menu.
5. The LCD now displays the current IP address.
6. Press ’RIGHT’ to switch to edit mode. The IP address digit that is blinking is the one that is being
modified.
7. Press ’UP’ or ’DOWN’ to change the digit’s value.
8. Press ’LEFT’ or ’RIGHT’ to move to the previous/next digit.
9. Once the displayed IP address is correct, press ’RIGHT’ until the end of the line is reached to validate
the new IP address.
10.If you made a mistake and want to cancel the changes, press ’LEFT’ until you reach the beginning
of the line.
The rear panel features all physical interfaces used to connect the IPGuardV2 to the IP network for
controlling and monitoring it, to connect the equipment to the IP networks to provide 1+1 automatic
redundancy.
www.enensys.com
1x power receptacle with On/Off switch (90-260VAC, 50/60Hz). Optionally 1x power receptacle
with 48VDC can be delivered instead.
1x optional redundant power receptacle with On/Off switch (90-260VAC, 50/60Hz or 48VDC).
With the HDc-Muti, the IPGuardV2 can embed up to 6x units into the same rack unit. The configuration
with 6x IPGuardV2 looks like the following:
IP1 IP2 IP3 IP4 IP1 IP2 IP3 IP4 IP1 IP2 IP3 IP4
The pictures below shows the configuration with SFP extension on 3 IPGuardV2:
SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP
IP1 IP2 IP3 IP4 IP1 IP2 IP3 IP4 IP1 IP2 IP3 IP4 GPS 1PPS 10MHz
www.enensys.com
Before proceeding, please check that the box contains all of the following items:
IPGuardV2 device
1x Ethernet cable (RJ45)
Power supply cable
Quick start guide
If any item is missing or has defects, do not install the device and contact our Technical
Support team via email (support@enensys.com).
1. Use an Ethernet cable (RJ45 plug) to connect the IPGuardV2's “Ctrl” port to the control network.
2. Plug the power cable into the power receptacle on the IPGuardV2's rear panel. Then, connect the
other end of the cable to the main power.
3. Press the On/Off switch to power on the IPGuardV2. Allow the IPGuardV2 a few seconds to
initialize and start.
Each product in the HDc has its own web browser interface. Using this interface you can configure and
monitor the different parameters available on the product. All of the web browser interfaces of the HDc are
accessible through the same Ethernet control port named “Ctrl”. To access a specific product in the HDc
you must know its IP address.
Each product in the HDc has a default IP address according to its slot location as shown on the picture
below:
Remark: For products using 2 slots the IP address is the one of the bottom slot.
www.enensys.com
4. Open a Web Browser (Mozilla 2.0 or Internet Explorer 7.0 or later).
5. In the address bar, enter the factory IP address of the IPGuardV2 (e.g. http://10.5.120.101 for slot1),
or enter the new address you defined. If the configuration is correct, you should now be able to
access the corresponding user interface. Obviously, the Ethernet port of your computer accessing
the IPGuardV2 must be configured to be on the same subnetwork as the IP address you want to
access.
www.enensys.com
1. Connect one Ethernet (RJ45) cable to the first input (IP1) and to a switch or an appliance that
delivers IP streams.
2. Connect another Ethernet (RJ45) cable to the second input (IP2) and to a switch or an appliance
that delivers IP streams.
3. Connect an Ethernet cable (RJ45) to the first output (IP3) and to a switch or an appliance that can
receive IP streams. The IPGuardV2 outputs over IP3 IP data from IP1 or IP2 based on the IP services
configuration and states.
www.enensys.com
This section describes the web interface that is used to configure and monitor IPGuardV2.
To connect to the Web-based graphical user interface, proceed as explained in section Accessing the
IPGuardV2 Graphical User Interface.
The Web browser loads the application used to configure and monitor the IPGuardV2 and the graphical
user interface is displayed.
The Status page is displayed by default. It enables a one glance overview of the device without having to
navigate through panels:
Main menu area (upper part): the navigation menu will help you to configure IPGuardV2.
Configuration/Monitoring area (center part): shows the content of the panel and is the
dedicated zone where IPGuardV2 is configured.
Status area (lower part): lets you see the server activity and also save or load IPGuardV2
configuration information.
Each time you change manually one or several parameters, click the button to apply the
modification.
www.enensys.com
5.1.1 Main menu
The menu is used to select the submenu to access to the configuration and monitoring panels.
This menu gives access to the following panels that are shown in the Configuration/Monitoring area:
5.1.2 Configuration/Monitoring
The content of the configuration and monitoring panel varies according to the menu you selected. This
panel lets you:
Set up
o The inputs/outputs naming
o The output switch mode
o The passthru mode
o The output streams characteristics
o IP services parameters
o Switching conditions for TSoIP streams
Monitor
o The IP traffic
o The input bit rates
o The incoming FEC
o The number of switches
o The main alarms
All panels are described later in this document.
www.enensys.com
5.1.3 Status Area
The status bar displays the following information:
o Activated LED means that data is being transferred from the IPGuardV2 server to the
client HTTP browser.
Note: Bitrates may differ between input and output due to the following reasons: Input
bitrate integrate IP header size in its value / a slight difference may appear in T2MI case as
T2 gateway adds very few NULL packets that will not be transferred on the output.
Profile: lets you load or save IPGuardV2 configuration file profile. Please note that network
information is not saved.
If the profile loaded contains a TS switching type needing a reboot of the product the
IPGuardV2 will reboot automatically without informing the operator
Peering: if the “Peering” licence is enabled, this field indicates the current state of the peering
feature.
Switching mode: this fields indicates the switching mode set (Automatic or manual).
Note: After reboot, the IPGuardV2 automatically restarts with the latest configuration.
www.enensys.com
5.2.1 Alarms Display
The Status panel displays a global overview of the IPGuardV2 status. This panel also enables configuration
of each alarm independently.
Real-time information is provided and separated between General and Services. Alarms information is
refreshed every second.
Selector
The Selector area shows the general status of the equipment and the status of each service and lets you
select the alarms to display in the right area.
5.2.1.1 General
General
Temperature: shows the IPGuardV2 instant temperature level and indicates that the max
temperature set in the Settings tab of the Status panel has been reached.
NTP Server: this alarm is raised if the IPGuardV2 is not locked to an NTP server.
Forward Buffer overflow: indicates if an overflow occurred in the forward way of IPGuardV2.
Backward Buffer overflow: indicates if an overflow occurred in the backward way of IPGuardV2.
Output Error: this alarm is raised if no bit rate is detected in output (the value is 0 in the status
bar or no data link at the output).
Power supply 1: shows the status of the first power supply unit.
www.enensys.com
Power supply 2: shows the status of the second power supply unit.
IP1/2 Alarms
IP1/2/3/4 Data Link: if this alarm is raised, check that an Ethernet cable is properly plugged in
the corresponding Data input.
Consistent Data Port Speed: this alarm is raised if the bit rate values of IP ports 1 to 4 are
different. You can check the values from the Monitoring panel, in the Statistics tab.
TS/RTP Alarms
Switching error: this alarm is raised if the IPGuardV2 has performed a switch-over operation.
Streams synchronized: the IPGuardV2 is able to synchronize incoming streams (not available in
basic switch operation mode).
Peering
Peering connection: this alarm is raised if the IPGuardV2 cannot find any other peer over the
network.
Peering conflict: this alarm is raised in case of peering conflict (explained in Peering section)
5.2.1.2 IP alarms
Input Stream presence: this alarm is raised if the configured IP stream is not present at the input
during 1 second.
Input Bitrate: this alarm is raised if the incoming IP stream bit rate exceeds during 1 second the
user-defined minimum bit rate of the IP stream.
RTP Packet lost: this alarm is raised if a RTP packet loss has been detected.
5.2.1.3 TS alarms
ETR1
TS Sync: ETR290 normalized error detection on the active stream. Error on the TS sync byte.
Raised when two or more consecutive corrupted sync bytes occur (every 50ms).
Sync byte: this alarm is raised if the 0x47 TS synchronization byte is not detected in the incoming
TS stream.
PAT: this alarm is raised when the PAT is not detected during a given period (minimum and
maximum repetition value, between 0 and 5 000 ms), or when a PID 0x0000 does not contain a
table id 0x00 (PAT), or when the Scrambling control field is not 00 for PID 0x0000.
PMT: this alarm is raised if sections with table_id 2 (i.e. a PMT) do not occur at least every
0.5 seconds on the PID which is referred to in the PAT or if the Scrambling control field is not 00
for all PIDs containing sections with table_id 0x02. The value can be set between 0 and 5 000 ms
in the Switching conditions parameters (Settings panel).
Continuity counter: this alarm is raised if one of the following conditions is met:
o The packet order is incorrect
o A packet occurs more than twice
o A packet is lost
o A continuity counter error is detected over a user-defined list of PIDs.
www.enensys.com
PID: this alarm is raised when a PID declared within the PMT is not present in the stream, or
when a PID declared within the PMT is not present after the period defined in the Switching
conditions parameters (Settings panel), between 1 and 80 seconds.
ETR2
Transport: this alarm is raised when the Transport_error_indicator in the TS-Header is set to "1".
The primary Transport_error indicator is Boolean, but there should also be a resettable binary
counter which counts the erroneous TS packets. This counter is intended for statistical
evaluation of the errors. If an error occurs, no further error indication should be derived from
the erroneous packet.
CRC: this alarm is raised when a CRC error occurs in CAT, PAT, PMT, NIT, EIT, BAT, SDT or TOT
table (i.e. the content of the tables is corrupted). You can enable or disable filters on tables.
PCR discontinuity: this alarm is raised when a PCR (Program Clock Reference) discontinuity of
more than 100 ms occurs without specific indication
PCR repetition: this alarm is raised when the time interval between two consecutive PCR values
is more than 40 ms (threshold is configurable)
ETR3
Timing: this alarm is raised if successive STS values are not self-consistent.
Periodicity: this alarm is raised if the pointer value or the number of packets between each MIP
packet does not remain constant.
Structure: this alarm is raised if the syntax of the MIP does not comply with the specification in
TS 101 191.
www.enensys.com
Presence: this alarm is raised if the MIP is inserted into the transport stream more than once per
megaframe.
Pointer: this alarm is raised if the megaframe size is not constant over time.
T2-MI
T2-MI TS piping presence: this alarm is raised when the input stream is not a valid T2-MI stream.
T2-MI TS piping validity: this alarm is raised when the input stream is not a valid T2-MI stream.
T2-MI packet count: This error indicates a discontinuity of T2-MI packets.
T2-MI CRC: this alarm is raised if a CRC error occurs in at least one T2-MI packet.
T2-MI packet type: this alarm is raised if for each T2 frame packet types 1016 (L1-current data) or
2016 (DVB-T2 Timestamp) are not present. If L1 repetition, in-band signalling (IBS) is indicated in
the L1-current data, an L1-future packet (1116) shall also be present.
T2-MI packet payload: this alarm if the number of BB-frames (packet_type 0016) relating to a PLP
in a given T2 frame does not match the value of PLP_NUM_BLOCKS signalled in the dynamic
signalling of both the L1-current and L1-future (when present). The signalled values of frame_idx
and superframe_idx for BB-frame packets shall be consistent with the time interleaver parameters
specified in the configurable signalling of the L1-current.
T2-MI payload: Raised if the decoded plp_id in T2-MI packets with packet_type 0016 is not
included in the list (L1 post_signalling/ configurable) of plp_id for the T2-MI signal.
T2-MI PLP num blocks: this alarm is raised if the number of FEC blocks in an Interleaving Frame
for a PLP as signalled in the Dynamic L1-post signalling is not consistent with the number of BB
frame packets.
T2-MI transmission order: this alarm is raised if the packet_types are in a wrong ordering
and position inside a T2 frame.
T2-MI DVB-T2 timestamp: this alarm is raised if a wrong timestamp is delivered inside a
superframe.
T2-MI DVB-T2 timestamp discontinuity: this alarm is raised if a non increasing timestamp occurs
(not relevant with null timestamps).
Bit rate
Video bit rate underflow: this alarm is raised when the bit rate of one video component of the
whole incoming stream is lower than or equal to the value set in the Switching conditions
parameters (Settings panel), between 0 and 10 000 kbits/s.
Audio bit rate underflow: this alarm is raised when the bit rate of one audio component of the
whole incoming stream is lower than or equal to the value set in the Switching conditions
parameters (Settings panel), between 0 and 10 000 kbits/s.
Stuffing bit rate too high: this alarm is raised when the bit rate of null packets is higher than the
value set in the Switching conditions parameters (Settings panel), between 0 and 50000 kbits/s.
Service bit rate too low: this alarm is raised if at least one SID bit rate referenced in the list of
services to monitor is lower than the value set in the Switching conditions parameters (Settings
panel), between 0 and 50 000 kbits/s.
Service bit rate too high: this alarm is raised if at least one SID bit rate referenced in the list of
services to monitor is higher than the value set in the Switching conditions parameters (Settings
panel), between 0 and 50 000 kbits/s.
www.enensys.com
Click the Reset button to clear the counter associated to an alarm. Click the Reset all
counters to reset the counters of all the alarms.
Advanced
Unscrambling: this alarm is raised if the incoming stream is declared as not scrambled while it is.
Scrambled error: No alarm associated: switch if the incoming stream is scrambled.
Unscrambled stream: No alarm associated: switch if the incoming is not scrambled.
PID presence: this alarm is raised when user-defined PIDs are not present in the incoming
stream.
Service presence: this alarm is raised if at least one SID referenced in the list of services to
monitor is missing.
www.enensys.com
5.2.2 Alarm Settings
The Settings tab of the Status panel lets you set the alarm criticism and SNMP behavior of each alarm.
Check the Display box to display the alarm in the Display tab and show the related events in the Logs
Events panel.
Check the Trap box to enable SNMP trap for this alarm. The SNMP IP address trap receiver can
be defined in the Network window.
Check the Relay Out box to close the dry relay contact for this alarm. Cf. Using the dry relay out
interface
Select the Log level (Info, Warning, Critical) for each alarm. The logs can be displayed in the
Monitoring window. A warning alarm turns the front panel led in orange and a critical alarm
turns the led in red.
You may also set the Temperature threshold. This generates an alarm when the system temperature is
over crossed (value can be set between 30°C and 60°C).
Note: the system is self-protected against high temperature independently from the above
parameter. In any case, if for any reason (fan failure, missing air conditioning, etc.) the
internal temperature exceeds 70°C, the system will force mute to reduce its internal
temperature. A manual switch-off/switch-on will be used to restart the IPGuardE2.
To configure the IPGuardV2, open the Settings page and follow the tab ordering from left to right.
www.enensys.com
5.3.1 General
The General tab lets you set:
1+1 port: redundancy is performed at the interface level. If one error is detected on the currently
selected interface, all of the streams are switched to the backup input.
1+1 stream: redundancy is performed at the stream level. If one error is detected on a stream, only
this stream is replaced by its associated backup stream. So on the output stream can come
simultaneously from both inputs.
TS/T2-MI:
o Using this mode the IPGuard is able to support:
up to 6 switches for TS/T2-MI streams
AND
www.enensys.com
up to 60 switches based on basic IP criteria
o You must use this mode if you want to perform seamless or near-seamless switching
between TS/T2-MI streams triggered on TS/T2-MI switching conditions
RTP:
o Using this mode the IPGuard is able to support
up to 6 switches for RTP or STL streams
AND
up to 60 switches based on basic IP criteria
o You must use this mode if you want to perform seamless switching between identical RTP
streams based on RTP packet losses.
Auto
o No priority: the IPGuardV2 switches over one input to another one whenever an error
occurs on one of the monitored IP stream. It does not switch if it detects errors on the other
IP stream.
o IP1/2 priority: the IPGuardV2 selects the IP stream from the first/second input as soon as it
is available and without any error. Set the Changeover period, which is the number of
seconds after which the input is detected viable that the IPGuardV2 should wait before
switching back on this input. The changeover period cannot exceed 300 seconds (5 min).
Manual: select manually the IP streams input source.
Switch on interface minimum bitrate (available only in 1+1 port):
o This switching condition can be used to trigger a switch as soon as the global bitrate on the
selected interface goes below the specified value. This condition can be used on its own.
Switch on optical RX level (available only if DOM is enabled on the SFP transceiver):
o This criteria can be used to trigger a switch based on a minimum optical RX level. If enabled,
the IPGuardV2 will switch if the measured optical level on the link goes below that value.
The DaisyChain mode can also be enabled from here. While selected, the IPGuardV2 enters a specific mode
to pass not monitored stream to a next IPGuardV2 product.
www.enensys.com
Disable Backward traffic: by default packets incoming on outputs of IPGuardV2 are forwarded to
both input. Using this feature, all of the packets coming into the outputs of the IPGuardV2 are
blocked.
Basic: the IPGuardV2 outputs the IP traffic of input1 (IP1) to output3 (IP3) and the IP traffic of
input2 (IP2) to output4 (IP4).
Advanced:
o In 1+1 stream mode: the IPGuardV2 outputs the IP traffic of the defined priority input (IP1 or
IP2).
o In 1+1 port mode: the IPGuardV2 outputs the last selected input
OptiPLP mode: that option must be enabled only in configuration using ENENSYS’ OptiPLP mode.
That mode is used in specific DVB-T2 architectures.
Bitrate: set here the size of the window used for bitrate measurement. That can be useful for
application with very low bitrate in which one the size of the window needs to be increased. Keep
in mind that setting a higher window size reduce the reactivity of the product regarding bitrate
measurements.
PID presence: set here the size of the window used for PID presence and Service presence. That
value must be a multiple of the Bitrate measurement window size. That can be useful for
application with PID with very low bitrate in which one the size of the window needs to be
increased. Keep in mind that setting a higher window size reduce the reactivity of the product
regarding PID/Service presence.
www.enensys.com
All incoming IP streams: the IPGuardV2 always outputs all the IP traffic of input1 (IP1) or all the
IP traffic of input2 (IP2), in addition to the IP streams declared.
Only filtered IP streams: the IPGuardV2 outputs only the IP streams that are declared within the
IP services.
You can also set the priority input.
5.3.1.11 Peering
The following options are available:
Disable/Master/Slave: This field allows to enable the peering mode and to indicate if this unit is
Master or Slave.
IP @: The IP Multicast address used for communication relative to peering between Master and
Slave(s)
Conflict resolution: The conflict situation is explained here. This field allows the operator to set the
behavior of the slave(s) in case a conflict occurs.
o Mute Slave: If a conflict is detected, the slave mutes its output on the stream in error.
5.3.2 TS Streams
The IPGuardV2 can manage up to 6 TSoIP streams.
The right area lets you edit and update the TSoIP service parameters.
www.enensys.com
5.3.2.2 Inputs configuration
For each input set the stream IP configuration with:
- Source IP address and the source port
- Destination IP address and destination port
- VLAN ID if any
If Daisy Chain mode is enabled on the unit, then the Output 2 parameters are not used.
Indeed, in Daisy Chain, the streams going out on the Output 2 are exactly the one arriving on
Input 2 of the unit.
Note: the latency of the IPGuardV2 is equal to the resynchronization buffer value + the
latency introduces by the FEC if any (could be found in the “FEC decoding” part of the GUI)
www.enensys.com
Once the TS-based switching conditions are defined, you must set the switching conditions that trigger the
switch. Switching conditions are based on the ETR 290 level 1, 2 or 3, MIP, T2-MI and advanced TS criteria.
Please refer to section TS alarms for detailed information about the errors supported.
Note: As soon as one of the switching condition is reached, IPGuardV2 switches to the
backup data port or backup stream on the other port.
Resynchronization buffer: the size of the resynchronization buffer. To be seamless this buffer must
be higher than:
o The maximum delay between the 2 inputs
o The maximum duration set for any repetition measurement (e.g. PAT repetition…)
Resynchronization PID: This parameter is available only for “seamless switch” mode and allows you
to choose which PID is used for the resynchronization of the streams. By default it is set to the PAT,
but if the PAT is spread over several TS packets in your environment it must be set to another table
(for instance the NIT 0x10).
In near-seamless operation mode, the IPGuardV2 allows to switch over persistent errors. It may be useless
to switch with unsteady errors. You may prefer triggering the switch only if the errors persist over time. In
such a case, the IPGuardV2 can switch over after C seconds (C ranging from 1 to 600 seconds or 10 minutes
if errors occur every D seconds (D ranging from 1 to 60 seconds):
If during C period, no error occurs during D seconds, then no switch-over is triggered, C and D are
reset to 0, and the countdown starts again;
If an error occurs before D ends, the period is reinitialized waiting for another error; and so on…
When C ends and if D is still not reached (i.e. no error matching current switching conditions), the
IPGuardV2 switch over to the other inputs (if the latter is error-free)
www.enensys.com
5.3.2.7 Input priority
If “Per stream settings” is set for input switch mode in the General screen, the following fields are available:
You can then set the input switch mode specific to this TS stream.
The FEC decoding could be configured using the fields shown below:
FEC decoding enabled: Check this box if you want the IPGuardV2 to apply error correction on
the stream
Buffer size: this field allows you to configure manually the size of the buffer used for FEC
decoding. This value must be equal or higher than the recommended value otherwise error
correction might not be properly done. Increasing this value increases the FEC latency but
allows the IPGuardV2 to cope with more complex FEC settings.
FEC Latency IP 1/2: These monitoring fields indicate the latency added in the IPGuardV2 by
the FEC decoding using its current configuration.
By default, IPGuardV2 forwards (passthru mode) the same FEC configuration at the output to enable other
appliances to correct packet loss after the IPGuardV2.
To generate a new FEC scheme, select RTP mode and the FEC configuration.
To remove FEC after the IPGuardV2, select UDP (no FEC) or RTP (no FEC).
Note: When FEC decoding is disabled, “RTP packet loss” switching conditions cannot be
used. Furthermore the monitoring information regarding the packet losses rate are not
relevant.
www.enensys.com
5.3.3 RTP streams
The IPGuardV2 can manage up to 6 RTP streams.
The right area lets you edit and update the stream parameters.
You can then set the input switch mode specific to this stream.
www.enensys.com
5.3.3.3 Output configuration
For each output set the stream IP configuration with:
- Source IP address and the source port
- Destination IP address and destination port
- VLAN ID if any
If Daisy Chain mode is enabled on the unit, then the Output 2 parameters are not used.
Indeed, in Daisy Chain, the streams going out on the Output 2 are exactly the one arriving on
Input 2 of the unit.
The FEC decoding could be configured using the fields shown below:
www.enensys.com
FEC decoding enabled: Check this box if you want the IPGuardV2 to apply error correction on
the stream
Buffer size: this field allows you to configure manually the size of the buffer used for FEC
decoding. This value must be equal or higher than the recommended value otherwise error
correction might not be properly done. Increasing this value increases the FEC latency but
allows the IPGuardV2 to cope with more complex FEC settings.
FEC Latency IP 1/2: These monitoring fields indicate the latency added in the IPGuardV2 by
the FEC decoding using its current configuration.
By default, IPGuardV2 forwards (passthru mode) the same FEC configuration at the output to enable other
appliances to correct packet loss after the IPGuardV2.
To generate a new FEC scheme, select RTP mode and the FEC configuration.
To remove FEC after the IPGuardV2, select UDP (no FEC) or RTP (no FEC).
5.3.4 IP Streams
The IPGuardV2 can manage up to 60 IP streams.
The right area lets you edit and update the IP service parameters.
www.enensys.com
5.3.4.1 Stream name
Set a service name to ease the monitoring and supervision of the IP service.
5.3.5 Summary
This screen summarizes the streams monitored by the IPGuardV2.
www.enensys.com
Name: the name of the stream
For each IP interface: a field composed of @SRC:PORT_SRC/@DEST:PORT_DST describing the
characteristic of the stream on this interface. NA means “not defined by operator”
Type:
o ts: The stream is defined as TSoIP with a near-seamless switch-over mode.
o ts/seamless SFN: The stream is defined as TSoIP with a SFN switch-over mode.
o ts/seamless switch: The stream is defined as TSoIP with seamless switch-over mode.
o ts/seamless T2-MI: The stream is defined as TSoIP with a T2-MI switch-over mode.
o ip: The stream is defined as IP.
www.enensys.com
The Monitoring panel lets you monitor the overall incoming and outgoing bit rates. For TSoIP or RTP
streams, it provides information related to the delay between inputs (in Seamless mode), some IP and FEC
statistics and the TS structure. It also provides all the logs related to any error or some specific actions.
General:
o Maximum negotiated bit rate per data port
o If SFP transceivers are used and the DOM is enabled on them, TX/RX levels are displayed
o Instantaneous bit rate of the IP traffic of the inputs/outputs
o Instantaneous bit rate of the backward IP traffic of the inputs/outputs
The bitrates displayed are computed on Layer 3, meaning it does not include Ethernet
header
www.enensys.com
5.4.2 Streams statistics
The stream statistics tab indicates for each TSoIP/IP stream monitored:
For TSoIP streams
Instantaneous bit rate of the streams
Some statistics related to delay between the IP streams
The currently used input and the number of switch that occurred between the inputs
IP statistics
The MPEG-2 TS structure for both IP streams
o For RTP streams
www.enensys.com
Instantaneous bit rate of the streams
The measured delay between the streams
Some statistics related to delay between the IP streams
The currently used input and the number of switch that occurred between the inputs
o For IP streams
Instantaneous bit rate of the streams
The currently used input and the number of switch that occurred between the inputs
IP statistics
www.enensys.com
5.4.3 Logs
This panel displays tracking of any alarms triggered, with it associated severity:
From the Mode list, you can choose the mode of logs display:
The List mode shows the list of all log events, that is when an error occurs and when its stops.
The Advanced mode groups the events per alarm, that is the start event and end event of an
alarm are both displayed on a same row. In Advanced mode, you can filter only active or inactive
alarms using the Alarm state list.
To filter out log messages, based on severity level, use the Severity lists below the logs table.
To save the file in .XML or .CSV format for remote analysis, click the Download button.
www.enensys.com
5.5.1 General
You can also set the time zone of the IPGuardE2 manually.
Please note that the date and time parameters are used only for logs timestamp purpose.
You can also choose the SNMP version to be used. The V2C INFORM mode repeats the trap sending every
x seconds, x being the number of seconds set in the Delay field, and up to y times, y being the value set in
the Max repetitions field.
www.enensys.com
5.5.2 Admin
From the Admin panel, you can enable authentication on the IPGuardE2 and assign the relevant
login/password to access the product.
Administrator: the 'Administrator' user has access in read and write mode over all the panels of
the IPGuardV2.
User: the 'User' user has access only in read mode over all the panels of the IPGuardV2.
Only the 'Administrator' user can assign login password to both users.
A panel window with login and password fields is popped-up for each new access to the GUI.
A login/password shall be provided to access the IPGuardV2 GUI.
If you lose the administrator login/password, perform a factory reset from the front panel to restore the
default value.
www.enensys.com
5.5.3 Network
The IPGuardV2 embeds an HTTP server that enables remote access from any Web browser connected to
the same network as the “Ctrl” interface.
The IPGuardV2 Network parameters can be configured manually with a fixed IP address. A ping utility
makes it possible to check the connection of any other unit to the same IP network as the one IPGuardV2 is
connected to.
The About panel provides information about the device: Serial number, hardware and software versions. It
also includes a component that is used to update the device, used when a new version is available.
www.enensys.com
For more information about firmware update availability, please contact ENENSYS support team
(support@enensys.com).
Click the icon to access the ENENSYS privileged area. As an ENENSYS customer, we
strongly advise you to ask for login and password to access our privileged area.
Click the icon to open IPGuardV2 user manual. Please note that PDF reader must be
installed on your computer.
Click the icon to save system configuration logs that can be required by our support
team in case of trouble.
Click the icon to perform a factory reset of the IPGuardV2 but keep the control IP
address configuration.
Use the Name and Location fields to identify your IPGuardV2. These fields are also displayed on the front
panel.
www.enensys.com
Coming soon…
www.enensys.com
You can know the current firmware version used on the IPGuardV2:
From the GUI, select the About tab and look at the Information box.
Through SNMP, open the ENENSYS-ENTERPRISE-MIB file, then choose the platform > device >
deviceFirmwareVersion leaf.
It is also possible to know about the last upgrade performed on the IPGuardV2 through the
deviceLastUpdateTime leaf. If this OID returns 0, it means that the IPGuardV2 is using the factory
settings firmware.
From the front panel
3. Select the appropriate .bin file from the file selection dialog box.
4. Click Update.
Through SNMP:
3. Set this OID to an URL corresponding to the appropriate .upd file for upgrade.
A command-line tool is available on request and lets you apply update batches. Contact your sales
representative to obtain this tool.
www.enensys.com
To get information on a specific IPGuardV2 on the network:
From the GUI: go to the About panel. This panel provides information about the device such as
serial number, firmware version and available options.
Through SNMP: open the ENENSYS-ENTERPRISE-MIB file and open the platform > device node.
www.enensys.com
This equipment is a class A digital device. It has been designed and tested to meet the requirements set by
the European Community directives and comply with the EN50022 and EN50024 rules as an Information
Technology Equipment. It also complies with EN55103-1 and 55103-2 rules applying to Audio Video
equipment under E1 to E5 environment conditions. To ensure compliance, properly shielded cables shall be
used for data I/Os, proper power cable and technical grounding connection shall be used to feed the
Network Adapter and device shall be operated as described in that document.
This equipment has been tested and found to comply with the limits for a class A digital device, pursuant to
Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interferences in a residential installation. This equipment generates, uses and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a particular
installation. Operation of this equipment in a residential area is likely to cause harmful interference, in
which case the user will be required to correct the interference at his own expense.
The IPGuardV2 has been designed to meet the safety requirements of Information Technology Equipment
including business equipment from the European EN 60950 and International IEC 950. For safety reasons,
do not open the metal housing but contact ENENSYS Technical Support.
www.enensys.com
9.1.1 IP Data Interfaces
The IPGuardV2 includes 4x 10/100/1000 Base-T Ethernet interfaces (two inputs and two outputs) for data
networks. Ethernet interfaces are RJ45.
www.enensys.com
This application note explains the procedure to set-up a configuration with peering and 2 IPGuardV2.
1. As peering messages are sent through control port, both IPGuard should be able to access each
other’s control port. Any Ethernet switch/router between the IPGuard should be configured to pass
Multicast messages.
2. The physical configuration should be similar to this one (inputs are the same on both peered
IPGuard)
IPGuardV2 #1
Peering
IPGuardV2 #2
3. Open GUI on both units and check that peering licence has been properly enabled as shown below:
4. Go to settings tab and set one IPGuard as Master and set the Multicast address of the Peering
messages
www.enensys.com
5. Set the other one to Slave and the same Multicast address as the master for the peering messages
www.enensys.com
7. You can check that the communication works properly between the peers by going to
Status/Display screen and by checking that “Peering connection” alarm is green:
8. You can then add the TS streams in the “Settings/TS Streams” screen. It is mandatory to add the
streams in the same order on both Master and Slave.
www.enensys.com
Forcing an input to “Manual” in “Peering” mode forces the other IPGuard also in Manual
mode.
www.enensys.com
In order to use the IPGuardV2 into environment with IGMP it is important to take several points into
consideration.
Indeed, due to its internal characteristics, the use of IGMP with IPGuardV2 must be done with some
attention.
Two major points to take into consideration while using IGMP with IPGuardV2:
www.enensys.com
In case of any trouble with one of ENENSYS Technologies' products, please report it to our Technical
Support team via email (support@enensys.com). Your request should specify:
1
Returned Material Authorization
www.enensys.com
A privileged area (http://privileged.enensys.com) is available on ENENSYS' web-site. Any registered user has
access to the privileged area where general documentation, user's manuals, software’s and products'
upgrades can be downloaded. In order to get access to the privileged area, you should register through the
registration form. You will then receive a password that will give you access to the privileged area.
Registration is highly recommended as product upgrades will be announced using the registered users’
mailing list.
www.enensys.com
CSV Comma-Separated Value
IP Internet Protocol
PIV Pentium IV
SI Service Information
www.enensys.com
SMPTE Society of Motion Picture and Television Engineers
TS Transport Stream
www.enensys.com
ENENSYS Technologies HQ
6 rue de la Carrière
CS 37734
35577 Cesson-Sévigné
FRANCE
www.enensys.com