Cisco Cisco Packet Data Interworking Function (PDIF)
AAA Introduction and Overview
Supported Features ▀
AAA Interface Administration and Reference, StarOS Release 18 ▄
23
If the message’s destination realm is abc.com then the message will be routed to
peer1
. If the message’s destination
realm is def.com then the message will be routed to
peer2
. If the destination realm is xyz.com then the message will be
routed to “
peer-default
”.
When multiple wildcard route entries are configured with same weights, then the routes are selected in a round robin
fashion. When multiple wildcard route entries are configured with different weights, then the route with the highest
weight will be selected.
fashion. When multiple wildcard route entries are configured with different weights, then the route with the highest
weight will be selected.
In case when there are multiple wildcard routes with higher and equal weights and some routes with lower weights, then
only the higher weight routes will be selected in round robin-fashion. The lower weight route can be selected only when
the higher weight routes are not valid because of the peers being not in good state.
only the higher weight routes will be selected in round robin-fashion. The lower weight route can be selected only when
the higher weight routes are not valid because of the peers being not in good state.
Rate Limiting Function (RLF)
Important:
Rate Limiting Function (RLF) is a license-controlled feature. A valid feature license must be
installed prior to configuring this feature. Contact your Cisco account representative for more information.
Th RLF feature implements a generic framework that can be used by multiple interfaces and products for rate-
limiting/throttling outgoing messages like Diameter messages on Gx, Gy interface towards PCRF.
limiting/throttling outgoing messages like Diameter messages on Gx, Gy interface towards PCRF.
When applications send messages to peers at a high rate, (e.g. when a large number of sessions goes down at the same
time, accounting stop messages for all the sessions are generated at the same time) the peer may not be able to handle
the messages at such high rates. To overcome this situation, the Rate Limiting Function (RLF) framework is developed
so that the application sends messages at an optimal rate such that peer is capable of receiving all the messages and does
not enter an overload condition.
time, accounting stop messages for all the sessions are generated at the same time) the peer may not be able to handle
the messages at such high rates. To overcome this situation, the Rate Limiting Function (RLF) framework is developed
so that the application sends messages at an optimal rate such that peer is capable of receiving all the messages and does
not enter an overload condition.
This feature can be enabled using the CLI command
rlf-template
in the Global Configuration mode. The users can
define the rate limiting configurations within this template. For more information on the command, see the Command
Line Interface Reference.
Line Interface Reference.
Important:
RLF template cannot be deleted if it is bound to any application (peers/endpoints).
When RLF feature is enabled, all the messages from the application are pushed to the RLF module for throttling and
rate control, and depending on the message-rate configured the RLF module sends the messages to the peer. Once the
rate or a threshold value is reached, the RLF module notifies the application to slow down or stop sending messages.
RLF module also notifies the application when it is capable of accepting more messages to be sent to the peer. RLF
module typically uses a Token Bucket Algorithm to achieve rate limiting.
rate control, and depending on the message-rate configured the RLF module sends the messages to the peer. Once the
rate or a threshold value is reached, the RLF module notifies the application to slow down or stop sending messages.
RLF module also notifies the application when it is capable of accepting more messages to be sent to the peer. RLF
module typically uses a Token Bucket Algorithm to achieve rate limiting.
Currently in the deployment of the Diameter applications ( Gx, Gy, etc.), many operators make use of “
max-
outstanding <number>
” as a means of achieving some rate-limiting on the outgoing control traffic. With RLF in
place, this is no longer required since RLF takes care of rate-limiting in all cases. If RLF is used and
max-
outstanding
is also used, there might be undesirable results.
Important:
If RLF is being used with an "
diameter endpoint
", then set the
max-outstanding
value of the
peer to be 255.
To use the template, Diameter or any other applications must be associated with the template. The RLF provides only
the framework to perform the rate limiting at the configured Transactions Per Second (TPS). The applications (like
Diameter) should perform the configuration specific to each application.
the framework to perform the rate limiting at the configured Transactions Per Second (TPS). The applications (like
Diameter) should perform the configuration specific to each application.