Hey Adam,
Looks good I wanted to keep it vague to show that all that really matters is what is in front of you and in this case it is "Monitor" and "Jitter" between devices. I struggled in the past with not having all (what I believe is all) the requirements but learned that all I needed to do was meet the requirement. Some things that were left up to you were type, codec, ports, etc. I believe "ip sla" is only on legacy IOS's and the newer IOS's use "ip sla monitor" - Please correct me if I am wrong I would like to how others put their solutions together Thanks Adam! From: Adam Booth [mailto:[email protected]] Sent: October-29-10 12:34 AM To: Jason Maynard Cc: [email protected] Subject: Re: [OSL | CCIE_RS] Question 160 Hi Jason, There's a number of jitter measurement options available using ip sla, I took the assumption that since your picture had IP phones, that udp jitter simulating a voip call may be appropriate. Below are my proposed configs. hostname R1 ! interface FastEthernet0/0 ip address 10.0.0.1 255.255.255.0 no shutdown ! ip sla 10 udp-jitter 10.0.0.2 16384 codec g729a ip sla schedule 10 life forever start-time now hostname R2 ! interface FastEthernet0/0 ip address 10.0.0.2 255.255.255.0 no shutdown ! ip sla responder R1#sh ip sla stati 10 Round Trip Time (RTT) for Index 10 Latest RTT: 22 milliseconds Latest operation start time: *00:14:19.003 UTC Fri Mar 1 2002 Latest operation return code: OK RTT Values: Number Of RTT: 1000 RTT Min/Avg/Max: 1/22/493 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: 999 Number of DS Jitter Samples: 999 Source to Destination Jitter Min/Avg/Max: 0/17/67 milliseconds Destination to Source Jitter Min/Avg/Max: 0/7/496 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): 4209067962 MOS score: 4.50 Number of successes: 1 Number of failures: 0 Operation time to live: Forever It is possible to reflect the configuration for R1 and R2 but since we get both Source to Destination and Destination to Source jitter this way, it's probably not required. Cheers, Adam On Fri, Oct 29, 2010 at 1:30 PM, Jason Maynard <[email protected]> wrote: Here is another question to test your skills. What would you configure to monitor jitter? You must provide an example using R1 and R2. <http://4.bp.blogspot.com/_RcSjgG49QBc/TMo8YRb73lI/AAAAAAAAAEY/SD-bnXKSdXM/s 1600/Phone.png> Error! Filename not specified. Error! Filename not specified. Error! Filename not specified. _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
