0% found this document useful (0 votes)
39 views34 pages

Release - Note - Dialog 2.4.1

The document provides release notes for Dialog version 2.4.1, detailing new features, enhancements, and bug fixes. Key features include flow fairness improvements, mobility switch mechanisms, and enhanced NMS GUI usability. It also outlines upgrade paths, backward compatibility, and known issues associated with the release.

Uploaded by

Mohamed Mustafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
39 views34 pages

Release - Note - Dialog 2.4.1

The document provides release notes for Dialog version 2.4.1, detailing new features, enhancements, and bug fixes. Key features include flow fairness improvements, mobility switch mechanisms, and enhanced NMS GUI usability. It also outlines upgrade paths, backward compatibility, and known issues associated with the release.

Uploaded by

Mohamed Mustafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 34

“Release Note

for
Dialog 2.4.1”

Version:
1.1

Date:
08 Apr, 2022
Authors List
Name Company

Reviewers List

Version Date Description


1.1 8 April 2022 Release 2.4.1.8
1.0 2 Feb 2022 Release 2.4.1.7

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 1 of 34 www.idirect.net
Table of Contents
0 Introduction .......................................................................................................................................... 4
1 Release Main Features ........................................................................................................................ 4
1.1 Flow Fairness ................................................................................................................................ 4
1.2 Mobility switch - make before break (split management-control plane for dynamic routing)
4
1.3 Hub MQTT event interface - route advertisement events ......................................................... 5
1.4 DMM beam overwrite on targetBeam of OpenAMIP settings (Beam Switch) ......................... 5
1.5 Provide costumer data within beam switch command (return multicast config). ................. 5
1.6 Mobility Without Beam information ............................................................................................ 5
1.7 Unidirectional command to unmute the modem ....................................................................... 5
1.8 NMS& NMS apps geo-redundancy - non-real-time config sync - automated switch ............ 6
1.9 NMS+Hub geo-redundancy for XIF ............................................................................................. 6
1.10 AES256 FWD signaling ............................................................................................................. 6
1.11 Mx-DMA Multi-Resolution Coding (MRC) return technology support ................................. 6
1.12 HRC : allow to configure the free capacity ............................................................................. 7
1.13 Support modem type SMB3315 and MDM3315 ...................................................................... 7
1.14 Improved C/D indication on modems with FPGA-based demodulator (MDM5010 +
AMC5001) ................................................................................................................................................. 7
1.15 Modem metrics in hub module TSDB ..................................................................................... 7
1.16 NMS GUI usability enhancement ............................................................................................. 8
1.17 Introduction of Centos7 on Dialog NPCI products (hub modules, Central NMS) .............. 8
1.18 Allow to override beam cost via attachment profile.............................................................. 8
1.19 Mobility Manager deployment on NMS module ..................................................................... 9
1.20 Removal of Shared Subnet + Dynamic Attachment terminals from NMS ........................... 9
1.21 Remove shared forward feature from Dialog ......................................................................... 9
2 Upgrade Path and Backward Compatibility ...................................................................................... 9
2.1 Upgrade ......................................................................................................................................... 9
2.2 Compatibility ................................................................................................................................. 9
2.3 Software Releases in Version ................................................................................................... 10
2.4 Hardware Releases in Version .................................................................................................. 10
3 Release Changes and bug fixes ....................................................................................................... 11
3.1 Release 2.4.1.0 - Fixed issues ................................................................................................... 11
3.2 Release 2.4.1 - API Changes ...................................................................................................... 16
3.2.1 Modem resource.................................................................................................................... 16
3.2.2 MrcReturnCapacityGroup resource....................................................................................... 16
3.2.3 MrcFrequencyRange resource .............................................................................................. 17

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 2 of 34 Version 1.1
3.2.4 ReturnPool resource ............................................................................................................. 17
3.2.5 ForwardLink resource ............................................................................................................ 17
3.2.6 DeviceRole resource ............................................................................................................. 17
3.2.7 HrcMxdmaReturnCapacityGroup resource ........................................................................... 17
3.2.8 SatelliteNetwork resource ..................................................................................................... 17
3.2.9 ServiceProfile resource ......................................................................................................... 17
3.2.10 StaticAttachement resource............................................................................................... 17
3.2.11 GXT file resource ............................................................................................................... 17
3.2.12 Hubmodule resource ......................................................................................................... 17
3.2.13 ForwardCarrier resource .................................................................................................... 18
3.2.14 Batch API improvements: .................................................................................................. 18
3.3 Release 2.4.1.1 - Fixed issues ................................................................................................... 18
3.4 Release 2.4.1.2 - Fixed issues ................................................................................................... 23
3.5 Release 2.4.1.3 - Fixed issues ................................................................................................... 25
3.6 Release 2.4.1.4 - Fixed issues ................................................................................................... 27
3.7 Release 2.4.1.5 - Fixed issues ................................................................................................... 29
3.8 Release 2.4.1.6 - Fixed issues ................................................................................................... 29
3.9 Release 2.4.1.7 - Fixed issues ................................................................................................... 30
3.10 Release 2.4.1.8 - Fixed issues................................................................................................ 30
4 Known Issues ..................................................................................................................................... 31

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 3 of 34 Version 1.1
0 Introduction
This document gives an overview of the exact software versions in the release and the changes and
known open issues for the Dialog R2.4.1.

The changes are referenced to the official R2.4.1 and the R2.2.3 and are classified according to:

• New feature

• Enhancement

• Bug Fix

• Other (e.g. workaround implementation to reduce severity)

1 Release Main Features


This section summarizes changes and new main roadmap features available in Dialog R2.4.1.

1.1 Flow Fairness


This feature will improve the inner mechanics of the IP traffic enhancement software and IP shaping
software, allowing them to deal better with changing browsing behavior (for example to better deal with
the increased use of QUIC protocol) and data flows.

The introduction of Flow Fairness may require customers upgrading from Dialog R2.2.3 or lower to review
and adapt the configuration to ensure that time-sensitive applications are allocated with the right priority,
as explained in this section below.
• TelliNet-TelliShape feedback is introduced. As a consequence, TelliNet is now aware of TelliShape
scheduling priorities and rate allocation. Therefore, packet drops are now noticeable in TelliNet.
• It is recommended to keep Free Capacity Assignment always enabled. It should only be disabled for
testing or troubleshooting purposes.
• RT1 and RT2 classes are built with smaller QoS queues sizes, and are meant to be used
for applications sensitive to latency and jitter, such as VoIP or SCADA, but not for applications such as
broadcast contribution.
• TCP traffic should not be used as RT1 or RT2.
• Depending on the application, UDP traffic must be prioritized over TCP traffic. In previous
Dialog releases, UDP always had priority over TCP. Customers must configure QoS classification
rules accordingly.

1.2 Mobility switch - make before break (split management-control


plane for dynamic routing)
In mobility use cases, it is important to re-route traffic when beam switch occurs. Hence routing tables
need to be updated, and typically this is done via dynamic routing protocols.
In the example of beam switching and using OSPF as dynamic routing protocol, this feature applies the
"make before break" mechanism. The OSPF connection between DEM of target beam and edge router is
established before breaking down the OSPF connection between current DEM and edge router. This
improves the beam switching time.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 4 of 34 Version 1.1
1.3 Hub MQTT event interface - route advertisement events
This feature is intended for mobility scenarios. The hub module will have an MQTT broker to which an
HNO can subscribe, enabling the HNO to collect relevant statistics in this scenario (for example, related
to beam switches duration).

1.4 DMM beam overwrite on targetBeam of OpenAMIP settings


(Beam Switch)
This feature is intended for mobile terminals. OpenAMIP settings used by the terminals for a specific
beam are configured by NMS. This feature allows to overwrite the configured NMS settings via DMM
control plane API (REST calls) in the mobility manager.
Please note that all OpenAMIP settings must be set to acceptable, realistic values via the Dialog NMS
GUI to allow the "beam overwrite via DMM REST API call" feature to work.

1.5 Provide costumer data within beam switch command (return


multicast config).
This feature allows Dialog customers to add customer data (in a binary format) into a REST API call
(TargetBeam) coming from the DMM. The TargetBeam REST API call will be extented with
"customerdata" (and the customerdata can be any kind of info). The content of this extra binary customer
data is customer's responsibility (in other words the DMM doesn't check the format or content of the
customer data).
Maximum customer data size is 251 bytes.

1.6 Mobility Without Beam information


This feature only applies for the aero modem card. This feature provides the ability to operate on beams
not in modem config.

1.7 Unidirectional command to unmute the modem


This feature allows to unmute the transmission of the aero modem card from the ground without requiring
a reboot.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 5 of 34 Version 1.1
1.8 NMS& NMS apps geo-redundancy - non-real-time config sync -
automated switch
From release 2.4.1.3

This feature is about geographical redundancy implementation on top of the improved (manual)
procedure that was introduced in R2.2.3.
As a result, an automated redundancy swap of the NMS (Network Management System) can be done
when an operator instructs it to.

1.9 NMS+Hub geo-redundancy for XIF


From release 2.4.1.3

This feature will enable a geo-redundancy swap whereby embedded NMS and XIF hub module
functionality swap as a whole to a standby system.
The Geo-Redundancy Controller (GRC) component external to Dialog keeps two identical Dialog
installations in sync and controls which one should be active, where the other one serves as a backup.

1.10 AES256 FWD signaling


This feature enables the encryption of the full forward link. In previous Dialog releases, the overall forward
broadcast signalling was not encrypted. The intention of this feature is to encrypt all the forward signalling
using static keys. This allows to encrypt the full forward link (using "blue" and "green" keys) or have the
possibility to encrypt only the signalling with a static ("green") key.
Supported modulator: MCM7500
Supported modem types: MDM5010

1.11 Mx-DMA Multi-Resolution Coding (MRC) return technology


support

Mx-DMA MRC is a cross-dimensional multiple access return technology which combines the scalability of
MF-TDMA with the ease-of-use and efficiency of Mx-DMA HRC. Where HRC has a carrier per terminal
with transmission parameters varying in real time, MRC introduces variable transmission lengths and

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 6 of 34 Version 1.1
scalable demodulator technology, while keeping the values of HRC. It will redistribute spectral capacity 25
times per second, and will support thousands of terminals in a single hub side demodulator.

Mx-DMA MRC is supported on the MCD7500. From terminal side it is supported on MDM2510,
MDM3310, MDM5010

1.12 HRC : allow to configure the free capacity


If there would still be capacity left after handling all capacity requests from demanding terminals, then via
the free capacity node the remaining bandwidth would be distributed among the terminals until the
configured PIR of a terminal was reached. In previous Dialog releases, a hard-coded value for the free
capacity node was applied. As of this release, this feature allows to configure a value for the free capacity
assignment.
This will be configurable as a parameter within an HRC Mx-DMA Return Capacity Group as a checkbox. If
checkbox is enabled, then you can enter a value between 0 and 250 Mbps (where 0 = free capacity
mechanism is disabled).

1.13 Support modem type SMB3315 and MDM3315


This feature prepares the Dialog NMS environment for the upcoming release of the SMB3315 and
MDM3315. These modem types are still on roadmap.

1.14 Improved C/D indication on modems with FPGA-based


demodulator (MDM5010 + AMC5001)
Modems with FPGA demods can provide metrics that allow advanced link troubleshooting (C/D, C/ND,
phase noise). An added benefit is that with a C/D measurement on the MDM5010, predistortion
transponder calibration can be done with an MDM5010 terminal in the beam footprint, rather than a
standalone modulator, making this much more operationally feasible. On modem GUI:

• The phase noise margin measurement will be displayed in the terminal status page.

• Phase noise margin and link margin will be visible in demodulator submenu (as expert) of the
modem GUI, underneath the Es/No value.

• In the demodulator submenu, C/D and C/ND measurements will be visible as extra columns in
the demodulator ModCods

These parameters will also appear in advanced terminal monitoring in Dialog NMS and will be available
from the modem REST API and the hub module TSDB.

1.15 Modem metrics in hub module TSDB


Modem statistics/status info is introduced in the hub module TSDB.

• System Stats (ID, uptime, name etc)

• Status Stats (temperature, state, name, CPU usage)

• Events Stats (various counters)

• Traffic Stats (statistics on rates and packet drops)

• TCP Stats (statistics on TCP sessions)

• Demod Stats (locks, EsNo, received signal, RX freq, SR, frame counters, modcod statistics)

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 7 of 34 Version 1.1
• BGP Neighbor Stats

1.16 NMS GUI usability enhancement


The configuration GUI on the NMS is enhanced with new technologies like Agile and CoreUI. It has the
same functionality as the existing GUI, however, brings important improvements:

• Future-ready technology, multi-screen ready

• Unified UI across different interfaces (Dialog, Standalone modems, Satnet Calculator,


HRC/MRC/CPM-controller UI’s)

• Better responsiveness

• Enhanced user experience options:

o Table filtering, sorting, paging

o CRUD (Create/Read/Update/Delete) entity actions, navigating from overview tables to


details forms, "are you sure" messages when deleting etc ...

o Error handling: error messages, http interceptors, ...

o Form validation: mandatory versus optional fields, field validation error messages, multi-
select boxes

o Online help tooltips

o Security: Login forms, Logged in User details

o Server Data Refresh (manual vs automatic) options

1.17 Introduction of Centos7 on Dialog NPCI products (hub modules,


Central NMS)
On cloud platforms the underlying Linux distribution is stepped from CentOS6 to CentOS7. Improvements
are mainly related to security (resolved vulnerabilities).

1.18 Allow to override beam cost via attachment profile


The beam cost was previously set per beam (mobility tab). All terminals which would like to use this beam
had the same beam cost. To allow an operator to give a terminal another beam cost (depending on the
ST Engineering iDirect Proprietary
Confidentiality: Company Confidential Page 8 of 34 Version 1.1
terminal type or another service criteria), it is now possible to set the beam cost via the advanced settings
of an attachment profile . Consequently during the AIBS process of a terminal, the beam cost set via
attachment profile will override the beam cost that was defined via the general beam settings.

The beam cost column in the attachment profile overview indicates if the beam cost is set via beam (bold
text) or via attachment profile (normal text).

1.19 Mobility Manager deployment on NMS module


It will be possible to deploy the Mobility Manager as a managed VNF (Virtual Newtork Functionality) on
Newtec private cloud infrastructure and manage its deployment like other VNF’s using the VNFM (Virtual
Network Functionality Manager).

1.20 Removal of Shared Subnet + Dynamic Attachment terminals from


NMS
Main change introduced with this feature is that provisioning a terminal with shared network config and
multi beam attachment profile is no longer allowed.

1.21 Remove shared forward feature from Dialog


This functionality has being removed from Dialog. This feature provided the ability to combine the Dialog
from data and an external source into the same forward carrier, making use of an extra ISI (Input Stream
Identifier) injected into the forward carrier.

2 Upgrade Path and Backward Compatibility


2.1 Upgrade
Upgrading to this version should be done using upgrade tooling and upgrade procedure provided by ST
Engineering Europe.

2.2 Compatibility
This Dialog® software release is compatible with the following terminal software version:

• MDM2x00 R 4.4.0.x

• MDM2x10 R 4.6.1.x

• MDM3x00 R 4.4.0.x

• MDM3310 R 4.6.1.x

• MDM50x0 R 4.6.1.x

As part of the upgrade procedure this Dialog® release is compatible with the terminal software version:
ST Engineering iDirect Proprietary
Confidentiality: Company Confidential Page 9 of 34 Version 1.1
• MDM2xx0 R 4.3.3.x and 4.4.0.x and R 4.6.0.z

• MDM3xx0 R 4.3.3.x and 4.4.0.x

• MDM50x0 R 4.3.3.x and 4.4.0.x

• Any terminal with a version below the ones mentioned should be upgraded before it becomes
operational.

2.3 Software Releases in Version


Following table reflects changes with regard to R2.2.3
Depending on the bug fix versions received, different versions might be applicable.

Component Previous Version Actual Version

M6100 Modulator 1.6D.2.90321 1.6D.2.90321

MCM7500 Modulator 2.0.0.19 2.1.2.4

TFR0200 1.0.2.90344 1.0.2.90344

MCD6000 S2 Demodulator 2.1.10.82420 2.1.10.82420

MCD6000 HRC Demodulator 3.0.2.2 3.0.7.1

MCD7000 HRC Demodulator 3.0.2.1 3.5.5.1

MCD7000 4CPM Demodulator 1.2.0.9 1.2.0.9

MCD7000 S2 Demodulator 3.2.1.76664 3.2.1.76664

MCD7500 HRC Demodulator 3.1.1.4 3.5.5.1

MCD7500 4CPM Demodulator 2.0.0.6 2.0.0.6

MCD7500 MRC Demodulator / 1.2.0.5

NTC2291 CPM Burst Demodulator 2.4.1 2.4.1

USS202 2.1.8 or 3.3.5.6 2.1.8 or 3.3.5.6

Dialog CLOUD VNFM 1.0.2.1 1.1.0.0

Dialog External Mobility Manager 1.1.8 1.4.0

2.4 Hardware Releases in Version


This combination is preferred

This combination should not be used

Component Dialog 1-IF Dialog 4-IF Dialog X-IF Central Dialog Cloud X-IF
hub hub hub NMS hub

HP Server Gen8

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 10 of 34 Version 1.1
Component Dialog 1-IF Dialog 4-IF Dialog X-IF Central Dialog Cloud X-IF
hub hub hub NMS hub

HP Server Gen9

HP Server Gen
10

Dell NPCI

HP NPCI

3 Release Changes and bug fixes


Summary of the changes compared with the previous SW version, next to the new features as described
in Chapter 3 Software Versions

The severity assigned to the issue is defined as follows:

• Critical: Worst case scenario: Service unavailable or high safety/security risk that requires
continuously resources in order to restore/resolve (24/24 7/7). Cannot be directly resolved by
(known) workarounds, manual intervention or redundancy trigger.

• Major: While the system is not completely down, it affects severely primary functionalities
(the traffic, billing and maintenance capabilities).

• Normal: Component down/degraded resulting in service difficult to use. Not critical but
restricted function or operational impact.

• Minor: Anything else.

3.1 Release 2.4.1.0 - Fixed issues


Key Customer Summary Severity

DLGH5GUI- A search field on the attachment profile inside the 'Attachment Profile' overview is Normal
2369 needed.

DLGH5GUI- On the terminal provisioning tabs, the table layout is not consistent. Minor
2312

DLGH5GUI- In a Classification Profile rule, the end value of a range should only be required Minor
2911 when the start value is set. Now, when emptying the start value, the end value
remains required.

DLGH5GUI- On the GUI, the following warning should be displayed in case only classification Minor
2903 rules are selected with Decapsulator bits: 'For Layer 2 traffic one needs a
classification filter for Layer 2 control packets to pass (ARP/NDP/...)'. ARP stands
for Address Resolution Protocol (TCP/IP). NDP stands for Nortel Discovery
Protocol.

DLGH5GUI- The modem Satellite Interface GUI does not allow to have a 5th decimal number Critical
3134 of the Symbol Rate different from 0.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 11 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI- When provisioning an S2 terminal, the frequency picker is not working. An empty Normal
3114 box is displayed.

DLGH5GUI- When saving changes in the GUI and nothing really changed, a message should Normal
3020 be given.

DLGH5GUI- Some advanced batch API options should be added: Minor


2963 - transactional options 'true' or 'false' to do an 'all or nothing batch update'
- limit 'x' to limit execution to a certain amount. Only for query based batch API,
and not with 'ID based' batch like UI is using mostly
- fail-fast options 'true' or 'false' to stop execution after the first error

DLGH5GUI- It is not possible to perform a batch action on the MRC settings. Normal
3080

DLGH5GUI- When the value '0' is filled in for a Critical Data class in a service profile, a Minor
2917 warning should be displayed.

DLGH5GUI- It is not always clear what is selected in a slider. Minor


2915

DLGH5GUI- On the tab 'Modem', the modem can be linked to a 'Remote configuration Profile'. Normal
3096 A new filter 'Any Remote Configuration Profile' which will allow the user to filter on
the different remote configuration profiles, should be added.

DMM-340 The Dialog Mobility Manager sometimes stops trying to connect to the HRC Major
Controller.

DLGH5GUI- Make some GUI tables wider to make them better readable. Normal
2733

DLGTICS- The Terminal Installation Certification System cannot find the satellite network of Major
285 the modem.

DLGTICS- The return measurements are not configured but yet an error concerning return Minor
279 measurements is thrown in the Alarm overview.

DLGTICS- Terminal Installation Certification should support forward verification of HRC Normal
267 terminals.

DLGTICS- The Terminal Installation Certification System GUI logs out automatically. Minor
239 Approximately every 5 minutes the Terminal Installation Certification System
goes back to the login screen of the GUI.

NMSCONF- While provisioning terminals, a check that prevents using a hub uplink / proxy Minor
4961 Domain Name System subnet on the terminal dedicated network is performed.
However, it is perfectly possible to provision the modem first and change the
proxy Domain Name System address equal to the modem IP or Proxy DNS IP
that is part of the modem Dedicated Subnet. This makes the Terminal
Configuration System modem configurations invalid.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 12 of 34 Version 1.1
Key Customer Summary Severity

NMSCONF- Enforce a limit on the 'Maximum Routes Learned' via the Border Gateway Normal
4955 Protocol on the Configuration Management Server. The number should be limited
to 6000.

NMSCONF- MRC Return Signal classes should use Volume Based Dynamic Capacity Normal
4948 requests instead of Rate Based Dynamic Capacity requests.

NMSCONF- Not all terminals are written in the modem map file, even though they are all Major
4934 present in the persister.

NMSCONF- The Generic Stream Encapsulation overhead calculation is incorrect due to Normal
4916 rounding off at the wrong moment.

NMSCONF- The duplicate use of the baseband ID results in unclear errors. Minor
4866

NMSCONF- There are no NMS checks to prevent having the same Packet Identifier for HRC Major
4864 and for MRC Waveform/Allocation in the same Satellite Network.

NMSCONF- The HRC Ulogon channel ID should be in the GUI and configured in the HRC Normal
4832 Controller configuration. Currently this is not the case.

NMSCONF- The NMS Service Profile API Call does not return the type to the mobility Normal
4833 manager.

NMSCONF- Two Return Capacity Groups are present in one HPS. Normal
4831 It is not possible to change the Ulogon ID to another value for both Return
Capacity Groups. An error message is displayed.

NMSCONF- The Interface Selection Alarm does not appear on the device, but is always Major
4817 reported in the NMS log of the device.

PLATO-5687 The Virtual Network Function Manager should restore customerconfig to the Hub Normal
Module Gateway Virtual IP address.

PLATO-5657 Controller Shaper Encapsulator CSV files access via http is missing. Minor

PLATO-5653 When using the Virtual Network Function Manager tool to deploy an extra Central Major
NMS for Geo redundancy, the deployment fails. When using CNMS with four
computes, only one is marked mandatory in the web interface and the
deployment fails

PLATO-5651 On the non-cloud 1IF hub module, the Central Processing Unit pinning is Normal
incorrect.

PLATO-5645 The default https certificate is about to expire. Minor

PLATO-5616 Improved log message for LWU pre-check result. Minor

PLATO-5548 The nms-conf.log is spammed with the logging of invalid credentials. This makes Minor
it difficult to go trough the log for other irregularities.

PLATO-5500 The MRC Return Controller is not correct linked to the Dialog Mobility Manager in Major
the configuration file.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 13 of 34 Version 1.1
Key Customer Summary Severity

PLATO-5498 The MRC Controller is not restarted after a Light-Weight Update. Normal

PLATO-5499 The mobility manager has sometime trouble to connect to the MRC Controller. Major

PLATO-5301 After automatic deployment, the infrastructure element sometimes monitors the Minor
wrong switch ports.

PLATO-5450 The redundancy-controller.properties should not mention workarounds. Minor

NMSCONF- Some default gateways should be blocked as they give a conflict with internal Minor
4248 addresses.

NMSCONF- The shared forward feature and the corresponding stream types are no longer Normal
4243 supported. The obsolete parameters should be removed.

NMSCONF- For MRC, duplicate IDs for pool nodes are present. The free capacity node and Normal
4410 the return signaling node are using the same IDs.

NMSCONF- When creating a new hub module without gateway or cloud infrastructure ID, the Minor
4731 displayed error message is not clear.

NMSCONF- When enabling 'MCD Overbooking Allowed' on an HRC frequency slot with too Minor
4737 many modems provisioned, there is no warning or error message.

NMSCONF- New device types can be provisioned in old versioned hub modules which do not Normal
4720 recognize these device types.

NMSCONF- NMS CONF does not validate all modems for certain properties. Major
4688

NMSCONF- One of the MCM7500 devices is not configured by the Redundancy Controller. Normal
4685

NMSCONF- When using a very low SNR MODCOD and using the HRC 68Mbaud feature, the Minor
4667 error message is unclear.

S3PDMA- The views 'Forward Carrier Provisioning' and 'Transponder Provisioning' are not Normal
4286 recreated upon restarting the element 'Dialog Provisioning'.

S3PDMA- The 'Output frequency' parameter has an incorrect description for the MCM7500 Minor
3990 modulator.

S3PDMA- Actual Tracked N0 or Noise Density trending on the main dashboard of the HPS Major
4692 HRC element is missing.

S3PDMA- The advanced terminal view shows a Border Gateway Protocol Virtual Routing Normal
4520 and Forwarding (BGP Vrf) name '0' which is not correct.

S3PDMA- On the 'Forward Link' view, the 'Delay' parameter is missing. Normal
4463

S3PDMA- In the Grafana overview, some dashboard links are not working. Normal
4444

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 14 of 34 Version 1.1
Key Customer Summary Severity

S3PDMA- The MRC overview gets corrupted when zooming out using the minus button. Normal
4903

S3PDMA- Return Pools & Capacity group elements and HRC elements give different values Major
4894 for allocated and requested rate.

S3PDMA- The 'RTN Es/No' graph is missing on the element for an MRC advanced terminal Major
4876 under 'Terminal'.

S3PDMA- CPM functions show 'Not initialized' on the Dialog NMS. Major
4869

S3PDMA- Run traffic with dedicated capacity for Virtual Network Operator 1 with dedicated Normal
4867 Best Effort and for Virtual Network Operator 2 with dedicated Critical Data. When
checking the 'Return Pools' tab, the following parameters are not correct: CIR,
PIR, CIR Congestion (in Class Based Parameters for the dedicated Critical Data
pool the value is 'Yes' and in the Return Pools the value is 'No'), Requested Rate
and Allocated Rate.

S3PDMA- The parameters on the 'MRC Class Pools', 'MRC Return Pools' and 'MRC Return Minor
4846 Capacity Group Statistics' in the 'MRC Return Capacity Groups' view are not
correctly reported.

S3PDMA- The return MODCOD is not displayed in the 'MRC Terminal Details' dashboard. Normal
4847

S3PDMA- In the MRC Return Capacity Groups, under the MRC Return Pools, some Minor
4845 changes are needed.

S3PDMA- For the MRC Return Capacity Groups, the unit of measurement should be Minor
4843 changed from bps to kbps.

S3PDMA- Change label of the parameter 'Switch Account' to 'Switch Count'. Minor
4839

S3PDMA- Under the element 'HPS Functions' on the view 'MRC Controller', the 'MRC Normal
4834 Controller Active parameter' is set to 'No' instead of 'Yes'.

S3PDMA- MRC Return Capacity Group Statistics have issues. Unities are not correct, some Major
4835 scales are wrong and names are incorrect.

S3PDMA- Remove the parameter 'RTSIGN' from 'Bidirectional Unicast Circuit'. Normal
4830

S3PDMA- MRC 'Rx Power 'and 'Rx Power Density' are swapped. Normal
4824

S3PDMA- After upgrade we noticed at RTN Pools&Capacity Groups for Request rate at Major
4943 CPM Return Pools and CPM return Class Pools are not getting updated. They
are not ok for aggregated values or for each one of the classes.

S3PDMA- The HNO/User/VNO provisioning access redirects the user to the terminal Minor
4941 provisioning page in Dialog NMS.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 15 of 34 Version 1.1
Key Customer Summary Severity

NMSCONF- When adding a satellite network, the polling sometimes starts too fast. Major
4910

NMSCONF- The redundancy controller does not respond to requests while a process is in a Minor
4865 running state. So the system does not detect the issue and does not report any
problems.

NMSCONF- Mobile modem updates done by automated scripts are registered in the NMS and Normal
4329 seen in the mobility manager, but the mobility manager does not update the
config files. The timestamps are outdated.

NMSCONF- Validation of the auto-attachment prototype without MAC address should be Minor
3936 possible.

NMSCONF- It should not be possible to put the modulation on the device while transmit is Normal
3748 disabled on the forward carrier.

NMSCONF- The help on the view 'Transponder' is incomplete. Minor


3693

S3PDMA- When the deletion of a modem failed, recreating this modem is not possible. Major
4890

S3PDMA- In the Grafana Dashboard in the tab 'terminal details', the terminal name should Major
4568 be displayed in stead of the ID.

S3PDMA- Dialog NMS is not updating when the CPU is high. Elements are missing. Major
4797

82 issues

3.2 Release 2.4.1 - API Changes


Following list gives an overview on the NMS API changes between release 2.2.3 and 2.4.1

3.2.1 Modem resource


• The dynamic attachment parameter has a new return technology: MRC

• The MRC attachment parameter has been added

• satelliteNetworkConfigurations and satnetsMissingNetworkConfiguration are deprecated

• tellinetAirVirtualAddress and managementAddress are added

• New call

POST modem/prototype/auto-
attachment/{autoAttachmentPrototypeId}/validate?satelliteNetworkId={satnetId}&macAdd
ress={macAddress}

3.2.2 MrcReturnCapacityGroup resource


• This new resource has been added. The associated calls are similar to other
ReturnCapacityGroup resources

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 16 of 34 Version 1.1
3.2.3 MrcFrequencyRange resource
• New calls were added to assign demodRole to a frequencyRange:

POST rest/mrc-frequency-range/{id}/link/demod-role/{demodRoleId}
POST rest/mrc-frequency-range/{domain}/{name}/link/demod-
role/{demodRoleDomain}/{demodRoleName}

• New calls were added to revoke demodRole from a frequencyRange:

DELETE rest/mrc-frequency-range/{id}/link/demod-role/{demodRoleId}
DELETE rest/mrc-frequency-range/{domain}/{name}/link/demod-
role/{demodRoleDomain}/{demodRoleName}

3.2.4 ReturnPool resource


• The property mrcReturnCapacityGroupId has been added

3.2.5 ForwardLink resource


• The properties mrcAllocationPid and mrcWaveFormPid have been added

• New properties were added, they have as goal to enable encryption on the
forwardLink : aes256Enabled, signallingKey, dataKey

3.2.6 DeviceRole resource


• The property consumerId has been replaces by consumerIds

3.2.7 HrcMxdmaReturnCapacityGroup resource


• The properties ulogonChannelId, freeCapacityEnabled and freeCapacityPir have been added

3.2.8 SatelliteNetwork resource


• The property loopbackEnabled had been added

• New call :

GET satellite-network/{id}/modem-counts

GET satellite-network/modem-counts

3.2.9 ServiceProfile resource


• The properties mrcIdleLogOffTimeout and mrcKeepAliveTimeout have been added

3.2.10 StaticAttachement resource


• The property addBeamToTerminalSatelliteConfiguration has been added

3.2.11 GXT file resource


• New ready only field: beamIds

3.2.12 Hubmodule resource


• New calls to return a collection of free HubProcessingSegments:

GET hub-module/hub-processing-segment/free

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 17 of 34 Version 1.1
GET hub-module/hub-processing-segment/free/per-hub-module

3.2.13 ForwardCarrier resource


• New call to return a collection of non-saturated ForwardCarriers

GET forward-carrier/available

Aside from these changes a general cleanup of old and deprecated fields happened.

3.2.14 Batch API improvements:


• Transactional support

Users are now able to use a "transactional" flag on the Batch API. This allows the whole batch action to
be seen as a single "unit of work".
This allows the user to revert all changes in case an error happens during the batch task.

Example use-case: delete all service profiles. Fail if one is still in use : curl -H "Accept:
application/vnd.newtec.nbi-v1+json" -X DELETE http://{CMS}/rest/service-profile/batch?transactional=true

The transactional flag is supported on all Batch API actions.

• New Batch actions

We've added two new dedicated Batch API actions: lock and unlock.
This behavior could be achieved through a normal update as well but these dedicated API calls have a far
higher throughput.

Examples:

• lock all modems : curl -H "Accept: application/vnd.newtec.nbi-v1+json" -X DELETE


http://{CMS}/rest/modem/batch/lock

• unlock all modems: curl -H "Accept: application/vnd.newtec.nbi-v1+json" -X POST


http://{CMS}/rest/modem/batch/unlock

• lock all modems asynchronously: curl -H "Accept: application/vnd.newtec.nbi-v1+json" -X


DELETE http://{CMS}/rest/modem/batch/async/lock

• unlock all modems asynchronously: curl -H "Accept: application/vnd.newtec.nbi-v1+json" -X


POST http://{CMS}/rest/modem/batch/async/lock

3.3 Release 2.4.1.1 - Fixed issues


Key Customer Summary Severity

NGMXDMACON- The configuration of the MRC controller doesn't take the GSE overhead into Normal
387 account.

NGMXDMACON- After a terminal is locked and unlocked, there is no new MRC login message Normal
381 sent.

NGMXDMACON- When a terminal logs in, but the first MRC burst is undecodable, it is directly Major
302 logged off again. This happens because the MRC Controller does not take
into account the configured error log off value after sending the logon signal.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 18 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI-3209 Wrong maximum value check on the 'CIR' or Committed Information Rate in Minor
the 'Forward Multicast Circuits' screen.

DLGH5GUI-3208 When adding a 'Forward Multicast Circuit' and clicking on the MODCOD Minor
dropdown list, the dropdown list is hidden behind the screen. Also, the label
'ModCod' should be 'MODCOD'.

DLGH5GUI-3199 In the view 'Hub Termination Point' in case of a layer 3 configuration, the Minor
field 'Untagged' should be removed. When switching from layer 3 to layer 2,
the field 'MTU' disappears. The field should remain.

DLGH5GUI-3206 The Border Gateway Protocol or 'BGP Filters' do not work correctly. Minor
The check on the 'IPv6' input field is not correct.
There is no maximum value check on the field 'Allowed AS Number'. The
value should be between '0' and '65535'.

DLGH5GUI-3202 The 'Uplink DNS proxy Address' placeholder in the 'IPv6 Uplink' view is not Minor
correct.

DLGH5GUI-3197 The Return Link Calibration cannot be changed when there are provisioned Normal
terminals using AUPC in the satellite network that is being modified.

DLGH5GUI-3195 On the view to create a return link calibration, the help question mark is on Minor
the wrong location and has an incorrect size.

DLGH5GUI-3185 Some value checks on the beam are missing. Minor

DLGDMADEVM- When an attachment profile ID is changed, a 'Modem Update Request' Major


141 should be sent.

DLGH5GUI-3188 The procedure for uploading a GXT file in 'Beams' is confusing. The help is Normal
not useful.

DLGH5GUI-3192 On the 'Forward Carriers' page, the units 'GHz' and 'MHz' are mixed. Only Minor
'GHz' should be used. 'MBaud' should be changed to 'Mbaud'.

DLGH5GUI-3190 Using the GUI, it is impossible to add an exclusion zone to a beam. Normal

DLGH5GUI-3184 Some information is missing on the 'Automatic Pointing Settings frequency' Minor
error message.

DLGH5GUI-3177 In the 'Service Profile Settings' screen, 'kBaud' should be replaced by Minor
'kbaud'.

DLGH5GUI-3179 In 'Show Advanced Settings - QoS Class Settings Return', the 'Selected Minor
Return QoS Classes' drop down box opens under the screen. The drop
down box should open upwards.

DLGH5GUI-3198 The help on the 'Service Profile Settings' has issues. Also, the help topics Normal
for MRC are missing.

DLGH5GUI-3176 On the 'Service Profile Settings' screen, no check is done when the numbers Minor
are decimals. The rounding should happen every time the value is changed.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 19 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI-3174 The value of the 'Weight' on the 'Service Profile Settings' screen should be a Minor
whole positive value. It cannot be a decimal.

DLGH5GUI-3175 In the 'Return QoS Class Settings' group case, the field 'Packet Size (bytes)' Minor
should be renamed to 'Average Packet Size (bytes)'.

DLGH5GUI-3173 On class based and transport based service profiles, there is no check on Minor
the maximum value of the 'PIR' or Peak Information Rate. Also, when
entering a lot of values, an unclear error message is shown.

DLGH5GUI-3171 On the screen 'Layer 2 Rule details', the label 'VLAN Tag' should be 'VLAN Minor
ID'.

DLGH5GUI-3172 When entering a wrong value in the field 'Weight' in the section 'Circuit Minor
Settings' in class based and transport based service profiles, an error
message is shown twice.

DLGH5GUI-3187 The attribute 'DSCP' is missing in the help of the 'Layer2ClassificationRule'. Normal
Also, the help that is displayed is not always the same for every
'Layer2ClassificationRule'.

DLGH5GUI-3169 The HRC Mx-DMA Request Margin should only be shown in case of the Minor
allocation type 'Dynamic Ingress Rate'.

DLGH5GUI-3168 A description field should be added to each rule of the classification profile. Minor

DLGH5GUI-3166 In the Terminal Installation Certification System, disabling the certification Normal
does not always work. The change is not always saved.

DLGH5GUI-3163 A field check should be executed on the 'GXT File Random Back Off' value Minor
in the 'Remote Configuration Profile'.

DLGH5GUI-3159 The 'Discard' and 'Apply' button bar is wrongly positioned on 'Terminal Minor
Provisioning'.

DLGH5GUI-3162 A value check should be executed on the field 'Prefix' in the 'Border Minor
Gateway Protocol' configuration.

DLGH5GUI-3161 A value check should be executed on the 'Max skew' value in the Normal
'Attachment Profile'.

DLGH5GUI-3158 When changing the parameter 'Return Capacity Group', the message Normal
'Changes applied.Success' appears. But when clicking outside this screen,
the message 'Unexpected Error.0' is displayed.

DLGH5GUI-3142 When provisioning a terminal, on the tab 'Modem' in the section 'Installation', Normal
there is no help available.

DLGH5GUI-3140 In Dialog NMS, the MRC Idle logoff value in a service profile has a wrong Normal
unit.

DLGH5GUI-3133 When clicking the 'Return QoS Plan' shortcut in an MRC Return Capacity Normal
Group, an error is thrown.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 20 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI-3135 When commissioning an 'MRCMCD' or MRC Multicarrier Demodulator in the Minor


IMS, the output card is not locked in the 'Interface Config' tab.

DLGH5GUI-3119 When provisioning a terminal with a new attachment profile and setting up Normal
the Layer 3 network configuration for a dedicated subnet, the 'Service Label'
is not visible.

DLGH5GUI-3117 It should be possible to filter terminals on the MRC 'Return Resource'. Minor

DLGH5GUI-3110 Loading a return Quality of Service Plan takes too long. Normal

DLGH5GUI-3100 The validation of the sum of the CIR/PIR for the class nodes in the child Normal
pools is wrong. The total is defined in Mbaud while the class nodes CIR/PIR
are defined in Mbps. Therefore they should not be compared to each other.

DMM-370 After selecting a new MRC beam from another MRC beam using Automated Normal
Initial Beam Selection, the terminal remains in the 'Locked' state in the MRC
Controller.

NMSCONF-5017 The Redundancy Controller - MCD communication is not correct because Normal
the MCD does not have the correct config.

NMSCONF-5005 The validation of Border Gateway Protocol or BGP Filters was not handled Minor
correctly. Therefore invalid configurations can occur with invalid IP
addresses.

NMSCONF-5001 GTP port can be configured with invalid values. Minor

NMSCONF-4982 When creating a beam and if the value in 'Automatic Initial Beam Selection Minor
cost' is too high, or if the GXT beam name is too long, an incorrect error
message is displayed.

NMSCONF-4980 When a forward link is moved from a sliced carrier to a non-sliced carrier, Normal
the 'Slice ID' is not set to '0', resulting in an error. The 'Slice ID' is kept as it
was before the move (unexpected behavior) but the GUI does not show it
anymore (expected behavior). This results in an error.
When moving to a non-annex M, the 'Slice ID' should either be automatically
set to '0' or just be ignored.

NMSCONF-4967 The table 'RouteAdvertisementSettings' should be cleaned up. Normal

NMSCONF-4943 Auto Attachment Prototype terminal provisioning using the REST API call Normal
does not work correctly.

NMSCONF-4941 The error message 'The binary does not contain a hardware id/mask' should Minor
be replaced by 'The binary file is corrupt. Please try downloading it again.'
for the multicast.

NMSCONF-4933 It should be possible to change the MRC Error logoff period (in ms) in the Normal
service profile.

NMSCONF-4915 The MRC Idle logoff maximum and minimum values are not defined in the Normal
API while they are present in the GUI.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 21 of 34 Version 1.1
Key Customer Summary Severity

NMSCONF-4895 It should not be possible to use the same VLAN for unicast and for multicast Normal
networks.

NMSCONF-4881 When the Matrix CPU goes down briefly the first couple of commands send Major
by the Redundancy Controller are not processed.

PLATO-5738 The amount of loggings generated by the HRC controller causes latency on Major
the Virtual Machine and HRC timeouts on a live system.

PLATO-5735 Management connectivity to the MCM7500 fails for a 10Gb-capable Normal


MCM7500 modulator connected via an HP5710 ASW switch.

PLATO-5730 Terminal Burst Time Plan processing is too late. Major

NGMXDMACON- The MRC Controller GUI can become unreachable after a long uptime
448

NGMXDMACON- It is possible that a modem appears twice in the controller view in the Dialog Normal
413 NMS.

NGMXDMACON- When the terminal is logged off, the last bursts in transit should not be Normal
401 counted any more.

NMSCONF-4149 The 'Virtual Network' label in the tab 'Ethernet Interface Configuration' does Normal
not show the name, but displays '0' instead.

S3PDMA-4927 Wrong title for MRC Shaping table in Advanced Terminal Element. Minor

S3PDMA-4915 The total rate values on the HRC Grafana dashboard are not correct. Normal

S3PDMA-4916 When the name of a Satellite is changed, not all old views are removed. Minor

S3PDMA-4909 When the 'Satnet Connection Info' table is updated due to a satellite network Major
update or a Hub Processing Segment update, the Time Series Database
Connections are not updated.
So if the IP-address is changed, the Time Series Database on the old IP-
address is still queried, resulting in no data coming in for the terminals on
that satellite network.

S3PDMA-4908 In the 'Satnet Connection Info' table of the 'Advanced Terminal Main' rows Minor
are present with key = 0.

S3PDMA-4906 The 'Satnet Connection Info' table of the Advanced Terminal Main element Major
is not updated when a Hub Processing Segment Update Request comes in.

S3PDMA-4905 In the 'Satnet Connection Info' table of the 'Advanced Terminal Main' Normal
element, the enclosure 'System Id' and 'System Name' are the same for all
hub modules.

S3PDMA-4929 The alarm on the Transmit State is not correct for the passive modulators. Normal

DLGH5GUI-3165 The help button should be displayed in a darker grey. Now it is hardly Minor
visible.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 22 of 34 Version 1.1
Key Customer Summary Severity

DMM-356 When an attachment profile with a different return technology is linked to a Major
terminal, the Dialog NMS Controller state and communication break.
The terminal receives no signaling for the new return technology, because it
is still locked in the old return technology controller by the Dialog NMS. The
modem log goes offline and receives no signaling from the old return
technology to log on in the new one.

DLGDMADEVM- When removing a beam from an attachment profile in the NMS-Conf GUI, Minor
137 no 'Attachment Update Request' arrives in the 'Dialog Provisioning Element'.

DLGH5GUI-3213 Using a 4IF hub, it is not possible to add /32 routes in the next hop routes. Major

DLGH5GUI-3196 On the 'Forward Link' view there are some help issues. Normal

DLGH5GUI-3112 When creating or editing a 'Forward Pool,' it is possible to leave the 'CIR' or Minor
Committed Information Rate and the 'PIR' or Peak Information Rate empty.

NMSCONF-4971 The maximum send data rate and maximum receive data rate in terminals Normal
should be dynamically set to a value slightly higher than the terminal Service
Level Agreement (1 to 2% higher), instead of the currently used fixed value
per modem type.

NMSCONF-4939 Terminals that are online do not pass traffic over the hub. Major

PLATO-5697 Queries polling the Time Series Database fail during Central Processing Major
Unit and memory peaks.

S3PDMA-4900 Return technology parameters are confusing when plotting multiple Minor
trendings.

S3PDMA-4904 The mobile terminal is not present under the Terminal Monitoring and the Major
Advanced Terminal Main elements. The terminal is present in the Standard
Terminal Manager.

S3PDMA-4872 The parameter 'N0 Deviation' should be introduced in the Time Series Normal
Database and the Dialog NMS element for HRC Advanced Terminals.

82 issues

3.4 Release 2.4.1.2 - Fixed issues


Key Customer Summary Severity

DLGH5GUI-3218 Editing the weight factor for a transport based service profile is not needed. Minor

DLGH5GUI-3216 When you create an ipv4 pool without a linked Satnet it will not be shown in Normal
the GUI.

DLGH5GUI-3221 Inconsistent naming in the Attachment profile 'Beam cost' instead of 'Beam Minor
Cost'

DLGH5GUI-3217 The help text in 'Network Resources - Networks - Edit BGP-SN1' states: Normal
"BGP Router-ID: The id of the router in the BGP system. This parameter
cannot be configured and is equal to the IPv4 Uplink Address of the

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 23 of 34 Version 1.1
Key Customer Summary Severity

Network."
This is correct, but in the GUI the router id can be configured.

DLGH5GUI-3203 On the 'Network Resources' screen, there is no value check on the field Minor
'GTP port'.

DLGH5GUI-3204 When assigning a modem to a shared network, an error is shown saying Normal
that no IPV4 pool is found. When checking the overview of IPV4 pools there
is no pool visible.
But when adding an IPv4 pool to the shared network, a message appears
saying that the pool already exits.

DLGDMADEVM- When a modem of the type MDM3310/MDM3315 or SMB3310/SMB3315 is Normal


133 provisioned, terminal monitoring on the Dialog NMS does not show the
provisioned modem.

HRCCON-1080 The HRC requested rate on terminal level should be supported for the Normal
Metrics API. Now, this rate is not present in HRC GUI.

NGMXDMACON- The MRC controller allocates at least 25 Kbps per terminal when there is a Major
473 capacity request and if the modem is configured as 'Transport Based'.

S3PDMA-4940 Dialog NMS terminal provisioning access redirects to the general CMS Minor
terminal view, instead of the CMS view of that terminal.

S3PDMA-4939 The redundancy of the MRC demodulator pool can get disabled without a Major
specific reason

PLATO-5768 The HRC controller sometimes gives timing alarm errors. Major

NMSCONF-5011 The invalid handling of beam removal causes an operation exception. This Minor
only happens for beams with more than one neighbor.

NGMXDMACON- Add a controller alarm or warning when the MRC debug logger is running. Major
452

NGMXDMACON- When a terminal is de-provisioned, a terminal logoff is sent anyhow, Normal


450 independent of the fact that the terminal is logged on or not. This can cause
an internal alarm.

NGMXDMACON- The sensitivity to phase noise should be decreased. Normal


427

NGMXDMACON- Improve the placement algorithm to cope better with carrier restrictions. Normal
414

S3PDMA-4933 When MF-TDMA return technology is disabled, the controller stays present. Major

S3PDMA-4931 An alarm is added in Dialog NMS that indicates the MRC Debuglogger is Major
running, as debuglogger consumes disk space.

S3PDMA-4930 The 'SatelliteNetwork Configuration' table of the Advanced Terminal Main Minor
elements contains empty objects.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 24 of 34 Version 1.1
Key Customer Summary Severity

S3PDMA-4922 In the 'OSPF and BGP Information' views, only IPv6 instances are present, Major
while also IPv4 instances are configured in the system.

S3PDMA-4921 The correct column name is "BGP neighbor ID" instead of "BGP neighbor Normal
IP"

DLGH5GUI-3214 When creating a new Forward link and when a Forward carrier different Normal
from the first one is assigned, sometimes the NMS does not assign the one
selected but the first one.

IPSW-14840 The terminal routes do not automatically refresh after a redundancy swap Normal

DLGH5GUI-3222 In the 'Forward Carriers' screen, the 'Candidate Settings' cannot be filled in. Major

PLATO-5759 The restore process of the databases failed as Galera did not work. Major

PLATO-5758 The MRC MCD redundancy controller input level template is not correct. Normal

DLGH5GUI-3224 The space for the list of the available Demod Roles for MRC is not wide Normal
enough to show the entire name.

NMSCONF-5037 In some occasions, the geo-redundancy monitor states a time out without a Major
reason.

PLATO-5769 There are no modem remote statistics appearing on the time series Major
database.

NMSCONF-5051 Swapping the active MRC demodulator role to a standby MCD results in an Critical
inconsistent configuration.

PLATO-5692 Deleting or updating a configured Configuration Management Server geo- Normal


redundancy system Internet Protocol via Basic Configuration Interface
results in a corrupted customer access network.

32 issues

3.5 Release 2.4.1.3 - Fixed issues


Key Customer Summary Severity

DLGH5GUI-3211 According to the online help text, the reordering delay should be presented Minor
in milliseconds whereas the GUI displays it in seconds.

DLGH5GUI-3193 On the 'Forward Link' page, the maximum value check on the 'Max Normal
Multicast Bandwidth' value should be corrected.

HRCCON-1047 Idle modems are using too much bandwidth. Legacy HRC modems are not Normal
sending any traffic. They should only use a 31KBd carrier but are using a
lot more.

DLGH5GUI-3183 It is not possible to create or modify a modem as a Virtual Network Owner Normal
user.

DMM-372 In case of a beam switch command during connection loss of a terminal, Normal
the sequence of the MQTT messages is wrong after restoring the

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 25 of 34 Version 1.1
Key Customer Summary Severity

connection.
Normally the Make-Before-Break should still work, but due to the sequence
of the published MQTT messages it does not. The old beam switching
behavior is still in place.

S3PDMA-4968 MRC RTSIGN and Management traffic is stored in the Time Series Minor
Database. This should not be the case.

HRCCON-1084 The HRC controller sometimes has connection problems with the Dialog Major
Mobility Manager.

NGMXDMACON- An initial maximum transmit power update is not taken into account by the Normal
489 MRC Controller.

PLATO-5767 Concerning the metrics of the MRC controller: the update interval for the Normal
GUI should be set to 10 seconds.

DMM-379 MRC to HRC beam switching does not work. Major

NMSCONF-5049 It is not possible to create a Class Based Service Profile using VNO rights. Normal

DMM-381 Request orders are not respected with the support of multiple return Major
controllers in a SatNet.

NMSCONF-5021 The online help text of the Carrier Randomization part when creating or Minor
editing an HRC Return Capacity Group should be updated.

NMSCONF-4995 The online help of the Hub Termination Point contains errors. Minor

NMSCONF-4992 When provisioning a modem, and no IPv4 pool is configured, the system Minor
displays an unattractive error message

PLATO-5698 Unable to upload modem software and GXT file. Normal

PLATO-5785 When a terminal requests more traffic than its PIR or Peak Information Critical
Rate, the reported dropped rate does not include all dropped traffic.

S3PDMA-4935 When the MRC return technology is disabled, the MRC elements remain Major
visible in the Dialog NMS.

S3PDMA-4936 The customer usually watches multicast stream using an element that Major
monitors all multicast streams via different hubs. This multicast stream
element is now missing.

S3PDMA-4932 The 'Satnet Information' table is not updated correctly when a SatNet was Normal
deleted.

DLGRTMCDEV- The Real-Time Monitoring and Control Software device manager Normal
55 subscribes with a cryptic client ID to the central broker.
The client ID should be more descriptive.

NMSCONF-5067 The BGP domain is not correctly updated when updating the domain of a Major
terminal.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 26 of 34 Version 1.1
Key Customer Summary Severity

SKYDIAG-650 The Dialog NMS agent could not access elements of unavailable agents in Normal
a cluster.

NMSCONF-5079 Updating terminals can cause clashes with IP addresses which are already Critical
assigned to other terminals, resulting in loss of traffic

S3PDMA-4965 Advanced terminals total forward parameters are sometimes not initialized Critical
in cases where there are a lot of active advanced terminals.

PLATO-5817 L2 traffic is intermittent. Drops happen. Critical

PLATO-5794 Due to an MQTT issue, the routes of the terminals are not advertised. Critical

PLATO-5784 The backup ignores certain parts of the database due to some errors. They Major
are not added to the database backup.

S3PDMA-4956 Mobile terminals do not update their KPI's. Critical

29 issues

3.6 Release 2.4.1.4 - Fixed issues


Key Customer Summary Severity

DLGH5GUI-3200 The 'Ipv6 Overview' contains errors. Some of the names of the fields are not Minor
correct. The linked help is not clear.

DLGH5GUI-2876 When no Transmit/Receive signal is associated with the satellite network, an Normal
indication should be displayed.

NMSCONF-5113 Process of fetching missing resources on hub side causes high CPU usage Critical

DLGH5GUI-3244 It should be possible to add a modem from the S2 frequency plan Normal

S3PDMA-4976 Adapt default Time Slice Parameter to 60s Major

DMM-386 Requesting a beam switch via Dialog NMS API does not send overwrites to Major
OpenAMIP

S3PFTB-125 Requesting a beam switch using the API, doesn't set the correct Major
PolarizationSkew value

S3PDMA-4969 Add used forward symbol rate monitoring per terminal. Major

DMM-384 When performing an API call towards Dialog NMS with invalid body the Normal
Dialog Mobility Manager does not response as expected

S3PDMA-4964 Satellite Network folder is left behind in the cube when moving a Satellite Normal
Network to another beam.

NMSCONF-5087 Request for custom names for QoS rules Normal

DLGH5GUI-3235 Editing HRC SCPC capacity groups in the spectrum view is not possible due Normal
to the changes not being applied

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 27 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI-3233 When you filter on terminal software group 0 you keep on seeing all terminals Minor

DLGH5GUI-3232 When creating new Return Pool via GUI, the child page sets 'Transport Normal
Based Service Pool' while showing QoS classes of 'Class Based Return
Pool'

S3PDMA-4918 Adaptations in the enclosures on the NMS GUI should induce an adaptation Major
of the 'Satnet Connection Info' tables of the 'Advanced Terminal Main
Elements'.

NMSCONF-5107 The modem configuration is sometimes not proper applied Normal

NMSCONF-5109 While performing API call towards Dialog NMS '/rest/beam/config' JSON Major
response does not contain field returnTechnology

HRCCON-1090 The MQTT status of the terminal is not mentioning the correct active beam Critical

NMSCONF-5118 Some of the configuration files are not cleaned up Normal

HRCCON-1086 HRC Controller goes unexpected into Ulogon after beam switch for non Major
spreaded logon terminal.

PLATO-5824 When some running services became unmonitored. it does not triggers a Normal
swap

S3PDMA-4951 Dialog NMS does not shows trending for the S2 ModCod parameter Normal

DLGH5GUI-3228 A user with observer rights is not able to open the terminal provisioning web Minor
interface.

DLGH5GUI-3234 When adding a Baseband Hub Module, a bug appears in the inventory GUI. Major
The system is complaining about a 'gateway' but no 'gateway' option is
available in the Baseband Hub Module.

NMSCONF-5069 GEO redundant deactivation of a gateway for the XIF NMS + Hub takes a Normal
long time to return a complete deactivation.

DLGH5GUI-3231 Upon creation of a new Class Based Service Profile, and performing the Normal
following actions:
- inserting values for the mandatory parameters
- enabling the traffic classes with values that will be used
- trying to link the service profile by going to 'VNO Linking'
the system displays an error.

DLGMETCOL-16 MRC metrics are not available from metrics collector Major

DLGRTMCDEV- RTMC DM causing continuous processing of tasks in HMMS leading to Critical


57 inconsistent configuration
28 issues

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 28 of 34 Version 1.1
3.7 Release 2.4.1.5 - Fixed issues
Key Customer Summary Severity

IPSW-15076 Moving terminals in batch to another satellite network resulted in losing the Normal
connectivity from the terminal to the TAS.

PLATO-5862 When publishing messages with the retain flag set, successive updates to the Major
same topic sometimes result in
a corrupted retain cache. This occurs sporadically in a cluster or on a single
node.

IPSW-15217 Although the modem is unlocked, the system is not taking the configuration Normal
changes as it should

IPSW-15142 One of the components didn't want to perform a redundancy swap automatic Normal

IPSW-15141 In some circumstances one of the components can perform redundancy swaps
on regular basis

NMSCONF- When updating the modem to link it to another satellite network, the L2 Major
5174 configuration does not update.

PLATO-5879 The level to write messages in the log file should be lowered to not overload the Minor
logs

PLATO-5097 The MQTT messages are missing a 'Retain' flag, so they are not kept by an Normal
external message broker and do not appear any more.

IPSW-14750 Packet loss can occur on long term high load traffic Normal

NMSCONF- The Terminal Configuration System keeps its Transmission Control Protocol Major
5188 connection open after it replied to a request from the terminal.

NMSCONF- The value of the PIR or Peak Information Rate in a class based service profile Critical
5114 changes after a full upgrade.

DLGH5GUI- Some filters in the GUI do not work. Major


3247

PLATO-5898 Sporadic Dialog Mobility Manager restarts occur due to a software issue. Critical

PLATO-5904 The configuration does not accept two baseband racks with different switch Major
types.

S3PDMA- The Remote Terminal Monitoring or RTM collector contains a memory leak on Major
5005 the Newtec Terminal Configuration System or TCS.
15 issues

3.8 Release 2.4.1.6 - Fixed issues


Key Customer Summary Severity

IPSW-14723 One of the internal components is not learning the default route of the satellite Normal
network

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 29 of 34 Version 1.1
Key Customer Summary Severity

DMM-218 The communication time between internal components should be improved. Normal

DLGH5GUI- When editing forward carrier settings via the Network Management System or Major
3249 NMS GUI, all interfaces can be selected as transmit interface.

DLGH5GUI- In a single screen, the prefix of the frequency sometimes is not identical. Minor
3250

DLGH5GUI- Filtering based on Return Technology is not possible via the Dialog Network Minor
3248 Management System or NMS GUI.

DMM-397 The HTTP subscriber gives a notification of failure to communicate and POST Major
the current subscribe events.

DLGH5GUI- When a modem with a Layer 3 network is copied, the network part returns Minor
3268 errors.
7 issues

3.9 Release 2.4.1.7 - Fixed issues


There is a security fix in this release

Key Customer Summary Severity

DMM-406 Routes are not always announced Normal

NMSCONF- Fix for the log4j security vulnerability. Critical


5211

PLATO-5958 Security fix: mitigation for Log4J CVE-2021-44228. Major

NMSCONF- After an upgrade from attachment profile to auto attachment, the modems do Major
5209 not re-provision.

S3PDMA- Influxed memory usage too high due to 'modem.tcs' measurements. Major
5046

NMSCONF- When deleting a Virtual Network Operator or VNO after being freed up from all Minor
5111 used resources, Dialog NMS does not allow to remove the VNO.

PLATO-5871 The MRC controller is not showing PTP alarms Minor


7 issues

3.10 Release 2.4.1.8 - Fixed issues


There is a security fix in this release

Keycloak can be used as alternative to CROWD within the Dialog system for authentication and
authorization purposes.

Key Customer Summary Severity

IPSW-15045 MPLS RSVP is not coming up on L2 Normal

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 30 of 34 Version 1.1
Key Customer Summary Severity

IPSW-15076 Moving terminals in batch to another satellite network resulted in losing the Normal
connectivity from the terminal to the TAS.

NMSCONF- Error when trying to remove the HRC SCPC frequency slot in the Return Minor
5201 Frequency Plan configuration.
Successfully removed the HRC MxDMA config, but the system is not allowing
to remove the SCPC config.

DLGTICS-316 Security fix: mitigation for Log4J CVE-2021-44228 Major


4 issues

Key Techpubs Customer Facing Description Severity

CP- Moving the MRC demodulator to an other satellite network gave an error on the start Major
679 and stop frequency

1 issue

4 Known Issues
All open and known issues are listed hereafter:

The severity assigned to the issue is defined as follows:

• Major: Limitation when using a feature but no workaround is available.

• Normal: Limitation when using a feature but a workaround is available.

• Minor: Anything else.

Key Customer Summary Severity

DLGDMADEVM- Distribution switch elements in Dialog NMS are still visible for Private Cloud Normal
129 Infrastructure Hub modules.

DLGDMADEVM- Adapting the Attachment Profile in the terminal does not send a 'Modem Major
136 Update Request' to the 'Dialog Provisioning Element'.

DLGDMADEVM- For a 4IF, the redundancy controller is not monitoring the L2DEM virtual Major
144 machine within the Dialog system.

DLGH5GUI-3280 Auto-Attachment MAC address search field is case sensitive and should not Minor
be.

DLGH5GUI-3281 The modem Advanced filtering gives an error when selecting a possible Major
match.

DLGH5GUI-3303 Renaming the Return Frequency Return Capacity Group adds a new QoS Major
class but does not delete the old one.

DLGH5GUI-3304 NMS Equalink or Non-linear Predistortion (NLDP) does not support M6100 Critical
but it overwrites the M6100 NLPD configuration.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 31 of 34 Version 1.1
Key Customer Summary Severity

DLGH5GUI-3305 In the GUI it is not possible to update the access rights of a return QoS child Major
pool dedicated to a Virtual Network Operator

DLGMETCOL-19 Some of the MRC metrics are not populated. Major

DLGRTMCDEV- In some cases it is not possible to disable terminal real time monitoring. Major
60

DLGRTMCDEV- MQTT messages are not always handled in correct time sequence. Major
63

DLGTICS-120 The information icons are not working on the Terminal Installation Minor
Certification System GUI.

DLGTICS-204 The Terminal Installation Certification System can get aborted with a Normal
modem access error.

MCM7500-742 Enabling AES256 can make the modem to log out and gives error Normal
messages

NMSCONF-4882 The baseband matrix is receiving the wrong configuration. Major

NMSCONF-5010 Changes on a Class Based Return Pool do not trigger an update on the Major
Return Controller Manager Distortion Margin.

NMSCONF-5067 The BGP domain is not correctly updated when updating the domain of a Major
terminal.

NMSCONF-5098 When repeatedly switching from HRC MxDMA to S2 and back, sometimes Major
the return technology switch does not take effect.

NMSCONF-5123 Some management traffic is processed as Best Effort traffic. Minor

NMSCONF-5149 In a certain use case, the batch API returns wrong result numbers. Major

NMSCONF-5170 The log of the redundancy controller is mentioning a lot of failed tasks when Minor
the Distribution Switch is misconfigured.

NMSCONF-5177 While creating a service profile with the API, the Peak Information Rate is Normal
set to '0'.

NMSCONF-5201 Error when trying to remove the HRC SCPC frequency slot in the Return Minor
Frequency Plan configuration.
Successfully removed the HRC MxDMA config, but the system is not
allowing to remove the SCPC config.

NMSCONF-5205 When removing a satellite network from the configuration, redundancy Major
swaps happen as not all configuration is removed.

NMSCONF-5212 When a lot of background tasks are running, the update of an attachment Major
profile can slow down the system.

NMSCONF-5241 Removing a shared network is not removing the address pools in the Major
database.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 32 of 34 Version 1.1
Key Customer Summary Severity

NMSCONF-5259 NMS Equalink or Non-linear Predistortion (NLDP) does not support M6100 Critical
but it overwrites the M6100 NLPD configuration.

NMSCONF-5261 The distribution switch didn't apply the VLAN changes when moving a Layer Major
2 terminal from one SatNet to another.

NMSCONF-5262 Some ports of the distribution switch were incorrectly disabled after a Geo- Major
redundancy swap

NMSCONF-5273 After a power cycle or Cisco reload without saving the current configuration, Major
the up-link VLANs are not loaded and require a manual action

PLATO-5309 Inframan shows irrelevant alarms for unused switch ports on a Dell Central Normal
NMS.

PLATO-5859 User data on UDP port 320 is dropped on cloud-based platforms because it Minor
is interpreted as PTP traffic.

PLATO-5900 When the customerconfig network partition gets temporarily disconnected, Major
the partition is not remounted automatically.
This condition will lead to failures while backing up the configuration or
performing a full-upgrade.

PLATO-5907 Disconnection between CSE devices occured due to a timeout. Major

PLATO-5914 The Time Series Database stops processing data even if the process is Major
running fine.

PLATO-5951 The GXT files are not restored as part of the backup. Major

PLATO-6002 One of the parameters is polling too fast causing a high load on the system. Critical

S3PDMA-4612 The 'Bidirectional Unicast Circuit' on the terminal view does not take the Major
'Best Effort catch all' rule into account.

S3PDMA-4917 A beam delete or update request should also distribute this beam delete or Minor
update request to all 'Advanced Terminal Main Elements'.

S3PDMA-4987 In the visio of the Baseband module not all demodulators are displayed. Normal

S3PDMA-4989 The Standard Terminal Manager only shows logged-on terminals. Major

S3PDMA-5003 The total alarm count parameter does not need an alarm in Inframan. Normal

S3PDMA-5008 The CPMCTL or Continuous Phase Modulation Controller does not reflect Major
the correct logon time.

S3PDMA-5020 Unable to add new alarms on most of the parameters in the Advanced Major
Terminal alarm template.

S3PDMA-5023 On high loaded systems, some L-band Switch Matrix elements display no Minor
Matrix information.

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 33 of 34 Version 1.1
Key Customer Summary Severity

S3PDMA-5037 When the number of bursts exceeds the max value, other MRCMCD Major
elements fail to display data.

S3PDMA-5039 Time Series Database typo at MRC metrics: 'configured_bandwidh' instead Minor
of 'configured_bandwidth'.

S3PDMA-5040 Some access switch element values were either too large or too small for Minor
an Int32 range which resulted in timeout alarms for those elements.

S3PDMA-5041 The Forward Link Efficiency and Received Rate in the Hub Module Status Major
dashboard should only give global data.

S3PDMA-5043 The throughput in the HRC Terminal Details dashboard is not correct when Minor
planned over several days.

S3PDMA-5049 The 'CPM Operational State' on the Grafana dashboard "Terminal Normal
Monitoring > CPM Terminal Details" shows logged off for logged on
terminals.

S3PDMA-5062 Show Base Band Pack occupation in the same graph for HRC-MxDMA and Major
HRC-SCPC.

S3PDMA-5063 A lot of buttons in the Dialog NMS mobile version do not work. Minor

S3PDMA-5065 Device Pool Status keep toggling between Manual/Auto in the Dialog NMS. Minor

S3PDMA-5066 Access Switch and Distribution Switch elements of the HP_FF_5710 Major
switches are created with the wrong driver.
55 issues

ST Engineering iDirect Proprietary


Confidentiality: Company Confidential Page 34 of 34 Version 1.1

You might also like