Known Issues
This chapter describes the known issues and caveats and limitations found in Oracle Communications Session Delivery Manager.
The following table provides the defect number, a description of the defect problem and any applicable workaround for a defect problem and what release the defect was found or fixed, and if the defect was closed because it was non-reproducible, or some other state. Refer to the Oracle external database (Bug DB) defect tool for more information about defect states.
Table 8-1 OCSDM Known Issues
| Defect Number | Description | Severity | Found |
|---|---|---|---|
| 30643522 | OCSDM 8.2.1 cannot
modify LI configuration for SBC S-Cz8.3.0m1p2 and later.
Workaround: Perform all LI configuration through the ACLI. |
4 | 8.2.1 |
| 29776859 | Customers upgrading from Oracle DB 11g, BI Publisher 11.1.1.7.0 to DB 11g 11.1.1.9.0, will be able to view reports as an administrator only. As 11g is supported for only a short time longer, Oracle recommends customers perform greenfield installation to DB 12c, BI Publisher 12.2.1.1.0. | 3 | 8.2.0 |
| 29620746 | When running the 3.1.0 version of ECB, the clear trap is missing for apSysMgmtCSVCfgSaveFailTrap. Clear trap needs to be provided by the ECB product. The ECB product is tracking this issue in defect 29620746. | 3 | 8.2.0 |
| 29557185 | Bulk Device Deployment should be triggered from the same node from where the corresponding Offline configuration was created. It may fail when executed from a different cluster node. | 2 | 8.2.0 |
| 29551254 | A user is incorrectly able to modify the configuration from the Configuration Manager when Synchronized mode is set to TRUE for a device using the Offline Config spreadsheet. The Synchronized mode value set at the device cluster level overrides the value set at the device level. | 3 | 8.2.0 |
| 29626456 | Attributes under the ext-policy-server configuration element accepts IP addresses using an invalid format. A correction is also required on the SBC. | 3 | 8.2.0 |
| 29669000 | Configuration Manager input text boxes are not hardened. | 4 | 8.2.0 |
| 29669522 | When resetting a user password in User Management, the OCSDM does not perform validation against password rules. | 3 | 8.2.0 |
| 28136135 | In OCSDM Release 8.1, the xcode-session-gen-info HDR group is not supported. | 4 | 8.1 |
| 26627620 | In OCSDM Release 8.1, the sobjects HDR group is not supported. | 4 | 8.0 |
| 25388326 | The
OCSDM setup application
process may fail or the
OCSDM server may fail to
start if you enter a password for the Report Manager user (OCSREMDW) with
$,
#, and
& special
character(s) in the Custom installation in the
OCSDM setup application.
Refer to the
Create a Report Manager Database Instance on the External
Oracle Database section in the
Oracle Communications Report Manager Installation
Guide for more information.
Workaround: The password must be eight characters or more, contain at least one uppercase character, one lowercase character and a number (1-9). You cannot use the $, #, and & special character(s) in the password. Use only the supported %, period (.), and ! special characters in your password at this time. |
3 | 8.1 |
| 28180392 | Historical Data Recording (HDR) data that is pushed to Oracle Communications Report Manager from devices using SFTP does not work for SCz8.1 and ECx8.1 releases. Refer to the SCz and ECx defect 28163745 for more information. | 4 | 8.1 |
| 27946885 |
Currently, both OCSDM and an SBC does not prevent a user from downgrading a device with a login password that is already encrypted by SHA-512 to an SBC version that does not support SHA-512 password encryption. If user takes this action, the device becomes unusable because they are not able to login again. Workaround: Change the password for the following user types if they are encrypted with SHA-512: admin, li-admin, and user |
4 | 8.1 |
| 27631241 | The IPsec element can be
configured from the
OCSDM GUI even when the
entitlement on the SBC is not enabled. However, the result is that a save and
activate action (performed in the
OCSDM GUI) fails on the
device.
Workaround: Remove the IPsec element and resubmit it by using the Save & activate configuration parameter in Configuration Manager (refer to the Update a Network Function Device Configuration section in the Oracle Communication Session Element Manager User Guide for more information) or enable the IPsec entitlement on the device if the IPsec entitlement is required. |
4 | 8.1 |
| 27069201 |
For a device that is running SCz or ECz Release 8.1 (and later), the ACME Control Protocol (ACP) over Transport Layer Security (TLS) feature must be enabled on OCSDM Release 8.1 so that this device can be managed by OCSDM. If you disable the ACP over TLS feature on a device to run ACP only for releases prior to SCz or ECz Release 8.1, OCSDM management operations for this device are compromised. Workaround: Use the following steps to prompt
OCSDM to start managing
the device again:
|
3 | 8.1 |
| 25918918 | When you edit SNMP parameters for a Network Function (NF) with a device(s) in Device Manager to go from SNMPv1 or SNMPv2 to SNMPv3, the NF (with its associated devices) needs to be removed and added again. | 4 | 8.0 |
| 27601270 |
The BI Publisher defect 27758948 states that anytime a line graph tries to display a constant value (horizontally across the x-axis) for a report, the report is not rendered in some web browsers. Workaround: Use a different web browser or to enable 3-D mode on the line graph through the Layout Editor. |
4 | 8.1 |
| 27699848 | When Lawful Intercept (LI) is
configured on a device using its ACLI, the configuration is stored in on the
device. If the device is ever restored using a backup of the device, the LI
configuration cannot be accessed through its ACLI. However, when this device is
loaded in
OCSDM in Configuration
Manager, the backed up device configuration appears, including the LI
configuration.
Workaround: In OCSDM, delete the old LI configuration, and enter the current LI configuration that you want to use. |
3 | 8.1 |
| 25353891 | When adding collection groups in Report Manager, you must collect HDR data for all HDR groups by clicking the Yes checkbox in the Add a Collection Group - Step 2 dialog box because of SBC defect 25576484. Refer to the Add a Collection Group section in the Configure Report Manager to Run Reports chapter of the Oracle Communications Report Manager User Guide for more information about setting this parameter. | 4 | 7.5M3 |
| 28129255 |
When you are editing a Fraud Protection List (FPL) entry and enter the realm name into the field for the Realm parameter, this entry is not recorded in the database. Workaround: You must first click the Realm drop down-list arrow first to select the name of the SIP realm that is configured on the device. The SIP realm is associated with the match value. If the realm for which you are looking does not appear in the drop-down list, you can then type the name of this realm in the field. |
3 | 8.1 |
| 25382198 | Report Manager does not support data gathering or the TscfStats group for SBC devices with ScZ7.40 and ScZ7.4.0p1 releases. This problem was fixed in the ScZ7.4.0p2 release (refer to SBC defect 25341897). | 2 | 7.5M3 |
| 26417111 | HDR failed to load because there was a duplicated column of GPRS Tunneling Protocol (GTP) statistics. | 4 | 8.0 |
| N/A | For the Oracle Communications Mobile Security Gateway M-Cz4.1.0 Software Release, a duplicate entry is created in the CSV header (defect 26424107) for the gtp-stats HDR group. Report Manager does not process this HDR group. | N/A | 8.0 |
| N/A | If you are using the Internet
Explorer web browser for your
OCSDM session and you
press the Backspace key on your key board while configuring fields or doing
other operations in the application, you may be logged out of your
OCSDM session and be
forced to log back into
OCSDM.
Workaround: We suggest that you use another supported vendor web browser, such as Firefox. |
N/A | 8.0 |
| N/A | Due to SBC defect 24361366, OCSDM does not support an SBC device with an IPv6 management address. | N/A | 8.0 |
| 28715250 | When the
OCSDM is processing an
update from the FTP server and you attempt to view the FPL, you may receive the
error message, "Failed to load page table contents. Error: An attempt was made
to reference a node that no longer exists; the node may be a bound variable or
part of a query context".
Workaround: Wait a short time and try displaying the list again. |
4 | 8.1.1 |
| 28707570 | While the OCSDM is processing an update from the FTP server, if a user tries to manually add an entry that is part of the update, the entry may be added twice. | 4 | 8.1.1 |
| 28742032 | Once you have successfully
assigned and then unassigned an FPL to an FDP, you cannot assign that same FPL
again.
Workaround: Copy the current FPL and assign the copied FPL to FDP. |
4 | 8.1.1 |
| 28817962 | To properly configure an FDP
registration name, the name cannot contain any blank spaces. If you attempt to
register an FDP name that contains spaces, you get the following error:
" FDP registration name contains invalid characters. Valid characters are a-z,A-Z,_,0-9,-." |
4 | 8.1.1 |
Resolved Known Issues
| ID | Description | Severity | Found In | Fixed In | |
|---|---|---|---|---|---|
| 28201485 | In OCSDM Release 8.1, the sip-codec-per-realm HDR group is not supported. | 4 | 8.1 | 8.2.0 | |
| 28194322 | In OCSDM Release 8.1, the sa-srtp HDR group is not supported. | 4 | 8.1 | 8.2.0 | |
| 28396076 | The session-agent, local-response-map configuration parameter has the wrong default value, generating warnings when running verify-config. | 3 | 8.1 | 8.1.1 | |
| 28605180 | OCSDM is sending trap information to trap receivers with the wrong sysUpTime OID type of gauge32 instead of TimeTick. | 2 | 8.1 | 8.1.1 | |
| 28151272 | Fraud Detection and Prevention (FDP) device support is not available. | 4 | 8.1 | 8.1.1 | |
| 26620683 |
The Acme Control Protocol (ACP) Transport Layer Security (TLS) feature on a device must be disabled before this device can be added to a device cluster in Device Manager. |
4 | 8.0 | 8.1 | |
| 26268556 |
In OCSDM release 8.0 and later, the Berkley database and OCSDM plug-in management system encounters problems if any IP address changes are made for each cluster member node after a successful OCSDM cluster deployment. This happens if you shut down the OCSDM cluster and re-run the setup program to change any of the cluster member IP addresses. |
3 | 8.0 | 8.1 | |
| 28035170 |
If an SBC is upgraded from SCz7.2.0M4 to SCz7.4.0M1p6, OCSDM takes a long time to load and show the new configuration during its first attempt. |
3 | 7.5 | 8.1 | |
| 27970655 | OCSDM cannot load a USM 6300 device configuration after OCSDM is upgraded to Release 8.0. | 3 | 8.0 | 8.1 | |
| 27770070 | The configuration for a device could not be loaded in OCSDM because there are attribute issues introduced in OCSDM Release 8.0 that affected the operation of some models. | 3 | 8.0 | 8.1 | |
| 27450645 | Orphaned commons-collections JAR files need to be removed from production directories. | 4 | 8.0 | 8.1 | |
| 27240846 | When two different users associate the same route set to the same device, the device cannot be added to the route set. | 2 | 7.5 | 8.1 | |
| 27235892 | If one user logs
into
OCSDM and is using Route
Manager route sets and locks a route set, a different user logged into
OCSDM at the same time
can add this locked route set to another device in the
Device Route Sets
tab.
Resolution: A confirmation message dialog box appears that asks the user if they want to continue with the operation. |
4 | 7.5 | 8.1 | |
| 27137117 | After importing a file for a Route Set, if the user selected all the available columns for display, the browser client would crash and the browser cache would have to be cleared to regain GUI control. | 2 | 7.5 | 8.1 | |
| 26989900 | A high-availability (HA) device pair cannot be added to OCSDM if the cli-more element is enabled in the device system-config. | 3 | 8.0 | 8.1 | |
| 26933744 |
Only the server where the schema upload was initiated has the new updated XSD schema in its local cache. The other nodes still retain the previous XSD schema in memory. For example, in a three-node cluster setup, if a schema file was uploaded on Member A, SBC provisioning fails on Member B and Member C. |
2 | 7.5M3 | 8.1 | |
| 24588116 | The
apEnvMonTrapCurrentState trap does not display the card name in SDM fault alarm
description field due to SBC defect 25348541, which was fixed in SCZ7.3.0M3 and
SCZ7.4.0M1.
Workaround: The correct card name displays in SDM if the SBC is using either SCZ7.3.0M3 or SCZ7.4.0M1 versions or later. |
4 | 7.5M1 | 8.1 | |
