Cisco Cisco Packet Data Interworking Function (PDIF)
AAA Introduction and Overview
Diameter Proxy ▀
AAA Interface Administration and Reference, StarOS Release 19 ▄
17
Diameter Proxy
The proxy acts as an application gateway for Diameter. It gets the configuration information at process startup and
decides which Diameter peer has to be contacted for each application. It establishes the peer connection if no peer
connection already exists. Upon receiving the answer, it uses the Diameter session ID to identify to which application
the message is intended.
decides which Diameter peer has to be contacted for each application. It establishes the peer connection if no peer
connection already exists. Upon receiving the answer, it uses the Diameter session ID to identify to which application
the message is intended.
Each PSC has a Diameter proxy identified by the IPv6 origin host address. If the number of configured origin hosts is
lesser than the number of active PSCs, some (i.e. those number where no origin hosts associated with) PSCs will not
activate Diameter processing at all, and instead notify administrators of the erroneous configuration with syslog/traps.
lesser than the number of active PSCs, some (i.e. those number where no origin hosts associated with) PSCs will not
activate Diameter processing at all, and instead notify administrators of the erroneous configuration with syslog/traps.
If the number of configured origin hosts is greater than the number of active PSCs, the application will automatically
select which configured host is to be used per PSC.
select which configured host is to be used per PSC.
In 18.0 and later releases, with the introduction of DPC2 card, the number of supported sessions has increased from
ASR5000 to ASR5500, and the TPS per proxy has also increased considerably. To handle more number of transactions
per proxy and support the requirement for the new DPC2 card in ASR 5500, Diameter Proxy has been scaled.
ASR5000 to ASR5500, and the TPS per proxy has also increased considerably. To handle more number of transactions
per proxy and support the requirement for the new DPC2 card in ASR 5500, Diameter Proxy has been scaled.
To support this scaling architecture, a new framework “proclet-map-frwk” has been developed. This framework works
in Client-Server model. For diamproxy enhancement, diactrl will act as the server and the proclets (sessmgr and aaamgr)
act as client. The framework will maintain a set of tables in both Client and Server which contains details about the
endpoint to diamproxy association.
in Client-Server model. For diamproxy enhancement, diactrl will act as the server and the proclets (sessmgr and aaamgr)
act as client. The framework will maintain a set of tables in both Client and Server which contains details about the
endpoint to diamproxy association.
In support of this feature, the existing CLI command “
require diameter-proxy
” has been enhanced to allow
multiple Diameter proxies per card and specify the proxy selection algorithm type in ASR 5500. For more information
on this command, refer to the Command Line Interface Reference, StarOS Release 18.
on this command, refer to the Command Line Interface Reference, StarOS Release 18.