Known Issues
This chapter describes the known issues in Oracle Communications Session Delivery Manager. The status column identifies what release the defect or caveat was closed, or if it was closed because it was non-reproducible, or some other state. See the Oracle external database (Bug DB) defect tool for more information about defect states.
Table 2-1 SDM Known Issues
| Defect Number | Description | Found | Fixed |
|---|---|---|---|
| 26354293 |
The Determine the RADIUS Group that Your Devices are Using section was added to the Security Manager chapter of the Oracle Communications Session Delivery Manager Administration Guide to provide the information required to integrate SDM with a RADIUS server for user authentication. |
7.5M2 | 8.0 |
| 25746713 | SDM trap support was missing for the apMonitorCollectionDownTrap and apMonitorCollectionClearTrap traps. Support for these traps was added in SDM, Release 8.0. However, even though SDM has correct trap mapping, there is an SBC defect regarding these traps, where the incorrect value is being sent from device to SDM. See defect 25876639 to track the SBC issue. | 7.5M3 | 8.0 |
| 26523097 |
The ACLI customer configuration failed to load due to XSD validation errors for local-policy/@source-realm and realm-config/@identifier attributes. These errors occurred because of a stricter regular expression pattern for these attributes in SCX630m3 XSD. The regular expression pattern for types RealmNameOrStar and Name in SCX630m3 and SCX630m7 XSDs were modified to replicate the ACLI behavior that allowed values starting with numbers or alphabetical characters with a length of up to 128 characters. |
7.5M2 | 8.0 |
| 21026830 | The customer cannot change or modify local-policies that have inter-attribute dependencies, where the value of the addr attribute determines value of type and addrPrefix attributes. SDM now accepts to and from from a sub-element with same addr value but a different type value. | 7.4M3 | 8.0 |
| 26355836 |
The NNCGEN AttributeTypeOverrides.xsd file was updated with the correct specific regex pattern of the attribute sipInterface/@stopRecurse and the XSDs were regenerated. |
7.5M2 | 8.0 |
| 20961816 | The Apply button on the various Realms tabs was disabled to prevent a user from reversing the LCV changes. This forces the realm configuration to be added before the SIP interface. | 7.5M3 | 8.0 |
| 25477544 | Berkeley DB XML was patched to free deleted file descriptors. | 7.5 | 8.0 |
| 28557993 |
When admin-security is enabled on an SBC 6350 HA device pair, the devices are unable to communicate with SDM by way of ACP. Workaround: On each HA device pair, you must disable the login banner so these devices can communicate with OCSDM. From admin mode, use the configure terminal > security > admin-security > login-config command path to access the enable-login-banner disabled configuration element to disable the login banner. |
8.0 | |
| 26174243 |
A configuration inventory containing an ACME 9650 networkInterfaceId sub-element with incorrect family attribute takes more than 30 minutes for the update of the family attribute to be applied before loading successfully. The "step 6 XQuery" was updated with refactored and efficient XQuery to update the family attribute of networkInterfaceId sub-elements, and another XQuery was updated to check for any invalid networkInterfaceId sub-element with empty family attribute even after all the updates have been made. If such an invalid networkInterfaceId sub-element exists, the load process is failed. |
8.0 | 8.0 |
| 25889227 | When upgrading from NNC75M1 to NNC75M3, the setup.sh script did not terminate after an upgrade was completed because the SessionAgent OD file incorrectly had nncIsRequired=true annotation for the identifiers attribute which was generating XSD with the mandatory SessionAgentIdentifier sub-element for sessionAgent element (minOccurs=1). When the user entered a SOAP add-element request, it did not contain value for this sub-element and therefore the operation failed during the required sub-element validation in SDM. The SessionAgent OD file was modified to remove the nncIsRequired=true annotation on the identifiers attribute and the XSDs were re-generated to make the SessionAgentIdentifier sub-element optional for sessionAgent element (minOccurs=0). | 7.5M3 | 8.0 |
| 25388326 | Report Manager does not support
the use of special characters in the ocsremdw password.
Workaround: You must use alphanumeric characters only. |
7.5M2 | |
| 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 will be fixed in the ScZ7.4.0p2 release. | 7.5M3 | N/A |
| 25353891 | For most SBC releases, Report
Manager does not support starting collection on individual HDR groups. See the
SBC defect 25576484 for more information.
Workaround: If individual selection of these groups is required, the user must log into the device(s) and run the start collection group. |
7.5M3 | |
| 24588116 | The apEnvMonTrapCurrentState trap
does not display the card name in SDM fault alarm description field due to an
SBC defect that 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. |
7.5M1 | N/A |
| 26417111
|
Historical Data Recording (HDR) failed to load because there was a duplicated column of GPRS Tunneling Protocol (GTP) statistics. | 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. | 8.0 | |
| N/A | If you are using the Internet
Explorer web browser for your
SDM 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
SDM session and be
forced to log back into
SDM.
Workaround: We suggest that you use another supported vendor web browser, such as Firefox. |
8.0 | |
| N/A | Due to SBC defect 24361366, SDM does not support an SBC device that is configured with an IPv6 management address. | 8.0 | |
| 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. |
8.0 | |
| 26409117 | There are some SBC devices that do not support SSH KEX, even though these devices suggest that they do support SSH KEX. For example, an SBC device suggests it supports diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, and diffie-hellman-group1-sha1 algorithms, but when SDM tries to SFTP using diffie-hellman-group14-sha1 or diffie-hellman-group1-sha1, it is unable to establish an SFTP session and the device remains unmanageable on SDM because either the XSD download or the load LCC is unsuccessful. | 8.0 |
