Oracle Communications Policy Management Specify Gx and Rx ... · Oracle® COMMUNICATIONS Policy Management Work Instruction . Release 12.2 . Specify Gx and Rx Result Codes While No

Oracle® COMMUNICATIONS Policy Management Work Instruction

Release 12.2

Specify Gx and Rx Result Codes While No Binding Info

E82612-01 February 2017

E82612-01 Page 2 of 31

Copyright © 2017 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services except as set forth in an applicable agreement between you and Oracle.

MOS (https://support.oracle.com) is your initial point of contact for all product support and training needs. A representative at Customer Access Support (CAS) can assist you with MOS registration. Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html.

http://www.oracle.com/

https://support.oracle.com/

http://www.oracle.com/us/support/contact/index.html

E82612-01 Page 3 of 31

TABLE OF CONTENTS

1. CONTACTS AND CUSTOMER CARE ........................................................................................................... 4 1.1 ORACLE CUSTOMER CARE ................................................................................................................................ 4 1.2 ACRONYMS ....................................................................................................................................................... 5

2. PURPOSE AND SCOPE ..................................................................................................................................... 6 3. PROCEDURE TO ENABLE THE FEATURE................................................................................................. 8 4. BACKOUT PROCEDURE ............................................................................................................................... 26


E82612-01 Page 4 of 31

1. Contacts and Customer Care

1.1 Oracle Customer Care The Oracle Customer Care Center is your initial point of contact for all product support needs. A representative takes your call or email, creates a Customer Service Request (CSR) and directs your requests to the Oracle Technical Assistance Center (TAC). Each CSR includes an individual tracking number. Together with TAC Engineers, the representative will help you resolve your request. The Customer Care Center is available 24 hours a day, 7 days a week, 365 days a year, and is linked to TAC Engineers around the globe. Oracle TAC Engineers are available to provide solutions to your technical questions and issues 7 days a week, 24 hours a day. After a CSR is issued, the TAC Engineer determines the classification of the trouble. If a critical problem exists, emergency procedures are initiated. If the problem is not critical, normal support procedures apply. A primary Technical Engineer is assigned to work on the CSR and provide a solution to the problem. The CSR is closed when the problem is resolved. Oracle Technical Assistance Centers are located around the globe in the following locations: Oracle – Global

CAUTION: MOS (https://support.oracle.com) is your initial point of contact for all product support and training needs. A representative at Customer Access Support (CAS) can assist you with MOS registration. Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html.


https://support.oracle.com/

http://www.oracle.com/us/support/contact/index.html

E82612-01 Page 5 of 31

1.2 Acronyms

Acronym/Term Definition

AF Application Function CCA Credit-Control-Answer (CC-Answer) CCR Credit-Control-Request (CC-Request) AAR Authorize-Authenticate-Request AAA Authorize-Authenticate-Answer STR Session-Termination-Request STA Session-Termination-Answer PCEF Policy and Charging Enforcement Function RAR Re-Auth-Request (RA-Request) UDR User Data Repository DRA Diameter Routing Agent


E82612-01 Page 6 of 31

2. Purpose and Scope This feature allows MRA to respond as configured Result-Codes ( different from the default values ) when the MRA receives the supported Gx:CCR-U/CCR-T ; Rx:AAR-I/AAR-U/STR messages without corresponded DRA binding information. Currently without DRA binding information, the MRA is returning the following default Result-Codes –

Gx:CCA: Result-Code 0:5002 DIAMETER_UNKNOWN_SESSION_ID Gx:CCA: Result-Code 0:5012 DIAMETER_UNABLE_TO_COMPLY Gx:CCA:Result-Code 0:3002_DIAMETER_UNABLE TO DELIVER Rx:AAA: Result-Code 10415:5065 IP_CAN SESSION_NOT_AVAILABLE Rx:STA: Result-Code 0:5012 DIAMETER_UNABLE_TO_COMPLY Use Reference [3] and [4] for valid applicable configured Result Codes and CC/Rx-Request-Type respectively. The following MRA Configuration keys should first set to enable the feature -

(1) DIAMETERDRA.TopologyHiding.Enabled should be set to “true”,

NOTE: An exception applied to Rx:AAR-I message regardless of the setting for this Configuration Key.

(2) And, DIAMETERDRA.TopologyHiding.Apps could contain values of “Gx,Rx”, OR either “Gx” or “Rx”, OR “*” for all

Next, in order to override the above-mentioned default returned Result-Codes , configure the following MRA Configuration Keys:

(1) DIAMETERDRA.NoBindingInfo.ResultCodeRuleIndexLimit – default value is 10. The value of this configuration is to limit the maximum number of Rules’ index as shown in the next Configuration Key in (2) below. Any Rule index number exceeds the RuleIndexLimit value, will NOT be executed. In other words, if the default limit value of 10 is configured, the RuleIndexNumber of 11 and beyond, won’t have any effect.

(2) DIAMETERDRA.NoBindingInfo.ResultCodeRulePrefix – applicable for all received Gx and Rx:STR messages. The value of this is the prefix of configuration’s key which is used to specify the Result Code rules containing one Filter prefix and one Action prefix with the following formats –

– [Prefix][IndexNumber].filter=App/MessageType/AVPList. Use Reference [4] and [5], Section 8.3 and Section 5.6.5 respectively.

– [Prefix][IndexNumber].action=VendorId:DiameterResultCode. Use Reference [3], Section 7.1

As shown in the following configuration example – DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Filter=Gx/CCR/CC-Request-Type=2

DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Action=0:5007 DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Filter=Gx/CCR/CC-Request-Type=3

DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Action=10415:5141


E82612-01 Page 7 of 31

DIAMETERDRA.NoBindingInfo.ResultCodeRule3.Filter=Rx/AAR/Rx-Request-Type=0 DIAMETERDRA.NoBindingInfo.ResultCodeRule3.Action=10415:5064

DIAMETERDRA.NoBindingInfo.ResultCodeRule4.Filter=Rx/AAR/Rx-Request-Type=1 DIAMETERDRA.NoBindingInfo.ResultCodeRule4.Action=99999:9999

DIAMETERDRA.NoBindingInfo.ResultCodeRule5.Filter=Rx/STR1

DIAMETERDRA.NoBindingInfo.ResultCodeRule5.Action=98765:1234 1Exception – just App/MessageType format. Refer RFC-4006, Section 8.3 for CC-Request-Types AVP Refer ETSI TS 129.214 V11.6.0, Section 5.3.31 for Rx-Request-Types AVP

(3) DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithDestinationHost – applicable for received Rx:AAR with Destination-Host AVP from AF ( P-CSCF) without Rx-Request-Type AVP.

(4) DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithoutDestinationHost - applicable for received Rx:AAR without Destination-Host AVP from AF ( P-CSCF) and without Rx-Request-Type AVP.


E82612-01 Page 8 of 31

3. Procedure To Enable The Feature

Pre-Enable Verification Steps Step Action Expected Results Pass | Fail

1 Verify MRA Subscriber Indexing configuration

CMP GUI: MRA Configuration ( Select MRA cluster name ) MRA Modify Subscriber Indexing

• Click on the “MRA association page name” as in the example shown below

• And, ensure that MRA Subscriber Indexing is set accordingly as shown in the example below –

NOTE: The rest of configuration may differ depending on each Customer deployment setup. As for the Subscriber Indexing, at least one configured should suffice and not necessarily need be the exact configuration as shown in the above example.

2 Enable the DiameterDRA of Topology Hiding

CMP GUI: MRA Configuration ( Select MRA cluster name ) MRA Advanced Modify Service Overrides Add

• Set the “DIAMETERDRA.TopologyHiding.Enabled” configuration key to “true” as shown –


E82612-01 Page 9 of 31

• Click on “OK” to save the setting. • Continue to the bottom of the configuration screen and click on

“Save” for the new configuration to be pushed into the corresponded MRA cluster.

• Validate the configuration key has been successfully set as

shown below –

NOTE: The legend is just a statement and does not have any impact to the proper function of this Configuration Key. • Next, set the “DIAMETERDRA.TopologyHiding.Apps “

configuration key to “ Gx,Rx” as in the example shown below – in this case, both Gx & Rx applications are configured. It can also be configured for either Gx or Rx.

• Click on “OK” to save the setting. • Continue to the bottom of the configuration screen and click on

“Save” for the new configuration to be pushed into the


E82612-01 Page 10 of 31

corresponded MRA cluster.

• Validate the configuration key has been successfully set as shown below –

NOTE: The legend is just a statement and does not have any impact to the proper function of this Configuration Key. A “ *” value can also be used to include all Diameter Applications besides Gx and Rx as in the above example. • Repeat the above steps for the next MRA cluster(s).


E82612-01 Page 11 of 31

Enable Steps Step Action Expected Results Pass | Fail

1 Set the limit on the number of Overiding Result Codes.


• Set the

“DIAMETERDRA.NoBindingInfo.ResultCodeRuleIndexLimit” configuration key for maximum limit value of the expected Result Codes to be overriden. Default value is 10. In this example, the limit value entered is “5”

• Click on “OK” to save the setting. • Continue to the bottom of the configuration screen and

click on “Save” for the new configuration to be pushed into the corresponded MRA cluster.

• Validate the new configuration has been successfully set as shown below –

• Repeat the above steps for the next MRA cluster(s).


E82612-01 Page 12 of 31

2 Configure the Result Codes Rule Indices and Actions


• There are 5 overridden Result Codes to be configured as the following –

DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Filter=Gx/CCR/CC-Request-Type=2 DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Action=10415:5144 DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Filter=Gx/CCR/CC-Request-Type=3 DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Action=10415:5141 DIAMETERDRA.NoBindingInfo.ResultCodeRule3.Filter=Rx/AAR/Rx-Request-Type=0 DIAMETERDRA.NoBindingInfo.ResultCodeRule3.Action=10415:5064 DIAMETERDRA.NoBindingInfo.ResultCodeRule4.Filter=Rx/AAR/Rx-Request-Type=1 DIAMETERDRA.NoBindingInfo.ResultCodeRule4.Action=99999:9999 DIAMETERDRA.NoBindingInfo.ResultCodeRule5.Filter=Rx/STR DIAMETERDRA.NoBindingInfo.ResultCodeRule5.Action=98765:1234

• The following is of initial configuration for DIAMETERDRA.NoBindingInfoResultCodeRule1.Filter prefix –

o Click on “OK” to save the setting. o As in previous steps, click on “Save” for the new

configuration to be pushed into the corresponded MRA cluster.

o Next, continue to add the DIAMETERDRA.NoBindingInfoResultCodeRule1.Action prefix as shown in the example below –

o Click on “OK” to save the setting. o As in previous steps, click on “Save” for the new


E82612-01 Page 13 of 31

configuration to be pushed into the corresponded MRA cluster as shown below for the completed of DIAMETERDRA.NoBindingInfoResultCodeRule1.Filter and DIAMETERDRA.NoBindingInfoResultCodeRule1.Action prefixes.

o Continue configuring for the next ResultCodeRule(x) Filter and Action, as previously stated.

• The completed configuration is shown below for the overriden Result Codes as intended -

NOTE: The legend is just an indication that the Configuration Key is dynamic and as expected.


3 Configure overridden Rx:AAR result code with Destination-Host AVP from AF


• Add the following Configuration Key of “DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithDestinationHost” as shown –


E82612-01 Page 14 of 31



• The completed configuration is as shown –


4 Configure overridden Rx:AAR result code without Destination-Host AVP from AF


• Add the following Configuration Key of “DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithoutDestinationHost” as shown –


E82612-01 Page 15 of 31



• The completed configuration is as shown –


5 <OPTIONAL> Validate the configuration via MRA CLI

• Log into Active MRA server of each configured cluster and perform the following CLI as shown below –

[root@brbg-mra-1b ]# /opt/camiant/mra/bin/mramgr

MraMgr> show cfgs DIAMETERDRA*

DIAMETERDRA.Enabled=true

DIAMETERDRA.Identity=brbg-mra-1.oracle.com


E82612-01 Page 16 of 31

DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithDestinationHost=0:5999

DIAMETERDRA.NoBindingInfo.ResultCodeForRxAARWithoutDestinationHost=10415:5990


DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Filter=Gx/CCR/CC-Request-Type=2


DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Filter=Gx/CCR/CC-Request-Type=3


DIAMETERDRA.NoBindingInfo.ResultCodeRule3.Filter=Rx/AAR/Rx-Request-Type=0


DIAMETERDRA.NoBindingInfo.ResultCodeRule4.Filter=Rx/AAR/Rx-Request-Type=1


DIAMETERDRA.NoBindingInfo.ResultCodeRule5.Filter=Rx/STR

DIAMETERDRA.NoBindingInfo.ResultCodeRuleIndexLimit=5

DIAMETERDRA.PCEF.GxLiteEnabled=true

DIAMETERDRA.Port=3868

DIAMETERDRA.Realm=oracle.com

DIAMETERDRA.Sctp.Enabled=false

DIAMETERDRA.TopologyHiding.Apps=Gx,Rx

DIAMETERDRA.TopologyHiding.Enabled=true


E82612-01 Page 17 of 31

Post-Enable Verification Steps

Step Action Expected Results Pass | Fail

1. Create the DRA binding

• Establish Gx session with initial CCR-I sent to MRA, and note the Session-id.

Diameter Message: CCR Version: 1 Msg Length: 592 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = INITIAL_REQUEST (1) CC-Request-Number (415,M,l=12) = 0 Diameter Message: CCA Version: 1 Msg Length: 676 Cmd Flags: PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Result-Code (268,M,l=12) = DIAMETER_SUCCESS (2001) Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = INITIAL_REQUEST (1)

• Log into active MRA server and perform the following CLI to view the DRA binding table as in the example below –

MraMgr> show dra binding |Number | UserId(s) | ServerId | IsSuspect | |-----------|--------------------------------------------------|----------------------------------|---------------| | 0 | IP:30.0.0.1| brbg-mpe-2.oracle.com| false | | | IMSI:555661114440001 | | | | | SESSID:hh_pgw;1460487609;0| | | Number of matching bindings found: 1 NOTE: In this example above, the MRA Subscriber Indexing is set for IPv4 Framed-IP, IMSI and Session-id. If others such as E.164 ( MSISDN) are set, they would also be listed in that table, provided the PCEF ( PGW) supports


E82612-01 Page 18 of 31

that indexing as well.

2. Simulate the lost of DRA binding

• Manually delete the designated binding record for the previously noted Gx Session-id as in this example -

MraMgr> delete dra binding SESSID:hh_pgw;1460487609;0 • Ensure that the binding record is no longer shown in the table.

MraMgr> show dra binding SESSID:hh_pgw;1460487609;0 |Number | UserId(s) | ServerId | IsSuspect | |-----------|-------------------------------------------------|----------------------------|---------------| No matching bindings found.

NOTE: This scenario case of binding lost applicable to the rest of test steps below

3. Send Gx:CCR-U for the previous Session-id

Diameter Message: CCR Version: 1 Msg Length: 172 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663568 End-To-End-Id: 3768657353 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = UPDATE_REQUEST (2) CC-Request-Number (415,M,l=12) = 1 Destination-Host (293,M,l=29) = brbg-mra-1.oracle.com

4. Verify the overridden Diameter Result Codes in the Gx:CCA-U

• Without this feature enabled, the Gx:CCA-U would respond with the default Result code of “DIAMETER_UNABLE_TO_DELIVER (3002) “

RECAP: This feature is enabled with the following overridden ResultCodes for Gx:CCR-U applicable for this test.

DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Filter=Gx/CCR/CC-Request-Type=2 DIAMETERDRA.NoBindingInfo.ResultCodeRule1.Action=10415:5144 • Ensure that the following overridden Result Code matches to the

above-mentioned configuration.

Vendor-id = 10415 ( 3GPP) Result-Code = 5144 ( Experimental ) Diameter Message: CCA Version: 1


E82612-01 Page 19 of 31

Msg Length: 168 Cmd Flags: PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 4247805854 End-To-End-Id: 4227463176 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Experimental-Result (297,M,l=32) = DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED (3GPP,5144) Vendor-Id (266,M,l=12) = 10415 Experimental-Result-Code (298,M,l=12) = 5144 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = UPDATE_REQUEST (2) CC-Request-Number (415,M,l=12) = 1

5. Send Gx:CCR-T for the previous Session-id

Diameter Message: CCR Version: 1 Msg Length: 172 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 846333967 End-To-End-Id: 2252261314 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = TERMINATION_REQUEST (3) CC-Request-Number (415,M,l=12) = 1 Destination-Host (293,M,l=29) = brbg-mra-1.oracle.com

6. Verify the overridden Diameter Result Codes in the Gx:CCA-T

• Without this feature enabled, the Gx:CCA-T would respond with the default Result code of “DIAMETER_UNABLE_TO_DELIVER (3002) “

RECAP: This feature is enabled with the following overridden ResultCodes for Gx:CCR-U applicable for this test.

DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Filter=Gx/CCR/CC-Request-Type=3 DIAMETERDRA.NoBindingInfo.ResultCodeRule2.Action=10415:5141 • Ensure that the following overridden Result Code matches to the


Vendor-id = 10415 ( 3GPP) Result-Code = 5141 ( Experimental ) Diameter Message: CCA Version: 1 Msg Length: 168 Cmd Flags: PXY


E82612-01 Page 20 of 31

Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 846333967 End-To-End-Id: 2252261314 Session-Id (263,M,l=27) = hh_pgw;1460487609;0 Experimental-Result (297,M,l=32) = DIAMETER_ERROR_TRIGGER_EVENT (3GPP,5141) Vendor-Id (266,M,l=12) = 10415 Experimental-Result-Code (298,M,l=12) = 5141 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = TERMINATION_REQUEST (3) CC-Request-Number (415,M,l=12) = 1

7. Send Rx:AAR without Destination Host and without Auth-Request-Type AVP

• Send AF Rx:AAR to the MRA under test without Destination Host as shown in

this example.

Diameter Message: AAR Version: 1 Msg Length: 444 Cmd Flags: REQ,PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2029023702 End-To-End-Id: 2450871420 Session-Id (263,M,l=27) = HH_AF;1460652250;8 Origin-Host (264,M,l=13) = HH_AF Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236 Destination-Realm (283,M,l=18) = oracle.com Media-Component-Description (517,VM,v=10415,l=28) = Media-Component-Number (518,VM,v=10415,l=16) = 0 Media-Component-Description (517,VM,v=10415,l=240) = Media-Component-Number (518,VM,v=10415,l=16) = 1 Media-Sub-Component (519,VM,v=10415,l=116) = Flow-Number (509,VM,v=10415,l=16) = 1 Flow-Description (507,VM,v=10415,l=55) = permit in 17 from 10.0.0.1 to 10.0.0.2 6024 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) Max-Requested-Bandwidth-UL (516,VM,v=10415,l=16) = 129000 AF-Application-Identifier (504,VM,v=10415,l=16) = voip Media-Type (520,VM,v=10415,l=16) = APPLICATION (3) Max-Requested-Bandwidth-DL (515,VM,v=10415,l=16) = 500 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) RS-Bandwidth (522,VM,v=10415,l=16) = 123 RR-Bandwidth (521,VM,v=10415,l=16) = 321 Subscription-Id (443,M,l=44) = Subscription-Id-Type (450,M,l=12) = END_USER_IMSI (1) Subscription-Id-Data (444,M,l=23) = 555661114440001 Reservation-Priority (458,V,v=13019,l=16) = PRIORITY_ONE (1)

8. Verify the overridden Diameter Result

• Without this feature enabled, the Rx:AAA would respond with


E82612-01 Page 21 of 31

Codes in the Rx-AAA

the default Result code of “IP_CAN SESSION_NOT_AVAILABLE

(5065) “

RECAP: This feature is enabled with the following overridden ResultCodes

• Ensure that the following overridden Result Code matches to the


Diameter Message: AAA Version: 1 Msg Length: 144 Cmd Flags: PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2029023702 End-To-End-Id: 2450871420 Session-Id (263,M,l=27) = HH_AF;1460652250;8 Experimental-Result (297,M,l=32) = UNKNOWN (v=10415,5990) Vendor-Id (266,M,l=12) = 10415 Experimental-Result-Code (298,M,l=12) = 5990 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236

9. Send Rx:STR • Send AF Rx:STR to the MRA under test with the configured indexing such as IMSI based, in this example –

Diameter Message: STR Version: 1 Msg Length: 160 Cmd Flags: REQ,PXY Cmd Code: 275 App-Id: 16777236 Hop-By-Hop-Id: 2029023703 End-To-End-Id: 2450871421 Session-Id (263,M,l=26) = HH_AF;1460652250;8 Origin-Host (264,M,l=13) = HH_AF Origin-Realm (296,M,l=18) = oracle.com Destination-Realm (283,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236 Destination-Host (293,M,l=29) = brbg-mra-1.oracle.com Termination-Cause (295,M,l=12) = DIAMETER_LOGOUT (1)


E82612-01 Page 22 of 31

10. Verify the overridden Diameter Result Codes in the Rx:STA

• Without this feature enabled, the Rx:AAA-I would respond with the default Result code of “DIAMETER_UNABLE_TO_DELIVER (3002) “


• Ensure that the following overridden Result Code matches to the above-mentioned configuration.

Diameter Message: STA Version: 1 Msg Length: 132 Cmd Flags: PXY Cmd Code: 275 App-Id: 16777236 Hop-By-Hop-Id: 2029023703 End-To-End-Id: 2450871421 Session-Id (263,M,l=26) = HH_AF;1460652250;8 Experimental-Result (297,M,l=32) = UNKNOWN (v=98765,1234) Vendor-Id (266,M,l=12) = 98765 Experimental-Result-Code (298,M,l=12) = 1234 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com

11. Send Rx:AAR-Update

• Send AF Rx:AAR to the MRA under test with the configured indexing such as IMSI based, in this example –

Diameter Message: AAR Version: 1 Msg Length: 460 Cmd Flags: REQ,PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2737402891 End-To-End-Id: 4000264508


E82612-01 Page 23 of 31

Session-Id (263,M,l=26) = HH_AF;1460663553;0 Origin-Host (264,M,l=13) = HH_AF Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236 Destination-Realm (283,M,l=18) = oracle.com Media-Component-Description (517,VM,v=10415,l=28) = Media-Component-Number (518,VM,v=10415,l=16) = 0 Media-Component-Description (517,VM,v=10415,l=240) = Media-Component-Number (518,VM,v=10415,l=16) = 1 Media-Sub-Component (519,VM,v=10415,l=116) = Flow-Number (509,VM,v=10415,l=16) = 1 Flow-Description (507,VM,v=10415,l=55) = permit in 17 from 10.0.0.1 to 10.0.0.2 6024 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) Max-Requested-Bandwidth-UL (516,VM,v=10415,l=16) = 129000 AF-Application-Identifier (504,VM,v=10415,l=16) = voip Media-Type (520,VM,v=10415,l=16) = APPLICATION (3) Max-Requested-Bandwidth-DL (515,VM,v=10415,l=16) = 500 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) RS-Bandwidth (522,VM,v=10415,l=16) = 123 RR-Bandwidth (521,VM,v=10415,l=16) = 321 Subscription-Id (443,M,l=44) = Subscription-Id-Type (450,M,l=12) = END_USER_IMSI (1) Subscription-Id-Data (444,M,l=23) = 555661114440001 Reservation-Priority (458,V,v=13019,l=16) = PRIORITY_ONE (1) Rx-Request-Type (533,V,v=10415,l=16) = UPDATE_REQUEST (1)

12. Verify the overridden Diameter Result Codes in the Rx:AAA

• Without this feature enabled, the Rx:AAA would respond with the default Result code of “DIAMETER_UNABLE_TO_DELIVER (3002) “



Diameter Message: AAA Version: 1


E82612-01 Page 24 of 31

Msg Length: 144 Cmd Flags: PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2737402891 End-To-End-Id: 4000264508 Session-Id (263,M,l=26) = HH_AF;1460663553;0 Experimental-Result (297,M,l=32) = UNKNOWN (v=99999,9999) Vendor-Id (266,M,l=12) = 99999 Experimental-Result-Code (298,M,l=12) = 9999 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236

13. Send Rx:AAR-Initial

• Send AF Rx:AAR to the MRA under test with the configured indexing such as IMSI based, in this example –

Diameter Message: AAR Version: 1 Msg Length: 460 Cmd Flags: REQ,PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2737402893 End-To-End-Id: 4000264510 Session-Id (263,M,l=26) = HH_AF;1460663553;2 Origin-Host (264,M,l=13) = HH_AF Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236 Destination-Realm (283,M,l=18) = oracle.com Media-Component-Description (517,VM,v=10415,l=28) = Media-Component-Number (518,VM,v=10415,l=16) = 0 Media-Component-Description (517,VM,v=10415,l=240) = Media-Component-Number (518,VM,v=10415,l=16) = 1 Media-Sub-Component (519,VM,v=10415,l=116) = Flow-Number (509,VM,v=10415,l=16) = 1 Flow-Description (507,VM,v=10415,l=55) = permit in 17 from 10.0.0.1 to 10.0.0.2 6024 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) Max-Requested-Bandwidth-UL (516,VM,v=10415,l=16) = 129000 AF-Application-Identifier (504,VM,v=10415,l=16) = voip Media-Type (520,VM,v=10415,l=16) = APPLICATION (3) Max-Requested-Bandwidth-DL (515,VM,v=10415,l=16) = 500 Flow-Status (511,VM,v=10415,l=16) = ENABLED (2) RS-Bandwidth (522,VM,v=10415,l=16) = 123 RR-Bandwidth (521,VM,v=10415,l=16) = 321 Subscription-Id (443,M,l=44) = Subscription-Id-Type (450,M,l=12) = END_USER_IMSI (1) Subscription-Id-Data (444,M,l=23) = 555661114440001 Reservation-Priority (458,V,v=13019,l=16) = PRIORITY_ONE (1) Rx-Request-Type (533,V,v=10415,l=16) = INITIAL_REQUEST (0)

14. Verify the overridden Diameter Result

• Without this feature enabled, the Rx:AAA would respond with the default Result code of “DIAMETER_UNABLE_TO_DELIVER (3002) “


E82612-01 Page 25 of 31

Codes in the Rx:AAA



Diameter Message: AAA Version: 1 Msg Length: 144 Cmd Flags: PXY Cmd Code: 265 App-Id: 16777236 Hop-By-Hop-Id: 2737402893 End-To-End-Id: 4000264510 Session-Id (263,M,l=26) = HH_AF;1460663553;2 Experimental-Result (297,M,l=32) = DUPLICATED_AF_SESSION (3GPP,5064) Vendor-Id (266,M,l=12) = 10415 Experimental-Result-Code (298,M,l=12) = 5064 Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777236


E82612-01 Page 26 of 31

4. Backout Procedure

Disable the Feature Step Action Expected Results Pass | Fail 1. Remove all the

configured overridden Result Codes Rule Indices and Actions

CMP GUI: MRA Configuration ( Select MRA cluster name ) MRA Advanced Modify Service Overrides Delete

• Highlight the configuration key and click on the “X Delete” button as shown in the example below –

• Continue with clicking on the second “Delete” button to remove it.

• Follow the above steps for the rest of Rule Indices and Actions. • Once done, click on the “save” button to save the new setting

as shown –

• Continue the above steps for the next MRA cluster(s).


E82612-01 Page 27 of 31

2. Disable/Remove the DiameterDRA TopologyHiding

CMP GUI: MRA Configuration ( Select MRA cluster name ) MRA Advanced Modify Service Overrides Edit / Delete

• Highlight the configuration key of “DIAMETERDRA.TopologyHiding.Enabled” and either click on the “X Delete” or “ Edit” button as shown in the example below

• If “Edit” button is chosen, set the value to “false” to

disable it as shown in the example below -

• If “Delete” button is chosen, click it to remove the configuration.

• Ensure that the Configuration Key is removed and continue by clicking on the “save” button as shown in the example below –


E82612-01 Page 28 of 31

• Continue the above steps for the next MRA cluster(s).

NOTE: The configuration key of “ DIAMETERDRA.NoBindingInfo.ResultCodeRuleIndexLimit“ and “DIAMETERDRA.TopologyHiding.Apps” will have no effect once the ““DIAMETERDRA.TopologyHiding.Enabled” configuration key is either disabled or removed. If necessary, it can be removed as well.

3. <OPTIONAL> Validate the configuration via MRA CLI

• Log into Active MRA server of each configured cluster and perform the following CLI as shown below –

[root@brbg-mra-1b ]# /opt/camiant/mra/bin/mramgr

MraMgr> show cfgs DIAMETERDRA*

DIAMETERDRA.Enabled=true

DIAMETERDRA.Identity=brbg-mra-1.oracle.com

DIAMETERDRA.PCEF.GxLiteEnabled=true

DIAMETERDRA.Port=3868

DIAMETERDRA.Realm=oracle.com

DIAMETERDRA.Sctp.Enabled=false

DIAMETERDRA.TopologyHiding.Apps=Gx,Rx

DIAMETERDRA.NoBindingInfo.ResultCodeRuleIndexLimit=5

DIAMETERDRA.TopologyHiding.Enabled=false NOTE: In the above output, it’s the case which those Configuration Keys are for future use if needed. Otherwise, those Keys highlighted in red will not be shown as completely removed from the MRA configuration.

Disable Verification Steps Step Action Expected Results Pass | Fail

1 Verify MRA Subscriber Indexing configuration

CMP GUI: MRA Configuration ( Select MRA cluster name ) MRA Modify Subscriber Indexing

• Click on the “MRA association page name” as in the example shown below


E82612-01 Page 29 of 31

• And, ensure that MRA Subscriber Indexing is still set accordingly as shown in the previous example below –

NOTE: The rest of configuration may differ depending on each Customer deployment setup.

2 Perform selective tests to validate the behavior with the feature disabled

• Create the DRA Binding by initial setup of Gx session as shown in this example –

• Establish Gx session with initial CCR-I sent to MRA, and note the Session-id.

Diameter Message: CCR Version: 1 Msg Length: 592 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = INITIAL_REQUEST (1) CC-Request-Number (415,M,l=12) = 0 Diameter Message: CCA Version: 1 Msg Length: 676 Cmd Flags: PXY Cmd Code: 272 App-Id: 16777238


E82612-01 Page 30 of 31

Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Result-Code (268,M,l=12) = DIAMETER_SUCCESS (2001) Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = INITIAL_REQUEST (1)

• Log into active MRA server and perform the following CLI to view the DRA binding table as in the example below –

MraMgr> show dra binding |Number | UserId(s) | ServerId | IsSuspect | |-----------|--------------------------------------------------|----------------------------------|---------------| | 0 | IP:30.0.0.1| brbg-mpe-2.oracle.com| false | | | IMSI:555661114440001 | | | | | SESSID: hh_pgw;1760497371;0| | | Number of matching bindings found: 1 NOTE: In this example above, the MRA Subscriber Indexing is set for IPv4 Framed-IP, IMSI and Session-id. If others such as E.164 ( MSISDN) are set, they would also be listed in that table, provided the PCEF ( PGW) supports that indexing as well.

• Simulate the lost of DRA binding by manually deleting as previously performed.

• Send Gx:CCR-U for the previous Session-id

Diameter Message: CCR Version: 1 Msg Length: 172 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = UPDATE_REQUEST (2) CC-Request-Number (415,M,l=12) = 1 Destination-Host (293,M,l=29) = brbg-mra-1.oracle.com

• Without the feature enabled, the expected CCA respond as the following –

Diameter Message: CCA Version: 1 Msg Length: 148


E82612-01 Page 31 of 31

Cmd Flags: PXY,ERR Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Result-Code (268,M,l=12) = DIAMETER_UNABLE_TO_DELIVER (3002) Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = UPDATE_REQUEST (2) CC-Request-Number (415,M,l=12) = 1

• Send Gx:CCR-T for the same previous Session-id

Diameter Message: CCR Version: 1 Msg Length: 216 Cmd Flags: REQ,PXY Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Origin-Host (264,M,l=14) = hh_pgw Origin-Realm (296,M,l=19) = tekelec.com Auth-Application-Id (258,M,l=12) = 16777238 Destination-Realm (283,M,l=18) = oracle.com CC-Request-Type (416,M,l=12) = TERMINATION_REQUEST (3) CC-Request-Number (415,M,l=12) = 2 Destination-Host (293,M,l=29) = brbg-mpe-3.oracle.com Subscription-Id (443,M,l=44) = Subscription-Id-Type (450,M,l=12) = END_USER_IMSI (1) Subscription-Id-Data (444,M,l=23) = 555661114440001

• Without the feature enabled, the expected CCA respond as the following –

Specify Diameter Message: CCA Version: 1 Msg Length: 148 Cmd Flags: PXY,ERR Cmd Code: 272 App-Id: 16777238 Hop-By-Hop-Id: 893663567 End-To-End-Id: 3768657352 Session-Id (263,M,l=27) = hh_pgw;1760497371;0 Result-Code (268,M,l=12) = DIAMETER_UNABLE_TO_DELIVER (3002) Origin-Host (264,M,l=29) = brbg-mra-1.oracle.com Origin-Realm (296,M,l=18) = oracle.com Auth-Application-Id (258,M,l=12) = 16777238 CC-Request-Type (416,M,l=12) = TERMINATION_REQUEST (3) CC-Request-Number (415,M,l=12) = 2


Documents

Oracle Communications Policy Management Specify Gx and Rx ... · Oracle® COMMUNICATIONS Policy Management Work Instruction . Release 12.2 . Specify Gx and Rx Result Codes While No