- IP SLAs Overview
- Configuring Auto IP SLAs in IP SLAs Engine 3.0
- Configuring IP SLA - Percentile Support for Filtering Outliers
- Configuring IP SLAs Video Operations
- Configuring IP SLAs UDP Jitter Operations
- IP SLA - Support for OnDemand UDP Probes
- Configuring IP SLAs UDP Jitter Operations for VoIP
- IP SLAs Multicast Support
- Configuring IP SLAs LSP Health Monitor Operations
- Configuring IP SLAs for Metro-Ethernet
- Configuring Cisco IP SLAs ICMP Jitter Operations
- Configuring RTP-Based VoIP Operations
- Configuring VoIP Gatekeeper Registration Delay Operations
- Configuring VoIP Call Setup Monitoring
- Configuring IP SLAs UDP Echo Operations
- Configuring IP SLAs HTTP Operations
- Configuring IP SLAs TCP Connect Operations
- Configuring IP SLAs ICMP Echo Operations
- Configuring IP SLAs ICMP Path Echo Operations
- Configuring IP SLAs ICMP Path Jitter Operations
- Configuring IP SLAs FTP Operations
- Configuring IP SLAs DNS Operations
- Configuring IP SLAs DHCP Operations
- Configuring IP SLAs DLSw+ Operations
- Configuring an IP SLAs Multioperation Scheduler
- Configuring Proactive Threshold Monitoring for IP SLAs Operations
- IP SLAs TWAMP Responder
- Finding Feature Information
- Prerequisites for IP SLAs Multicast Support
- Restrictions for IP SLAs Multicast Support
- Information About IP SLAs Multicast Support
- How to Configure IP SLAs Multicast Support
IP SLAs Multicast Support
This module describes how to configure and schedule an IP Service Level Agreements (SLAs) multicast UDP jitter operation for measuring and reporting statistics such as one way latency, jitter, and packet loss for each multicast receiver in a user-specified multicast group. .
- Finding Feature Information
- Prerequisites for IP SLAs Multicast Support
- Restrictions for IP SLAs Multicast Support
- Information About IP SLAs Multicast Support
- How to Configure IP SLAs Multicast Support
- Configuration Examples for IP SLAs Multicast Support
- Additional References for IP SLAs Multicast Support
- Feature Information for IPSLA Multicast Support
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for IP SLAs Multicast Support
Time synchronization, such as that provided by Network Time Protocol (NTP), is required between the source and the target device in order to provide accurate one-way delay (latency) measurements. To configure NTP on the source and target devices, perform the tasks in the "Performing Basic System Management" chapter of the Network Management Configuration Guide. Time synchronization is not required for the one-way jitter and packet loss measurements. However, if the time is not synchronized between the source and target devices, one-way jitter and packet loss data will be returned, but values of "0" will be returned for the one-way delay measurements provided by the UDP jitter operation.
All devices must be part of the same VRF in order for IP SLAs multicast operations to succeed.
The devices on which the responder and probe are to configured must both be running Cisco software images that support the IP SLAs Multicast Support feature. Before configuring any IP SLAs application, use the show ip sla application command to verify that the operation type is supported on your software image.
Restrictions for IP SLAs Multicast Support
The multicast UDP Jitter operation can provide only One Way (OW) data.
Information About IP SLAs Multicast Support
Multicast UDP Jitter Operations
Analyze and evaluate the performance of a multicast network after deploying a new multicast network application or implementing new multicast-based protocols on the network.
Check the network behavior for multicast before actually utilizing the multicast network for an important event.
Take a proactive approach to monitoring a network to isolate possible problem areas.
The sender in a multicast UDP jitter operation sends UDP packets at a specified interval from the source device to a multicast IP address. During the initial configuration, a specified endpoint list provides a list of all the responders to be contacted for a given multicast operation. The multicast subsystem sends a unicast control packet to each of the multicast receivers in the endpoint list, utilizing the unicast path. A control message is sent to each receiver so that it can join the multicast group.
The IP SLAs multicast responder on the multicast receiver receives the UDP packets and records the time-stamp data.
A list of valid responders that have completed a successful IGMP join is maintained on the sender side. Once the responder list is received, multicast packet generation can proceed.
Because all multicast traffic is one way, from sender on the source to responder on the receiver, each responder that is part of the operation is responsible for performing local calculations and for storing the statistics. The statistics are sent back to the sender to be displayed at the end of each cycle of the operation (after all packets have been transmitted to the responder). Because the responder does not maintain a history of the statistics, and also releases all associated memory after sending the information to the sender, each scheduled operation (based on the frequency) is considered a new operation by the multicast responder, with no relationship to the previous one.
Multicast UDP jitter operations are supported in IPv4 networks.
How to Configure IP SLAs Multicast Support
Configuring the IP SLAs Responder on a Destination Device
Note | A responder should not configure a permanent port for a sender. If the responder configures a permanent port for a sender, even if the packets are successfully sent (no timeout or packet-loss issues), the jitter value is zero. |
DETAILED STEPS
Creating a List of Multicast Responders on the Source Device
All responders to be added to the endpoint list (of responders) must first be configured on the destination device. For configuration information, see the "Configuring an IP SLAs Responder on the Destination Device" section.
1.
enable
2.
configure
terminal
3.
ip
sla
endpoint-list
type
ip
template-name
4.
description
description
5.
ip-address
address
[-address
|
,
...
,
address]
port
port
6.
end
7.
show
ip
sla endpoint-list
[type
ip
[template-name]]
DETAILED STEPS
Configuring Multicast UDP Jitter Operations
Note |
|
1.
enable
2.
configure
terminal
3.
ip
sla
operation-number
4.
udp-jitter
{destination-ip-address |
destination-hostname}
destination-port
endpoint-list
endpoint-list [ssm]
[source-ip
ip-address] [source-port
port-number] [num-packets
number-of-packets] [interval
interpacket-interval]
5.
control retry
retries
6.
control timeout
seconds
7.
dscp
dscp-value
8.
tree-init
number
9.
history
distributions-of-statistics-kept
size
10.
history
enhanced
[interval
seconds] [buckets
number-of-buckets]
11.
frequency
seconds
12.
history
hours-of-statistics-kept
hours
13.
owner
owner-id
14.
request-data-size
bytes
15.
history
statistics-distribution-interval
milliseconds
16.
tag
text
17.
threshold
milliseconds
18.
timeout
milliseconds
19.
tos
number
20.
verify-data
21.
vrf
vrf-name
22.
end
23.
show
ip
sla
configuration
[operation-number]
DETAILED STEPS
Scheduling IP SLAs Operations
- ip sla schedule operation-number [life {forever | seconds}] [start-time {[hh:mm:ss] [month day | day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
- ip sla group schedule group-operation-number operation-id-numbers {schedule-period schedule-period-range | schedule-together} [ageout seconds] frequency group-operation-frequency [life {forever | seconds}] [start-time {hh:mm [:ss] [month day | day month] | pending | now | after hh:mm [:ss]}]
1.
enable
2.
configure
terminal
3.
Enter one of
the following commands:
4.
end
5.
show
ip
sla
group
schedule
6.
show
ip
sla
configuration
DETAILED STEPS
Troubleshooting Tips
If the IP Service Level Agreements (SLAs) operation is not running and not generating statistics, add the verify-data command to the configuration (while configuring in IP SLA configuration mode) to enable data verification. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.
Use the debug ip sla trace and debug ip sla error commands to help troubleshoot issues with an IP SLAs operation.
What to Do Next
To add proactive threshold conditions and reactive triggering for generating traps (or for starting another operation) to an IP Service Level Agreements (SLAs) operation, see the “Configuring Proactive Threshold Monitoring” section.
Configuration Examples for IP SLAs Multicast Support
Example: Multicast UDP Jitter Operation
Device# show ip sla endpoint-list Endpoint-list Name: multicast Description: ip-address 192.0.2.1 port 1111 ip-address 192.0.2.2 port 2222 ip-address 192.0.2.3 port 3333
Device# show ip sla configuration 22 IP SLAs Infrastructure Engine-III Entry number: 22 Owner: Tag: Operation timeout (milliseconds): 5000 Type of operation to perform: udp-jitter Target address/Source address: 224.1.1.1/0.0.0.0 Target port/Source port: 2460/0 Type Of Service parameter: 0x0 Request size (ARR data portion): 32 Packet Interval (milliseconds)/Number of packets: 20/10 Verify data: No Vrf Name: Control Packets: enabled Schedule: Operation frequency (seconds): 60 (not considered if randomly scheduled) Next Scheduled Start Time: Pending trigger Group Scheduled : FALSE Randomly Scheduled : FALSE Life (seconds): 3600 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): notInService Threshold (milliseconds): 5000 Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History: sno oper-id dest-ip-addr !<---Responders in endpoint list: multicast 1 976271337 192.0.2.1 2 1632881300 192.0.2.2 3 2138021658 192.0.2.3
Additional References for IP SLAs Multicast Support
Related Documents
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
IP SLAs commands |
|
Information about Cisco IP SLAs |
“Cisco IOS IP SLAs Overview” module of the IP SLAs Configuration Guide |
MIBs
MIB |
MIBs Link |
---|---|
CISCO-IPSLA-TC-MIB |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for IPSLA Multicast Support
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.Feature Name |
Releases |
Feature Information |
---|---|---|
IPSLA Multicast Support |
15.2(4)M 15.3(1)S Cisco IOS XE Release 3.8S 15.1(2)SG Cisco IOS XE Release 3.4SG |
This feature introduced the multicast UDP jitter operation for measuring and reporting statistics such as one way latency, jitter, and packet loss for each multicast receiver in a user-specified multicast group. The following commands were introduced or modified: clock-tolerance ntp oneway, control (IP SLA), dscp (IP SLA), history distributions-of-statistics-kept, history enhanced, history hours-of-statistics-kept, ip-address (endpoint list), operation-packet priority, owner, precision, show ip sla application, show ip sla configuration, show ip sla endpoint-list, show ip sla statistics, show ip sla statistics aggregated, tag (IP SLA), timeout (IP SLA), tos, tree-init, udp-jitter, verify-data (IP SLA), vrf. |