Configuring Diameter Profile Endpoint on the Gx and Gy Interfaces
To configure the Diameter profile endpoint on the Gx and Gy interfaces, use the following sample configuration:
config
profile diameter-endpoint interface_name
name profile_name
internal-vip ip_address
destination-host-avp message_type
vsa-support vendorId-source
max-outstanding number_of_messages
response-timeout response_timeout_value
connection-timeout connection-timeout_value
basemsg retransmission-timeout retransmission_timeout_value
basemsg retransmissions max_retry_value
basemsg watchdog-interval interval_value
dscp [ dscp_value | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef ]
origin realm realm_name
origin host host_name address ipv4 ip_address
origin peer origin_peer_name
realm realm_name
address ipv4 ip_address
port peer_port
destination-host-name destination_host_name
load-balancing-algorithm highest-weight
route-entry host [ host-name | * ] realm [ realm-name | * ] peer peer_name weight weight_value
route-failure deadtime deadtime_value result-code result_code_value threshold number
route-failure result-code result_codes_value
route-failure threshold threshold_number
route-failure recovery-threshold percent recovery_threshold_percentage
dynamic-route expiry-timeout expiry_timeout_value
dynamic-origin-state-id boolean_value
exit
NOTES:
-
profile diameter-endpoint interface_name : Specify a Diameter profile for the Gx or Gy interface.
-
name profile_name : Specify the profile name of the Diameter profile interface. Each profile configures the Diameter source information and the peer information for the Diameter messages that go toward those peers.
NoteYou can define a maximum of 100 profiles per interface.
-
internal-vip ip_address : Specify an internal VIP IP address for communication with service pods. internal-vip is a mandatory parameter.
-
destination-host-avp message_type : Specify the type of message in which the destination host AVP is to be encoded.
NoteSMF supports only the always value for the message_type .
-
vsa-support vendorId-source : Specify the source of vendor IDs DIABASE to be used for negotiation of Diameter peer capabilities.
NoteSMF supports only the all-from-dictionary value for the vendorId-source .
-
max-outstanding number_of_messages : Specify the maximum number of Diameter messages to be sent to any peer in the profile, while awaiting the responses. The default value is 256. number_of_messages must be in the range of 1–4096.
-
response-timeout response_timeout_value : Specify the maximum allowed response time for request messages that the Diameter applications send to the Diameter server. The default value is 60. response_timeout_value must be in the range of 1–300.
-
connection-timeout connection-timeout_value : Specify the maximum allowed time for establishing the transport layer connectivity, such as the TCP connection, toward the Diameter server. The default value is 30. connection-timeout_value must be in the range of 1–300.
-
basemsg retransmission-timeout retransmission_timeout_value : Specify the timeout value between retransmissions of the base messages, such as Device Watchdog Request (DWR) and Capability Exchange Request (CER), toward the Diameter server. The default value is 30. retransmission_timeout_value must be in the range of 1–120.
-
basemsg retransmissions max-retries : Specify the maximum number of times the base messages must be retransmitted. The default value is 1. max-retries must be in the range of 1–10.
-
basemsg watchdog-interval interval_value : Specify the time interval between the two DWR messages that are sent toward the Diameter server. The default value is 30. interval_value must be in the range of 6–30.
-
dscp [ dscp_value | af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef ] : Specify the Differential Services Code Point (DSCP) value in the IP header of the Diameter messages that are sent toward the Diameter server. The default value is be . dscp_value must be in the range of 0–63. Choose in the following other DSCP values, as required:
-
af xx: Specify this value for the use of an assured forwarding xx per hop behavior (PHB).
-
be : Specify this value for the use of the best effort forwarding PHB. be is the default value.
-
cs x: Specify this value for the use of class selector x per PHB.
-
ef : Specify this value for the use of expedited forwarding PHB.
-
-
origin realm realm_name : Specify the name of the realm for the Diameter endpoint. This parameter is mandatory.
-
origin host host_name address ipv4 ip_address : Specify the host name, which is the FQDN of the Diameter endpoint. Specify the IPv4 address, which is the Diameter endpoint Bind IP address for the Diameter client connections.
-
origin peer origin_peer_name : Specify the identifier for a Diameter peer. This parameter is mandatory.
NoteYou can configure a maximum of 5000 peers.
-
realm realm_name : Specify the name of the realm for a peer with the name of the peer. This parameter is mandatory.
-
address ipv4 ip_address : Specify the IP address of the Diameter peer.
-
port peer_port : Specify the port of the Diameter peer. This parameter is mandatory.
-
destination-host-name destination_host_name: Specify the custom destination host name to be used in destination host AVP. This parameter is optional.
-
load-balancing-algorithm highest-weight : Choose an idle server with the highest weight in failure scenarios. If multiple servers have the same high weight, then the load balancing happens among those servers.
-
route-entry host [ host-name | * ] realm [ realm-name | * ] peer peer_name weight weight_value : Use this command to configure two static entries, such as a peer in the route table. If you configure an entry with the existing same flag, host, realm, then only the weight is updated with the higher of the two of them. The host and realm parameters allow wildcard character values. The weight is an optional parameter with the default value as 10. The peer is a mandatory parameter.
NoteYou can configure multiple route entries with the same host and realm but a different peer without being overridden.
-
route-failure deadtime deadtime_value result-code result_code_value threshold number : Specify the duration in seconds for which the system keeps the route in the FAILED status. After the configured duration expires, the system changes the status to AVAILABLE . deadtime_value must be an integer in the range of 1–86400. The default value is 60.
-
route-failure recovery-threshold percent recovery_threshold_percentage : Specify the percentage value at which the failure counter is reset when provisionally changing the status from FAILED to AVAILABLE . For example, a failure counter of 16 caused the AVAILABLE status to change to FAILED status. After the configured deadtime expires, the status changes to AVAILABLE . If you configured recovery_threshold_percentage with 75 percent, the failure counter resets to 12, which is 75 percent of 16. The default value is 90.
-
dynamic-route expiry-timeout expiry_timeout_value : Specify the expiration time for dynamic routes that you created after reaching the Diameter destination host. The default value is 86400 secs, which equals one day.
-
dynamic-origin-state-id boolean_value : Specify whether you want to enable or disable the dynamic origin state ID. The default value is true.
NoteAfter the configuration changes from dynamic to static, if the peer is started with either the dynamic origin state ID or the static origin state ID, the peer sends the default static value. Similarly, for a configuration change from the dynamic to static, the peer sends the dynamic value that the Diameter endpoint fetches from the cache pod. In this case, there’s a reconnection.