Cisco Cisco Packet Data Interworking Function (PDIF)
Global Configuration Mode Commands (L-S)
▀ require diameter-proxy
▄ Command Line Interface Reference, StarOS Release 18
5518
facility
: This algorithm specifies that the Diameter proxy (endpoint) will be selected based
on the facility type. This is the default option. In this algorithm, all AAA endpoints will be
present in CPU 0 and all session manager endpoints will be present in CPU 1.
present in CPU 0 and all session manager endpoints will be present in CPU 1.
round-robin
: This algorithm specifies that the Diameter proxy selection will be in Round
Robin fashion. For example, if the number of proclets running per card is 2, the first
endpoint configured is associated with CPU 0 (proxy running in CPU 0 of the same card)
and the next endpoint configured will be associated with CPU 1, the third one with CPU 0
and fourth one with CPU1.
endpoint configured is associated with CPU 0 (proxy running in CPU 0 of the same card)
and the next endpoint configured will be associated with CPU 1, the third one with CPU 0
and fourth one with CPU1.
single [ diamproxy-per-card 2 ] [ algorithm { facility | round-robin } ]
Configures one Diameter proxy for the entire chassis.
Important:
The
[ diamproxy-per-card 2 ] [ algorithm { facility | round-
robin } ]
options are primarily applicable for ASR 5500 DPC2 hardware. Multiple Diamproxies
per card is the default behavior for the DPC2. This functionality can be extended to the DPC with a
maximum of 2 instances of Diamproxies.
maximum of 2 instances of Diamproxies.
diamproxy-per-card
: Configures the number of Diameter proxies per card. By default, two
Diamproxies are spawned for each DPC2. This allows the DPC2 to handle more transactions per
proxy.
proxy.
algorithm
: Configures the algorithm to be used to distribute the load to Diamproxies. The algorithm
determines how the endpoints are distributed. Whenever an endpoint is associated with a service, the
session controller sends an Allocate-Request message specifying the endpoint name with the facility
type. The framework allocates a CPU based on the algorithm that has been configured.
session controller sends an Allocate-Request message specifying the endpoint name with the facility
type. The framework allocates a CPU based on the algorithm that has been configured.
facility
: This algorithm specifies that the Diameter proxy (endpoint) will be selected based
on the facility type. This is the default option. In this algorithm, all AAA endpoints will be
present in CPU 0 and all session manager endpoints will be present in CPU 1.
present in CPU 0 and all session manager endpoints will be present in CPU 1.
round-robin
: This algorithm specifies that the Diameter proxy selection will be in Round
Robin fashion. For example, if the number of proclets running per card is 2, the first
endpoint configured is associated with CPU 0 (proxy running in CPU 0 of the same card)
and the next endpoint configured will be associated with CPU 1, the third one with CPU 0
and fourth one with CPU1.
endpoint configured is associated with CPU 0 (proxy running in CPU 0 of the same card)
and the next endpoint configured will be associated with CPU 1, the third one with CPU 0
and fourth one with CPU1.
Usage
When the Diameter Proxy mode is enabled, each proxy process is a Diameter host, instead of requiring every
Diameter application user (such as, every ACSMgr and/or every SessMgr, depending on the application) to
be a host.
Diameter application user (such as, every ACSMgr and/or every SessMgr, depending on the application) to
be a host.
Important:
It is always recommended that the chassis be rebooted when moving from non-proxy mode to proxy
mode i.e. when configuring the
require diameter-proxy
CLI command at global configuration mode.
In Master-Slave mode, multiple Diameter proxies are running, one on each packet processing card. One
proxy serves as the Master and the other proxies are Slaves. The Master relays the traffic from an incoming
connection to a specific Slave Diameter proxy.
In releases prior to 18, when the chassis is in standby state, all the Diameter proxies are stopped. In18 and
later releases, all the Diameter proxies will be running even when the chassis is in standby mode. Any change
in ICSR grouping mask will lead to stopping and restarting of all the diamproxies on the standby chassis.
proxy serves as the Master and the other proxies are Slaves. The Master relays the traffic from an incoming
connection to a specific Slave Diameter proxy.
In releases prior to 18, when the chassis is in standby state, all the Diameter proxies are stopped. In18 and
later releases, all the Diameter proxies will be running even when the chassis is in standby mode. Any change
in ICSR grouping mask will lead to stopping and restarting of all the diamproxies on the standby chassis.