The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS IP SLAs commands for the Cisco Nexus 7000 series devices.
To set the acceptable Network Time Protocol (NTP) clock synchronization tolerance for a one-way Cisco NX-OS IP Service Level Agreements (SLAs) operation measurement, use the clock-tolerance command. To return to the default value, use the no form of this command.
clock-tolerance ntp oneway {absolute value | percent value}
The NTP clock synchronization tolerance is set to 0 percent.
UDP jitter configuration mode (config-ip-sla-jitter)
|
|
---|---|
You must configure the precession microseconds command before you use the clock-tolerance command.
This example shows how to enable microsecond precision, configure the NTP synchronization offset tolerance to 10 percent, and set the packet priority to high for IP SLAs UDP jitter operation 1:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To specify the data pattern in a Cisco NX-OS IP Service Level Agreements (SLAs) operation to test for data corruption, use the data pattern command. To remove the data pattern specification, use the no form of this command.
Hexadecimal string to use for monitoring the specified operation. |
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
The data-pattern command allows you to specify an alphanumeric character string to verify that the operation payload does not get corrupted in either direction (source-to-destination or destination-to-source.).
This example show how to specify 1234ABCD5678 as the data pattern in an IPv4 network:
To configure a Cisco NX-OS IP Service Level Agreement (SLA) FabricPath echo probe operation, use the fabric-patch echo command in the IP SLA sub-configuration mode.
fabric-path echo switch-id [profile profile-id [interface type number ]]
IP SLA sub-configuration (config-ip-sla)
|
|
---|---|
Before starting the operation, install and enable the fabricpath feature set on the device.
This example shows how to configure operation 6 as a Cisco NX-OS IP SLA FabricPath operation:
|
|
---|---|
To set the rate at which a specified IP Service Level Agreements (SLAs) operation repeats, use the frequency command. To return to the default value, use the no form of this command.
Number of seconds between the IP SLAs operations. The range is from 1 to 604800 seconds. |
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
|
|
---|---|
A single IP SLAs operation repeats at a given frequency for the lifetime of the operation. For example, a User Datagram Protocol (UDP) jitter operation with a frequency of 60 sends a collection of data packets (simulated network traffic) once every 60 seconds for the lifetime of the operation. The default simulated traffic for a UDP jitter operation consists of ten packets sent 20 milliseconds apart. This payload is sent when the operation is started and is sent again 60 seconds later.
If an individual IP SLAs operation takes longer to execute than the specified frequency value, a statistics counter called “busy” is incremented rather than immediately repeating the operation.
This example shows how to configure an IP SLAs UDP echo operation (operation 10) to repeat every 90 seconds:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the number of history buckets that are kept during the lifetime of a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history buckets-kept command. To return to the default value, use the no form of this command.
Number of history buckets kept during the lifetime of the operation. The range is from 1 to 60. |
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
Each time that IP SLAs start an operation, a new bucket is created until the number of history buckets that matches the specified size or the lifetime of the operation expires. History buckets does not wrap (which means that the older information is not replaced by the newer information).
To define the lifetime of an IP SLAs operation, use the ip sla schedule command.
By default, the history for an IP SLAs operation is not collected. If history is collected, each bucket contains one or more history entries from the operation.
The type of entry stored in the history table is controlled by the history filter command.
The total number of entries stored in the history table is controlled by the combination of the samples-of-history-kept, history buckets-kept, and history lives-kept commands.
This example shows how to configure an UDP echo operation to keep 25 history buckets during the operation lifetime:
To set the number of statistics distributions kept per hop during a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history distributions-of-statistics-kept command. To return to the default value, use the no form of this command.
history distributions-of-statistics-kept size
no history distributions-of-statistics-kept
Number of statistics distribution kept per hop. The size is from 1 to 20 characters. |
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter).
|
|
---|---|
In most situations, you does not need to change the number of statistics distributions kept or the time interval for each distribution. Change these parameters only when distributions are needed, for example, when performing statistical modeling of your network.
To set the statistics distributions interval, use the history statistics-distribution-interval command.
When the number of distributions reaches the size specified, no further distribution-based information is stored.
This example shows how to set the statistics distribution to five and the distribution interval to 10 ms for an UDP echo operation. The first distribution contains statistics from 0 to 9 ms, the second distribution contains statistics from 10 to 19 ms, the third distribution contains statistics from 20 to 29 ms, the fourth distribution contain statistics from 30 to 39 ms, and the fifth distribution contains statistics from 40 ms to infinity.
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To enable enhanced history gathering for a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history enhanced command. To return to the default value, use the no form of this command.
history enhanced [interval seconds] [buckets number-of-buckets]
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
|
|
---|---|
This command enables enhanced history for the IP SLAs operation.
Performance statistics are stored in buckets that separate the accumulated data. Each bucket consists of data accumulated over the specified time interval. When the interval expires, history statistics are gathered in a new bucket. When the specified number of buckets is reached, statistic gathering for the operation ends.
By default, IP SLAs maintain two hours of aggregated statistics for each operation. The value from each operation cycle is aggregated with the previously available data within a given hour. The enhanced history feature in IP SLAs allows for the aggregation interval to be shorter than one hour.
This example shows how to enable enhanced history gathering for a Cisco NX-OS IP Service Level Agreements (SLAs) operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To define the type of information kept in the history table for a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history filter command. To return to the default value, use the no form of this command.
history filter {all | failures | none | overThreshold}
no history filter {all | failures | none | overThreshold}
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
Use the history filter command to control what gets stored in the history table for an IP SLAs operation. To control how much history gets saved in the history table, use the history lives-kept, history buckets-kept, and the samples-of-history-kept commands.
This example shows how to collect only the operation packets that have failed and are kept in the history table:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the number of hours for which statistics are maintained for a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history hours-of-statistics-kept command. To return to the default value, use the no form of this command.
history hours-of-statistics-kept hours
no history hours-of-statistics-kept
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
|
|
---|---|
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest information is replaced by newer information).
This example shows how to maintain 3 hours of statistics for an UDP echo operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the number of lives maintained in the history table for a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history lives-kept command. To return to the default value, use the no form of this command.
Number of lives maintained in the history table for the operation. If you specify 0 lives, history is not collected for the operation. The range is from 0 to 2 lives. |
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
The following rules apply to the history lives-kept command:
• The number of lives you can specify is dependent on the type of operation that you are configuring.
• The default value of 0 lives means that history is not collected for the operation.
• When the number of lives exceeds the specified value, the history table wraps (that is, the oldest information is replaced by newer information).
• When an operation makes a transition from a pending to an active state, a life starts. When the life of an operation ends, the operation makes a transition from an active to pending state.
This example shows how to maintain the history for five lives of an UDP echo operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the time interval for each statistics distribution kept for a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the history statistics-distribution-interval command. To return to the default value, use the no form of this command.
history statistics-distribution-interval milliseconds
no history statistics-distribution-interval
Distribution interval value in milliseconds (ms). The range is from 1 to 100 milliseconds. |
The default interval used for each statistics kept is 20 milliseconds.
TCP connect configuration mode (config-ip-sla-tcp)
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
In most situations, you does not need to change the time interval for each statistics distribution or number of distributions kept. Change these parameters only when distributions are needed, for example, when you are performing statistical modeling of your network.
This example shows how to set the time interval for each statistics distribution kept for a Cisco NX-OS IP Service Level Agreements (SLAs) operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To configure a Cisco nx-OS IP Service Level Agreements (SLA) Internet Control Message Protocol (ICMP) echo probe operation, use the icmp-echo command. To remove the settings, use the no form of this command.
icmp-echo destination-ip-address
IP SLA configuration mode (config-ip-sla)
|
|
---|---|
This example shows how to configure an IP SLA Internet Control Message Protocol (ICMP) echo probe operation:
|
|
---|---|
Begins the configuration for an IP SLAs operation and enters IP SLA configuration mode. |
|
Permanently enables the IP SLAs responder functionality on a specified IP address and port. |
To specify an interface type and number, use the interface command.
Interface configuration mode (config-if)
|
|
---|---|
This example shows how to specify an interface type and number:
|
|
---|---|
Begins the configuration for an IP SLAs operation and enters IP SLA configuration mode. |
|
Permanently enables the IP SLAs Responder functionality on a specified IP address and port. |
To define an IP access list access control list (ACL) in order to enable filtering for packets, use the ip access-list command. To remove the settings, use the no form of this command.
ip access-list access-list-name
no ip access-list access-list-name
Global configuration mode (config)
|
|
---|---|
This example shows how to define an IP ACL in order to enable filtering for packets.
To specify a primary IP address for an interface, use the ip address command. To remove the default settings, use the no form of this command.
Global configuration mode (config)
|
|
---|---|
This example shows how to specify a primary IP address for an interface:
To begin configuring a Cisco NX-OS IP Service Level Agreements (SLAs) operation and enter IP SLA configuration mode, use the ip sla command. To remove all configuration information for an operation, including the schedule of the operation, reaction configuration, and reaction triggers, use the no form of this command.
Operation number used for the identification of the IP SLAs operation that you want to configure. The range is from 1 to 2147483647. |
Global configuration mode (config)
|
|
---|---|
Use the ip sla command to specify an identification number for the operation you are about to configure. After you enter this command, the router enters IP SLA configuration mode.
The ip sla command is supported in IPv4 networks.
IP SLAs allow a maximum of 2000 operations.
Debugging is supported only on the first 32 operation numbers.
After you configure an operation, you must schedule the operation. For information on scheduling an operation, see the ip sla schedule and ip sla group schedule global configuration commands.
After you schedule an operation, you cannot modify the configuration of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla command) and then reconfigure the operation with the new operation type.
This example shows how to configure operation 99 as a UDP jitter operation in an IPv4 network and schedule it to start running in 5 hours. The example shows the ip sla command being used in an IPv4 network.
To perform group scheduling for Cisco NX-OS IP Service Level Agreements (SLAs) operations, use the show ip sla group schedule command. To cause all the IP SLAs operations that belong to a multioperation schedule to become inactive, use the no form of this command.
ip sla group schedule group-id {operation-ids | add operation-ids | delete operation-ids | reschedule} schedule-period seconds [ageout seconds] [frequency [seconds | range random-frequency-range]] [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}]
no ip sla group schedule group-id
The multioperation schedule is placed in a pending state (that is, the group of IP SLAs operations are enabled but are not actively collecting information).
Global configuration mode (config)
|
|
---|---|
Although the IP SLAs multioperation scheduling functionality helps in scheduling thousands of operations, you should be cautious when specifying the number of operations, the schedule period, and the frequency to avoid any significant CPU impact.
This example shows how to schedule IP SLAs operations 3, 4, and 6 to 10 (identified as group 1) using multioperation scheduling. In this example, the operations are scheduled to begin at equal intervals over a scheduled period of 20 seconds. The first operation (or set of operations) is scheduled to start immediately. Because the frequency is not specified, it is set to the value of the schedule period (20 seconds) by default.
This example shows how to schedule IP SLAs operations 1 to 3 (identified as group 2) using the random scheduler option. In this example, the operations are scheduled to begin at random intervals over a schedule period of 50 seconds. The first operation is scheduled to start immediately. The frequency at which each operation restarts is chosen randomly within 80 to 100 seconds.
To configure the scheduling parameters for a single Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the ip sla schedule command. To stop the operation and place it in the default state (pending), use the no form of this command.
ip sla schedule group-operation-number [life {forever | seconds}] [start-time {hh:mm[:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
no ip sla schedule operation-number
|
|
---|---|
After you schedule the operation with the ip sla schedule command, you cannot change the configuration of the operation. To change the configuration of the operation, use the no form of the ip sla global configuration and reenter the configuration information.
The following time line shows the aged-out process of the operation:
W----------------------X----------------------Y----------------------Z
•W is the time that the operation was configured with the ip sla command.
•X is the start time or start of life of the operation (that is, when the operation became active).
•Y is the end of life as configured with the ip sla schedule command (life seconds have counted down to zero).
•Z is the aged-out time of the operation.
When the operation is in an active state, it immediately begins collecting information.
The aged-out time starts counting down at W and Y, is suspended between X and Y, and is reset to its configured size at Y.
The operation can ageout before it executes (that is, Z can occur before X). To ensure that this situation does not happen, configure the difference between the operation’s configuration time and start time (X and W) to be less than the aged-out seconds.
The recurring keyword is supported only for scheduling single IP SLAs operations. You cannot schedule multiple IP SLAs operations using the ip sla schedule command. The life value for a recurring IP SLAs operation should be less than one day. The aged-out value for a recurring operation must be “never” (which is specified with the value 0), or the sum of the life and aged-out values must be more than one day. If the recurring option is not specified, the operations are started in the existing normal scheduling mode.
This example shows how to configure scheduling operation 3 to begin collecting data immediately and to run indefinitely:
This example shows how to configure scheduling operation 15 to begin automatically collecting data every day at 1:30 a.m.:
|
|
---|---|
To define the criteria for whether appropriate packets meet the particular policy, use the match ip address command. To return to default setting, use the no form of this command.
no match ip address access-list
Specifies the IP access list name. The maximum size is 63 characters. |
Rote-map configuration mode (config-route-map)
|
|
---|---|
The match clauses define the criteria for whether appropriate packets meet the particular policy (that is, the condition to be met). The set clauses than explain how the packets should be routed once they have met the match criteria. To match packets based on IP address use the match ip address command. The IP standard or extended ACLs can be used to establish the match criteria. The standard IP access lists can be used to specify the match criteria based on application, protocol type, type of service (ToS), and precedence.
This example shows how to define the criteria for whether appropriate packets meet the particular policy:
To specify match address of route or match packet, use the match ip address command. To return to the default setting, use the no form of this command.
no match ip address access-list
Route-map configuration mode (config-route-map)
|
|
---|---|
This example show how to specify match address of route or match packet:
To specify the packet priority in a Cisco NX-OS IP Service Level Agreements (SLAs) operation template, use the operation-packet priority command. To return to the default value, use the no form of this command.
operation-packet-priority {normal | high}
UDP jitter configuration (config-ip-sla-jitter)
|
|
---|---|
Increasing the packet priority of an IP SLAs operation can reduce the delay time for the packets in the queue. This command is supported by the IP SLAs User Datagram Protocol (UDP) jitter operation only.
The following example shows how to enable microsecond precision, configure the Network Time Protocol (NTP) synchronization offset tolerance to 10 percent, and set the packet priority to high for an IP SLAs UDP jitter operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To configure the Simple Network Management Protocol (SNMP) owner of a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the owner command in the appropriate submode of IP SLA configuration. To return to the default value, use the no form of this command.
IP SLA configuration mode (config-ip-sla)
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
|
|
---|---|
The owner name contains one or more of the following: ASCII form of the network management station’s transport address, network management station name (that is, the domain name), and network management personnel’s name, location, or phone number. In some cases, the agent itself will be the owner of the operation. In these cases, the name can begin with “agent.”
This example shows how to set the owner of IP SLAs UDP echo operation 1 to 1234:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To create an access control list (ACL) rule that permits traffic matching its conditions, use the permit ip command. To return to the default value, use the no form of this command.
no permit ip source destination
|
|
---|---|
This example shows how to create an access control list (ACL) rule that permits traffic matching its conditions:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the level of precision at which the statistics for a Cisco NX-OS IP Service Level Agreements (SLAs) operation are measured, use the precision command. To return to the default value, use the no form of this command.
precision {millisecond | microseconds}
Sets the precision of IP SLAs operation measurements to 1 millisecond (ms). |
|
Sets the precision of IP SLAs operation measurements to 1 microsecond (usec). |
Measurements for the IP SLAs operation are displayed in milliseconds.
UDP jitter configuration mode (config-ip-sla)
|
|
---|---|
If the milliseconds keyword is configured (default), the measurements for an IP SLAs operation are displayed with the granularity of 1 ms. For example, a value of 22 equals 22 ms. If you use the microseconds keyword, the measurements for an IP SLAs operation are displayed with the granularity of 1 microsecond. For example, a value of 202 equals 202 microseconds.
This command is supported by the IP SLAs User Datagram Protocol (UDP) jitter operation only.
This example shows how to enable microsecond precision, configure the Network Time Protocol (NTP) synchronization offset tolerance to 10 percent, and set the packet priority to high for an IP SLAs UDP jitter operation.
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To set the protocol data size in the payload of a Cisco NXOS IP Service Level Agreements (SLAs) operation’s request packet, use the request-data-size command. To return to the default value, use the no form of this command.
Size of the protocol data in the payload of the request packet of the operation, in bytes. The range is from 4 to 1500. |
The default data size varies depending on the type of IP SLAs operation that you are configuring.
IP SLA configuration mode (config-ip-sla)
UDP echo configuration mode (config-ip-sla-udp)
|
|
---|---|
The request-data-size command can be used to set the padding size for the data frame of an IP SLAs Ethernet operation.
This example shows how to set the request packet size to 40 bytes for an IP SLAs UDP echo operation:
|
|
---|---|
Begins the configuration for an IP SLAs LSP Health Monitor operation and enters auto IP SLA MPLS configuration mode. |
To specify a route map, use the route-map command. To return to the default value, use the no form of this command.
Route-map configuration mode (config-route-map)
|
|
---|---|
This example shows how to specify a route map:
|
|
---|---|
Begins the configuration for an IP SLAs LSP Health Monitor operation and enters auto IP SLA MPLS configuration mode. |
To configure a route map that sets the next-hop IPv4 address as the default, use the set ip default next-hop command. To delete an entry, use the no form of this command.
set ip default next-hop ip-address [ ...ip-address ] [ load-share | verify-availability ]
no set ip default next-hop ip-address [ ...ip-address ]
IPv4 address of the next hop to which packets are output.The next hop must be an adjacent router. You can configure up to 32 IP addresses. |
|
Route-map configuration (config-route-map)
|
|
---|---|
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ip-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, it routes the packet to this next hop. The first next hop specified with the set ip default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ip policy route-map command, the route-map global configuration command, and the match and set commands to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used with one another. They are evaluated in the following order:
Note The set ip next-hop and set ip default next-hop command are similar but have a different order of operations. Configuring the set ip next-hop command causes the system to use policy routing first and then use the routing table. Configuring the set ip default next-hop command causes the system to use the routing table first and then policy route the specified next hop.
For software-forwarded traffic, the route that is present in the unicast routing table (of the VRF in which packet was received) for the packet-specified destination takes preference over what is specified in the set ip default next-hop command when there is condition match. Even if there is a default route present in the VRF, that default route overrides what is set in the command. This applies to software-forwarded traffic only.
This example shows how to configure a route map that sets the IPv4 default next-hop address as the default:
To configure the route map to verify the reachability of the tracked object, use the set ip next-hop verify-availability command. To return to the default value, use the no form of this command.
set ip next-hop verify-availability next-hop-address [track object ] [load-share]
no set ip next-hop verify-availability next-hop-address [track object ] [load-share]
IP address of the next hop to which packets will be forwarded. |
|
Object number that the tracking subsystem is tracking. The acceptable range is from 1 to 500. |
|
The NTP clock synchronization tolerance is set to 0 percent.
|
|
---|---|
This example shows how to configure the route map to verify the reachability of the tracked object:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To indicate where to output packets that pass a match clause of a route map for policy routing and for which the Cisco NX-OS software has no explicit route to a destination, use the set ipv6 default next-hop command. To delete an entry, use the no form of this command.
set ipv6 default next-hop ipv6-address [ ...ipv6-address ] [ load-share | verify-availability]
no set ipv6 default next-hop ipv6-address [ ...ipv6-address ] [ load-share | verify-availability]
IPv6 address of the next hop to which packets are output.The next hop must be an adjacent router. You can configure up to 32 IPv6 addresses. |
|
Route-map configuration (config-route-map)
|
|
---|---|
An ellipsis (...) in the command syntax indicates that your command input can include multiple values for the ipv6-address argument.
Use this command to provide certain users a different default route. If the software has no explicit route for the destination in the packet, then it routes the packet to this next hop. The first next hop specified with the set ipv6 default next-hop command needs to be adjacent to the router. The optional specified IP addresses are tried in turn.
Use the ipv6 policy route-map i nterface configuration command, the route-map global configuration command, and the match and set route-map configuration commands to define the conditions for policy routing packets. The ipv6 policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria —the conditions under which policy routing occurs. The set commands specify the set actions —the particular routing actions to perform if the criteria enforced by the match commands are met.
The set clauses can be used with one another. They are evaluated in the following order:
Note The set ipv6 next-hop and set ipv6 default next-hop are similar commands but have a different order of operations. Configuring the set ipv6 next-hop command causes the system to use policy routing first and then use the routing table. Configuring the set ipv6 default next-hop command causes the system to use the routing table first and then policy route the specified next hop.
This example shows how to configure a route map that sets the IPv6 default next-hop address:
To configure the route map to verify the reachability of the tracked object, use the set ipv6 next-hop verify-availability command. To return to the default value, use the no form of this command.
set ipv6 next-hop verify-availability next-hop-address track object
no set ipv6 next-hop verify-availability
IPv6 address of the next hop to which packets will be forwarded. |
|
Object number that the tracking subsystem is tracking. The acceptable range is from 1 to 500. |
The NTP clock synchronization tolerance is set to 0 percent.
|
|
---|---|
This example shows how to configure the route map to verify the reachability of the tracked object:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To display global information about the Cisco NX-OS IP Service Level Agreements (SLAs) application, use the show ip sla application command.
|
|
---|---|
Use the show ip sla application command to display information such as the supported operation types and supported protocols.
This example shows how to display information about the IP SLA application:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To display configuration values including all defaults for all Cisco NX-OS IP Service Level Agreements (SLAs) operations or a specified operation, use the show ip sla configuration command.
show ip sla configuration [operation]
(Optional) Displays the number of the IP SLAs operation for which the details are displayed. The range is from 1 to 2147483647. |
|
|
---|---|
This example shows how to display the configuration values including all defaults for all Cisco NX-OS IP Service Level Agreements (SLAs) operations or a specified operation:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To display the group schedule details for Cisco NX-OS IP Service Level Agreements (SLAs) operations, use the show ip sla group schedule command.
show ip sla group schedule group-operation-number
(Optional) Number of the IP SLAs group operation. The range is from 1 to 2147483647. |
|
|
---|---|
This example shows how to display the information about group (multiple) scheduling. The last line in this example indicates that the IP SLAs operations are multiple times scheduled (TRUE):
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To display the current operational status and statistics of all Cisco NX-OS IP Service Level Agreements (SLAs) operations or a specified operation over the last one hour, use the show ip sla statistics command.
show ip sla statistics [operation-number] [aggregated] [details]
Displays output for all running IP SLAs operations.
|
|
---|---|
Use the show ip sla statistics command to display the current state of IP SLAs operations, including how much life the operation has left, whether the operation is active, and the completion time. The output also includes the monitoring data returned for the last (most recently completed) operation.
This example shows how to display the operational status and statistics over the last one hour:
This example shows how to display the aggregated statistics:
|
|
---|---|
Displays the configuration including default values of IP SLAs auto-measure groups. |
To specify the data pattern in a Cisco NX-OS IP Service Level Agreements (SLAs) operation to test for data corruption, use the tag command. To remove the data pattern specification, use the no form of this command.
IP SLA configuration (ip-sla-config).
|
|
---|---|
An operation tag is used to logically link operations in a group.
Tags can be used to support automation (for example, by using the same tag for two different operations on two different routers echoing the same target).
This example shows how to specify the data pattern in an IPv4 network in UDP echo configuration mode within IP SLA configuration mode:
To define a Cisco NX-OS IP Service Level Agreements (SLAs) Transmission Control Protocol (TCP) connection operation, use the tcp-connect command.
tcp-connect {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]
No IP SLAs operation type is associated with the operation number being configured.
IP SLA configuration (config-ip-sla)
|
|
---|---|
The TCP connection operation is used to discover the time required to connect to the target device. This operation can be used to test virtual circuit availability or application availability. If the target is a Cisco router, IP SLAs make a TCP connection to any port number specified by the user. If the destination is a non-Cisco IP host, you must specify a known target port number (for example, 21 for FTP, 23 for Telnet, or 80 for an HTTP server). This operation is useful in testing Telnet or HTTP connection times.
You must enable the IP SLAs responder on the target router before you can configure a TCP Connect operation.
The control protocol is required when the target device is a Cisco router that does not natively provide the UDP or TCP Connect service. Prior to sending an operation packet to the target router, IP SLAs sends a control message to the IP SLAs responder to enable the destination port. If you disable control by using the control disable keyword combination with this command, you must define the IP address of the source for the responder by using the ip sla responder tcp-connect ipaddress command on the destination device.
This example shows how to configure IP SLAs operation 11 as a TCP connection operation using the destination IP address 172.16.1.175 and the destination port 2400:
|
|
---|---|
Begins the configuration for an IP SLAs operation and enters IP SLA configuration mode. |
|
Permanently enables the IP SLAs Responder functionality on a specified IP address and port. |
To set the class of service (CoS) for a Cisco NX-OS IP Service Level Agreements (SLAs) Ethernet operation, use the threshold command. To return to the default value, use the no form of this command.
Length of time required for a rising threshold to be declared, in milliseconds (ms). The range is from 0 to 60000. The default is 5000. |
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter).
|
|
---|---|
The value specified for this command must not exceed the value specified for the timeout command.
The threshold value configured by this command is used only to calculate network monitoring statistics created by a Cisco NX-OS IP SLAs operation. This value is not used for generating Simple Network Management Protocol (SNMP) trap notifications. Use the ip sla reaction-configuration command to configure the thresholds for generating IP SLAs SNMP trap notifications.
This example shows how to configure the threshold of the IP SLAs UDP echo operation to 4000:
To enable or disable control messages in an auto IP Service Level Agreements (SLAs) operation template, use the control command. To return to the default value, use the no form of this command.
The default timeout value varies depending on the type of IP SLAs operation that you are configuring.
IP SLA configuration mode (config-ip-sla)
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
TCP connect configuration (config-tplt-tcp-conn)
UDP echo configuration (config-tplt-udp-ech)
|
|
---|---|
The value of the milliseconds argument should be based on the sum of both the maximum round-trip time (RTT) value for the packets and the processing time of the IP SLAs operation.
Use the timeout command to set how long the operation waits to receive a response from its request packet, and use the frequency command to set the rate at which the IP SLAs operation restarts. The value specified for the timeout command cannot be greater than the value specified for the frequency command.
This example shows how to set the timeout value for an IP SLAs operation 1 from 5000 ms:
To define a type of service (ToS) byte in the IPv4 header of a Cisco NX-OS IP Service Level Agreements (SLAs) operation, use the tos command. To return to the default value, use the no form of this command.
Service type byte in the IPv4 header. The range is from 1 to 255. |
UDP jitter configuration mode (config-ip-sla-jitter)
IP SLA configuration mode (ip-sla-config)
UDP echo configuration mode (config-ip-sla-udp).
|
|
---|---|
The ToS value is stored in an 8-bit field in the IPv4 packet header. This value contains information such as precedence and ToS. This information is useful for policy routing and for features like Committed Access Rate (CAR), where routers examine ToS values.
This example shows how to configure IP SLAs operation 1 as an UDP echo operation with destination IP address 172.16.1.176. The ToS value is set to 0x80.
|
|
---|---|
Enters IP SLA template configuration mode for defining an auto IP SLAs operation template. |
|
Displays the configuration including default values of auto IP SLAs operation templates. |
To track the reachability of an object, use the track command. To remove the settings, use the no form of this command.
track object-number ip sla entry-number reachability
Tracking configuration mode (config-track)
|
|
---|---|
This example shows how to track the reachability of an object:
To define a Cisco NX-OS IP Service Level Agreements (SLAs) User Datagram Protocol (UDP) echo operation, use the udp-echo command. To remove the list, use the no form of this command.
udp-echo {destination-ip-address | destination-hostname} destination-port [source-ip {ip-address | hostname} source-port port-number] [control {enable | disable}]
No IP SLAs operation type is associated with the operation number being configured.
IP SLA configuration mode (config-ip-sla)
|
|
---|---|
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla global configuration command) and then reconfigure the operation with the new operation type.
IP SLAs UDP echo operations support IPv4 addresses.
The control protocol is required when the target device is a Cisco router that does not natively provide the UDP or TCP Connect service. If you disable control by using the control disable keyword combination, you must define the IP address of the source for the IP SLAs Responder by using the ip sla responder udp-echo ipaddress command on the destination device.
This example shows how to configure an IP SLAs operation as a UDP echo operation using the destination IPv4 address 172.16.1.175 and destination port 2400:
|
|
---|---|
Begins the configuration for an IP SLAs operation and enters IP SLA configuration mode. |
|
Permanently enables the IP SLAs responder functionality on a specified IP address and port. |
To configure a Cisco NX-OS IP Service Level Agreements (SLA) User Datagram Protocol (UDP) operation that returns Voice over IP (VoIP) scores, use the udp-jitter command with codec option.
udp-jitter {destination-ip-address | destination-hostname} destination-port codec codec-type [codec-numpackets number-of-packets] [codec-size number-of-bytes] [codec-interval milliseconds] [advantage-factor value] [source-ip {ip-address | hostname}] [source-port port-number] [control {enable | disable}]
The default number of packets sent by the udp-jitter operation without codec is 10 packets.
IP SLA configuration mode (config-ip-sla)
|
|
---|---|
The udp-jitter command configures an IP SLAs UDP Plus operation. The UDP Plus operation is a superset of the UDP echo operation. In addition to measuring the UDP round-trip time, the UDP Plus operation measures per-direction packet loss and jitter. Jitter is an interpacket delay variance. Jitter statistics are useful for analyzing traffic in a Voice over IP (VoIP) network.
You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter) before you can configure any of the other parameters of the operation. To change the operation type of an existing IP SLAs operation, you must first delete the IP SLAs operation (using the no ip sla global configuration command) and then reconfigure the operation with the new operation type.
You must enable the IP SLAs responder on the target router before you can configure a UDP jitter operation. Prior to sending an operation packet to the target router, IP SLAs send a control message to the responder to enable the destination port. The control protocol is required when the target device is a Cisco router that does not natively provide the UDP or TCP Connect service. If you disable the control by using the control disable keyword combination with this command, you must define the IP address of the source for the IP SLAs responder by using the ip sla responder udp-echo ipaddress command on the destination device.
The default request packet data size for an IP SLAs UDP jitter operation is 32 bytes. Use the request-data-size command to modify this value.
IP SLAs UDP jitter operations support IPv4 addresses.
When you specify the codec in the command syntax of the udp-jitter command, the standard configuration options are replaced with codec-specific keywords and arguments. The codec-specific command syntax is documented separately from the command syntax for the standard implementation of the udp-jitter command.
This example shows how to configure operation 6 as a UDP jitter operation with the destination IPv4 address 172.30.125.15, the destination port number 2000, 20 packets, and an interpacket interval of 20 ms:
switch(config-ip-sla)# udp-jitter 172.30.125.15 2000 num-packets 20 interval 20
To cause a Cisco NX-OS IP Service Level Agreements (SLAs) operation to check each reply packet for data corruption, use the verify-data command. To return to the default value, use the no form of this command.
UDP echo configuration mode (config-ip-sla-udp)
UDP jitter configuration mode (config-ip-sla-jitter)
IP SLA configuration mode (config-ip-sla)
|
|
---|---|
Use the verify-data (IP SLA) command only when data corruption may be an issue. does not enable this feature during normal operation because it can cause unnecessary network overhead.
This example shows how to cause an IP SLAs operation to check each reply packet for data corruption: