Cisco IOS IP SLA Config

[#Chri5#]

Anyone set this up before? I'm trying a simple config first...

Central - Cisco 878 (SDSL) - 192.168.10.1 (internal VLAN)
Remote - Cisco 877 (ADSL) - 192.168.20.1 (internal VLAN)

There's an IPSEC tunnel between the two routers and you can ping across it from the VLAN interfaces.

On the remote 877, I've done:

ip sla responder

On the central 878, I've got an icmp-echo between the routers working under "ip sla config 1". I'm now trying to add a VoIP jitter monitor but I'm getting a timeout :

newcastle#show ip sla stat 2

Round Trip Time (RTT) for       Index 2
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 11:20:08.046 PCTime Tue Dec 15 2009
Latest operation return code: Timeout
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 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
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 0
        Mean Opinion Score (MOS): 0
Number of successes: 0
Number of failures: 2
Operation time to live: Forever

This is my config for the jitter (g711alaw):

newcastle#show ip sla config 2
IP SLAs, Infrastructure Engine-II.
Entry number: 2
Owner:
Tag:
Type of operation to perform: udp-jitter
Target address/Source address: 192.168.20.1/192.168.10.1
Target port/Source port: 16384/16384
Operation timeout (milliseconds): 5000
Codec Type: g711alaw
Codec Number Of Packets: 1000
Codec Packet Size: 172
Codec Interval (milliseconds): 20
Advantage Factor: 0
Type Of Service parameters: 0x0
Verify data: No
Vrf Name:
Control Packets: enabled
Schedule:
   Operation frequency (seconds): 180  (not considered if randomly scheduled)
   Next Scheduled Start Time: Start Time already passed
   Group Scheduled : FALSE
   Randomly Scheduled : FALSE
   Life (seconds): Forever
   Entry Ageout (seconds): never
   Recurring (Starting Everyday): FALSE
   Status of entry (SNMP RowStatus): Active
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:

Any suggestions to where I'm going wrong?

Cheers,
Chris.

 

[Tui]

You've also got to set up a UDP specific responder with the destination address and port. So on the 877:

ip sla responder udp-echo 192.168.10.1 16384

 

[#Chri5#]

Should the ip address in the ip sla responder by the IP address of the router which is the responder or the one running the probe? The Cisco doc's say "the IP address and port number must match those configured on the source device for the IP SLA operation" which suggests it's the router running the probe.

I've tried both with no joy though.

 

[Tui]

Yes, the address and port should match those of the probe source. The config should have been:
ip sla responder udp-echo ipaddress 192.168.10.1 port 16384

I take it you still have enabled responders on the 877 with:
ip sla responder
Try disabling with no and the re-enabling again - when I tested it seemed any changes to the udp-echo values didn't take affect unless this was done.