Cisco Cisco ASR 5700
Diameter Endpoint Configuration Mode Commands
route-failure ▀
Command Line Interface Reference, StarOS Release 17 ▄
3535
threshold counter
Configures the number of errors that causes the status to become FAILED. The counter value must be an
integer from 0 through 4294967295. Default: 16
The error counter begins at zero, and whenever there is a good response it decrements (but not below zero) or
increments (but not above this threshold).
integer from 0 through 4294967295. Default: 16
The error counter begins at zero, and whenever there is a good response it decrements (but not below zero) or
increments (but not above this threshold).
Usage
Use this command to control how failure/recovery is performed for the route table. After a session is
established, it is possible for the session to encounter errors or Diameter redirection messages that cause the
Diameter protocol to re-use the route table to switch to a different route.
Each Diameter client within the chassis maintains counters relating to the status of each of its connections to
different hosts (when the destination is realm/application without a specific host, the host name is kept as “”,
i.e., blank).
Moreover, those counters are further divided according to which peer is used to reach each host. Each
Diameter client maintains a status of each peer-to-host combination. Under normal good conditions the status
will be AVAILABLE, while error conditions might cause the status to be FAILED.
Only combinations that are AVAILABLE will be used. If none are AVAILABLE, then system attempts the
secondary peer if failover is configured and system can find an AVAILABLE combination there. If nothing is
AVAILABLE, the system uses a FAILED combination.
established, it is possible for the session to encounter errors or Diameter redirection messages that cause the
Diameter protocol to re-use the route table to switch to a different route.
Each Diameter client within the chassis maintains counters relating to the status of each of its connections to
different hosts (when the destination is realm/application without a specific host, the host name is kept as “”,
i.e., blank).
Moreover, those counters are further divided according to which peer is used to reach each host. Each
Diameter client maintains a status of each peer-to-host combination. Under normal good conditions the status
will be AVAILABLE, while error conditions might cause the status to be FAILED.
Only combinations that are AVAILABLE will be used. If none are AVAILABLE, then system attempts the
secondary peer if failover is configured and system can find an AVAILABLE combination there. If nothing is
AVAILABLE, the system uses a FAILED combination.
Example
The following command configures the time duration for route failure to
90
seconds:
route-failure deadtime 90