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.1.0.0
The following table lists the resolved bugs in DSR 9.0.1.0.0 release.
Table 7-1 DSR 9.0.1.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 |
| 35559679 | 3 | 9.0 | DSA low layer filtering feature changes |
| 35574248 | 3 | 8.5.0.2.1 | Invalid Framed-Ipv6-Prefix Error during Radius Call |
| 35699416 | 3 | 9.0 | Mediation - Rule template screen gets blank whenever they tried to add custom AVP |
| 35684946 | 3 | 8.6.0.5.0 | DSR8.6.0.5:core core.httpd formed in initial installation Partner Visible |
| 35826484 | 3 | 9.0 | DCA:DSA option is unavailable in measurement report |
| 35867245 | 3 | 9.0 | Mismatch of the vulnerability validation condition in DSA Userguide and DSA FD of Application-ID Whitelist Screening (AppIdWL) countermeasure |
| 35625042 | 4 | 9.0 | DSR Signaling FW malfunctions on IPFE with multiple TSA configured |
| 35625042 | 4 | 8.6 | Update DSR Security Guide for tpdProvd password reset |
7.2.2 vSTP
Release 9.0.1.0.0
Table 7-2 vSTP Release 9.0.1.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 35706581 | 3 | 8.6 | EIR service is not working when message is rt on gt |
| 35616149 | 3 | 8.6 | vSTP GUI: Issue with import for HSL links in interface mappings |
| 35248609 | 3 | 9.0 | PDU Pool exhausted on eLynx setup |
| 35133399 | 3 | 8.6 | Negative Ack for SRI Message when MSISDN is found in UDR |
| 34886332 | 3 | 8.6 | vSTP abterms and watchdog failures due to Segmented XUDT packets reassembly |
| 35168080 | 3 | 8.6 | eLynx E1 physical status is not available in application |
| 35124036 | 3 | 8.6 | IR21 conversion providing empty file of NE in output |
| 35070313 | 3 | 8.6 | Ready status not send to peer when received in proving period |
| 35200075 | 3 | 8.6 | Ready status not send to peer when received in proving period |
| 35277482 | 3 | 8.6 | SIF = 272 and SIO = 1 packet is truncated |
| 35363059 | 3 | 8.6 | Syntax issue for Domain Name or Address of the DNS Record in ENUM |
| 35248790 | 3 | 8.6 | PDU buffer continuously growing |
| 35478052 | 3 | 8.6 | [vENUM] DNS non-existing domains timing out |
| 35478029 | 4 | 8.6 | Decrease logging frequency for Event 70472 "ENUM Prof not found" |
| 35414654 | 4 | 8.6 | Requirement of loop back status in Link status with eLynx |
| 35363033 | 4 | 8.6 | Multiple links or connections cannot be selected under vSTP maintenance tab |
| 35143179 | 4 | 8.6 | [vENUM] Long numbers are rejected by ENUM. Need to accept long numbers upto 30 digits. |
| 35297513 | 4 | 8.6 | M2PA Config Description should include milliseconds (8.6) |
| 35545559 | 4 | 8.6 | Venum FMP was blocking traffic on port 49153 |
7.2.3 VNFM
The following table lists the resolved bugs in VNFM 6.0.1.0.0 release.
Table 7-3 VNFM Release 6.0.1.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 35874844 | 2 | 9.0 | DSR Signaling Cloud-Init Failed to connect to Signaling VIP instance |
| 35854237 | 3 | 9.0 | Network Not Configured correctly when VNFM is ipv4 & VIM is ipv6 |
| 35814357 | 3 | 9.0 | SBR Scale Issue - Newly spawned SBRs are not added to any Server Group |
| 35472050 | 3 | 9.0 | Graceful termination failure for DSR Signaling and SDS Signaling (9.0.1.0.0_98.3.0) on VNFM_6.0.1.0.0_60.3.0 |
| 35594972 | 4 | 6.0 | "numServiceMp" parameter not mentioned in VNFM 6.0.0 usage instructions page. |
| 35754632 | 4 | 9.0 | VNFM : 6.0.1-60.5.2 : Only one Server group is creating for SBR in Diameter+sbr large setup |
| 35788901 | 4 | 6.0 | Response 400 if "vnfInstanceDescription" parameter (optional) left empty |
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.2 vSTP
Release 9.0.1.0.0
Table 7-4 vSTP 9.0.1.0.0 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 35846227 | 3 | 9.0 | vSTP GUI: Issue in Edit operation using GUI for GttActions MO after DIU. | GUI screen for Insert freezes in some
scenarios.
Workaround: Use MMI for Insert operation. |