Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2243178.1
Update Date:2017-03-14
Keywords:

Solution Type  Problem Resolution Sure

Solution  2243178.1 :   After Upgrade in SOAM GUI Egress Throttle Group Status Showing UNK  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Symptoms
Changes
Cause
Solution
 5.0
 6.0
 Workaround
References


Created from <SR 3-14285920161>

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 6.0 and later
Information in this document applies to any platform.

Symptoms

On the upgraded node, "Rate Limiting Operational Status" and "Rate Limiting Operational Reason" on "Diameter-> Maintenance->Egress Throttle Groups" are reported by SOAM with "UNK".

Changes

DSR Node was upgraded from 5.0.1-50.25.0 -> 6.0.2-60.37.0.

Cause

In DRL there are validity checks on EgressThrottleGrp values before storing them into RTDB The issue is EgressThrottleGrp value of rateAbateTime check failure at 6.0(Upgraded release) and not at 5.0 (Original release) which caused the CFG-DB failure issues.

Solution

There is a Bug 19115341-Incorporate recommendation from Egress Throttling tests: short term improvements.

As per the bug the value of DrlMinEtgAbateTime was changed from 200 (50.23) to 50 (50.25). But the merge to integration was done with (50.23) which doesn’t have this bug fix Similar bug fix has been done for 5.1 release Bug 19120288-Incorporate recommendation from Egress Throttling tests: short term improvements.

But this fix is not done for 6.0 Release which is why the upgrade release 6.0.2_60.37.0 does not have these changes.

DpiEgressThrottleGrp table values:

id=12 name=BSF_AH_00 birthTime=07/07/2016 13:13:52.000 rateAdminState=Enabled maxRate=100 rateOnsetThres1=85 rateOnsetThres2=90 rateOnsetThres3=95 rateAbateThres1=84 rateAbateThres2=89 rateAbateThres3=94 rateSmoothFactor=90 rateAbateTime=50 pendTransAdminState=Disabled maxPendTrans=0 pendTransOnsetThres1=0 pendTransOnsetThres2=0 pendTransOnsetThres3=0 pendTransAbateThres1=0 pendTransAbateThres2=0 pendTransAbateThres3=0 pendTransAbateTime=0 mcl=0

maxRate=100 rateOnsetThres1=85 rateAbateThres1=84 rateSmoothFactor=90 rateAbateTime=50 The check which doesn’t fail in 5.0 and fails in 6.0 is (rateAbateTime is less than DrlMinEtgAbateTime)

5.0

DrlMinimumEtgRate=100 DrlMaximumEtgRate=250000
DrlInvalidEtgThreshold=0
DrlMinEtgRateSmoothFactor=0 DrlMaxEtgRateSmoothFactor=95
DrlMinEtgAbateTime=50 DrlMaxEtgAbateTime=10000

6.0

DrlMinimumEtgRate=100 DrlMaximumEtgRate=250000
DrlInvalidEtgThreshold=0
DrlMinEtgRateSmoothFactor=20 DrlMaxEtgRateSmoothFactor=90
DrlMinEtgAbateTime=200 DrlMaxEtgAbateTime=10000

Workaround

As a workaround, the following needs to be done to make sure DRL accepts the ETG and SLDB and stop CFG-DB alarm wrt DRL ETG:

  1. Go to Diameter -> Configuration -> Egress Throttle Groups -> [Edit]
  2. Change rateAbateTime (Abatement Time) from 50 to 200 for EgressThrottle groups

References

<BUG:19120288> - [238351]INCORPORATE RECOMMENDATION FROM EGRESS THROTTLING TESTS: SHORT TERM IMPR
<BUG:19115341> - [238351]INCORPORATE RECOMMENDATION FROM EGRESS THROTTLING TESTS: SHORT TERM IMPR

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback