Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Medianet Reference Guide - Cisco
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 6<br />
<strong>Medianet</strong> Management and Visibility Design Considerations<br />
<strong>Cisco</strong> Network Analysis Module<br />
Number of Jitter Samples: 16490<br />
Source to Destination Jitter Min/Max: 1/4<br />
Destination to Source Jitter Min/Max: 1/6<br />
Source to destination positive jitter Min/Avg/Max: 1/1/4<br />
Source to destination positive jitter Number/Sum/Sum2: 440/457/505<br />
Source to destination negative jitter Min/Avg/Max: 1/1/4<br />
Source to destination negative jitter Number/Sum/Sum2: 496/512/558<br />
Destination to Source positive jitter Min/Avg/Max: 1/1/6<br />
Destination to Source positive jitter Number/Sum/Sum2: 571/587/679<br />
Destination to Source negative jitter Min/Avg/Max: 1/1/6<br />
Destination to Source negative jitter Number/Sum/Sum2: 513/529/621<br />
Interarrival jitterout: 0 Interarrival jitterin: 0<br />
Packet Loss Values<br />
Loss Source to Destination: 0 Loss Destination to Source: 0<br />
Out Of Sequence: 0 Tail Drop: 0 Packet Late Arrival: 0<br />
Number of successes: 10<br />
Number of failures: 0<br />
Failed Operations due to over threshold: 0<br />
Failed Operations due to Disconnect/TimeOut/Busy/No Connection: 0/0/0/0<br />
Failed Operations due to Internal/Sequence/Verify Error: 0/0/0<br />
Distribution Statistics:<br />
Bucket Range: 0-19 ms<br />
Avg. Latency: 1 ms<br />
Percent of Total Completions for this Range: 100 %<br />
Number of Completions/Sum of Latency: 10/10<br />
Sum of RTT squared low 32 Bits/Sum of RTT squared high 32 Bits: 10/0<br />
Operations completed over thresholds: 0<br />
For the example above, the IPSLA responder was an actual <strong>Cisco</strong> TelePresence CTS-1000. Only IPSLA<br />
responder operations can be configured on <strong>Cisco</strong> TelePresence System endpoints; they cannot function<br />
as IPSLA sources. Configuration is only via the SSH CLI, as shown in Example 6-5.<br />
Example 6-5<br />
IPSLA Responder Configuration on a CTS-1000<br />
admin: utils ipsla responder initiators add net 10.16.1.0/24<br />
admin: utils ipsla responder enable start<br />
The configuration above enables the IPSLA responder function for initiators (senders) on the<br />
10.16.1.0/24 subnet. This corresponds to the source of the IPSLA packets from the <strong>Cisco</strong> Catalyst 6500.<br />
By default, the range of ports enabled on the CTS-1000 is from 32770 to 33000. However, the port range<br />
can be enabled by including start and end ports within the utils ipsla responder enable command. For<br />
a discussion of all the commands available via the SSH CLI, including all the IPSLA commands, see the<br />
<strong>Cisco</strong> TelePresence System Release 1.6 Command-Line Interface <strong>Reference</strong> <strong>Guide</strong> at the following URL:<br />
http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_6/CLI/cts1_6cli.html.<br />
The use of IPSLA as a pre-assessment tool can be disruptive to existing traffic on the IP network<br />
infrastructure. After all, the objective of the pre-assessment test is to see whether the network<br />
infrastructure can support the additional service. For example, if a particular link within the network<br />
infrastructure has insufficient bandwidth, or a switch port has insufficient buffering capacity to support<br />
existing TelePresence traffic as well as the additional traffic generated from the IPSLA pre-assessment<br />
tests, both the existing TelePresence call and the IPSLA operation show degraded quality during the<br />
tests. You must therefore balance the possibility of temporarily degrading production services on the<br />
network against the value of the information gathered from running an IPSLA pre-assessment test during<br />
normal business hours. Running the IPSLA tests after hours may not accurately assess the ability of the<br />
network to handle the additional service, because after-hour traffic patterns may vary significantly from<br />
traffic patterns during normal business hours. Further, running a successful pre-assessment test after<br />
hours may lead to the installation of a production system that then results in degraded quality both for<br />
itself and for other production systems during normal business hours.<br />
OL-22201-01<br />
<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />
6-31