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.1.0.0.0
The following table lists the resolved bugs in DSR 9.1.0.0.0 release.
Table 7-1 DSR 9.1.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 37386705 | 2 | 9.1 | DNS lookup of hostnames of servers not working after upgrading to Release 9.1 |
| 36818553 | 3 | 8.6 | Error while enabling or preparing the DB in SBR |
| 36949476 | 3 | 9.0.2 | Issue in Data Export SOAM GUI as insert option is not enabled. |
| 36949017 | 3 | 9.0.1 | SQL failure while inserting/deleting Ipfe Target sets |
| 36818553 | 3 | 9.0.1 | Error while enabling or preparing the DB in SBR |
| 35972236 | 3 | 8.6 | Restrict the internal services on OAM servers to OAM networks only |
| 36887803 | 3 | 9.0.2 | Mediation rule [Error Code 40020]-Operation failed: Wrong value in the drop down list Message Copy |
| 36616189 | 3 | 9.0.2 | Insert option is not enable while adding Data export server |
| 37183866 | 3 | 9.0.1 | [Rel 9.1] DCA:DSA Very slow progress for importing DSA related config CSV in SO GUI |
| 36512429 | 3 | 9.0 | SFTP User not getting created |
| 36605629 | 3 | 9.0.1 | DCA:DSA S6a Reset-Request RSR w/o User-Id Detection |
| 36546579 | 3 | 9.0 | Documentation bug for adding proper notes around importing NO and SO jsons in DCA_DSA application after DSR upgrade |
| 36854727 | 3 | 9.0 | DSA user guide with UDR need to change for the comagent configuration |
| 36392648 | 3 | 8.6 | Incorrect current HaHeirRole received at the application side for Da_Mp_Leader resource's subresouce when the IMI interface (eth1) is up |
| 37063040 | 4 | 9.0 | Measurement Counter RxTcpDupPkt is Getting Pegged Incorrectly |
| 37153483 | 4 | 9.0 | Additional validation of Ring Buffer Configuration in upgrade procedure |
| 36997204 | 4 | 9.0.1 | Cron file missing after upgrade |
| 37047383 | 4 | 8.6 | Increase Hostname Length in ConnectionStatus table from 21 to 31 |
7.2.2 vSTP
Release 9.1.0.0.0
Table 7-2 vSTP Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 36234363 | 3 | 8.6.0.0.0 | Sfapp Velocity check getting failed for Update GPRS location from SGSN as LastUpdatedTS is common for VLR and SGSN |
| 36476734 | 3 | 8.6.0.0.0 | Parameter, Security Logging is not found in exported configuration of Linkset |
| 36533381 | 3 | 9.1.0.0.0 | VSTP: Operational state showing degraded in SCCP application status even after UDR is connected |
| 36856495 | 4 | 9.0.0.0.0 | SFAPP - Neighboring countries table is ignored in the Sfapp feature processing in other modes than OFF mode |
| 36079673 | 3 | 8.6.0.0.0 | SFAPP Validation Velocity Check Failed Event changes |
| 36116898 | 4 | 8.6.0.0.0 | Correct presence of value (instead of n/a) under 'VstpTmLnkAvailable' column in 'VSTP Link Usage' Measurement report |
| 36080002 | 3 | 8.6.0.0.0 | In the VLR Profile and VLR Roaming tables, 'Last Used Time' have a future timestamp |
| 36083934 | 3 | 8.6.0.0.0 | DSR 8.6.0.0.0_95.16.0 | MRN Set Id entry cannot be deleted |
| 36744071 | 3 | 9.1.0.0.0 | On DSR 9.0.2 running the vSTP applications, a user cannot update the throttle threshold for Sfthrot/Indv_Throt |
| 36809388 | 3 | 9.1.0.0.0 | Velocity of Travelling value cannot be set higher than 700 |
| 36666342 | 4 | 8.6.0.0.0 | eLynx TDM Link Failure Due To E1 HSL Bandwidth exceeding |
| 36825022 | 3 | 9.1.0.0.0 | vSTP 8.6.0.5 | MAP based routing not working for "forwardSM (MT) Opcode 46 MAP v2" messages |
| 36856033 | 3 | 9.1.0.0.0 | VSTP:SFAPP event log have missing information which makes it difficult for analysis |
| 37116736 | 4 | 9.1.0.0.0 | SFAPP: Handling timed out stale entries in UDR, in scenario where UDR does not get updated from home network STPs |
| 37116718 | 4 | 9.1.0.0.0 | SFAPP: Handling scenarios where ATI response from HLR does not contain ageOfLocation. Skip velocity check and update UDR data in this case. |
| 36872898 | 2 | 9.0.0.0.0 | Rel 9.0.2_vSTP: Abterm with SA= SNSCgPN ,NSCgPN for TIF and TIF2 service |
| 37093704 | 3 | 9.0.0.0.0 | After upgrade to 9.0.2 M3UA links to HLR are not sending the NA=12 causing traffic impact |
| 37099648 | 4 | 9.0.0.0.0 | Removing extra Vital logs in SFAPP code leg that may be causing timing/performance issues |
| 37143183 | 4 | 9.1.0.0.0 | vSTP SFAPP - SS7FW - CCNDCMCC mapping table fault ( Not allowing multiple entry with same MCC) |
7.2.3 VNFM
Release 6.1.0.0.0
The following table lists the resolved bugs in VNFM 6.1.0.0.0 release.
Table 7-3 VNFM 6.1.0.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 36748037 | 4 | 9.0 | Section 11.5 needs to be added to DSR Security Guide |
| 37258661 | 4 | 9.1 | Third Party Library Upliftment For VNFM |
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.1.0.0.0
The following table lists the known bugs in DSR 9.1.0.0.0 release.
Table 7-4 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 37473056 | 2 | 9.0.0.0.0 | vDSR v9.1.0 Replication Audit not completing for Spare SBR after rebooting Active SBR | The SBR server switchover stops during
audit.
Workaround: There is no workaround available. |
| 37475504 | 2 | 9.0.2.0.0_99.14.0 | GUI Slowness observed for both NOAM & SOAM in DSR 9.0.2.0.0_99.14.0 | The GUI runs slowly as the disk space on SOAM is full.
Workaround: Guided customer to clear the disk space, post clearing, the GUI worked. |
| 37765567 | 2 | 6.1.0.0.0_61.3.12 | All the servers are not coming via VNFM 6.1.0 , DSR version 9.0.1.1 | A few C-Level servers failed to launch during the
release of DSR 9.0.1.1.0. Deployment was done
manually.
Workaround: There is no workaround available. |
| 36524008 | 3 | 9.0.2.0.0-99.13.0 | DSR Traces showing Unkown Profile while using XLVM profile , MMI fixes for XLVM | MMI GET/PUT operations will not work for some of the MP
profiles that is XLVM , 35K_MPS etc.
Workaround: There is no workaround available. |
| 37212776 | 3 | 9.0.1.0.1-98.16.0 | Not able to open DSR SOAM & NOAM GUI | Unable to open DSR SOAM and NOAM GUI
Workaround: In order to log in to SOAM and NOAM, WA must restart Comcol when the login attempt fails. |
| 37355117 | 3 | 9.0.1.0-98.14.0 | KPI Graph only scaling up 100 | As the graph consistently displays values up to 100 but
the MPS (Multimedia Priority Service) numbers are significantly higher
than 100, the KPIs filter will not correctly display the graph for MPS
statistics.
Workaround: KPI (Key Performance Indicator) Graph is displayed properly with accurate scaling. |
| 37373105 | 3 | 9.0.0.0.0 | DSR Disaster Recovery Planning | Document cleanup Disaster Recovery
Workaround: There is no workaround available. |
| 37380237 | 3 | 9.0.1.0.1_98.16.0 | IPFE issue ,Fix to handle duplicate live configurations iptables rules | Duplicate live configurations IP table rules.
Workaround: The purpose of this update is to eliminate duplicate IP table rules and prevent race conditions that could affect configured rules and chains and result in IP tables restoration. |
| 37460349 | 3 | 9.0.0.0.0 | False Critical alarms for DA Leader process on wrong SOAM | False Critical alarms for DA Leader process on wrong
SOAM
Workaround: No functional impact. Alarm is not relevant since MPs and VSTP MPs are not part of topology. WA (Wide Area) already shared to clear the alarm. |
| 37500262 | 3 | 9.0.0.0.0 | [Rel 9.2] Advance Upgrade Health Check fails | Advance Upgrade Health Check fails and stops at 20% with
an exception.
Workaround: The advance upgrade Health Check will generate the required report. |
| 37663915 | 3 | 9.0.2.0.0_99.14.0 | remoteServerCleanup.sh script is not correctly executed in the SOAMs | Backup and measurement files that have been exported
cannot be deleted, consuming up disk space.
Workaround: There is no workaround available. |
| 37727909 | 3 | IDIH 9.1.0.0.22 | IDIH Functionality issues post installing 9.1.0.0.22 | Due to the cinder volume dependencies, VMs are not
returning to a normal state when Mysql or Kafka VMs go down, and cinder
volumes are not mounting.
Workaround: There is no workaround available. |
| 37781521 | 3 | 9.0.0.0.0 | Upgrade getting Failed from version 8.6.0.1 to 9.0.1.1 on the Standby NOAM | 1st HOP upgrade was failing for TPD version.
Workaround: New TPD 8.0.0.0.0_90.19.1 is provided and fix for same is submitted in DSR 9.0.1.2.0. |
| 37848613 | 3 | 9.0.1.0.0 | [9.1] TSA MAX DAMP count from 16 to 32 | Feature to upgrade from 16 IPs to 32 IPs done in 8.6
release, adding it back in 9.0.1.0.0.
Workaround: There is no workaround available. |
| 37171152 | 4 | 9.2.0.0 99.14 | DCA Script Compilation Error |
Customer getting DCA script compilation error alarm when enabling the TDC check for continent in DSA. Workaround: Issue resolved, alarm will clear, and DSA application will start. |
| 37396728 | 4 | 8.6.0.2.1_110.15.1 | DSR 9.0.1| ERROR: Birva inside reserversc size in NOAM upgrade log | No functional impact. |
| 37502132 | 4 | 9.0.0.0.0 | Upgrade document update for DSR 9.1 | Upgrade document update for DSR 9.1.
Workaround: The upgrade document is updated with resolution. |
| 37520607 | 4 | 8.6.0.0.0 | The Export File Transfer failure alarm (10104) does not provide Task ID in instance | The Export File Transfer failure alarm (10104) does not
provide Task ID in instance. Users insist TaskId to be part of GUI
display.
Workaround: TaskId is displayed along with manual clearing of alarm upon next successful export. |
| 37581533 | 4 | 8.6.0.3.0 | Documentation bug to address FQDN validation change | Single word FQDN/Realm not
supported.
Workaround: There is no workaround available. |