Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Cisco Network Analysis Module Chapter 6 Medianet Management and Visibility Design Considerations Class-map: BROADCAST-VIDEO (match-all) 771327514 packets, 1039749488872 bytes 30 second offered rate 0000 bps, drop rate 0000 bps Match: ip dscp cs5 (40) Queueing queue limit 173 packets (queue depth/total drops/no-buffer drops) 0/0/0 (pkts output/bytes output) 771327514/1039749488872 bandwidth 5% (124400 kbps) Class-map: TRANSACTIONAL-DATA (match-all) 0 packets, 0 bytes 30 second offered rate 0000 bps, drop rate 0000 bps Match: ip dscp af21 (18) af22 (20) af23 (22) Queueing queue limit 173 packets (queue depth/total drops/no-buffer drops) 0/0/0 (pkts output/bytes output) 0/0 bandwidth 5% (124400 kbps) Class-map: BULK-DATA (match-all) 0 packets, 0 bytes 30 second offered rate 0000 bps, drop rate 0000 bps Match: ip dscp af11 (10) af12 (12) af13 (14) Queueing queue limit 139 packets (queue depth/total drops/no-buffer drops) 0/0/0 (pkts output/bytes output) 0/0 bandwidth 4% (99520 kbps) Class-map: SCAVENGER (match-all) 79 packets, 6880 bytes 30 second offered rate 0000 bps, drop rate 0000 bps Match: ip dscp cs1 (8) Queueing queue limit 64 packets (queue depth/total drops/no-buffer drops) 0/0/0 (pkts output/bytes output) 79/6880 bandwidth 1% (24880 kbps) Class-map: class-default (match-any) 3209439 packets, 908940688 bytes 30 second offered rate 1000 bps, drop rate 0000 bps Match: any Queueing queue limit 695 packets (queue depth/total drops/no-buffer drops) 0/0/0 (pkts output/bytes output) 3052981/905185696 bandwidth 20% (497600 kbps) Exp-weight-constant: 4 (1/16) Mean queue depth: 1 packets class Transmitted Random dropTail drop Minimum Maximum Mark pkts/bytes pkts/bytes pkts/bytes thresh thresh prob 0 3052981/905185696 0/0 0/0 173 347 1/10 1 0/0 0/0 0/0 194 347 1/10 2 0/0 0/0 0/0 216 347 1/10 3 0/0 0/0 0/0 237 347 1/10 4 0/0 0/0 0/0 259 347 1/10 5 0/0 0/0 0/0 281 347 1/10 6 0/0 0/0 0/0 302 347 1/10 7 0/0 0/0 0/0 324 347 1/10 The main difference between the router and the Cisco Catalyst 4500 switch with Sup6E is that the router implements queues in software. It is therefore not limited to eight egress queues as is the Cisco Catalyst 4500 with Sup6E. Example 6-27 shows the 12-class QoS model implemented with 12 separate egress queues over the OC-48 POS interface. Each class-map entry highlighted in bold corresponds to a queue. With this model, traffic from multiple service classes do not have to share a 6-62 Medianet Reference Guide OL-22201-01
Chapter 6 Medianet Management and Visibility Design Considerations Cisco Network Analysis Module single queue. This can provide a higher level of granularity into the visibility of various video applications, if separate applications are mapped to separate service classes. The traffic rate and drop rate, as well as counts of total packets and bytes outbound, and also counts of total drops for each queue can be seen from the show policy-map interface command when such a policy map is applied to the interface. Simple Network Management Protocol The Simple Network Management Protocol (SNMP) refers both to a specific protocol used to collect information and configure devices over an IP network, as well as an overall Internet-standard network management framework. The SNMP network management framework consists of the following components: • Network management stations (NMSs)—Typically a server that runs network management applications, which in turn uses the SNMP protocol to monitor and control network elements. • Network elements—The actual managed devices (routers, switches, TelePresence codecs, and so on) on the IP network. • Agents—Software components running within network elements that collect and store management information. • Managed objects—Specific characteristics of network elements that can be managed. Objects can be single entities or entire tables. Specific instances of managed objects are often referred to as variables. • Management information bases (MIBs)—Collections of related management objects. MIBs define the structure of the management data through a hierarchical namespace using object identifiers (OIDs). Each OID describes a particular variable that can either be read from a managed object or set on a managed object. MIBs can be standards-based or proprietary. Because SNMP management information uses a hierarchical namespace, individual vendors can extend the management capabilities of their products through proprietary MIBs, which are typically published. Currently, three versions of SNMP are commonly deployed: • SNMPv1—The initial version introduced in the late 1980s. The security model used by SNMPv1 consists of authentication only, using community strings (read-only and read/write) that are sent in clear text within SNMP messages. Because of this, SNMPv1 is considered inherently insecure, and read/write capability should be used with caution, even over private networks. • SNMPv2c—Proposed in the mid 1990s. The “c” in SNMPv2c indicates a simplified version of SNMPv2 that also uses a security model based on community strings. SNMPv2 improved the performance of SNMPv1 by introducing features such as the get-bulk-request protocol data unit (PDU) and notifications, both listed in Table 6-3. However, because SNMPv2c still uses the same security model as SNMPv1, read/write capability should be used with caution. • SNMPv3—Introduced in the early 2000s, and is currently defined primarily under IETF RFCs 3411-3418. A primary benefit of SNMPv3 is its security model, which eliminates the community strings of SNMPv1 and SNMPv2. SNMPv3 supports message integrity, authentication, and encryption of messages; allowing both read and read/write operation over both public and private networks. As mentioned above, the SNMP protocol defines a number of PDUs, some of which are shown in Table 6-3, along with the particular version of SNMP that supports them. These PDUs are essentially the commands for managing objects through SNMP. OL-22201-01 Medianet Reference Guide 6-63
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:
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 234 and 235: Application-Specific Management Fun
Page 250 and 251: Summary Chapter 6 Medianet Manageme
Page 252 and 253: Auto Smartports Chapter 7 Medianet
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?