Caveats and Limitations

Oracle Communications Session Delivery Manager

Migration from OCSDM 7.5M3 to OCSDM 8.2.1 is not supported. Customers running OCSDM 7.5M3 must first migrate to any previous release of OCSDM 8.x and then upgrade to 8.2.1.
When you add or edit the snmp-user-entry element through the OCSDM GUI for a device, applying a none or empty password for the Auth protocol and Priv protocol parameters are not supported.
Workaround: If a none or empty password is required for Auth protocol and Priv protocol parameters, you must apply these parameters through the device ACLI.
Do not add spaces to the "To Address" of the local routing policy.
SNMPv3 parameters are not supported when adding a Network Function (NF) through the OCSDM REST API.
Workaround: You can enter SNMPv3 parameters for an NF that you want to add through the OCSDM GUI.
OCSDM does not support devices with IPv6 management addresses. Refer to defect number 24361366 for more information.
New R226 security features where introduced in the SCz8.1 and ECz 8.1 releases. If you need to manage devices with these releases (and later) with OCSDM, you must perform the following tasks:
1. Upgrade to OCSDM 8.1 or later to manage releases which have the R226 security features.
2. You must enable ACP over TLS on the devices.
Refer to the Configure Transport Layer Security Certificates section in the Oracle Communications Session Delivery Manager Installation Guide for more information regarding OCSDM support.
We recommend that the target name of your SBC device does not have an underscore character (_). This character may cause information to not appear correctly for an SBC device in OCSDM product applications. Also, the historical data record (HDR) data detection feature does not work on an SBC device if its name has an underscore.
If the plug-in is replaced or upgraded, any previously uploaded XSD work spaces are removed.

Workaround: If required, reapply the XSD work spaces once the plug-in is installed.
When a user installs a plug-in on a cluster node that supports new functionality, other users that are logged in may not see this new functionality.
Workaround: The user can use click Refresh in Device manager or log out of their SDM GUI session and then log back in to see the change.
When you use the OCSDM setup process to create a self-signed certificate for OCSDM northbound WebServer HTTPS communication, a single DNS name can be used only because OCSDM supports one northbound HTTPS interface.
When you use the OCSDM setup process to create an entity certificate to facilitate mutual authentication for OCSDM southbound (ACP), a single DNS name can be used only because the OCSDM supports one southbound ACP over TLS interface.
In the Element Manager Plugins table (Tools > Plugin Management), you cannot sort the Status, Server, and Date Modified columns in ascending or descending order.
If you implement an OCSDM cluster, one server only must be started successfully and operational before other servers in the cluster can be started.
When connecting an SDM to an SBC with the Admin Security ACP feature enabled, you must have the security, admin-security, enable-login-banner configuration parameter set to disabled.
The ability to use an offline configuration to provision network function (NF) device clusters is not available for the Acme Packet 9200 platform.
When the Fraud Detection and Prevention feature is enabled, you must run the OCSDM as a standalone server only.
When any changes are made to existing entitlements, OCSDM does not automatically refresh and the new entitlements changes are not enabled.
Workaround: Remove and re-add the device to OCSDM.
In custom OCSDM installations, SAML Single sign on configuration for importing self-signed certificates into the Route Manager certificates file (cacerts), is not currently supported.

Oracle Communications Session Element Manager

Many components of the Oracle Communications session delivery product device software are licensed by Oracle and some product devices require a license key. Product devices that have applied a license key appear in Device Manager, however device license entitlements do not currently appear in Device Manager.
Workaround: Use the show entitlements command in the device ACLI to gather license entitlement information.
In the event of an unexpected server shutdown, the incremental save operation may be incorrectly reported as being successful if it is associated with a offline configuration update.
When entering a single quote in an attribute value, use the backslash symbol "\" to escape.
A CXF (SOAP) client may have its connection closed by the server for long duration transactions.

Oracle Communications Report Manager

If you are upgrading Oracle Communications Session Report Manager from a previous version, BI Publisher and Oracle database (Listener and Listener 2) need to be running and properly connected when you use the Oracle Communications Session Delivery Manager setup installation process, during which these databases are migrated. See the Prepare for a Report Manager Upgrade section in the Pre-Installation Tasks chapter of the Oracle Communications Session Report Manager Installation Guide for more information.
By default, the password for the nncentral user, OCSREMDW database user, and BI Publisher (for example, DEV_MDS and DEV_BIPLATFORM) database users for the Oracle reporting database expires in 6 months. Once the password expires, the nightly backup and restore capability for reporting fails. You must go to the Oracle database to change each user password. Ask your Oracle support for more specific information about performing this task.
Note:
This limitation applies to Report Manager users who have installed an Oracle database on the same server as OCSDM only.
Report Manager does not support data gathering or the TscfStats group for SBC devices with ScZ7.40 and ScZ7.4.0p1 releases. This problem will be fixed in the ScZ7.4.0p2 release.
With the introduction of OCSDM, Release 8.0, there is a single secure sockets layer (SSL) keystore that includes BI Publisher certificates. Any BI Publisher certificates that were previously imported into the keystore before Release 8.0 are lost.
- Ensure that the BI Publisher certificate is in the desired directory on the OCSDM server. If the BI Publisher certificate is not on the server you must transfer it to server. See the Save and Transfer the BI Publisher Certificate to Session Delivery Manager section in the Register Oracle BI Publisher chapter of the Oracle Communications Report Manager Installation Guide for more information.
- Ensure that the BI Publisher Certificate is added to the keystore either through the OCSDM server setup program (setup.sh) or upload it through the OCSDM GUI.
  
  Note:
  If you are using the OCSDM server setup program to upload a BI Publisher certificate, you must run the setup program on each OCSDM server cluster node to upload the BI Publisher certificate on each node. If you perform this task through the OCSDM GUI, the BI Publisher certificate is replicated to all OCSDM server cluster nodes.
  - See the Configure Southbound Interface Transport Layer Security section in the Custom Installation chapter of the Oracle Communications Session Delivery Manager Installation Guide for more information about loading the BI Publisher certificate through the OCSDM server setup program.
  - See the Manage Certificates for Southbound Authentication chapter in the Oracle Communications Session Delivery Manager Administration Guide for more information about loading the BI Publisher certificate through the OCSDM GUI.
In OCSDM, Release 8.0 or earlier, Report Manager is supported on Oracle Linux 6.5, 6.6, 6.7, 6.8 only. Also, Oracle Database 11g Standard Edition One, and Oracle Business Intelligence (BI) Publisher 11g are supported only.
In OCSDM, Release 8.x, Report Manager does not support device clustering.
In OCSDM 8.2.1, Report Manager works with Oracle DB 12c/BIP 12.2.1.1.0 and not DB 11g. Therefore, during migration from a previous OCSDM 8.x release (running 11g) to OCSDM 8.2.1, only Element Manager is migrated and Report Manager is not.