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.0.0
The following table lists the resolved bugs in DSR 9.0.2.0.0 release.
Table 7-1 DSR 9.0.2.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 36343511 | 3 | 9.0 | Host OS and KVM version needs to be updated for DSR 9.x documents |
| 36141126 | 3 | 8.6 | Fixing DSA issue : When peer node name configured is greater than 15 characters |
| 35963762 | 2 | 8.5 | Process Resources Exceeded alarm appears continuously/active NOAMP (apwSoapServer) |
| 36120741 | 3 | 8.6 | DSR:DCA removal of routed service due to replication issue in UDR in 9.0.2 |
| 36220105 | 3 | 9.0 | TCL India || Duplicate Alarms observed from both Active and Standby SOAM to NMS system |
| 35785631 | 3 | 9.0 | Utilizing whitelisting rather than blacklisting example, FS.19/B.3.4.6 (Vendor Specific AVPs) |
| 36254481 | 3 | 9.0 | LDAP not working in DSR 9.x |
| 36293150 | 3 | 9.0 | Getting dsr process rebooted when Radius traffic has started | Fresh Installed Setup 9.0.2.0.0-99.8.0 |
7.2.2 vSTP
Release 9.0.2.0.0
Table 7-2 VSTP Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 36362100 | 4 | 8.6 | [vENUM] Response for Queries with digits less than 5 digits changed from SERVFAIL to NXDOMAIN |
| 36341699 | 4 | 8.6 | There is a need of functionality where user can select and copy the data from the Maintenance section of the vSTP SOAM GUI |
| 36312989 | 4 | 8.6 | [vENUM] DNSKEY queries to ENUM application turned off |
| 36176548 | 3 | 8.6 | VstpDynVelCrossed not reflecting actual count in VSTP SFAPP Performance Report - Simple |
| 36163111 | 3 | 8.6 | GTT Selector configuration issue |
| 36366450 | 3 | 8.6 | VSTP boot when configuration update on MRN set happens |
| 36157593 | 3 | 8.6 | eLynx driver crash on receiving ATH |
| 36189385 | 3 | 8.6 | RSP Status not updated for indirect high cost route via other VSTP MP |
| 35944185 | 3 | 8.6 | MMI is allowing to create users with un-allowed characters in comment |