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.0.2.2.0
The following table lists the resolved bugs in DSR 9.0.2.2.0 release.
Table 7-1 DSR 9.0.2.2.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37952982 | 3 | 9.0 | SDS 9.0.2: Command log script failed to execute due to python upgrade |
| 38010747 | 3 | 9.0 | [Rel 9.0.2.2] Certificate Bulk Upload |
| 37416020 | 3 | 9.0 | DCA:DSA Incorrect behaviour observed regarding vendorId for AVPWL_Screening countermeasure and Implementation of getavpmap in 9.0.2 |
| 37848602 | 3 | 9.0 | [9.0.2] TSA MAX DAMP count from 16 to 32 |
| 37848430 | 3 | 9.0 | [9.0.2] IPFE Alternate IP in TSA, giving 500 error |
| 37663915 | 3 | 9.0 | remoteServerCleanup.sh script is not correctly executed in the SOAMs |
| 37733630 | 3 | 9.0 | APW 9.0.2 : Alarm 10104 clearance on successfull export |
| 37860557 | 4 | 9.0 | Script for FQDN/Realm label format issue - 9.0.2 |
7.2.2 vSTP
Release 9.0.2.2.0
Table 7-2 vSTP Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37516782 | 3 | 9.0.2 | Traceoam boot on DSR,VSTP MP after process reboot |
| 37343731 | 3 | 9.0.2 | Editing SftThrot action in GTT Action is giving error as the TA Index is incrementing in 9.0.2.0.0_99.14.1 |
| 37093704 | 3 | 9.0.2 | Network Appearance (NA) for ITU-S network is not sent in outgoing packet |
| 37099648 | 3 | 9.0.2 | "sendToCommagent: Successfully sent message to commagent" log continuously seen |
| 37503220 | 3 | 9.0.2.1 | vSTP is not sending SRI for the MO forwardSM |
| 37381316 | 3 | 9.0.2.1 | VSTP SMS Home Reroute - for the SRI SM sent by vSTP, HLR is sending aborts with reason: "application-context-name-not-supported" |
| 37554656 | 3 | 9.0.2 | Customer is unable to configure the TTMAP feature via the GUI on DSR 9.1 |
7.3 Known Bug List
The section lists the known bugs for DSR, vSTP, and VNFM along with the associated customer impact statements.