1. Diameter Signaling Router Rx ShUDR Application User's Guide
  2. Configure RSA

4 Configure RSA

This section contains information about RSA and describes the procedures used to activate, configure, and deactivate RSA.
RSA uses the following tables for holding configuration values:
  • Rx_Client Table
  • PDNGWHost_PCRF_Mapping Table
  • Topology_Hiding Table
  • Error_Action_Config Table
  • System_Config_Options Table

Rx_Client Table

This is the first table Application lookup when Rx Initial message is received from client.

Figure 4-1 Rx_Client Provision Table

Rx_Client Provision Table

Figure 4-2 Rx_Client Provision Table Insert Screen

Rx_Client Provision Table Insert Screen

PDNGWHost_PCRF_Mapping Table

This table gets the PCRF address from PDNGW_Host received from HSS (Sh:UDA Response).

Figure 4-3 PDNGWHost_PCRF_Mapping table

PDNGWHost_PCRF_Mapping table

Figure 4-4 PDNGWHost_PCRF Provision Table Insert Screen

PDNGWHost_PCRF Provision Table Insert Screen

Topology_Hiding Table

This table is used when a AAA Response is reeived from PCRF, message generated from PCRF, message generated from Rx Client other than AAR Initial message for apply the topology hiding (replace the PCRF address with Pseudo FQDN).

Figure 4-5 Topology_Hiding table Provision Table

Topology_Hiding table Provision Table

Figure 4-6 Topology_Hiding Provision Table Insert Screen

Topology_Hiding Provision Table Insert Screen

Error_Action_Config Table

This table used when non success response is received from HSS (Sh:UDA Response from HSS) to map to AAA Response (Result code, Error Message, Vendor Id).

Figure 4-7 Error_Action_Config table Provision Table

Error_Action_Config table Provision Table

Figure 4-8 Error_Action_Config Provision Table Insert Screen

Error_Action_Config Provision Table Insert Screen

System_Config_Options Table

This table is used to configure system wide configuration that is used for Sh UDR message creation and sends the error response to Rx Client.

Figure 4-9 System Config Option table

System Config Option table

4.1 RSA Prerequisites

Before activating RSA as a DCA application, DCA framework must be activated on the NO. See Diameter Custom Applications Feature Activation Guide for detailed information.

After DCA framework activation, RSA can be activated.

Note:

After RSA is activated, by default, the application is in the disabled state. When disabled, no diameter traffic is delivered to RSA. See Diameter User’s Guide for the procedure to enable the application.

RSA’s operational status is unavailable until a successful compiled version (production or trial version) of RSA is configured.

4.2 Activating RSA

This procedure activates RSA. See Diameter Custom Applications Feature Activation Guide for detailed information.
  1. Ensure that the DCA framework is activated.
  2. Activate RSA using the DCA Application Activate procedure.
    1. Recommended DCA Short Name: RSA
    2. Recommended DCA Long Name: Rx ShUDR Application
  3. Post RSA activation, check the visibility of RSA subtree in the main menu DCA Framework, and then Diameter Security Application.
This procedure verifies that RSA is activated before enabling RSA and perform the provisioning activities.
  1. Confirm the RSA folder is visible on the GUI under the main menu DCA Framework.
  2. Check if all measurements and KPIs associated with the DCA framework are visible on the Measurements, and then Report and Status & Manage, and then KPIs screens.
After activation, RSA becomes visible across DSR (for example, ART and maintenance).

Note:

After activating DCA, the DCA framework allocates a default set of resources to it.

4.3 Configuring RSA Business Logic and Database Schema

This procedure imports RSA business logic and the configuration database schema using the RSA JSON file.

See DCA Programmer’s Guide for detailed information.

RSA NO JSON filename: Rx_ShUDR_Application-Version1.json

  1. From the NO GUI main menu, DCA Framework, and then Rx ShUDR Application, and then Application Control.
  2. Select the newly added RSA Version Name.
  3. Click Business Logic in the Import section of the Application Control page.
  4. Click Browse and select the Rx_ShUDR_Application-Version1.json file from the File upload screen.
  5. Mark the Abort on first error checkbox to abort the import process in case of error.
  6. Click Import to start the import process.

4.3.1 Verification

Perform the following steps to verify if the RSA JSON has successfully imported before enabling RSA and performing provisioning activities.
  1. From the NO GUI main menu, DCA Framework, and then Rx ShUDR Application, and then Application Control and ensure that an entry is added in DCA application version details table.
  2. Select the newly added version and click Config Tables and Data.
  3. Ensure that all DSA configuration tables are listed.
  4. Select the newly added version and click Development Environment.
  5. Ensure that DSA Perl business logic is present.
This ensures that the RSA JSON has successfully imported.

4.4 Configuring RSA Mandatory Options

This procedure configures various RSA Mandatory Options.

  1. From the NO GUI main menu, DCA Framework, and then Rx ShUDR Application, and then General Options.
  2. Update Perl Subroutine for Diameter Request to process_request.
  3. Update Perl Subroutine for Diameter Answer to process_answer.
  4. Uncheck the Enable Opcodes Accounting option to disable opcode accounting.
  5. Click Apply.
You have successfully configured RSA mandatory options.

4.5 Configuring ART for RSA

ART rule is configured to route all Rx message to DCA Application (Rx ShUDR Application)

RSA processes ingress Rx Diameter messages received from foreign networks. For this:
  1. Create an ART to route all the Rx traffic to RSA.
  2. Assign the ART to all the foreign peers.

If you do not want to screen ingress diameter messages from a specific foreign peer, then skip the ART configuration for that peer.

RSA also processes egress diameter messages to send to a foreign network from a home network. For this:
  1. Create an ART to route only egress traffic from a home network toward a foreign network to RSA.
  2. Create an ART to route all the Rx Traffic based on Application ID.
  3. Assign the ART only to those home network peers that can send egress messages to a foreign network.

If you want to screen the diameter message using Rx ShUDR Application, then assign the ART to the home peers that can send egress messages to a foreign network.

4.6 Enabling RSA

This procedure enables RSA on the SO.

  1. Click Diameter, and then Maintenance, and then Applications.
  2. Select DCA_RSA entries you want to enable.
  3. Click Enable.
The selected DCA_RSA entries are enabled.

4.7 Disabling RSA

This procedure disables RSA on the SO.

  1. Click Diameter, and then Maintenance, and then Applications.
  2. Select DCA_RSA entries you want to disable.
  3. Click Disable.
The selected DCA_RSA entries are disabled.

4.8 Deactivating RSA

This procedure deactivates RSA.

Note:

You cannot deactivate RSA while a version of the respective application is still in the Production and/or Trial state.

RSA must be disabled on all MPs in the network and no ART rules should refer to RSA.

  1. Disable RSA for all the MPs from the SO GUI main menu, Diameter, and then Maintenance, and then Applications.
  2. Delete ART rules referring to RSA.
  3. Deactivate RSA using DCA Application Activate procedure in Diameter Custom Applications Feature Activation Guide.
RSA is deactivated.