Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Auto Smartports Chapter 7 Medianet Auto Configuration Table 7-6 Policies Associated With ASP Detectors Detector Policy Event 1 neighbor-discovery Mandatory.link.sh link-event down 2 neighbor-discovery Mandatory.link2.sh link-event admindown 3 neighbor-discovery Mandatory.lldp.sh lldp update 4 mat Mandatory.mat.sh use-mat-db yes hold-down 65.000 5 neighbor-discovery Mandatory.cdp.sh cdp update 6 identity Mandatory.identity.sh aaa-attribute {auto-smart-port} As an example, when a link-event down occurs, neighbor discovery will run the script Mandatory.link.sh. Details of the script can be seen with the command: sh macro auto event manager policy registered detailed The scripts can be read with a little background in programming. It is possible to register user-generated scripts, although the details of that procedure are not included in this document. There are significant differences in the system scripts packaged in Auto Smartports and those found in Enhanced Auto Smartports. Each script fetches information from the router configuration, such as the current macro description. Based on the calling event, passed variables, and interface configuration, the policy script generates a trigger. Triggers are mapped to shell functions. This mapping can be seen with the command: sh shell trigger This displays all of the mapped triggers. However ASP is only relevant to those triggers that map to a function that contains AUTO_SMARTPORT in the function name. Arguments are passed into the shell function from the trigger. Common arguments include $LINKUP, $INTERFACE, $TRIGGER, and $ACCESS_VLAN. With this information, the function applies the appropriate configuration to the interface of the switch. The functions can be customized. The shell function details can be seen with the command: show shell function As an example, consider the case were a CDP packet is received on an interface that was previously configured with the appropriate ASP configuration. Neighbor-discovery calls the script Mandatory.cdp.sh. The script first checks to see if CDP detection is available; if so, then the CDP capabilities are checked. If the host bit is set, then the CDP platform type is compared against known types. The previous trigger is noted by pulling the macro description from the interface configuration. Another check is made to see if discovery is enabled for that particular type of device. If so, then the script continues to check the other capabilities bits for Phone, Access Point, Router, or Switch. If the host bit is set in conjunction with the phone bit, then the phone trigger takes precedence. Finally a trigger is generated and mapped to a shell function. Different policies can generate the same trigger. For example, both Mandatory.link.sh and Mandatory.cdp.sh can generate a CISCO_DMP_EVENT trigger, but pass the variable LINKUP with a different value into the shell function. The event policy has the logic to handle various situations, such as the case where the new trigger is the same as the previous trigger that was last used to configure the interface. The event policy also checks to see if the interface is configured with a sticky macro. These are not removed when the link is down. As discussed previously, this could result in an err_disabled state if a different device is attached to a sticky interface with port security. Sticky configurations should not be used if the intent is to dynamically configure the interface based on device discovery when devices move from port to port. The relationship between the various components is shown in Figure 7-2. The example flow shows the result of a CDP event. 7-8 Medianet Reference Guide OL-22201-01
Chapter 7 Medianet Auto Configuration Auto Smartports Figure 7-2 Auto Smartports Event Flow Link Down CISCO_DMP_EVENT CISCO_DMP_AUTO_SMAR TPORT CISCO_DMP_AUTO_SMAR TPORT UP / DOWN Rx Packet cdp lldp Radius MAC Address Neighbor Identity Detection Manager sh macro auto event manager detector all sh macro auto event manager history events Link Admin Down MAC Address CDP LLDP MAB Policy Manager CISCO_IPVSC_EVENT CISCO_IP_CAMERA_AUTO _SMARTPORT CISCO_LAST_RESORT EVENT flash:/overridden_ last_resort.txt CISCO_PHONE_EVENT CISCO_PHONE_AUTO_SM ARTPORT CISCO_ROUTER_EVENT CISCO_ROUTER_AUTO_S MARTPORT CISCO_SWITCH_EVENT CISCO_SWITCH_AUTO_SM ARTPORT Trigger Mappings CISCO_IP_CAMERA_AUTO _SMARTPORT UP/DOWN flash:/overridden_last_res ort.txt UP/DOWN CISCO_PHONE_AUTO_SM ARTPORT UP/DOWN CISCO_ROUTER_AUTO_S MARTPORT UP/DOWN CISCO_SWITCH_AUTO_SM ARTPORT UP/DOWN Shell Functions sh macro auto event manager policy registered sh shell trigger sh shell functions brief | in SMARTPORT 229924 Medianet Devices with Built-in ASP Macros The following devices are currently supported by built-in ASP macros. Cisco IPVS Cameras Cisco IPVS cameras support CDP as the detection mechanism for executing the built-in ip-camera ASP macro. There are slight differences in the built-in ip-camera macro applied depending upon the platform (Catalyst access switch or Catalyst 4500) and upon whether the platform supports Enhanced ASP macros or regular ASP macros. The example in Table 7-7 shows the switchport configuration applied after a link-up event for a Catalyst access switch, both with regular ASP Macros and Enhanced ASP Macros. The configuration assumes the initial switchport configuration was a default configuration (meaning no configuration on the interface). OL-22201-01 Medianet Reference Guide 7-9
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:
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: 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?