Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Solution Chapter 1 Medianet Architecture Overview Cisco Catalyst switching product lines have industry-leading high-availability features including VSS and NSF/SSO. When deployed with best practices network design recommendations, including routed access designs for the campus switching network, media applications with even the strictest tolerances can be readily supported. Bandwidth, Burst, and Power Application Intelligence and QoS As discussed earlier, provisioning adequate bandwidth is a key objective when supporting many types of media applications, especially interactive real-time media applications such as Cisco TelePresence. In the access layer of the campus switching network, consider upgrading switch ports to Gigabit Ethernet (GE). This provides sufficient bandwidth for high-definition media capable endpoints. In the distribution and core layers of the campus switching network, consider upgrading links to 10 Gigabit Ethernet (10GE), allowing aggregation points and the core switching backbone to handle the traffic loads as the number of media endpoints and streams increases. Additionally, ensure that port interfaces have adequate buffering capacity to handle the burstiness of media applications, especially video-oriented media applications. The amount of buffering needed depends on the number and type of media applications traversing the port. Finally, the campus infrastructure can also supply Power-over-Ethernet to various media endpoints, such as IP video surveillance cameras and other devices. Having a comprehensive QoS strategy can protect critical media applications including VoIP and video, as well as protect the campus switching network from the effects of worm outbreaks. The Cisco Catalyst switching products offer industry-leading QoS implementations, accelerated with low-latency hardware ASICs, which are critical for ensuring the service level for media applications. QoS continues to evolve to include more granular queuing, as well as additional packet identification and classification technologies. One advance is the Cisco Programmable Intelligent Services Adapter (PISA), which employs deeper packet inspection techniques mappable to service policies. Intelligent features like PISA will continue to evolve at the network edge to allow application intelligence, enabling the network administrator to prioritize critical applications while at the same time control and police unmanaged or unwanted applications which may consume network resources. Once traffic has been classified and marked, then queuing policies must be implemented on every node where the possibility of congestion could occur (regardless of how often congestion scenarios actually do occur). This is an absolute requirement to guarantee service levels. In the campus, queuing typically occurs in very brief bursts, usually only lasting a few milliseconds. However, due to the speeds of the links used within the campus, deep buffers are needed to store and re-order traffic during these bursts. Additionally, within the campus, queuing is performed in hardware, and as such, queuing models will vary according to hardware capabilities. Obviously, the greater the number of queues supported, the better, as this presents more policy flexibility and granularity to the network administrator. Four queues would be considered a minimum (one strict-priority queue, one guaranteed bandwidth queue, one default queue, and one deferential queue). Similarly, Catalyst hardware that supports DSCP-to-Queue mappings would be preferred, as these (again) present the most granular QoS options to the administrator. Consider an example, the Catalyst 6500 WS-X6708-10G, which provides a 1P7Q4T queuing model, where: • 1P represents a single, strict-priority queue • 7Q represents 7 non-priority, guaranteed-bandwidth queues • 4T represents 4 dropping thresholds per queue 1-26 Medianet Reference Guide OL-22201-01
Chapter 1 Medianet Architecture Overview Solution Additionally, the WS-X6708-10G supports DSCP-to-Queue mapping, providing additional policy granularity. With such a linecard, voice, video, and data applications could be provisioned as shown in Figure 1-11. Figure 1-11 Campus Medianet Queuing Model Example Application DSCP 1P7Q4T Voice Broadcast Video EF CS5 EF CS5 CS4 Q8 (PQ) Realtime Interactive Multimedia Conferencing Multimedia Streaming Network Control Internetwork Control Call Signaling Network Management Transactional Data CS4 AF4 AF3 (CS7) CS6 CS3 CS2 AF2 AF4 AF3 CS7 CS6 CS3 CS2 AF2 AF1 Q7 (10% ) Q6 (10%) Q5 (10%) Q4 (10%) Q3 (10%) Q6T4 Q6T3 Q6T2 Q6T1 Bulk Data AF1 DF/0 Q2 (25%) Best Effort DF Scavenger CS1 CS1 Q1 (5%) 224552 Broadcast Optimization with IP Multicast IP multicast is an important part of many campus switching network designs, optimizing the broadcast of one-to-many streams across the network. Cisco Catalyst switching products provide industry-leading IP multicast proven in business critical network implementations. The IPmc foundation offers further value in networks in optimizing broadcast streaming. Leveraging Network Virtualization for Restricted Video Applications The objective of many media applications is to improve effectiveness of communication and collaboration between groups of people. These applications typically have a fairly open usage policy, meaning that they are accessible by and available to a large number of employees in the company. Other media applications have more restrictive access requirements, and are only available to a relatively small number of well defined users. For example, IP video surveillance is typically available to the Safety and Security department. Access to Digital Signage may only be needed by the few content programmers and the sign endpoints themselves. Additionally, it would generally be prudent to restrict visiting guests from on-demand or streaming content that is confidential to the company. OL-22201-01 Medianet Reference Guide 1-27
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 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: Network Availability Technologies C
Page 88 and 89:
Network Availability Technologies C
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:
Page 150 and 151:
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 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
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 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Cisco Network Analysis Module Chapt
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Application-Specific Management Fun
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
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

Create successful ePaper yourself

Delete template?

Save as template?