Cisco Cisco Packet Data Gateway (PDG)
AAA Introduction and Overview
▀ Supported Features
▄ AAA Interface Administration and Reference, StarOS Release 18
22
table. This route entry will be flagged as Dynamic and a Path Cache entry. The following entries will be added to the
dynamic route entry.
dynamic route entry.
Flag (Dynamic and Path-Cache)
Host name (Corresponding to the Origin-Host from the response)
Realm (Obtained from the session)
Application id (Obtained from the session)
Peer (From which the response was received)
Weight (Inherit the weight of the realm-based route entry based on which the request was routed)
Dynamic Route Deletion
The dynamic route will be deleted from the routing table in the following conditions:
The peer associated with the route-entry is deleted.
When the route is not used by any of the sessions for a given period of time.
When the realm based route from which the dynamic route is derived, is deleted.
The route deletion can be accomplished by introducing a new CLI in the Diameter Endpoint configuration mode. This
CLI allows configuring an expiry timeout based on which the route entry will be deleted.
CLI allows configuring an expiry timeout based on which the route entry will be deleted.
For information on the commands used for configuring the realm-based routing feature, refer to the Command Line
Interface Reference.
Interface Reference.
Wildcard based Diameter Routing
This feature provides customers the ability to configure wildcard based Diameter realm routing to avoid configuring
individual Diameter peers and/or realms for all possible Diameter servers in their network.
individual Diameter peers and/or realms for all possible Diameter servers in their network.
The wildcard Diameter routes can be statically configured under a Diameter endpoint configuration using the CLI
“
“
route-entry realm * peer peer_name
”.
These route entries are treated as default route entries and they will be selected when there is no matching host@realm
based or no realm based route entry available.
based or no realm based route entry available.
The wildcard route entry can be configured in the following ways:
route-entry realm * peer peer_name
- or -
route-entry host * realm * peer peer_name
Both these configurations have the same effect; matches to any host and any realm.
The wildcard Diameter route is added along with other realm based route entries in diabase. The wildcard route entry
will be selected to route a message only if the message’s destination realm does not match with any of the other static
realm based routes.
will be selected to route a message only if the message’s destination realm does not match with any of the other static
realm based routes.
For example,
route-entry realm abc.com peer peer1
route-entry realm def.com peer peer2
route-entry realm * peer peer-default