Cisco Cisco ASR 5700
Diameter Endpoint Configuration Mode Commands
▀ use-proxy
▄ Command Line Interface Reference, StarOS Release 17
3540
on all the Sessmgrs and assigns the optimal Sessmgr to the Diameter session. Once a Sessmgr is allocated for
the session, a mapping of session-id to Sessmgr is added at Diamproxy. All further requests for this session
will be directly routed to Sessmgr.
Each proxy task will automatically select one of the host names configured with the
the session, a mapping of session-id to Sessmgr is added at Diamproxy. All further requests for this session
will be directly routed to Sessmgr.
Each proxy task will automatically select one of the host names configured with the
origin host
command. Multiple proxy tasks will not use the same host names, so there should be at least as many host
names as proxy tasks. Otherwise, some proxy tasks will not be able to perform Diameter functionality. The
chassis automatically selects which proxy tasks are used by which managers (i.e., ACSMgrs, Sessmgrs),
without verifying whether the proxy task is able to perform Diameter functionality.
To be able to run this command, the Diameter proxy must be enabled. In the Global Configuration Mode
Commands chapter, see the description of the
names as proxy tasks. Otherwise, some proxy tasks will not be able to perform Diameter functionality. The
chassis automatically selects which proxy tasks are used by which managers (i.e., ACSMgrs, Sessmgrs),
without verifying whether the proxy task is able to perform Diameter functionality.
To be able to run this command, the Diameter proxy must be enabled. In the Global Configuration Mode
Commands chapter, see the description of the
require diameter-proxy
command.
In 17.0 and later releases, when a PCEF is connected to OCS via multiple Diameter proxies, PCEF will
choose the same Diameter proxy for the subsequent messages as long as it is available. Any subsequent
messages (CCR-U/CCR-T) to the same host are sent via the same peer. Once the next-hop is chosen via
round-robin method, the subsequent message for the session is sent to the same next-hop (peer).
choose the same Diameter proxy for the subsequent messages as long as it is available. Any subsequent
messages (CCR-U/CCR-T) to the same host are sent via the same peer. Once the next-hop is chosen via
round-robin method, the subsequent message for the session is sent to the same next-hop (peer).
Example
The following command enables Diameter proxy for the current endpoint:
use-proxy
The following command disables Diameter proxy for the current endpoint:
no use-proxy