Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Cisco Network Analysis Module Chapter 6 Medianet Management and Visibility Design Considerations Avg. Latency: 0 ms Percent of Total Completions for this Range: 100 % Number of Completions/Sum of Latency: 10/3 Sum of RTT squared low 32 Bits/Sum of RTT squared high 32 Bits: 3/0 Operations completed over thresholds: 0 Round trip time (RTT) Index 25 Start Time Index: .10:53:07.856 EST Mon Nov 16 2009 Type of operation: jitter Voice Scores: MinOfICPIF: 0 MaxOfICPIF: 0 MinOfMOS: 0 MaxOfMOS: 0 RTT Values Number Of RTT: 94672 RTT Min/Avg/Max: 1/1/8 Latency one-way time milliseconds Number of Latency one-way Samples: 0 Source to Destination Latency one way Min/Max: 0/0 Destination to Source Latency one way Min/Max: 0/0 Source to Destination Latency one way Sum/Sum2: 0/0 Destination to Source Latency one way Sum/Sum2: 0/0 Jitter time milliseconds Number of Jitter Samples: 94662 Source to Destination Jitter Min/Max: 1/4 Destination to Source Jitter Min/Max: 1/7 Source to destination positive jitter Min/Avg/Max: 1/1/3 Source to destination positive jitter Number/Sum/Sum2: 2498/2559/2691 Source to destination negative jitter Min/Avg/Max: 1/1/4 Source to destination negative jitter Number/Sum/Sum2: 2553/2620/2778 Destination to Source positive jitter Min/Avg/Max: 1/1/7 Destination to Source positive jitter Number/Sum/Sum2: 4470/4511/4725 Destination to Source negative jitter Min/Avg/Max: 1/1/6 Destination to Source negative jitter Number/Sum/Sum2: 4413/4448/4622 Interarrival jitterout: 0 Interarrival jitterin: 0 Packet Loss Values Loss Source to Destination: 0 Loss Destination to Source: 0 Out Of Sequence: 0 Tail Drop: 0 Packet Late Arrival: 0 Number of successes: 10 Number of failures: 0 Failed Operations due to over threshold: 0 Failed Operations due to Disconnect/TimeOut/Busy/No Connection: 0/0/0/0 Failed Operations due to Internal/Sequence/Verify Error: 0/0/0 Distribution Statistics: Bucket Range: 0-19 ms Avg. Latency: 0 ms Percent of Total Completions for this Range: 100 % Number of Completions/Sum of Latency: 10/5 Sum of RTT squared low 32 Bits/Sum of RTT squared high 32 Bits: 5/0 Operations completed over thresholds: 0 Round trip time (RTT) Index 26 Start Time Index: .10:53:02.892 EST Mon Nov 16 2009 Type of operation: jitter Voice Scores: MinOfICPIF: 0 MaxOfICPIF: 0 MinOfMOS: 0 MaxOfMOS: 0 RTT Values Number Of RTT: 16500 RTT Min/Avg/Max: 1/1/8 Latency one-way time milliseconds Number of Latency one-way Samples: 0 Source to Destination Latency one way Min/Max: 0/0 Destination to Source Latency one way Min/Max: 0/0 Source to Destination Latency one way Sum/Sum2: 0/0 Destination to Source Latency one way Sum/Sum2: 0/0 Jitter time milliseconds 6-30 Medianet Reference Guide OL-22201-01
Chapter 6 Medianet Management and Visibility Design Considerations Cisco Network Analysis Module Number of Jitter Samples: 16490 Source to Destination Jitter Min/Max: 1/4 Destination to Source Jitter Min/Max: 1/6 Source to destination positive jitter Min/Avg/Max: 1/1/4 Source to destination positive jitter Number/Sum/Sum2: 440/457/505 Source to destination negative jitter Min/Avg/Max: 1/1/4 Source to destination negative jitter Number/Sum/Sum2: 496/512/558 Destination to Source positive jitter Min/Avg/Max: 1/1/6 Destination to Source positive jitter Number/Sum/Sum2: 571/587/679 Destination to Source negative jitter Min/Avg/Max: 1/1/6 Destination to Source negative jitter Number/Sum/Sum2: 513/529/621 Interarrival jitterout: 0 Interarrival jitterin: 0 Packet Loss Values Loss Source to Destination: 0 Loss Destination to Source: 0 Out Of Sequence: 0 Tail Drop: 0 Packet Late Arrival: 0 Number of successes: 10 Number of failures: 0 Failed Operations due to over threshold: 0 Failed Operations due to Disconnect/TimeOut/Busy/No Connection: 0/0/0/0 Failed Operations due to Internal/Sequence/Verify Error: 0/0/0 Distribution Statistics: Bucket Range: 0-19 ms Avg. Latency: 1 ms Percent of Total Completions for this Range: 100 % Number of Completions/Sum of Latency: 10/10 Sum of RTT squared low 32 Bits/Sum of RTT squared high 32 Bits: 10/0 Operations completed over thresholds: 0 For the example above, the IPSLA responder was an actual Cisco TelePresence CTS-1000. Only IPSLA responder operations can be configured on Cisco TelePresence System endpoints; they cannot function as IPSLA sources. Configuration is only via the SSH CLI, as shown in Example 6-5. Example 6-5 IPSLA Responder Configuration on a CTS-1000 admin: utils ipsla responder initiators add net 10.16.1.0/24 admin: utils ipsla responder enable start The configuration above enables the IPSLA responder function for initiators (senders) on the 10.16.1.0/24 subnet. This corresponds to the source of the IPSLA packets from the Cisco Catalyst 6500. By default, the range of ports enabled on the CTS-1000 is from 32770 to 33000. However, the port range can be enabled by including start and end ports within the utils ipsla responder enable command. For a discussion of all the commands available via the SSH CLI, including all the IPSLA commands, see the Cisco TelePresence System Release 1.6 Command-Line Interface Reference Guide at the following URL: http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_6/CLI/cts1_6cli.html. The use of IPSLA as a pre-assessment tool can be disruptive to existing traffic on the IP network infrastructure. After all, the objective of the pre-assessment test is to see whether the network infrastructure can support the additional service. For example, if a particular link within the network infrastructure has insufficient bandwidth, or a switch port has insufficient buffering capacity to support existing TelePresence traffic as well as the additional traffic generated from the IPSLA pre-assessment tests, both the existing TelePresence call and the IPSLA operation show degraded quality during the tests. You must therefore balance the possibility of temporarily degrading production services on the network against the value of the information gathered from running an IPSLA pre-assessment test during normal business hours. Running the IPSLA tests after hours may not accurately assess the ability of the network to handle the additional service, because after-hour traffic patterns may vary significantly from traffic patterns during normal business hours. Further, running a successful pre-assessment test after hours may lead to the installation of a production system that then results in degraded quality both for itself and for other production systems during normal business hours. OL-22201-01 Medianet Reference Guide 6-31
Page 1 and 2:
Medianet Reference Guide Last Updat
Page 3:
About the Authors Solution Authors
Page 6 and 7:
Contents Application Intelligence a
Page 8 and 9:
Contents The Globalization of the W
Page 10 and 11:
Contents NetFlow Collector Consider
Page 12 and 13:
Contents viii Medianet Reference Gu
Page 14 and 15:
Business Drivers for Media Applicat
Page 16 and 17:
Business Drivers for Media Applicat
Page 18 and 19:
Challenges of Medianets Chapter 1 M
Page 20 and 21:
Challenges of Medianets Chapter 1 M
Page 22 and 23:
Solution Chapter 1 Medianet Archite
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Conclusions Chapter 1 Medianet Arch
Page 48 and 49:
Related Documents Chapter 1 Mediane
Page 50 and 51:
Related Documents Chapter 1 Mediane
Page 52 and 53:
Measuring Bandwidth Chapter 2 Media
Page 54 and 55:
Packet Flow Malleability Chapter 2
Page 56 and 57:
Shapers Chapter 2 Medianet Bandwidt
Page 58 and 59:
Shapers versus Policers Chapter 2 M
Page 60 and 61:
Shapers versus Policers Chapter 2 M
Page 62 and 63:
Converged Video Chapter 2 Medianet
Page 64 and 65:
Bandwidth Over Subscription Chapter
Page 66 and 67:
Capacity Planning Chapter 2 Mediane
Page 68 and 69:
Load Balancing Chapter 2 Medianet B
Page 70 and 71:
EtherChannel Chapter 2 Medianet Ban
Page 72 and 73:
Bandwidth Conservation Chapter 2 Me
Page 74 and 75:
Summary Chapter 2 Medianet Bandwidt
Page 76 and 77:
Network Availability Chapter 3 Medi
Page 78 and 79:
Network Availability Chapter 3 Medi
Page 80 and 81:
Device Availability Technologies Ch
Page 82 and 83:
Device Availability Technologies Ch
Page 84 and 85:
Network Availability Technologies C
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Operational Availability Technologi
Page 106 and 107:
Summary Chapter 3 Medianet Availabi
Page 108 and 109:
Drivers for QoS Design Evolution Ch
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Cisco QoS Toolset Chapter 4 Mediane
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Enterprise Medianet Strategic QoS R
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149: Enterprise Medianet Strategic QoS R
Page 150 and 151: Enterprise Medianet Strategic QoS R
Page 152 and 153: References Chapter 4 Medianet QoS D
Page 154 and 155: References Chapter 4 Medianet QoS D
Page 156 and 157: An Introduction to Securing a Media
Page 166 and 167: Medianet Security Reference Documen
Page 168 and 169: Medianet Security Reference Documen
Page 170 and 171: Network-Embedded Management Functio
Page 180 and 181: Cisco Network Analysis Module Chapt
Page 234 and 235: Application-Specific Management Fun
Page 248 and 249:
Application-Specific Management Fun
Page 250 and 251:
Summary Chapter 6 Medianet Manageme
Page 252 and 253:
Auto Smartports Chapter 7 Medianet
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Location Services Chapter 7 Mediane
Page 278 and 279:
Summary Chapter 7 Medianet Auto Con
Page 280:
References Chapter 7 Medianet Auto
show all

Medianet Reference Guide - Cisco

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?