Sencore VB330 V Manual v6.0
Sencore VB330 V Manual v6.0
Copyright
© 2020 Sencore, Inc. All rights reserved.
3200 Sencore Drive, Sioux Falls, SD USA
www.sencore.com
This publication contains confidential, proprietary, and trade secret information. No part of this document
may be copied, photocopied, reproduced, translated, or reduced to any machine-readable or electronic
format without prior written permission from Sencore. Information in this document is subject to change
without notice and Sencore Inc. assumes no responsibility or liability for any errors or inaccuracies.
Sencore, Sencore Inc, and the Sencore logo are trademarks or registered trademarks in the United
States and other countries. All other products or services mentioned in this document are identified by
the trademarks, service marks, or product names as designated by the companies who market those
products. Inquiries should be made directly to those companies. This document may also have links to
third-party web pages that are beyond the control of Sencore. The presence of such links does not imply
that Sencore endorses or recommends the content on those pages. Sencore acknowledges the use of
third-party open source software and licenses in some Sencore products. This freely available source
code can be obtained by contacting Sencore Inc.
About Sencore
Sencore is an engineering leader in the development of high-quality signal transmission solutions for the
broadcast, cable, satellite, IPTV, and telecommunications markets. The company’s world-class portfolio
includes video delivery products, system monitoring and analysis solutions, and test and measurement
equipment, all designed to support system interoperability and backed by best-in-class customer support.
Sencore products meet the rapidly changing needs of modern media by ensuring the efficient delivery
of high-quality video from the source to the home. More information about Sencore is available at the
company’s website, www.sencore.com.
This product can include software developed by the following people and organizations with the following
copyright notices:
• Curl. Copyright © Daniel Stenberg and many contributors. All rights reserved.
• Dropbear. Contains software copyright © 2008 Google Inc. All rights reserved.
• OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/).
Copyright © 1998-2017. The OpenSSL Project. All rights reserved.
All trademarks and registered trademarks mentioned herein are the property of their respective owners.
Contents
Contents 3
1 INTRODUCTION 9
1.1 About the Software Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.1 VB330-SW – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.2 Software Probe – Platform alternatives . . . . . . . . . . . . . . . . . . . 10
1.1.3 Software Probe – Functionality . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 PRINCIPLE OF OPERATION 13
VB330 PROBE
DSLAM OR
VB330 PROBE PC
FIBRE
VB288 CONTENT EXTRACTOR AGGREGATION
RG STB
SUPER HEADEND CORE NETWORK REGIONAL METRO NETWORK ACCESS NETWORK
HOME NETWORK
TV PHONE PAD
REGIONAL
CABLE
IP ASI QPSK/ IP ASI QAM NETWORK IP ASI COFDM
DVB-S/S2 VB12-RF PROBE GPS
RF
VB120 PROBE & VB272 QPSK/DVB-S/S2 MODULE VB120 PROBE & VB262 QAM/VSB DVB-C MODULE VB120 PROBE & VB252 DVB-T/T2 MODULE
REGIONAL MONITORING OF SATELLITE AND IP REGIONAL MUX AND QAM MODULATOR REGIONAL MUX AND COFDM MODULATOR
The OTT software option is available on the VB330-SW and enables monitoring of up to 1000
adaptive bitrate channels in steps of 5 or 50 (Bulk OTT option) OTT engines depending on licensing.
A built-in web server in the VB330-SW allows remote signal monitoring using a standard web
browser. This can be managed either through a separate Ethernet network, or by using the regular
video/data network – both IPv4 and IPv6 are supported.
The VB330-SW Software Probe can also be managed via the VideoBRIDGE Controller. The Video-
BRIDGE Controller will add management features like alarm aggregation and report functionality.
The Software Probe is a server appliance, that can be installed onto any server that meets
the minimum requirements specified in chapter 3 or delivered as a pre-configured and pre-
installed appliance server.
Note that the VB330 software image can be licensed to run any bitrate from 1 Gbit/s to 100 Gbit/s.
Full Service Monitoring (FSM) checks that vital system components like CA-servers are active.
Optional Ethernet TR 290 monitoring allows the operator to check parameters like transport stream
sync and PSI/SI standards conformity. This option also performs further PSI/SI analysis, making it
possible to view PSI/SI contents. PID and service bitrates are also continuously measured.
Optional OTT monitoring allows the operator to set up active testing of Over-the-top type signals
as found in adaptive bitrate streaming architectures. Formats supported include Apple ™ HLS,
Microsoft ™ Smoothstream, RTMP, MPEG DASH, Adobe ™ HDS and Nullsoft SHOUTcast™.
The Software Probe can be expanded through license options to monitor the T2MI protocol layer as
found in DVB-T2 networks.
The Software Probe can also be licensed with an SCTE 35 option that allows monitoring and logging
of splice time codes embedded in the transport streams.
The Content Extraction and Analysis option adds QoE monitoring, including freeze-frame, MOS
and VMAF scoring, closed caption and audio level monitoring, thumbnail and metadata extraction,
as well as Encounder Boundary Point monitoring. The Timeline view includes an analysis capability
for an enormously data analysis technology that allows users to play through recorded data in an
NLE-style Timeline display to observe correlations and patterns of errors occurring over any time
period.
VB330-SW Software
Ethernet Management
SNMP Traps
Monitoring Engine
A simplified diagram of the alarm handling mechanisms of the Software Probe is shown in figure 2.2.
The input signals are continuously analyzed, and measured data are checked against user defined
threshold values. If the data do not comply with the threshold values alarms will be generated. The
overall alarm settings further make it possible to enable and disable alarms, thus defining which
alarms should be reported in the Software Probe alarm list and sent as SNMP traps to an external
management system.
1 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_
Administrators_Guide/ch-Web_Servers.html
Alarm
Settings
Threshold
Settings
Signal
Measurements
Figure 2.2: Simplified Diagram of the Alarm Handling in the Software Probe
The Software Probe can be license upgraded to a higher bitrate independently of the hardware. It
may thus be useful to obtain better hardware which allows for future license upgrade.
Recommended NICs
Interface NIC Notes
1G BASE-T Intel I340 and Intel RJ45 connector.
I350 Dual or single input.
10G BASE-T Intel X550-T2 (dual) RJ45 connector.
Dual or single input.
Supports 100Mb/1GbE/2.5GbE/5GbE/10GbE.
10G SFP28 Mellanox ConnectX-4 SFP+ compatible connector.
Lx 10gbe Dual or single input.
Supports 1/10GbE.
25G SFP28 Mellanox ConnectX-4 Dual or single input.
Lx 25gbe Also available for OCP with Host Management.
Supports 1/10/25GbE.
100G QSFP28 Mellanox ConnectX-5 Dual or single input.
Ex 100gbe PCIe 4.0 Supports 1/10/25/40/50/100GbE.
Supported platforms:
If the system is upgraded to an unsupported operating system release, an error message will be
displayed in the Application notification menu upon accessing the user interface. Check the release
notes available for the currently installed software version before updating to a new operating system
release.
• For DVD-based installations, burn the downloaded ISO image to a DVD and insert into
the server.
• For USB-based installation, transfer the downloaded image to a USB mass storage device
using a tool such as dd (Mac, Unix, Linux) or USBWriter3 (Windows).
• For installation in a virtualized environment, attach the downloaded ISO image to a
virtual DVD-ROM unit.
Note: Please read the advice on how to configure the virtual machine in section 3.3 to
ensure optimal performance.
3. Boot the server and make sure that the primary boot device is set appropriately. If the system
fails to boot from the medium, you may need to configure the boot loader for ‘legacy BIOS
mode’.
4. The installer will run, please follow the on-screen prompts to install the system, taking note of
the following:
1 https://docs.centos.org/en-US/centos/install-guide/
2 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_
guide/index
3 https://sourceforge.net/projects/usbwriter/
5. At the end of the installation procedure, the server is rebooted. Remove the installation media
and ensure that the system boots up properly.
6. If you installed the Red Hat Enterprise Linux server flavor, make sure you follow the instruc-
tions on how to subscribe the system to the Red Hat Customer Portal7 .
If you install the CentOS Linux flavor, you may want to enable the Continuous Release
repository8 to be able to get access to security updates as quickly as possible.
7. Enter the selected IP address in your web browser to access the Software Activation page. If
your host is using dynamic addressing, you can log in to the account created during installation
and issue the command ip addr to display the address assigned to the system.
Continue to chapter 3.5 for details on how to enable the Software Probe system.
The kickstart will install CentOS Linux 7 or Red Hat Enterprise Linux 7 on the server. The
disks will be formatted and all contents lost. Make sure that any important data on the server
has been backed up before beginning the procedure.
guide/appe-disk-partitions-overview
5 https://docs.centos.org/en-US/centos/install-guide/
6 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_
guide/index
7 https://access.redhat.com/solutions/253273
8 https://wiki.centos.org/AdditionalResources/Repositories/CR
At this point, we recommend you read the After Installation chapter of the Installation Guide9 .
1. Launch a web browser application on the management system. One of the following browsers
are recommended:
• Google Chrome
• Mozilla Firefox
• Microsoft Edge
• Apple Safari
2. Type the IP address of the server in the browser URL field and press Enter .
If you get a HTTPS certificate warning, just accept it.
The network settings should have been set when the operating system was installed. If the web
browser is unable to reach the web server, check the server’s network settings in the operating
system.
3. The Cockpit administrative interface should be displayed inside the browser. Cockpit is
password-protected and uses the system accounts for logging in. When logging in to the
console of the pre-built images, the default password for the root user is elvis. The page
displayed should look similar to figure 3.1.
5. The Software Probe is not enabled by default on the newly installed server. To enable it, click
the icon next to its name. This will open a detailed view with display details of the installed
software, such as the installed version and the hardware key. If you have a license key that
you want to enable and have not yet done so, enter the key in the field labeled Apply license
key and click the Add license button.
6. Click the button labeled Activate and wait for it to finish. If successful, the Software Probe
should now be activated, and you will be presented with a link to the user interface. The next
time you access the server using a web browser, you should be taken automatically to the
enabled software.
Please note that it may take some additional time before the user interface of the activated
product becomes available. If you receive an error trying to access it, please wait for a few
minutes before trying again.
Note that it is not possible to activate the Software Probe and the VB7880 Advanced Content
Extractor on a single system at the same time.
To return to the Cockpit administrative interface to make changes, open the About — License tab
in the Software Probe user interface and click the link labeled Manage server.
It is strongly recommended that the system time is configured to be synchronized against an
external NTP server. Please refer to F Appendix: Enabling NTP time synchronization for more
information on configuring time synchronization.
• Verify that the client machine and the Software Probe are configured on the same subnet and
that they have different addresses, or, if you use different subnets, verify that the routing and
gateways are set correctly on both the client machine and the Software Probe.
• Make sure that the IP address of the gateway and the network interface are not the same.
• Verify that the appropriate Ethernet link indicators of the PC and the Software Probe are lit.
on the server’s command line. If it is not running properly, or you are seeing DNS lookup
failure errors, try issuing the command
• If you can reach the Cockpit administrative interface, but the Software Probe GUI is not
working, enter the command probehello on the server’s command line to verify that the
VB330-SW services are running. If services are not running, try re-installing the VB330-SW.
Please refer to D Appendix: Network configuration for more information on server network configu-
ration using the Cockpit administrative interface.
If you are running Red Hat Enterprise Linux, the above command might fail because the correct
repository not being enabled. Please run the following commands and try again:
Then re-install the upgrade image as described above to enable the administrative interface.
• Google Chrome
• Mozilla Firefox
• Microsoft Edge
• Apple Safari
The default management view should look similar to figure 3.2. If you have problems accessing the
user interface, refer to chapter 3.6 for troubleshooting.
3.11 Deactivating
To deactivate Software Probe, you must first access the administrative interface (see the previous
section) and make sure that it is not set to the default. Expand the product details heading and click
the Remove as default button.
Once this is done, access the Software Probe user interface and de-activate it from the About —
License view.
2. Inspect the OTT monitoring progress using the OTT — Active testing dialog. Useful infor-
mation on OTT monitoring can be found in Appendix C.
4.3 Monitoring
When input signal parameters have been set, the signals may be monitored.
For Ethernet multicasts the relevant monitoring views are Main, Alarms, Multicasts, MW, Traffic
and Ethernet. If the probe is equipped with the ETR 290 and/or the OTT option then the views
ETR 290 and OTT are of relevance as well.
Ethernet monitoring hints are found in B Appendix: Monitoring Practices.
The VB330-SW web interface is reached by pointing a web browser to the IP address of the Software
Probe as shown in the screenshot above. The following web browsers are recommended:
• Google Chrome
• Mozilla Firefox
• Microsoft Edge
• Apple Safari
Note that different web browsers behave differently with respect to memory leaking, and if the
VB330-SW GUI should be available at all times the browser should be selected carefully. A browser
The intention of this page, together with the alarm list, is to provide enough information for the
operator to immediately see if there is anything seriously wrong with one or more input streams.
The following parameters are shown:
NTP/timesync
(Bulb): The NTP/timesync bulb indicates whether the VB330-SW clock is locked to an
external time reference signal. Green indicates that the VB330-SW is locked to an
external reference whereas grey indicates that the VB330-SW runs in unlocked
mode or the status is unknown.
Updated: The time since the last time synchronization update.
Freq offset: Indicates the measured frequency offset for the system clock.
Timezone: The time zone relative to UTC. Configured in the OS.
Time: The current local time.
We recommend using the standard operating system tools for configuring the system clock. Please
refer to the operating system instructions1 for further details on how to configure the date and time.
RDP
(Bulb): The RDP bulb indicates whether RDP is active or not. Green indicates RDP active
whereas grey indicates that RDP is currently not active.
1 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_
Administrators_Guide/chap-Configuring_the_Date_and_Time.html
Probe
Name: The VB330-SW name as defined by the operator in the Setup — Params view.
Location: The VB330-SW location as defined by the operator in the Setup — Params view.
Access: The access rights of the current user. Access rights are either full access or read only
access, and are defined by the operator in the Setup — Security view.
Traffic
RX data: The total bitrate of received data traffic
Monitored data: The total bitrate of multicasts and unicasts monitored (analyzed) by the probe
ETH info
Joined: The number of joined streams (multicasts and unicasts)
Unicasts: The number of unicasts currently being joined/monitored by the probe
Multicasts: The number of multicasts currently being joined/monitored by the probe
IGMP ver: The IGMP version currently used by the probe. IGMPv2 is used unless the operator
has enabled IGMPv3 in the Setup — Params view.
OTT info
Channels: The number of enabled OTT channels.
Profiles: The total number of profiles in the enabled OTT channels.
At the very bottom of the Summary page, an overview of the Ethernet network interfaces on the
VB330-SW are displayed.
Network interfaces
Interface: The ID of the selected network interface.
Link: Indicates whether the interface is connected.
Speed: Shows the current bitrate for the interface.
Description: Provides a human-readable description of the interface, if available2 .
IPv4 address: Lists the IPv4 address and netmask of the network interface, if set.
IPv6 address: Lists the IPv6 address and netmask of the network interface, if set.
Timestamp: Indicates whether the network interface supports hardware timestamping for
precise measurements, or if kernel timestamping is used.
2A description can be set using the command ip link set interfacename alias "Description"
The CPU usage view is meant for troubleshooting performance issues in case of excessively high
traffic load.
Three internal performance indicators (System, User and Idle) are displayed as percentage numbers
and also graphed for the last minute. Issues can potentially arise if the System indicator becomes
high (>80%).
The CPU usage view displays CPU usage of the Software Probe. To view the CPU usage averaged
over the last 10 seconds click the Current button. To view the usage averaged over the last 60
seconds click the Last 60 seconds button. Clicking the Peak any 10 secs or Peak any 60 seconds
button will display the historical maximum value for an averaging period of 10 s and 60 s respectively.
To clear peak values click the Clear peaks button.
The length of the queues for multicast video analysis are displayed in the Backlog column, with the
highest recorded value in the Peak backlog column. If these values keep growing, the probe is not
able to keep up with the amount of data it has been set to monitor, and will eventually start dropping
data to catch up again. Additionally, the currently running process (at the time of update) on each
CPU core is displayed in the Current task column.
The Thumb overview view displays a mosaic of all decoded thumbnails. By default the Normal
mode is used. Placeholder images will be displayed if thumbnailing has not been enabled in the
Setup — Params view, indicating the type of stream being received.
If the Small button is clicked the Thumb overview view will display service names and thumbs
only, allowing more thumbnails to be displayed in a view. To display the stream address and name
(as defined in the Multicasts — Streams and OTT — Channels views) click the Stream info
button.
The following information is displayed for each stream:
Thumb overview
Service name: Shows the name defined for the TV service in the SI service descriptor.
If no SI is present in the stream the service id will be shown.
Service ID: For TS services, the ID of the selected service within a transport stream.
Type: For non-TS services, the service type is displayed.
The Thumbs Details pop-up view is accessed by clicking a thumb in the Thumb overview view.
For more information about the details displayed in the Thumbs Details pop-up see chapter 5.4
for multicast streams, and chapter 5.3.2 for OTT channels. Note that thumbnails are only decoded
automatically if the Extract thumbnails option has been enabled in the associated OTT or multicast
setup, or if freeze-frame or color-freeze alarming (Content Extraction and Alarming option) has
been enabled in the Content threshold template. The same pop-up details are displayed as when
opened from the ETR 290 — Services view.
Clicking the Close button will close the view.
Eii is short for External Integration Interface and constitutes a set of XML files accessible through
the VB330-SW web server interface for machine access to measurement data.
Portions of the Eii interface are available in this view for simple trend graphing over arbitrary long
time by the web browser.
The screenshot shows the bandwidth of two IP streams being graphed by sampling the Eii interface
every 2 seconds. The graph is stored in the client web browser for as long as the graph window
remains open. The graph starts again with zero history if the window is closed and then opened
again.
Refresh (seconds) selects how often samples are read and plotted on the graph. Click Apply to
store the parameters and then click the Plot chart link to open the chart.
Refresh (seconds) selects how often samples are read and plotted on the graph. Click Apply to
store the parameters and then click the Plot chart link to open the chart.
Refresh (seconds) selects how often samples are read and plotted on the graph. Click Apply to
store the parameters and then click the Plot chart link to open the chart.
Please refer to the separate Eii documentation for further details.
Alarm Settings
System Events
and Scheduling
FSM Settings
FSM Measurements
Figure 5.1 shows an overview of the alarm handling in the Software Probe. It is useful to obtain an
understanding of the alarm processing of the Software Probe – in particular how threshold settings
and alarm setup will affect alarm handling.
The Software Probe continuously compares measurement data with user defined thresholds in order
to generate alarms. These alarms are further checked against the settings defined in the Alarms —
Alarm setup view, and the resulting alarms are presented in the alarm lists. These alarms will also
be sent as SNMP traps to support third party management systems. Refer to Appendix: VB330-SW
Versus VBC Alarms for a description of alarm handling in the VideoBRIDGE Controller.
The Software Probe distinguishes between events and alarms. The ETR software module will always
generate alarms and the Systems software module will always generate events. The Ethernet software
module will by default generate events for errors that are resolved within 1 second, otherwise it will
The Alarms view gives the user the possibility of viewing alarms according to type or as one
combined list. The individual alarm lists can hold the number alarms indicated below independently
of each other, meaning that one may become full without affecting the other lists.
If Auto-refresh list is selected, the alarm list will be continuously updated with new alarms. Active
alarms are always located at the top of the list.
Clicking the View list offline button gives the user the opportunity to view the complete alarms and
events list. By clicking one of the blue information icons leftmost in the offline list, a detailed alarm
description can be viewed. The search field in the upper right corner of the view allows the user
to type a text string and the alarm list is updated to display only streams and alarms matching the
specified text. To update the offline alarm list click the Auto-refresh list button and then go back to
the offline mode.
The Alarm setup represents the final filtering stage for VB330-SW alarms. The user selects whether
an alarm should be enabled or ignored, and associates an error severity level with each alarm, and
associates an error severity level with each alarm. When changes have been made to alarm settings
click the Apply changes button for changes to take effect.
Figure 5.1 gives an overview of the total alarm handling of a Software Probe. The settings in the
Alarm setup view are represented by the Alarm Settings box in this figure.
Note that the probe alarm handling will also depend on the threshold template settings defined by the
user in the Multicasts — Ethernet thresh., ETR 290 — ETR thresh., ETR 290 — PID thresh.,
ETR 290 — Service thresh., and OTT — Thresholds views.
Also note that only enabled alarms are shown in the alarm lists and forwarded as SNMP traps.
Enabling or disabling Software Probe alarms does however not affect the alarms presented by the
VBC. Refer to Appendix: VB330-SW Versus VBC Alarms for a description of the VB330-SW
versus VBC alarm handling.
The following alarm severity levels may be selected:
OK: If enabled, the alarm will be present in the alarm list, color green
Warning: If enabled, the alarm will be present in the alarm list, color yellow
Error: If enabled, the alarm will be present in the alarm list, color orange
Major: If enabled, the alarm will be present in the alarm list, color red
Fatal: If enabled, the alarm will be present in the alarm list, color black
OTT Alarms
The number of profiles changed: The number of profiles Default: Enabled,
flagged in the manifest file severity ‘Warning’
changed
Profile stream type changed: The stream type of the profile Default: Enabled,
changed in the manifest severity ‘Warning’
Minimum profiles The channel has less profiles Default: Enabled,
than specified in the threshold severity Warning
Wrong profile type The channel has profiles of a Default: Enabled,
different type than specified severity Warning
in the threshold
Download bitrate low: The download duration time Default: Disabled,
exceeds the OTT bitrate severity Warning
threshold. The bitrate thresh-
old is part of the OTT thresh-
old template defined in the
OTT — Thresholds view. A
threshold template is assigned
to a stream in the OTT —
Channels view.
Download bitrate too low: The download duration time Default: Enabled,
exceeds the OTT chunk dura- severity Error
tion time
The FLASH option enables the Flash alarms tab. This alarm list contains the last 20,000 alarms
and keeps them on the hard disk so that they survive reboots and power-outages. This opens up a
lot of possibilities for probes that cannot be reached while doing measurements and for probes that
need to be powered down and consulted elsewhere. It also severely increases the size of the alarm
list allowing browsing of older alarms.
The OTT option enables monitoring of up to 1000 OTT channels. Up to 50 OTT engines (depends
on license) can operate in parallel, and each engine licensed allows any channels to be analyzed.
Each engine analyses channels in series and can be configured with any number of channels up to
the maximum allowed by the license.
The Software Probe will parse a channel’s manifest file, and for a live channel one of the latest
chunks in each OTT profile’s chunk sequence will be analyzed. The engine then moves on to the
next OTT channel in the channel list defined by the user. For a VoD channel the OTT engine will
analyze all chunks in the VoD file, one in each round-robin loop.
If manifest file parsing or chunk analysis reveals an error, an alarm will be raised. Note that some
alarms depend on user defined threshold values. Alarms must also be enabled in the Alarm —
Alarm setup view.
Thumbnail decoding is available for non-encrypted HLS, HDS, DASH, Smoothstream and RTMP
channels, as well as AES128 and SAMPLE-AES encrypted HLS channels, and fixed key CENC
encrypted DASH.
The page to display can be selected from a drop-down menu.
The following OTT information is displayed in the Active testing view:
OTT channels
Status bulb: A bulb indicates the current status of the channel, i.e. the most severe
profile status.
The Profiles view in this pop-up consists of two tables detailed below:
The following information relevant for the overall OTT channel is shown in the first part of the
Details — Profiles pop-up window:
Channel
Channel: The channel name defined by the user and linked to a URL in the OTT —
Channels view. A bulb indicates the current status of the channel, i.e. the most
severe profile status.
Progress: Channels will be analyzed sequentially, and the progress bar shows which
channel is currently being monitored and how analysis is progressing.
Stream type: Channel and profile information is resolved from the manifest files. At channel
level the OTT format is displayed (Smoothstream, HLS, Adobe HDS, MPEG
DASH or SHOUTcast).
In the same view below the table for the overall channel a more detailed view per channel profile is
shown with the following information in it:
Profiles
Profile: The name of the OTT profile as flagged in the manifest files.
Type: Live for live content or VoD for stored content. The distinction between
the two is done based on whether the profile sequence numbers update or
not.
Profile health: * A timeline graph display of a combined bitrate and alarm representation
for individual profiles. Refer to Appendix C for a description of these
graphs. The timeline duration is either 2 or 24 hours, and the graph
resolution is one minute for the 2 hour graph, and twelve minutes for the
24 hour graph.
Profile bps: * The profile nominal bandwidth as flagged in the manifest files.
Actual bps: * The actual profile bitrate, i.e. the chunk size (megabits) divided by the
chunk length (seconds). The actual profile bitrate should match the man-
ifest bitrate specification within limits defined by the user in the OTT
thresholds template associated with a channel. Otherwise an alarm will be
raised.
Download bps: * The download bitrate, i.e. the chunk size (megabits) divided by the down-
load time (seconds).
Chunk length: * The profile chunk length (seconds) specified in the manifest file.
Download time: * The actual profile chunk download time (seconds).
First byte: * The time (in seconds) before the first payload data byte was received.
Download size: * The actual profile chunk size (bytes).
Note: Items marked with * are not available if the channel has been configured to only perform
latency measurements (see chapter 5.3.3 for more details).
The Manifest view shows health information on the overall manifest file for the channel as well as
for the manifest files for the individual profiles.
Channel
Channel: The channel name defined by the user and linked to a URL in the OTT —
Channels view. A bulb indicates the current status of the channel, i.e. the most
severe profile status.
Progress: Channels will be analyzed sequentially, and the progress bar shows which
channel is currently being monitored and how analysis is progressing.
Profiles: The number of profiles associated with a channel.
Profile status: The channel health bar displays the current status for individual channel profiles.
Profiles are separated by vertical black lines.
Colors indicate profile alarm status:
• Green: OK
• Yellow: Warning
• Orange: Error
• Red: Major
• Black: Fatal
Just below the channel manifest information in the same window is the detailed manifest information
per profile. This view contains the following information:
Profiles
Profile: The name of the OTT profile as flagged in the manifest files.
Profile bps: The profile nominal bandwidth as flagged in the manifest files.
Type: Live for live content or VoD for stored content. The distinction between the
two is done based on the contents of the manifest file.
Seq.age: The profile sequence shows how long it has been since the manifest was
updated in whole seconds.
Manifest size: The size in bytes of the manifest file for a particular profile.
Manifest file: Clickable URL for displaying the manifest file as text for this particular profile.
Manifest URL: Clickable URL to the profile manifest file.
HTTP header: URL to HTTP header in text form for a particular profile manifest file.
The Details — Alarms view gives an at-a-glance overview of any active OTT alarms for the selected
channel. An alarm log for the selected channel is also provided here.
In the right corner of the pop-up window is a free text search field used to narrow down the entries
in the alarm log.
The alarms are the same ones as explained for the Alarms — Alarm setup view, see chapter 5.2.2
for more information.
The Thumbnails tab will provide information about the current thumbnails in the channel.
The quality of the content in the selected profile can be viewed in the thumbnail section, and the
user may alter the selected profile in the drop down list.
The section on the right hand side provides specific decoder and chunk information.
By pressing the Apply button without selecting a profile from the drop-down list the thumbnail will
be switched to the default selection; Auto select. Auto select will select the profile with the highest
bitrate and video data.
Video information
Size: The video picture size of the selected profile
Aspect ratio: The video aspect ratio of the selected profile
Pixel aspect ratio: The video pixel aspect ratio of the selected profile
Codec: The video encoding format of the selected profile
Pixel format: The video sampling format of the selected profile
Frame rate: The video frame rate of the selected profile (Hz)
Blockiness: Detected picture blockiness, in percent. Displayed if QoE scoring is
enabled.
The QoE scores are only calculated for the profile with the highest bitrate. To measure the quality
loss between profiles, enable VMAF scoring and use the measurements displayed on the Alignment
tab.
Audio Information
Codec: The audio encoding format
Sample rate: The audio sample rate
Channels: The number of audio channels represented by the audio PID
Layout: The audio channel layout
Bitrate: The effective audio bitrate
Peak level: The audio peak level for the currently decoded chunk
Chunk Information
Engine ID: The OTT engine monitoring the selected channel.
Channel ID: The ID of selected channel corresponding to the list of channels defined
by the user.
Profile ID: The ID of the selected profile.
Bitrate: Bitrate rate of the a chunk.
Streamtype: The type of the stream detected; live or video on demand.
Sequence Number: The sequence number of a chunk.
The Alignment tab gives the user a view of all the profiles for a selected channel with thumbnails
and corresponding data.
The current version of the VMAF algorithm and model (denoted as VMAF 0.3.1), released as part
of the VMAF Development Kit open source software, uses the following elementary metrics fused
by Support Vector Machine (SVM) regression: Visual Information Fidelity (VIF), Detail Loss
Metric (DLM), Motion
Software Probe release 6.0 utilizes the VMAF 0.3.1 DLM metrics for its QoE scoring.
The OTT Channel Latency Distribution feature makes it possible to measure the delay from when a
chunk is available through different caches, compared to its origin.
Before using this feature, you must set aside a number of OTT engines to exclusively measure the
timings of one channel on one server. This is done in the OTT — Settings view. In general, you
would need to use two Latency Engines per channel: one for the origin and one for the cache.
After selecting the number of Latency Engines, open the OTT — Channels view and add the channel
from multiple sources (URLs), using the same base name, but different classes, e.g. TV1@Origin
and TV1@CDN. Then set the Measurement mode to Latency if you are only interested in the
timings from this server, or Both if you also want the traditional Active Testing measurements. Each
added channel will use one dedicated Latency Engine, if you try setting Latency or Both and there
is no free Latency Engine available, it will default back to Normal.
Once the configuration is finished, you are ready to use this feature. Select the channel to produce a
latency graph for using the Channel drop-down. Then select which of the classes of the channel
that is to be used as the reference in the Reference drop-down. This is used to calculate the time
delta difference.
The graph will start off showing the difference in availability time of each chunk for the last minute
and will build up history until displaying the last hour. Due to the nature of timing in different
engines, these measurements are accurate down to ±0.5 seconds. To minimize these inaccuracies, a
moving average is provided, smoothing the spikes. The sliding window can be manually controlled
by moving the Avg window slider. It is also possible to display the minimum and maximum values
by checking the Show min/max checkbox.
The OTT Channel Configuration list shows OTT channels configured by the user.
To add a channel to the list click the Add new channel button. This will open the Edit channel
pop-up view, allowing the user to define channel parameters. A channel entry can be selected
by clicking the channel; the list entry will be highlighted. Several list entries can be selected by
using regular Ctrl + click functionality. Clicking the Duplicate selected button will open the Edit
channel pop-up view with all channel parameters duplicated, except the channel name. Clicking
Delete selected will delete the highlighted list entry. Clicking Distribute selected will distribute
the selected channels across the licensed OTT engines (the VB330-SW can be licensed with up to
50 OTT engines). Clicking Edit selected will open the Edit channel pop-up view associated with
the highlighted channel. Batch editing is supported; this is convenient if a new threshold template
should be assigned to a number of channels or if monitoring of several channels should be enabled
or disabled. Select the channels and click the Edit selected button. Parameters differing between
channels will be indicated in the Edit selected pop-up view by an asterisk wildcard symbol.
The search field in the upper right corner of the view allows the user to type a text string, and the
OTT channel list is updated to display only channels matching the specified text.
Adv. manifest
Enable adv. settings: Check this box to enable the advanced manifest settings. If unchecked,
all settings on this page are ignored.
Method: Determines which HTTP method to use when requesting the top-level
manifest file. Supported methods are GET and POST.
Content-Type: When requesting the manifest using the HTTP POST, use this Content-
Type for the submitted request body.
Additional headers: To provide additional custom request headers or overwrite the default
headers when requesting the top-level manifest file, create a text file
containing the headers and upload them here.
Body: When requesting the manifest using the HTTP POST, upload the file to
submit here.
The Settings tab makes it possible to change global and per-engine OTT monitoring parameters.
Press Apply to confirm changes made.
The OTT Threshold presets list shows OTT threshold templates configured by the user.
To add a threshold template to the list click the Add new threshold button. This will open the Edit
threshold pop-up view, allowing the user to define threshold parameters. A threshold template entry
can be selected by clicking the threshold template; the list entry will be highlighted. Several list
entries can be selected by using regular Ctrl + click functionality. Clicking the Duplicate selected
button will open the Edit threshold pop-up view with all threshold template parameters duplicated,
except the threshold template name. Clicking Delete selected will delete the highlighted list entry.
Clicking Edit selected will open the Edit threshold pop-up view associated with the highlighted
threshold template. Batch editing is supported. Select the threshold templates and click the Edit
selected button. Parameters differing between templates will be indicated in the Edit selected
pop-up view by an asterisk wildcard symbol.
The search field in the upper right corner of the view allows the user to type a text string, and the
threshold list is updated to display only thresholds matching the specified text.
Threshold preset
Name: The threshold template name defined by the user.
Refs: The number of channels associated with the threshold template
Profile stream type: The stream type (Live or VoD). If any of the profiles have a different
type a wrong profile type alarm will be raised.
Download speed error: The maximum allowed difference between profile bitrate and down-
load bitrate (%). If the difference exceeds the threshold value a bitrate
error alarm will be raised.
Download speed warn: The maximum allowed difference between profile bitrate and down-
load bitrate (%). If the difference exceeds the threshold value a bitrate
error warning will be raised.
Actual bitrate min: The minimum allowed bitrate when measured actual bitrate is com-
pared to profile bitrate (%). If the actual bitrate goes below the thresh-
old an actual bitrate alarm will be raised.
Actual bitrate max: The maximum allowed bitrate when measured actual bitrate is com-
pared to profile bitrate (%). If the actual bitrate exceeds the threshold
an actual bitrate alarm will be raised.
Sequence age: The maximum time a manifest can remain unchanged before a mani-
fest age alarm is raised.
Manifest XML size: The maximum detected size of the manifest before a manifest size
alarm is raised.
The Multicasts — Parameters view displays detailed information about each stream.
The user selects which group of measurements should be displayed. Selections are IP parameters, TS
parameters, Ethernet parameters, RTP and FEC parameters, User-defined parameters and Statistical
parameters. If User-defined parameters is selected, the Multicasts view displays parameters selected
by the user in the Multicasts — Parameters — Fields view.
For each page the Accumulated row at the bottom of the multicast list displays accumulated values
for all streams associated with the page. The accumulated Min bitrate and Max bitrate is the
minimum and maximum value of the Accumulated current bitrate.
When the Current page button is clicked it is possible to select the page from a drop-down menu.
The associated thumbnails are shown in the leftmost column of the list of measurements. Click one
of the small thumbnails to view a larger thumbnail that is updated more frequently. Note that it is
possible to disable probe thumbnail extraction in the Setup — Params view.
When All streams (offline) is clicked a complete list of measurements for all joined streams is
displayed. A search field allows the user to type a text string and the multicast list is updated to
display only multicasts matching the specified text. Note that monitoring parameters and thumbs
will not be updated in All streams (offline) mode.
Clicking a stream brings up the Detailed monitoring pop-up described later in this section.
In All streams (offline) mode a search field allows the user to type a text string and the multicast
list is updated to display only multicasts matching the specified text.
Joined multicasts
:
i Click the information icon to access the Detailed Monitoring pop-up view.
Thumb: A thumbnail is displayed for each stream. Click the small thumbnail to view a
larger image that is updated more frequently.
Name: The stream name specified by the user in the Edit Multicast view
Signal: Time since last signal loss
Page: The page associated with the multicast
CPU: CPU core monitoring this multicast
Input: Network interface used to receive this multicast
Mapping: For MPEG-2 Transport streams, the number of MPEG-2 packets mapped into
each RTP or UDP packet is displayed here. For SMPTE 2022-6 SDI over IP
streams, “SDI/RTP” is displayed, and for other unsupported RTP streams, “RTP
data” is displayed.
Net bitrate: Instantaneous MPEG-2 Transport Stream bitrate excluding null packets (PID
8191). The instantaneous bitrate is measured over a time period of 1000 ms.
Statistical parameters
Thumbnails
The probe will try to generate thumbnail pictures for all streams. For multi-program transport
streams (MPTS) the first video component is selected. MPEG-2, H.264/MPEG-4, H.265/HEVC
and JPEG 2000 video formats in standard definition, high definition or ultra-high definition are
supported in MPEG-2 transport streams, as well as SMPTE 2022-6 uncompressed video in RTP
streams.
The thumbnail update rate will depend on how the streams are coded and if they are standard
definition, high definition or ultra-high definition. It is possible to increase the update rate by
opening the Thumb View pop-up, described below.
If the probe is unable to generate a thumbnail from the signal, it will present one of the following
icons:
Shown if no data is received for the stream. There should be a match between
presenting this icon and a No-signal alarm; however since the alarm and thumbnail
mechanisms work independently of each other they have been given different names
(loss of signal and no signal).
Shown while the thumbnail engine is trying to decode a thumbnail picture and more
precise status information has not yet been obtained. This icon is typically displayed
after probe reboot or if new streams have recently been joined.
Shown if the service does not carry a video PID — which is the case for radio
services.
The signal cannot be decoded due to excessive CC errors or RTP packet drops.
The signal is recognized as being MPEG-2 encoded but the thumbnail extractor is
unable to correctly decode a thumbnail picture.
The signal is recognized as being MPEG-4/H.264 encoded but the thumbnail extractor
is unable to correctly decode a thumbnail picture.
The signal is recognized as being MPEG-H/H.265 encoded but the thumbnail extrac-
tor is unable to correctly decode a thumbnail picture.
The signal is recognized as being JPEG 2000 encoded but the thumbnail extractor is
unable to correctly decode a thumbnail picture.
The signal is recognized as being an uncompressed (raw) video stream but the
thumbnail extractor is unable to correctly decode a thumbnail picture.
This icon is shown if the probe is unable to receive or analyze the PMT PID. Only
streams with PSI information can have thumbnails decoded since the probe does not
support a manual specification of the video PID.
The probe can only generate a thumbnail picture if the video data is not scrambled.
Detailed Monitoring
The Detailed Monitoring pop-up is activated by clicking a stream line in the monitoring list.
The current parameters for the selected stream are displayed in the bottom of the dialog, as in the
Joined multicasts list.
Clicking the Clear button will clear all information about the selected stream, including PSI/SI
analysis data. Clicking the MediaWindow button will open the Media Window Selected channel
view. This is described in section 5.5.
Detailed Monitoring — Services
Service/Pid: For each service, the service-name or service-id is obtained from the PSI/SI tables.
PIDs that do not belong to a service are denoted ‘Other PIDs’. The service ID is
presented in square brackets.
Bitrate: Service or component bitrate in bits per second
Min bitr.: Minimum service or component bitrate in bits per second
Max bitr.: Maximum service or component bitrate in bits per second
CC errors: Number of Continuity Counter occurrences
Thumb: Click the
i icon to access the Thumb pop-up view, explained below
Type: The list entry service type or PID type
PCR: This field will be checked if the corresponding PID carries PCR
Scr: This field will be checked if the corresponding PID is scrambled
In the Detailed Monitoring — IAT view, the Inter Arrival Time histogram shows the accumulated
number of IAT measurements within each presented interval. Vertical green lines indicate the
maximum and minimum IAT values. By clicking the IAT range buttons it is possible to change the
zooming of the graph. If the Auto zoom button is pressed the diagram will auto-scale to always
include the minimum and maximum IAT readings.
Thumb View
The Thumb View pop-up is accessed by clicking an information icon in the Detailed Monitoring
— Services view. This view presents a large thumbnail, as well as video and audio metadata for the
selected stream, with an increased update rate compared to non-selected streams. Service loudness
and audio phase data are indicated in graphs for each audio component. The same pop-up can be
opened from the Main — Thumb Overview view, see chapter 5.1.3 for more information.
Clicking the Close button will close the Thumb View view.
The following metadata is displayed for multicasts:
Please note that audio information is only decoded when enabled through the assigned content
threshold. Audio information is updated periodically, and the initial display can take up to ten
seconds. For more details on the content thresholds, please refer to the Content — Content thresh.
view.
If caption monitoring has been enabled for the channel, the last two caption events for the service
are displayed. For more details on these events, compare the Content — Captions view.
The following stream status information will be displayed (bulbs will be green for status OK, red to
indicate an active alarm and grey if the associated check has been disabled):
Status description
Audio silence: A bulb indicates the audio silence status with reference to the defined require-
ment.
Threshold: The audio silence detection threshold (LUFS/LKFS) as defined
in the stream threshold template associated with the stream.
Audio too loud: A bulb indicates the audio too loud status with reference to the defined require-
ment.
Threshold: The audio peak detection threshold (LUFS/LKFS) as defined in
the stream threshold template associated with the stream.
Audio phase: A bulb indicates the audio phase status with reference to the defined require-
ment.
Threshold: The audio phase detection threshold as defined in the stream
threshold template associated with the stream.
Freeze-frame: A bulb indicating the freeze-frame detection status. The freeze-frame error
timeout value is set as part of the content threshold group associated with
each multicast (refer to the Content — Content thresh. and Multicasts —
Streams — Edit views).
Consecutive frozen frames: The number of consecutive equal frames that
have been detected
Multicast
Transport stream ID: The ID of the selected stream as shown in the list of multicasts in the
Ethernet section; non-TS services display 1 here
Name: The name of the multicast containing the selected service, as defined by
the user
Type: The type of the stream containing the selected service; multicast or
unicast
Multicast address: The multicast address of the stream containing the selected service
Multicast port: The port number of the multicast containing the selected service
Bitrate: The total stream bitrate of the multicast containing the selected service
(bits/s)
Content Threshold: The name of the content threshold template assigned to the multicast
Service Threshold: The name of the service threshold template assigned to the multicast
Schedule: The name of the content alarm masking schedule template assigned to
the multicast
Service
Service ID: The service ID of the selected service; non-TS services display
1 here
PSI/SI Name: The name of the selected service, as derived from PSI/SI;
non-TS services display the multicast name here instead
Number of PIDs/Components: The number of PIDs or components associated with the se-
lected service
Video Information
Size: The video picture size of the selected service
Aspect ratio: The video aspect ratio of the selected service, or “N/A” if no information is
available
Pixel aspect ratio: The video pixel aspect ratio of the selected service, or “N/A” if no informa-
tion is available
Codec: The video encoding format of the selected service
Pixel format: The video sampling format of the selected service
Frame rate: The video frame rate of the selected service (Hz)
Interlace: Whether the video source is interlaced or not
Blockiness: Detected picture blockiness, in percent. Displayed if QoE scoring is en-
abled.
Blurriness: Detected picture blurriness, in percent. Displayed if QoE scoring is enabled.
Noisiness: Detected picture noisiness, in percent. Displayed if QoE scoring is enabled.
Brightness: Detected picture brightness, in percent. Displayed if QoE scoring is enabled.
Contrast: Detected picture contrast, in percent. Displayed if QoE scoring is enabled.
MOS score: Calculated picture quality score, on a scale from 1.0 to 5.0, where 5.0 is
best. Displayed if QoE scoring is enabled.
Audio PID/Component
PID/Component: The audio PID of the selected service for MPEG-TS services, or the audio
component number for non-TS services
Note that there may be several audio PIDs or components associated with a
service
Type: The audio encoding standard
Has PCR: Yes if the selected Audio PID contains PCR
Bitrate: The audio bitrate for this PID or component (bit/s)
Language: The language of the audio, as defined in the MPEG-TS Program Map Table
(PMT)
The Multicasts — Parameters — Fields view enables selection of the parameters to be displayed
in the Multicasts — Parameters view. Note that thumbnails must also be enabled in the Setup —
Params view for thumbnail availability.
The intention of this page, together with the alarm list, is to provide enough information for the
operator to immediately see if there is anything seriously wrong with one or more Ethernet input
streams. The overall status for the Full Service Monitoring (FSM) is also shown.
Throughout this view the bulb colors indicate the most severe active alarm. They may be green (no
alarm), yellow (warning), orange (error) or red (major). The bulb color is based on user defined
alarm severity settings for each alarm. A grey bulb indicates that monitoring is disabled.
The following Ethernet parameters are shown:
Eth streams withactive alarms: Shows the number of streams that are presently in an alarm
state. Note that the number of alarms counted refers to default
settings, and alarms disabled by the user will still be counted.
Interface bitrate: This is the total bitrate sensed on the data/video interface(s).
It should be greater than or equal to the Monitoring bitrate.
Monitoring: This is the total number of Ethernet streams monitored and
the total bitrate for these streams.
Full Service Monitoring status: The number of enabled FSM services / number of OK FSM
services
The probe is capable of monitoring several thousand streams simultaneously. The probe splits
streams into pages for easy handling. Each of the 30 predefined pages can be given a name and have
a user defined number of streams associated.
Part of the page-status is error-second statistics for the fundamental parameters MLR, RTP, overfl
and nosig summed across all streams belonging to that page.
‘Bulb’: The bulb indicates the most severe active alarm for any of the streams on the page.
Active alarms are located on top of the alarm list. The alarm severity is reflected by
the color of the associated icon.
Next to the bulb is a link that will lead to the Monitoring page if pressed. The
Monitoring page will present error-second statistics for each stream individually.
OK: Shows how many of the streams monitored on this page are without active alarms
ES(MLR): Number of seconds in selected period with continuity counter errors in the MPEG2
transport stream (which corresponds to the number of seconds with non-zero Media
Loss Rate).
ES(RTP): Number of seconds in selected period with RTP packet-drop
ES(overfl): Number of seconds in selected period with bitrate overflow
ES(nosig): Number of seconds in selected period where no signal (i.e. no data) was received
The probe keeps statistical Ethernet information for the last 4 days for visual inspection in the
history timeline view.
Each bar in the histogram corresponds to a number of events that occurred within a certain time
interval. The interval that each bar represents depends on the scale, from 1 minute (when 90 min is
selected) to 1 hour (when 4 days is selected).
No signal: The number of streams that reported the ‘No signal’ alarm during the interval
represented by the bar.
CCerr: The number of times a discontinuity has been detected for all the MPEG-2 Transport
Stream continuity counters in the interval represented by the bar. This parameter
corresponds to the sum of CC errs reported by all streams.
RTPdrop: Accumulated number of dropped IP-frames due to network errors in the interval
represented by the bar. This parameter corresponds to the sum of RTP drops
reported by all streams.
RTPdup: Accumulated number of duplicate IP-frames in the interval represented by the bar.
This parameter corresponds to the sum of RTP dups reported by all streams.
RTPooo: Accumulated number of times a packet has been found to be out of order in the
interval represented by the bar. This parameter corresponds to the sum of RTP ooo
reported by all streams.
Tot bitr: Bitrate sensed on the data/video interface(s).
Mon bitr: Bitrate on the data/video interface(s) corresponding to joined multicasts.
CRC errs: Detected CRC errors. Ethernet CRC errors are most likely caused by a bad cable or
a misconfigured router. A CRC error may impact packet loss measurements such as
CC errors and RTP errors.
Note that the history graphs show the sum for all streams being analyzed across all pages. So for
example, if two streams experience No signal at the same time the No signal graph will increase by
2.
The SAP view displays streams announced using the Session Announcement Protocol, detected by
the VB330-SW.
As long as Enable SAP discovery is enabled in the Setup — Params view, the VB330-SW will
continuously try to detect streams. Click the View list offline button to view the stream list in offline
mode. Click the Refresh button to update the stream list in offline mode.
The source address makes it possible for the Software Probe to distinguish between multicasts with
the same destination IP address and port, provided that Source specific multicasts has been enabled
in the Setup — Params view.
If the stream is currently joined by the Software Probe (i.e. the VB330-SW is currently monitoring
the stream), the Joined field is set to yes.
Detected streams can be added to the VB330-SW’s stream list by selecting streams and clicking the
Add selected to stream list. To add all detected streams the Add all to stream list button can be
pressed.
In order for the defined Ethernet multicasts to be monitored by the probe, they must be joined.
The Multicasts — Join view and the Multicasts — Streams view allow the user to select which
multicasts that are joined by the probe.
Streams defined in the Multicasts — Streams view will appear as available streams on the left hand
side of the arrows in this view. Select streams to be monitored by clicking them and moving them to
the right hand side of this view using the arrow. Changes should be confirmed by clicking the Apply
changes button.
Joined streams may be freely associated with the 30 probe pages. The streams will be presented in
the Joined multicasts list in the Multicasts — Parameters view.
It is possible to flush or fill the multicasts/unicasts to monitor list by clicking the corresponding
button. Note that these operations will take effect immediately; it is not necessary to click Apply
changes for multicasts to be joined or unjoined.
In this view the operator can define multicasts available to the probe and associate a name with each
multicast address. This name will be used by the probe when referring to the multicast. If no name
has been defined the probe will use the multicast address:port notation.
It is possible to add, delete or edit several entries simultaneously. Several entries are selected by
using the regular Ctrl + click or Shift + click functionality. When adding new entries the current
dialogue values will be used as the template with the values for Name and Address incremented for
each.
Note that both multicast and unicast addresses can be entered here.
The Distribute ETR engines button will distribute the selected streams, with ETR disabled, on
the unused ETR engines. An ETR engine is considered unused if no stream with ETR enabled is
assigned to it.
The search field in the upper right corner of the view allows the user to type a text string, and the
multicast list is updated to display only streams matching the specified text.
Clicking Add new or selecting one or more multicasts and clicking Edit selected will open the
Multicast — Streams — Edit pop-up view. When multicasts have been defined, clicking Join
selected will join the selected multicasts and enable monitoring. The probe will only analyze joined
multicasts. Clicking Join all will join all multicasts in the list (up to the licensed maximum number
of channels). Unjoining one or more multicasts is done by selecting multicasts and clicking Unjoin
selected or by clicking Unjoin all.
When the Edit button is clicked it is possible to define the following multicast parameters (note
that some parameters are only relevant and selectable when the probe is equipped with the correct
options):
Address: The IP address of the unicast or multicast. For a T2MI inner stream enter
a dummy address.
Port: The port number of the unicast or multicast. For a T2MI inner stream
enter a dummy port number.
Ethernet thresholds: The Ethernet thresholds specify various error limits. Selectable Ethernet
thresholds templates are defined in the Multicasts — Ethernet thresh.
view. For a T2MI stream select a dummy threshold template.
VBC thresholds: The VBC thresholds specify various error limits to be used by Video-
BRIDGE Controller to generate alarms. These thresholds are only rele-
vant if the VideoBRIDGE Controller is used. VBC threshold templates
are defined in the Setup — VBC thresh. view.
Join stream: Check the ‘Join stream’ check box to join a multicast or unicast. Only
joined streams are analyzed. A stream may also be joined from the
Multicasts — Join or Multicasts — Streams views, and the status of
this check box will be updated accordingly.
VB330-SW 10G Software Probe User’s Manual version 6.0 93
Extract thumbnails: When enabled, the probe will generate thumbnails for this multicast. In
order to enable this option, Extract thumbnails also needs to be enabled
in the Setup — Params view
Join interface: Select which interface to join the selected multicast. The data interface(s)
are listed.
Page: For easy navigation, each stream can be assigned a specific page. The
names of the pages are defined in Setup — Pages.
Seamless Protection Switching (SMPTE 2022-7) monitors the same stream transmitted twice. The
probe verifies that the two streams combined do not have packet loss and the jitter between the
two streams. When two multicast/unicast streams are selected, the probe will report errors report
errors if the same RTP packets are missing from both streams. Errors are also reported if the timing
between the two stream exceeds the threshold settings.
SSM
SSM source 1: If a zero source address is specified for a multicast it will be joined without
a source. This allows both source specific multicasts and non-source specific
multicasts to co-exist in the same network and be joined by the VB330-SW.
SSM source 2: Additional SSM source addresses may be specified to enable back-up solutions.
Note that it is the operator’s responsibility to ensure that a multicast is only
transmitted by one SSM source at any time.
SSM source 3: Additional SSM source address
SSM source 4: Additional SSM source address
SSM source 5: Additional SSM source address
FEC
Has FEC: The stream carries COP3 (SMPTE 2022-5) Forward Error Correction. If enabled,
statistics about FEC drops and correctible errors will be reported for the stream.
L2TP (remote PHY) streams are mapped into multicasts. In order to identify the correct stream the
multicast address is entered in the General tab and the session ID of the L2TP stream is specified
here. The port number is not used, and will be shown as 0.
To identify available session IDs, join the stream first and then use the Multicasts — Detect view
to see the session IDs that are available. Both IPv4 and IPv6 is supported.
Thresholds are used to determine when to actually raise an alarm upon detection of an error. The
Ethernet thresholds are used for generating Ethernet probe alarms as well as for calculating error-
seconds. Error seconds and ETH probe alarms are issued whenever measurements exceed the
Ethernet thresholds
Name: A text string that identifies the Ethernet threshold
The MW Media Window view provides an at-a-glance status for each of the multicasts/unicasts
being monitored. From the graphs it is easy to see the jitter characteristics of the signal and if there
is packet loss or CC errors present in the signal. Periods of no signal are also displayed.
The measurements are always aggregated over a time interval – typically one second. The IAT(max)
is the maximum time measured between two neighboring IP frames within the measurement time
interval (the peak packet Inter-arrival time). IAT is expressed in milliseconds.
The MLR is the peak estimated number of lost MPEG-2 Transport Stream packets inside any second
within the actual time period. The number of lost TS packets is derived from the continuity counters
inside the TS packet headers.
A common scenario is to have 7 TS packets per UDP frame. Losing an IP packet will therefore
usually (but not always) result in an MLR of 7 (not always the case because some TS packets such
as null packets or PCR packets do not carry a valid CC field).
The patented Sencore VideoBRIDGE Media Window presents both jitter and packet loss mea-
surements in one graph, with jitter (IAT) values growing upwards (+ve Y) and packet loss (MLR)
growing downwards (-ve Y). Each sample along the x-axis corresponds to a measurement time-
interval that depends on the range of the graph selected. Periods of no sync are also displayed in the
graph.
Error-second statistics for the graph-interval is displayed to the right. As the graphs are zoomed or
scrolled the error-second statistics is updated as well as the graphs.
Tool-tip provides the exact jitter (IAT) and packet loss (MLR) values for a selected bar in a selected
graph, the denotation is IAT::MLR. The current graph value displayed under ‘Running’ provides the
maximum MLR and IAT values measured during the last 3 seconds.
By zooming and panning the user can pinpoint more accurately when errors occurred. In the above
diagram tool-tip reveals that ‘No signal’ occurred between 9:15 and 9:20.
By clicking the Popup button, a pop-up window will appear. This separate window can be used
to display the selected channel even when navigating away from the probe. This also provides the
ability to monitor media windows for several streams without starting several browser sessions.
By clicking the IAT:RTP button the graph displays the packet jitter as a function of time. The
composite graphs displays the RTP packet loss below the X-axis. If the monitored stream is not RTP
encapsulated, IAT will be represented by grey color and there will never be any indication of packet
loss in the graph.
Click the icons in the Control tab to activate or de-activate an RDP engine. There are different icons
for controlling RDP engines depending on whether they are configured to relay or record. The state
of each RDP engine is restored after a reboot.
For recordings and triggered recordings the last recording is made available in the Destination column
along with the metadata file. The metadata file contains basic information about the recording such
as the recording size, list of PIDs and CC-errors for each PID. In the case of triggered recording, the
alarm causing the recording is also included. Pressing the Delete button deletes the recording. For
triggered recordings the number of recordings is stated in the Status column. Pressing the Delete
button resets this counter. The buffer utilization is stated as a percentage and should never approach
100% for correct relaying or recordings.
Each of the RDP engines is configured separately. First the Mode is selected. Depending on the
mode either the Relay or Record settings needs to be configured. The Input selects the stream or
interface to relay or record.
These are the settings:
When mode Relay over IP has been selected, the RDP parameters are:
RDP Ethernet
When mode Record or Trigger recording has been selected the options are:
The maximum recording size depends on the amount of free disk on the probe, up to a maximum of
1500 Mbyte.
The Protocols view allows monitoring of IP traffic on the selected port in terms of the protocols
used.
The interface can be selected using the drop-down at the bottom of the page. Clicking the Clear
statistics button will reset displayed values.
The following measurements are presented, depending on which statistic is selected:
Statistics
Statistic: The protocol for which the following measurements apply
Cur bitrate: The current total bitrate for this protocol (measured over the last 1s period)
Max bitrate: The maximum bitrate during any 1s period
Min bitrate: The minimum non-zero bitrate during any 1s period
Frames/sec: Traffic speed in number of IP packets per second
Frames: Number of Ethernet frames
Frames %: Percentage of total number of frames
Min flen: Minimum Ethernet frame length
Max flen: Maximum Ethernet frame length
Bitrates
Statistic: As above
Cur bitrate: As above
Bitrates: A graph displaying the bitrate over time, displaying the last five minutes
Frames
Statistic: As above
Frames/sec: Traffic speed for this protocol expressed in number of IP packets per second
Frames: A graph displaying frames per second over time, displaying the last five minutes
Frames graph: Click the frames graph button to display a detailed frames per second graph for
the specified protocol
Interface statistics
Link status: Displays whether the interface is up or down
Link speed: Displays the interface speeds, as bits per second
Link duplex: Indicates whether the interface is operating at full or half duplex
UDP unicasts: The number of detected UDP unicasts
UDP multicasts: The number of detected UDP multicasts
COP3 Correctable: Total count of dropped payload IP packets that are correctable by the
FEC
COP3 Uncorrectable: Total count of dropped payload IP packets that cannot be corrected by
the FEC
COP3 Late: Payload or FEC packets are received slightly too late according to the
buffer model and may result in errors in another implementation of the
specifications. The number of packets with this error.
COP3 Errors: Either the L/D parameters are not consistent across the streams or
payload/FEC packets are received too late or too early according to the
buffer model. The number of packets with these errors.
The Traffic Detect view displays all UDP traffic sensed by the probe. Note that promiscuous
network mode should be enabled in the Setup — Params view for the probe to detect all traffic,
and not only multicasts already joined by the probe. Note that generally the upstream switch or
router will not output streams that are not joined by downstream equipment, i.e. usually only joined
streams will be available for monitoring.
If the unicast/multicast destination address is known to the probe (i.e. listed in the Multicasts —
Streams view) the stream’s Name is looked up, otherwise a generic name is used.
When the Traffic — Detect view is entered after probe booting, the probe will continuously try to
detect streams. Click the View list offline button to view the stream list in offline mode. Click the
Refresh button to update the stream list in offline mode.
The source address makes it possible for the probe to distinguish between multicasts with the same
destination IP address and port, provided that Source specific multicasts has been enabled in the
Setup — Params view.
If the stream is currently joined by the probe (i.e. the probe is currently monitoring the stream), the
Joined field is set to yes.
Detected streams can be added to the probe’s stream list by selecting streams and clicking the Add
selected to stream list. To add all detected streams the Add all to stream list button can be pressed.
Only streams not already in the probe’s stream list are considered. Clicking the Export button will
generate an XML-file that opens in a new window.
A drop down menu allows filtering of detected streams, making is possible to view streams of a
specific type only. Stream types are defined in the Traffic — Filter setup view. If the AEO option
is enabled for the probe the Detect list will contain the following additional columns: Mapping,
signal, RTP drops, CC errors and Bitrate. These parameters are the same as on the Multicasts page.
Please note that the Multicast scan and the Detect features are mutually exclusive, so it is necessary
to click the Exit scan mode in the Multicast scan view to resume population of the Detect list.
The Traffic — Filter statistics view makes it possible to view statistics for different stream types.
Stream types are defined by the user in the Traffic — Filter setup view.
Statistics is displayed for a time period selected by clicking one of the time duration buttons.
Clicking the icon next to each value brings up the detailed graph window.
Clicking a graph icon displays the corresponding detailed graph for the selected filter. Clicking the
trend graphs itself will bring up the same detailed graph but will plot all the filters so that they can
easily be compared.
The Traffic — Filter setup view makes it possible to define stream filter requirements affecting the
Traffic — Detect and Traffic — Filter statistics views. Ten filters can be defined and enabled by
the user.
Statfilter settings:
Name: A text string defining the filter
Enabled: Only enabled filters are in use
Streams: The number of streams matching filter requirements
Cast: The type of stream: No filtering, Only unicasts or Only multicasts
RTP: The RTP mode: No filtering, Only with RTP header or Only without RTP header
VLAN: VLAN selection mode: No filtering, Only tagged traffic, Only untagged traffic
or Require matching specified value (a specific VLAN ID).
The Microbitrate feature allows sampling of bitrate at various sampling intervals. When enabling
this feature, each Ethernet frame is timestamped in hardware on probe ingress. This timestamp is
used to calculate exact bitrates at various sampling intervals.
The Interval is the sampling interval of each bitrate calculation. There are six intervals tracked
simultaneously, the five pre-defined intervals and the user-interval. The User-interval is a user-
given sampling interval shown in the graph and used for microbitrate alarming.
The Max interval frames is the max number of frames within one interval last second. The Max
interval bitrate is the max sum of Ethernet frame sizes inside one interval last second converted to
bits per second. This number should always be bigger or equal for shorter intervals.
Click the legends in the graph to show or hide graphs.
The above graph is a typical OTT-traffic graph where the client periodically requests limited amounts
of data at maximum speed resulting in traffic that is bursting near line-speed at 10 Gbit/s for
short intervals while the average bitrate for larger intervals is only a fraction. This traffic shape is
challenging for network equipment since it demands all remaining capacity up to line speed.
• Microbitrate bursting
These alarms are both associated with the user-interval, which is a user-specified graph sampling
interval.
If the bitrate of the user-interval exceeds the Burst threshold setting, the Microbitrate bursting
alarm will be raised.
Sometimes this will yield a lot of alarms, so a second alarm has been defined. Whenever the bitrate
of the user-interval exceeds the Burst threshold for ES threshold number of seconds during the
last ES Alarm window seconds, the Microbitrate excessive ES bursting alarm is raised.
The Multicast scan feature is useful for scanning an IPv4 multicast interval to see which multicasts
are available in the network. Detected multicasts can easily be added to the stream list. The
parameters displayed are the same as in the Traffic — Detect view, please see chapter 5.7.2 for
details.
Configure the scan interval and other scan parameters in the Setup view.
Setup
Multicast range: The multicast range to scan (IPv4 addresses).
All UDP ports: Check this to disable filtering on UDP port.
UDP port range: Filter to be used for UDP port unless All UDP ports is checked.
Simultaneous joins: Number of joins performed simultaneously.
Expect traffic within (s): The probe will wait this long to determine if the multicasts joined
actually exist.
Select input: Input interface to scan.
VB330-SW 10G Software Probe User’s Manual version 6.0 119
In fast networks it is useful to increase the Simultaneous joins to a larger number.
Please note that the Multicast scan and the Detect features are mutually exclusive, so it is necessary
to click the Exit scan mode to resume population of the Detect list.
5.8 Ethernet
5.8.1 Ethernet — FSM
Full Service Monitoring (FSM) allows easy validation of any server reachable by the probe via
Ethernet. The servers may be probed by either sending an ICMP Echo Request packet (also known
as Ping) or performing an HTTP Get request.
Up to 10 services may be defined and each service will be checked at regular intervals. Any errors
will be logged. An error is defined as no reply within 5 seconds for the Ping option or no, or
incorrect, reply within 5 seconds for the HTTP option. If there are more consecutive errors than a
fails threshold value an alarm will be raised.
For convenience a manual ping field is located below the status table. By entering a valid IP address
or host name and clicking the Ping button an arbitrary server may be pinged.
The Clear all button will clear accumulated data for all enabled FSM services, but active alarms
will not be removed.
Clicking the Traceroute button will open a new window, allowing the user to trace the network
route to a specified IP address.
Each of the 10 FSM services may be defined or edited by clicking on the corresponding Edit button
in the left hand table.
The probe supports ping and generic HTTP GET protocols for online status verification of arbitrary
targets. After completing configuration of the selected service Apply changes must be pressed to
save and apply the changes.
These fields are common for both the ping and the HTTP GET protocols:
http://<IP address>: The request to send to the target, for example index.html
Expect word reply: A case sensitive word or sentence to be expected in the reply. To find a
suitable string, use the Show content link. Leave this field empty to let
the probe ignore the contents of the reply.
Last reply: The last reply Show content link points to the last HTML file that was
generated by this service.
Port: The port used by the target server, often 80 for HTTP requests
Support cookies: If enabled, the HTTP GET request will remember cookies returned by
the target and provide them in subsequent requests.
The VB330-SW has a built-in syslog server which captures all incoming messages (UDP, port 514).
Messages are displayed in a pageable grid with the following columns: Facility, Severity, Timestamp,
Hostname, Agent and Message. Currently displayed page can be exported as an XML-document.
Since the syslog server typically stores about 100 pages of messages there is a group of buttons for a
fast navigation:
Syslog server has a limited capacity which is usually enough to store the latest 10,000 messages
depending on the size of the syslog messages. When a new message arrives and no storage space
remains the oldest messages are removed.
Note that the syslog server is very sensible to time settings, so it is strongly recommended to have a
time synchronization enabled.
The IGMP view shows all IGMP (version 2 or 3) messages detected by the probe. This includes
IGMP query messages sent by routers, IGMP reply messages sent by the probe itself and IGMP
reply messages sent by other probes and devices on the same subnet.
The live IGMP page can be paused by clicking the View list offline button. The IGMP messages
can be exported as XML by clicking the Export. . . button, and the list is cleared by clicking the
Clear list button.
:
i Click the blue information icon to open the IGMP record pop-up view
The VB330-SW can make PCAP recordings on the data interface based on simple user configurable
filters. If the FLASH option is available, the recorded PCAP files can be moved to the internal hard
drive using the Data — Storage view. The PCAP format supports microsecond timing accuracy.
Incoming traffic is recorded if it matches one or more of the enabled filters while outgoing traffic is
always recorded. So for instance, to record all OTT traffic on the data interface it is sufficient to
enable the “Capture all TCP traffic” filter (since OTT uses the HTTP protocol which is always TCP).
Recording
Size: Size of current recording.
Dropped packets: Number of dropped packets due, usually caused by running temporarily
out of buffer due to too high traffic. To allow higher bitrate recordings
Capture only headers may be enabled.
Buffer use %: Current buffer utilization. At 100% the Dropped packets will start
counting.
Disk free: Remaining disk size.
Capture: The recorded capture. May be invalid if recording is still in progress.
Start recording: Click to start a new recording. This will clear the current rec.pcap file.
Stop recording: Click to stop the current recording.
Sort recorded frames At high bitrates, some Ethernet frames may be recorded out of order as
on packet time: a result of the multi-core architecture. Click to sort frames in recording
according to time-stamp.
The ETR 290 — Overview view will show ETR 290 status for ETR 290 monitored streams. ETR
290 monitoring may be enabled for Ethernet streams in the Multicasts — Streams — Edit view.
The streams currently being analyzed are highlighted and a circular progress icon shows the
monitoring progress.
The analysis time for each stream is set as part of the ETR thresholds parameters list in the ETR
290 — ETR thr. — Edit view.
The result of the different ETR 290 tests are shown as table entries in a condensed view called
MicroETR, a scaled down version of the regular ETR display, one icon representing one stream.
Green color indicates status OK whereas red color indicates an active alarm for that particular test.
A white field shows that a check has not yet been performed, usually due to lack of measurement
data, and grey indicates that a check is disabled. Tool-tip functionality allows the user to view the
name of an individual check in the MicroETR display. Let the mouse pointer hover over the field for
a moment to view the tool-tip.
When clicking one of the MicroETR icons the detailed ETR 290 status for that stream is displayed
in the ETR 290 — ETR Details view. By entering this view through the MicroETR, the view will
remain static irrespective of the round-robin looping, thus making it easy to examine one stream in
detail without interruptions. The round-robin looping and associated alarm handling will continue
in the background.
Note that it is possible to deactivate individual ETR 290 alarms by defining appropriate ETR
thresholds.
If the user wants to examine one particular Ethernet stream in more detail, he can lock the ETR 290
analysis to that stream by clicking the lock field at that stream. The round-robin operation of the
The ETR Details view shows the ETR 290 status for the current stream of the user-selected input.
The name of the current stream is displayed in addition to the two round-robin indicator icons when
relevant: the time cycle icon and the lock icon. By clicking the lock icon the round-robin tuning
process is stopped (locked to the current frequency) or resumed. A DVB, ATSC or ISDB icon
indicates the analysis mode. The analysis mode is defined as part of the ETR threshold template.
The ETR 290 parameters are grouped into five different categories. The first three groups are
defined in the ETSI TR 101 290 guidelines. The fourth category contains checks defined by Sencore
allowing CA system checks, custom PID and service checks and the Gold TS reference checks. The
last category contains checks of the input interfaces.
For each check a bulb indicates the current status of that parameter check: green indicates status
OK whereas red indicates an active alarm. When the probe has not yet received data relevant for
a particular check, the corresponding bulb is white. Grey color indicates that the check has been
deactivated (as set in ETR 290 — ETR thr. — Edit).
When clicking one of the ETR 290 parameters, details about the current status can be viewed for
that item.
The alarm graph shows the ETR alarm status over time in the form of a status timeline. The timeline
bar shows the stream status for a time span of 90 minutes, 8 hours or 24 hours as selected by
PID Details:
PID: The PID for which the following parameters apply
Current bitrate: The current bitrate measurement for this PID. The bitrate is averaged
over 1 second.
Minimum bitrate: The minimum bitrate measurement for this PID since the start of the
monitoring period. (I.e. when the probe tuned to the frequency or when
the monitoring of this frequency was restarted by the user clicking on
Clear status in the ETR 290 — ETR Details view.)
Maximum bitrate: The maximum bitrate measurement for this PID since the start of the
monitoring period.
Carries PCR: If the PID carries Program Clock Reference information, this field will
be set to Yes. If PCR analysis is enabled in the ETR threshold template
a link will be shown to bring up the PCR histogram data for this PID.
Scrambling: If the PID is scrambled, this field will show if it is scrambled with Odd
or Even control word.
The ETR290 — Services view lists the services and service components of the current stream of
the selected input.
The name of the current stream is displayed in addition to the two round-robin indicator icons when
relevant: the time cycle icon and the lock icon. By clicking the lock icon, the round-robin cycling is
stopped or resumed. A DVB, ATSC or ISDB icon indicates the analysis mode. The analysis mode is
defined as part of the ETR thresholds.
When tree nodes are selected, detailed information will be displayed on the right hand side of the
view.
If the service tree ‘Services’ top node is clicked, a summary list of stream services and PIDs is
displayed. Each service’s service ID and each component’s PID value and bitrate are displayed
together with individual PID and service bitrates.
When clicking a service, details about the service and service components will be displayed.
If a PID is scrambled this is indicated in the service tree by the color green or blue (for even and odd
scrambling respectively). A missing PID is indicated by the color red. Click on the PID to show
more details.
Click the Show thumbnail button to view a thumbnail of the selected service. Thumbnails can only
be shown for services that are not scrambled.
When clicking a service component, associated key parameters and references will be displayed.
This view shows a graphical representation of service and PID bitrates. The current bitrate is shown
as the length of the light blue bar whereas the dark blue bar represents bitrate variation, spanning
from minimum to maximum measured bitrate.
The name of the current stream is displayed in addition to the two round-robin indicator icons when
relevant: the time cycle icon and the lock icon. By clicking the lock icon the round-robin tuning
process is stopped (locked to the current frequency) or resumed. A DVB, ATSC or ISDB icon
indicates the analysis mode. The analysis mode is defined as part of the ETR thresholds.
The user may select to view a list of services and component PIDs, to view PIDs only or to view
PIDs without the null PID. This is selected by clicking the Show Services, Show only PIDs or
Show only PIDs but not NULL PID button respectively.
This view lists the PSI and SI or ATSC tables and table contents of the currently active stream of the
selected input.
The name of the current stream is displayed in addition to the two round-robin indicator icons when
relevant: the time cycle icon and the lock icon. By clicking the lock icon the round-robin cycling is
stopped or resumed. A DVB, ATSC or ISDB icon indicates the analysis mode. The analysis mode is
defined as part of the ETR thresholds.
Clicking the ‘Sections’ node displays detected tables and associated repetition rates.
Clicking a table enables viewing the table contents in a readily readable format.
The selected table entry is highlighted in the table dump. Note that values shown in the table list
may not correspond directly to the highlighted hex dump byte(s), because some of the table entries
do not add up to whole bytes.
By hovering the cursor over the items in the tree a tool-tip is displayed showing the start position of
the data in the hexadecimal dump and the length of data. Press the save icon to download and save
the raw table data on your computer.
A description of each PSI/SI table is beyond the scope of this manual, please refer to the specifications
for more information about PSI/SI.
If you get “Unknown descriptor” in the table parsing it could be that the stream contains additional
descriptors that can be enabled. Make a note of the descriptor_tag and go to Setup — ETR to
enable the parsing of the descriptor.
Or in summary mode:
The PCR jitter histogram displays PCR jitter as measured by the probe. A list of detected PCR PIDs
in the selected stream is shown together with their current and maximum PCR jitter values. A PCR
PID is selected for histogram presentation by clicking the associated table entry. The histogram
shows the number of received PCR values versus jitter. PCR jitter is by default measured as PCR-AC
for all interfaces. By creating an ETR threshold template that enables PCR-OJ and assigning this
template to a stream it is possible to select PCR-OJ measurement mode by clicking the PCR_OJ
button. The PCR_OJ measurement is not relevant for Ethernet streams.
Please note PCR analysis will be disabled if none of the PCR-AC, PCR-OJ, PCR Accuracy or PCR
Jitter checks are enabled in the ETR thresholds. So to use the ETR 290 — PCR functionality this
needs to be enabled.
The name of the current stream is displayed in addition to the two round-robin indicator icons when
relevant: the time cycle icon and the lock icon. By clicking the lock icon the round-robin cycling is
stopped or resumed. The push-buttons Zoom in and Zoom out enables rescaling of the graph. This
makes it possible to view PCR jitter values that are outside the range defined by the auto-scaling.
Clicking the Clear button will clear historical data from the histogram.
Tool-tip functionality provides information about each histogram bar: the number of samples, the
percentage of total number of samples and the jitter interval represented by the bar. For PCR
measurements to be valid it is essential that the signal be stuffed with null packets (PID 8191) to
obtain an absolutely constant bitrate. The stream info above the histogram shows if the analyzed
stream contains null packets or not. A color indicator above the PCR jitter histogram indicates
whether the signal is of constant bitrate or not, as perceived by the PCR filter in the processing
engine. Green indicates OK, red indicates that the PCR jitter measurements are not valid due to the
bitrate not being constant.
Note that PCR jitter measurements for Ethernet streams are very sensitive to packet loss, and packet
loss results in a large jitter values – often for all PCR PIDs of an MPTS.
The PCR PID list displays the following parameters:
Max jitter (ns): The maximum jitter value measured from the time the PID was selected.
Average jitter (ns): The average jitter in nanoseconds.
Bin resolution (ns): The width of the jitter interval spanned by each histogram bar.
Outside thresholds: The number of PCR values that are outside the PCR jitter thresholds
(defined by the user as part of the ETR threshold template).
Out of view: The number of PCR values that are out of the currently displayed view.
T2MI monitoring is a licensed option available for transport streams over Ethernet. T2MI is enabled
on a per stream basis, most of the information is found in this GUI extracted from the L1 current
packets in the T2MI streams. The full parsing of this information table is found in the ‘Tables’
section.
Overview:
T2 timestamp: The last received T2 timestamp. The probe supports both
relative and absolute timestamps.
Super frame index: The last received superframe index.
Frame index: The index of the last received frame.
Input streams: Indicates whether Single or Multiple Input Streams are used.
Coding and modulation: Whether the stream uses Constant Coding and Modulation or
Adaptive Coding and Modulation.
Input stream sync: The Input Stream Synchronizer (ISSY) value.
Input stream format: The format of the input stream. Will normally be ‘TS’.
Input stream identifier: The input stream identifier for the current stream.
Num TS pkt. last T2MI frame: The number of transport stream packets that was in the last
T2MI frame.
Null packet deletion: Whether null packet deletion is in use or not.
High efficiency mode: Whether high efficiency mode is active or not.
Crc Errors BB header: The number of CRC errors on the BB header detected since
the monitoring of the stream started.
Crc Errors whole packet: The number of CRC errors calculated over the whole T2MI
packet since the monitoring of the stream started.
L1 information:
T2 version: The version of the T2 spec used. Up to version 1.3.1 is supported
including T2 lite.
Type: The type of data carried in the Transport stream.
T2 lite profile used: Set to true if the T2 lite profile is used for sending power efficient
broadcasts to portable clients.
BW ext: The carrier mode (normal or extended).
S1: T2-SISO, T2-MISO or Non-T2.
S2: FFT mode and guard interval.
PAPR: The PAPR reduction mode (if any).
Pilot pattern: Pilot pattern PP1 to PP8.
TX ID availability: Should always be set to ‘No transmitter identification signals are used’.
Cell id: The cell ID for the transmitter.
Network id: The network id for this DVB-T2 network.
Clicking the blue information symbol in the PLP list will bring up more detailed information for
that PLP.
SCTE 35 is a specification which allows equipment to splice in local content at specific times, SCTE
35 is basically just the signaling mechanism the equipment uses to know when to switch from the
master transmission to insert local content. It can be used to allow insertion of local advertising at
certain points in time or to allow the local operator to insert their own programs such as local news
transmission.
SCTE 35 requires a license for the probe and also an ETR 290 engine to connect it to.
The SCTE 35 option enables monitoring of SCTE 35 events of all streams captured by the ETR
engines. It is recommended to have one ETR engine dedicated to each SCTE 35 stream to get
continuous monitoring.
If an ETR engine is monitoring a transport stream containing SCTE 35 information, the current
stream will be added to the list in the SCTE 35 view. By pressing the blue information button a
When pressing the information button for a specific event a new window will pop-up with detailed
information about the event. The pop-up will show a log of the SCTE 35 events signaled for the
specified transport stream. Splice NULL messages are not logged.
The ETR 290 — Status view shows a stream content overview linked to current alarms, making it
easy to view what services and PIDs are currently affected by errors.
By clicking any of the ‘view’, service or PID nodes, more information will be displayed on the right
hand side of the table. This information is described in ETR 290 — Services.
The Compare view is based on analysis performed by the ETSI TR 101 290 engine and only the
streams monitored by ETR will be listed.
The Compare view allows comparison of services or transport streams across different probe
interfaces. Clicking Show streams results in a list of selectable transport streams and services,
and clicking Show services results in a list of selectable services. Note that the screen is not
auto-refreshed, click the Compare tab to perform an active refresh.
One or more services or transport streams are selected by clicking and later Ctrl + clicking items
from the list. Clicking the Compare selected button will launch a condensed overview page that
allows status parameters for services or streams to be viewed side by side. Key parameters are
Stream overview shows a number of key parameters for the selected stream/service.
Stream overview
TS ID: The transport stream ID of the selected stream or the stream containing the
selected service
NW ID: The network ID of the selected stream or the stream containing the selected
service
Orig NW ID: The original network ID of the selected stream or the stream containing the
selected service
Error statistics
Total monitoring time: The total time the stream has been monitored by the ETR engine
ETR Priority 1: The time the stream has been affected by ETSI TR 101 290 Priority 1
errors
ETR Priority 2: The time the stream has been affected by ETSI TR 101 290 Priority 2
errors
ETR Priority 3: The time the stream has been affected by ETSI TR 101 290 Priority 3
errors
No signal: The time the stream has been affected by ‘No signal’ alarm
CC errors: The time the stream has been affected by ‘CC error’ alarm
Interface errors: The time the stream has been affected by ‘Interface error’ alarm
Other checks: The time the stream has been affected by miscellaneous ‘Other’ alarms
Pie charts indicate for how long the stream has been affected by errors compared to the total
monitoring time, green color representing ‘OK’ and red color ‘Error’.
Service alarm
If a transport stream is selected for comparison the Services subview displays a list of services present
in the stream. Clicking the plus icon at a service will expand the service tree, displaying the service’s
individual components. The minimum and maximum effective bitrates of a service/component are
also shown, in addition to the number of continuity counter errors and the maximum measured PCR
jitter (if relevant).
Colored PIDs indicate scrambling; blue and green representing odd and even scrambling respectively.
Note that all references to a PID will result in a PID entry, i.e. one PID may be displayed several
times in the list.
Alarm graph
The ETR details subview shows the same alarm overview as the ETR 290 — ETR Details view.
Clicking a check will open a pop-up view displaying alarm details. Please refer to the ETR 290 —
ETR Details section of this user’s manual for a comprehensive description of this view.
The ETR thresholds make it possible to define detailed conditions for ETR 290 alarm triggering on
a per-stream basis. There are seven predefined ETR threshold templates that are write-protected and
cannot be edited by the operator:
• Default
• ETSI TR 101 290
• ATSC Default
• Optimised
• IP-SPTS
• CMTS downlink
• Analog carrier
These predefined thresholds may be used when defining a monitoring configuration, but it is a
good idea to create editable copies of these threshold templates and use these copies rather than the
originals. Doing so will allow fine-tuning of parameters later on.
There are two different ways of creating user-defined thresholds. To create a new threshold template
from scratch the operator should click the Add new threshold button. A pop-up window will appear
allowing the user to define alarm conditions and set the round-robin cycling time. The default values
of the different parameters settings are in accordance with the template Default. Another way of
creating a user-defined threshold template is by highlighting one of the threshold templates already
defined and then click the Duplicate highlighted button. The copy created this way may be edited
during the fine-tuning phase of system configuration.
Deleting an ETR threshold template is done by highlighting the threshold template that should be
removed and clicking Delete highlighted. Note that if the deleted threshold template is assigned to
PAT – Minimum The minimum number of services that must be present in the PAT.
number of services: Set to 0 to disable this check. Default: 0
PAT – Allowed When this field is left blank all TS IDs are considered valid. If one or
Transport Stream IDs: more TS IDs are specified (separated by commas or as a range) only
these IDs are considered valid, and any other TS ID will trigger an
alarm. Example of a valid field: ‘100-120, 300,320’
Continuity: Enable or disable alarming of Continuity Counter errors
PMT: Enable or disable alarming of Program Map Table errors
PMT – Maximum The maximum allowed section repetition interval for the PMT tables.
interval (ms): Default according to ETSI TR 101 290: 500 ms
PMT – Minimum The minimum number of components that must be present in all
number of components: services. Set to 0 to disable this check. Default: 0
PMT – Require If enabled it requires a language descriptor to be present for all audio
language descriptors: components signaled in the PMT. Default: Disabled
Note that errors affecting individual PIDs may be effectively masked by creating suitable PID
threshold templates that are associated with these PIDs. This is particularly useful for PIDs affected
by continuity counter errors, missing PID errors and unreferenced PID errors.
PCR – Minimum The minimum interval between reception of PCR values. Nor-
interval (ms): mally this setting should be 0. Default: 0 ms
PCR – Discontinuity The maximum change in the PCR value between two adjoining
threshold (ms): PCR values (where the discontinuity indicator flag has not been
set). Default according to ETSI TR 101 290: 100 ms
PCR Accuracy: Enable or disable alarming of PCR Accuracy (PCR Jitter) errors
for OCR_AJ and PCR_OJ. PCR_OJ is not relevant for Ethernet
streams.
PCR Accuracy – Maximum The maximum allowed PCR jitter for PCR_AC measurements.
PCR_AC jitter (ns): Default according to ETSI TR 101 290: 500 ns
PCR Accuracy – Maximum The maximum allowed PCR jitter for PCR_OJ measurements.
PCR_OJ jitter (ns): PCR_OJ measurement does not apply to IP streams. Default
according to ETSI TR 101 290: 500 ns
PTS: Enable or disable alarming of Presentation Time Stamp errors
PTS – Maximum The maximum allowed interval between the reception of two PTS
interval (ms): values. Default according to ETSI TR 101 290: 700 ms
CAT: Enable or disable alarming of Conditional Access Table errors
CAT – Maximum The maximum allowed section repetition interval for the CAT
interval (ms): table. Default according to ETSI TR 101 290: 500 ms
NIT – Maximum The maximum allowed section repetition interval for the NIT Other
interval Other (ms): table. Default according to ETSI TR 101 290: 10 s
NIT – Require If enabled the probe will require that the network ID found in the
network id: NIT matches the configured value. Default: Disabled
NIT – Require If enabled the probe will require that the original network ID found
orig. netw. id: in the NIT matches the configured value. Default: Disabled
NIT – Min. The minimum number of transport streams that must be present in
num. transport streams: the NIT. Set to 0 to disable this check. Default: 0
SDT – Minimum The minimum allowed section gap interval for the SDT table. De-
gap interval (ms): fault according to ETSI TR 101 290: 25 ms
SDT – Verify If enabled an alarm will be generated if a service found in the PAT
SDT against PAT: is not listed in the SDT. Default: Disabled
EIT – Minimum The minimum allowed section gap interval for the EIT tables. De-
gap interval (ms): fault according to ETSI TR 101 290: 25 ms
EIT – Required If one or more table IDs are specified an alarm will be generated
Table IDs: if these table IDs are not present in the stream on the EIT PID.
Entries should be separated by commas, or a range may be specified.
Example: ‘78,79,80-85’ Default: Disabled
EIT – Verify that If enabled, an alarm will be raised if one or more services don’t have
present event is a present event transmitted in the EIT (i.e. no EPG for the current
transmitted program)
EIT – Check valid If enabled, an alarm will be raised if time signaled for the present
time for present event event (the current program) is not correct. The maximum offset
from the current time can be configured.
EIT – Maximum timing The maximum timing error to allow for the present event. If the
error for present event(s) current time is not inside the program start/stop times by this margin
then an alarm will be raised.
EIT – Verify that If enabled, an alarm will be raised if one or more services don’t
following event is have a following event transmitted in the EIT (i.e. no EPG for the
transmitted next program)
TDT – Require Check this checkbox if TOT presence is required. Default: disabled
TOT presence:
ATSC EIT – Maximum The maximum allowed section repetition interval for the ATSC
interval EIT–1 to EIT–1 to EIT–3 tables. Default: 5000ms
EIT–3 (ms):
ATSC EIT – Maximum The maximum allowed section repetition interval for the ATSC
interval EIT–4 to EIT–4 to EIT–127 tables. Default: 30000ms
EIT–127 (ms):
ETT – Maximum The maximum allowed section repetition interval for the ATSC
interval ETT–1 to ETT–1 to ETT–3 tables. Default: 5000ms
ETT–3 (ms):
ETT – Maximum The maximum allowed section repetition interval for the ATSC
interval ETT–4 to ETT–4 to ETT–127 tables. Default: 30000ms
ETT–127 (ms):
CA system checks – The maximum time allowed between ECM changes. Default:
Maximum ECM 25000ms
change period (ms):
CA system checks – The averaging period used to calculate EMM bitrate. Note that the
EMM bitrate average average period must be at least 20s less than the round-robin tuning
period (s): period, e.g. with a round-robin tuning period of 70s the maximum
EMM bitrate average period is 50s. Default: 10s
CA system checks – The maximum allowed control word period (the maximum time
Maximum control word that can go by without a change in the scrambling control bits for
period (ms): scrambled PIDs). Default: 25 000 ms
PID minimum Enable or disable alarming of PID minimum bitrate. The bitrates
bitrate checks: are set in the PID threshold template.
PID maximum Enable or disable alarming of PID maximum bitrate. The bitrates
bitrate checks: are set in the PID threshold template.
PID checks: Enable or disable alarming of PID presence errors, scrambling/clear
requirements and PID type checks. The checks are set in the PID
threshold template.
Service minimum Enable or disable alarming of service minimum bitrate errors. Re-
bitrate checks: quirements are specified in the service threshold template associated
with the stream.
Service maximum Enable or disable alarming of service maximum bitrate errors. Re-
bitrate checks: quirements are specified in the service threshold template associated
with the stream.
Service checks: Enable or disable alarming of service presence, scrambling/clear
required, service type, service name and service ID errors. Require-
ments are specified in the service threshold template associated
with the stream.
Service checks – Check this box to enable service ID checks against the service ID
Only allow services listed list specified in the service threshold template associated with the
in service template: stream.
Gold TS check: Enable or disable alarming for tables failing Gold TS reference
checking.
Gold TS check – When enabled an alarm will be raised for any change, including a
Also check version change in the table version number and CRC.
number and CRC:
Gold TS check – Do verification of the PAT table against the stored reference PAT
Verify PAT table: table.
Gold TS check – Do verification of the PMT tables against the stored reference PMT
Verify PMT tables: tables.
Gold TS check – Do verification of the CAT table against the stored reference CAT
Verify CAT table: table.
Gold TS check – Do verification of the SDT actual table against the stored reference
Verify SDT actual table: SDT actual table.
Gold TS check – Do verification of the SDT other tables against the stored reference
Verify SDT other tables: SDT other tables.
Gold TS check – Do verification of the BAT table against the stored reference BAT
Verify BAT table: table.
Gold TS check – Do verification of the NIT actual table against the stored reference
Verify NIT actual table: NIT actual table.
Gold TS check – Do verification of the NIT other tables against the stored reference
Verify NIT other tables: NIT other tables.
Time information check: Enable or disable alarming if there are errors in the time information
sent in the streams. Probe should use NTP time sync to use this
functionality.
Time information check – Check the time in the TDT table and alarm if it is wrong.
Check TDT:
Time information check – Check the time in the TOT table and alarm if it is wrong.
Check TOT:
Time information check – The maximum number of seconds the time information provided
Max time offset: in the stream can deviate from the probe time before an alarm is
raised.
Time information check – The maximum time without any time information before an alarm
Max repetition time: is raised.
The PID thresholds make it possible to define detailed conditions for alarm triggering on a PID or
PID type basis. There is one predefined PID threshold template that cannot be edited by the operator:
‘Default’. The ‘Default’ PID threshold template contains no PID definitions and will therefore not
alter alarming for any service.
By associating scheduling templates to checks it is possible to disable alarming at pre-selected time
intervals. Scheduling templates are defined in the Setup — Scheduling view and will be available
from a selection drop-down menu for some of the checks.
In the ‘PID Thresholds’ table, the ‘Refs’ column shows how many streams are associated with each
threshold template.
There are two different ways of creating user-defined thresholds. To create a new threshold template
from scratch the operator should click the Add new threshold template button. A pop-up window
will appear allowing the user to define alarm conditions. Another way of creating a user-defined
threshold template is by highlighting one of the templates already defined and then click the
Duplicate highlighted button.
The Service thresholds make it possible to define detailed conditions for alarm triggering on a
per-service basis. There is one predefined service threshold template that cannot be edited by the
operator: Default. The Default service threshold template contains no service definitions and will
therefore not alter alarming for any service.
By associating scheduling templates to service threshold templates it is possible to disable alarming
at pre-selected time intervals. Scheduling templates are defined in the Setup — Scheduling view
and will be available from the schedule drop-down menu.
In the ‘Service Thresholds’ table, the ‘Refs’ column shows how many streams are associated with
each threshold template. Thresholds are associated with each stream in the Multicasts — Streams
— Edit view.
Note that it is possible to create a service threshold template that allows probe alarming if a new
service appears in a stream. This is done by creating a threshold template listing the service IDs
The Gold TS reference feature is used to compare the tables in the transport stream with a set of
stored reference tables. This allows the operator to be notified of any changes in the PSI/SI tables
such as:
• A service disappearing
To use the Gold TS reference functionality, first store away tables for a stream or a set of streams.
Go to ETR 290 — Gold TS thr..
Here you can see the reference thresholds currently stored on the probe and they can be renamed or
edited.
To add new reference thresholds or update the existing thresholds click on the button named
Add/update threshold. The following dialog is then shown:
• Creating a template for all streams on a specific input (or all inputs)
When creating a template for a specific stream the table set is saved immediately. It is therefore
recommended that the ETR tuning is locked to this stream to avoid the round-robin operation from
tuning to a new frequency just before the table set is stored. It can take 30 seconds after tuning to
receive all tables.
When creating templates for all streams on an input this is done as a part of the round robin cycle at
the end if the tuning period. It can then take a while for all thresholds to be generated (or updated)
depending on the number of streams on that input.
When the reference template have been created it is automatically associated with the stream for
which it was generated.
The operation of the Gold TS reference thresholds are controlled by the ETR threshold template
associated with the stream. No settings are changed here when creating the reference templates so
this needs to be done manually by going to ETR 290 — ETR thr.
If needed a new template can be created and associated with the stream(s). Or the existing template(s)
can be changed.
Also check version By default the version number and the original CRC of the tables are
number and CRC not checked. In many systems the version number can be updated
even if no other changes are performed (for instance if a multiplexer
is rebooted). So for most cases this should be left disabled.
Verify PAT table When enabled the Program Allocation Table will be checked. This
allows the operator to catch addition and removal of services as well
as changes to the PMT PIDs used for the different services.
Verify PMT table When enabled the Program Map Table will be checked. This allows
the operator to catch lots of changes to the different services:
• Changes in frequency
• Network name
Verify NIT actual tables When enabled the Network Information Tables for the other networks
will be checked. This is disabled as default. This allows the operator
to catch changes such as:
• Changes in frequency
• Network name
The Gold TS reference checking is performed by the ETR engines and can be performed in round
All the different tables and sections monitored are listed here. If there have been any changes to the
tables the check will turn red and alarms be sent.
When the ETR engine is tuned to a stream it is possible to compare the tables for this stream with
the stored reference tables by clicking on the entry in the list. This opens up a new window where
the table data can be compared, both as a tree-breakdown and as a hexadecimal dump:
The Content — Captions view provides an overview of the closed caption status of each service.
The services that the Software Probe extracts captions from are presented in a list of services.
Thumb: Thumbnail
Name: Service name
Parent MC stream: Name of the multicast stream this service is extracted from.
#SCTE 20: Number of SCTE 20 caption services detected in this service.
#CEA 608: Number of non-SCTE 20, CEA 608 caption services detected in this
service.
#CEA 708: Number of CEA 708 caption services detected in this service.
Errors: Number of caption related errors on this service since joined.
Caption service
Press the blue information button on a service to open the caption service window. This window
gives you access to view all closed caption services, and see the alarms for this service.
The Encoder Boundary Point (EBP) monitoring is designed to monitor Adaptive Transport Streams
(ATS) carrying boundary signaling. The VB330-SW presents Presentation Time Stamp (PTS) mea-
surements and calculations for IDR frames, and EBPs following the OpenCable EBP specification3 .
Buttons in the GUI control which data is presented in the table. Parsing of the OpenCable EBP
3 Encoder Boundary Point Specification, Version I01, OC-SP-EBP-I01-130118 https://www.cablelabs.com/
specifications/encoder-boundary-point-specification?v=I01
Thumb: The thumbnails will not always be generated at the same time for all
streams in a group. This means that the thumbnails displayed in the user
interface might differ even though the streams are synchronized.
Name: The name of the stream or group. A group row will have a + or - sign to the
left of the name. This can be used to expand and collapse the group. If a
name is highlighted in the table it means that it is the reference for Group
PTS skew calculations for the group members.
Status: The EBP status of the stream or group. The colors reflect the status of the
EBP or IDR frame alarms. A group’s status will have one field per member
and show the status of all stream members. These are not in order. The
colors show the following
• Green: No active alarms
• Red: One or more alarms are active
• Grey: The stream has No signal
PTS: The latest PTS read, for the boundaries (EBP or IDR frame) depending on
the Measurement type selected.
Group PTS skew The skew between the stream’s and the group reference’s boundary PTSs.
This value is calculated based on the points that are expected to be synchro-
nized. If a stream has fallen out of sync with the group, the value is updated
continuously. The value is calculated by subtracting the reference’s PTS
from the stream’s PTS. A positive value means the PTS of the stream is
larger (later in time) than that of the reference. A negative value means
smaller (before in time). Typically the streams will share the same PTSs,
and the skew is expected to be 0.
EBP-IDR PTS diff The difference between the PTS of the packet containing the EBP, and
the PTS of the IDR frame. As the header indicates, the IDR frame PTS
is subtracted from the EBP PTS. A positive value means the PTS of the
stream is larger (later in time) than that of the reference. A negative value
means smaller (before in time). An ATS is expected to carry an EBP in
the IDR frame. In this case they have the same PTS with no difference
between the EBP and IDR frame.
PTS gap The gap between the EBP or IDR frame PTSs of the respective stream.
The table below describes the buttons found at the bottom of the page.
Measurement type: Selects which measurements are displayed in the table. The currently
selected measurement type’s button is highlighted.
Options: Encoder Boundary Points or IDR frames
Time window: Selects the time window of the gap statistics. The currently selected
time window’s button is highlighted. Time units: m = minute, h = hour,
d = day.
Options: 5m, 20m, 1h, 8h, 1d or 4d
Reset measurements: These buttons are used to reset the EBP data of the streams.
Reset selected: reset the EBP data of streams (table rows) currently
selected in the table.
Reset all streams: resets the EBP data of all streams.
How to set up EBP Opens a pop-up with a short description of how to set up the EBP
monitoring.
Setup guide
By default, the EBP and IDR frame PTS monitoring is not enabled. The setup consists of two main
steps: create content thresholds, and configure the streams. The monitoring is controlled by the
content thresholds. A stream must be assigned a content thresholds template with EBP and/or IDR
frame monitoring enabled to appear in the Content — EBP view.
Create content thresholds:
1. Go to the Content — Content thresh. view.
The Timeline view requires the Timeline option. Select Timeline from the Content tab, and the
timeline should load in the main content area.
Navigating in time
To navigate in time you have two options. Back and forth in time, and zoom in / out.
To go back and forth it time you can select the desired time from the time and date picker located at
the center top. The time and date picker is most useful for large jumps in time, like if you want to
look at data from days/weeks/months back in time. Just select the correct date and time, and the
timeline should automatically jump to that point in time.
The buttons to the left and right of the time-picker let you move in small increments in both directions,
and are most suited for smaller adjustments in time.
The last way to navigate in time is to drag the timeline in the direction you would want to move
it. The timeline should smoothly glide with the dragging motion, and new data should pop up
seamlessly.
To zoom in and out, use the + and – buttons located to the right of the filter box. Between the buttons
the current zoom level is shown. The zoom level describes how much time is shown in one box.
Persistent layout
When you are happy with the widget layout, you may save the layout by pressing the Save button on
the top of the screen and giving the layout an unique name. If you later want to update this layout,
just save with the same name, and the new layout will override the old.
Thresholds are used to determine when to actually raise an alarm upon detection of an error. The
Content thresholds are used for generating content alarms as well as for calculating error-seconds.
Error seconds and content alarms are issued whenever measurements exceed the defined threshold
levels for a parameter. The alarm level of each of these alarms is set in the Alarms — Alarm setup
view. Note that it is also possible to disable alarms in the Alarms — Alarm setup view.
The Content — Content thresh. view makes it possible to define threshold values that operate at
stream level. Thresholds are associated with each stream in the Multicasts — Streams — Edit
and OTT — Channels views. There are two different ways of creating user-defined thresholds.
To create a new threshold template from scratch the operator should click the Add new threshold
button. A pop-up window will appear allowing the user to define alarm conditions. Another way of
creating a user-defined threshold template is by highlighting one of the threshold templates already
defined and then click the Duplicate highlighted button.
Deleting a threshold template is done by highlighting the threshold template that should be removed
and clicking Delete selected. It is possible to delete or edit several entries simultaneously. Several
entries are selected by using the regular Ctrl + click or Shift + click functionality. Click the Edit
Content thresholds
Name: A text string that identifies the Content threshold
Thresholds are used to determine when to actually raise an alarm upon detection of an error. The
Content — Service thresh. view makes it possible to define detailed conditions for alarm triggering
on a per-service basis. This is particularly useful to specify individual alarm handling rules for
services in a multi-program transport stream (MPTS). Note that if there is a stream and service
threshold mismatch, the service threshold will apply. This may be the case if QoE or scheduling
requirements are set differently in the stream threshold template and service threshold template
associated with a stream. There is one predefined service threshold template that cannot be edited
by the operator: Default. The Default service threshold template contains no service definitions and
will therefore not alter alarming for any service.
By associating scheduling templates to service threshold templates it is possible to disable alarming
at pre-selected time intervals. Scheduling templates are defined in the Setup — Scheduling view
and will be available from the schedule drop-down menu.
In the ‘Service Thresholds’ table, the ‘Refs’ column shows how many streams are associated with
each threshold template. Thresholds are associated with each stream in the Multicasts — Streams
— Edit view.
There are two different ways of creating user-defined thresholds. To create a new threshold template
from scratch the operator should click the Add new threshold group button. A pop-up window
will appear allowing the user to assign a name and value to the new threshold and define the alarm
conditions. Another way of creating a user-defined threshold template is by highlighting one of the
templates already defined and then click the Duplicate selected button.
Deleting a service threshold template is done by highlighting the template that should be removed
and clicking Delete selected. Note that if the deleted threshold template was assigned to a stream
being monitored, the new threshold template for that stream will default to the Default template.
The Content — Setup view is used to configure storage and display parameters for the Timeline.
The individual streams that should be archived and made available in the Content — Timeline view
are configured using the Content — Content thresh. view.
By default, all streams available in the Timeline database are available in the selection drop-down.
If services have undergone many renames, the Shown/hidden streams view can be used to select
which streams should be available.
Use Show joined streams to move all streams that are currently joined to the Shown streams
list. Use Hide unjoined streams to move all streams that are currently not joined to the Hidden
streams list.
Timeline storage
Storage capacity warning threshold: This defines the amount of free space that should
be available on the file system holding the Timeline
database before a warning is issued.
Archiving of data types not marked as critical is sus-
pended when the free space goes below this threshold.
When you get an alarm saying the disk is getting full,
you can change the configuration to keep it for a shorter
duration, or add more disk to the server.
192 VB330-SW 10G Software Probe User’s Manual version 6.0
Minimum storage capacity required: This value is the amount of free space that should
be available on the file system holding the Timeline
database for any data to be stored in the database.
This value is set to five percent or fifty gigabytes,
whichever is lowest.
Current free storage: This shows the currently available free space on the file
system holding the Timeline database.
Timeline durations
Duration: For each supported data type, this selects for how long data is retained in the Timeline
database.
Critical: If a data type is set as critical, it is still stored in the Timeline database if the amount
of free space drops below the warning threshold, as long as it is above the minimum
storage capacity required value.
The Status view displays the status of the redundancy switches. The Redundancy switch list on the
left side gives an overview of all the switches.
Active: The arrow indicates which input is currently selected as the output.
Name B: Displays the name of the stream on input B (even numbered ETR engine). To the left
of the name is a bulb showing the ETR290 alarm status.
The field also provides the following information:
• Bold text indicates that the stream is the currently selected as the output.
• An empty field together with Name A displaying “switch inactive” means that
one or both of the ETR engines are not in use.
• “setup error” is displayed if there is a setup error. Opening the respective
switch information will give more details.
Mode: The operation mode, described in section 5.11.4, set for the switch
A = Auto, M = Manual, S = SuperLocal
To the right of the Redundancy switch list, more detailed information about a switch is displayed.
This is information about the redundancy switch currently selected in the switch list. A switch can
be selected by clicking the respective list entry. The following information is displayed:
The Switch setup view shows the current setup of all the switches. Using this view is the most
effective way to edit the setups of the redundancy switches. Multi-edit functionality makes it possible
to edit several setups simultaneously. Highlight the setup list entries that should be edited and click
the Edit selected button. The link in the Edit column can be used to edit the setup on that specific
row.
Any setting can be set from the setup page regardless of current mode etc. The probe does not have
a way to read the status from the external device. The Setup view can be used to manually sync the
VB330-SW probe’s switch settings to the settings of the external device.
The Integration view is used to set the parameters needed to integrate with the external switching
device. IP redundancy switching is currently supported on the DMG 4000. The following parameters
are supported:
Integration parameters
IP address: IP address used to reach the external switching device.
Port: Port used to connect to the external device.
Access URL: Path to control API.
Username: Username used to authenticate against the external device.
Password: Password used to authenticate against the external device.
Modes
Auto: Switching between the inputs is done automatically based on the user defined
alarm setup. A switch is triggered when the active stream has an active alarm
while the inactive stream is alarm free. The return delay specifies a period of time
following an automatic switch where a new automatic switch cannot be triggered.
VB330-SW 10G Software Probe User’s Manual version 6.0 197
Manual: An action from the user is required to switch. The switching can be performed
using the Manual control buttons in Redundancy — Status, editing the setup in
Redundancy — Switch setup or through the Eii.
SuperLocal: The redundancy switches can only be controlled through the web GUI. Control
through Eii is disabled. Use this mode to disable externally triggered switches.
2. Open the edit popup of the multicast you want to couple with a redundancy switch.
5. Assign the multicast to the ETR engine of the switch you want it to be coupled with:
In the "ETR" tab, set "Selected ETR engine" to the number of the ETR engine. Only a single
multicast can been assigned to ETR engines used for redundancy switching.
6. If the switch will use the Auto mode, set the ETR thresholds:
In the "ETR" tab, select the ETR thresholds using the "ETR thresholds" drop-down. How to
set up the ETR thresholds for redundancy switching is described in the next section (ETR
thresholds for automatic switching).
7. The multicasts will be listed in the Redundancy — Status view’s Redundancy switch list. If
the name of the multicast is not in the list, make sure that the options mentioned in points 3–5
are set correctly. Redundancy switch list error texts are described in chapter 5.11.1.
An automatic switch can be triggered by an alarm when the alarm is enabled and has the Redundancy
checkbox checked in the ETR threshold. If an alarm should be reported, but not trigger a switch, it
should then be enabled with the drop-down menu and not have the Redundancy checkbox checked.
Setting up ETR thresholds:
1. Go to the ETR 290 — ETR thr. view.
2. Create a new threshold or open an existing one for editing.
This will open the pop-up seen above.
3. Enable the alarms that should be reported for the stream:
Select "Alarm" in the Setting column of the alarms.
4. Allow automatic switching on alarms:
Check the checkbox in the "Redundancy" column of the alarms.
5. To assign the ETR thresholds to multicasts, follow the steps describing how to couple multi-
casts to redundancy switches in the previous section.
The Setup — Params view is used to configure basic parameters for the Software Probe. This page
is displayed by default when accessing the web interface, until the configuration has been saved by
clicking the Apply changes button.
Various
Probe name: Each probe can be assigned a user defined name. It is part of the probe’s
MIB. The name is shown in the Main — Summary view, which is the
probe default page, as well as in the browser’s title line.
The name is also used for identifying the system when activating the
license on-line, see G Appendix: On-line License Activation for more
details.
Organization: The name of the organization (usually the company name) that is running
the probe. This name is only used for identifying the system when
activating the license on-line.
Probe contact: The probe contact is part of the probe’s MIB, and this parameter is relevant
for SNMP use only. It is used to identify the contact person responsible
for this probe.
Probe location: The probe location is part of the probe’s MIB. It is used to identify the
physical location of the probe. The probe location is also shown in the
Main — Summary view and in the browser’s title line.
This name is also used for identifying the system when activating the
license on-line.
Alarms
Freeze log when full: When enabled the alarm list will freeze when full (an event
will show that it is full). When the list is full new alarms are
ignored until Clear alarms is pressed.
This can sometimes be useful if a unit is placed unattended.
Treat Ethernet events as alarms: When enabled each event is treated as an alarm that is active
for ten seconds. This may be useful when reporting to
external systems that do not support events but only active
or cleared alarms. This setting affects the local alarm list
and SNMP traps.
Network settings
Enable SAP discovery: When enabled, the Software Probe makes streams announced
using the Session Announcement Protocol available through
the Multicasts — SAP view.
Enable IGMPv3 support: Required for probe to support the IGMP v3 protocol. Should
always be enabled in networks that support IGMP v3.
Gap between joins (millisecs): When monitoring a lot of multicasts, sending join requests
for all of them at the same time may overload the network
infrastructure. This setting specifies the minimum time, in
milliseconds, between join requests.
Time zone
SNMP
Community string: The probe SNMP community string can be changed.
Trap destination 1–3: SNMP traps will be sent to the specified destinations. Set to 0.0.0.0 to
disable SNMP trap transmission.
Year in trap time If enabled, dates in SNMP traps include the year number.
The Setup — Pages view allows names to be associated with different pages. Individual multicasts
can be assigned to different pages in the Multicasts — Streams view, to facilitate easier navigation
in the different Multicasts views.
The page names for OTT channels are configured using the OTT — Settings view.
The Setup — Colors view allows the user to define colors that should be recognized if a color-freeze
condition should occur. A mono-colored freeze frame condition may in some cases indicate what
equipment is failing, resulting in the color-freeze.
A freeze color is defined by clicking the Add new color button and assigning an RGB value to a
name. A maximum of four colors may be defined. An existing color may be modified by clicking
the associated Edit link.
Edit color
Name: The color name. This name will be part of a color alarm description and the
associated SNMP trap.
Description: A description of the color or an error indication.
Color: The RGB color on the format #XX(Red)XX(Green)XX(Blue) where XX repre-
sents a hexadecimal figure spanning 0-255 in decimal notation. If supported by
the browser, clicking the color should pop up a color selection dialog.
The VideoBRIDGE Controller can automatically detect the Software Probe and add it to the VBC
equipment list, provided that the auto-detect functionality is enabled and the VBC server address is
known to the VB330-SW. Note that the network must be transparent to traffic between the VBC
server and Software Probes for auto-detection to work.
The VBC server’s host name may be typed in the VBC server address field. The IP address associated
with the DNS name will be displayed. If host name lookup fails, it is necessary to type the VBC
server’s IP address. Host name lookup is only performed if auto-detect is enabled.
When changes have been made in the Setup — VBC view, click the Apply button for changes to
take effect.
By default, there is no access control and all users have access to all features. When access control is
activated, anyone with access to the VB330-SW will first be presented with the login view, requiring
the user to log in before being able to access the user interface.
Log-in is performed by providing the correct username and password. The default user name and
password to is admin and elvis. The operator may define a new password that should be easy to
remember. The password for the “admin” user is configured in the Setup — Security — Password
view.
Note that when logged in from the VBC, the VBC user’s access rights apply.
4 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/
sec-using_firewalls
The Setup — ETR view allows the user to select miscellaneous ETR handling modes.
If the locking mechanism works in a time limited mode a clock icon (see image above) is superim-
posed on the regular lock icon in the different ETR 290 subviews. When the specified lock time is
out the round-robin cycling will resume. When ETR tuning control parameters have been changed,
click the Apply button for changes to take effect.
ETR details
The user selects if service names should be displayed in the ETR 290 — ETR Details view. Note
that a large screen size is required for proper service name displaying.
It is possible to extend EIT analysis to include EIT schedule, however this is not recommended
except for ad-hoc troubleshooting, as analysis of EIT schedule can be extremely demanding
on probe processing resources. If full-time monitoring of all EIT information is required,
dedicated probes should be used for this task.
Table IDs are specified as a comma separated list, or alternatively an ID range can be defined, e.g.
78, 80–95.
SCTE 35
The Log time_descriptor messages setting determines whether the SCTE35 messages containing
nothing else than a time_descriptor should be included in the log of SCTE35 messages. In some
systems there are a lot of these messages (they can be used as keep alive messages to ensure that there
always is some traffic on the SCTE35 PID). If the SCTE35 log is filled up with the time_descriptor
messages disable logging of these messages.
The VBC error second thresholds are used by the VideoBRIDGE Controller to issue VBC specific
alarms. The VBC will raise an alarm when the number of error seconds exceeds the error seconds
threshold. The VBC thresholds are only relevant when a VideoBRIDGE Controller is part of the
monitoring system.
The reason for using error second thresholds is to avoid alarms that toggle on and off, which for a
large monitoring system might otherwise lead to an unintelligible user interface. The VBC thresholds
will allow masking of minor error incidences thus resulting in a control system GUI that presents
persistent alarms only.
The VBC error second thresholds are specified as the number of seconds affected by an error
situation. These thresholds refer to a monitoring window of one hour, meaning that if the number of
error seconds summed over any one-hour period exceeds the associated error second threshold an
alarm will be raised by the VBC.
The Setup — Scheduling view enables definition of scheduling templates which are associated
with PIDs or services using the PID threshold or service threshold template system. For content
alarms, they can also be associated with multicasts or services using the stream content monitoring
configuration. This way it is possible to mask alarms during selected time intervals, e.g. due to
maintenance.
In the Schedule list table the ‘Refs’ column shows how many references exist for each scheduling
template. References to scheduling templates may be found in PID, service and content service
threshold templates, and in the stream content monitoring setup.
The search field in the upper right corner of the view allows the user to type a text string and the
schedule list is updated to display only scheduling templates matching the specified text.
The predefined scheduling templates Never and Always result in alarms being masked never or
always, respectively. A new scheduling template is created by clicking the Add new schedule
button. It is also possible to copy an existing scheduling template by highlighting a schedule template
and clicking the Duplicate selected button. The alarm masking intervals are defined for individual
week days or for all week days. Intervals are specified on the form hhmm–hhmm, for instance
the interval 1200–1400 means that alarm masking should start at noon and finish at 2 pm. Several
alarm masking intervals may be specified for each day using comma separation. To edit an existing
scheduling template, highlight it and click the Edit selected button. To delete a template, highlight
it and click the Delete selected button.
When a scheduling template has been modified, click the Apply changes button. Defined scheduling
templates become available as selections in the Multicasts — Streams — Edit — Content, ETR
290 — PID thresh. — Edit, ETR 290 — Service thresh. — Edit and Content — Service thresh.
— Edit views.
The Setup — Routing view allows users to override the default interface for out-going probe traffic.
To override the default interface for one or more types of traffic select the interface from the
drop-down menu and click the Apply changes button.
Note: When monitoring both multicast (UDP) and OTT (TCP) traffic, we recommend using different
network interfaces. Mixing the two traffic types on the same network can have unwanted impact on
the monitored signals.
Routing setup
Default This setting determines the default interface.
IP monitoring Defines the interface to use for the multicasts specified in the Multicasts —
Streams view. The available interfaces depend on the probe license.
OTT Interface to use for OTT channels specified in the OTT — Channels view.
Note that routing for Full Service Monitoring (FSM) is selected in the Ethernet — FSM — Setup
— Edit view.
5.12.11Setup — Security
The Setup — Security view is a restricted section where only the administrator should have
access, making it possible to disable selected communication protocols to increase safety against
unauthorized access to the Software Probe.
To access this view, you have to be logged in. If probe access control has been disabled, you will
need to visit Setup — Login first. The default user name and password to enter this view is admin
and elvis. The password is changed in the Setup — Security — Password sub-view.
To change the parameters in this view, you need to access the VB330-SW user interface directly,
they are not available when logged in through the VBC.
Security parameters
Enable SNMP: If SNMP is disabled, no MIB is available on port 161. However SNMP traps
are sent as usual on port 162.
Defaults to on.
The Setup — Security — Authentication view makes it possible to restrict access to the VB330-
SW user interface by requiring the user to log in first.
Authentication method
Disabled VB330-SW authentication is disabled, and no login is required when accessing
the VB330-SW from a web browser. The Software Probe is seamlessly accessible
from the VideoBRIDGE Controller.
This is the default setting.
Tacacs+ VB330-SW authentication is enabled.
When accessing the VB330-SW with a web browser, users needs to authenticate
themselves with a username and password. These need to match the pre-defined
admin user, a user available on the Tacacs+ server configured through the Setup —
Security — Tacacs+ view, or any of the users configured in the Setup — Security
— Local users view.
Local users VB330-SW authentication is enabled.
When accessing the VB330-SW with a web browser, users needs to authenticate
themselves with a username and password. These need to match either the pre-
defined admin user, or any of the users configured in the Setup — Security —
Local users view.
If authentication has been enabled when accessing the VB330-SW through the VideoBRIDGE
This view is used to configure a Tacacs+ server for user authentication. For this to be used, Tacacs+
authentication must be selected in the Setup — Security — Authentication view.
To use Tacacs+ authentication, the IP address of the Tacacs+ server must be specified, along with
the secret key used to encrypt the communication between the Tacacs+ server and the VB330-SW
server. The same key must also be specified as part of the Tacacs+ server configuration.
We recommend using HTTPS when using authentication, as this combines authentication with
encryption. Using authentication with HTTP is not considered very secure since it is possible to
sniff the un-encrypted communication and possible reverse engineer the scrambling of login details.
Tacacs+ parameters
Server IP address IP address of the Tacacs+ server used for authentication.
Secret Configures a fixed string used to encrypt the communication with the server.
Default local user Defines the local user ID that should be used on successful Tacacs+ authen-
tication.
Auth-key Defines which key in the Tacacs+ authentication response to use to determine
the user access level. The value of this key is compared to the Access level
below.
Access level 1–3 Up to three different Tacacs+ access levels can be configured to map to
different local user accounts, allowing different authenticated users to have
different access levels.
The value configured here is matched with the value of the Auth-key con-
figured above.
This view is used to configure local users that are allowed to access the VB330-SW user interface.
For these to be used, Local users authentication must be selected in the Setup — Security —
Authentication view. The VB330-SW supports up to 30 local users.
In addition to the users defined here, the predefined “admin” user can also log in. The password
for the “admin” user is configured in the Setup — Security — Password view. Note that the login
requirements towards the Security tab is independent of the general authentication and always
requires the login of the admin user.
It is not possible to see which user is actually logged in to the VB330-SW, as this information is not
kept or used by the probe.
Edit user
Enabled If this is checked, the user is allowed to log in.
Name User-name of the account used to log in.
Password Password of the account used to log in.
Read-only If this is checked, the user only has read-only access to the user interface.
When read-only access is activated a READ-ONLY access message is displayed
under the alarm list. To change any parameters, the user needs to log out and then
log in as another user.
The Setup — Security — Password view is used to change the password used to access all
of the Setup — Security section. The password is changed by entering a new password and
clicking the Apply changes button. If authentication has been enabled in the Setup — Security —
Authentication view, the password defined here can be used with the special username “admin”.
The password defined here controls access to the VB330-SW user interface. The administrative
interface uses the system accounts, please refer to chapter 3.5 for details.
5.13 Data
5.13.1 Data — Configuration
The software section allows the Software Probe to be upgraded to a newer software version. Select
the .tea file from the local PC and click Go! to copy the software to the VB330-SW. When the
upload is complete, clicking the Update software button will begin the upgrade procedure.
Upgrading to a new major release requires a valid software maintenance license, please refer to
H Appendix: Software Maintenance for more details. If the current software maintenance license
does not cover the uploaded software version, the upgrade will be aborted and the current version is
kept.
It is possible to upload parser files to the probe adding support for private descriptors. Private
descriptors should be enabled (in the Setup — ETR view).
Contact Sencore for more information about private descriptors.
The External integration interface (Eii) allows inclusion of Sencore VideoBRIDGE equipment
into 3rd party NMS systems. In order to facilitate integration the Data — Eii view allows export
of XML files containing the data typically being requested by an NMS system via the regular Eii
interface.
Please refer to the document Eii External Integration Interface for detailed information about
Eii.
The FLASH option allows the internal hard drive to be used for storing recordings. RDP recordings
made from the RDP — Control view are automatically stored and can be retrieved from here.
PCAP recordings made from the Ethernet — PCAP view can also be stored for later retrieval.
When a PCAP recording is available, clicking the Transfer files button copies it to the persistent
storage area.
The probe will generate system information messages when the storage has less than 10 % free
memory. When the storage is full, a system error is generated. These are configured in the Alarms
— Alarm setup view.
This view shows the software version, the software build date and the version of the underlying
operating system for the Software Probe.
The License view displays the currently active license. The license includes the available Software
Probe options and software maintenance details. By clicking the blue information icon associated
with each option it is possible to view option details.
The Software Probe supports two different licensing schemes, on-line licenses and classic licenses.
When using a classic license, product and software maintenance license keys are tied to the hardware
key, which is the shorter of the two keys presented, in a non-transferable manner. The license is
installed once, and can also be exported in XML format from this page. The classic keys can be
imported using the Data — Configuration view.
When using an on-line license, the key is activated periodically towards a license server. The key is
transferable between systems running the same software, but only as long as on-line activation is
supported. The longer system identifier is used to identify the system. The Current license field
will display information on when the license key was last activated. Click the Renew button to
immediately renew the license with the license server.
Please refer to G Appendix: On-line License Activation for more information on how to use on-line
licenses. This appendix also describes how to renew the license when the Software Probe cannot
connect to the Internet.
Please refer to H Appendix: Software Maintenance for more details on software maintenance
licenses.
Click the Manage server link to access the Cockpit administrative interface, see chapter 3.5 for
more information.
To disable the Software Probe, uncheck the Activate software checkbox and click the Change
button. You cannot do this if it has been set as the default software through the administrative
interface (which is done by default the first time you activate the software), you will need to remove
it as the default before disabling Software Probe. See chapter 3.11 for more details.
Demo license
Entering a demo license key pair will start a trial period during which the features defined in the
demo license are available. Once the trial period ends, the VB330-SW will revert back to the
previous license. The time remaining is indicated in the License details page.
To end a trial period manually, enter a valid permanent license key.
The Technologies view lists some of the technologies available in the Sencore VideoBRIDGE
product family.
This view shows information about the software included with the Software Probe.
• TS sync
• Sync byte
• PAT
• Continuity
• PMT
• Missing PID
The VBC GUI has functionality for searching for all Software Probe alarms that have corresponding
VBC alarms. This makes it easier to find the cause of an VBC alarm.
Ethernet measurement data are sent from the VB330-SW Software Probe together with Ethernet
error-second threshold values (as set in the VB330-SW Software Probe Setup — VBC thresh.
view). The VBC monitors the error seconds for each parameter and will raise an alarm provided that
the error-seconds figure exceeds the threshold value, as monitored during the windowing period.
VBC
Alarm
Settings
VBC
Probe
Sequence Effect
. . . , 10, 11, 12, 13, 14, 17, 18, 19, . . . Monitoring page: RTPdrop:+2
2 dropped packets (15-16) Alarms & events: RTP Packet drop: 2
. . . , 10, 12, 13, 16, 17, 18, 19, . . . Monitoring page: RTPdrop:+3
1 and 2 dropped packets (11, 14-15) Alarms & events: RTP Packet drop: 3
Monitoring page: RTPdrop:+2
. . . , 10, 11, 15, 12, 14, 16, 18, 19, . . . Monitoring page: RTPooo:+1
2 dropped packets (13, 17) Monitoring page: RTPlag: 3 (at least)
1 out of order packets of order 3 (15 → 12) Alarms & events: RTP Packet drops: 2
Alarms & events: RTP out of order packets (lag:3)
PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51
CC: 1 CC: 6 CC: 2 CC: 7 CC: 3 CC: 8 CC: 4 CC: 9 CC: 5 CC: 10
PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51 PID: 50 PID: 51
CC: 6 CC: 11 CC: 7 CC: 12 CC: 8 CC: 13 CC: 9 CC: 14 CC: 10 CC: 15 ...
When the Transport Stream reaches our imaginary head-end some packets (those with red frame)
have been lost (maybe due to a bad satellite connection). Our IP-Streamer packs 7 and 7 MPEG-2
TS packets into each UDP-frame (mapping is 7TS/UDP) and the resulting frames may look like:
...
Sequence Effect
UDP packet #1 (7 MPEG2 TS packets):
PID 50: 12, 13, 14, 15
PID 51: 1, 2, 4, 5, 8 Monitoring page: CCerr:+2
PID 51 has 2 CC discontinuities of 2 (2 → 4)
and 3 (5 → 8)
UDP packet #2 (7 MPEG2 TS packets):
PID 50: 4, 5, 6, 7
Monitoring page: CCerr:+1
PID 51: 9, 10, 11
PID 50 has 1 CC discontinuity of 6 (13 → 4)
Alarms & events:
CC skips:9 discontinuities:3
If no more CC-errors for at least 1 second
Depending on the thresholds you may also get: MLR
>= warning-threshold (9 >= 1)
There were 9 TS packets missing (with red frame) and the alarm reflects this.
If a UDP packet goes missing after it has left the router it will visually affect both the IAT and MLR
for CBR streams. The pink line represents one elementary measurement.
For VBR streams a similar packet-loss will not necessarily affect the IAT graph even if the time
between two neighboring packets doubles. The pink line represents the IAT and MLR value measured
for the missing packet.
The pink line indicates a packet loss of 6 or 7 and a doubling of the jitter component.
A UDP packet-drop will usually show up in the MLR value as a multiple of the mapping value; for a
mapping value of 7 TS packets into each UDP packet, the MLR component will be equal to 7, 14,
21 etc.
Slightly lower values such as 6, 13, and 20 can be expected if a missing UDP packet did contain one
TS packet without continuity counter (i.e. a PCR packet with no payload).
As we have seen, there is no sure way to distinguish between UDP packet-loss and loss in the
underlying TS packets. One way to deal with the situation is to have a probe doing zero readings
close to the signal source before the network can introduce UDP packet loss.
The profile health bar displayed at channel level shows an overview of current status for individual
channel profiles. Different colors indicate status:
• Green: OK
• Yellow: Warning
• Orange: Error
• Red: Major
• Black: Fatal
All enabled alarms may affect the profile health bar, and alarm severities can be assigned to each
alarm in the Alarms — Alarm setup view.
Select the interface to be edited and then select Edit. . . from the menu.
1 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/getting_
started_with_cockpit/
2 If
the nmtui tool is not available on your system, you can install it by issuing the command yum install
NetworkManager-tui
3 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_
Guide/sec-Networking_Config_Using_nmtui.html
Selecting Automatically connect will ensure the interface is connected next time the system boots.
Sometimes it is desirable to select Never use this interface for default route, particularly if
additional interfaces are only used for monitoring multicast traffic or when setting up a native
interface for adding VLANs.
To add a VLAN interface from nmtui main menu select Edit a connection followed by Add. Scroll
to the bottom of the list and select VLAN:
After entering the configuration for the VLAN interface select OK to return the previous menu, then
select Back and finally Activate a connection to activate the newly created VLAN interface.
Installing packages requires an active Internet connection. If you are using Red Hat Enterprise
Linux, you will need an active subscription to install packages.
1 https://wiki.centos.org/HowTos/Https
2 https://certbot.eff.org/lets-encrypt/centosrhel7-apache
3 https://wiki.apache.org/httpd/RewriteHTTPToHTTPS
4 https://wiki.apache.org/httpd/RedirectSSL
Setting the VBC IP address in the Setup — VBC view will automatically add it as a time synchro-
nization source.
For more details on configuring the date and time settings, please refer to the System Administrator’s
Guide, chapters Configuring the Date and Time1 and Using chrony2 .
1 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_
Administrators_Guide/chap-Configuring_the_Date_and_Time.html
2 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_
administrators_guide/ch-configuring_ntp_using_the_chrony_suite
Please make sure you have the license key available before you release the license, as you must
enter it again on the system you wish to transfer the license to. The license key is not displayed
in the VB330-SW user interface.
If you have lost the license key, contact your dealer to retrieve it. Make sure you include all
details from the About — License view in your request.
When the Software Probe sends the on-license activation over the Internet, it includes some basic
information to verify the Software Probe. This includes a basic hardware footprint, as well as parts
of the SNMP identification data configured in the Setup — Params view.
G.2 Requirements
The VB330-SW needs to be able to contact the license server either directly or via a proxy server,
as described below. If proxy connectivity also is not available, an off-line activation procedure is
available as well.
The VB330-SW must also be configured with a correct date and time. Please refer to F Appendix:
Enabling NTP time synchronization for more information on configuring time synchronization.
Follow the steps described in the dialog to renew or activate the license. To abort the procedure,
click the License details button to return to the previous screen.a
First, download the license request document from the Software Probe to the computer you are
browsing from. Once the file has been downloaded, connect the computer to the Internet if not
already connected, and open the link to the off-line license manager2 .
1 https://tinyproxy.github.io/
2 https://license.microanalytics.org/offline
3. Transfer the image to the probe using the software upload functionality in the Data —
Software view or by using ssh, and save the new software image on the system.
Note that the probe will restart when the new software has been installed, and the probe’s user
interface will be unresponsive until restart has completed.
cd /path/to/download
cp filename.tea /var/opt/btech/probe
/opt/btech/probe/bin/vprobe_upgrade
Google Chrome: Settings — Advanced — Clear browsing data — Cached images and files
Mozilla Firefox: Options — Privacy & Security — Cached Web Content — Clear Now
Microsoft Edge: Settings — Clear browsing data — Choose what to clear — Cached data and files
1 https://www.chiark.greenend.org.uk/~sgtatham/putty/