Medianet Reference Guide - Cisco

Auto Smartports
Chapter 7
Medianet Auto Configuration
Table 7-12
Configuration Example 4—Overridden Macro within a Flash File on the Switch
Global Configuration Command
!
macro auto execute CISCO_DMP_EVENT remote flash:DMP_macro.txt
!
Contents of the Flash File Overriding the Built-in Macro
me-w-austin-3#more DMP_macro.txt
if [[ $LINKUP -eq YES ]]; then
conf t
interface $INTERFACE
macro description $TRIGGER
switchport access vlan $ACCESS_VLAN
switchport mode access
switchport block unicast
mls qos trust dscp
spanning-tree portfast
spanning-tree bpduguard enable
priority-queue out
exit
end
fi
if [[ $LINKUP -eq NO ]]; then
conf t
interface $INTERFACE
no macro description
no switchport access vlan $ACCESS_VLAN
no switchport block unicast
no mls qos trust dscp
no spanning-tree portfast
no spanning-tree bpduguard enable
no priority-queue out
if [[ $AUTH_ENABLED -eq NO ]]; then
no switchport mode access
fi
exit
end
fi
The benefit of this method is that a single overridden macro file can be created centrally—perhaps on a
management server—and copied to each switch which needs to override the built-in ASP macro. This
can help reduce the administrative burden and potential for errors, increasing the scalability of Auto
Smartports deployments.
The downside is that there is no method to validate that the overridden macro actually functions correctly
when it is typed in a separate text file and subsequently downloaded to the Catalyst switch. It is
recommended that the network administrator test any overridden macros—perhaps using a
non-production lab or backup switch—before deploying them in order to avoid such errors. Errors in
overridden macros will cause macro processing to immediately exit. This can result in un-deterministic
results in the configuration of an interface, based upon where in the macro the error occurred. The
network administrator should also note that currently no error or warning will be generated to the switch
console or syslog when the macro exits due to an error.
A second downside is that there is no method to validate that the overridden macro is correct for the
particular model of switch to which it is being downloaded. There are slight command differences
between Catalyst access switches and Catalyst 4500 Series switches which could cause a macro written
for the wrong switch model to execute incorrectly. This can again result in un-deterministic results in
7-16
Medianet Reference Guide
OL-22201-01