Features in SDM Releases 8.2.5 to 8.2.1
This section provides a summary of the features introduced in the Releases SDM 8.2.5 to 8.2.1.
Features listed from Releases SDM 8.2.5 to 8.2.1.
| Feature | Description | Where Documented |
|---|---|---|
| SDM 8.2.5 Release | ||
| Log4J upgrade to 2.16 | SDM 8.2.5 addresses CVE-2021-44228 and CVE-2021-45046, a remote code execution vulnerability, where Apache Log4J2 2.16.0 version has been applied. | Release Notes |
| View and save an audit log function | The downloaded CSV file is limited to 500 entries. | Administration Guide |
| JDK Upgrade | With SDM 8.2.5, JDK has been upgraded from 1.8u291 to 1.8u311 | Release Notes |
| Oracle Linux support | SDM 8.2.5 supports Oracle linux version 8.4 | Installation Guide |
| Fraud Protection List Data Type Formats | Phone numbers with a leading '+' Plus symbol are allowed |
|
| SDM 8.2.4 Release | ||
| SBC Software image and Bootloader file integrity Check | OCSDM performs a file integrity check on software image file and bootloader file. OCSDM continues with the workorder to upgrade a target SBC only if the image file integrity check is positive. If the image file integrity check fails, then the upgrade process is aborted on that specific SBC and continues with the workorder to upgrade the next target SBC. |
|
| Route Manager LRT Support | SDM 8.2.4 has new fields
format, priority
and weight for each route entry.
In the GUI, format is a check box which can be toggled based on the user input. If it is checked, then both priority and weight attributes must be mentioned for each route to be added using SDM. SDM 8.2.4 supports the import and export of the Priority and Weight fields from a CSV file or an existing LRT file. SDM 8.2.4 supports management of the fields Priority and Weight using the Route Manager northbound REST API interface. |
|
| Restriction to Purge Audit Logs |
SDM 8.2.4 restricts the number of days to retain audit logs by introducing a range of 2-90 days. This range is checked during manual purge and automatic purge. |
|
| JDK Upgrade | With SDM 8.2.4, JDK has been upgraded from from JDK 1.8u261 to JDK 1.8u291 |
|
| SDM 8.2.3 Release | ||
| Support for full FCAPS support for ECB. | The OCSDM 8.2.3 schema model provides the required Fault, Configuration, Auditing, Performance and Security FCAPS support for managing the Enterprise Communications Broker (ECB) devices. Configuration support, Performance support, and new Trap support have been introduced in addition to existing Traps support and Device manager support on release nnPCZ330.bz. | SDM 8.2.3 Release Notes |
| Display of alphabets in device version and schema in OCSDM | SDM now allows the display of the complete patch version number to be incorporated with the device version. For example, Acme Packet 4600 SCZ8.3.0 MR-1 Patch 10 A (Build 542) which translates to SCZ830m1p10A, is displayed as device version on the GUI and retained as is for all the modules in SDM. | SDM 8.2.3 Release Notes |
| Bootloader Upgrade with R226 license enabled | Starting with SCz8.4, when the R226 license is enabled, users cannot modify or list files from the ‘/boot’ directory using external applications. New commands have been introduced to modify files in the ‘/boot’ directory, and to provide support for the automated software and bootloader upgrades on the network function using OCSDM. | SDM 8.2.3 Release Notes |
| Route Manager LRT comment support | With SDM 8.2.3 a new field has been introduced to include descriptions for the individual route entries in a route set. SDM provides full support for the route level description field from the Web GUI, CSV provisioning and through REST interface. | Session Route Manager User Guide |
| Removing Flash Player graph and chart | 31 December 2020 was the end-of-life
for the Flash Player. Charts and grahps using the Flash player have
been removed and tabular data is now made available for the
following:
|
|
| Deleting or adding a sub-element using the REST API | Using REST northbound API you can programmatically add, update, and delete the configuration sub-elements. |
|
| SDM 8.2.2 Release | ||
| Golden Configuration Comparison and Report | Users of the Administrator and LI Administrator group can create and manage the Golden Configuration of a SDM-managed device to maintain the integrity of the network. SDM users can create, and manage a configuration comparison report. This report can be used to compare a device configuration with the master Golden Configuration. The deviations in the configuration are higlighted in the comparsion report. Users can download the report as a PDF or GZIP file. |
|
| OCSDM uses FQDN to launch the GUI | Configuring and accessing the GUI for ESBC, ECB, EOM, FDP, and ISR using an IP address (http/https) has been extended. OCSDM now allows managing SBC, ESBC, ECB, FDP, EOM, or ISR by using FQDN or IP address. You can configure OCSDM to use FQDN when connecting to the web GUI using http/https for ESBC, ECB, EOM, FDP and ISR. OCSDM can continue to manage SBC, ESBC, ECB, FDP, EOM, or ISR by preserving the current ability of managing the network function using the resolved IP address. |
|
| North Bound SNMPv3 support | In SDM, you can specify a Northbound interface for example, a network management system to receive the SNMP traps. With SDM 8.2.2, SNMPv3 is supported to forward traps to the Northbound interface. The SNMPv3 protocol provides authentication, privacy, access control, and address security vulnerabilities over SNMPv2. |
|
| Enable access control on the server-side | The Security Manager component of SDM controls access and authorization through permissions granted to user groups. Server-side access control introduces permission checks for all the APIs. If an SDM user attempts to perform an unauthorized request, the action is recorded in the application logs. |
|
| Query user before replacing network function certificates | SDM 8.2.2 prevents the replacement of security certificate and private key of the target SBC(s) with the certificate, and security key of the SBC used to create the Offline Configurtation. The Offline Configuration is associated to the device cluster and bulk configuration. |
|
| Using li-admin credentials to push li-configuration | SDM can now use the li-admin credentials over ACP or ACP/TLS to push LI-configuration to the SBC device enabled with LI license. |
|
| Fix for Adobe Flash Player end-of-life | SDM 8.2.2 removes the dependency on Adobe Flash Player. Alarms Summary is now provided as a table along with a graphical representation. |
|
| SDM 8.2.1 Release | ||
| SBC Bootloader Upgrade | Adds the ability to remotely upgrade the SBC bootloader image in addition to the SBC software image during software updates. |
|
| R226 Compliance | Eliminates the ability to view and edit both Lawful intercept (LI) and SIPREC configuration elements when running in R226 mode. Note: When R226 compliance is enabled, devices added with a LI encryption password can be managed by changing the device permissions via the Security Manager. |
|
| Lawful Intercept Config Options | Restricts the ability to view and edit LI configuration elements to the LIadmin user. |
|
| LDAP Filters Support | In addition to the existing mandatory
LDAP parameters, the OCSDM now supports the following additional
LDAP attributes and parameters:
|
|
| Audit Log Policy Enhancement | The audit log purging policy has been enhanced to always retain the last 48 hours of audit logs and cannot be configured to a lesser value. |
|
| Multiple Interface Support | OCSDM supports multiple interfaces as
follows:
|
|
| IPv6 Support | OCSDM supports IPv4 and IPv6
addresses for the following different interfaces:
|
|