Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring the Diameter Application (SRC CLI)

 

You can configure the properties of the application, client, server, and logging destination of the SRC Diameter application.

Perform the following tasks to configure these properties:

Configuring the Diameter Application Properties

The SRC software supports Diameter application properties such as Juniper Networks Session Resource Control (JSRC) and southbound Gx interface. JSRC and southbound Gx interface communicate with the Service Activation Engine (SAE) (remote SRC peer).

Use the following configuration statements to configure the properties for the Diameter application:

To configure the Diameter application:

  1. From configuration mode, access the statement for the Diameter application.
    Note

    The java-* options have default values that should not be changed unless directed by Juniper Networks Technical Assistance Center (JTAC).

  2. If you encounter problems caused by lack of memory, change the maximum memory size available to the Java Runtime Environment (JRE).
  3. Configure the amount of space available to the JRE when the Diameter server starts.
  4. Configure the garbage collection functionality of the Java Virtual Machine.
  5. Specify the protocol for the transport connection.
  6. (Optional) Specify the local IP addresses that remote peers can use to reach this server.
  7. (Optional) Specify the port for the server.
  8. (Optional) Specify the fully qualified domain name (FQDN) used to identify this host to its Diameter peers.
  9. (Optional) Specify the realm used to identify this host to its Diameter peers.

    The Diameter realm should be configured to the domain name of the origin host. For example, if the FQDN of the host is host.juniper.net, then the realm should be juniper.net.

  10. (Optional) Configure the timeout value until which the Diameter server holds unsolicited requests such as Point to Point Protocol (PPP) and Abort Session Request (ASR), and waits for a matching response such as Push Profile Answer (PPA) and Abort Session Answer (ASA). The server discards the responses received after the specified time. The value range is 1–65,565 seconds. The preferred value is 10–30 seconds. By default, the value is set to 25 seconds.
    Note

    diameter-server-timeout and reply-timeout under the [edit shared sae group configuration driver] hierarchy should be configured with the same value.

  11. (Optional) Specify whether the peer connection is in active mode.
    Note
    • Active mode means that the SRC software actively tries to connect to the peer. Make sure the peer you are connecting to supports active peers. The MX Series router does not support active peers. The SRC software can still be configured, but the connection attempts will not work.

    • If the peer connection is configured to be in active mode, you must configure the remote peer address for all Diameter peers by using the address option under the [edit shared network diameter peer name] hierarchy.

  12. (Optional) Specify whether the peer connection is in debug mode.
  13. (Optional) Configure the load-balancing mode for peer selection when forwarding a request message.
  14. (Optional) Configure the log level for the transaction processing log.

    where log-level is one of the following:

    • log-no-messages—Do not log any messages.

    • log-severe-messages—Log only severe messages.

    • log-normal-messages—Log only normal messages.

    • log-debug-messages—Log only debug messages.

  15. (Optional) Configure the log level for the packet tracing log.

    where log-level is one of the following:

    • log-no-messages—Do not log any messages.

    • log-severe-messages—Log only severe messages.

    • log-normal-messages—Log only normal messages.

    • log-debug-messages—Log only debug messages.

  16. (Optional) Configure the log level for the peer state machine log.

    where log-level is one of the following:

    • log-no-messages—Do not log any messages.

    • log-severe-messages—Log only severe messages.

    • log-normal-messages—Log only normal messages.

    • log-debug-messages—Log only debug messages.

  17. (Optional) Configure the log level for the configuration log.

    where log-level is one of the following:

    • log-no-messages—Do not log any messages.

    • log-severe-messages—Log only severe messages.

    • log-normal-messages—Log only normal messages.

    • log-debug-messages—Log only debug messages.

Configuring the Diameter Client Properties

This procedure configures the client-side adapter of the SRC Diameter server, which handles client connections. Configuration should be necessary only if you encounter performance problems.

Use the following statements to configure the properties for the Diameter client:

To configure the Diameter client properties:

  1. From configuration mode, access the statement for the Diameter client.
  2. (Optional) Specify the number of threads to use.
  3. (Optional) Specify the time to wait for new commands.

Configuring the Diameter Server Properties

Use the following statements to configure the properties for the Diameter server:

To configure the Diameter server properties:

  1. From configuration mode, access the statement for the Diameter server.
  2. (Optional) Specify the minimum number of threads to use.
  3. (Optional) Specify the time to wait for new commands.

Configuring Logging Destinations

Use the following configuration statements to configure logging destinations for Diameter:

To configure logging destinations to store log messages in a file:

  1. From configuration mode, access the statement that configures the name and type of logging destination.
  2. Specify the properties for the logging destination.

    For more information about configuring properties for the logging destination, see Configuring Logging Destinations to Store Messages in a File (SRC CLI).

Related Documentation