Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Cisco Network Analysis Module Chapter 6 Medianet Management and Visibility Design Considerations Table 6-3 SNMP Versions and PDUs Version PDU Description SNMPv1 get-request Command/response mechanism by which an NMS queries a network element for a particular variable SNMPv1 response Command/response mechanism by which an NMS receives information about a particular variable from a network element, based on a previously issued SNMP request message SNMPv1 get-next-request Command/response mechanism that can be used iteratively by an NMS to retrieve sequences of variables from a network element SNMPv1 set-request Issued by an NMS to change the value of a variable on a network element, or to initialize SNMP traps or notifications to be sent from a network element SNMPv1 trap Asynchronous mechanism by which a network elements issues alerts or information about an event to an NMS SNMPv2 get-bulk-request Improved command/response mechanism that can be used by an NMS to retrieve sequences of variables from a network element with a single command SNMPv2 inform-request Provides similar functionality as the trap PDU, but the receiver acknowledges the receipt with a response PDU SNMP traps and/or informs (generically referred to a notifications) can be used to send critical fault management information, such as cold start events, link up or down events, and so on, from a medianet infrastructure device back to an NMS. This may be helpful in troubleshooting issues in which a video session has failed. SNMP GET commands can be used to pull statistics medianet infrastructure devices, which may then be used for assessing performance. Example 6-28 shows basic configuration commands for enabling SNMP on a Cisco Catalyst 6500 Switch. Example 6-28 Sample SNMP Configuration on a Cisco Catalyst 6500 Switch me-westcore-1(config)#snmp-server group group1 v3 priv access 10 me-westcore-1(config)#snmp-server user trapuser group1 v3 auth sha trappassword priv des privacypassword me-westcore-1(config)#snmp-server trap-source Loopback0 me-westcore-1(config)#snmp-server ip dscp 16 6-64 Medianet Reference Guide OL-22201-01
Chapter 6 Medianet Management and Visibility Design Considerations Cisco Network Analysis Module me-westcore-1(config)#snmp-server host 10.17.2.10 version 3 priv trapuser me-westcore-1(config)#snmp-server enable traps me-westcore-1(config)#access-list 10 permit 10.17.2.10 This configuration creates an SNMP group called group1 that uses SNMPv3 and access-list 10 to limit access to only the NMS workstation at IP address 10.17.2.10. A userid called trapuser is associated with the SNMP group. The userid uses Secure Hash Algorithm (SHA) for authentication with password trappassword, and DES for encryption with password privacypassword. The commands snmp-server enable traps and snmp-server host 10.17.2.10 version 3 priv trapuser cause the switch to send SNMP traps to the NMS workstation. Note that this enables all traps available on the Cisco Catalyst switch to be enabled. The network administrator may desire to pare this down to traps applicable to the configuration of the Cisco Catalyst switch. Finally, the switch is configured to send traps using the Loopback0 interface with the DSCP marking of CS2 (note that not all platforms support the ability to set the DSCP marking of SNMP data). The SNMP group information can be displayed with the show snmp group command shown in Example 6-29. Example 6-29 Sample Output From show snmp group Command on a Cisco Catalyst 6500 Switch me-westcore-1#show snmp group groupname: group1 readview : v1default security model:v3 priv writeview: notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F row status: active access-list: 10 Similarly, the SNMP user information can be displayed with the show snmp user command shown in Example 6-30. Example 6-30 Sample Output From show snmp user Command on a Cisco Catalyst 6500 Switch me-westcore-1#show snmp user User name: trapuser Engine ID: 800000090300001874E18540 storage-type: nonvolatile active Authentication Protocol: SHA Privacy Protocol: DES Group-name: group1 Note that the specific management objects that can be accessed via SNMP depend on the platform and software version of the platform. The Cisco MIB Locator, at the following URL, can be helpful in determining supported MIBS: http://tools.cisco.com/ITDIT/MIBS/servlet/index. OL-22201-01 Medianet Reference Guide 6-65
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 182 and 183: 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

Create successful ePaper yourself

Delete template?

Save as template?