Diameter Intelligence Hub (DIH/pDIH) Does Not Show Some Diameter Over SCTP Messages

Asset ID:	1-71-1959252.1
Update Date:	2016-06-09
Keywords:

Solution Type Technical Instruction Sure

Solution 1959252.1 : Diameter Intelligence Hub (DIH/pDIH) Does Not Show Some Diameter Over SCTP Messages

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 4.1 to DSR 5.1 [Release DSR 4.0 to DSR 5.0]
Information in this document applies to any platform.

Goal

If a 3rd party vendor is using non-standard Payload Protocol Identifiers (PPID) values when sending traffic via the Diameter Signaling Router (DSR), they may not be captured by the pDIH.

How can we accommodate a non-standard PPID value that will allow the iDIH to capture all messages?

Solution

The pDIH uses filters to control the types of messages to be captured. The existing parameters are not "incorrect", but do not include every possible value. That is why it is a filter.

The DIAMETER RFC recommendation is not to use the unspecified payload protocol identifier (value 0).

RFC 6733 Diameter Base Protocol October 2012
Section 2.1.1

A Diameter agent SHOULD use dedicated payload protocol identifiers
  (PPIDs) for clear text and encrypted SCTP DATA chunks instead of only
  using the unspecified payload protocol identifier (value 0). For
  this purpose, two PPID values are allocated: the PPID value 46 is for
  Diameter messages in clear text SCTP DATA chunks, and the PPID value
  47 is for Diameter messages in protected DTLS/SCTP DATA chunks.

The workaround consists of adding PPID value of 0, 9, 46, 47, 100.

Check the value being used by the vendor or in a pcap capture from PMF.

If it is using a value other than 46/47 contact Oracle Support.

Also ensure that all ports from trafic are defined at IP Transport layer of IxpBuild (Builder subscription).

Workaround procedure

Procedure below will remove PPID filter so that every PPID will pass through PMF:

Login into NSP VM as tekelec user
Copy the attached files into /tmp directory as “tekelec” user.
Verify that "tekelec" is the owner of the files:
[root@nsp tmp]# ll
-rw-r--r-- 1 tekelec tekelec 126 Jan 28 14:03 DisablePPID.sql
-rw-r--r-- 1 tekelec tekelec 126 Jan 28 14:03 EnablePPID.sql
Run the command:
sqlplus nsp/<passwod>@//IP_ORACLE/pic
sqlplus prompt should appear after running the command
Run sql script:
@/tmp/upgradePPIDScript.sql
Output of the command should be “1 row updated”
In NSP CCM, apply changes on PMF

Script can be downloaded here:

revertPPIDScript.sql can be used to enable PPID filter again.

Checks

Verify that frames are matching the newly added lines (between 56 and 62):

cat /proc/driver/pmia/filter_cnt

Before modification:

...
1 41 2584
1 42 1264
1 53 620556018
1 54 557983038
1 55 556990548
1 2047 61389
...

After modification:

...
1 41 18
1 42 8
1 53 6259615
1 54 5501178
1 55 5488733
1 56 198548
1 57 384
1 58 30
1 59 30
1 60 30
1 61 30
1 62 5488733
1 2047 439
...

Attachments

This solution has no attachment