Ok, so we're not liking the +20% CPU spike from our SNMP-based data collection. I have a fairly ugly TCL script that puts the output of "show ip arp" and "show mac-address-table" in a file, then copies the file to a TFTP server. At this point, instead of using SNMP to read the data from the switch, we process the output file and get the same data.

My TCL script:

set SC [exec "show startup-config"]

regexp {hostname ([A-Za-z0-9\-\.]*)} $SC match hostname

regexp {ip domain-name ([A-Za-z0-9\-\.]*)} $SC match domain

set FQDN "$hostname.$domain"

set FILENAME "nosnmp-$FQDN"

set DATASRV "tftp://dropbox"

set FH [open "disk0:/$FILENAME" w]

# CLI commands will output to the filehandle

puts $FH [exec "show ip arp"]

puts $FH [exec "show mac-address-table"]

close $FH

puts [exec "copy disk0:/$FILENAME $DATASRV/$FILENAME"]

Is there a better way to write this using the EEM TCL interpreter directly??