[c-nsp] Using IP SLA to monitor a multicast network? Is it supported or possible?

[P C]

I would like to use IP SLA to monitor udp jitter/loss over multicast.  Is
this supported?  What about just packet loss?

I can't find any mention of if it can be done or not in the documentation.
The only mention on google I found is from 6 years ago here (see pdf pages
85-87):
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6552/prod_presentation0900aecd806694e4.pdf

At the time it seemed the message was "try again later".

Regardless, I decided to try anyways without much luck.  The control packets
get to the destination just fine by multicast as shown by the sender and
receiver, but the host never seems to send the data packets, instead
claiming "No connection" in the show ip sla commands.  In some cases, it
would say "1997" packets tail dropped (out of 2000).

I only tried the udp-jitter option, but perhaps one of the others which
don't require a responder might be more suitable.  I'm ok with data
collection only being at the receiver.

Or more likely, it's just not possible.

Various config/show commands below.


config:

-------ip sla sender------

ip sla 1
 udp-jitter 232.1.100.1 5555 source-ip 1.1.1.1 num-packets 2000 interval 4
 request-data-size 64

int loopback0
 ip pim sparse-mode
 ip addr 1.1.1.1 255.255.255.255


mroute shows traffic sent by the IP SLA:

(1.1.1.1, 232.1.100.1), 00:36:16/00:02:42, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet0/0, Forward/Sparse, 00:36:16/00:02:42

Group: 232.1.100.1, Source count: 1, Packets forwarded: 12, Packets
received: 12
  Source: 1.1.1.1/32, Forwarding: 12/0/80/0, Other: 12/0/0

show ip sla statistics:
#show ip sla statistics
IPSLAs Latest Operation Statistics

IPSLA operation id: 1
Type of operation: udp-jitter
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: *01:58:39.317 UTC Sat Mar 5 2011
Latest operation return code: No connection
RTT Values:
        Number Of RTT: 0                RTT Min/Avg/Max: 0/0/0 milliseconds
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0
milliseconds
        Destination to Source Latency one way Min/Avg/Max: 0/0/0
milliseconds
Jitter Time:
        Number of SD Jitter Samples: 0
        Number of DS Jitter Samples: 0
        Source to Destination Jitter Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Jitter Min/Avg/Max: 0/0/0 milliseconds
Packet Loss Values:
        Loss Source to Destination: 0           Loss Destination to Source:
0
        Out Of Sequence: 0      Tail Drop: 0
        Packet Late Arrival: 0  Packet Skipped: 0
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 0
        Mean Opinion Score (MOS): 0
Number of successes: 0
Number of failures: 1
Operation time to live: 0




---------ip sla responder-----------

interface Loopback0
 ip address 2.2.2.2 255.255.255.255
 ip pim sparse-mode
 ip igmp join-group 232.1.100.1 source 1.1.1.1

show ip sla responder
IP SLAs Responder is: Enabled
Number of control message received: 27 Number of errors: 0
Recent sources:
        1.1.1.1 [01:54:57.463 UTC Sat Mar 5 2011]
        1.1.1.1 [01:54:52.459 UTC Sat Mar 5 2011]
        1.1.1.1 [01:54:47.459 UTC Sat Mar 5 2011]
        1.1.1.1 [01:52:57.703 UTC Sat Mar 5 2011]
        1.1.1.1 [01:52:52.699 UTC Sat Mar 5 2011]
Recent error sources:

udpEcho Responder: