Cisco Cisco Packet Data Interworking Function (PDIF)
Diameter Endpoint Configuration Mode Commands
▀ route-entry
▄ Command Line Interface Reference, StarOS Release 18
3566
route-entry
This command creates an entry in the route table for Diameter peer.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > Diameter Endpoint Configuration
configure > context context_name > diameter endpoint endpoint_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-ctx-diameter)#
Syntax
route-entry { [ host [ * ] host_name ] [ peer peer_id [ weight priority ] ] [ realm [ * ]
realm_name [ application credit-control peer peer_id ] [ weight value ] | peer peer_id [
weight value ] ] }
realm_name [ application credit-control peer peer_id ] [ weight value ] | peer peer_id [
weight value ] ] }
no route-entry { [ host [ * ] host_name ] [ peer peer_id ] [ realm [ * ] realm_name {
application credit-control peer peer_id | peer peer_id } ] }
application credit-control peer peer_id | peer peer_id } ] }
no
Disables the specified route-entry table configuration.
host [ * ] host_name
Specifies the Diameter server’s host name as an alphanumeric string of 1 through 63 characters. In 18.0 and
later releases, the host name can additionally accept wildcard character (*). The support for wildcard entry is
provided to allow routing of Diameter messages destined to any host @ any realm through the next-hop peer.
later releases, the host name can additionally accept wildcard character (*). The support for wildcard entry is
provided to allow routing of Diameter messages destined to any host @ any realm through the next-hop peer.
realm [ * ] realm_name
Specifies the realm name as an alphanumeric string of 1 through 127 characters. The realm may typically be a
company or service name. In 18.0 and later releases, the realm name can additionally accept wildcard
character (*). The support for wildcard entry is provided to allow routing of Diameter messages destined to
any host @ any realm through the next-hop peer.
company or service name. In 18.0 and later releases, the realm name can additionally accept wildcard
character (*). The support for wildcard entry is provided to allow routing of Diameter messages destined to
any host @ any realm through the next-hop peer.
application credit-control
Specifies the credit control application — DCCA or RADIUS.
peer peer_id
Specifies the peer ID of the Diameter endpoint route as an alphanumeric string of 1 through 63 characters.
weight priority
Specifies the priority for a peer in the route table as an integer from 0 through 255. Default: 10