7 Resolved and Known Bugs
This chapter lists the resolved and known bugs for DSR release 8.5.x.
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.
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.
Resolved Bug List
This sections lists all resolved bug list for DSR, vSTP, VNFM, and SCEF in this release.
DSR
The following Resolved Bugs tables list the bugs that are resolved in DSR 8.5.1.0.0 release.
Table 7-1 DSR Release 8.5.1.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 33563946 | 3 | 8.5.0.2.0 | Unable to add TTG in RG4 and RG5 of Routelist |
| 33562240 | 3 | 8.5.0.0.0 | DSA Session Id issue fix |
| 33404539 | 3 | 8.5.1.0.0 | MMI command not working for "pendingtransactionlimitingconfigurationsets" present in the NOAM |
| 33378172 | 3 | 8.5.1.0.0 | "count" is different than the total records in CSV exported file |
| 33188157 | 3 | 8.5.1.0.0 | Unable to add more than 10 Application IDs and Vendor IDs in CEX Configuration Set |
| 32494839 | 3 | 8.5.1.0.0 | Increase the number of Route Groups per Route List (from 3 to at least 5) |
| 33218214 | 3 | 8.5.0.1.0 | DSA Business logic fix to handle the error code |
| 33138921 | 4 | 8.5.0.0.0 | TTG is not visible in RL GUI in edit mode |
| 32997291 | 4 | 8.5.0.0.0 | Increasing application id support per connection |
| 26313885 | 4 | 8.1.0.0.0 | DSR 8.1:ST: Status & Manage ->Files is not accessible from NO & throw error |
| 33562219 | 4 | 8.5.0.0.0 | RSA Session Id issue Fix |
| 30792667 | 4 | 8.4.0.0.0 | Fabr with UDR |
| 33511318 | 4 | 8.5.0.0.0 | Incorrect IP address state in SCTP Statistics for SCTP Multi-Homed association. |
| 33431087 | 4 | 8.4.0.3.0 | DSA Business logic fix to handle grouped AVP cases for DSD 1204 |
vSTP
The following table lists the resolved bugs in vSTP 8.5.1.0.0 release.
Table 7-2 vSTP Release 8.5.1.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 33017494 | 3 | 8.5.0.0.0 | M2PA, MTP2 and MTP3 Timer Description, Default and Range values are not correct |
| 33073200 | 3 | 8.5.0.0.0 | Parameter value 2 configuration error on Common screening List |
| 33351566 | 3 | 8.5.0.0.0 | Issue with Remote Signaling Point Status GUI |
| 33405810 | 3 | 8.5.0.1.0 | Problems to provision Global Title Addresses (GTA) with hexadecimal digits |
| 33458522 | 3 | 8.5.0.2.0 | IDPR options changed by MMI and parameter in GUI does not show the change |
| 33468738 | 3 | 8.5.0.2.0 | Unable to export VSTP IDPR options from GUI screen |
| 33517159 | 3 | 8.5.0.2.0 | M2PA Data Ack and T7 timeout issues |
| 33545600 | 3 | 8.5.0.0.1 | SCCP Options table is not in the list of Export/Import Data |
| 33549355 | 3 | 8.5.0.0.0 | NPP Action Set not modifying in NPP Rule SET |
| 33554879 | 3 | 8.5.0.0.0 | MtpScreeningRule import fails |
| 32865170 | 4 | 8.5.0.0.0 | vSTP throttling action should throw configured TCAP error when “Return on Error” bit is ON |
SCEF
Table 7-3 SCEF Release 8.5.1.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 33523101 | 3 | 8.5.0.2.0 | ME Num of UE - JSON attribute requires correction as per 3GPP spec |
| 33582289 | 3 | 8.5.0.0.0 | SCEF_RDS:SCEF node reattempts not working correctly in case of T2 |
| 33562657 | 3 | 8.5.1.0.0 | SCEF_RDS:Incorrect error message in case of portUE values as 0 and |
| 33562644 | 3 | 8.5.1.0.0 | SCEF_RDS:Able to create NIDD context with RDS as True and rdsPo |
| 33562630 | 3 | 8.5.1.0.0 | SCEF_RDS:Incorrect response in case of -ve values are used with rds |
| 33562381 | 3 | 8.5.1.0.0 | SCEF_RDS:DSR Crash with abterm in case of -ve scenario |
| 33545972 | 3 | 8.5.1.0.0 | SCEF_RDS:Abterm observed while running RDS MT call |
| 33545407 | 3 | 8.5.1.0.0 | SCEF_RDS:Incorrect reliableDataService value in NIDD RDS SUBMIT response |
| 33534565 | 3 | 8.5.1.0.0 | SCEF_RDS:DSR process crash in case of ODR with NO RDS Frame |
| 33506588 | 3 | 8.5.1.0.0 | SCEF_RDS:Able to create NIDD Group context with RDS as True |
| 33469335 | 3 | 8.5.1.0.0 | SCEF_RDS:NIDD RDS Submit port validation NOT working |
| 33410867 | 3 | 8.5.1.0.0 | SCEF : Reliable Data Service handling for MT buffering |
| 33487739 | 3 | 8.5.1.0.0 | SCEF_RDS:reliableDataService is always False in Delete Response |
| 33482204 | 3 | 8.5.1.0.0 | SCEF: Reliable Data Service 3rd BCR Submission |
| 33478390 | 3 | 8.5.1.0.0 | SCEF_RDS:No Error raised in case of context creation with RDS False in SOAM and True in payload |
| 33464417 | 3 | 8.5.1.0.0 | SCEF_RDS:T8 Success for NIDD RDS context in case of context is part of NIDD Group and PDN exists without EPCO |
| 33463491 | 3 | 8.5.1.0.0 | DSR Process crash and abterms observed while sending 256 RDS port |
| 33415311 | 3 | 8.5.1.0.0 | SCEF: UE_REACHABILITY reporting needs correction (above base bug) |
| 33431624 | 3 | 8.5.1.0.0 | NIDD MT call test case with RDS flag disabled which is existing functionality is not working, observing it's value showing as True in logs |
| 33421063 | 3 | 8.5.1.0.0 | SCEF_RDS:Incorrect content in GET operation for RDS context |
| 33421046 | 3 | 8.5.1.0.0 | SCEF_RDS:Not able to configure RDS context with default RDS ports |
| 33410106 | 3 | 8.5.1.0.0 | SCEF: Reliable Data Service Feature Phase 1 - Second BCR |
| 33380540 | 3 | 8.5.1.0.0 | SCEF_RDS:MMI Guide RAML support is not available for RDS feature |
| 33380523 | 3 | 8.5.1.0.0 | SCEF_RDS:PUT/POST operation in apnconfigurationsets MO not supported to enable RDS |
| 33351972 | 3 | 8.5.1.0.0 | SCEF: Reliable Data Service Feature Phase 1 |
| 33419896 | 3 | 8.5.1.0.0 | SCEF: undecoded value in parameter edrxCycleLength |
| 33425763 | 3 | 8.5.0.2.0 | SCEF: Group MT NIDD Submit Response delay |
| 33421131 | 3 | 8.5.0.2.0 | SCEF: Crash on ME subscription with Type NUMBER_OF_UES_IN_AN_AREA |
| 31083226 | 4 | 8.5.0.0.0 | SCEF: Error during GET NIDD after increase in the data buffer value |
Customer Known Bug List
DSR 8.5.X
Table 7-4 lists the known bugs and associated Customer Impact Statements. This information is provided for information purposes only.
Table 7-4 DSR Release 8.5.X Customer Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 32911957 | 3 | 8.5 | IPv6: [Multi-Homing]: Traffic is NOT Auto-shifted to Primary XSI IP and Connection went down If Secondary IP is bring down via 'ifdown' command |
This issue is specific to the scenario when the eth interface on the VM is shutdown using "ifdown" command. Other scenarios of multihoming switching are working fine. Workaround: None |
| 28134563 | 3 | 8.3 | Auto Site Upgrade failure not cleaned up automatically, reupgrade attempt blocked |
If during Automated Site Upgrade, the upgrade on a server fails due to an issue like NTP failure or greater than 70% /var usage, the customer may observe a message, site already has an automated site upgrade in progress, stating upon trying to restart the upgrade. Workaround: Cancel the Site upgrade task from Main Menu: Status & Manage > Tasks > Active Tasks screen. Then, restart the upgrade. |
| 28353971 | 3 | 8.3 | OCSG does not validate special characters in ScsAsId delimiter |
If customers enter special characters in SCSASID_APN_Suffix_Delimiter in the OCSG console, the URL is rendered incorrectly. Workaround: APIGW user document will describe the constraint on the delimiter configuration parameter. |
| 28435966 | 3 | 8.3 | Invalid notification sent if DRR is with missing Absent-Subscriber-Diagnostic-T4 |
If an SMSC sends a DRR with invalid SM-Delivery-Outcome-T4 AVP value as '0' but missing 'Absent-Subscriber-Diagnostic-T4' AVP, the SCEF Notification report will not be correct. Notification report: Workaround: None |
| 28545072 | 3 | 8.3 | Duplicate OID name in DSR MIB (eagleXgDsrDbHealthImpactNotify) |
There is a duplicate name DbHealthImpact for different OIDs, which will cause an issue when trying to load the MIB file into the SNMP server. Workaround: In the MIB file, edit the OID name for the 31151 event from DbHealthImpact to DbHealthImpactPersist. |
| 26939388 | 3 | 8.2 | SDS Upgrade: NOAM Servers shall not switchover while Auditing is in progress |
None, if the documented workaround is followed. Workaround: NOAM upgrades are manual upgrade, and the documented procedure instructs the operator to look for the Audit clearance Alarm. |
| 26969222 | 3 | 8.2 | EVENT_NUMBER: 31000 GN_INTERN/WRN Upload failed [FileUploader.cxx:123] post 8.2 | Minimal impact is the problem that occurs. The alarm may cycle a few times and then clear after the system retries file transfer. This has only been observed in one test system and did not have a long-term impact on the system. |
| 27087175 | 3 | 8.2 | Device Deployment Failed alarms on IPFEs while upgrading from 7.1.1 to 8.2 |
In the unlikely event that the TPD provd server is down, and we happen to have a device edit pending, the edit will be blocked and an alarm is raised. (Bug title reflects an instance where this has happened once in the test cycle.) Workaround: Perform a trivial edit to the device; this will retry the edit operation with tpdprovd. |
| 27355369 | 3 | 8.2 | [8.2ST]: ERA process restart observed on NO while upgrading SDS 7.3 to 8.2 |
During the SDS upgrade, after the switchover from the primary cluster to the upgraded cluster, users provisioned data. Abterms were observed for a process, which monitors provisioning tables, however, the process is independent of provisioning.
Workaround: None. The issue occurred once in a partial upgraded system. There is no traffic impact on SDS. The affected process recovers from abterm automatically. |
| 27413746 | 3 | 8.2 | SNMP Trapping screen issues for SNMPv3 Engine ID field |
Users cannot view generated SNMPv3 Engine ID on the SNMP Trapping screen. Workaround: 1. Navigate to Configuration > Networking > Networks. 2. Check the default network name for NOAM/SOAM according to the requirement (for example, to configure SNMP trapping for the NOAM/SOAM server group, "XMI" is the default network name). 3. Execute the command:
ip link | grep -A1
<network name> | grep ether | awk '{print
$2}' on NOAM for NOAM SG and on SOAM for SOAM SG
where <network name> is text from step 2. The expected
output of the command is formatted like:
4. Remove all of the colons (:) from the output of step #3 and concatenate it after "800001430c" for the engine ID. For example: 800001430c022a84bc810c |
| 26710183 | 4 | 8.2 | RE when edited to remove the destination, should not be saved |
If an RE is edited and all destination are set to None, then any FABR queries to this particular RE will fail (ATTACH failures will be observed). Workaround: None. As a note: for any FABR query to pass, a valid destination must be assigned to an RE. |
| 27182197 | 4 | 8.2 | [8.2FT]: Domain ID field in filter gets disabled after filtering it once | In Main Menu: SDS > Configuration > Subscribers screen, after filtering on Domain ID, if the page is reloaded, the Domain ID text box is greyed out and disabled. |
| 26116286 | 3 | 8.1 | USBR update and concurrentupdate stackevent resets the creationTime to 0 | If any DCA application uses update API or concurrentUpdate API, the creation time of a USBR record will be reset to 0. So, the DCA application business logic cannot rely on the USBR record creation time. However, there is currently no requirement of DCA applications developed so far to use the record's creation time. |
| 26186891 | 3 | 8.1 | 8.1 VSTP-ST:Obs Routing fail events for UDTS msg without mentioning its UDTS | Minimal impact. The fix would help in debugging messages discarded at MTP3 due to routing failure. With fields currently reported in event 70064, users will not be able to differentiate whether UDT/XUDT or error message like UDTS/XUDTS. Additional fields will help in troubleshooting which messages are being discarded by MTP3 due to routing failure. |
| 26243446 | 3 | 8.1 | Information showing as green even though HostName is incorrect | No functional impact. Error text is displayed with a green background. |
| 26290407 | 3 | 8.1 | 8.1 Maj Upg NOAM "10134 Server upgrade operation failed", but upgrade succeeded | There will be a false alarm, but the upgrade will still be in progress. Upgrade progress can be verified from the Upgrade Screen. Moreover, Upgrade logs can be verified to see the progress of the upgrade. |
| 25573507 | 4 | 8.1 | [DSR SSST 8.1] IPFE validation missing in IPFE > Configuration > Options screen | If a wrong IP address is used, then TSA will not work. This will only happen when operator is configuring the IP address incorrectly. In field, operator shall use the correct IP address and verify the configuration before starting the traffic. |
| 25737480 | 4 | 8.1 | [DSR SSST 8.1]When we insert device, XSI IPv4 address replaces with IPv6 address. | Operators will not be able to add two devices at the same time |
| 26188293 | 4 | 8.1 | [DASH:P&C] DSR Dashboard PCA Avg Ing MPS instead reported as RxPdraMsgRate | The Dashboard screen does not include OCDRA MPS, it is showing only PDRA MPS. SBR Sessions under Servers tab SBR Sessions field is not including OCDRA Sessions count. |
| 26270776 | 4 | 8.1 | Process Util spikes seen for pingAllLivePeer and iptablesAdm |
This has no impact on the advertised performance figures. While testing the smallest VM resource profile, such as 4 vCPUs/8G RAM), we observed an anomaly wherein pingAllLivePeer, and iptablesAdm tasks result in CPU spikes. The bench-marked/ advertised MPS, that is, 6K RBAR MPS per DA-MP) has already considered these spikes and runs fine with this anomaly. |
| 26313885 | 4 | 8.1 | DSR 8.1:ST: Status & Manage > Files is not accessible from NO & throw error |
In NOAM and SOAM when there will be a large number of files present inside File Management Area (/var/TKLC/db/filemgmt) and the user clicks on "Status & Manage > Files" option on GUI for that server, then apwSoapServer will become slow as it will utilize the max CPU to sort the files in memory. This will impact the apwSoapserver functionality as well as that overall server performance. This is limited to OAM servers and will not impact Signaling Servers. This is a legacy issue.
This issue occurred because Remote Server Copy was not deleting the files after copying them to the remote server. A separate Bug will be raised to address this issue. |
| 24564563 | 3 | 8 | Network Devices added via GUI or MMI become "Discovered" on delete |
No operational impact. The issue is transient and clears on its own. Workaround: None. |
| 24796935 | 3 | 8 | [AW:oampAgent] "DB Late Write Nonactive" alarm by NO during Act->Stby transition |
No operational impact. Alarm may be triggerred when switchover of NOAM occurs. Workaround: None. |
| 25505595 | 3 | 8 | DSR 8.0:ST: InstallOS op on guests using PMAC failed with reason as internal err |
No impact to traffic. Filesystem full could prevent normal operations such upgrades or addition of new servers. The filesystem full condition was a result of an ISO being copied into an incorrect location (home/admusr). Workaround: Delete extra files that have been incorrectly copied to /home/admusr. This will clear the alarm and allow normal operation. |
| 25529974 | 3 | 8 | DSR MMI Issues in AppWorks MON URIs | None. Measurement budget is not currently enforced. |
| 25575141 | 3 | 8 | [PDRA:Recon] Disabling PDRA during USBR Recon fails with Error code 21648 | Users will not be able to disable PDRA function while running a reconfiguration plan for a USBR database. Users can disable function after all reconfiguration plans have been completed. |
| 25637633 | 3 | 8 | Unknown column 'ROLE' in 'where clause' |
Minimal impact as filter is not typically used for System OAM during upgrades. User will receive error "Unknown column 'ROLE' in 'where clause'", when filtering on Server Role "System OAM" through the Main Menu: Administration > Software Management > Upgrade screen. Workaround: Users can navigate to the desired System OAM tab to get the data. |
| 25651803 | 3 | 8 | [PCA:CACD] Alarm for Degraded ComAgent Conns when USBRs removed from Session RD |
No functional impact. Alarm is raised for servers that do not belong to the active Session SBR Database. Workaround: To clear the alarm, restart the SBR servers on which the alarm is raised. CAUTION: If any DCA application is actively sending data to these SBR servers, this workaround is NOT recommended as it may cause traffic loss. |
| 25656089 | 3 | 8 | DSR8.0:ST: ISO deployment got stuck for the site when servers got restarted |
During preparation for upgrade activity, if the user reboots a server while an ISO transfer is taking place, the transfer will be stopped and will not restart until a manual workaround is performed. Workaround: Contact My Oracle Support for assistance. |
| 25669402 | 3 | 8 | DSR 8.0:ST:VIPs not activated when servers are in same network but diff sites |
If all SOAM servers (different sites) are in the same network, users will not be able to access SOAM using VIP when spare SOAM server becomes active. Workaround: is available. |
| 25719122 | 3 | 8 | [PDRA:ApplRestart] psbr abterm can occur during controlled shutdown/restart | No service/traffic impact. An abterm may be generated during the process restart through GUI (Status&Manage > Server). |
| 25730821 | 3 | 8 | [ISBR:HaRes] SBRs may fail to de-register COMCOL Resources when removed from RDs |
No impact to traffic since this issue was observed on a decommissioned server group that is not a part of resizing plan. Also, there should be no operational impact as MOP source documentation has been updated to the required cleanup of decommissioned Servers and Server Groups. Workaround: If there are any Servers and Server Groups which are no longer being used after the completion of a Resizing plan, then the user should delete them. |
| 23421644 | 4 | 8 | [AW]Log In button not centered in the box at the Login Screen in Firefox browser | No operational impact. Cosmetic issue only. |
| 23858799 | 4 | 8 | Local Pause Update Inconsistent | No operational impact. On several GUI screens, there are two Pause Updates check boxes, one with scope global to the GUI and the other with a scope local to that menu item. |
| 24377541 | 4 | 8 | [Network Insert Screen]: VLAN ID field should not be mandatory | In the Main Menu > Networking > Networks [Insert] screen, users will need to populate the VLAN ID field with a value of 1-4094 regardless of whether used or not. |
| 24479659 | 4 | 8 | IPFE Target Set issue with BIE and gcli | Exported IPFE files cannot be used for import operations. |
| 24621473 | 4 | 8 | The SBR HA and HA health check scripts accessing tables instead of SOAP APIs. | No impact. |
| 24935222 | 4 | 8 | LRGSYS: KPI screen taking a long time to display |
Potential GUI delay. On large topologies, it can take up to 90 seconds to draw the KPI screen. Workaround: None. |
| 25028429 | 4 | 8 | DSR Backout: invalid response from User (yes vs. y) shouldn't abort CLI Session |
If users do not type y or N in response to, "Continue backout? [y/N]:", there is no reason given for the abort of the backout command. Workaround: The backout command can be re-entered. |
| 25379612 | 4 | 8 | IDIH : 80.17.2: OAM GUI showing extra Mediation input Sources |
No operational impact. Extra mediation source entries may be displayed. If the IDIH has ever been modified to retrieve data from another DSR SOAM, table entries for server hosts from the other SOAM will be displayed in IDIH OAM application screen Applications > DSR>"Mediation Input Sources". Workaround: Disregard hosts that no longer apply to the current configuration. |
| 25462998 | 4 | 8 | Pause update not functioning on Comm Agent Screens |
Minimal customer impact. The GUI status screens under "Communication Agent > Maintenance" will continue to update when a pause update check box is selected. |
| 25542610 | 4 | 8 | When NMS server added user may return to a screen with addtion not reported |
Update may not be reflected on GUI until it is manually refreshed. Workaround: None. Users need to navigate back to the desired screen rather than be automatically returned to it. |
| 25584247 | 4 | 8 | Misleading DCA Custom Event Template Throttling Description | Misleading 'Alarm Throttling Interval' description. Minimum value is incorrect. [Default = 60; Range = 0-300] should read [Default = 60; Range = 5-300]. |
| 25616683 | 4 | 8 | Capacity Summary screen constraints inconsistent with Online Help doc | Online help has an inaccuracy concerning max local nodes =32 instead of 48. |
| 25660736 | 4 | 8 | Backout: SOAM returns errors with verifyUpgrade and verifyBackout. |
The only impact is ERRORs may be returned when running verifyUpgrade and verifyBackout. The backout completes successfully. Workaround: None. The backout completes successfully. |
| 23132640 | 3 | 7.3 | [DSR7.3] Issues configurating/reconfiguring PCRF records |
If two sites are configured using the same SOAM Network Element, it is not possible to configure the same PCRF entry at both sites. Workaround: Use a different SOAM Network Element at each site. During the installation, it is possible to configure two SOAM Network Elements with different names and all of the same network configuration. |
| 29518322 | 3 | 8.4 | MIX of ANSI + ITUI traffic (72K for 8 MP¿s per site) is not able to run on my performance setup, whereas same amount of traffic for just ITUI domain is running fine. |
MIX traffic routing results in MSU failure, when running traffic is close to configured Link TPS.
Workaround:None |
| 29518100 | 3 | 8.4 | Few ITUI domain links got stuck in congestion level though I have reduced traffic to zero | When a linkset is pushed for more traffic routing, which triggers egress congestion, and if remains under this traffic stress, where links bounce due to congestion. Some Links get stuck in congestion levels though traffic gets reduced to zero. Here, Congestion level stuck links will never route egress traffic until they get reset. |
| 29531355 | 4 | 8.4 | STP8.4_GPORT_FT: MTSMSIMSI not taking ASDDN / ASDRNDN values | Resonse messages in case of GPORT cannot be encoded MTSMSIMSI as ASDDN and ASDRNDN. |
| 29408014 | 3 | 8.4 | On making the relativeCost value of Secondary entry same as relativeCost value of Primary entry, load sharing is not happening with respect to the weight. |
Load sharing will not occur correctly on changing to the same cost. This could cause an early onset of congestion due to not using all available paths to load share. Workaround: Reconfigure the MAP load sharing group by deleting the existing mapset group. Or, avoid put operation for changing RC. |
| 31860267 | 3 | 8.5 | R8.5_ST:Obsrvng VstpMsgDiscardDuetoCongestion discards during HA state change activity on MP |
Message discards/loss is observed when the vSTP MP is abruptly brought down manually during live traffic, by either changing the HA state of MP to OOS, or by disabling the vstp process at MP manually. Such operations are not recommended during normal vSTP MP operation. Workaround: None |
| 31757106 | 3 | 8.5 | vSTP_SIG: XCA and CBA message are not sent for ITUN24 domain |
SNM (Signalling Network Management) messages for ITUN24 domain will not work. ITUN24 domain traffic is running fine. For other domains, SNM messages are working fine. Workaround: None |
| 31757057 | 3 | 8.5 | [vSTP_SIG]: for ITUN24 domain, RST message is not sent when TFP message is received |
SNM (Signalling Network Management) messages for ITUN24 domain will not work. ITUN24 domain traffic is running fine. For other domains, SNM messages are working fine. Workaround: None |
| 31588873 | 3 | 8.5 | MP_Perf: Observed discards due to congestion with MTP screening traffic |
The MTP Screening with wild characters is heavy operation & consuming excessive CPU causing M3RL layer to congest. System shall limit TPS to 15K per MP when MTP3 Screening is turned ON. Workaround: Limit MTP3 Screening traffic to 15K TPS per vSTP MP for Gateway STP. No Impact for Non-Gateway deployments. |
| 32672994 | 3 | 8.5 | vSTP_SIG : During traffic at 100% TPS, links are getting down and not coming up |
M2PA links may go down some time when the traffic runs at the maximum MP capacity and does not recover automatically. Workaround: Disable and then enable the affected link from GUI/MMI to bring the link up. |
| 32573278 | 3 | 8.5 | 8.5.0.1_ST:Comagent connection gets deleted in case of UDR based traffic |
Comagent connections between vSTP and UDR go down for some time during high traffic scenarios. Transactions at vSTP MP may timeout and fail during such time when the connection is down with UDR. Workaround: None. The comagent connections recover automatically. |
| 31983406 | 3 | 8.5 | R8.5.0.1:VstpM3UAEventQueue alarms on intervstp M3UA links |
Queue alarms and congestion is observed while running 10K TPS traffic on one of the M3UA links. Workaround: None. Run lower than 10K TPS per M3UA link. |
| 33550855 | 4 | 8.5 | SCEF-T8-NIDD-API.yaml needs to be updated (NIDD Group Delivery) | No functional impact.
Workaround: None. |