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.0.0.0
The following table lists the resolved bugs in DSR 9.0.0.0.0 release.
Table 7-1 DSR 9.0.0.0.0 Resolved bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 35140336 | 2 | 9.0.0.0.0 97.13.0 | DSR process is getting crashed when setting the “VM:35K_MPS” DA-MP profile in ‘Profile Assignments’ table |
| 34790072 | 3 | 8.5.0.1.0 91.17.0 | Not able to add IP address in local node if local node is used in a disabled connection |
| 35004363 | 3 | 8.6 | DCA Exception feature countermeasure changes in 8.6.0.4 |
| 34944189 | 4 | 9.0.0.0.0-97.10.0 | Host-ip-address Avp is missing in CEA Error Response |
| 34333660 | 4 | 8.3 | Realm_imsi_consistancy check not working for exceptional case |
| 33758816 | 4 | 8.6 | DSD 1375 fix for Orig-Host Orig Realm value |
7.2.3 VNFM
The following table lists the resolved bugs in VNFM 6.0.0.0.0 release.
Table 7-2 VNFM Release 6.0.0.0.0 Resolved Bugs
| Bug Number | Severity | Found in Release | Title |
|---|---|---|---|
| 35221806 | 3 | VNFM-6.0 - VNFM Replication Routes are not getting added | |
| 35216237 | 3 | Scale Operation failing on a Stack which has been discovered using "Discover a VNF" API | |
| 34835812 | 3 | Getting wrong subnet error while deploying IDIH -8.2.3 on VNFM 6.0 | |
| 35205234 | 3 | VNFM - 6.0 - VNFM DSR and SDS Template Changes to fix IPv6 Route Issue | |
| 35239412 | 3 | VNFM - DSR Signaling cloud init failure due to root user login disable | |
| 33750684 | 4 | VNFM Uplift from OL7 to OL8 | |
| 35254589 | 4 | VNFM to support SNMP V3 for system alerts using Prometheus |
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.0.0.0.0
There are no DSR known bugs for DSR 9.0.0.0.0 release.
Release 8.6.0.4.0
There are no DSR known bugs for DSR 8.6.0.4.0 release.
Release 8.6.0.3.0
There are no DSR known bugs for DSR 8.6.0.3.0 release.
Release 8.6.0.2.0
The following table lists the DSR known bugs along with the customer impact statements for DSR 8.6.0.2.0 release.
Table 7-3 DSR 8.6.0.2.0 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 shuts down using "ifdown" command. Other scenarios
of multihoming switching are working fine.
Workaround: None |
| 28134563 | 3 | 8.3 | Auto Site Upgrade failure is not cleaned up automatically, resulting in reupgrade attempt | 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 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. |
| 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 upgrades, 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. |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 24621473 | 4 | 8 | The SBR HA and HA health check scripts accessing tables instead of SOAP APIs. | No impact. |
| 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. |
| 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. |
| 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. |
| 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. |
7.3.2 vSTP
Release 9.0.0.0.0
There are no known bugs for vSTP 9.0.0.0.0 release.
Release 8.6.0.4.0
There are no known bugs for vSTP 8.6.0.4.0 release.
Release 8.6.0.3.0
The following table lists the vSTP known bugs along with the customer impact statements for vSTP 8.6.0.3.0 release.
Table 7-4 vSTP 8.6.0.3.0 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 34903932 | 3 | 8.6 | vSTP Reassembly failure for XUDT Segmented packets with segments having optional parameter after TCAP | vSTP process can restart when such XUDT Segmented
packets are received that have segments with optional parameter after
TCAP portion.
Workaround is to disable the Reassembly/Segmentation feature of XUDT Class1 segmented packets. |
The following table lists the vSTP known bugs along with the customer impact statements for vSTP 8.6.0.2.0 release.
Table 7-5 vSTP 8.6.0.2.0 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 34693998 | 3 | 8.6.0.1.0 | Exporting the measurements while selecting Scope other than Network Element fails | Workaround: Export measurements with scope configured as 'Network Element' and any Server Group from the drop down menu. |
| 33884723 | 3 | 8.5.0.0.0 | vSTP: MRNSET update issue when MRNSET is modified during high traffic load | vSTP: MRNSET update issue when MRNSET is modified during
high traffic load.
Workaround: Perform the MRNSET configuration changes during maintenance window or when the traffic rate is not high. |
| 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. |
| 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. |
| 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. |
Release 8.6.0.1.0
The following table lists the vSTP known bugs along with the customer impact statements for vSTP 8.6.0.3.0 release.
Table 7-6 vSTP 8.6.0.1.0 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 34342490 | 3 | 8.6.0.0.0 | Issue with ordering of MTP screening rules during Bulk Import from GUI | Exporting the MO "MTP Screening Rules" into a csv
changes the order of rules in the exported file. So importing this
exported csv again will cause issues in MTP screening configuration.
Workaround: None. Do not use export/import for "MTP Screening Rules" MO. |
| 34342460 | 3 | 8.6.0.0.0 | Issue with MTP screening Import when rules are inter dependent | Exporting the MO "MTP Screening Rules" into a csv, and
then importing the csv again through GUI introduces some errors in the
screening rules in a specific scenario when the rules are
inter-dependent.
Workaround: None. Do not use export/import for "MTP Screening Rules" MO. |
| 33884723 | 3 | 8.5.0.0.0 | vSTP: MRNSET update issue when MRNSET is modified during high traffic load | vSTP: MRNSET update issue when MRNSET is modified during
high traffic load.
Workaround: Perform the MRNSET configuration changes during maintenance window or when the traffic rate is not high. |
| 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. |
| 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. |
| 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. |
Release 8.6.0.0.0
The following table lists the vSTP known bugs along with the customer impact statements for vSTP 8.6.0.3.0 release.
Table 7-7 vSTP 8.6.0.0.0 Known Bugs
| Bug Number | Severity | Found in Release | Title | Customer Impact |
|---|---|---|---|---|
| 34062266 | 3 | 8.6.0.0.0 | R8.6_vSTP: Random link toggling at 80% MP capacity with link busy parameter ON | In case vSTP receives an M2PA Link Busy message from
remote end at high link TPS traffic, then the M2PA link may go into
congestion and toggle.
Workaround: Turn the enhanced Link busy parameter OFF. |
| 33935352 | 3 | 8.6.0.0.0 | R8.6_vSTP:M2PA Links toggle observed when traffic is run for the first time after vstp process of MPs are restarted | When starting traffic on a link sometimes, if there are
initial traffic bursts or spikes, then the M2PA link may toggle. But it
recovers and stabilizes thereafter and there is no impact after the
initial toggle.
Workaround: None. |
| 33884723 | 3 | 8.5.0.0.0 | vSTP: MRNSET update issue when MRNSET is modified during high traffic load | vSTP: MRNSET update issue when MRNSET is modified during
high traffic load.
Workaround: Perform the MRNSET configuration changes during maintenance window or when the traffic rate is not high. |
| 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. |
| 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. |
| 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. |