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.2.0.0.0
The following table lists the resolved bugs in DSR 9.2.0.0.0 release.
Table 7-1 DSR 9.2.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37670709 | 3 | 9.0.1.0.0 | Measurement reports not be deleted |
| 38036238 | 3 | 9.0.2.0.0 | DSR 9.2 PcrfRealm update issue in table when peer node configuration changed |
| 38037911 | 3 | 9.1.0.0.0 | Database comparison does not show correct count |
| 37663915 | 3 | 9.1.0.0.0 | remoteServerCleanup.sh script is not correctly executed in the SOAMs |
| 38115166 | 3 | 9.0.1.0.0 | Alarms List cannot be opened in GUI |
| 37500262 | 3 | 9.0.0.0.0 | [Rel 9.2] Advance Upgrade Health Check fails |
| 37937211 | 3 | 9.1.0.0.0 | 31000 Critical alarm is observed after upgrade |
| 37973188 | 3 | 9.0.2.0.0 | Mediation Rule for Rx-Request-Type as "AVP Code" is not working as expected. |
| 37355117 | 3 | 9.0.1.0.0 | KPI Graph only scaling up 100 |
7.2.2 vSTP
Release 9.2.0.0.0
The following table lists the resolved bugs in vSTP 9.2.0.0.0 release.
Table 7-2 vSTP 9.2.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37503220 | 3 | 9.0.2.0.0 | vSTP SMS Home Routing - vSTP is not sending SRI for the MO forwardSM |
| 37381316 | 3 | 9.0.2.0.0 | VSTP SMS Home Routing - for the SRI SM sent by vSTP, HLR is sending aborts with reason: "application-context-name-not-supported" |
| 37466616 | 3 | 9.1.0.0.0 | "VSTP Link Usage" export not working |
| 37343731 | 4 | 9.0.2.0.0 | Editing SftThrot action in GTT Action is giving error as the TA Index is incrementing |
| 38424695 | 2 | 9.1.0.0.0 | Traffic impact post SOAM site upgrade to 9.1 from 9.0.1.2 |
| 38206945 | 3 | 9.1.0.0.0 | DNS query for the entire zone does not work over TCP |
| 37965623 | 3 | 9.1.0.0.0 | vSTP 9.1 | Fail Action GTT "tcaperr" when SFAPP validation fails is not sending response to the originator of the Query |
| 37947628 | 3 | 9.1.0.0.0 | Capacity increase of Neighboring Country Table in SS7 Firewall |
| 37936936 | 3 | 9.0.1.0.0 | VSTP IR21 Utility throws error message(IR21 XML file not found). |
7.2.3 VNFM
Release 6.2.0.0.0
The following table lists the resolved bugs in VNFM 6.2.0.0.0 release.
Table 7-3 VNFM Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 38357244 | 3 | 6.0.2.1.0 | Discover VNF support "vnfSoftwareVersion", display Upgraded DSR Image - Query All VNF API |
| 38124321 | 4 | 6.0.2.1.0 | Scaling feature in VNFM 6.2 Experiencing Issues assigning null for XSI nw in stack overview for backward compatibility of VNFM 5.4.1 |
| 38399547 | 3 | 6.0.2.1.0 | Backward compatibility, Change Discover and scale VM Host name "vnf-discover-instance" to original for scaled VMs |
| 38412158 | 3 | 6.0.2.1.0 | Graceful Termination automatically cleans up DSR and SDS Noam for DSR and SDS signaling, as well as DR Noam setup termination. |
| 38357193 | 2 | 6.0.2.1.0 | Backward compatibility support / Discover and scale to level VNF support from VNFM 5.4.1 to VNFM 6.2 |
| 38356952 | 3 | 6.0.2.1.0 | Prometheus startup script file placement, trace interval, and permission issue |
| 37801542 | 2 | 6.1.0.0.0 | MySql and Kafka Cinder Volume Removal from EIDIH Template |
| 37801607 | 2 | 6.1.0.0.0 | Removal of MySQL, Kafka, Docker and Podman Version from VNFM & IDIH Deployments |
7.2.4 IDIH
Release 9.2.0.0.0
The following table lists the resolved bugs in IDIH 9.2.0.0.0 release.
Table 7-4 IDIH 9.2.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 38146701 | 4 | 9.1.0.0.0 | New AP circle || EIDIH || Error “No record found for traceInstance” while capturing the new trace |
| 37879165 | 4 | 9.1.0.0.0 | OCC|| Not able to configure the EIDIH VMs |
| 37930624 | 3 | 9.1.0.0.0 | EIDIH 9.1 | Unable to launch IDIH Application |
| 37727909 | 3 | 9.1.0.0.0 | IDIH Functionality issues post installing 9.1.0.0.22 |
7.2.5 ATS
Release 9.2.0.0.0
The following table lists the resolved bugs in ATS 9.2.0.0.0 release.
Table 7-5 ATS 9.2.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37872848 | 3 | 9.0.0.0.0 | ATS GUI and CLI is not accessible |
| 37280182 | 3 | 9.0.0.0.0 | VzW ME Lab- vDSR 902 ME ATS lab: Roaming regression test cases failure. |
| 37264618 | 3 | 9.0.0.0.0 | Verizon vDSR-902 ME ATS lab: ATS-902 Test Case failing |
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.2.0.0.0
The following table lists the known bugs in DSR 9.2.0.0.0 release.
Table 7-6 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 37945057 | 3 | 9.0.1.0.0 | Measurements reports not generating | Maintenance |
| 38058523 | 3 | 9.0.1.0.0 | newly instantiated MP servers use hardcoded password for guiadmin user | Maintenance |
| 38434733 | 2 | 8.6.0.0.0 | Verizon || All radius connections are down after upgrade 9.0.2 | Signaling |
| 37212776 | 3 | 9.0.1 | Not able to open DSR SOAM GUI | Install/Upgrade |
| 38201236 | 4 | 9.0.2 | Post DCA Activation Issues Seen | Maintenance |
| 37937211 | 3 | 9.0.2 | 31000 Critical alarm is observed after upgrade. | Install/Upgrade |
| 38114548 | 4 | 8.6 | Bharti || KK WF NOAM || Excessive Shared Memory & Excessive Shared Memory Early Warning | Maintenance |
| 38235349 | 2 | 9.1 | DSR_Call failures observer for multiple PGW,SBC,PCRF for TNC and Kel Circle | Signaling |
| 38340618 | 3 | 9.1 | vDSR 9.1.0 || dsr service restarted causing connections flapped on particular DAMP | Maintenance |
| 38452339 | 3 | 9.0.2 | MP1A DIupgrade rejected during vDSR upgrade from version 9.0.2.0.0-99.14.0 to 9.0.2.2.0_99.22.0. | Install/Upgrade |
| 37212776 | 4 | 9.0.1 | Not able to open DSR SOAM GUI | Maintenance |
| 37717657 | 3 | 9.0 | IPFEs alarming 5002/5003 randomly | Signaling |
| 38201236 | 4 | 9.0.2 | Post DCA Activation Issues Seen | Signaling |
| 38238334 | 4 | 9.0.1 | USCC Services, LLC || DSA error in AVPWL SCRN security measure counter in vDSR | Signaling |
| 38414241 | 3 | 9.0.1 | Rel_9.0.1.3: Server core file (core.vpsetup) detected in DSR after Upgrade from 9.0.1.2.0_98.26.0 to 9.0.1.3.0_98.27.0 | Signaling |
| 37105931 | 4 | 9.0 | Password Related Weaknesses | Maintenance |
7.3.2 vSTP
Release 9.2.0.0.0
The following table lists the known bugs in vSTP 9.2.0.0.0 release.
Table 7-7 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 38411674 | 3 | 9.1.0.0.0 | GTT Action testmode ON, SCPVAL FAILED but Skipped | No impact |
7.3.5 ATS
Release 9.2.0.0.0
The following table lists the known bugs in ATS 9.2.0.0.0 release.
Table 7-8 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 37637869 | 4 | 9.1.0.0.0 | OCDSR-ATS-GUI: ATS GUI should have a contrast ratio of at least 4.5:1 of text to its background | No impact |