7 Resolved and Known Bugs
This chapter lists the resolved and known bugs for DSR.
These lists are distributed to customers with a new software release at the time of General Availability (GA) and are updated for each maintenance release.
7.1 Severity Definitions
The problem report sections in this document refer to bug severity levels. Definitions of these levels can be found in the publication, TL 9000 Quality Management System Measurement Handbook.
Problem Report
A report from a customer or on behalf of the customer concerning a product or process defect requesting an investigation of the issue and a resolution to remove the cause. The report may be issued through any medium.
Problem reports are systemic deficiencies with hardware, software, documentation, delivery, billing, invoicing, servicing, or any other process involved with the acquisition, operation, or performance of a product. An incident reported to request help to bring back the service or functionality to normal without the intent to investigate and provide a resolution to the cause of the incident is not a problem report.
Severity Definitions
Service requests for supported Oracle programs may be submitted by you online through Oracle’s web-based customer support systems or by telephone. The service request severity level is selected by you and Oracle and should be based on the severity definitions specified as follows:
- Severity 1 - Your production use of the supported programs is
stopped or so severely impacted that you cannot reasonably continue work. You
experience a complete loss of service. The operation is mission critical to the
business and the situation is an emergency. A Severity 1 service request has one
or more of the following characteristics:
- Data corrupted.
- A critical documented function is not available.
- System hangs indefinitely, causing unacceptable or indefinite delays for resources or response.
- System crashes, and crashes repeatedly after restart attempts.
Except as otherwise specified, Oracle provides 24 hour support for Severity 1 service requests for supported programs (OSS will work 24x7 until the issue is resolved) when you remain actively engaged with OSS working toward resolution of your Severity 1 service request. You must provide OSS with a contact during this 24x7 period, either on site or by phone, to assist with data gathering, testing, and applying fixes. You are requested to propose this severity classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Oracle.
Network Software Support & Sustaining Support, please see the Oracle Communications Network Premier & Sustaining Support and Oracle Communications Network Software Support & Sustaining Support sections above. - Severity 2 - You experience a severe loss of service. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
- Severity 3 - You experience a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality.
- Severity 4 - You request information, an enhancement, or documentation clarification regarding your software but there is no impact on the operation of the software. You experience no loss of service. The result does not impede the operation of a system.
7.2 Resolved Bug List
This sections lists all resolved bugs for DSR, vSTP, and VNFM in this release.
7.2.1 DSR
Release 9.3.1.0.0
The following table lists the resolved bugs in DSR 9.3.1.0.0 release.
Table 7-1 DSR 9.3.1.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 39443386 | 2 | 9.2.0.0.0 | 5001 alarms generated on IPFE after running savelogs_plat on MPs |
| 39482717 | 2 | 9.2.0.0.0 | GUI does not open and throws an exception when RAM usage exceeds 90% -- DSR Version --9.2.0.0.0_102.16.0 |
| 39481822 | 3 | 9.0.0.0.0 | SDS pdbi connection got down due to memory leak issue |
| 39697674 | 3 | 9.0.0.0.0 | SDS: Patches for Copy-Fail Remediation Do Not Match md5sum.txt Values |
| 39573218 | 3 | 9.0.0.0.0 | 9.0.1.0.1-98.16.0_ Issue when attempting to perform "backup all" command from GUI |
| 39335993 | 3 | 9.0.0.0.0 | apwSoapServer process restart | decryptKey cert length processing issue |
| 39668170 | 3 | 9.2.0.0.0 | Rule template has been skipped message when importing Rule Template |
| 39488167 | 3 | 9.0.0.0.0 | Assistance Needed: DSR 8.6 to 9.0.1.1 Migration Script Output and IPv6 Mapping Issues |
| 39327480 | 3 | 9.0.0.0.0 | TLS certificates were removed after upgrading from version 8.6 to 9.0.1.1 |
| 39368934 | 3 | 9.0.0.0.0 | Log rotation persistence reverted to default after DSR 9.2.0.0.0 upgrade |
| 39475049 | 3 | 8.6.0.0.0 | Multiple alarms generated on IPFEs while running savelogs_plat on IPFE Servers |
| 39571436 | 3 | 9.3.0.0.0 | Analyze IDIH URL issue in Diameter -> Troubleshooting with IDIH -> Maintenance -> Traces screen |
| 39670620 | 3 | 9.3.0.0.0 | Centralized IDIH flag modification and starting of network traces when the flag is disabled |
| 39359375 | 3 | 9.3.0.0.0 | Backward Compatible support/Enhancement in DSR 9.3.1 for IDIH 9.3 and 10.x |
| 39702752 | 3 | 9.2.0.0.0 | [Error Code 19004] - No available VIP address to be added to the Local Node when attempting to insert local node |
| 39558142 | 4 | 8.6.0.0.0 | Legacy TLS v1.0 and v1.1 are accepted by SDS on xDS listener port 5876 creating compliance risk |
7.2.2 vSTP
Release 9.3.1.0.0
The following table lists the resolved bugs in vSTP 9.3.0.0.0 release.
Table 7-2 vSTP 9.3.1.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 39794237 | 2 | 9.0.2.0.0 | vSTP process restarts observed when WGTTLS is enabled |
| 39787090 | 2 | 9.1.0.0.0 | vSTP Process Restarts observed on MNP number conditioning |
| 39147895 | 3 | 9.3.0.0.0 | DSR_Upgrade : 9.0.2.0.0 to 9.3.0.0.0 : ENUM traffic not working post upgrade |
| 39552401 | 3 | 9.1.0.0.0 | TT Modification Not Working for TT-Only Changes |
| 39564667 | 3 | 9.1.0.0.0 | SSN value '0' not accepted in GUI with OPTSN |
| 39564684 | 3 | 9.1.0.0.0 | Restriction on Reusing Point Codes Across Loopsets |
| 39224311 | 3 | 9.3.0.0.0 | MOBR: Unable to define an OPC in a different domain than the DPC in RTX MO unless an OPC alias is configured. |
| 39788704 | 3 | 9.1.0.0.0 | M2PA links not coming UP after migration from EAGLE to vSTP |
| 39762658 | 3 | 9.1.0.0.0 | Problem with Measurement for vENUM MP Performance in Release 9.1 |
| 39803206 | 3 | 9.1.0.0.0 | vSTP excess logging in fetchVstpSecuLog.sh script causing /var partition size increase |
| 39875514 | 3 | 9.0.2.0.0 | Deletion of MRN Set with same IDs and associated with GTT Actions is not working correctly |
| 39875675 | 4 | 9.1.0.0.0 | Missing linkset filter in GttSelector and Adjustment of GTA Config parameters in vSTP GUI |
| 39737550 | 4 | 9.1.0.0.0 | International ITU-T Point Code Display Order is non-standard |
| 39158599 | 4 | 9.3.0.0.0 | "Normalated" error seen on Operation Reason of M3UA links |
| 39177438 | 4 | 9.0.2.0.0 | ENH: For Sfapp store the current VLR in UDR in case of ATI Timer Expiry |
7.3 Known Bug List
The section lists the known bugs for DSR, vSTP, and VNFM along with the associated customer impact statements.
7.3.1 DSR
Release 9.3.1.0.0
The following table lists the known bugs in DSR 9.3.1.0.0 release.
Table 7-4 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 39812333 | 2 | 9.2.0.0.0 | Error Code 500 Internal Server Error occurs while logging into Primary NOAM GUI | GUI access issue. |
| 39552954 | 3 | 9.0.0.0.0 | Request for Validation of Oracle Linux 8 STIG Remediation for RMS/vDSR Environment | In most cases, based on the initial analysis, the DSR guest is not expected to be impacted by the STIG remediation performed on the host VM. For additional details, refer to the updated engineering comments provided in the attachment to the bug. |
| 39418748 | 3 | 9.2.0.0.0 | DSR 9.2.0.0.0-102.16.1 | dsr process restart observed on few DA-MPs | Telus | Some traffic was lost while the DSR process was restarting. The root cause of the DSR restart could not be determined, as no ABTERM was generated to indicate the reason for the restart. |
| 39350928 | 3 | 9.0.0.0.0 | Multiple DMPs Reporting Continuous 31000 Alarms | Only alarms were there for information purpose. Script has been provided and two configuration issues has been figured out in debug session. No known impact. |
| 39680609 | 3 | 9.1.0.0.0 | DSR 9.1: 33304 DCA Runtime Errors observed in vDEA | The customer reported some alarms in the DSA application. Some of those are related to missing configurations, but while analyzing the logs, it was identified that some improvements are needed in the DSA Perl logic. |
| 39554512 | 3 | 9.2.0.0.0 | Production MDS Data Flow check | The customer has configured multiple metrics to be streamed from Kafka. It is recommended to limit the configuration to 40 metrics. The documentation will be updated with this limitation, and code changes will be added in DSR 9.3.1 to limit the number of metrics that can be configured to 40. |
| 39633017 | 3 | 9.2.0.0.0 | After upgrade to 9.2.0.0.0-102.16.1 observing Idih Producer Queue Congested frequently for MPs | The customer is seeing the expected IDIH Producer Queue Congested and MPCpuCongested alarms when there is a CPU spike. |
| 39440354 | 3 | 9.0.0.0.0 | Primary path is down for CFX peer |
The CFX peer connections were down. The CFX peer was sending an abort in response to packets originating from the secondary source of DSR to the primary address of the CFX peer. The CFX peer was expecting the primary source of DSR to send the packet to the primary CFX peer. |
| 39576485 | 3 | 9.2.0.0.0 | Server goes into grub rescue and fails to boot during upgrade |
The issue is on TPD. During the upgrade from DSR 9.0.2 to 9.2, the affected servers may enter GRUB rescue mode and fail to boot, potentially disrupting traffic until manual recovery is performed. The issue may recur after a reboot, even after applying the workaround. |
| 39444393 | 3 | 9.0.0.0.0 | Getting UDR Internal Error: Update record failed after Activation of Stateful DSA for DSR 9.0.2.1 |
The customer is getting the DCA to UDR ComAgent error alarm, due to which vulnerable messages are generated. Asked the customer for the connectivity details between the DSR and UDR. |
| 39832646 | 3 | 9.0.0.0.0 | DSR Migration 8.6 to 9.0 Traversing Platforms Causes NetworkRoutes To Be Untethered | Network route addition failure |
| 39776800 | 3 | 9.1.0.0.0 | CSV files are removing hourly from SOAM export path | CSV files getting cleaned up. |
| 39747736 | 3 | 8.6.0.0.0 | Investigation of stale SBR Session records associated with Old PCRF in SBR Session Server in RJIO | Old sessions are not being cleaned up as the release RAR queue is full. |
| 39837637 | 3 | 9.0.0.0.0 | Midwest 5G Core DRA Design and Configuration | Design related queries. |
| 39750223 | 3 | 9.0.0.0.0 | NOAM errors during DSR DSCP Rules Implementation | Error while adding DSCP rules. |
| 39818167 | 3 | 8.6.0.0.0 | DSR Server-Grouped Scoped Routes Don't Deploy to One Member Server | Route deployment issue on MP |
| 39791064 | 3 | 9.2.0.0.0 | Alarm history Export task hangs when filtered with severity equal Info or event id equal 22008 | Certain alarms are not getting exported. |
| 39764413 | 3 | 9.2.0.0.0 | Topology Hiding : Message From Untrusted MME to Protected HSS, HSS Name Not Restored | Routing related queries. |
| 39829089 | 4 | 9.0.0.0.0 | Site Accept upgrade Stuck Due to tpdProvd Running as Root | Ugrade accepance alarm remain in server. |
| 39544823 | 4 | 9.1.0.0.0 | OCC || Exporting DSA provisioning table misses Realm_List and CSV upload fails with error 50031 | Applied WA waiting for customer feedback. |
7.3.2 vSTP
Release 9.3.1.0.0
The following table lists the known bugs in vSTP 9.3.1.0.0 release.
Table 7-5 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 39922082 | 3 | 9.3.1.0.0 | Upgrade & Backout issues from 9.2.0.0.0_102.16.0 to R9.3.1 | Issues might be seen during the upgrade from 9.2 to 9.3.1 vSTP. The workaround is to reboot the VMs. It is also recommended to upgrade all vSTP MPs in batches within a small window of time to avoid these issues. |
| 35813705 | 3 | 9.0.0.0.0 | Rel 9.0.1: ENUM/DNS - NS records gets failed to add in zones after adding/rebuilding enum mp to server group. |
NS records may be missing from zones after an ENUM MP add or rebuild, causing DNS record alarms and possible zone inconsistency. Workaround: Delete and re-add the NS record with the same data to clear the alarm and ensure the record is added successfully. Alternatively, disable VENUM, delete the master file, and then re-enable VENUM. |
7.3.5 ATS
Release 9.3.1.0.0
The following table lists the known bugs in ATS 9.3.1.0.0 release.
Table 7-6 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 39909236 | 3 | 9.3.1.0.0.0 | Update required in MDS ATS suite corresponding to the changes in fix for Bug 39840798 | Non vulnerable DSA scenarios will be reported as fail. |
| 39910131 | 3 | 9.3.1.0.0.0 | CVE-2026-13346 on PIP version 26.1.2 | It is security vulnerability issue in PIP. In ATS, there is no requirement to download any package. PIP can be uninstalled. |