C.5Quality of service and packet loss in IP networks256
C.6Error improvement257
C.7Latency and overhead258
DQuality of Service, Setting Packet Priority261
D.1MPLS261
D.2Layer 3 routing261
D.2.1CP524 configuration262
D.3Layer 2 priority262
D.3.1CP524 configuration262
EAlarms263
FReferences277
1History
Revision DateComments
2.0.02013-11-01 – Updated with Nevion flavors.
1.0.382012-09-11 – Added section about Hitless switching and RTP/IP diversity reception.
1.02012-06-20 – First version of manual
History11
– Added global alarm config chapter.
– Added chapters on automatic service ID and PID re-mapping.
– Added sections on PMCP format PSIP-EIT/ETT loading (Dynamic PSIP).
– Section on generate system report.
– Added order codes in list of SW options.
– Updated output status header screen shot.
– Updated status header screen shot.
–
This manual is written for operators and users of the CP524 TS Adapter and provides necessary
information for installation, operation and day-to-day maintenance of the unit. The manual
covers the functionality of the software version 2.0.0 or later, and continues to be relevant to
subsequent software versions where the functionality of the equipment has not been changed.
When a new software version changes the functionality of the product, an updated version of
this manual will be provided.
The manual covers the following topics:
• Getting started
• Equipment installation
• Operating instructions
• WEB interface description
• Preventive maintenance and fault finding
• Alarm listing
• Technical specifications
2.2 Warnings, cautions and notes
Throughout this manual warnings, cautions and notes are highlighted as shown below:
Warning: This is a warning. Warnings give information, which if strictly
observed, will prevent personal injury and death, or damage to personal
property or the environment.
Caution: This is a caution. Cautions give information, which if strictly
followed, will prevent damage to equipment or other goods.
Note: Notes provide supplementary information. They are highlighted for
emphasis, as in this example, and are placed immediately after the relevant
text.
• All warnings marked on the product and in this manual should be adhered to. The
manufacturer cannot be held responsible for injury or damage resulting from negligence of warnings and cautions given.
• All the safety and operating instructions should be read before this product is installed and operated.
• All operating and usage instructions should be followed.
• The safety and operating instructions should be retained for future reference.
2.4 Contact information
Our primary goal is to provide first class customer care tailored to your specific business and
operational requirements.
The CP524 is part of the Nevion cProcessor product family for processing and handling of
MPEG transport streams. The cProcessor family represents a line of compact and powerful, yet
cost-effective, products designed for advanced modification of MPEG Transport Streams.
The CP524 is a Transport Stream Re-multiplexer for regional multiplexing of MPEG transport
streams.
The CP524 supports insertion of unsignaled PIDs on the input (Ghost PIDs) into outgoing
services.
3.1 Summary of Features
Features of the CP524 include:
• Flexible transport stream processing
− PID and program filtering
− Service component filtering by PID value or by component tag
− Program re-multiplexing (option)
− TS rate adaptation
− Minimum null-packet rate feature
• Powerful PSI/SI/PSIP handling
− PSI/SI regeneration
− Flexible EIT handling
− Zero or configurable minimum null-packet rate by filling up with EIT
• PSI/SI/PSIP editor
− Generate and create custom static PSI/SI/PSIP signalling.
− Easy integration to NMS systems with SNMP Trap support
− SNMPv2c agent
− Equipment monitoring from Nevion Connect
• Embedded redundancy controller (Option)
• RTP/IP diversity reception (option)
− Seamless switching between two IP streams from the same source.
• Transmission of transport stream over Gigabit Ethernet
− Forward Error Correction (Option)
• Reception of transport stream over Gigabit Ethernet
− Forward Error Correction (Option)
3.2 Software options
The CP524 functionality depends on the sofware licences installed. The following table describes
the features available as software options. Please refer to Section 8.4.8.3 for more information
how to obtain and enable feature upgrades.
Table 3.1.a Functionality enabled through software licences
FunctionalityCode Max
SFP moduleSFP-Enables operation of the Small form-factor pluggable (SFP)
SFP configurationSFPC-Enables configuration interface and parameter storage for some
Number of input
ports activated
Input switchingISW- Enables creation of input switching groups.
TSIX24 Controls the number of simultaneously activated transport stream
Caution: The CP524 must be handled carefully to prevent safety hazards
and equipment damage. Ensure that the personnel designated to install
the unit have the required skill and knowledge. Follow the instructions
for installation and use only installation accessories recommended by the
manufacturers.
4.1 Inspect the package content
• Inspect the shipping container for damage. Keep the shipping container and cushioning
material until you have inspected the contents of the shipment for completeness and
have checked that the CP524 is mechanically and electrically in order.
• Verify that you received the following items:
− CP524 with correct power supply option
− Power cord(s)
− CD-ROM containing documentation and Flash Player installation files
− Any optional accessories you have ordered
Note: 48 VDC versions do not ship with a power cord; instead a Power
D-SUB male connector for soldering to the supply leads is supplied.
4.2 Installation Environment
As with any electronic device, the CP524 should be placed where it will not be subjected to
extreme temperatures, humidity, or electromagnetic interference. Specifically, the selected site
should meet the following requirements:
• The ambient temperature should be between 0 and 50◦C (32 and 122◦F).
• The relative humidity should be less than 95 %, non-condensing. Do not install the
unit in areas of high humidity or where there is danger of water ingress.
• Surrounding electric devices should comply with the electromagnetic field (EMC) standard IEC 801-3, Level 2 (less than 3 V/m field strength).
• The AC power outlet (when applicable) should be within 1.8 meters (6 feet) of the
CP524.
• Where appropriate, ensure that this product has an adequate level of lightning protection. Alternatively, during a lightning storm or if it is left unused and unattended for
long periods of time, unplug it from the power supply and disconnect signal cables.
This prevents damage to the product due to lightning and power-line surges.
Warning: If the CP524 has been subject to a lightning strike or a power
surge which has stopped it working, disconnect the power immediately.
Do not re-apply power until it has been checked for safety. If in doubt
contact Nevion.
4.3 Equipment installation
The CP524 is designed for stationary use in a standard 19" rack. When installing please observe
the following points:
• Route cables safely to avoid them being pinched, crushed or otherwise interfered with.
Do not run AC power cables and signal cables in the same duct or conduit.
• The CP524 has all connectors at the rear. When mounting the unit, ensure that the
installation allows easy access to the rear of the unit.
• The fans contained in this unit are not fitted with dust/insect filters. Pay particular
attention to this when considering the environment in which it shall be used.
• Make sure that the equipment is adequately ventilated. Do not block the ventilation
holes on each side of the CP524.
4.4 Ventilation
Openings in the cabinet are provided for ventilation to protect it from overheating and ensure
reliable operation. The openings must not be blocked or covered. Allow at least 50 mm free
air-space each side of the unit.
Warning: Never insert objects of any kind into this equipment through
openings as they may touch dangerous voltage points or create shorts that
could result in a fire or electric shock. Never spill liquid of any kind on or
into the product.
• This product should never be placed near or over a radiator or heat register. Do not
place in a built-in installation (e.g. a rack) unless proper ventilation is provided in
accordance with the device airflow design as depicted in Figure 4.1.
• The CP524 may be vertically stacked in 19" racks without intermediate ventilation panels. In systems with stacked units forced-air cooling may be required to reduce the
operating ambient temperature.
Figure 4.1 shows the air path through the unit, where cool air is taken from the left
The CP524 may be delivered rated for AC or DC operation, respectively.
Warning: This product should be operated only from the type of power
source indicated on the marking label. Please consult a qualified electrical
engineer or your local power company if you are not sure of the power
supplied at your premises.
4.5.1 AC power supply
The CP524 has a wide-range power supply accepting the voltage range 100-240 VAC, 50/60 Hz.
Please refer to Appendix B for a detailed specification of the AC power supply.
4.5.2 Dual AC power supplies
Alternatively, the CP524 may be fitted with dual internal wide-range AC power supplies. If so,
the size of the cabinet is full-width 19" rack, 1RU. The power supplies cover the voltage range
100-240 VAC, 50/60 Hz.
During normal operation, load-sharing is used between the internal supplies. In case of a single
power supply failure alarms will be raised and the unit will continue operating off the second
power supply. To guard against failure in the external power circuitry it is imperative to connect
each power supply to separate AC mains circuits.
Please refer to
Appendix B for a detailed specification of the AC power supply.
4.5.2.1 AC power cable
Ensure that the AC power cable is suitable for the country in which the unit is to be operated.
Caution: Power supply cords should be routed so that they are not likely
to be trod on or pinched by items placed upon or against them. Pay
particular attention to cords at plugs and convenience receptacles.
The unit is supplied with a two meter detachable mains supply cable equipped with a moulded
plug suitable for Europe, UK or USA, as appropriate. The wires in the mains cable are coloured
in accordance with the wire colour code shown in Table 4.1.
Wire UK (BS 1363) EUROPE (CEE 7/7) USA (NEMA 5-15P)
Earth Green-and yellowGreen-and yellowGreen
NeutralBlueBlueWhite
LiveBrownBrownBlack
4.5.2.2 Protective Earth/technical Earth
To achieve protection against earth faults in the installation introduced by connecting signal
cables etc., the equipment should always be connected to protective earth. If the mains supply
cable is disconnected while signal cables are connected to the equipment, an earth connection
should be ensured using the Technical Earth connection terminal on the rear panel of the unit.
Warning: This unit must be correctly earthed through the moulded plug
supplied. If the local mains supply does not provide an earth connection
do not connect the unit.
Caution: Consult the supply requirements in Appendix B prior to connecting the unit to the supply.
The unit has a Technical Earth terminal located in the rear panel. Its use is recommended. This
is not a protective earth for electrical shock protection; the terminal is provided in order to:
1. Ensure that all equipment chassis fixed in the rack are at the same technical earth
potential. To achieve this, connect a wire between the Technical Earth terminal and a
suitable point in the rack. To be effective all interconnected units should be earthed
this way.
2. Eliminate the migration of stray charges when interconnecting equipment.
Warning: If the terminal screw has to be replaced, use an M4x12mm long
pozidrive pan head. Using a longer screw may imply a safety hazard.
4.5.2.3 Connecting to the AC power supply
Warning: Do not overload wall outlets and extension cords as this can
result in fire hazard or electrical shock. The unit is not equipped with an
on/off switch. Ensure that the outlet socket is installed near the equipment
so that it is easily accessible. Failure to isolate the equipment properly may
To connect the unit to the local AC power supply, connect the AC power lead to the CP524
mains input connector(s) and then to the local mains supply.
4.5.3 DC power supply
The CP524 can be delivered with a 48 VDC power supply for use in environments where this
is required. The DC power supply accepts an input voltage range of 36-72 VDC. Please refer to
Appendix B for detailed specification of the power supply.
4.5.3.1 DC power cable
Units delivered with DC power supply have a 3-pin male D-SUB power connector instead of
the standard mains power connector. Also a female 3-pin D-SUB connector is supplied. The
pin assignment is shown in Table 4.2. The power cable itself is not supplied.
Table 4.2 DC power connector pin
assignment
Pin Placement Specification
1 top+ (positive terminal)
2 middle- (negative terminal)
3 bottomChassis Ground
To connect the unit to the local DC power supply:
1. Use an electronics soldering iron or a hot air workstation to attach the supplied female
D-SUB power connector to suitable power leads.
2. Connect the power leads to your local power supply.
3. Connect the DC power connector, with attached power leads, to the CP524 power input
connector.
4.5.4 Powering up/down
Before powering-up the unit, please ensure that:
• The unit is installed in a suitable location
• The unit has been connected to external equipment as required
Power up the unit by inserting the power cable connected to the power source. When the unit
has finished the start-up procedure, the fans will run at normal speed. Please check that all
cooling fans are rotating. If they are not, power down the unit immediately.
Power down the unit by removing the power supply connector at the rear of the unit.
The CP524 is an MPEG Transport Stream Adapter, designed for easy and flexible manipulation
of Transport Streams for carriage over ASI, SMPTE 310M or Ethernet connections. The SFP
connector can also be used for data carriage. Use of SFP is enabled with a SW licence key.
The product offers an easy-to use WEB based user interface, a flexible and powerful MPEG
Transport Stream re-generation module and integration with network management systems via
the SNMP interface.
This chapter gives a brief description of the inner guts of the CP524, to give a better understanding of how the product works, how you use it and what you can use it for.
Figure
5.1 shows a functional block diagram of the main components inside CP524. The different
blocks are described more in detail in the following sections.
Figure 5.1 Product block diagram
5.2 TS inputs
The CP524 can be fitted with up to 8 ASI ports. Each of the ASI ports can be used as either
input or output port. When only using IP output, all 8 ASI ports can be used as inputs. In
ATSC+DVB configuration mode, SMPTE 310M input format is also supported.
In addition to 8 Transports stream inputs on ASI, a number of Transport streams can be received
on either of the Ethernet data interfaces.
The number of TS inputs that can be enabled simultaneously is limited with a SW licence key,
making it possible to start with few inputs and then enable more ports when needed. The
licence key also covers the transport streams received on Ethernet/IP.
5.3 TS output
The CP524 can generate up to 4 MPEG output Transport Streams. The outputs can be programmed to be presented as ASI on one or more of the physical BNC I/O connectors as
described in chapter 6.1.2. In ATSC+DVB configuration mode, SMPTE 310M output is also
supported.
The output is always re-clocked, configuring a wanted bitrate for each output multiplex.
The output transport stream can also be transmitted on either of the Ethernet data interfaces.
5.4 Input switching
The CP524 supports combination of several inputs into a prioritized order switching group,
where the highest priority source that has sync and no critical alarms, is automatically selected
as the source of program data and PSI/SI/PSIP data.
The input switch is itself modelled as an input, so once defined, it can be referred to as the
source of programs and PSI/SI/PSIP data when building up the output multiplex. A sync loss
on the currently selected source will cause immediate switching to an alternative input in the
switching group.
The signals on each of the inputs in a switching group, can be identical or different. Fastest
switching times are achieved when the signals are identical with respect to PIDs and services.
The input switching function can be used on both ASI sources and IP sources, or any combinations of these. Signal loss detection on IP sources is slower than for ASI sources.
Sources that are members of a switching group cannot be referred to directly.
The input switching feature is protected by a SW licence key.
5.5 Video over IP
5.5.1 Input and output
The CP524 supports MPEG transport streams over IP, input and output.
IP inputs are defined dynamically on need, up to a maximum number that is 16 at the time
of writing. Once the IP inputs are defined, they are modelled to have the same functionality
as the ASI input ports, and content received will be available to the multiplexer generating the
output. The input streams can be either SPTS or MPTS and streams with or without RTP layer
are accepted.
The multiplexer can generate 4 output multiplexes and the operator chooses whether to transmit
these streams over IP or not. Each transport stream can be transmitted to up to 8 IP destinations.
Two Ethernet interfaces can be used simultaneously for video carriage, the interfaces are bidirectional. When using the SFP slot, one of the Electrical interfaces will be disabled.
When transmitting and receiving MPEG transport streams over IP, the protocol mapping is
according to figure 5.2. The VLAN framing and RTP encapsulation are optional.
The RTP layer is important for diagnosing network related problems, since it contains a sequence
number that can be used for packet loss detection.
The maximum transfer unit (MTU) for Ethernet is usually 1500 bytes. This limits the number of
transport stream packets to embed into the outgoing Ethernet/IP frames to be between 1 and
7.
5.6 Management sub-system
The management subsystem is a set of modules that handles all the interfaces to monitor and
control the operation of the CP524.
The management subsystem communicates with the users, both humans and machines, via the
following interfaces:
• Front panel and back panel LEDs for status
• Graphical user interface via Flash application in WEB browser
• SNMP traps on alarms
• SNMPv2c Agent
• TXP (T-Vips XML Protocol) to retrieve and set configuration and status
• Alarm relays on alarms
• SNTP client for real time clock synchronisation
• Terminal interface either over Telnet or USB interface for debugging
• FTP server for direct file system access
The management subsystem communicates with other internal modules to make the unit perform the wanted operations.
5.6.1 Graphical user interface
Operators monitor and control the CP524 mainly via the Adobe Flash GUI application served
from the device’s WEB server. The GUI application is accessed via a WEB browser that communicates with the configuration framework through an HTTP/XML based protocol.
The device exposes extensive status information to the web GUI providing detailed reports and
real-time monitoring displays to the device administrator.
All the device configuration parameters available on the CP524 can be controlled from the web
GUI.
5.6.2 Configuration database
The management subsystem processes configuration changes as transactions. All configuration
changes made to the device are validated against the current running configuration before
committing them to the device. This limits the risks of the administrator implementing changes
that may cause down-time on the unit due to incompatible configuration settings.
Configurations can be imported and exported via the GUI. It is possible to clone the entire configuration of one device to another by exporting the configuration of one device and importing
it to another.
Configurations exported via the web GUI are formatted as human readable/modifiable XML
files. These files can be viewed or altered using any standard text or XML editor such as
Windows Notepad.
To simplify cloning of devices, certain exported parameters within the XML file are tagged
as device specific and therefore will be ignored when imported to either the same device or
another. These parameters are as follows:
• Device Name and Inventory ID
• IP network parameters
• ASI Port mappings
• On-device stored configurations
5.6.3 Alarm manager
The CP524 contains an integrated alarm manager responsible for consistently displaying the
alarm status of each individual interface.
“Port Alarms” are alarms bound to a specific input or output port via a port indexing system.
The alarm severity for port related alarms can be configured per port level. “Device Alarms”
are global to the device and are not bound to any specific port. They do not follow the indexing
scheme. These are classified as “System Alarms”.
Alarms are graphically represented in a tree structure optimized for simplified individual viewing and configuration. The “Device Alarm” tree is available from the “Device Info” page. The
alarm tree for each port is available on the “Alarms” page for each port.
The alarm manager presents the alarm of highest severity upon the external interfaces of the
device. The severity level of each individual alarm can be defined by the administrator. Alarm
configuration is covered in greater detail in the “Alarm configuration” section.
SNMP traps are dispatched to registered receivers whenever there is an alarm status change.
Alarm relay 1 and alarm LED are controlled to signal whenever there is a critical alarm present.
Alarm relay 2 is configurable.
The alarm manager keeps a log in non-volatile memory of the latest 10000 alarms that have
occurred.
As an additional option, the alarm manager in the CP524 supports so-called Virtual AlarmRelays. These are highly programmable items that can be customised to react to virtually any
given alarm event or combination of alarm events. The status of each virtual alarm relay can
be viewed in the GUI and can also be exported using SNMP. Details on configuring the virtual
alarm relays can be found in the WEB interface section.
5.7 Time synchronisation
The CP524 contains an internal real-time clock that is used for all internal timestamps. The
internal clock is battery backed up in order to continue operating while the unit has no power.
The internal time can be synchronised as follows:
• Manual setting.
• From one of the ASI/SMPTE 310M ports (using TDT/TOT or STT)
• From NTP servers using SNTP protocol. Up to four NTP servers can be configured for
NTP server redundancy.
More than one clock source may be specified in a prioritised order. If one source fails the next
priority source will be used.
The internal clock can be used for generation of TDT/TOT on the output.
5.8 TSP Module
The TS Processor (TSP) module is the heart of the unit. Its job is to create a new MPEG Transport Stream based on configuration and current input signals. Figure 5.3 shows the different
components in the TSP subsystem.
The lower left hand corner represents the interface between the management subsystem and
the TSP subsystem.
The central process in the TSP module is the TS Builder, which handles the logic creating PID
routing and regenerate PSI/SI/PSIP based on configuration and current PSI/SI/PSIP tables.
Section 5.8.6 for more details on service and PID routing.
See
The following chapters covers more on the different modules shown in the figure.
Note: The overall architecture of the TSP module, and the description in
this chapter, is shared between several products in the cProcessor product
family, but not all modules are available on every product.
A PID router module tells the TS Builder which PIDs are present.
The router is used by the TS Builder to pass on the correct elementary streams from the input
to the output. New PID values can be assigned to any elementary stream. One elementary
stream can only be transmitted on an output once, so one input PID can only have one output
PID value. This is reflected in the GUI and configuration structure.
TS packets that have a route to the output are travelling on the “main highway” through the
unit. This is where video, audio and other service components are passed. Packets that are
filtered do not have a route.
The output TS packets carrying PSI/SI/PSIP may either be routed through on the highway,
or they are played out through the PSI/SI/PSIP playout module. This is one of the most
important details to learn from figure 5.3, since the applied configuration determines the data
flow direction.
The PSI/SI/PSIP TS packets on the input can, in addition to being routed on the highway to
the output, be routed to the PSI/SI/PSIP section filter module, which is briefly described in
section 5.8.2.
Read more about the prioritisation of data in chapter 5.8.4.
The PSI/SI/PSIP section filter is a real-time process in the system. It receives continuous streams
of TS packets on the different PSI/SI/PSIP PIDs and checks the content for version number
updates. One PSI/SI/PSIP table section can span a number of TS packets. The filter keeps state
information for every PSI/SI/PSIP PID and re-builds the section blocks whenever a version
number update is detected.
The output of the section filter module is re-created table sections (sub-tables). These are posted
to the input PSI/SI/PSIP database, which in turn triggers an event to the TS Builder.
5.8.3 PSI/SI/PSIP playout module
The PSI/SI/PSIP playout module is the reverse of the PSI/SI/PSIP section filter, and generates
a continuous streams of TS packets from PSI/SI/PSIP sections. PSI/SI/PSIP tables that are
configured in any “Playout” mode (see section
are played out via the PSI/SI/PSIP playout module according to the user configured repetition
interval.
An important detail in figure 5.3 is the arrow tagged with “Flow Control” pointing from the
player output queues to the PSI/SI/PSIP player. This means that data played out here is under
flow control making loss of TS packets unlikely. The flow control mechanism also makes it
possible to configure a SI/PSIP playout that fills up spare capacity with EIT packets, since a
buffer can be kept full with packets to insert when there is spare capacity.
8.6.2.7), are posted through this module. Tables
The playout module prioritises data in 2 levels; first by dividing the different table types into
3 groups that are handled by system processes of different priority, then by assigning each
PID stream to one of 3 packet posting queues with different priority level. All packets on
one PSI/SI/PSIP PID must be transmitted on the same queue to assure the the packets are
transmitted in sequence.
Table 5.1 shows the table_ID-to-process assignement in the first level of prioritisation.
Table 5.1 PSI/SI/PSIP playout table ID process priorities
3NIT other, SDT other, BAT, ETT, EIT p/f other, EIT schedule actual and other
Note: The priorities in table 5.1 are the priorities referred to by the output
alarm “Pri X tables delayed” where x is the priority level.
Table 5.2 shows the table PID to queue number assigment in the second level of prioritisation.
The actual priority of each of these queues can be configured, but the normal case would be to
use falling priority for these queues.
Table 5.2 PSI/SI playout table PID to queue assignment.
Table 5.3 shows the table PID to queue number assigment in the second level of prioritisation
Player Queue TablesCorresponding PID Values
Player 1PAT,CAT,PMT,TDT 0, 1, PMT*N, 20
Player 2NIT, SDT16, 17
in ATSC mode.
See Section 5.9 for a more details on PSI/SI/PSIP playout.
Player 3EIT18
Table 5.3 PSI/PSIP playout table PID to queue assignment.
Player Queue TablesCorresponding PID Values
Player 1PAT,CAT,PMT0, 1, PMT*N
Player 2MGT/TVCT/CVCT/SST/RRT 8187
Player 3EIT/ETTX
5.8.4 Output Priority Queue
The right hand part of figure 5.3 represents the TS packet output priority queue of the TSP. It
indicates that all data is prioritised before being output.
The CP524 generates a constant (configurable) output bitrate translating to a fixed number of
available packet slots per time unit. Data from different sources are mapped to the priority queue
on the output to compete for the available bandwidth according to the configured priority rules.
Some data sources have fixed priorities to assure proper behaviour; other data source priorities
are configurable. The ones that are configurable are framed with a darker grey rectangle within
the MUX symbol in Figure 5.3.
PID sources fall into the following different categories:
Table 5.4.a Priority queue categories.
Cat. Sub-
A1MIP inserter packetsIf the CP524 is set to operate as an SFN adapter
NameDescription
group
and MIP packet transmission is configured, the MIP
packets are transmitted at fixed packet positions.
To assure exact positioning, these are transmitted
with highest priority.
B1Forced stuffingDownstream equipment may require a certain
C
D1Table data from internal carousels (PSI/SI/PSIP
E1Null packetsThese packets are stuffing packets that are
NameDescription
group
amount of stuffing packets to operate properly.
This may be guaranteed by activating the forced
stuffing function, specifying the maximum number
of TS packets between each stuffing packet. This
packet transmission operates at fixed priority just
below the MIP inserter, therefore the max distance
between each null packet may deviate with 1 from
the configured value if used in combination with
MIP insertion.
1Components routed from input (video/audio/data) This is typically audio or video components
belonging to an input service that are to be
inserted into the outgoing stream. CP524 will be
able to buffer these packets for a significant time,
but the delay through the unit shall generally be as
short as possible.
2Transparent input PSI/SI/PSIPDependent on the configuration for PSI/SI/PSIP
table handling, the input PAT and PMT tables may
be transmitted transparently as components
through the unit. No caching of these tables will
be done; they are let through on a
packet-by-packet basis.
3Unreferenced PIDsUnreferenced PIDs are components that are not
signalled in any services.
When PSI/SI/PSIP tables are configured for
player)
playout via the PSI/SI/PSIP player, the tables are
cached internally and are played out at the
configured intervals according to algorithms
described in this document. PID streams generated
by the PSI/SI/PSIP player are devided into 3
sub-groups on which the priority can be controlled
individually. The 3 queues are shown in table 5.2
transmitted when no other source requests
transmission of packets, i.e always at the lowest
priority.
MIP insertion, and hence Group A, is not available on the CP524.
Groups A, B and E have fixed priority, while the priority of the queues within the C and D
group may be freely configured. Group C and D queues can also be assigned a maximum
bandwidth.
Queues in group C are handled without flow control, meaning that packets will be discarded
if there is not enough packet positions on the output to empty the packets filled into these
queues. This will also happen if the bandwidth for each queue exceeds the configured shaping
threshold.
Group D queues used by the PSI/SI/PSIP player have flow control, allowing the player to
suspend waiting for available space. This means that if the D groups are configured with lower
priority than the C groups, and the available bandwidth after passing video/audio is less than
the bandwidth required to play out PSI/SI/PSIP at configured rate, the PSI/SI/PSIP player will
stagger on the queues, trying to fill up remaining capacity on the output. If the pass-through
data is not varying too much in bitrate, it will actually be able to fill up the stream, with the
effect of not having any stuffing packets inserted.
There are two main variants of the priority queue as presented in figure 5.4.
The basic variant to the left, offers 1 queue for category C data and the 3 shown queues for
group D data. Priorites can be freely configured between the category C and D queues.
The advanced queue configuration is only available on some products. Different flavours of
queue structures may exist.
Figure 5.5 Dual leaky bucket algorithm for bitrate shaping
Category C and category D queues (section 5.8.4) support configuration of bitrate shaping to
assure data is discarded if exceeding a configured threshold.
The method used for shaping is a “dual leaky bucket” algorithm illustrated in figure 5.5.
The configurable parameters are R1(Shaping) and B2(Max Burst). B1+B2<= Bt, where Btis
128 on the current implemention.
TS packets are dumped into bucket-1 when they arrive, and are extracted into bucket-2 at the
configured shaping bitrate R1. Only queues that have TS packets in bucket-2 participate in the
competition for a packet slot on the output. The highest priority queue that has a packet in
bucket-2 wins.
The maximum extraction rate R2from a queue is Rt, i.e the configured total output bitrate. The
B2parameter is referred to as “Max Burst” since, even with an R1that is much lower than Rt,
B2packets can be transmitted back-to-back at Rtif bucket-2 has been able to build up for some
time due to higher priority queues having data to send.
5.8.6 TS Builder - Service and PID routing
The TS Builder reacts to the following events:
• Configuration changes that affect the output Transport Stream.
• New PSI/SI/PSIP table arrived on any input, or a table has timed out on the input.
• Table update in the downloaded PSI/SI/PSIP database.
• Changes to the list of present PIDs on any input.
When activated, the builder retrieves information from the different databases and from the
PID lists, to create new PID routing.
If PSI/SI/PSIP tables are configured for playout, they are generated and posted to the PSI/SI/PSIP
playout module for continuous packetisation and repetition.
Services and PIDs are passed or stopped based on configuration choices made by the user or by
the system. Both services and components may be passed or stopped implicitly with a default
rule, or explicitly with an include or exclude rule.
Re-mapping of service ID and PID values requires an explicit routing rule.
The process of selecting services and unsignalled PIDs to pass can be illustrated by the flow
chart in figure
5.6.
First, each present PID is checked for a PID configuration rule. If there is no explicit configuration entry, unsignalled PIDs may be routed or stopped by a default rule. Signalled PIDs can
only be routed here if they are tagged with a pass-unconditionally rule.
Then the incoming PAT is traversed and the programs are routed in the order of which they
appear in the incoming PAT. If a program has an explicit rule, that rule is used either to stop
or forward the program. If no explicit rule is found the default rule for services on that port is
used either to stop or pass the service.
The ’Map Service’ block in the service routing diagram involves forwarding the wanted service
components for that service. This process is illustrated in figure 5.7.
As can be seen from the figure, service components are traversed in the order they appear in
the incoming PMT for the program. Then the same logic is applied to components merged from
other programs, and then the PCR PID before the known ECM PIDs. The order or traversal
determines which PIDs are dropped in the event of a PID conflict.
At the top of the loop we can see that the global PID table is checked for stop commands and
global re-map entries first.
PID rules are looked for before tag rules, and local re-mappings stored on either a PID rule or
a Tag rule are only used if no global remapping was found.
If no rule exists for the component, the default behaviour is retrieved from the service configuration for the given service. If this service is routed by default rule, the default component
behaviour is to pass the component.
If a PID conflict is detected with a PID previously routed in the routing process, the new PID
is filtered and an alarm is activated.
5.9 PSI/SI/PSIP playout
The CP524 contains a playout module for PSI/SI/PSIP tables as shown earlier in section
This module is designed to repeatedly transmit any legal PSI/SI/PSIP table to the CP524 output
transport stream.
The PSI/SI/PSIP played out is managed on a table to table basis, and may be sub-sets or
complete sets of tables retrieved from the inputs, or complete sets downloaded from an external
SI/PSIP system.
The alternative to playing out PSI/SI/PSIP via the SI/PSIP player is to pass through PID elementary streams in the same way as for audio and video.
Bandwidth occupied by main components (audio/video)
Remaining variable bandwidth available for carousel data and Null packets
Time
5.9.1 Main configuration
The fundamental configuration parameter for the playout module is to specify a wanted repetition
interval for a given table ID. Each table (identified by table_id and a number of sub-id’s) is played
out regularly at the given interval. The repetition interval indicates the maximum time a receiver
must wait before the table is received and is therefore an indication of the perceived quality of
the service (wait time before receiver has fetched all information).
The dependency between repetition interval and resulting bitrate is dependent on several factors:
• The number of tables that should be played out
• The size of each table; larger tables yields higher rate
For a given table ID and corresponding sub-ID’s, the playout module will aim to keep the
configured repetition interval. It will also play out the tables such that the requirement for
minimum distance between sections (25ms) will not be violated.
5.9.2 Carousel priorities
Within the PSI/SI/PSIP player, there are 3 priority levels for tables as shown in table 5.2 in
chapter 5.8.3. The priority levels become significant when there is not enough bandwidth
available in the output stream.
The PSI table queue is typically placed at a high priority level, above data routed from the input
to assure PAT and PMT is transmitted even in an overload situation.
The EIT queue is typically configured at lowest priority with a high bandwidth limitations if
one want to fill up rest capacity with EIT. Another option is to configure the EIT queue at
high priority but with a limited bandwidth to create an EIT stream with sub-table repetition
intervals that are not influenced by other content on the output, but with a controlled bandwidth
consumption.
5.9.3 Carousel bitrate
In a typical scenario, the available Null packet rate available for PSI/SI/PSIP playout will be
variable, as shown in figure 5.8.
Figure 5.8 Illustration of remaining variable bandwidth in
transport stream
1. All repetition intervals fulfilled.2. Complete saturation3. Bandwidth limited playout
It will be possible to configure at least 3 scenarios with the CP524 product.
1. There are plenty of available bandwidth in the transport stream, and the resulting
bandwidth due to repetition rate configuration fits well within the available bandwidth.
2. The configured repetition rate results in a bandwidth that is too high compared to the
available bandwidth. The playout carousel will utilise all available bandwidth.
3. Carousel max. bitrate is set to a certain value to guarantee a certain amount of Null
packets in the outgoing transport stream. If the repetition intervals are set sufficiently
low, the carousel playout will utilise all the bandwidth within the configured limits.
The 3 scenarios are shown in figure 5.9.
Figure 5.9 Three different playout scenarios
For case 2 and 3, we have a saturation scenario, e.g. the carousel will completely fill up the
configured bandwidth. In this scenario, the configured repetition intervals will not be fulfilled.
All configured tables will “suffer” a certain amount. The expected behaviour for this scenario
is described in the next section.
5.9.4 Bitrate saturation handling
This chapter does not apply in ATSC mode.
In the descriptions below, we assume that the different tables are played out on the same carouselpriority level, for example priority level 3.
Scenario: The configured repetition intervals lead to a bandwidth that is higher than the configured bandwidth. The playout carousel will continuously try to transmit tables to the output,
leaving no room for null packets at all.
In this case, the playout module will try to “spread” the resulting delay equally across all tables,
independently of configured interval.
• Assume that one EIT table group is configured with 9 seconds repetition interval while
later groups are configured with 27 seconds interval and this leads to a saturation
scenario.
• A resulting scenario in this case may be that all tables will suffer 3 seconds higher
repetition intervals
• The interval for the first group will increase from 9 to 12 seconds while the interval for
the second group will increase from 27 to 30 seconds.
Note that the scenario above is just intended for illustration. In practise, the suffered delay
will vary dependent on the available bitrate in the stream. There will also be a small random
variation in the delays due to variable section lengths etc.
5.9.5 Configurable back-log time
This chapter does not apply in ATSC mode.
Refer to
ured too low to keep up with the configured repetition intervals, each output table will “suffer”
a certain time for each repetition cycle. Compared to the “ideal” playout time, each section will
be more and more delayed.
When the output bitrate capacity becomes high enough again to keep up with the configured
repetition intervals, there are basically two ways to go:
CP524 allows for both strategies, using a configurable “back-log” time. Figure
the concept.
The dark green graph illustrates the “ideal” transmission time for each section. It is a long line
with “even” spacing between each table section.
The purple graph illustrates a table that does not allow for “back-log”. In period B, the distance
between each section again becomes the normal, configured interval.
The red graph illustrates the case when a back-log is configured larger than zero. In this case,
the CP524 will actually reduce the transmission interval until the “ideal” line again is reached.
This means that the average repetition interval will be fulfilled.
Section 5.9.4 regarding bitrate saturation handling. In case the output bitrate is config-
1. Accept the resulting introduced delay and just continue using the normal repetition
interval. The wanted repetition interval has then not been achieved for the time period
that passed.
2. Try to utilise the extra capacity available and “speed up” transmission by using a lower
repetition interval. In this way, it is possible that the average target repetition interval
will be fulfilled.
5.10 illustrates
The back log time is controlled by a configuration parameter “Backlog time”, which is specified
as a fraction of the repetition interval. The default value is 1.0, which indicates that a table is
allowed to be delayed by time for one, complete repetition interval.
5.10 Programming Metadata Communication Protocol (PMCP)
Programming Metadata Communication Protocol (PMCP), specified in ATSC A/76, is a standard
for use within digital television broadcast facilities for transfer of source data used to generate
EIT and ETT tables comprising the electronic program guide (EPG) listings and other programrelated information. PMCP is a XML-based platform-independent protocol for the exchange
of data, which may then be transported between systems in a variety of forms such as files,
messages, web or e-mail services. The resulting data may then be sent to a ATSC PSIP generator
for conversion to a broadcast-ready format. A generic overview of EPG regeneration using
PMCP can be seen in figure 5.11
Support of the PMCP-standard on the CP524 requires a licence. This licence enables acquisition
of PMCP data from an HTTP-server or an FTP-server to regenerate PSIP EIT and ETT tables. This
is achieved by parsing the XML-based structure of PMCP and translating it into an internal data
structure, ready to be regenerated into PSIP tables. The regenerated tables are then multiplexed
on-the-fly together with the transport stream processed by the CP524, and transmitted on regular
intervals at the output.
Figure 5.11 Genericoverviewof
EPG regeneration using PMCP.
5.11.1 General
The CP524 offers a SW module for redundancy on service level. The module monitors the
alarm level for two services and selects the best service according to the user specified switching
criterias.
Note: Service fall-back is a licensed feature and this tab is only visible if
the licence key is installed.
A block diagram of the service fallback switcher is shown in figure 5.12
The service fallback switch controller only relates to alarm levels for the two corresponding
services and the ports for each service. It is up to the user to configure appropriate alarm levels
for each of the alarms an input/service is able to generate. The switching criteria are configured
as follows:
For each alarm level (starting with the highest, most severe level), the following configuration
is done:
• Enable/disable switching for this level
• Required alarm level of the other (spare) input to allow switching
• The confirm time for this level (how long to wait before doing a switch)
The required level of the other service needs to be lower than the configured level, e.g. when
configuring the switch criteria for “Critical (6)” main level, the spare input must be on level
“Major (5)” or lower.
Example: A very simple configuration may be to only switch on “Critical (6)” level and require
“OK (1)” level on the spare input.
In “auto” state, the switch controller is “armed” and continuously listens to change in the top
level alarm status for each service. For each change event, the controller evaluates the levels and
checks if the switching criteria is met. If the answer is “yes”, the controller does the following:
• If the confirm_time is zero, the controller does a switch immediately and jumps to
a wait state where it will wait switch_timeout seconds before it re-enters the auto
state.
• If the confirm_time is larger than zero, the controller jumps to a wait_confirm state
to actually confirm that the switch criteria still is met after the configured time. If the
criteria is still met, the controller performs a switch and jumps to the wait state. If the
criteria is no longer met, the controller does no switching and jumps back to the auto
state.
Both the confirm_time and switch_timeout can be individually configured for each service
switcher.
The state of the switch controller (including timing information) is available in the GUI.
5.11.2 Details on confirm timeout handling
The confirm_time is configured for each severity level. I.e. a confirmation time for “critical”
main input level can be set lower than for “major” and so on.
For example, 5 seconds may be configured for the “critical” state while 20 seconds may be
configured for the “major” state.
A special case deserves more explanation: multiple alarms, with different severity levels, during
the wait_confirm state. The controller is designed so that it will not “stay forever” in the
wait_confirm state and will respond to the most critical alarm.
The controller has separate timers for each severity level, and each timer has an independently
configured confirm_time. When an alarm event is detected the timer for that alarm level
will be started and the switch will enter the wait_confirm state. When the timer reaches the
confirm_time then the controller will perform a switch and enter the wait state. If, whilst the
switch is in the wait_confirm state, a second alarm event occurs with a different alarm level
then the timer for that alarm level will be started and will run “in parallel” with the timer for
the first alarm event. There is then a “race” between timers and in this case the first timer to
reach its confirm_time will cause the controller to perform a switch and enter the wait state
at which point all alarm timers are reset.
Three example scenarios illustrate the behaviour. Assume that the controller is configured to
switch at both “major” and “critical” levels.
The confirm_time values are configured as follows:
Major: 30 seconds
Critical: 5 seconds
Example scenario 1
• A major event is detected and the switch controller jumps to the wait_confirm
state and the alarm timer for the major event alarm level is started.
• After 10 seconds, a critical event is detected and the alarm timer for the critical
event alarm level is started. After a further 5 seconds the critical event alarm timer
reaches its confirm_time and the controller will perform a switch. (The critical
alarm timer “beats” the major event timer in the “race” to switch).
Example scenario 2
• A major event is detected and the switch controller jumps to the wait_confirm
state and the alarm timer for the major event alarm level is started.
• After 28 seconds, a critical event is detected and the alarm timer for the critical
event alarm level is started. After a further 2 seconds the major event alarm timer
reaches its confirm_time and the controller will perform a switch. (The major
alarm timer “beats” the critical event timer in the “race” to switch).
Example scenario 3
• A major event is detected and the switch controller jumps to the wait_confirm
state and the alarm timer for the major event alarm level is started.
• After 10 seconds, a critical event is detected and the alarm timer for the critical
event alarm level is started. After a further 2 seconds the critical event clears and
the critical event timer is reset without a changeover occurring. After a further 18
seconds the major event alarm timer reaches its confirm_time and the controller
will perform a switch. (The critical alarm exits the “race” after 2 seconds without
a switch being carried out).
Functional Description45
5.11.3 Manual switching on GPI
The service fallback module has the option to be manually controlled by a GPI (general purpose
input) signal on the relay/alarm connector (see
This GPI signal can also be used to trigger a unit reset. Naturally, only one of the functions can
be used at a time.
When used as an input to a service switcher, the GPI signal is used for manual switch over,
performing the same action as when pressing the ’switch to main’ or ’switch to spare’ buttons
(see Section 8.6.2.5.4).
5.14 shows the timing contraints on the GPI input signal. The input signal is sampled 10 times
a second, and a state change is detected on 3 consecutive samples in the same state after a flank.
The black lines in the diagrams show the input GPI signal, which is used to generate an internal
GPI state signal shown in red. Whenever the GPI input state changes an event is sent to the
service fallback switch controller, which will perform a switch if switching on GPI is enabled
and the new state signalled is oppsite to the currently active service. The blue line, which
indicates the currently active output service, shows that there is a delay TBbetween the GPI
state change and the actual performance of the switch.
The first part of the last time line in the diagram shows how the GPI line should be controlled
to perform a manual switch if the current level of the GPI is already in the same position as the
wanted switch position. A pulse of slightly more than one sampling interval is required before
pulling the signal back, to be able to detect a flank.
Sample point with down-count from flank to GPI state change
GPI signal
Filtered GPI state
Service switch position
TA 0.2-0.3s Time from GPI flank to state change
TB Time from GPI state change to service switch
normal switch main to spare
normal switch spare to main
switch to spare, spare already active
interrupted switch
Switch spare to main, dual flank
T
C
TCMore than 0.1s for successful flank detection
5.12 Hitless switching
The CP524 enables hitless switching by combining smallcast on the transmitter side with RTP/IP
diversity reception on the receiver sider. Hitless switching provides redundancy by protecting
the stream against errors in IP transmission, but in a different manner compared to Forward
Error Correction (FEC). FEC is designed to protect the stream against single or short burst packet
losses, whereas hitless switching provides protection against loss of complete data input, for
example, due to link or equipment failure.
The main idea of hitless switching is to transmit two identical copies of the data stream over
separate network paths. At the receiver side, the data from the two incoming streams are
combined at packet level to form one data stream. This way, if one of the network paths
experiences severe packet loss or complete link failure, data from the other network path can
be used to output an error free stream.
At the transmitter side, the CP524 allows sending identical copies of the data stream to a user
defined list of destinations by enabling smallcast. During smallcast transmission all identical
streams are tagged with the same, randomly generated Synchronization Source ID (SSRC). For
each destination, the network interface (or a VLAN on any the interfaces) and separate unicast
or multicast destinations are selected so that the two data streams used for diversity reception
are routed to their respective network paths directly at the CP524 or at the first sebsequent
network node.
At the receiver side, the IP source parameters are first configured as the master and slave sources
(i.e. first and second IP source). When the data streams have identical SSRCs, they are assumed
to be identical streams and used for diversity reception. Diversity reception operates on the RTP
packet level. The two incoming data streams are combined to form one error free stream as long
as there is one correctly received packet from either input stream. There will be packet loss at
the combined stream only when the packet is received on neither of the two IP sources. The
data stream resulting from combining the two incoming data streams will then be processed as
one RTP packet stream. RTP/IP diversity reception is a licensed feature and is required at the
receiver side. No licence is required for smallcast transmission.
Note: If the same data streams are received at both sources, the sources
will act as equal providers of data. If received streams at the sources are
not identical, the data from the master IP source will be used and data
from the slave IP source will be discarded.
5.13 Redundancy controller
The Embedded Redundancy Controller is a generic software module that implements redundancy schemes. The module is included in the operational device; external PCs are therefore
not required for operation.
One separates between main and spare devices. A spare device continuously monitors the health
of an associated main device. When the spare detects a critical alarm condition in the main
device, the spare will take the necessary actions to replace the main device. The redundancy
controller may be configured to switch back to the main device automatically if the main device
recovers.
The main device requires no additional configuration when used in a redundancy scheme. The
only configuration needed is in the spare device since this unit controls the switching. The
Redundancy Controller licence must be present in both main and spare devices.
The communication between the devices relies on a proprietary XML protocol.
Figure 5.15 An overview of the embedded redundancy controller
All redundancy control enabled Nevion devices advertise a set of services. A service might be
an IP transmitter port, ASI port, SDI port etc. Any service on a Nevion device with redundancy control can be a spare for any compatible service on another Nevion device licenced for
redundancy control. The main tasks of the Embedded Redundancy Controller is to monitor the
health of the main device and if necessary take over control of transmission of one or several
services.
To be compatible, the two services must be of the same type and have the same service version
number.
The Embedded Redundancy Controller provides a strict one-to-one redundancy solution. Two
spare services cannot backup the same main service. A spare service cannot backup another
spare service. A main service cannot have two spare services.
The system will always be in one of the three states shown in table
Table 5.5 Typical states of the redundancy controller
StateMainSpare
Normal operationOutput enabledOutput disabled
Main service has alarmOutput disabledOutput enabled
No contact with main device Unknown, typically port on switch disabled Output enabled
5.5.
Normal Operation
The main services are output and the spare services are disabled. The redundancy controller polls the main device for status and service configuration. In addition a set of
SNMP OIDs can be monitored. These OIDs are set when a switch to spare services is performed due to loss of contact with the main device. The OIDs are also set when manually
switching the entire redundancy controller between main and spare services.
Main service has alarm
When the main service has an alarm and the switch criteria are fulfilled the service switcher
for that particular service will take the necessary actions to replace the main service. This
includes disabling the main service before applying the main service configuration to the
spare service and finally enabling output of the spare service.
No contact with main device
When the spare device loses contact with the main device all service switchers will switch
to spare transmission. In addition a set of OIDs can be set via SNMP. The purpose of this
is to be able to stop the transmission from the main device, even if there is no contact with
it. The most typical use is to configure a switch behind the main device to stop the data
transmission from it.
The Embedded Redundancy Controller also offers automatic switch back to main. After a switch
to the spare unit has been performed, the spare unit continue to poll the main device. When the
main device has recovered it is possible to perform an automatic switch back. The automatic
switch back scheme is seperated into three different options, “Return if OK”, “Return if spare
alarm”, “No return”.
The front panel provides two LEDs per CP524. The meaning of each LED indicator is shown
in table 6.1.
Table 6.1 Front panel LED descriptions
Indicator Colour Description
PowerGreen This LED is lit when power is on and initialisation is complete
AlarmRed This LED is lit when a failure is detected by the unit
These LEDs are also replicated on the rear panel, which is shown in figure 6.1.
Figure 6.1 Rear panel
Remove mains supply before moving or installing the equipment. Ensure ESD precautions are
observed whilst interconnecting equipment.
6.1.2 ASI ports
The CP524 is shipped with 8 ASI connectors on the back panel. The layout is as shown in figure
6.1. The ports have flexible direction control to best meet the usage scenario of the device.
The CP524 can generate up to 4 transport stream outputs, and each ASI port can either be used
as an output carrying a copy of a TS, or as an input to an input switch or the multiplexer.
Switching the direction on a port does not require a re-boot, and can be performed while the
other ports are in service.
6.1.3 ASI input ports
All physical ports are available for use as inputs, but the number of ports simultaneously enabled
as inputs is limited by the licence key Number of input ports activated.
6.1.4 ASI output ports
Any of the physical ports can be configured to carry any of the output signals. The number of
different transport stream outputs is limited by the licence key Output transport streams.
6.1.5 1 PPS Input
This coaxial connector is not used in the CP524.
6.1.6 Alarm/Reset
The unit is equipped with a 9-pin male DSub connector to provide alarm information.
Two programmable relays are provided. The first relay is always activated on a critical alarm or
when the unit is not powered. Please refer to section 8.4.2.3 for a description of how to program
the relays.
The pin out of the connector is shown in table 6.2.
Table 6.2 Alarm/Reset
connector pin out
Pin Function
1. Relay 2 - Closed on alarm (NC)
2. Relay 2 Common
3. Relay 2 - Open on alarm (NO)
4. Prepared for +5V Output
5. Ground
6. Alarm Relay - Closed on alarm (NC)
7. Alarm Relay Common
8. Alarm Relay - Open on alarm (NO)
9. Optional Reset Input / GPI
When there is a critical (level 6) alarm in the unit, unit is not powered or any other programmed
condition for relay 1 is satisfied, there will be a connection between pin 6 and pin 7. When the
above conditions are not present, there will be a connection between pin 7 and pin 8.
The optional (additional) relay will follow the same behaviour, except that it can also be programmed not to be activated for a critical (level 6) alarm.
A connection between pin 9 and 5 (or a TTL low on pin 9) will hold the unit in reset if this
function has been enabled. The connection must be held for 0.5 seconds in order to active the
reset. This can be used to force a hard reset of the unit from an external control system. This
pin can also be used as a general purpose input (GPI).
For more details regarding the alarm relay, please refer to Appendix on Technical Specifications
B.
6.1.7 Electrical Ethernet data ports
The CP524 comes with two Ethernet data ports. These data ports can be used to carry MPEG
transports streams if the licence key Ethernet data interface is installed.
These ports can also be used for management of the device.
6.1.8 Ethernet management port
The CP524 provides one Ethernet port for control and management. Connect the management
port to the management network. The LEDs for the management port are used as follows:
Table 6.3 Ethernet management port LEDs
LED indicator Location DescriptionColour
SpeedLeftUnlit = 10 Mbit/s, Lit = 100 Mbit/s Green
Traffic and link RightLit=Link, Blink=data tx or rxGreen
6.1.9 The SFP module
The SFP module (SFP = small form-factor pluggable) is a third-party product providing an extra,
optional interface to the CP524. Depending on the module type it may act as a direct bridge
to E3 and T3 telecom network lines using coaxial cable, or provide a high-speed STM-1/OC-3
optical interface employing single or multi-mode optical fibre.
Figure 6.2 A
typical SFP module
An SFP module may be configurable or non-configurable. Using a configurable SFP module the
parameters relevant to its operation are controlled through the CP524 WEB interface. Control
information is passed to and from the SFP module using the I2C protocol.
A wider range of settings are available using the SFP module internal WEB server. To access the
internal WEB server an SFP configuration adapter is required. For further information on this,
and for detailed technical specifications, refer to the vendor’s manual for the specific device.
The CP524 provides a slot to accommodate an SFP module. Access to the SFP interface is
possible if the SFP software is installed and the feature key has been licensed (see section
Section 8.4.8).
The SFP interface must be expressly enabled from the CP524 user interface (Device Info >
Maintenance > General) by selecting SFP from the Electrical/SFP dropdown menu and hitting
Apply
After rebooting, the user interface will reflect the presence of the SFP network interface. This is
managed the same way as other network interfaces, but with an extra WEB page tab to support
SFP specific functionality.
Note that when using the SFP slot, the "DATA 2" Electrical Ethernet port is automatically turned
off.
6.1.10 Serial USB interface
USB interface:
• USB 1.1
• Mini USB connector
The USB interface requires a special COM port driver on the PC that shall communicate with
the device. This driver is provided on the product CD shipped with the device. The USB
interface is intended for initial IP address setup.
6.1.11 Power Supply
Section
instructions, prior to connecting the units power cable.
4.5 provides details of the power supply, protective earth and security. Read all these
6.1.12 Technical Earth
Connect the Technical earth to a suitable earth point.
The CP524 is configured and controlled locally and remotely through a Flash-based Web interface. The only application required on the computer to use this interface is a Web browser and
the Adobe Flash Player.
Note: Adobe Flash Player 9.0 or newer is required to use the Web interface
of the CP524. As a general rule it is recommended to always use the latest
official release of Flash Player (version 10 or newer). If the Flash Player is
not installed on the adminstrator PC, a copy is provided on the CD delivered with
the device. Alternatively, the latest Adobe Flash Player can be downloaded free of
charge from
http://www.adobe.com.
Note: When using Microsoft Internet Explorer, version 6.0 or higher is
required. It is however recommended to upgrade to version 8.0 or newer
for best performance.
7.1 Accessing the graphical user interface
The default IP address of the CP524 will most probably not be suitable for the network where the
unit will operate. Initially therefore, the user should change the IP address of the management
interface so that access may be gained from the network.
The CP524 offers two options to alter the user interface IP address; through an Ethernet connection or using a USB terminal interface. If your management computer allows setting a fixed
IP address, change the IP address using the Ethernet option described in Section 7.3.1.
If a static address cannot be configured on your management computer, Section 7.3.2 gives the
procedure to initially configure device network parameters (IP, netmask, etc...) using the USB
terminal interface.
Configuring the device functionality according to operational needs is done using the Web
interface, see Chapter 8.
7.2 Password protection
Remote access to the device is controlled by password protection. If you access the CP524 using
the USB terminal interface a password is not required.
There are 3 user levels providing different user privileges, each with a separate default password:
Username Default password Privileges
adminsalvadorFull access to device
operatornatalConfigure setting, cannot alter passwords
The passwords can later be changed, either from the Web GUI or via the terminal.
7.2.1 Resetting the password list
If a password is lost, the password list can be reset to factory defaults via the local USB terminal
interface. To reset the password list, type the following command in the terminal interface:
userdb factory_defaults
Note: The factory_defaults option on the userdb command is avail-
able without administrator previledges only when accessing the terminal
via the local USB interface. In remote terminal sessions with a Telnet
client, administrator privileges are required to run the same command.
7.3 Changing the IP address of the unit
The CP524 is supplied with a dedicated management Ethernet port, labeled Control. The default
IP configuration (IP address and netmask) of the port is 10.0.0.10/255.255.255.0.
7.3.1 Changing IP address via the Web GUI
Changing the default IP address using the Web interface requires that your management computer may be configured with a static IP address.
Note: Avoid connecting through a network at this stage, as this may give
unpredictable results due to possible IP address conflicts.
1. Connect an Ethernet cable directly between the PC and the Ethernet control port of the
CP524. Configure the PC to be on the same sub net as the CP524. See Figure 7.2.
2. Open your web browser and type http://10.0.0.10 in the address field of the browser.
Log into the GUI with username admin and password salvador.
3. Browse to Device Info -> Network -> Control in the GUI, and set the correct IP address
settings. Click apply to activate the new parameters. Figure 7.1 shows this GUI screen.
Note: Contact with the unit’s GUI will be lost. Please type http://<your
new IP address> in your browser to reconnect to the unit.
Windows XP example
The screen-shot in Figure 7.2 shows how to configure the network interface in Windows
XP to communicate with the CP524 with factory default settings. The IP address/netmask
Figure 7.1 Configuring network settings via the Web GUI
Figure 7.2 Setting static IP address 10.0.0.11 in Windows XP
is set to 10.0.0.11/255.255.255.0 which is on the same sub net as the CP524, and does not
conflict with the IP address of the device.
Note: If several new devices are accessed, one after another, the ARP
cache of the computer from which the devices are being accessed may
have to be flushed between each device, since the same IP address will be
used for different MAC addresses. On Windows XP this is done on the command
line typing the command ’arp -d *’
7.3.2 Changing the management port IP address via terminal interface
If a static IP address cannot be configured on your computer, follow the procedure below to
configure the IP address via the terminal interface.
1. Install the USB driver from the product CD (setup_ftdi_usb_drivers.exe). (This step may
be omitted if the driver has already been installed.)
2. Connect your computer USB port to the CP524 USB port using a suitable cable.
3. Access the terminal interface using a suitable terminal program, emulating an ANSI
terminal, on your PC (e.g. HyperTerminal). The USB will appear as a virtual COM
port on your PC. No specific serial port settings are required. Assure "scroll lock" is
not on. Type <enter> and see that you have a prompt (app>).
4. Test that the connection is successful by hitting the <Enter> key. If successfull an >app
prompt should be shown.
5. In the terminal, type the following command and press <Enter>:
This will result in the IP address 10.40.80.100 being set. The subnet mask is set to 255.255.255.0
and the default gateway to 10.40.80.1.
Note: The product CD shipped with the CP524 contains a USB driver
to use for serial communication with the device on the USB port. The
MS Windows driver installation script is configured to give a one-to-one
relationship between the physical USB port number on the PC and the COM port
number to use on the PC. Drivers retrieved from http://www.ftdichip.com will also
work, but these may not have the same COM port number mapping.
7.3.3 Configuring automatic IP address assignment
The CP524 can be configured to obtain an IP address automatically from a DHCP server on the
network. See section 7.3.1 for how to connect, and section 8.4.5.1.1.1 for how to configure this
from the GUI. Alternatively, configure it in the terminal by connecting as in 7.3.2 and issuing
the following command:
ipconfig --dhcp 1 --hostname <your_device_name>
Example:
ipconfig --dhcp 1 --hostname bonemachine-100
Replace <your_device_name> with the name to register in the DNS system for your device.
After this, it should be possible to contact the unit in a browser using the URL:
http://<your_device_name>
To disable automatic IP assignment, use the command
Note: Hostname registration is only done via the DHCP server, so if
DHCP is not enabled the hostname is not registered. The default hostname
used is on the format CP524-<serial-no>-<interface-no>
Note: If automatic IP address assignment is configured and the interface
is connected to a network that does not support DHCP, the interface will
not receive an address and will fall back to a link local address after about 1
minute, using the first available address in the range 169.254.1.0 - 169.254.254.255.
If you have a unit that has been configured with DHCP, but current network does
not support it, you should be able to connect to the device for reconfiguration on a
local network connection using the address 169.254.1.0. If more devices are using
link local addresses, try 169.254.1.1, 169.254.1.2, etc.
7.3.4 Detecting the management port IP address
If you have a unit and do not know the IP address of the Control Interface there are a few
options available. The simplest solution is connecting through the USB interface.
7.3.4.1 USB Interface
7.3.2 on how to connect to the unit using the USB Interface.
See
Type the following command to list the currently assigned IP addresses:
app>net ipconfig
7.3.4.2 Nevion Detect
If you are not able to connect through the USB Interface, you may use the Nevion Detect
software. This software may be found on the Nevion Product CD (version 2.20 and newer), or
by contacting Nevion Support (see Section 2.4). An User’s Manual is also included.
The Nevion Detect software detects devices by sending broadcast messages that the CP524
and other Nevion devices will recognize and reply to with some essential information. The PC
running Nevion Detect may be on a totally different subnet than the CP524, such that the device
will be discovered regardless of IP addresses and IP submasks.
Warning: Some Ethernet equipment might block broadcast traffic. Con-
nect your PC directly to the CP524 to avoid this.
Note: It is possible to avoid that the CP524 is detected by the Nevion
Detect software. See Section 8.4.5.1.1 for details on how to do this.
The CP524 is entirely controlled through a WEB interface using the web browser’s Flash plugin.
After log-in the main status page appears displaying an overall view of the device functionality
and status. It also displays a number of tabs giving access to all functional controls of the
device.
This chapter goes through the different GUI pages used to control the CP524 and get status
information.
8.1 Login
Access the CP524 by entering its IP address in the address field of your favourite browser. When
accessing the CP524 the first time, the progress bar (Figure 8.1) should appear while the Flash
application is loading from the device.
Figure 8.1 Flash application loading
When the loading of the Flash application is finished, the login window (see Figure 8.2) is displayed. Type the username and password to enter the GUI application. The default passwords
are listed in Section 7.2.
Figure 8.2 GUI login window
The login dialogue has an option “Save password”, which makes the browser store the username
and password in a cookie and use them as default values at next login.
After successful login the start page is shown. The top part of the page (shown in
is called the status header.
Figure 8.3 The status header
In the status header the product name is shown on the left hand side, along with the Nevion
logo.
The status bar displays an indicator showing the overall alarm status of the device. The colour
of the indicator shows the highest level alarm currently active in the unit. It is green if no alarm
is active. Other possible colours are described in Appendix E.
Several items are presented in the right corner/section of the header. Starting from the left:
• The user defined device name, if entered.
• A button to log out from the GUI.
• A button to switch current user level.
• A text showing the current user name.
• The local device time.
• A button for minimising the header. Using this hides a lot of the header information
and gives more space for the rest of the page.
Figure 8.3)
• An activity indicator.
Note: The activity indicator shows one box for each request being
processed by the unit. Each box may change from green to red if ex-
cessive time elapses during the processing. During normal operation, no
squares should turn red. If squares start turning red there might be a problem with
the communication between the device and the computer, or the device may be
busy. If the device has not responded to a request within 20 seconds, the indicator
turns yellow. If no response has been received after 40 seconds, it turns red.
A tab bar is located beneath the status header. The exact number of tabs and tab labelling
depends on the units operational mode and licences. Clicking a tab will open the corresponding
page with a navigation pane to the left as shown in Figure 8.4. This pane is used to navigate
between sub-pages of the tab.
Note: The navigator can be collapsed to economise on screen space. Click
the vertical grey line with two small arrows to the left of the navigator.
8.3 Status
The status page presents an overview of the device operational status as well as a log of alarm
events.
There are two sub-pages within the status page.
Current Status
Indicates the running status of the device.
Alarm Log
Presents the device alarm log and provides operations for clearing the log or exporting it
as a comma separated value file (.CSV).
8.3.1 Current Status
Figure 8.5 Current status
This page displays the current status of the device. It consists of a block diagram illustrating the
device with its input and output ports, an overview of the currently active network interfaces
and a list of currently active alarms.
Block Diagram
The block diagram provides a compact view of the unit status. It shows:
• The name of the functional units of the device.
• The name and alarm status of each input/output port.
The alarm status is shown with colours indicating the severity of the alarm. The various
severities and colours used are described in Appendix E.
Access to additional information pertaining to the various ports of the block diagram is
provided by hovering the mouse pointer over the port within the diagram. The port
representations in the diagram also act as shortcuts to the corresponding configuration
page for the port. The shortcut is activated by clicking on the port in the diagram.
If an input switch is defined, it is shown in the status diagram as a box inside the device
block in front of a MUX block. The block shows the ports that are members of the switching
group, and the currently selected port. Clicking the switch block will take you to the
configuration page for the switch.
Right-clicking the status block diagram top bar offers a shortcut to clear device statistics
parameters. Selecting Reset device statistics brings up a dialogue where you can select which
information to clear.
Current Alarms
The bottom part of the page shows the currently active alarms. Some alarms may contain
several sub-entries that are displayed by clicking on the arrow in front of the entry’s
description. The severity of each alarm is represented by an error indicator (visually
similar to a LED). The colour of the indicator represents the severity level configured for
the specified alarm. The various severities and colours used are described in Appendix
E.
The Current Alarms table contains six columns:
Description
Description of the alarm condition.
For sub-entries, the extended index is shown in brackets. To the left is an indicator visualising the severity of the alarm. The indicator has a tool-tip providing a textual description
of the alarm severity.
On Time
The time when the alarm was raised.
Alarm type
Category of the alarm, i.e. Port, System, Switch etc.
Source
This identifies the source of the alarm. For port alarms, this is a reference to the specific
port raising the alarm. This field has a tool-tip showing the subid1 and subid2 values for
the alarm.
Subid1
Reserved for future use in multi-slot chassis and is always set to 1 in the CP524.
Subid2
The device or port to which the alarm relates. The value is zero for alarms that are
related to the device rather than to a specific port. Values of 1 and up reference
specific ports.
Alarm ID
Each alarm condition has an associated numerical alarm ID.
Details
An optional string to provide more alarm information in human readable form. The format
of this string depends on the alarm type. Hovering the mouse over this field produces a
tool-tip displaying the full text.
A detailed overview of alarm conditions is given in Appendix E.
8.3.2 Alarm log
Figure 8.6 Alarm log
The alarm log shows every alarm that has been triggered since the last time the alarm log was
cleared.
The table consists of the same columns as the Current Alarms table, but does not show details
by default. You can change which columns to show, including the details column, in Section
8.4.2.4. Additionally a column named Off Time shows the time the alarm condition was cleared.
Rows will not have the Off Time set if the alarm is still active.
Each row provides additional information via a tool-tip shown when hovering the cursor over
the row. The tool-tip entries are:
Sequence #
A number identifying this specific alarm instance. This number is incremented each time
an alarm condition is raised.
SubID 1
The primary numerical index of the alarm instance. This index is reserved for future use
and is always set to 1 in the CP524.
SubID 2
The secondary numerical index of the alarm instance. When the alarm is of type Port
alarm this index contains the port number for which the alarm was raised. Other types of
alarms may use this index to identify a sub module, but normally it is set to 0.
SubID 3
The tertiary numerical index of the alarm instance. The use of SubID 3 depends on the
type of alarm. Some of the Port type alarms use this index to signal the PID value or
Service ID for which the alarm was raised. For example, if the CC Error of a PID is raised
then the PID value is given by SubID 3.
Details
An optional string providing more information about the alarm in human readable form.
The content and format of this string depends on the alarm type.
Beneath the alarm table is a caption showing the total count of alarms currently stored in the
alarm log.
To the right of the table are three buttons and a check box.
Clear Alarm Log
Clears all alarms from the alarm log.
Export to File
Saves the alarm log to a comma-separated value (.CSV) file. The button opens a file
dialogue where the user can choose the destination to save the file on the computer.
Export to Browser
Opens the complete log in a new browser window, showing the alarm log as a commaseparated value list. The format of this list is a text file (not HTML or XML).
Enable updates
This check box can be unchecked to stop the log from scrolling if new alarms are triggered
while watching the log.
The alarm log is stored in non-volatile memory, so the content is kept even if the unit is rebooted.
The log is circular. Events occurring after the maximum number of entries has been reached
overwrite the oldest entries in the log. The maximum number of stored entries is 10000.
8.4 Device Info
The device info page contains all the information and settings that are not related to a single
input or output port. It is divided into multiple sub pages accessed via the navigation list to
the left. In the list of physical interfaces in the navigation list, the currently active interface is
shown in bold. See Figure 8.7.
The exact layout of the navigator depends on the resources and features currently available in
the device.
The product info page contains general device information.
Figure 8.8 Product Information
Name
Configures the current user defined name of the unit. This parameter, together with the
management network parameters are used as device identifiers and remain untouched if
the unit configuration is changed by loading a different configuration file. See Section
8.4.7. The device name is shown in the web GUI status header (see Section 8.3.1), and in
the web browser title bar to facilitate identification of each device.
Inventory ID
Configures the current user defined inventory ID of the unit. This parameter, together with
the management network parameters are used as device identifiers and remain untouched
if the unit configuration is modified. It is only intended as a label/tag and will not affect
the operation of the unit.
Configuration ID
Configure a user defined name for the current configuration of the unit. This name will, if
given, be diplayed in brackets after the unit name in the status header as shown in Figure
8.3. The Configuration ID does not, as opposed to the Name and Inventory ID fields, remain
untouched when loading a new unit configuration. Loading a new unit configuration will
change the Configuration ID. See Section 8.4.7 on how to load a new configuration.
Product name
Displays the name of the product as designated by Nevion.
Serial number
The serial number of the device.
Software version
The version of the software currently installed on the device. The software version is given
by the following syntax:
<major_version>.<minor_version>.<patch_version>
The convention for the SW version numbering is as follows:
major_version
Incremented for significant SW changes.
minor_version
Incremented for minor changes. The minor version number is even for official retail
releases and odd for beta releases.
patch_version
If minor_version is even, patch_version gives the patch level of that version. A patch
level of zero means the SW is built on the latest code base, an even patch_version
means this is a released SW patch on a previous release. An odd patch_version means
that this is a test version. If minor is odd, this is a beta version, and the patch_version
simply gives the build number.
Software build time
Reports the time of which the current release image was built.
Device up time
The amount of time that has passed since the device was last reset.
Internal temperature
This shows the current internal temperature of the unit in degrees Celsius and Fahrenheit.
Fan speed
This bar chart shows the current speed of the device fans relative to full speed.
Flash Power LED button
The Flash Power LED button activates flashing the green power LED on the device in
question. This is useful for identifying which device is currently being configured. Each
click of the button extends the blinking period by five seconds up to a maximum of about
30 seconds of blinking.
8.4.2 Alarms
The Alarms page is shown in Figure 8.9:
Figure 8.9 Alarm configuration
This page displays the status of all system alarms and allows the user to program the severity
of these alarms. Global alarm configuration is performed on this page, as well as alarm relay
configuration and alarm log configuration.
It gives access to the following sub pages:
• Device Alarms
• Global configuration
• Relay and LED configuration
• Alarm Log Settings
8.4.2.1 Device alarms
The page shown in Figure 8.9 provides the administrator with an interface to view the status
and configure the behaviour of all alarms related to the system. At the top the Reset Alarm
Counters button allows resetting all alarm counters simultaneously.
The page is divided into two parts. On the left is a tree that shows all the alarms. The colour
of the folder icon and the specific indicator represents the current status of the alarm. The text
to the right of the tree shows the currently configured severity of the alarm.
The right hand side of the page displays the Alarm Details field when an alarm is selected:
Alarm ID
The internal numerical ID of the selected alarm.
Alarm
Title of the alarm.
Description
Brief description of the condition of the alarm.
Severity
A configurable option defining the severity of the alarm. Options in the pull-down box
range between Filtered (meaning ignored) to Critical. The text in brackets represents the
default setting.
Alarm turned on
The number of times the alarm has transitioned from off to on since last reset of the alarm
counter.
Error count
Not used.
’Reset Counters’ button
When clicked, clears the alarm counters for the current alarm.
The right-click context menu of the device alarm page provides an option to reset the counters
of all the alarms in the Device Info tree.
This page provides an interface to configure globally the behaviour of all alarms. By default
ports use the global configuration settings but each port alarm can be configured individually
to override these settings.
For each alarm a custom severity level can be configured. In addition the alarms can be omitted
from the alarm log and trap transmission.
Edited rows are highlighted until changes have been applied.
Tip: For the Log and Send Trap columns, you can quickly select/deselect
all items by right-clicking on the header fields in the columns.
8.4.2.3 Relays and LED
This page lets the user configure the alarm severity level that shall turn the relays and alarm LED
on. The behaviour of Alarm relay 1 and Alarm relay 2, and the Alarm LED may be configured
individually for each alarm severity level. Note that the Alarm relay 1 and the Alarm LED will
always be enabled for alarm severity level Critical, as indicated by the disabled check boxes in
the Relay and LED level triggers field. The current state of the relays and LED is indicated
inside the associated brackets.
Figure 8.11 Relays and LED configuration
For further details on the physical relays refer to Section B.5.1.
The Virtual Relays field shown in Figure 8.11 also includes settings for the so-called virtualrelays. These are programmable status indicators that can be set to react to any specific alarm
condition. In the simplest case you may want to enable a relay in case a specific alarm ID turns
up. In another case you may want to enable a relay if a specific alarm turns up on a given port.
Each relay status are exported on SNMP. Activation of a virtual relay also generates a specific
alarm, named "Virtual alarm relay activated" (ID=169).
The key element in the settings of the virtual relays is the Expression value. The expression is
very close to SQL in syntax and specifies when the relay should be activated. The behaviour is
as follows for each virtual relay:
1. Each active alarm event is evaluated against the Expression for the virtual relay (if
enabled).
2. If the expression evaluates to true, the Count value is increased by 1. You can at any
time see the current count value. The Count value simply tells you how many of the
current (active) alarm events in the unit that matches the expression.
3. If the count value is larger than or equal (>=) to the Count Thresh. value the relay is
activated.
The expressions are validated before they are accepted by the unit. Table 8.1 shows the field
values you may enter in an expression.
Table 8.1 Legal field values to use in expressions
Field name Extracts from event: TypeSample expression
In the expressions you may enter parentheses to group sub-expressions together. Together with
the supported list of operators this gives great flexibility in constructing advanced “match”
patterns.
Table 8.2 summarises the operator types you are allowed to use. Please note that the examples
below are used for illustration purposes only. For example, the plus and minus operators may
not be very useful in practise, but they are included in this table for completeness.
INSet operator. Returns true if left-hand part is included in set to the right. id IN (169,200,201)
+Additionid + 9 = 169
-Subtractionid - 8 = 160
*Multiplyid * 10 = 100
/Divideid / 20 = 8
>Greater thanid > 100
<Less thanid < 90
>=Greater than or equalid >= 100
<=Less than or equalid <= 100
Some examples are given in Table 8.3.
Table 8.3 Expression examples
TaskExpressionCount threshold value
To generate an alarm when any alarm with
ID = 200 turns up (independent on source)
To generate an alarm when alarm with ID =
200 turns up on port with ID = 1 (subid2 =
1)
To generate an alarm when alarm with ID =
200 turns up on both port 1 AND port 2
id = 2001
(id = 200) AND (port = 1)1
(id = 200) AND ((port = 1) OR (port
= 2))
2
Note the last example in the table: Here the count threshold value must be set to 2 to get the
expected behaviour. This is because the expression entered matches two different alarm events
(port=1 or port=2), and in order to match them both two matches are required in the global
alarm list.
8.4.2.4 Alarm log settings
This page is used to set alarm log properties.
Log delimiter
This parameter is used when exporting the alarm log. It specifies the column separator
character. The default value for the delimiter is ;. The character used may affect autoimporting of the exported file into your favourite tool used to inspect the file content.
Each of the columns in the alarm log table has a checkbox. Columns that are selected are
shown on the alarm log page.
8.4.3 Port Mappings
This page offers an interface to configure the direction of the installed ASI ports. The valid
options are visible as selectable radio buttons for each port.
The number of ports shown in the port map grid corresponds to the number of physical connectors installed in the chassis and the meaning of the different choices are:
Mode
Direction of the port, with two choices:
Input
Use the port as an ASI input to the multiplexer. All input ports can be used, but the
number of inputs that can be enabled simultaneously is limited by the licence key
Number of input ports activated.
Output-Copy
Use the port as an ASI output, transmitting the multiplex generated by the unit.
The valid selections are also documented in
Section 6.1.2.
Format
Additional option for output ports, only available in ATSC+DVB mode. This option makes
it possible to transmit both ASI and SMPTE 310M simultaneousy, the ports carrying the
same content.
ASI/310M
The format on the output port follows the format configured on the TS-OUT port.
ASI
The port is always using ASI, even when the TS-OUT is configured to SMPTE 310M.
Configure the mapping that best matches your needs and press apply to activate the new matrix.
Re-configuration does not require re-booting. The choices made will be reflected in the logical
block diagram of the device on the status screen (see also Section 8.3.1)
Note: The port map settings are tagged to follow the device (see Section
5.6.2, and even though the parameters are exported in the configuration
file format, they are not overwritten when loading a configuration file via
the GUI to another device.
8.4.4 Time Settings
Figure 8.14 Time Settings
The time settings page lets the user configure time zone, the source for synchronising the internal
device time clock and set the internal clock in case of failure of all external sources of clock
synchronisation. The main use of the device time is stamping the entries of the alarm log.
The page consists of four main parts. Top left is the General box, containing the following
parameters:
Drop-down list to configure the time zone of the unit.
Status
The status of the time synchroniser.
Active
The time source currently in use by the time synchroniser.
The Manual Adjust Time field allows the operator to set the time. The manually configured
time will only be used when no other time sources are configured in the Prioritised time sources
list.
The Timesource prioritisation field contains two lists showing configured time sources. Disabled
time sources are greyed out. Enabled time sources are shown with an indication of the time
source status. The list to the right shows time sources that are defined but not used by the
time synchroniser. Enabled time sources may be moved to the leftmost list by using the arrowleft button, and back again by using the arrow-right button. Time sources in the left hand
list are used by the time synchroniser to set the time. They are listed in prioritised order; the
source with the highest priority at the top. The order of priority can be altered by clicking an
item in the list and using the up or down arrows to the left of the list to increase or decrease,
respectively, the item priority. The time synchroniser will use the time source with the highest
priority whose status is “OK” (represented by a green indicator).
Figure 8.15 Time Settings - Add time source
To add a time source to the system, click the “Add Timesource” button, which brings up the
dialog shown in Figure 8.15 with the following fields:
Time source retrieving time from DVB TDT, DVT TOT or ATSC STT time tables on a
port.
Input source
Lists ports that can be used as time sources with the selected time source type
(Figure 8.15. Multiple entries can be selected to add more than one time source.
For switched inputs, you may select the time source to get time from the input switch group, which will make the time source retrieve the time from the
currently active input in the switch.
To remove time sources, Select them in the list and click the “Remove Timesource” button. Time
sources for dynamic ports such as IP inputs and Switch inputs, are automatically removed if
the dynamic port is removed.
Located below the lists is also a field to define the maximum allowed time interval between
updates from the currently used time source. Exeeding this interval the source is considered
“Not OK” and the synchroniser selects the next source in the prioritised list.
Upon selecting a time source, the Timesource Details box at the bottom right of the page provides
additional details relating to the selected time source. Depending on the type of time source
selected the box may contain some or all of the following parameters:
Active
A checkbox to enable or disable the time source. Disabled time sources are never updated.
Time sources configured and present in the prioritised list must be removed before they
can be disabled.
IP address
Specifies the IP address of an SNTP time server source to poll for updates.
Type
Type of time source selected. The sources are product dependent, but SNTP is always
available.
Last updated time
The most recent time value received from the time source.
State
The current state of the time source.
Reference
Provides the time reference source address of accessed time source.
Reference stratum
Indicates the hierarchy level of the current time source. The master reference is at stratum
0 (highest).
Indicates if the time source is currently governed by a time source at a higher stratum.
Reference precision
The expected timing accuracy of the current time source.
8.4.5 Network
Figure 8.16 Network status
This page presents status information about network interfaces, including virtual (VLAN) interfaces, present on the device. The management interface is always present, and bold characters
indicate the web management interface connection. An interface shown in grey colour means
that the interface is disabled. There may be physical interfaces on the unit that are not shown
in this table as the availability of each interface may vary with the installed software licences
and operational mode.
Interface
A label identifying the interface. If it is a physical interface with virtual interfaces attached to it an arrow is shown. Clicking this arrow will expand/collapse the list of virtual
interfaces.
IP Address
The IP address configured for this interface.
Link Speed
The current link speed detected for this interface. Applicable to physical interfaces only.
Duplex Mode
The duplex mode detected for this interface, half or full duplex. Applicable to physical
interfaces only.
TX Bitrate
The bitrate currently transmitted through this interface. Applicable to physical interfaces
only.
The bitrate currently received through this interface. Applicable to physical interfaces
only.
Enabled
Shows whether the interface is currently enabled.
Data
Shows whether data traffic is currently enabled for this interface.
Management
Shows whether management traffic is currently enabled for this interface.
8.4.5.1 Interfaces
Each available network interface has an entry in the Navigator list. Selecting an interface brings
up pages where it is possible to configure the interface and view its status. Accessible parameters vary with the interface selected since the functionality of the available interfaces are not
necessarily identical.
8.4.5.1.1 Main
Figure 8.17 Main IP settings
This page provides the main configuration settings for the physical interface.
Caution: Modifying the settings of the interface you are currently using
for the GUI application may cause loss of contact with the unit. Make sure
you will still be able to contact the unit before applying changed settings.
Enables/disables the interface. It is not possible to disable the currently used management
interface.
Media Select
Provides a choice between network port Data 2 and the SFP module for the second data
interface. Select RJ-45 to use the data port marked Data for data traffic. Select SFP to use
the SFP module for data traffic.
Speed/duplex mode
The speed and duplex mode of the interface. The Auto setting enables automatic speed
and mode negotiation for the Ethernet link. This option is not available for SFP interfaces.
Note: Modifying the default settings of interface duplex to anything other
than auto can cause unpredictable results unless all peer systems accessing
the port use similar settings. For more technical information regarding auto
negotiation and duplex mismatch, refer to the Wikipedia duplex mismatch article
(http://en.wikipedia.org/wiki/Duplex_mismatch).
Automatic IP address
Enables automatic IP address assignment using DHCP. This option requires that a DHCP
server is present on the network on which the device is connected.
8.4.5.1.3 DHCP Settings
Hostname
The DNS hostname of the interface. This name is sent to the DHCP server with a request
to register it at the DNS server. If the name registers correctly, the fully qualified domain
name of the interface will be the hostname pluss the domain name assigned by the server.
Domain
Optional field where wanted domain name can be specified. Normally the DHCP decides
the domain name for a client, the DHCP server must be set up specifially to allow a client
to select a domain name.
Renew button
Press button to renew address now. Renew is done by sending a request for renewal of
lease of existing parameters, using uni-cast to DHCP server.
Rebind button
Press to rebind address. Rebind is done by broadcasting a request for the same IP address
as previously used.
Shows the current state of the DHCP client (RFC2131, Figure 5).
Possible values are:
Disabled
DHCP is not turned on.
Selecting
Client is broadcasting Discover messages and checking for offers from answering
DHCP servers. Normally the client should immediately receive and answer and
switch to bound state.
Bound
Client has received IP settings and is ready for use.
Renewing
Client is uni-casting request to leasing server to renew previous lease.
Rebinding
Client is broadcasting requests to re-bind to previously assigned address.
Checking
Client is evaluating wether offered IP address is already in use on network.
Backing off
Client received a nack from the server.
DHCP server
The IP of the selected server.
IP address
The IP address assigned to this interface by the server.
Subnet mask
The subnet mask assigned to this interface by the server.
Gateway
The IP address of the gateway to use, assigned by the DHCP server.
DNS servers
Prioritized list of DNS servers to use assigned by the DHCP server. See chapter Section
8.4.5.2 for manual configuration of DNS server addresses.
Note: If the DNS server is not located on a sub-net local to the unit, it
may be required to configure the routing table to route DNS requests to
the correct network interface.
These two boxes enable read and write attributes of the Nevion Detect IP assignment server
module. This server is a stand-alone PC application that can be used to discover Nevion
devices on a local network and assign IP addresses to them.
Enabling the Read option makes the CP524 visible for the Nevion Detect on the LAN. If the
Write option is enabled the IP address of the CP524 may be configured using the Nevion
Detect. These options do not affect the operation of the device from the management
application Nevion Connect.
8.4.5.1.8 Alarms
Alarms related to the interface are listed on the Alarms page. Clicking an alarm opens the field
to configure the alarm. Please see Section 8.4.2 for alarm configuration details.
Figure 8.18 Network interface alarms
At the top of the page two radio buttons are provided to select between displaying error count
or error severity. In addition all alarm counters related to this interface may be reset.
8.4.5.1.9 Advanced
This sub-tab allows configuring advanced IP settings of the interface.
Figure 8.19 Advanced IP settings
Allow ping response
Check this box to filter incoming ICMP messages. If this option is not enabled the device
will not answer ping requests to this port.
Tick this box to allow management traffic on this interface. It is not possible to disable this on
the dedicated management interface or on the interface you are currently using for management.
Allow data traffic
Tick this box to allow data traffic on this interface. It is not possible to enable data traffic on
the management interface.
Multicast router
This parameter is not shown in the management interface page.
The IP address of the multicast router. The address here is used in conjunction with the
Use multicast router option in the "IP Output" page,
Section 8.6.4.1.
IGMP version
This parameter is not shown in the management interface page.
The preferred IGMP version to use. If fixed is selected the unit will keep trying to use the
selected version even if it is not supported by the network.
8.4.5.1.10 Status
Figure 8.20 Interface Status
This page shows detailed status and error information on the selected physical interface. Different types of interfaces support different status and error parameters; not all parameters listed
will be shown for all interface types.
The detected current duplex mode of the interface. The duplex mode indicates whether
data may flow in one direction (half duplex) or bidirectionally (full duplex).
The following parameters are available for both received and transmitted packets:
bitrate
The total bitrate received/transmitted.
load
Interface load, measured relative to max speed.
Total packets
The total number of IP packets received/transmitted.
Good packets
The number of IP packets received/transmitted containing valid CRCs.
Multicast packets
The number of IP multicast packets received/transmitted by the interface.
Broadcast packets
The number of broadcast packets received/transmitted.
Octets
The number of octets received/transmitted
The Errors field:
CRC errors
Number of packets received with CRC errors.
Alignment errors
Number of packets detected with alignment errors (non-integer number of bytes).
Receive errors
Number of erroneous packets received.
Missed packets
Number of packets missed.
Link symbol errors
Number of link symbol errors detected.
Carrier extension errors
Number of carrier extension errors detected.
Receive length errors
Number of packets with invalid size.
The SFP Info field is only shown if the SFP interface is active. It displays information provided
by the SFP module installed.
This page is only shown on interfaces with VLAN (virtual interface) support. The page allows
adding, removing and editing virtual interfaces (VLAN) using the selected physical interface.
Current VLANs interfaces are shown in the grid on the left, and parameters for each interface
are edited by selecting the interface in the grid first.
Once editing is finished, clicking the Apply button will commit all the changes. Hitting Refresh
will cancel all changes.
In addition to the Apply and Refresh buttons there are buttons to enable adding and removing
VLANs.
8.4.5.1.12 Main Settings
Enable interface
Enable/disable the virtual interface.
VLAN ID
The VLAN id of this virtual interface. Must be in the range 1-4094. All virtual interfaces
on one physical interface must have a unique id.
VLAN priority
The VLAN priority of this virtual interface. Numers 0 to 7 are valid. For further information on VLAN priority usage, see reference
[7].
Automatic IP address
Enables automatic IP address assignment using DHCP. This option requires that a DHCP
server is present on the network on which the device is connected.
The gateway address to use for the virtual interface.
8.4.5.1.14 Advanced Settings
Enable data traffic
Checked box enables the virtual interface to allow video data traffic. Not shown for dedicated management interface.
Enable management traffic
Checked box enables the virtual interface to allow management traffic.
Enable ping
Checked box enables the virtual interface to respond to ping messages.
Multicast router
The multicast router for this virtual interface. Only visible if multicast is allowed.
IGMP ver
Provides selection of the IGMP version to use. Not applicable to the "Control" interface.
8.4.5.1.15 DHCP settings and status
Please refer to Section 8.4.5.1.1.2 and Section 8.4.5.1.1.3 for a description of the parameters
related to DHCP, which are identical to the ones on the main tab.
8.4.5.1.16 SFP
The SFP tab is visible for the second network interface if this interface is set to use SFP. How
to enable the SFP is described in section 8.4.8.1 , provided the appropriate licence has been
installed .
The SFP tab gives access to three sub-pages: SFP Status, STM-1/OC-3 Config and E3/T3
Config. The two configuration sub-pages reflect that separate configuration files are used to
configure the different SFP module types. For each module type the CP524 stores a configuration
file that can be edited “off-line”. These pages are visible only if SFP configuration has been
licensed. The settings will not be committed to the module until writing of the file is expressly
initiated.
The SFP Status page, shown in figure Figure 8.23, provides an overview of the module status.
The appearance of the status page and the range of parameters shown depend on the type of
module attached.
Figure 8.23 The SFP status page
The Module General Status field displays the status of the module as seen by the CP524.
SFP Present
Indicates that the module has been detected by the CP524.
The type of transceiver inside the SFP module. Only a limited range of transceivers is
compatible with the CP524.
Connector type
Indicates the network connector type.
Serial number
The serial number of the SFP module.
The Module <type> Configuration field shows the internal functional status as read back from
the module. The field heading will reflect whether a STM-1/OC-3 or an E3/T3 module is
installed. A discussion of the parameters shown is included in the Config pages description.
The Module (type) Alarms field is shown if the STM-1/OC-3 module is present and shows all
link related alarms settings of the module. Red indicates that the alarm has been raised.
Refer to product specific documentation for further discussion of these parameters.
The Module (type) Link Status field is shown if the E3/T3 module is present and shows the
status of all link related alarm settings of the module. Red indicates that the alarm has been
raised.
BV
Bipolar Violation
LCV
Line Coding Violation
LOS
Loss of Signal
RDI
Remote Detection Indication
WLD
WAN Loop Detected
EZ
Excessive Zeroes
PCV
P-bit Coding Violation
OOF
Out of Frame
LLD
Lan Loop Detected
LOL
LIU Out of Lock
CCV
C-bit Coding Violation
AIS
Alarm Indication Signal
SS
System Status.
Refer to product specific documentation for further discussion of these parameters.
The Module (type) Error Counters field displays errors as they occur, counted during a 15
minute period. Es = Errored seconds, Ses = Severely errored seconds, Cv = Coding violations,
Uas = Line unavailable seconds
Current
The counter increments every time an error is detected, resetting every second.
Displays the result of the previous 15 minutes counting interval.
Section
“Section” related error counts
Line
“Line” related error counts
Path
“Path” related error counts
At the page bottom is the Clear Module Statistics button. Clicking this will flush all error
counters.
The STM-1/OC-3 Config page.
The STM-1/OC-3 module provides an optical interface for high speed data communications in
SDH or SONET networks. This page provides access to change the configuration settings of
the module. As shown in figure
parameters. The Alarms and Error counters fields are identical to those described for the SFP
Figure 8.24 the page contains four fields to set operational
Status sub-page. Editing the configuration settings will alter the SFP configuration file stored
in the CP524, only.
Figure 8.24 The configuration page
for the STM-1/OC-3 SFP module
In the General field the main operational parameters are set.
Indicates if the module has been detected by the CP524.
Write to module
This box must be checked to allow the configuration file be written to the SFP module.
If the box is not checked the configuration file may still be edited without affecting the
module. If the box is checked the configuration file is written to the module every time
the Apply button is clicked.
Tx clock source
The transmitter clock may be internally generated, or derived from the received data
stream.
Frame type
Select SDH or SONET, respectively, according to the accessed network.
Payload FCS (Frame check sequence)
Check this box to enable FCS error detection.
Disable interface
Not available.
Scrambler
Tick this box to enable the module internal scrambler. Must be ticked to successfully
receive scrambled network data.
Ethernet flow control
A tick enables flow control of Ethernet data from the CP524 to the SFP module. Flow
control prevents data overflow in the SFP module buffer. Buffer overflow leads to data loss
that would go unnoticed until attempting to decode the data at the receiving end.
In the Fault Propagation field check boxes allow to select which network fault(s) shall cause
shut-down of the Ethernet data flow:
LOS
Loss of signal
AIS
Alarm indication signal
RDI_P
Remote defect indication
In the Thresholds field bit error rate measurements indicate an estimate of the network link
quality. The check boxes allow selection of pre-defined threshold BER values to raise alarms.
For further details refer to the vendor SFP user manual.
The Taffic Queues field allows mapping of network traffic queues to VLAN priorities. For
information on VLAN priority usage refer to
To aid troubleshooting while changing configuration the Module Alarm and Module Error Coun-
[7].
ters fields of the status page are replicated here.
At the bottom of the page are three buttons:
Apply
Writes changes to the SFP configuration file. Also initiates writing the configuration file to
the module if the Write to module box has been ticked.
Refresh
Cancels changes that have been entered.
Reset Factory Defaults
Only active if the Write to module box has not been ticked. Clicking this button returns
the module to factory default settings but will not affect the settings of the configuration
page. The status of the SFP module is at all times displayed in the SFP Status sub-page.
The E3/T3 Config page.
The E3T3 module provides an electrical interface for high speed data communications in E3 or
T3 networks. This page provides access to change the configuration settings of the module. As
shown in figure Figure 8.25 the page contains four fields to set operational parameters. Editing
the configuration settings will alter the SFP configuration file stored in the CP524, only.
E3/T3 present
Indicates if the module has been detected by the CP524.
Write to module
This box must be checked to allow the configuration file be written to the SFP module.
If the box is not checked the configuration file may still be edited without affecting the
module. If the box is checked the configuration file is written to the module every time
the Apply button is clicked.
Interface type
Click the appropriate button for the network used.
Module protocol
Allows selecting the desired data link protocol for the network; HDLC (High Level Data
Link Control), GFP (Generic Frame Protocol) or cHDLC (Cisco extension to HDLC).
Line type
Line protocol selection. Choices vary according to the interface type and data link protocol
selected.
The transmitter clock may be internally generated, or derived from the received data
stream.
Line code
Must be HDB3 for an E3 interface. Select between B3ZS and AMI for a T3 interface.
Line length
Only applicable for a T3 interface. Allows the output signal to be adjusted according to
the line length to reach the termination point.
FEAC
Far end alarm and control indication. Only applicable for a T3 interface using G.751 line
protocol.
VCAT overhead
Only applicable when using the GFP data link protocol. VCAT allows arbitrary grouping
of VCAT members (STS1 or STS3c timeslots) to accommodate any bandwidth.
Payload FCS (Frame check sequence)
For error detection. Only applicable when using the GFP data link protocol.
Only applicable when using the GFP data link protocol. Tick this box to enable the module
internal scrambler. Must be ticked to successfully receive scrambled network data.
GFP keep alive
If enabled, sends 2-3 keep alive messages per second. Enable this parameter if Loss of
Frame (LOF) indication is frequently encountered. Generally relevant to older equipment
types. Only applicable when using the GFP data link protocol in a T3 interface.
Ethernet flow control
A tick enables flow control of Ethernet data from the CP524 to the SFP module. Flow
control prevents data overflow in the SFP module buffer. Buffer overflow leads to data loss
that would go unnoticed until attempting to decode the data at the receiving end.
In the Fault Propagation field check boxes allow to select which TDM network fault(s) shall
cause shut-down of the ethernet data flow:
LOS
Loss of signal
AIS
Alarm indication signal
RDI
Remote defect indication
LOF
Loss of frame
FEAC
Far end alarm and control
Whether or not RDI, LOF and FEAC are applicable depends on Interface type, Module protocol
and Line type settings.
In the Loss of Signal Behaviour field check boxes allow selecting which TDM condition shall
send an LOS indication to the Ethernet interface:
LOS
Loss of signal
LOC
Receive loss of lock
AIS
Alarm indication signal
RDI
Remote defect indication
The Taffic Queues field allows mapping of network traffic queues to VLAN priorities. For
information on VLAN priority usage refer
To aid troubleshooting while changing the configuration the Module Alarm and Module Error
Counters fields of the status page are replicated here.
At the bottom of the page are three buttons:
Apply
Writes changes to the SFP configuration file. Also initiates writing the configuration file to
the module if the Write to module box has been ticked.
Refresh
Cancels changes that have been entered.
Reset Factory Defaults
Only active if the Write to module box has not been ticked. Clicking this button returns
the module to factory default settings. This will not affect the settings of the configuration
page. The status of the SFP module is at all times displayed in the SFP Status sub-page.
8.4.5.2 DNS Settings
Figure 8.26 DNS settings
The DNS settings page lets you configure a main and secondary DNS server IP address. The
DNS server is used to map names to IP addresses.
8.4.5.3 IP Routing
Figure 8.27 IP Routing
The IP Routing table lets the user configure IP routing rules for the unit. These rules tell the
unit which interface to send IP traffic to, based on the destination IP address of the traffic.
The destination IP address to use for matching against this routing rule.
Netmask
The subnet mask to use for matching against this routing rule.
Gateway
The IP destination to send a packet to if the destination address of the packet is on a
different subnet than the destination interface.
Interface
IP packets matching this rule will be sent through this interface.
Metric
The metric of the routing rule. If more than one rule matches a destination address the
rule with the lowest metric will be used.
When an IP packet is sent from the unit the destination address of the packet is matched against
the configured routing rules. If the destination address matches one or more rules the rule with
the lowest metric will be used. The packet will then be forwarded to the interface determined
by this rule. If the destination address is on a different subnet than the configured interface the
packet will be sent to the gateway determined by the rule.
Below the table is a checkbox where the user can Allow IP forwarding. If enabled incoming TCP
packets that are not addressed to the unit will be forwarded to an interface according to the
routing rules. The receiving interface must have management traffic enabled to forward TCP
traffic to a different interface.
Note: Modifying the IP routing rules may cause loss of contact with the
unit. Make sure you will still be able to contact the unit with the new
settings before applying the changes.
8.4.5.4 TXP Settings
Figure 8.28 TXP Settings
TXP is a Nevion proprietary HTTP/XML based protocol designed to retrieve configuration and
status information using WEB/HTTP requests. TXP exists side by side with an SNMP agent and
provides an alternative way to access data in a product. TXP and SNMP therefore complement
each other.
The Simple Network Management Protocol (SNMP) is used to monitor network-attached devices
for conditions that warrant administrative attention. This page gives access to SNMP settings
such as destination IP addresses of trap receivers and community string. It Also displays a log
of the latest traps sent by the unit.
The Trap Destination table lets the user configure the trap servers that should receive SNMP
traps from the unit. To add a server click the Add new button, enter an IP address, then click
the Apply button. To delete an entry select a server entry from the list and click the Delete
button.
The Settings group of parameters configures MIB-2 parameters and SNMP password protection.
The SNMP version to use for traps, version 1 or version 2, may be selected. When selecting to
transmit SNMPv2 traps, two additional options are applicable.
Status change traps
Selecting this causes a trap to be transmitted each time the overall device status changes.
The ping tool can be used to check for connectivity between devices. It is especially useful to
ping the receiving data port from the IP transmitter to see if the receiver can be reached.
Figure 8.30 The Ping tool
IP destination
The IP address of the receiving data port. The ping messages will be routed to the matching
Ethernet port, either data or management, or to the port configured as default management
interface if the specified IP address does not match either of the two sub-nets. Note that
if you are pinging between data interfaces, the Allow ping response option on the network
page Advanced tab (see Section 8.4.5.1.3) must be enabled both in the transmitter and the
receiver.
Note: When the IP destination is a multicast address one cannot expect to
receive a response to a ping request. It is recommended to test connectivity
using the device’s actual IP address.
TTL (Time To Live)
Enter the time to live value for the ping messages here. The time to live value is a field in
the IP protocol header that is decremented once for each router that the datagram passes.
When the count reaches 0, the datagram is discarded. You can use this to check the
number of routers between the transmitter and the receiver by starting with a low value
and increment it until ping responses are received. TTL is also specified for each data
channel on the IP transmitter, and must be high enough to reach the receiver. Values range
from 1 to 255.
Ping count
The number of ping messages to send. The messages are transmitted with an interval of
about 1 second.
MTU
Maximum Transfer Unit. Specify a length for the ICMP frames to check that frames with
given length pass through the network. The ICMP data payload size is adjusted to yield
Ethernet frames with the specified length. The ping messages are transmitted with the
“don’t fragment” bit set.
Start
Press this button to start the pinging sequence configured above. The status of the ping