Newtec Dialog Monitoring Guide
Newtec Dialog Monitoring Guide
User Guide
Version 1
November, 2023
© 2023 ST Engineering iDirect (Europe) CY NV and/or its affiliates. All rights reserved.
Reproduction in whole or in part without permission is prohibited. Information contained herein is
subject to change without notice. The specifications and information regarding the products in this
document are subject to change without notice. While every effort has been made to ensure the
accuracy of the statements, information and recommendations in this document, they are provided
without warranty of any kind, express, or implied. Users must take full responsibility for their
application of any products. Trademarks, brand names and products mentioned in this document are
the property of their respective owners. All such references are used strictly in an editorial fashion
with no intent to convey any affiliation with the name or the product's rightful owner.
Table of Contents
For details about accessing the monitored metrics and statistics via API, refer to the
Newtec Dialog Monitoring API Description
A caution message indicates a hazardous situation that, if not avoided, may result in
minor or moderate injury. It may also refer to a procedure or practice that, if not
correctly followed, could result in equipment damage or destruction.
A hint message indicates information for the proper operation of your equipment,
including helpful hints, shortcuts or important reminders.
The Dialog platform fully manages all aspects of a service: bandwidth usage, real-time
requirements, network characteristics and traffic classification. The platform offers these services
with carrier grade reliability through full redundancy of the platform components.
The Dialog platform supports multiple traffic types, such as the following:
• Video and audio
• Data
• Voice
• Data casting
The core of the Dialog platform is the Hub, which is located at a physical gateway site. A Dialog
platform can consist of one or more hubs, located at one or more gateways.
A hub consists of one or more Hub Modules. A hub module contains all hardware and software
required for aggregating and processing traffic of one or more satellite networks.
• The NextGen Hub Infrastructure is suited for very large networks and provides full flexibility and
scalability. It can serve up to 18 satellite networks. It is the combination of one or two baseband
hub modules and one processing hub module:
– The baseband hub module holds the RF devices. It is also referred to as DBR2100 .
– The processing hub module holds the processing servers. It is also referred to as
DCR2000. The DCR2000 is deployed on the Common iDirect Deployment Infrastructure or
CIDI.
Equipment redundancy is supported for all devices in the hub module. A hub module may be
implemented fully redundant, non-redundant or partially redundant.
The Terminal is the equipment located at the end-user’s site. It consists of the outdoor unit
(antenna, LNB and BUC) and the indoor unit, i.e. the modem.
A hub module is connected to an IP backbone at one side and to an RF interface at the other side,
establishing the Satellite Network.
A satellite network is associated with forward link capacity from one physical or virtual (in case of
DVB-S2X Annex M) forward carrier and with the corresponding return link capacity. The forward link
is based on one of the following technologies:
• DVB-S2
• DVB-S2X
• DVB-S2X Annex M.
The return link supports multiple return link technologies:
• HRC Mx-DMA
• MRC Mx-DMA
Network Resources are configured on top of the physical satellite networks and are isolated from
each other using VLAN identifiers. Dialog provides end-to-end network connectivity for three types
of networks:
• Layer 3
• Layer 2
• Multicast
Layer 3 network resources consist of one or more virtual networks. A layer 3 virtual network is an
isolated IPv4 or IPv6 network. Devices within the same virtual network can directly communicate
with each other. A virtual network can independently use its own addressing scheme and the same
addressing schemes can be reused in different virtual networks.
Layer 2 network resources consist of one or more point-to-point virtual connections. A layer 2
point-to-point virtual connection can be considered as a virtual Ethernet pipe, which establishes
isolated communication between two devices.
A multicast network connects an uplink network on the hub side with one or more LAN networks on
the modem side. This consists of a single multicast routing instance providing unidirectional routing
of multicast IP traffic from the uplink network to the modem LAN networks. The MC network can
therefore be compared to a multicast router.
The Dialog platform is managed through a single Network Management System or NMS. The
NMS can be embedded in a hub module or it can be a standalone hub module, which is deployed on
a Common iDirect Deployment Infrastructure or CIDI.
The NMS provides a unified management interface to monitor, manage and control the Dialog
platform. It serves as a single point of access and embeds the following configuration and
management interfaces:
• Satellite resources
• Network resources
• Service and classification profile management
• Terminal provisioning
• Fault (alarms) and performance (metrics) management
DataMiner®
Dialog's initial fault and performance management system fully relied on DataMiner® for metrics
collection, processing and visualization. DataMiner (DMA) delivers out of the box support providing
drivers for devices to monitor such as Linux servers, Cisco devices and ST Engineering iDirect
equipment. The DMA driver polls the data from the devices or virtual machines and stores them in
the DMA database. DMA is an integral part of the NMS.
Because the DataMiner data is inherent to the NMS platform, you can use all NMS functionality,
such as setting alarms (refer to alarms on page 131), creating reports (refer to reports on page 133)
or setting out trends (refer to trends on page 135..
DataMiner interfaces can have different look and feels. The parameters can be organized in static
panes as shown in the screenshot below.
Or the parameters can be organized in tables as shown in the screenshot below. You can drag and
drop columns by clicking and holding the column title, then dragging it to its new location. Click the
column title to sort its content.
DataMiner® has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about the software capabilities and features.
For reasons of scalability, part of the fault and performance monitoring is transformed to a
hierarchical collection model where data is collected as close to the data source as possible and
stored in hub local Time Series DataBases (TSDBs). This guarantees access to performance
metrics without a requirement to the link availability between the NMS and the hub modules.
On a Grafana dashboard you can have numerous types of panels: graph, stat, gauge, etc. The type
of panel typically depends on the parameter that needs to be visualized.
You can drag and drop panels by clicking and holding the panel title, then dragging it to its new
location. You can easily resize panels by clicking and moving the bottom right corner.
In the upper left of each dashboard, you can see the name of the dashboard as well as the folder to
which it belongs.
Click the folder (System in this example) to view all dashboards that exist within this folder. Click the
dashboard name (Host overview in this example) to show the recently viewed dashboards and the
existing folders.
In the upper right of each dashboard, you have a number of buttons to manage the dashboard, such
as:
1. Save the dashboard.
2. Set the time range. Click the drop-down button to select another range, or use the magnifying
glass to zoom out in periods of one day.
Panels that display the parameter over a time range, such as the graph panel, are updated
accordingly.
Select an area on the panel to zoom in. All panels on the dashboard are updated accordingly.
3. Refresh the dashboard manually or click the drop-down button to change the refresh period.
For more information about how to use Grafana dashboards and panels, refer to
[Link]
On a Kibana dashboard you can have numerous types of visualization: chart, table, metric, etc. The
type of visualization typically depends on the metric that needs to be visualized.
You can drag and drop panels by clicking and holding the panel title, then dragging it to its new
location. You can easily resize panels by clicking and moving the bottom right corner.
In the upper right of the Kibana dashboard, you can see the time range of the visualization. Click the
time range to select another range.
To access the GUI of the Dialog Network Management System, execute the following steps:
1. Open the Internet Explorer browser and browse to [Link]
CMS_VIP is the virtual IP address of your NMS system. This IP address is set
during the installation of your hub module. For more information, refer to the
corresponding Newtec Dialog Hub Installation Guide.
2. Select the user at the left hand side and enter the password.
The NMS login credentials are set during the installation of the hub module. For
more information, refer to the corresponding Newtec Dialog Hub Installation Guide.
3. Click Log on. The NMS client application connects to the specified Dialog NMS server and the
home page of the Dialog NMS user interface opens.
Select the 'Save my user name and password' check box to save the logon
credentials. When selected, you will automatically log on the next time the Dialog
NMS client is started.
4. To log off, click the user name at the right in the header bar and select Log off.
The NMS GUI has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about the user interface components and their functionality.
items are identified with the icon. Nodes are preceded by a colored bar, which indicates the
alarm state of the node. The table below maps the alarm severity level to the color.
Normal Green
Warning Blue
Minor Cyan
Major Yellow
Critical Red
In case a node holds multiple alarms, the alarm with the highest priority will define the alarm state
(and the color) of the item.
The NMS GUI has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about the surveyor tree.
From the menu button in the upper left of the card pane, you can go to:
• The hub module provisioning interface. See Gateway/HubmoduleProvisioning on page 16.
• The About section displaying the system, GUI and NMS version.
A gateway is provisioned during the installation of a hub module. For more information,
refer to the corresponding Newtec Dialog Hub Installation Guide.
From the menu button in the upper left of the card pane, you can go to:
• The gateway provisioning interface. See Gateway Provisioning on page 16.
• The About section displaying the system, GUI and NMS version.
A hub module is provisioned during the installation of the hub module. For more
information, refer to the corresponding Newtec Dialog Hub Installation Guide.
The Centralized Logging node is available for the following hub modules:
• NMS module (embedded or stand-alone)
You can find a Centralized Logging node in the surveyor tree for each enclosure of
the XIF processing hub module HUB7303 and each HPS pool of the XIF processing
hub module HUB7318.
Select Centralized Logging in the surveyor tree. The card pane displays a Kibana dashboard
showing information about events that have been logged for a virtual machine or server, such as the
number of events and type of events.
(The screenshot shows the Centralized Logging item for the HUB7318 XIF processing hub module.)
[Link] HPS
An HPS or Hub Processing Segment corresponds with the processing capabilities of one satellite
network.
The data plane of a satellite network is functionally scoped into four different segments. Each
segment has its own functionality. The functionality is provided by physical devices and virtual
machines (VMs) or virtual network functions (VNFs). Segments 2, 3, and 4 correspond with the HPS
subsystem.
In the surveyor tree there is an HPS node for each satellite network that you have created in your
hub module. Refer to SatNet Provisioning on page 78 to link the HPS to a satellite network.
Select the HPS node in the surveyor tree to display a Grafana dashboard with the key KPIs of the
corresponding satellite network.
Forward L3 Unicast This is the rate at which the DEM receives forward layer kb/s
Input Rate 3 unicast traffic bits.
Forward L2 Input Rate This is the rate at which the L2DEM receives forward b/s
layer 2 traffic bits.
Forward Multicast Input This is the rate at which the CSE receives forward b/s
Rate multicast traffic bits.
The Forward Satellite section displays traffic rates monitored at the CSE VM.
Forward Symbol Rate This is the rate at which the CSE (encapsulator) Mbaud
transmits forward traffic symbols. The rate includes
unicast, multicast and control traffic, and encapsulation
overhead.
Forward Send Rate This is the rate at which the CSE (shaper) transmits kb/s
forward traffic bits. The rate includes unicast, multicast
and control traffic, and eTCP overhead for unicast traffic.
Forward Link This parameter indicates how much of the forward link is %
Occupation used. The value equals 100*(actual symbol
rate/configured symbol rate).
Forward Link Efficiency This parameter indicates how efficiently the forward link bits/baud
is used. The value equals actual bit rate/configured
symbol rate.
Forward Unicast Send This is the rate at which the CSE (shaper) transmits b/s
Rate forward unicast traffic bits. The rate includes eTCP
overhead.
Forward Multicast Send This is the rate at which the CSE (shaper) transmits b/s
Rate forward multicast traffic bits. The rate includes multicast
traffic but excludes the terminal software multicast
streams. The software multicast streams are accounted
in the control statistics.
Forward Control Send This is the rate at which the CSE (shaper) transmits kb/s
Rate forward control traffic bits. The rate includes control
traffic. Control traffic includes a.o. forward signaling and
the terminal software multicast traffic.
The Return Uplink section displays output traffic rates monitored at the DEM, L2DEM and DCP
VMs.
Return L3 Unicast This is the rate at which the DEM transmits return layer b/s
Output Rate 3 unicast traffic bits.
Return L2 Output Rate This is the rate at which the L2DEM transmits return b/s
layer 2 traffic bits.
Return Multicast Output This is the rate at which the DCP transmits return b/s
Rate multicast traffic bits.
Click on one of the KPI panels in the Forward Uplink, Forward Satellite or Return Uplink section to
go to the detailed overview. The detailed overview shows the parameters as graphs trended over
time, as well as the minimum, maximum, average and current value. Hover your mouse over a graph
panel to get the value for a specific time.
The Return Satellite section displays the input rate monitored at the DCP VM and the provisioned
and operational terminals monitored at the return controller.
The parameters are described in the table below.
Return Receive Rate This is the rate at which the DCP receives return traffic b/s
bits. The rate includes unicast, multicast and control
traffic, and eTCP overhead for unicast traffic.
Click on the Return Receive Rate panel to go to the detailed overview. The detailed overview shows
the parameter as a graph trended over time, as well as the minimum, maximum, average and current
value. Hover your mouse over the graph panel to get the value for a specific time.
Click on an HRC terminal panel to go to the detailed overview.
• For the detailed overview of an HRC terminal, refer to the dashboard details in HPS/HRC on page
26.
The Common section displays parameters monitored at the TAS VM. They are described in the
table below.
Active ETCP This is the number of active ETCP connections for the
Connections TAS. This number corresponds with the number of
terminals that have set up an ETCP tunnel with the
TelliNet instances of the TAS.
Click a panel in this section to go to the detailed overview. Refer to HPS/TAS on page 41 for more
information.
Under each HPS node you will find a node per virtual machines. These VM nodes are described in
the next chapters.
[Link].1 HPS/CSE
The CSE item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 24
• dashboard details on page 25
• webinterface on page 25
dashboard
The dashboard tab displays key KPIs of the CSE VM. The key KPIs are described in the table
below.
Sent Bit Rate This is the rate at which the CSE (shaper) transmits kb/s
forward traffic bits.
Sent Symbol Rate This is the rate at which the CSE (encapsulator) Mbaud
transmits forward traffic symbols.
Sent Packet Rate This is the rate at which the CSE (shaper) transmits packets/s
forward traffic packets.
Drop Bit Rate This is the rate at which the CSE (shaper) drops b/s
forward traffic bits.
Delay This is the average time that packets are queued in the ms
CSE.
Link Occupation This parameter indicates how much of the forward link %
used. The value equals 100*(actual symbol
rate/configured symbol rate).
Link Efficiency This parameter indicates how efficiently the forward link bits/baud
is used. The value equals actual bit rate/configured
symbol rate.
Most of these parameters are also available in Beam/Satellite Network/Forward Link on page 81.
dashboard details
Click on one of the panels in the dashboard tab or click the dashboard details tab to go to the
detailed overview. The detailed overview shows the parameters as graphs trended over time, as well
as the minimum, maximum, average and current value. Hover your mouse over a graph panel to get
the value for a specific time.
webinterface
Click webinterface to open the TelliShape web interface.
[Link].2 HPS/DCP
The DCP item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 26
• dashboard details on page 26
• webinterface on page 26
dashboard
The dashboard tab displays key KPIs of the DCP. The key KPIs are described in the table below.
Received Bit Rate This is the rate at which the DCP receives return b/s
traffic bits.
Received Packet Rate This is the rate at which the DCP receives return packets/s
traffic packets.
dashboard details
Click on one of the panels in the dashboard tab or click the dashboard details tab to go to the
detailed overview. The detailed overview shows the parameters as graphs trended over time, as well
as the minimum, maximum, average and current value. Hover your mouse over a graph panel to get
the value for a specific time.
webinterface
Click webinterface in the upper left of the card pane to open the TelliShape web interface.
[Link].3 HPS/HRC
The HRC item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 27
• dashboard details on page 28
• terminals on page 29
• terminal details on page 30
• webinterface on page 30
dashboard
The dashboard tab displays parameters related to the HRC return link technology. The Actual N0
and Transponder Frequency Offset parameters are displayed as a graph trended over time. The time
period is indicated in the upper right of the card pane. Hover your mouse over the graph panel to get
the value for a specific time. The graph panel also shows the minimum, maximum, average and
current value at the bottom of the panel.
The parameters are described in the table below.
Actual N0 This is the actual noise power density from the dB/Hz
demodulator, trended over time.
Clear Sky N0 This is the clear-sky noise power density from the dBm/Hz
demodulator.
Actual Tracked N0 This is the current and actual noise power density dBm/Hz
from the demodulator.
Sym Rate N0 This is the symbol rate of the carrier at which noise baud
higher than or equal to 3 dB above the average
noise level, was measured. The noise could indicate
the presence of interference. When there is no
interference, the value is NULL.
Demod Not Resp Cnt This is the number of times the demodulator did not
respond.
dashboard details
The dashboard details tab displays parameters per HRC return capacity group. You can select the
HRC return capacity group of your interest from the drop-down list. All parameters are displayed as
graphs trended over time. At the bottom of each graph you can find the minimum, maximum,
average and current value. Hover your mouse over a graph panel to get the value for a specific time.
The parameters are described in the table below.
Requested Rate This is the bit rate requested for the return pool. The bps
rate includes encapsulation overhead.
Allocated Rate This is the bit rate allocated to the return pool. The bps
rate includes encapsulation overhead.
terminals
The terminals tab displays parameters per HRC terminal with Monitoring Type set to Advanced.
You can select specific terminals or all terminals. Each parameter is displayed as a single value.
The parameters are described in the table below.
Fwd Throughput The rate at which the CSE (shaper) transmits bps
forward traffic bits for that modem. The rate includes
eTCP overhead for unicast traffic.
Rtn Throughput The rate at which the DCP receives return traffic bits bps
for that modem. The rate includes eTCP overhead
for unicast traffic.
Fwd EsN0 This is the energy per symbol (Es) to noise power dB
spectral density (N0) ratio of the forward link
measured at the modem and signaled to the hub. It
is an indication of the forward link quality.
Rtn Hrc EsN0 This is the energy per symbol (Es) to noise power dB
spectral density (N0) ratio of the return link of the
terminal measured at the HRC demodulator and
signaled to the HRC controller (HRCCTL). It is an
indication of the return link quality.
terminal details
The terminal details tab gives a detailed overview of the parameters in the terminals view. Each
parameter is displayed as a graph trended over time. The time period is indicated in the upper right
of the card pane. Hover your mouse over a graph panel to get the parameter value for a specific
time. Each graph panel, except Modcod, also shows the minimum, maximum, average and current
value at the bottom of the panel.
Additionally, the page also displays the parameters described in the table below.
Rtn Errored Frames This is the number of received HRC baseband frames
packets with an error.
Rtn Rx Power Density This is the received power level density measured at dBm/Hz
the HRC demodulator.
Rtn BBP Occupation This parameter indicates how many of the baseband %
packets for that terminal are used. The value equals
used bit rate/total allocated bit rate.
webinterface
Click webinterface to open the web interface of the HRC controller (HRCCTL). The interface shows
the parameters described in the table below for each provisioned HRC terminal.
Rx Level Density This is the received power level density measured at dBm/Hz
the HRC demodulator.
Symbol Rate This is the current symbol rate used by the modem. Bd
Allocated Bitrate This is the bit rate allocated to the modem. The rate bps
includes encapsulation overhead.
ACM Margin The difference with the link margin is that this value dB
is used by the internal algorithms.
Tx Power Density This is the power level density transmitted by the dBm/Hz
terminal. This is signaled to the terminal.
Assigned MCD Role This is the demodulator of the return traffic from the
modem.
BUC Frequency Offset This is the measured frequency offset from BUC. Hz
This value should be very small when the modem
and BUC are slaved to the same reference clock.
Insufficient Carrier Guard This is the number of times the provisioned guard
Band Count band for the terminal was not sufficient.
[Link].4 HPS/L2DEM
The L2DEM item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 33
• dashboard details on page 34
Return
dashboard
The dashboard tab displays key KPIs of the L2DEM. The KPIs are classified by:
• Port type: DPDK, internal and VXLAN.
• Port: bridge edge, brirge MPLS, bridge VxEline, edge bond, MPLS bond, VxLAN tunnel.
The key KPIs are described in the table below.
Transmitted Bit Rate Rate at which the L2DEM transmits layer 2 unicast bps
bits successfully through the selected interface (from
the out-port of each bridge), including the headers
Transmitted Packet Rate Rate at which the L2DEM transmits layer 2 frames packets/s
successfully through the selected interface (from the
out-port of each bridge).
Each port in the bridge can be in/out port based on
the forward/return traffic
Received Bit Rate Rate at which the L2DEM receives layer 2 unicast bps
bits successfully through the selected interface (from
the out-port of each bridge), including the headers
and payload of the frames.
Each port in the bridge can be in/out port based on
the forward/return traffic
Received Packet Rate Rate at which the L2DEM receives layer 2 frames packets/s
successfully through the selected interface (from the
out-port of each bridge).
Each port in the bridge can be in/out port based on
the forward/return traffic
dashboard details
Click on one of the panels in dashboard view or click the dashboard details tab to go to the detailed
overview. The detailed overview shows the traffic rates as graphs trended over time, as well as the
minimum, maximum, average and current value. Hover your mouse over a graph panel to get the
rate for a specific time.
[Link].5 HPS/L3DEM
The L3DEM item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 35
• dashboard details on page 36
Return
dashboard
The dashboard tab displays key KPIs of the DEM. The KPIs are organized in four sections:
• External Network Interface; corresponds with the external interface towards the customer network.
• Internal Network Interface; corresponds with the internal interface towards the satellite.
• External Network Interface Control Plane Traffic; corresponds with the external interface towards
the customer network and control traffic.
• Internal Network Interface Control Plane Traffic, corresponds with the internal interface towards
the satellite and control traffic.
The key KPIs are described in the table below.
dashboard details
Click on one of the panels in the dashboard tab or click the dashboard details tab to go to the
detailed overview. The detailed overview shows the traffic rates as graphs trended over time, as well
as the minimum, maximum, average and current value. Hover your mouse over a graph panel to get
the rate for a specific time.
[Link].6 HPS/MRC
The MRC item displays a Grafana dashboard with the following tabs in the upper left of the card
pane:
• dashboard on page 37
• terminals on page 37
• terminal details on page 38
• webinterface on page 39
dashboard
The dashboard tab displays parameters related to the MRC return link technology. The
Transponder Frequency Offset parameter is displayed as a graph trended over time. The time period
is indicated in the upper right of the card pane. Hover the mouse over the graph panel to get the
value for a specific time. The graph panel also shows the minimum, maximum, average and current
value at the bottom of the panel.
The parameters are described in the table below.
terminals
The terminals tab displays parameters per MRC terminal with Monitoring Type set to Advanced.
You can select specific terminals or all terminals. Each parameter is displayed as a single value.
Fwd Throughput Rate at which the CSE (shaper) transmits forward bps
traffic bits for that modem. The rate includes eTCP
overhead.
Rtn Throughput Rate at which the DCP receives return traffic bits for bps
that modem. The rate includes eTCP overhead.
Rtn Mrc EsN0 Energy per symbol (Es) to noise power spectral dB
density (N0) ratio of the return link of the terminal
measured at the MRC demodulator and signaled to
the MRC controller (MRCCTL). It is an indication of
the return link quality.
terminal details
The terminal details tab gives a detailed overview of the parameters in the terminals view. Each
parameter is displayed as a graph trended over time. The time period is indicated in the upper right
of the card pane. Hover your mouse over a graph panel to get the parameter value for a specific
time. Each graph panel, except Modcod, also shows the minimum, maximum, average and current
value at the bottom of the panel.
Additionally, the page also displays the parameters described in the table below.
MRC Operational State State of the terminal (logged on or logged off) every
20 minutes.
Rtn Errored Frames Number of received MRC baseband packets with an frames
error.
Rtn Rx Power Density Received power level density measured at the MRC dBm/Hz
demodulator.
Terminal bitrate Requested and assigned rates for the QoS classes kb/s
assignment at the MRC link.
webinterface
Click webinterface to open the web interface of the MRC controller or MRCCTL. The interface
shows the parameters described in the table below for each provisioned MRC terminal.
Symbol Rate (min) Minimum symbol rate assigned to the terminal. sym/s
Symbol Rate (max) Maximum symbol rate assigned to the terminal. sym/s
Requested bitrate Bit rate requested by the terminal in the return kbps
capacity group
Allocated Bitrate Bit rate allocated to the modem. The rate includes kbps
encapsulation overhead.
Average Physical Layer Number of physical layer bits divided by frequency bps/Hz
Efficiency bandwidth, including guard bands and roll-off.
CW Frame Error Ratio Ratio of received MRC code words frames with an %
error and the total number of MRC code words
frames.
Rx Level Density Received power level density measured at the MRC dBm/Hz
demodulator.
Tx Power Density Power level density transmitted by the terminal. This dBm/Hz
is signaled to the terminal.
Offset to phase noise Offset to the default phase noise mask (-70dBc/Hz dB
mask at 1kHz) in dB.
For more information on transmit modes
and phase noise masks, please refer to
the Dialog Functional Description.
RMS phase noise Root mean square of the measured phase noise degrees
expressed in degrees
Cycle slip bursts The cycle slip counter counts the number of times a #
high phase offset was measured in the phase
tracking loop.
These parameters are also available in Advanced Terminal Monitoring on page 106.
Additional parameters are available in MRC Controller on page 49.
[Link].7 HPS/Summary
The Summary item displays a Grafana dashboard with the following tabs in the upper left of the
card pane:
• dashboard
• dashboard details
The information displayed in both dashboards is the same as in the HPS item. Refer to HPS for
more information about the parameters.
[Link].8 HPS/TAS
The TAS item displays a Grafana dashboard with parameters related to the TellliNet server. You
can select specific TelliNet server instances or all TelliNet server instances. A TAS virtual machine
deploys up to six TelliNet server instances and the NMS balances the modems over these
instances. You can find the TelliNet server instance to which the TelliNet client of a modem is
connected in Terminal Configuration on page 107.
The parameters are monitored at the TAS VM and are displayed as graphs trended over time. The
time period is indicated in the upper right of the card pane. Hover your mouse over the graph panel
to get the value for a specific time. Each graph panel also shows the minimum, maximum, average
and current value at the bottom of the panel.
The parameters are described in the table below.
Number of ETCP The number of active ETCP connections for the Tellinet
Connections instance. This number corresponds with the number of
terminals that have set up an ETCP tunnel with the
Tellinet instance.
Memory in Use The actual memory used by the Tellinet instance. If the
number of accelerated TCP increases, the used memory
will also increase.
Select the Instance under the TAS node in the surveyor tree to go to the corresponding TelliNet
server instance web interface.
[Link].9 Functions
The parameters of the Functions item are collected and visualized using the DataMiner application.
The DATA section in the card navigation pane gives access to the following DataMiner displays:
• CSE
• DCP
• HRC Controller
• MRC Controller
• L3 VRF
• OSPF / BGP
• TCS
Select a DATA display in the card navigation pane or via the drop-down box in the upper left of the
card pane. By default the CSE display is selected.
CSE
The CSE card displays CSE related parameters.
Control Symbol Rate This is the rate at which the CSE (encapsulator) Mbaud
transmits forward control symbols. The rate includes
control traffic and encapsulation overhead.
Control Link Occupation This parameter indicates how much of the available %
forward link bandwidth is used for control traffic. The
value equals 100*(control symbol rate/configured
symbol rate).
This metric is monitored for alarms. If the control or
signaling traffic, which also includes the software
multicast streams, exceeds 50% of the available
forward link bandwidth an alarm will be triggered. For
more information about the software multicast streams,
refer to Software Terminal Upgrade on page 100.
Send Rate This is the rate at which the CSE (shaper) transmits Mbps
forward traffic bits. The rate includes unicast, multicast
and control traffic, and eTCP overhead for unicast
traffic.
Send Symbol Rate This is the rate at which the CSE (encapsulator) Mbaud
transmits forward traffic symbols. The rate includes
unicast, multicast and control traffic, and encapsulation
overhead.
DCP
The Receive Rate indicates the rate at which the DCP receives return traffic bits. The traffic
includes unicast, multicast and control traffic, and eTCP overhead for unicast traffic.
Additional parameters are available in HPS/DCP on page 25.
HRC Controller
When the HRC controller is active, the card shows the current alarm states of the monitored HRC
related parameters as well as the alarm history.
Alarm Description
Internal Error An error has occurred that was not covered by any of
the other alarms.
Timing Error The HRC controller has strict timing deadlines in order
to get everything processed and signaled to the
relevant components. When one of these deadlines is
violated, a timing alarm will be activated.
Possible causes are:
• Resource problems in the VM.
• Wrong PTP time domain configuration (controller
slaved to the wrong PTP master).
Tx Mode Selection Error For one or more terminals, the controller was unable
to find a Tx Mode that satisfied the following
constraints:
• A terminal may not surpass BEPD.
• A terminal may not saturate the ODU.
• A terminal must respect the ACM Margin
When no valid Tx Mode can be found, the controller
will log that terminal off
System Noise Too Low At least one demodulator has an estimated clear sky
N0 value below -140 dBm/Hz.
As any electronic equipment, the demodulator has an
internal noise floor, which is a combination of thermal
noise, cosmic noise, atmospheric noise, etc... Typical
values are between -160 and -145 dBm/Hz, but can
be higher depending on the physical conditions. The
HRC demodulator needs a noise floor parameter to be
able to do reliable estimations of other parameters,
such as EsN0 and CoND. The HRC controller will use
the noise-based estimated parameters to estimate the
link conditions. A noise level at the input of the
demodulator, which is lower than the demodulator's
internal noise level will cause unreliable estimations
Transponder Frequency Offset Unknown The HRC controller uses the frequency offset
introduced by the transponder and present in the
transmitted HRC carrier, to adjust the demodulator
receive frequency. This assures that the demodulator
receiver is very close to the correct frequency. A small
frequency uncertainty of 3 kHz (+/- 1.5 kHz) is taken
into account to compensate for unaccounted frequency
errors.
When the controller does not know the transponder
frequency offset, chances are that the demodulator
receiver is not at the same frequency as the actual
transmitted carrier frequency.
This alarm is typically raised when a satellite network
is used for the first time. As long as no terminal is
logged on, the alarm will remain active.
Demod Protocol Error The HRC controller has detected a problem in the
messages received from the demodulator.
Possible Interference Present This alarm indicates that for at least one terminal the
noise deviation was more than 3 dB.
This alarm is for informational purposes only.
The ACM mechanism should be able to handle the
situation but the interference should be investigated.
Terminal Power Too High At least one terminal is transmitting at a PSD more
than 3 dB above BEPD.
This may point at incorrect configuration of an SCPC
carrier, incorrect lineup settings, or the alarm can
occur during lineup itself.
This alarm is for informational purposes only. It is the
responsibility of the operator to correct the erroneous
situation.
Wrong Initial Configuration The configuration of the HRC controller was rejected
at startup. This points to an internal error of the Dialog
system.
Terminal ACM Bypass Mode For at least one terminal the HRC controller ACM
mechanism was unable to find a suitable MODCOD
and had to fall back to the minimal Tx Mode.
In order to prevent short RF disturbances from
immediately logging off a terminal, the controller will
keep the terminal online for a couple of seconds, in the
hope the link will restore itself.
The minimal Tx Mode is a combination of the lowest
allowed (symbol rate + power) and the lowest
MODCOD. Checks on BEPD level are still maintained
so the miminal Tx Mode will never violate BEPD.
Terminal Insufficient Guard Band There's not enough bandwidth for at least one SCPC
terminals.
HRC Demodulator Processing Range The configured bandwidth could not be handled
Overflow correctly for at least one SCPC terminal. This is
caused by a processing limitation of the demodulator.
The service of the SCPC terminal is interrupted.
HRC Demodulator Processing Range Hit For at least one Mx-DMA terminal the allocated
bandwidth was impacted by the processing limitation
of the demodulator. This results in lower bandwidth
allocation for the terminal.
Demodulator Capability Not In Line With This alarm occurs when at least one terminal is
Terminal Capability assigned to a demodulator which does not support the
full capabilities as requested by the terminal.
No Demodulator Capacity for a Terminal This alarm indicates that there is not enough
demodulator capacity for at least one terminal.
No Mobility Manager Connected The HRC CTL sends updates and heartbeats to the
DMM. This alarms occurs when a a connection
between the HTC CTL and the DMM cannot be
detected, or is not valid or active.
Multiple Mobility Manager Connected This alarm happens when multiple DMM connecting to
a single HRC controller.
When a second DMM connection becomes valid, it
gets activated, de-activating the previous one. The
de-activated DMM connections are kept alive but they
will receive no state change notification and their
control orders are ignored.
The Scheduling Event Error Count indicates the number of time a scheduling event error
occurred.
Click the Open... button next to Open Act...ns Page or select HRC Controller Actions in the card
navigation pane to:
• Reset the frequency tracking offset
• Reset the gain tracking
Click the Open... button next to Open HRC PTP Page or select HRC PTP in the card navigation
pane to view information about PTP.
MRC Controller
When the MRC controller is active, the card shows the current alarm states of the monitored
MRC-related parameters as well as the alarm history.
Alarm Description
Burst Info Lost The controller has given capacity to different terminals
based on the terminals capacity requests. This alarm
is triggered when a specific terminal is not using the
assigned burst capacity, therefore no valid signal at
the demodulator side for a specific burst location can
be seen.
Internal Failure An error has occurred that was not covered by any of
the other alarms.
Debuglog Active This alarm happens when a high detailed log level
remain active.
Tx Mode Selection Error The MRCCTL could not come up with the burst plan
for a terminal. This can be due to a local interference
for a terminal or a terminal with bad lineup interfering in
other terminals.
L3 VRF
The L3 VRF card displays parameters related to the layer 3 network resources.
Each router in the network, including the modem, that forwards the IP traffic of the layer 3 virtual
networks should be able to route the traffic of each virtual network independently. Therefore, the
router supports multiple independent Virtual Routing and Forwarding or VRF functions. One VRF
function provides the routing functions for one virtual network.
Return
Fwd Data Rate This is the rate at which the DEM: bps
• receives layer 3 unicast traffic bits (external
interface).
• transmits layer 3 unicast traffic bits (TAS
interface).
Fwd Packet Rate This is the rate at which the DEM: packets/s
• receives layer 3 unicast packets (external
interface).
• transmits layer 3 unicast packets (TAS interface).
Rtn Data Rate This is the rate at which the DEM: bps
• transmits layer 3 unicast bits (external network).
• receives layer 3 unicast bits (internal network).
Rtn Packet Rate This is the rate at which the DEM: packets/s
• transmits layer 3 unicast packets (external
interface).
• receives layer 3 unicast packets (TAS interface).
These rates are also available in the External Network Interface and Internal Network Interface
section of HPS/L3DEM on page 34.
For more information about the subnets, refer to Network Resources on page 76.
OSPF / BGP
The OSPF/ BGP card displays status information related to OSPF or BGP per provisioned L3 subnet
or virtual network.
The OSPF Information section shows the connectivity state of the external router. The following
states exist:
• up: The connectivity with the external router is operational.
• down: The connectivity with the external router is down.
• start: The connectivity with the external router is being set up but is not yet operational.
The BGP Neighbors Information section shows the parameters described in the table below.
BGP Neighbor Status This is the status of the BGP connectivity for a
specific neighbor.
BGP Last Error Code Descriptive text of the last error that occurred.
BGP Number of Learned This is the number of learned routes for this BGP
Routes association.
TCS
The TCS card displays Terminal Configuration System related information.
In the Terminal Configuration System Table section, you can see which software version is
installed on your terminal.
The Terminal Per Software Version section gives you the number of terminals that are running on
a certain software version.
The Terminal Configuration System Table and Terminals Per Satellite Configuration Version
sections provide information about the terminal's satellite configuration.
For more information about the satellite configuration, refer to the Remote Terminal
Satellite Configuration chapter in the Newtec Dialog Functional Description.
You can find a Local Monitoring node in the surveyor tree for each enclosure of the
processing hub module and for each HPS pool of the processing hub module.
Select Local Monitoring in the surveyor tree. The card pane displays a Grafana dashboard
showing system performance parameters for each server and virtual machine in the hub module.
Select the virtual machine or server of your interest from the Server drop-down list.
The available nodes under the Physical Devices node in the surveyor tree depend on the type of
hub module. The table below indicates which nodes are available for which hub module.
[Link] x
DP x
LSM x
Cloud x x
DMA x
[Link].1 [Link]
Select [Link] in the surveyor tree to view system information and performance parameters of
the Enclosure.
There are two VISUAL displays:
• overview, which gives you the status of the enclosure, power supplies and network connectors.
• enclosure, which gives you a picture of the enclosure.
More detailed information is spread over several DATA displays.
Select General in the card navigation pane or via the drop-down box in the upper left of the card
pane to view system information, such as up time, and fan and power supply statistics.
Select Network in the card navigation pane or via the drop-down box in the upper left of the card
pane for information about the network connectors.
Select Blades in the card navigation pane or via the drop-down box in the upper left of the card
pane for information about the blade servers.
[Link].2 DP/MOD
[Link].3 DP/MCD
The demodulators are grouped in device pools and operate in an N:M pool redundancy
configuration, with N active devices and M standby devices. Pool redundancy is provided per type of
demodulator. The type depends on the return link technology (e.g. CPM, HRC, MRC, S2) and the
capabilities (for example CPM 16MHz or HRC 17MBd/70MHz) of the device.
Select <X>MCD in the surveyor tree to view device information and statistics of the demodulator,
or to access the web interface. X refers to the return link technology: HRC, or MRC.
• Signaling and Data, to view the signaling and data destination IP address, UDP ports and output
bit rates.
• MRC Demod Monitoring, to view physical layer monitoring metrics.
[Link].4 Cloud
Select Cloud in the surveyor tree to view information of the virtual machines, such as CPU usage
and memory usage.
Select the DATA display Inventory display in the card navigation pane or via the drop-down box in
the upper left of the card pane.
[Link].5 LSM
Select LSM in the surveyor tree to view information of the L-band switch matrix, such as up time,
matrix layout and health.
The information is spread over several DATA displays.
[Link].6 DMA
Select DMA in the surveyor tree to view system information and performance parameters of the
DataMiner application.
[Link] Performance
All parameters are collected and visualized using the DataMiner application.
Select Performance in the surveyor tree and then select the DATA display Terminals to view
QoS-related configuration information, signal quality and throughput statistics of the provisioned
terminals.
The signal quality and throughput parameters are described in the table below.
Total Forward Throughput This is the rate at which the CSE (shaper) transmits kbps
forward traffic bits for the modem. The rate includes
unicast traffic and eTCP overhead.
Total Return Throughput This is the rate at which the DCP receives return kbps
traffic bits for the modem. The rate includes unicast
traffic and eTCP overhead.
Forward Throughput per This is the rate at which the CSE (shaper) transmits kbps
QoS Class forward traffic bits for the modem and the specific
QoS class. The rate includes unicast traffic and
eTCP overhead.
Return Throughput per This is the rate at which the DCP receives return kbps
QoS Class traffic bits for the modem and the specific QoS class.
The rate includes unicast traffic and eTCP overhead.
Total Forward Dropped This is the rate at which the CSE (shaper) drops kbps
Rate forward traffic bits for the modem. The rate includes
unicast traffic and eTCP overhead.
Forward Dropped Rate per This is the rate at which the CSE (shaper) drops kbps
QoS Class forward traffic bits for the modem and the specific
QoS class. The rate includes unicast traffic and
eTCP overhead.
Forward Es/N0 Average This is the average energy per symbol (Es) to noise dB
power spectral density (N0) ratio of the forward link
measured at the modem and signaled to the hub. It
is an indication of the forward link quality.
This is the average of all values measured over the
monitoring interval.
Forward Es/N0 Minimum This is the minimum energy per symbol (Es) to noise dB
power spectral density (N0) ratio of the forward link
measured at the modem and signaled to the hub. It
is an indication of the forward link quality.
This is the minimum value measured over the
monitoring interval.
Forward Es/N0 Maximum This is the maximum energy per symbol (Es) to dB
noise power spectral density (N0) ratio of the
forward link measured at the modem and signaled to
the hub. It is an indication of the forward link quality.
This is the maximum value measured over the
monitoring interval.
Max Forward Es/N0 The is the maximum value of the average forward dB
Average Es/N0 values measured over a period of 24 hours.
These parameters are also available in Advanced Terminal Monitoring on page 106.
[Link] REDCTL
Select Server redundancy in the card navigation pane or via the drop-down box in the upper left of
the card pane for information about the status and redundancy of servers and virtual machines.
The VMs of the HPS sub-system use the concept of “protection groups” for redundancy. Each
enclosure has its own protection group mechanism with two protection groups:
• SCP protection group, including PGIDCP, PGICPMCTL, PGIS2CTL, PGICSE and PGIHRCCTL;
• EDP protection group, including PGIDEM, PGIL2DEM and PGITAS.
An instance of the SCP protection group is deployed on blade servers located in uneven slot
positions. An instance of the EDP protection group is deployed on blade servers located in even slot
positions.
The collection of one instance of each protection group corresponds with one hub processing
segment (HPS). Within a protection group (SCP or EDP) of the same enclosure an N:M redundancy
configuration is applied. Redundant protection groups are marked as standby.
For more information about configuring the gateway, refer to Gateway Provisioning on
page 16.
The CIDI is a combination of hardware and virtualization software. It allows to abstract the Dialog
products and functionalities and the hardware that these products require.
The components of the private cloud, for example the cloud servers or the network switches, need
to be monitored and managed. Dialog's Inframan is a set of components capable of monitoring the
CIDI that hosts the Dialog Cloud. One Inframan is deployed per CIDI.
Inframan monitors the following components:
• TOR switches
• R640 servers
• RedHat OpenShift
• TFR0210
There is no redundancy in Inframan VM. In case it shuts down, the Dialog platform
keeps on working. This means that there is no service impact but alarms will be lost.
[Link] Access
Select Cloud_Monitoring in the surveyor tree. The card pane displays a Grafana dashboard
showing the overall health of the cloud system.
Click the NPCI folder in the upper left of the card pane to view the available NPCI dashboards.
Note that no credentials are needed to get read-only access to the Grafana web GUI.
Parameter Description
This dashboard provides a list of the alarms that were generated in a selected time frame.
Parameter Description
Host List Active List of hosts checked and their status. 1 for OK, 2 for Critical/Warning, 3
checked for Critical, 4 for Unknown.
This dashboard monitors the virtual switch that links together the running VMs in each compute
node.
Use the drop-down menus in the upper left to filter on platform and nodes.
Parameter Description
AVS Transmit Number of discarded packets by the virtual switch on its lifetime.
Discards
Each controller or compute block has two switches. This dashboard monitors the function of the
switches.
Use the drop-down menus in the upper left to filter on platform and switch.
Parameter Description
CPU Overview CPU usage value for the last 5 seconds, 1 minute and 5 minutes.
Trending graph for the CPU usage for the last 5 seconds, 1 minute and 5
minutes.
Switch Memory Current switch memory usage and trending graph of its historical data.
Switch Temperature Current switch temperature and trending graph of its historical data.
Parameter Description
Interface Throughput Trending graph of the throughput for the selected switch and interface.
Stats
Interface Error Stats Number of transmitted or received packets with errors for the selected
switch and interface.
Interface Discard Number of transmitted or received packets that were discarded for the
Stats selected switch and interface.
This dashboard monitors the compute, control and storage nodes within the NPCI/CIDI.
Parameter Description
Node CPU Usage Trending graph of the CPU usage of each node.
Note that the CPU monitoring is done for the CIDI itself,
not for the VMs.
Node Memory Usage Trending graph of the memory usage of each node.
This dashboard summarizes the alarm state of a chosen platform and can be used to monitor the
overall health of the system.
Parameter Description
Cloud Status The system inventory and maintenance service reports system changes
with different degrees of severity:
• Critical
• Mayor
• Minor
• Warning
Host Status Host Status corresponds to the compute nodes, storage, switches and
controllers. It gives a count of the number of hosts up and down in the
cloud platform.
Host Alarms List of alarms generated due to host issues. It includes the timestamp of
the alarm, a meaningful description and the state of the alarm, for
example, Warning or Critical.
Service Alarms List of alarms generated due to service issues. It includes the timestamp
of the alarm, a meaningful description and the state of the alarm, for
example, Warning or Critical.
This dashboard monitors the temperature, power consumption and speed of the fan of the platform.
Parameter Description
Node Temperature Trending graph of the temperature in °C in each node of the platform.
Node Power Trending graph of the power consumption in W in each node of the
Consumption platform.
Node Fans (RMP) Trending graph of the speed in rpm of the cooling fans in each node of
the platform.
This dashboard monitors the power consumption per Power Supply Unit (PSU). A trending graph
with the power consumption of each compute node in watts is presented per PSU.
This dashboard monitors the state of the Top of the Rack or ToR switches.
Parameter Description
TOR-DSW CPU CPU usage per each of the ToR switches. Current value and trending
graph.
TOR-DSW Power Power consumption per each of the ToR switches. Current value and
trending graph.
TOR-DSW Memory Memory usage per each of the ToR switches. Current value and trending
graph.
In case one switch fails, the other takes the load and the
system keeps on running. In this scenario, the uptime is
not reset.
TOR-DSW Temperature per each of the ToR switches. Current value and trending
Temperature graph.
[Link] VM - Load
This dashboard monitors the CPU and memory usage of the VMs within the NPCI/CIDI.
Use the drop-down menus in the upper left to filter the VMs on platform, project (for example,
Dialog MM, Dialog Hub or Dialog NMS), and instance.
Parameter Description
Cloud - Network I/O Network statistics. Trending graph of the throughput per instance.
DISK : read/write byte Trending graph of the read and write rates in disk.
rate
DISK : read/write Trending graph of the read and write request in disc per second.
requests per sec
Memory Assigned Memory Assigned to the VM. Note that this value must be static unless
more memory is assigned.
5.2 License
The License node provides an overview of the current usage of features and capabilities on
platform level and on modem level. For example: 'Throughputs'.
This overview can be used to compare the actual usage of features and capabilities or entitlements
with the available features and capabilities as defined in the Purchase Order (licenses).
The available licenses are grouped according to:
• Platform on page 73
• Modem on page 74
The parameters are generated from events that measure the use of the licensed product software
instances.
Platform License
The parameters of the platform license are described in the table below.
Forward Link This is the sum of the peak information rate or PIR used Mbps
Throughput S2 (DVB-S2 per satellite network. Click on the parameter to see the
/ DVB-S2X) used PIR per satellite network.
Return Link Throughput This is the sum of the peak information rate or PIR used Mbps
per return link technology. Click on the parameter to see
the used PIR per return link technology.
Modem License
The parameters of the modem license are described in the table below.
Return Link Technology This is the number of MDM3300 modems that are
- 4CPM MDM3300 provisioned to use the 4CPM MF-TDMA return link
technology. Click on the parameter for a list of the
individual terminals.
Return Link Technology This is the number of MDM3X00 modems that are
- HRC-SCPC MDM3100 provisioned to use the HRC SCPC return link
/ MDM3300 technology. Click on the parameter for a list of the
individual terminals.
Return Link Technology This is the number of MDM3X00 modems that are
- HRC-MxDMA provisioned to use the HRC Mx-DMA return link
MDM3100 / MDM3300 technology. Click on the parameter for a list of the
individual terminals.
Return Link Technology This is the number of MDM3300 modems that are
- S2 MDM3300 provisioned to use the S2 return link technology. Click
on the parameter for a list of the individual terminals.
For more information about the Network Resources interface, refer to the Newtec
Dialog Configuration User Guide.
5.4 Profiles
This is the provisioning interface where you define:
• Attachment profiles. A terminal is linked with the forward and return link resources of each satellite
network in which the terminal should exist via a dynamic attachment profile. An attachment profile
contains one or more home network attachments and optionally visited network attachments. The
home network attachment defines the beam resources of the operator that serves the terminal.
The visited network attachment defines the beam resources of the networks of another operator.
• BGP profiles. When using BGP as the routing protocol for layer 3 network resources it is possible
to filter the routes which are exchanged across BGP peers.
• Classification profiles. A classification profile is a set of rules that classify ingress unicast traffic into
QoS traffic classes (for both forward and return link).
• Firewall profiles. A firewall profile allows you to block any incoming traffic, except the one that
matches specific rules.
• Remote configuration profiles. In the Remote Configuration Profile you define if remote
configuration of the satellite interface on the modem is allowed or not.
• Service profiles. A service profile specifies the shaping settings for the QoS classes and terminal
circuits.
For more information about the Profiles interface, refer to the Newtec Dialog
Configuration User Guide.
For more information about the Beam Provisioning interface, refer to the Newtec
Dialog Configuration User Guide.
For more information about the SatNet Provisioning interface, refer to the Newtec
Dialog Configuration User Guide.
For more information about the Transponder Provisioning interface, refer to the Newtec
Dialog Configuration User Guide.
For more information about the FW Carrier Provisioning interface, refer to the Newtec
Dialog Configuration User Guide.
For more information about these provisioning interface, refer to the Newtec Dialog
Configuration User Guide.
The card displays the forward link configuration and the overall satellite network parameters.
The parameters are described in the table below. The traffic rates include unicast, multicast and
control traffic, and encapsulation overhead.
Forward Link This parameter indicates how much of the forward link is %
Occupation used. The value equals 100*(actual symbol
rate/configured symbol rate).
Send Rate This is the rate at which the CSE (shaper) transmits kbps
forward traffic bits. The rate includes unicast, multicast
and control traffic, and eTCP overhead for unicast traffic.
Send Symbol Rate This is the rate at which the CSE (encapsulator) Mbaud
transmits forward traffic symbols. The rate includes
unicast, multicast and control traffic, and encapsulation
overhead.
Send Packet Rate This is the rate at which the CSE (shaper) transmits packets/s
forward traffic packets. The rate includes unicast,
multicast and control traffic, and eTCP overhead for
unicast traffic.
Dropped Bitrate The rate at which the CSE (shaper) drops forward traffic kbps
bits. The rate includes unicast, multicast and control
traffic, and eTCP overhead for unicast traffic.
Dropped Packet Rate This is the rate at which the CSE (shaper) drops forward packets/s
traffic packets. The rate includes unicast, multicast and
control traffic, and eTCP overhead for unicast traffic.
Link Efficiency This parameter indicates how efficiently the forward link bits/baud
is used. The value equals actual bit rate/configured
symbol rate.
FWD Link Delay Average delay the packet stays in the queues. ms
For more information about the configuration parameters of the forward link, refer to
the Newtec Dialog Configuration User Guide.
The card mainly displays the forward carrier configuration. The Physical Layer Efficiency indicates
the usage of the physical layer. The value equals 100*(actual symbol rate/configured symbol rate) of
the forward carrier.
For more information about the configuration parameters of the forward carrier, refer to
the Newtec Dialog Configuration User Guide.
Unicast Send Bitrate This is the rate at which the CSE (shaper) transmits kbps
forward unicast traffic bits. The rate includes eTCP
overhead.
Unicast Send Packet This is the rate at which the CSE (encapsulator) packets/s
Rate transmits forward unicast traffic packets. The rate
includes eTCP overhead.
Unicast Dropped Bitrate This is the rate at which the CSE (shaper) drops forward kbps
unicast traffic bits. The rate includes eTCP overhead.
The traffic rates are described in the table below. The rates include multicast traffic but exclude the
terminal software multicast streams. The software multicast streams are accounted in the control
statistics.
Multicast Send Bitrate This is the rate at which the CSE (shaper) transmits kbps
forward multicast traffic bits.
Multicast Send This is the rate at which the CSE (encapsulator) kbaud
Symbolrate transmits forward multicast symbols. The rate includes
encapsulation overhead.
Multicast Send Packet This is the rate at which the CSE (shaper) transmits packets/s
Rate forward multicast traffic packets.
Multicast Dropped This is the rate at which the CSE (shaper) drops forward kbps
Bitrate multicast traffic bits.
The left column show the rates for all forward control traffic, this includes a.o. forward signaling and
the terminal software multicast traffic. The right column only shows the rates for the software
multicast traffic. The traffic rates are described in the table below.
Send Rate This is the rate at which the CSE (shaper) transmits kbps
forward control traffic bits.
Send Symbolrate This is the rate at which the CSE (encapsulator) kbaud
transmits forward control traffic symbols. The rate
includes encapsulation overhead.
Send Packet Rate This is the rate at which the CSE (shaper) transmits packets/s
forward control traffic packets.
Dropped Bitrate This is the rate at which the CSE (shaper) drops forward kbps
control traffic bits.
The Maximum Symbol Rate Of The Link is set when creating the forward carrier.
Click on a node in the tree structure to view its parameters. The right side of the card pane displays:
• Node configuration information, such as the name of the pool, the identifier of the forward link,
CIR, PIR and weight values, etc.
• Two tabs at the bottom: Items and Monitoring.
The Items tab shows information about the child nodes.
The Monitoring tab shows monitored parameters of the selected node, such as transmit rate
and CIR congestion.
Forward Pools
In this card all information is shown on the same card and is structured in several tables.
The L0 pool corresponds with the container pool. The L1 pools correspond with the class- or
transport-based child pools of the container pool and the L2 pools corresponds with the class pools
of the class-based pool. The pool information and metrics are represented in tables.
Transmit Rate This is the rate at which the CSE (shaper) forward pool kbps or
transmits forward traffic for the forward pool. The traffic kbaud *
rate includes unicast and eTCP overhead .
This parameter exists for all pools.
Transmit Rate Packet This is the rate at which the CSE (shaper) transmits Pps
forward traffic packets for the forward pool. The traffic
rate includes unicast and eTCP overhead for unicast
traffic.
This parameter exists for all pools.
Drop Rate This is the rate at which the CSE (shaper) drops forward kbps
traffic for the forward pool. The traffic rate includes
unicast and eTCP overhead.
This parameter exists for all pools.
EIR Shaping Ratio This parameter indicates the level of congestion in the
pool. The value can range from 0 to 1000, where 1000
means there is no congestion.
This parameter only exists for L1 and L2 pools.
* The traffic unit is kbps for the L0 (container) and L2 (QoS classes) pools but depends on the Child
Pool Shaping Mode setting of the container Pool for the L1 pools: Bit Rate Shaping or Symbol Rate
shaping.
For more information about the configuration parameters of the forward pools and QoS
classes, refer to the Newtec Dialog Configuration User Guide.
There are several DATA displays, divided per return link technology:
• HRC-MxDMA Return Capacity Groups, see HRC Mx-DMA on page 90.
• HRC-MxDMA Tree View, see HRC Mx-DMA on page 90.
• MRC Return Capacity Group, see MRC NxtGen Mx-DMA on page 94.
• MRC Tree View, see MRC NxtGen Mx-DMA on page 94.
Select a display in the card navigation pane or via the drop-down box in the upper left of the card
pane.
On a frequency level, an HRC Mx-DMA return capacity group or RCG is defined with a start and stop
frequency
On a Quality of Service or QoS level, an HRC Mx-DMA RCG or root pool is divided in one or more
return pools, which can be transport-based or class-based, dedicated or shared, etc. A class-based
return pool on its turn can have one or more child pools, which correspond with the class pools.
The first two tables display the configuration parameters and metrics of the available HRC Mx-DMA
return capacity groups.
Requested Rate This is the bit rate which is requested for the return kbps
capacity group. The rate includes unicast traffic and
encapsulation overhead.
Allocated Rate This is the bit rate which is assigned to the return kbps
capacity group. The rate includes unicast traffic and
encapsulation overhead.
Receive Bitrate This is the rate at which the DCP receives traffic bits for kbps
the return capacity group. The rate includes unicast
traffic and eTCP overhead.
Receive Packet Rate This is the rate at which the DCP receives packets for packets/s
the return capacity group. The rate includes unicast
traffic and eTCP overhead.
Physical Layer This parameter indicates how efficiently the physical bps/Hz
Efficiency layer is used. These are the number of bits that are used
per Hz.
Best ModCod Efficiency This is the number of bits that are used per Hz for the bps/Hz
best MODCOD.
Requested Unsolicited This is the number of ulogon requests from the HRC
Logon Count controller. This is available when ulogon is enabled.
The following two tables display the configuration parameters and metrics of the available return
pools and class pools.
EiR Shaping Ratio This parameter indicates the level of congestion in the
pool. The value can range from 0 to 1000, where 1000
means there is no congestion.
Requested Rate The bit rate requested for the return pool. The rate kbps
includes unicast traffic and encapsulation overhead.
Allocated Rate The bit rate allocated to the return pool. The rate kbps
includes unicast traffic and encapsulation overhead.
Req. Rate The bit rate requested for the class pool. The rate kbps
includes unicast traffic and encapsulation overhead.
All. Rate The bit rate allocated to the class pool. The rate includes kbps
unicast traffic and encapsulation overhead.
EiR Shaping Ratio This parameter indicates the level of congestion in the
pool. The value can range from 0 to 1000, where 1000
means there is no congestion.
For more information about the configuration parameters of HRC Mx-DMA resources,
refer to the Newtec Dialog Configuration User Guide.
On a frequency level, an MRC NxtGen Mx-DMA return capacity group or RCG is defined with a start
and stop frequency
On a Quality of Service or QoS level, an MRC NxtGen Mx-DMA RCG or root pool is divided in one
or more return pools, which can be transport-based or class-based, dedicated or shared. A
class-based return pool on its turn can have one or more child pools, which correspond with the
class pools.
The first two tables display the configuration parameters and metrics of the available MRC return
capacity groups.
Allocated QoS Carriers Estimates the number of carriers that would be used if
free capacity is disabled.
Requested Rate Requested bit rate for the return capacity group. The kbps
rate includes unicast traffic and encapsulation overhead.
Allocated Rate Assigned bit rate to the return capacity group. The rate kbps
includes unicast traffic and encapsulation overhead.
Keep Alive Rate Average keep alive rate assigned to the MRC RCG.
Frame Error Ratio Ratio of received MRC baseband frames with an error
and the total number of received MRC baseband
frames.
The following two tables display the configuration parameters and metrics of the available return
pools and class pools.
EiR Shaping Ratio Indicates the level of congestion in the pool. The value
can range from 0 to 1000, where 1000 means there is
no congestion.
Requested Rate Requested bit rate for the return pool. Includes unicast kbps
traffic and encapsulation overhead.
Allocated Rate Allocated bit rate to the return pool. Includes unicast kbps
traffic and encapsulation overhead.
Requested Rate Requested bit rate for the class pool. Includes unicast kbps
traffic and encapsulation overhead.
Allocation Rate Allocated bit rate to the class pool. Includes unicast kbps
traffic and encapsulation overhead.
EiR Shaping Ratio Indicates the level of congestion in the pool. The value
can range from 0 to 1000, where 1000 means there is
no congestion.
This card has a tree menu at the left side of the card pane. The top node of the tree represents an
NxtGen Mx-DMA MRC return capacity group. Under the RCG node, you will find one or more return
pools.
Click on a node in the tree menu to view its parameters. The right side of the card pane displays:
• Node configuration information, such as the name of the pool, CIR and PIR values, and the
metrics of that node.
• Details of the child nodes.
The information in the MRC Tree View display is the same as what you find in MRC Return Capacity
Groups.
For more information about the GXT File Provisioning interface, refer to the Newtec
Dialog Configuration User Guide.
The dashboard displays parameters related to the provisioned forward multicast streams. Each
parameter is displayed as a trend over a certain time period. The time period is indicated in the
upper right of the card pane. Hover your mouse over the graph panel to get the parameter value for
a specific time. Each graph panel also shows the minimum, maximum, average and current value of
the parameter at the bottom of the panel.
The parameters are monitored at the CSE VM and described in the table below.
Sent Bit Rate This is the rate at which the CSE (shaper) transmits bps
forward multicast traffic bits.
Sent Packet Rate This is the rate at which the CSE (shaper) transmits pps
forward multicast traffic packets.
Drop Bit Rate This is the rate at which the CSE (shaper) drops forward bps
multicast traffic bits.
Drop Packet Rate This is the rate at which the CSE (shaper) drops forward pps
multicast traffic packets.
Delay This is the time that packets are queued in the CSE ms
(shaper).
5.6 Terminals
5.6.1 Intro
Under the Terminals node you can find several fault and performance interfaces, and provisioning
interfaces.
The fault and performance interfaces provide information about your terminals. All parameters are
collected and visualized using the DataMiner application.
For more information about the TICS interface, refer to the Newtec Dialog Terminal
Installation Certification System Manual.
Select Terminal Certification Monitoring under the Terminal Certification node in the surveyor
tree to view the terminal certification parameters.
The parameters are spread over two DATA displays:
• Devices
• Terminals
Select a display in the card navigation pane or via the drop-down box in the upper left of the card
pane.
Devices
This card provides status information of the TICS equipment and measurement channels.
Terminals
This card provides information about the certification results for each terminal where the certification
has been performed.
• Advanced (TSDB Only): Choose this type if you want to collect metrics in real time, but you do
not use the DataMiner® database. The advanced metrics are only be available from the TSDB,
but the standard monitoring is still synchronized with the DataMiner® database. This reduces the
load on the system in large networks. The polling interval for the metrics is 30 seconds by default.
• Standard: Choose this type if you want to collect averaged parameters. The parameters are
averaged over five minutes. Less parameters are polled than the Advanced type but more
terminals can be monitored.
• None: Choose this type if you do not want to collect parameters for this modem.
When the Monitoring Type is set to Advanced, the Monitoring Option appears. Select one of the
following values:
• Local: Only terminal related parameters from the hub are monitored. The extra terminal
parameters are not fetched over the satellite link. This is the default value.
• Remote: Additional terminal parameters, such as terminal errored frames, modem temperature,
RX level statistics, etc. are fetched over the satellite link every 10 seconds. Keep in mind that this
monitoring option consumes satellite resources.
In case you have a large number of mobile terminals (>2000) and satellite networks
(>25) Standard monitoring must be disabled. If standard monitoring is enabled, the
DMA will run into severe performance issues.
This means that you must not select the standard monitoring type and that, when you
select the advanced monitoring type, the standard monitoring part must be disabled.
Only ST Engineering's personnel can disable the standard monitoring part in advanced
monitoring. Contact ST Engineering's customer services to request the change.
Select a terminal resource in the surveyor tree to display the corresponding information in the card
pane.
The Standard Terminal Management card has a filter section allowing you to filter on VNO and
terminal.
When selecting the VNO, the KPI link becomes available. Clicking this link displays the window
shown below.
The General section displays the aggregated parameters. The parameters are described in the table
below.
VNO Total Forward This is the rate at which the CSE transmits traffic bits to kbps
Throughput the terminals of the VNO. The rate includes unicast
traffic and eTCP overhead.
VNO Total Return This is the rate at which the DCP receives traffic bits kbps
Throughput from the terminals of the VNO. The rate includes unicast
traffic and eTCP overhead.
VNO Total Forward This is the rate at which the CSE drops traffic bits kbps
Dropped Rate destined to the terminals of the VNO. The rate includes
unicast and eTCP overhead.
VNO Logged On This is the number of the VNO's terminals that are
Terminals logged on.
VNO Logged Off This is the number of the VNO's terminals that are
Terminals logged off.
The Forward Throughput, Return Throughput and Forward Dropped Rate is also monitored per
QoS class. The sum of the throughputs per QoS class corresponds with the value of the
corresponding general parameter.
The Forward Link Quality section displays the minimum, maximum and average Es/N0 value. The
forward Es/No is measured at the VNO's terminals.
When you select a terminal, the KPI link becomes available. Clicking this link displays the following
terminal metrics:
You can only select terminals with Monitoring Type set to Standard or Advanced.
For more information about the Monitoring Type, refer to Terminal Provisioning on
page 101.
Total Forward This is the rate at which the CSE (shaper) forwards kbps
Throughput traffic bits to the terminal. The rate includes unicast
traffic and eTCP overhead.
Total Return Throughput This is the rate at which the DCP receives traffic bits kbps
from the terminal. The rate includes unicast traffic and
eTCP overhead.
Total Forward Dropped This is the rate at which the CSE (shaper) drops traffic kbps
Rate bits destined to the terminal. The rate includes unicast
traffic and eTCP overhead.
The Forward Link Quality section displays the minimum, maximum and average Es/N0 value
measured at the terminal. The peak hold Es/N0 value is the maximum value of the forward Es/N0
values measured over a period of 24 hours.
The Forward Throughput, Return Throughput and Forward Dropped Rate is also monitored per
QoS class. The sum of the throughputs per QoS class corresponds with the value of the
corresponding general parameter.
Additionally, the QoS classes also display the configured CIR and/or PIR value.
This is only available for terminals with Monitoring Type set to Advanced. For more
information about the Monitoring Type, refer to Terminal Provisioning on page 101.
FWD Es/N0 This is the energy per symbol (Es) to noise power dB
spectral density (No) ratio of the forward link measured
RTN Es/N0 [HRC] This is the energy per symbol (Es) to noise power dB
spectral density (No) ratio of the return link of the
terminal measured at the HRC demodulator and
signaled to the HRC controller (HRCCTL). It is an
indication of the return link quality.
This metric is available in case the return link
technology is HRC Mx-DMA or HRC SCPC.
RTN Es/N0 [MRC] This is the energy per symbol (Es) to noise power
spectral density (No) ratio of the return link of the
terminal measured at the MRC demodulator and
signaled to the MRC controller (MRCCTL). It is an
indication of the return link quality.
Total Throughput This is the total rate at which the CSE (shaper) forwards kbps
FWD traffic bits to the terminal. The rate includes unicast
traffic and eTCP overhead.
Total Throughput This is the total rate at which the DCP receives traffic kbps
RTN bits from the terminal. The rate includes unicast traffic
and eTCP overhead.
• Terminal GUI, which is the link to the local modem GUI as a normal user.
• Terminal GUI (admin), which is the link to the local modem GUI as an expert user.
• Provisioning, which is the link to the provisioning interface of the terminal.
For more information on how to provision a terminal, refer to the Newtec Dialog
Configuration User Guide.
The card displays all kind of information of the terminal, such as MAC address, software version and
return link technology.
You can also find the satellite network in which the terminal is provisioned and the associated HPS
or Hub Processing Segment. Use this HPS name to retrieve the satellite network specific metrics.
For more information, refer to HPS.
Click next to the Satellite Network ID/Name parameter to display the display the trend graph
over time. This is useful to verify in which satellite network a terminal was active.
The card displays general traffic information and parameters related to the HRC Mx-DMA return link
technology.
The Polled Timestamp is the timestamp at which the parameters were polled.
The HRC Conf Settings displays the configuration settings of the HRC SCPC carrier and the power
settings.
The general Traffic information shows the parameters described in the table below.
Forward Modcod This is the MODCOD and frame size (normal/short) that
the S2 forward carrier is using.
The CSE (ACM controller) decides upon the MODCOD.
It will listen to the requested MODCOD from the modem
but can select a more robust MODCOD to fill up
available capacity.
Forward Es/N0 This is the energy per symbol (Es) to noise power
spectral density (N0) ratio of the forward link measured
at the modem and signaled to the hub. It is an indication
of the forward link quality.
Max Hold FWD Es/N0 This is the maximum value of the forward Es/N0 values
measured over a period of 24 hours.
Total Forward This is the total rate at which the CSE (shaper) forwards kbps
Throughput traffic bits to the terminal. The rate includes unicast
traffic and eTCP overhead.
Total Return Throughput This is the total rate at which the DCP receives traffic kbps
bits from the terminal. The rate includes unicast traffic
and eTCP overhead.
Symbol Rate This is the current symbol rate used by the modem. kBd
The rate includes encapsulation overhead.
The HRC Traffic related metrics are described in the table below.
Allocated Bitrate This is the bit rate allocated to the terminal. The rate kbps
includes encapsulation overhead. This value is
averaged over the measurement interval.
Frame Error Ratio This is the ratio of received HRC baseband frames %
with an error and the total number of received HRC
baseband frames.
Errored Seconds Count This is the total number of measured errored seconds
seconds. An errored second is a second when a
provisioned terminal has no valid service without
packet loss.
The Link Quality related metrics are described in the table below.
ACM Margin The difference with the link margin is that this value dB
is used by the internal algorithms.
N0 deviation = Rx N0 - Avg N0
BUC Frequency Offset This is the measured frequency offset from BUC. Hz
This value should be very small when the modem
and BUC are slaved to the same reference clock.
Rx Level Density This is the received power level density measured at dBm/Hz
the hub.
Tx Power Density This is the power level density transmitted by the dBm/Hz
terminal. This is signaled to the terminal.
Out Of Lock During This is the total number of times that the terminal
Measurement Interval lost lock.
Logon Time This is the time it takes for the terminal to logon. seconds
Logon Search Range During the logon a terminal will scan a specific Hz
frequency range to compensate a possible
terminal TX frequency offset.
This value indicates the search range of the
previous log on attempt. This is independent
whether the previous logon attempt was
successful or not.
Requested Unsolicited Logon This is the total number of ulogon requests by the
Count HRC controller for the terminal.
Received Unsolicited Logon This is the total number ulogons received from
Count the terminal.
[Link].3 MRC
The card displays general traffic information and parameters related to the NxtGen Mx-DMA MRC
return link technology.
The general Traffic information shows the parameters described in the table below.
Forward Modcod This is the MODCOD and frame size (normal/short) that
the S2 forward carrier is using.
The CSE (ACM controller) decides upon the MODCOD.
It will listen to the requested MODCOD from the modem
but can select a more robust MODCOD to fill up
available capacity.
Forward Es/N0 Energy per symbol (Es) to noise power spectral density
(N0) ratio of the forward link measured at the modem
and signaled to the hub. It is an indication of the forward
link quality.
Forward Symbol Rate Assigned symbol rate for the terminal. symbol/s
ec
Total Forward Total rate at which the CSE forwards traffic bits to the kbps
Throughput terminal. The rate includes unicast traffic and eTCP
overhead.
Total Return Total rate at which the DCP receives traffic bits from the kbps
Throughput terminal. The rate includes unicast traffic and eTCP
overhead.
The Time and Frequency Statistics are described in the table below.
HPA Model Tx Power Current safety margin applied with respect to the dB
Sat Margin transmission power saturation.
Path Gain Current Tracked current path gain for the terminal. dB
Path Gain Clear Sky Tracked clear sky path gain for the terminal. dB
BEPD Clear Sky Tracked clear sky BEPD power density limit at MCD dB
where terminal traffic bursts are landing.
ACM Margin Total Current total ACM margin for the terminal. dB
Current
System Noise Tracked system noise density at the MCD where dBm/Hz
Density Current terminal traffic bursts are landing
Regrowth Limited Indicates whether the terminal TX power level has been
limited because of available BUC power.
Possible values: yes, no, indeterminate, not applicable.
Total ACM Margin Total ACM Margin including margin for errored bursts. dB
RMS phase noise Root mean square of the measured phase noise degrees
expressed in degrees
Offset to phase noise Offset to the default phase noise mask (-70dBc/Hz at dB
mask 1kHz) in dB.
For more information on transmit modes
and phase noise masks, please refer to the
Dialog Functional Description.
Cycle slip bursts The cycle slip counter counts the number of times a #
high phase offset was measured in the phase tracking
loop.
Symbol Rate Current symbol rate used by the modem. The rate kBd
includes encapsulation overhead.
Requested bitrate Bit rate requested by the terminal in the return capacity kbps
group
Allocated Bitrate Bit rate allocated to the terminal, including encapsulation kbps
overhead. This value is averaged over the
measurement interval.
Frame Error Ratio Ratio of received MRC baseband frames with an error %
and the total number of received MRC baseband
frames.
Codeword error ratio Ratio of undecodable FEC words to the total amount of %
received FEC words
Physical Layer Efficiency of tthe physical layer: the number of bits bits/Hz
Efficiency which are used per Hz
The Link Quality related metrics are described in the table below.
Tx Power Power level transmitted by the terminal. This power level dBm
is signaled to the terminal.
Tx Power Density Power level density transmitted by the terminal. This is dBm/Hz
signaled to the terminal.
Rx Power Density Received power level density measured at the hub. dBm/Hz
The card shows information about the unicast circuit configuration, such as CIR and PIR, and the
unicast rates per QoS class.
The information is displayed in several tables. Each table has a row per existing QoS class.
FWD QoS
The forward QoS parameters are monitored at the CSE VM. The parameters are described in the
table below.
FWD QoS Satellite Rate This is the rate at which the CSE (shaper) transmits kbps
forward unicast traffic bits for the modem and the
specific QoS class. The rate includes eTCP
overhead.
FWD QoS Dropped Rate This is the rate at which the CSE (shaper) drops kbps
forward unicast traffic bits for the modem and the
specific QoS class. The rate includes eTCP
overhead.
FWD QoS Average Delay This is the average time that packets are queued in ms
the CSE (shaper) for a modem and specific QoS
class.
RTN QoS
The return QoS satellite rate is monitored at the DCP VM. The satellite rate is described in the table
below.
RTN QoS Satellite Rate This is the rate at which the DCP receives the return kbps
unicast traffic bits from the modem and specific QoS
class. The rate includes eTCP overhead.
HRC QoS
The HRC QoS rates are monitored at the HRCCTL VM. The rates are described in the table below.
HRC Shaping Assigned This is the bit rate assigned by the HRC controller kbps
Rate for a specific QoS class. The rate includes
encapsulation overhead.
HRC Shaping Requested This is the bit rate requested by the terminal for a kpbs
Rate specific QoS class. The rate includes encapsulation
overhead.
MRC QoS
The MRC QoS rates are monitored at the MRCCTL VM. The rates are described in the table below.
MRC Shaping Assigned This is the bit rate assigned by the MRC controller kbps
Rate for a specific QoS class. The rate includes
encapsulation overhead.
MRC Shaping Requested This is the bit rate requested by the terminal for a kpbs
Rate specific QoS class. The rate includes encapsulation
overhead.
The card shows information about the multicast circuit configuration, such as IP address, CIR and
PIR, and the received rate.
The Received Rate is the rate at which the DCP receives multicast traffic bits from the modem.
When the Monitoring Option is set to Remote additional terminal metrics, such as terminal errored
frames, modem temperature, RX level statistics, etc. are fetched over the satellite link every 10
seconds. For more information about the Monitoring Option, refer to Terminal Provisioning on page
101.
Device Status
This section provides information about the uptime, temperature and CPU load.
Qos Statistics
This section provides information about the quality of service per active QoS class.
The parameters are described in the table below.
Return Tx Bitrate This is the rate at which the TelliShape application in the kbps
terminal transmits return traffic bits. The rate includes
eTCP overhead.
Return Drop Packet This is the number of packets that the TelliShape packets
Count application in the terminal has dropped.
Return Queue Time This is the average time that a packet is queued in the ms
TelliShape application in the terminal.
Demodulator Statistics
This section provides information about the demodulator and MODCOD. The parameters are
described in the tables below.
Demod Statistics
Demod Lock Events This is the number of times the terminal acquired a
Count terminal lock.
Demod BBF Drop Frame This is the number of baseband frames that the terminal
Count could not decode.
Demod Operational This is the MODCOD that is used for the terminal. It is
Modcod determined by the ACM algorithm (ACM client).
Phase Noise Margin This is the difference between the estimated phase dB
noise and the DVB-S2 reference mask (outbound VSAT
services critical mask).
MODCOD Statistics
There is an entry for each forward MODCOD configured on the forward link.
MODCOD BBF Frame This is the number of baseband frames that the terminal
Count has received using this MODCOD.
MODCOD BBF Drop This is the number of baseband frames that the terminal
Framecount has received using this MODCOD and which could not
be decoded.
[Link].7 BGP
The Operational Commands interface allows you to reboot a terminal. Click Reboot and monitor the
response.
The item will only display the terminals with Monitoring Type set to Advanced. For
more information about the Monitoring Type, refer to Terminal Provisioning on page
101.
The card displays the provisioned terminals where the Monitoring Type is set to Advanced.
Alarms Table
This section monitors the parameters described in the table below.
The alarms are only displayed for terminals that are Logged On and not Locked.
The parameter is highlighted in green when there is no error.
Burst Error Ratio This parameter indicates how many allocated bursts %
are corrupt or incorrect. The ratio equals lost volume
/(idle + busy + lost volume). The higher the value,
the more bursts are lost.
This value is available for terminals using the 4CPM
return link technology.
Frame Error Ratio This parameter indicates how many HRC baseband
frames have an error. The value is the ratio of the
received HRC baseband frames with an error and
the total number of received HRC baseband frames.
For more information about the forward and return unicast circuit metrics, refer to
Bidirectional Unicast Circuit on page 115.
For more information about the return multicast circuit metrics, refer to Return Multicast Circuit on
page 117.
For more information about the remote terminal monitoring metrics, refer to
Remote Terminal Monitoring on page 117.
[Link] BGP
For more information about the BGP statistics, refer to BGP on page 120.
[Link] Terminals
The card displays the terminals for which beam roaming has been enabled and for which the
administrative state is unlocked.
[Link] Beams
The card displays the number of logged on terminals for each beam that has been provisioned.
[Link] Statistics
Non operational This is the number of mobile terminals that are not
operational.
[Link] Alarms
The alarms are described in the table below. The persistence failure alarms are monitored.
Persistence Save Failure When the value is On, the mobility Contact ST Engineering
orchestrator has issues with saving one iDirect customer support.
or more files.
Persistence Load Failure When the value is On the mobility Contact ST Engineering
orchestrator has issues with loading iDirect customer support.
one or more files.
Satellite Network Failure When the value is On at least one Contact ST Engineering
satellite network is failing. iDirect customer support.
HNO Provisioning
There is only one HNO domain, which is created during the installation of the hub module. You can
view the domain when logged in as HNO user.
User Provisioning
As a VNO you can view and create user accounts that are linked to your domain. As an HNO you
can view and create user accounts that are linked to your domain and to your VNO domains.
VNO provisioning
As an HNO you can view and create VNO domains.
For more information about the HNO, User and VNO provisioning interface, refer to the
Newtec Dialog Configuration User Guide.
Queries are how Grafana panels communicate with data sources to get data for the visualization. A
query is a question written in the query language used by the data source. If the query is properly
formed, then the data source responds. How often the query is sent to the data source and how
many data points are collected can be adjusted in the panel data source options. Grafana supports
up to 26 queries per panel.
Grafana can visualize, explore, and alert on data from many different databases and cloud services.
Each database or service type is accessed from a data source.
The following data sources are available in the Dialog environment:
• platform_metrics_HPSP; accesses the InfluxDB on MON-0-0 deployed on the HMMS sub-system
or NMS sub-system depending on where you are checking the Local Monitoring item.
• MON-0-1 and MON-0-2; accesses the InfluxDB instance on the dedicated MON VM. MON is
deployed on both the HMMS and NMS in an active standby constellation.
• platform-logs; accesses the Elasticsearch database on LOG-0-0.
Each data source has a specific query editor that is customized for the features and capabilities that
the particular data source exposes. You can combine data from multiple data sources into a single
dashboard, but each panel is connected to a specific data source that belongs to a particular
organization.
Click the Alert icon to set an alert rule and send notifications when the conditions are met.
Click the Save dashboard icon in the upper right of the Grafana screen to save the dashboard. The
dashboard can be saved to an existing folder or you can create a new folder.
The screenshot below is a new dashboard created in de Satellite Network Monitoring folder.
You can create multiple dashboards. To switch from one dashboard to another, including the Dialog
predefined ones, click the folder (Satellite Network Monitoring in the example above) to select a
dashboard that exist within this folder or click the dashboard name (My Own Dashboard in the
example above) to go to another folder and select a dashboard in that folder.
Click the Dashboard settings icon in the upper right of the Grafana screen to delete a dashboard.
7 Alarms
This feature is not available for data that is stored in the InfluxDB or Elasticsearch
DataMiner continuously retrieves a wide variety of parameter values from all elements. When a
parameter is monitored, each time a value is retrieved from an element, that value is compared to a
user-defined threshold. Each time that threshold is violated, DataMiner will generate an alarm. Most
of the alarm functionality is available via the alarm console. To open the alarm console, single-click
the alarm bar at the bottom of the NMS GUI or click in the bottom right corner of the alarm bar.
To view detailed information about an alarm, right-click an alarm in the Alarm Console, and select
Open > Alarm Card.
The alarm thresholds for all monitored parameters is defined in an alarm template. An alarm
template is an XML file that contains all alarm thresholds for all parameters defined in a particular
DataMiner protocol. It is an overlay file that overrides the default alarm thresholds defined in a
DataMiner protocol.
To view the alarm template of a particular element, execute the following steps, right-click on the
element item in the surveyor tree and select Protocols & Templates > View alarm template
'Default' from the drop-down menu.
DataMiner® has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about alarms and handling alarms.
8 Reports
This feature is not available for data that is stored in the InfluxDB or Elasticsearch
DataMiner generates graphical reports showing a multitude of statistical data and operational
metrics.
Built-in reports are available when you click an item in the surveyor tree. Select REPORTS in the
card navigation pane. There are two displays:
• General: This display, depending on the type of item you have selected in the surveyor tree,
shows a number of graphs with alarm information for a particular time span.
• More: This display opens the reports in the Reporter app on page 134.
You can also open the report for a particular parameter on a DATA display of an element card.
Double-click the parameter and select DETAILS in the upper left of the card pane.
The figure below displays the report for the Frame Error Ratio parameter of an advanced terminal
element.
Built-in reports are also available in the Reporter app. Click in the navigation pane and then
select Reports & Dashboards.
DataMiner® has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about reports.
9 Trending
This feature is not available for data that is stored in the InfluxDB or Elasticsearch
Trend graphs make it possible to view and compare trend data logged by DataMiner.
For performance reasons, trending is only activated for a limited number of parameters. Trending
templates determine which parameters are trended.
Parameters for which trending graphs are available are indicated with the trend graph icon . Click
the icon to display the trend graph of the parameter.
DataMiner® has a comprehensive Help functionality. Click ? in the header bar of the
NMS GUI to learn more about trending and handling trend graphs.