Cisco ASR 9000 Serie Configuration Manuals page 253

Implementing IP Service Level Agreements
Command or Action
Step 9
tos number
Example:
RP/0/RSP0/CPU0:router(config-ipsla-icmp-path-echo)#
tos 5
Step 10 timeout milliseconds
Example:
RP/0/RSP0/CPU0:router(config-ipsla-icmp-path-echo)#
timeout 10000
Step 11
tag text
Example:
RP/0/RSP0/CPU0:router(config-ipsla-icmp-path-echo)#
tag ipsla
Step 12
lsr-path ipaddress1 {ipaddress2 {... {ipaddress8}}}
Example:
RP/0/RSP0/CPU0:router(config-ipsla-icmp-path-echo)#
lsr-path 20.25.22.1
Step 13 exit
Example:
RP/0/RSP0/CPU0:router(config-ipsla-icmp-path-echo)#
exit
RP/0/RSP0/CPU0:router(config-ipsla-op)# exit
RP/0/RSP0/CPU0:router(config-ipsla)# exit
RP/0/RSP0/CPU0:router(config)#
Step 14 ipsla schedule operation op-num
Example:
RP/0/RSP0/CPU0:router(config)# ipsla schedule
operation 432
RP/0/RSP0/CPU0:router(config-ipsla-sched)#
Step 15 life {forever | seconds}
Example:
RP/0/RSP0/CPU0:router(config-ipsla-sched)# life 1
Cisco ASR 9000 Series Aggregation Services Router System Monitoring Configuration Guide, Release 4.2.x
Configuring the ICMP Path-echo Operation
Purpose
Defines a type of service (ToS) byte in the IP header of
IP SLA operations.
The ToS byte can be converted to a Differentiated
Note
Services Code Point (DSCP) value, but you
cannot enter the DSCP value directly. To use a
DSCP value, multiply it by 4 and enter the result
as the number argument.
Sets the time that the IP SLA operation waits for a
response from its request packet.
• Use the milliseconds argument to specify the number
of milliseconds that the operation waits to receive a
response.
(Optional) Creates a user-specified identifier for an IP SLA
operation.
Specifies the path in which to measure the ICMP echo
response time.
• (Optional) Use the ip address argument of the
intermediate node or nodes in a path to the
destination.
Exits IP SLA operation configuration mode and IP SLA
configuration mode. Returns to global configuration mode.
Schedules the start time of the operation. You can
configure a basic schedule.
The forever keyword schedules the operation to run
indefinitely. The seconds argument schedules the lifetime
of the operation, in seconds. The default lifetime of an
operation is 3600 seconds (one hour).
237