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-2240029.1
Update Date:2017-04-05
Keywords:

Solution Type  Problem Resolution Sure

Solution  2240029.1 :   Policy Front Enf (PFE) Advanced Configuration Settings: DIAMETERDRA.MaxMsgSize  


Related Items
  • Oracle Communications Policy Management
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec Policy
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-14335586141>

Applies to:

Oracle Communications Policy Management - Version POLICY 11.5.0 to POLICY 12.2.0 [Release POLICY 11.0 to POLICY 12.0]
Information in this document applies to any platform.

Symptoms

 Diameter connection between MRA (PFE) and DRA is frequently disconnecting with error " DIAMETER.MaxMsgSize buffer size '32768' is too small "

Cause

 If MRA (PFE) receive Gx message (diameter packet ) more than 16384, which trigger DRA connection down.

(Which can happen even due to TCP combining/reassembling the Diameter packets)

Following Java error message is observed in mra.log. It can be search by keyword "MaxMsgSize" or "too small" in /var/camiant/log/mra.log*

#grep MaxMsgSize mra.log.0

2017-02-24 13:06:44.778 ERROR [Diameter.Selector:WorkerThread-1] camiant.diameter.DiameterProtocolDecoder.decode:140 - Serious error. The DIAMETER.MaxMsgSize buffer size '32768' is too small, need 37696, consider increase.Reading bytesToRead=37676 bytes bytesRead=20 bytes.
2017-02-24 15:05:18.105 ERROR [Diameter.Selector:WorkerThread-2] camiant.diameter.DiameterProtocolDecoder.decode:140 - Serious error. The DIAMETER.MaxMsgSize buffer size '16384' is too small, need 37680, consider increase.Reading bytesToRead=37660 bytes bytesRead=20 bytes.

Solution

There is a workaround for this issue

DIAMETERDRA.MaxMsgSize parameter is configurable on policy server which can solve the issue.

All the connections with the DRA needs to be re-connected, so that the new changes are effective. MRA Failover would be required so that the new value is pushed to all the connections with the DRA.

Following are the detailed steps:

Setting up the new configuration value:

On Configuration Management Platform (CMP) web GUI, click on MRA, Configuration and select the affected MRA and click  “MRA” tab, press “Advanced” key.
In “Other Advanced Configuration Settings”, press “Add” to add a new configuration setting.
A new window with the name “Add Configuration Key Value” will be shown. In “Configuration Key” text box, type “DIAMETERDRA.MaxMsgSize” and In “Value” text box, type “32768” and "Change Log" text box, type "Date or Reason for change"
Press “Save” button. (This adds a new configuration setting and changes the socket buffer size )
Scroll down and press “Save” button on the “Policy Server” tab as well. (Do not forget this otherwise this configuration will not be saved and will not be applied)
Go to “System” tab and press “Reapply Configuration” button.

 

Usually whenever the connection bounces, the new settings will be applied on the same.

Note: To avoid bouncing of the connections, a Failover of the MRA is required, so that all connections are disconnected and re-connected with the new settings.
 

References

<BUG:25597670> - DIAMETER.MAXMSGSIZE BUFFER SIZE '16384' IS TOO SMALL ERROR FOR MRA-DRA

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