| Asset ID: |
1-71-2098569.1 |
| Update Date: | 2016-08-29 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2098569.1
:
Sy Transaction: DSR Longer Transferring Message For Particular Sy AppID - SLA Or STA Message.
| 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
Created from <SR 3-11120571151>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 5.0 and later
Information in this document applies to any platform.
Goal
DSR is used for transferred traffic between peers PCRF (x.x.x.x) and IN(y.y.y.y for Sy AppID. We’ve observe that DSR longer transferring message for particular Sy AppID - SLA or STA message.
Solution
The ACK message was delayed by ~99ms & 50 ms from the peer (x.x.x.x5) and DSR sent the next available packet immediately after receiving the ACK from peer. So delay was introduced from peer side not from DSR end.
Example#1 Analysis ==> ~50 ms delayed ACK (frame#358) from x.x.x.x5 (Peer) for STA sent from z.z.z.z (DSR) frame#322. This may be the reason DSR did not sent the next available TCP packet and finally sent after receiving the ACK in frame#360.
Example#2 Analysis ==> ~99 ms delayed ACK (frame#3313) from x.x.x.x (Peer) for STA sent from z.z.z.z (DSR) frame#3251. This may be the reason DSR did not sent the next available TCP packet and finally sent after receiving the ACK in frame#3315.
The Nagle algorithm has a known problem with delayed answers.
Please review the web pages below for a description of Nagle and delayed answers.
http://www.stuartcheshire.org/papers/nagledelayedack/
http://smallvoid.com/article/winnt-nagle-algorithm.html
http://blogs.technet.com/b/nettracer/archive/2013/01/05/tcp-delayed-ack-combined-with-nagle-algorithm-can-badly-impact-communication-performance.aspx
Attachments
This solution has no attachment
