Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Diameter Peers (SRC CLI)


Use the following configuration statements to configure the Diameter peers:


When you commit the Diameter peer configuration, keep in mind the following conditions:

  • The origin host, remote peer address, or both should be specified for the Diameter peer.

  • If the enforce source address is configured for the Diameter peer, the remote peer address should be specified for the Diameter peer.

  • If the peer connection is configured to be in active mode for a particular Diameter peer or globally for all Diameter peers by using the active-peers option under the [edit system diameter] hierarchy, the remote peer address should be specified for the Diameter peers.

To configure the Diameter peer:

  1. From configuration mode, access the statements for the peer.

    The peer name must be unique.

  2. Specify the protocol for the transport connection.
  3. (Optional) Specify the addresses of the remote peer. If SCTP is the transport protocol, you can specify multiple addresses. If TCP is the transport protocol, you can specify only a single address.
  4. (Optional) Specify whether the remote peer must connect from one of the IP addresses listed by the address option.
  5. (Optional) Specify the local address of the peer.
  6. (Optional) Specify the maximum amount of time allowed for the Diameter peer to respond to a connection request.
  7. (Optional) Specify the watchdog timeout used for the connection to the remote peer.
  8. (Optional) Specify the Diameter state machine timeout.
  9. (Optional) Specify the time interval between connection attempts when the peer is in the disconnected state.
  10. (Optional) Specify the port for the client.
  11. (Optional) Specify the identifier for the endpoint that the peer presents during connection establishment.
  12. (Optional) Specify the number of messages allowed on the incoming message queue for a peer.
  13. (Optional) Specify whether the peer connection is in active mode.

    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.