NX-OS EEM script for SVI

Hello,
I'm looking for a simple eem script for enabling an SVI if its goes down. we have some issue is NX-OS running 6.0.2.(1) where we occure a SVI down for itself.
Regard
Adil

Unfortunately, this is not possible on NX-OS. EEM on NX-OS is EEM by name only. The feature is very different than it is on IOS. What you could do is use an IOS box as a proxy. That is, send a trap using EEM from your NX-OS box, then have IOS do the telnet to the other NX-OS box to perform the necessary commands.

Similar Messages

Auto Email on event - EEM script for NxOS

I generated EEM script for Duplicate IP address detection, but i do not know how to trigger email in NxOS.
event manager environment emailto "[email protected]"
event manager applet Duplicate_IP
description "Detect Duplicate IP and Send Trap"
event syslog pattern "%ARP-2-DUP_SRC_IP"
action 1.0 snmp-trap strdata "Duplicate IP Detected on Host $hostname"
action 2.0 cli sh logg last 100
action 3.0 event-default
Somebody know how to trigger email. There is no good document on EEM email triggering mechanism.

Not sure if this would work in NxOS but I think it would go something like this;
Specify the action of sending a short e-mail when the EEM applet is triggered via the event syslog pattern you already have defined:
Router(config-applet)# action label mail server server-address to to-address from from-address subject subject body body-text
Remember to define the EEM environment variables first when setting up the applet as follows:
event manager environment _email_server
event manager environment _email_to
event manager environment _email_from

Basic traceroute EEM script (for hop-by-hop network analysis)

I'd like to do a hop-by-hop analysis by running a traceroute script that runs on an interval (say every 5-15 minutes) and puts output to a file.
The goal is to let the script run for a day, and see what kind of hop changes might occur over time, and also monitor for any latency increase or packetloss at certain times of day (peak hours).
If I used an EEM script to do a basic traceroute from one endpoint of the network to a server in the core (for instance), this could show how a client's path may be impacted during peak hours.
I'd want the output stored in a file on the router's flash disk, and then I'd have to find some way to parse and analyze the output later (not sure how I'd do that, perhaps with excel or another diff-like program).

Something like this should work for you. In config mode, specify three EEM environment variables:
event manager environment traceroute_timer 600
event manager environment traceroute_target 10.1.1.1
event manager environment traceroute_file flash:/traceroute.txt
Then register this EEM Tcl policy:
::cisco::eem::event_register_timer watchdog time $traceroute_timer
namespace import ::cisco::eem::*
namespace import ::cisco::lib::*
array set arr_einfo [event_reqinfo]
if [catch {cli_open} result] {
    error $result $errorInfo
} else {
    array set cli1 $result
if [catch {cli_exec $cli1(fd) "enable"} _cli_result] {
    error $_cli_result $errorInfo
if [catch {cli_exec $cli1(fd) "traceroute $traceroute_target"} _cli_result] {
    error $_cli_result $errorInfo
set fd [open $traceroute_file a]
puts $fd [clock format [clock seconds]]
puts $fd $_cli_result
close $fd
# Close open cli before exit.
catch {cli_close $cli1(fd) $cli1(tty_id)} result

Need EEM script for write mem config details.

Looking for an EEM script that will send an email of config details when a write mem is performed.
Any help would be appreciated as i'm new to EEM.

Something like this could work:
event manager applet email-write-mem
event cli pattern "^(write memory|write|copy running-config startup-config)*$" sync no skip no
action 0.5 info type routername
action 1.0 mail from [email protected] to [email protected] server 10.1.1.1 subject "Write mem on $_info_routername" body "A write mem was done on $_info_routername"

How to shut no shut interface of switch using(EEM) Script for 3560 switch

Dear community experts,
I'm new for creating scripting for EEM and below is my situation, need your support.
Present I'm using 3560 switch, one of the switch port(FA0/1) has added Cisco Access point(PoE), actually what happening daily this Access point getting struct when I'M doing the switch port (FA0/1) shut then no shut it is working fine .
So my question is i need script, that should continuously ping the IP off the Access point if the IP will drop 4 packets the switch do shut and then no shut for that I need the script, Please help me.
if it is not possible please provide the batch file, which will ping the particular IP if 4 packet drops it will telnet the switch and go to the interface do shut no shut
Note:
instead of mentioned 3560, I mentioned 2960 now corrected it please provide the script.

This should work:
ip sla 1
icmp-echo 10.10.10.1
frequency 15
ip sla schedule 1 life forever start now
ip sla enable reaction-alerts
ip sla reaction-configuration 1 react timeout action-type trapOnly threshold-type consecutive 4
event manager applet reset-ap
event ipsla operation-id 1 reaction-type timeout
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "int fa0/1"
action 4.0 cli command "shut"
action 5.0 cli command "no shut"
action 6.0 cli command "end"

EEM Scripting for error and drop counters

Hi,
We want to check the following counters for drops every 5 minutes and generate an alarm if a certain threshold of errors (example: increment of 100 in the error/drop counters in the last 5 minutes) is overcome:
My sample script is inline, i'm missing how to parse and generate the alarm if the threshold is surpassed:
Example command:
SPLAB_7600_3#remote command module 4 show platform hardware drops | include Selene|drp
------ Selene 0 Channel 0 ------
Selene Ingress Drop Counters Ch[0]
Selene Egress Drop Counters Ch[0]
    egr_tot_fifo_drp_ctr                          25
Selene Drop Counters
------ Selene 1 Channel 0 ------
Selene Ingress Drop Counters Ch[0]
Selene Egress Drop Counters Ch[0]
Selene Drop Counters
Best Regards,
Afonso
::cisco::eem::event_register_timer watchdog time $check_interval nice 1
# EEM policy to monitor a internal counters
# August 2012, Cisco Systems
# Copyright (c) 2012 by cisco Systems, Inc.
# All rights reserved.
namespace import ::cisco::eem::*
namespace import ::cisco::lib::*
# 2. Execute the counter show commands
if [catch {cli_open} result] {
    error $result $errorInfo
} else {
    array set cli1 $result
if [catch {cli_exec $cli1(fd) "enable"} result] {
    error $result $errorInfo
if [catch {cli_exec $cli1(fd) "cisco"} result] {
    error $result $errorInfo
# - - - - - - Interface error counters
if [catch {cli_exec $cli1(fd) "remote command module x show platform hardware selene np-idx 0 counters | include drop"} result] {
        error $result $errorInfo
set egr_drp_ctr $result
#- Parsing and conditional programming for the generation of traps based on the drop value extracted from the show command
action_syslog priority info msg "Counter Alarm"
#Exit
if [catch {cli_exec $cli1(fd) "end"} result] {
    error $result $errorInfo

I believe this is what you are looking for:
set egr_drp_ctr $result
expr {$egr_drp_ctr + 100} sumof
if {$egr_drp_ctr >= $sumof}
    puts "Alarm"
It may need correction on the syntax , but thats the logic.

EEM script for SUP failover notification

Hello All- From this thread: https://supportforums.cisco.com/thread/2059622?tstart=0, I have a need for a script which parses the output of show redundancy state, and preferably emails me the result. We are using both 6500s with SUP720/MSFC3, and 4500s with SUP II+ & SUP V.
Many thanx in advance
-michael

Exactly what do you want parsed out of this output? That is, what do you want emailed to you?

Need Help with EEM script for monitoring Rx and Tx load on Link

Hello,
I'm trying to implement a script, which monitors the Tx and Rx Load on the Link and sends a syslog in case the load is exceeded 200 mark (i.e If Rx or Tx load > 200)
I have implemented the following script. But it is not giving the required results.
event manager applet test
event interface name Tunnel111 parameter rxload entry-val 200 entry-op gt entry-val-is-increment true poll-interval 5000
action 1.0 syslog msg "Increase Load On the Link"
I'm trying to monitor the load on Tunnel 111 which is mapped to WAN interface.
Router (Cisco 2821) has following IOS
c2800nm-advipservicesk9-mz.124-25g.bin

Hello Joseph,
As per your suggestion, we made some changes in our script and the following script is working fine. Its giving the required syslogs when the load is exceeded.
event manager applet test
event interface name Tunnel111 parameter txload entry-val 200 entry-op gt entry-val-is-increment false poll-interval 5
action 1.0 syslog msg "Increased Load On the Link"
Your prompt assistance is really appriciated.

Eem scripting for IP SLA

I am trying to extract the numerical value from the followng using Embedded event manager(TCL Scripting)
i also have SLA probes running between 2 connected routers
sho ip sla statistics | sec SD Jitter
So i write the the following
conf ter
event manager applet STAT
event none sync yes
action 1 cli command "enable"
action 2 cli command "sho ip sla stat | sec SD Jitter"
action 3 regexp " [0-9]+ " $_cli_result result
action 4 puts "$result"
However it produces result
*Mar 27 16:42:08.806: %HA_EM-3-FMPD_UNKNOWN_ENV: fh_parse_var: could not find environment variable: result
*Mar 27 16:42:08.806: %HA_EM-3-FMPD_ERROR: Error executing applet STAT statement 4
pls clarify

Does the "show ip sla stat | sec SD Jitter" show any output with numbers? If not, then the result variable will not be populated. Try adding line 2 below into your applet so if there is not a match it will not produce an error.
event manager applet STAT
event none sync yes
action 1 cli command "enable"
action 2 set result "No match"
action 3 cli command "sho ip sla stat | sec SD Jitter"
action 4 regexp " [0-9]+ " $_cli_result result
action 5 puts "$result"

Help with EEM TCL / CLI scripting for re-direction/wccp counters

Being new with EEM scripting I wanted to see if I was on the right track and get some help to finish my idea.
Our problem I am trying to fix is our remote sites utilize pairs of Cat3650's for some routing and WCCP redirection. We are encountering ACL denial issues causing slow down and access issues. The fix for the issue we remove the WCCP service groups to break peering with our wan optimizers and re-insert the configuration thus re-establishing peering and restoring service.
My idea is to use a TCL scipt on a watchdog timer to parse the "sh ip wccp | inc denied (or unassign)" output for denial and unassignable error counters. If a counter is found I wanted to create a syslog message that would then kick off a simple EEM CLI script to remove the service groups, wait 10 seconds, then re-add the service groups. Please point me in the right direction if I am off track as I am not sure if I can use the EEM CLI for all this or since I want to retreive specific info from the sh ip wccp output if I do need to utilize TCL. I am also unsure if the "total denied" ascii string pulled via the "sh ip wccp | inc denied" will cause issues when attempting to just pull the counter information.
sh ip wccp | inc Denied Red
Total Packets Denied Redirect: 0
Total Packets Denied Redirect: 0
Script thus far :
TCL
if [catch {context_retrieve "EEM_WCCP_ERROR_COUNTER" "count"} result] {
set wccpcounter 0
} else {
set wccpcounter $result
} if [catch {cli_open} result] {
error $result
} else {
array set cli $result
} if [catch {cli_exec $cli(fd) "show ip wccp | incl Denied"} result] {
error $result
} else {
set cmd_output $result
set count ""
catch [regexp {receive ([0-9]+),} $cmd_output} ignore count]
set count
set diff [expr $count - $wccpcounter]
if {$diff != 0} {
action_syslog priority emergencies msg "WCCP counters showing incremental Denied packet counts"
if [catch {cli_close $cli(fd) $cli(tty_id)} result] {
error $result
context_save EEM_WCCP_ERROR_COUNTER count
CLI
event manager applet WCCP_COUNTER_WATCH
event syslog priority emergencies pattern "WCCP counters showing incremental Denied packet counts"
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "no ip wccp 61"
action 004 cli command "no ip wccp 62"
action 005 wait 10
action 006 cli command "ip wccp 61"
action 007 cli command "ip wccp 62"
action 008 wait 15
action 009 cli command "clear ip wccp"
action 010 cli command "end"
Thanks for all the help

This won't work as EEM cannot intercept its own syslog messages. However, I'm not sure why you need this form of IPC anyway. Why not just make the Tcl script perform the needed CLI commands?
And, yes, you could use all applets here. But since you've written the hard stuff in Tcl already, it might be best just to add the missing calls to reconfigure WCCP to that script.

Monitoring dual core (Supervisor Engine 7-E) through EEM Script.

Hi,
I have a Cisco Catalyst 4500E Supervisor Engine 7-E and configured an EEM Script to monitor the dual core CPU Utilization through PRTG Network Monitor.
event manager applet dualcore authorization bypass
event timer cron cron-entry "* * * * 0-6"
action 100 cli command "en"
action 120 cli command "show process cpu | include five"
action 220 regexp "Core 0: CPU utilization for five seconds: ([^%]+)%; one minute: ([^%]+)%; five minutes: ([^%]+)%.*" $_cli_result result c0cpu5sec c0cpu1min c0cpu5min
action 240 if $_regexp_result eq 1
action 260 end
action 320 regexp "Core 1: CPU utilization for five seconds: ([^%]+)%; one minute: ([^%]+)%; five minutes: ([^%]+)%.*" $_cli_result result c1cpu5sec c1cpu1min c1cpu5min
action 340 if $_regexp_result eq 1
action 360 end
action 440 cli command "config t"
action 441 cli command "snmp mib expression owner cisco name c0cpu5sec"
action 442 cli command "expression $c0cpu5sec"
action 443 cli command "snmp mib expression owner cisco name c0cpu1min"
action 444 cli command "expression $c0cpu1min"
action 445 cli command "snmp mib expression owner cisco name c0cpu5min"
action 446 cli command "expression $c0cpu5min"
action 550 cli command "config t"
action 551 cli command "snmp mib expression owner cisco name c1cpu5sec"
action 552 cli command "expression $c1cpu5sec"
action 553 cli command "snmp mib expression owner cisco name c1cpu1min"
action 554 cli command "expression $c1cpu1min"
action 555 cli command "snmp mib expression owner cisco name c1cpu5min"
action 556 cli command "expression $c1cpu5min"
action 600 cli command "end"
end
It works fine but on the logging buffer there are a lot of %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:moncores) messages   -one per minute-   here an example:
Oct 29 17:54:01: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:dualcore)
Oct 29 17:55:01: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:dualcore)
Oct 29 17:56:01: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:dualcore)
Oct 29 17:57:01: %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:dualcore)
I considered to use the logging suppress duplicates command to prevent the consecutive logging of more than one copy of the same system logging (syslog) message but it is only available to the Cisco IOS XR.
Someone could help me to determine if it is possible to avoid this messages through Embedded Syslog Manager, I tried to do that but
I was not successful.
Regards,
~Sergio

Hi,
I did transitioned CLI actions to the EXPRESSION-MIB SNMP but I could not receive anything information about the dualcore utilization on the PRTG Network Monitor and received a lot of %HA_EM-7-FMFD_SNMP_ERRCODE: fh_fd_snmp_errcode: Error status: 6 NO_ACCESS_ERROR: 1. messages on the WS-C4507.
Considering the initial EEM script, could ypu help me to avoid the %SYS-5-CONFIG_I: Configured from console by on vty0 (EEM:moncores)
messages using Embedded Syslog Manager.
Here some snmpwalk to validate that I could not get the OIDs to monitor both cores.
STEP 1     Only one value is given because there is only one physical cpu.
cpmCPUTotalPhysicalIndex
1.3.6.1.4.1.9.9.109.1.1.1.1.2
C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.4.1.9.9.109.1.1.1.1.2
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.4000 = INTEGER: 4000
STEP 2
entPhysicalName
1.3.6.1.2.1.47.1.1.1.1.7
C:\usr>
C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.47.1.1.1.1.7.4000
SNMPv2-SMI::mib-2.47.1.1.1.1.7.4000 = STRING: "Linecard(slot 4)"
#sh mod
Chassis Type : WS-C4507R+E
Power consumed by backplane : 40 Watts
Mod Ports Card Type                              Model              Serial No.
---+-----+--------------------------------------+------------------+-----------
1    18 10GE (X2), 1000BaseX (SFP)             WS-X4606-X2-E      JAE151904JC
2    24 1000BaseX (SFP)                        WS-X4624-SFP-E     JAE152001AE
4     4 Sup 7-E 10GE (SFP+), 1000BaseX (SFP)   WS-X45-SUP7-E      CAT1522L0G1
5    48 10/100/1000BaseT (RJ45)V, Cisco/IEEE   WS-X4548-GB-RJ45V JAE12067N8K
M MAC addresses                    Hw Fw           Sw               Status
--+--------------------------------+---+------------+----------------+---------
1 e8b7.4880.e5db to e8b7.4880.e5ec 1.2                               Ok
2 e8b7.48cc.6167 to e8b7.48cc.617e 1.2                               Ok
4 4055.39d7.76c4 to 4055.39d7.76c7 1.0 15.0(1r)SG2 03.01.01.SG      Ok
5 001e.f7da.d290 to 001e.f7da.d2bf 4.1                               Ok
Mod Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+----------------------------------
4   Active Supervisor   SSO                 Active
STEP 3
cpmCPUTotal1minRev
1.3.6.1.4.1.9.9.109.1.1.1.1.7
C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.4.1.9.9.109.1.1.1.1.7
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.7.4000 = Gauge32: 9
C:\usr>
ADDITIONAL INFORMATION
C:\usr>
C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.90
SNMPv2-SMI::mib-2.90.1.1.1.0 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.1.2.0 = Gauge32: 0
SNMPv2-SMI::mib-2.90.1.1.3.0 = Gauge32: 0
SNMPv2-SMI::mib-2.90.1.1.4.0 = Gauge32: 0
SNMPv2-SMI::mib-2.90.1.1.5.0 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = STRING: "9"
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = STRING: "11"
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = STRING: "8"
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = STRING: "13"
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = STRING: "13"
SNMPv2-SMI::mib-2.90.1.2.1.1.3.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = STRING: "11"
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.4.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 1
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.5.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = ""
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.6.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.7.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.8.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = Counter32: 0
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.49.109.105.110 = INTEGER: 2
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.53.109.105.110 = INTEGER: 2
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.48.99.112.117.53.115.101.99 = INTEGER: 2
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.49.109.105.110 = INTEGER: 2
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.53.109.105.110 = INTEGER: 2
SNMPv2-SMI::mib-2.90.1.2.1.1.9.5.99.105.115.99.111.9.99.49.99.112.117.53.115.101.99 = INTEGER: 2
C:\usr>
C:\usr>snmpwalk -v 2c -c m4nc4rc0 10.20.91.2 1.3.6.1.2.1.47.1.1.1.1.2
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1 = STRING: "Cisco Systems, Inc. WS-C4507R+E 7 sl
ot switch "
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.3 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.6 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.7 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.8 = STRING: "WS-C4507R+E 7 slot switch chassis sl
ot"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.9 = STRING: " WS-C4507R+E 7 slot switch backplane
SNMPv2-SMI::mib-2.47.1.1.1.1.2.10 = STRING: "Container of Fan Tray"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.11 = STRING: "FanTray"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.12 = STRING: "Container of Container of Power Sup
ply"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.13 = STRING: "Container of Power Supply"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.14 = STRING: "Power Supply ( AC 2800W )"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.15 = STRING: "Power Supply Fan Sensor"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.16 = STRING: "Container of Power Supply"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.19 = STRING: "Clock Module"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.20 = STRING: "Mux Buffers for Redundancy Logic"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.21 = STRING: "Mux Buffers for Redundancy Logic"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.22 = STRING: "Mux Buffers for Redundancy Logic"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.23 = STRING: "Mux Buffers for Redundancy Logic"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.24 = STRING: "Mux Buffers for Redundancy Logic"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1000 = STRING: "10GE (X2), 1000BaseX (SFP) with 6
10GE X2 ports"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1001 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1002 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1003 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1004 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1005 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.1006 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2000 = STRING: "1000BaseX (SFP) with 24 SFP Ports
Jumbo Frame Support"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2001 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2002 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2003 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2004 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2005 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2006 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2007 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2008 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2009 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2010 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2011 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2012 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2013 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2014 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2015 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2016 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2017 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2018 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2019 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2020 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2021 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2022 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2023 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2024 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2047 = STRING: "1000BaseSX"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.2048 = STRING: "1000BaseSX"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4000 = STRING: "Sup 7-E 10GE (SFP+), 1000BaseX (S
FP) with 4 SFP+ Ports"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4001 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4002 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4003 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.4004 = STRING: "Port Container"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5000 = STRING: "10/100/1000BaseT (RJ45)V with 48
10/100/1000 baseT voice power ports (Cisco/IEEE)"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5001 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5002 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5003 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5004 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5005 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5006 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5007 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5008 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5009 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5010 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5011 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5012 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5013 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5014 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5015 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5016 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5017 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5018 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5019 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5020 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5021 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5022 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5023 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5024 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5025 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5026 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5027 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5028 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5029 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5030 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5031 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5032 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5033 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5034 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5035 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5036 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5037 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5038 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5039 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5040 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5041 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5042 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5043 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5044 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5045 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5046 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5047 = STRING: "Gigabit Ethernet Port"
SNMPv2-SMI::mib-2.47.1.1.1.1.2.5048 = STRING: "Gigabit Ethernet Port"
C:\usr>

EEM Script to use in an triple play network

Hi,
I have a customer which have a tripe play network. I attach the following drawing so you can have a better idea how the network looks like.
IPTV, Internet and IP telephony is getting in in our customer network at both PE some you can see in the drawing.
Basicaly our customer deliver the network infrastructure while ISP1, ISP2 and ISP3 deliver the content (IPTV, Internet and IP telephony).
The two PEs which are getting the content in the network from the 3 ISPs are running the following hardware and IOS:
cisco CISCO7606 with WS-SUP720 MSFC3 Daughterboard Rev. 3.2.
IOS version: c7600s72033-advipservicesk9-mz.122-33.SRC5.bin
BGP is used between the PEs and the ISPs router.
The PEs are redundant for each other.
Our issue is when one of the ISP is having some maintenance on their routers one the PEs goes really high on CPU until reaching 100%.
I don't know why that is happening that is why I want to use EEM to dig deeper into it.
So What I want to do is an EEM script that could do the following:
1) The script should be triggered when CPU Threshold is reached (lets say 85 %).
3) Run a show tech and save the output in flash.
2) Then the script should run do the following commando and save the outputs to flash:
        - sh ip bgp vpnv4 vrf VRF10102 neighbors
        - sh bgp vpnv4 unicast vrf VRF10102 summary
        - sh ip bgp vpnv4 vrf VRF10102 neighbors x.x.x.x advertised-routes
        - sh ip bgp vpnv4 vrf VRF10102 neighbors x.x.x.x received-routes
        - sh isis neighbors detail
3) Run "sh log" and save the output into flash.
Anyone has an idea how I could made this script with EEM?
Thanks in advance for your help.
Best regards,
Laurent

I don't think you need a script for this. An applet should work just fine. This kind of thing is commonly done by TAC to aid in data collection for transient problems. This policy should work provided the CPU instance is correct. A 7600 will have at least two CPUs. This applet assumes CPU instance 1 is the desired CPU, but it may be CPU instance 2 you need to monitor.
event manager applet watch-cpu event snmp oid 1.3.6.1.4.1.9.9.109.1.1.1.1.11.1 get-type exact entry-op ge entry-val 90 exit-op lt exit-val 90 poll-interval 60 maxrun 300 action 1.0 cli command "enable" action 1.1 cli command "term exec promp time" action 2.0 cli command "show tech | append disk0:/high_cpu.txt" action 3.0 cli command "sh ip bgp vpnv4 vrf VRF10102 neighbors | append disk0:/high_cpu.txt" action 4.0 cli command "sh bgp vpnv4 unicast vrf VRF10102 summary | append disk0:/high_cpu.txt" action 5.0 cli command "sh ip bgp vpnv4 vrf VRF10102 neighbors x.x.x.x advertised-routes | append disk0:/high_cpu.txt" action 6.0 cli command "sh ip bgp vpnv4 vrf VRF10102 neighbors x.x.x.x received-routes | append disk0:/high_cpu.txt" action 7.0 cli command "sh isis neighbors detail | append disk0:/high_cpu.txt" action 8.0 cli command "show logg | append disk0:/high_cpu.txt"

Error in EEM script mail

Hi,
I'm trying to email an alert by eem script when a catalyst 6807 rises a syslog message for an environment alarm (ex: power down). I use the attached script but when i want to add the syslog message in body email (line 83) something is wrong and i can't fixed the error : catalyst try to execute the syslog message (see email).
Same error for a catalyst 4507 4506 Sup 6L-E 10GE IOS 15.2(1)E but the same script works for a catalyst 4506 Sup 6L-E 10GE IOS 15.0(2)SG.
Any ideas ?
Thanks

Hi,
I found my mystake. In the script, I commented the command "enable" and thus show commands were not recognized by cli. The script has always worked well, "Invalid input" was the result of show command. For ios 15.2, i need to gain enable level.
So I suspect a different behavior between versions 15.0 and 15.2 for running level of tcl script.

Nexus 7k EEM Script

I had plans to configure a EEM script to send a email when an OSPF adjacency drops. I have an odd spanning-tree issue that I believe the drops are related to and I want to see if my suspicions are correct. This doesn't happen very often, and it's normaly late at night.
I originally planned something like this:
event manager environment _email_server 192.168.x.x
event manager environment _email_to [email protected]
event manager environment _email_from [email protected]
event manager session cli username "user"
event manager applet OSPF
event syslog pattern "%OSPF-"
action 1.0 cli command "enable"
action 1.1 cli command "show spanning-tree vlan 192"
action 1.2 cli command "show spanning-tree vlan 192 detail"
action 1.3 wait 10
action 1.4 cli command "show spanning-tree vlan 192"
action 1.5 cli command "show spanning-tree vlan 192 detail"
action 1.6 wait 20
action 1.7 cli command "show spanning-tree vlan 192"
action 1.8 cli command "show spanning-tree vlan 192 detail"
action 1.9 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Spanning-tree results" body "$_cli_result"
After trying this, it doesn't seem that NXOS support the email function.
My questions:
1. What alternative do I have? Is there a way to send the CLI output via SNMP or syslog?
2. Will this even run EVERY time the syslog pattern matches? Meaning if I get four %OSPF syslog messages, it will run four times repeatedly? \
Thank you,

Hello Arie,
Thank you for answering my questions.
This is what I've got now. I think it will work well.
event manager applet OSPF
event syslog pattern "%OSPF-4-NEIGH_ERR"
action 1.0 cli command "enable"
action 1.1 cli command "show clock >> bootflash:ospf"
action 1.2 cli command "show spanning-tree vlan 192 >> bootflash:ospf"
action 1.3 cli command "show spanning-tree vlan 192 detail >> bootflash:ospf"
action 1.4 wait 10
action 1.5 cli command "show clock >> bootflash:ospf"
action 1.6 cli command "show spanning-tree vlan 192 >> bootflash:ospf"
action 1.7 cli command "show spanning-tree vlan 192 detail >> bootflash:ospf"
action 1.8 wait 10
action 1.9 cli command "show clock >> bootflash:ospf"
action 2.0 cli command "show spanning-tree vlan 192 >> bootflash:ospf"
action 2.1 cli command "show spanning-tree vlan 192 detail >> bootflash:ospf"
action 2.2 cli command "end"
action 2.3 cli command "exit"
--- Turns out "wait" isn't a option in NXOS either. I just put "show logging info" in its place, and didn't append it to the output file. That command takes about 10-15 seconds to run for some reason, so it should give me the pause I want.

Cisco 1841/871 crash EEM scripting 15.1(1)T

We have been testing 15.1.1T on a couple of lab Cisco 1841 and Cisco 871 devices.
On the devices we are using EEM to automate the failover/failback process for a cellular modem attached to f3 on the 871 or f0/1 on the 1841. One of the EEM applets we use fires from a cron timer event that occurs every 10 minutes on the router.
IOS revision 12.4(22)T we had no problems with using the cron-timer triggered applet (every 10 minutes between 7am to 10pm), except for the fact that every command issued by EEM required AAA authentication. The EEM applet is causing our routers to saturate our Cisco ACS servers (we use 700+ routers in the field, all exectuing this EEM script) with single-connect requests. We will refer to the cron-timer executed applet as 'Maintenance' from here on out.
As of 15.1(1)T the addition to bypass the AAA authentication process became available. This was a huge speed increase to our EEM applets, specifically the Maintenance applet. I will include the applet for clairity.
event manager applet Maintenance authorization bypass
event timer cron name 10min cron-entry "*/10 7-21 * * *" maxrun 30
action 001 cli command "en"
action 002 cli command "show ip route | section B\*[ ]+0\.0\.0\.0"
action 003 regexp "^B\*.([ ]+)(0\.)+0" "$_cli_result"
action 004 set bgpstate "$_regexp_result"
action 005 cli command "show ip route | section S[ ]+208\.38\.154\.8"
action 006 regexp "^S([ ]+)208\.38\.154\.8" "$_cli_result"
action 007 set wireless "$_regexp_result"
action 008 track read 1
action 009 set track1 "$_track_state"
action 010 if $wireless eq 0
action 011       if $bgpstate eq 0
action 012             cli command "conf t"
action 013             cli command "int fa0/1"
action 014             cli command "no shut"
action 015             cli command "int tun201"
action 016             cli command "no shut"
action 017             cli command "int lo201"
action 018             cli command "no shut"
action 019             if $track1 eq up
action 020                   exit
action 021                   else
action 022                   cli command "conf t"
action 023                   cli command "int s0/0/0"
action 024                   cli command "no shut"
action 025             end
action 026             cli command "end"
action 027             cli command "exit"
action 028       else
action 029             exit
action 030            end
action 031 else
action 032       if $bgpstate eq 1
action 033             cli command "conf t"
action 034             cli command "int fa0/1"
action 035             cli command "shut"
action 036             cli command "int tun201"
action 037             cli command "shut"
action 038             cli command "int lo201"
action 039             cli command "shut"
action 040             cli command "end"
action 041             cli command "exit"
action 042      else
action 043             if $track1 eq up
action 044                   exit
action 045             else
action 046                   cli command "conf t"
action 047                   cli command "int s0/0/0"
action 048                   cli command "no shut"
action 049             end
action 050             cli command "end"
action 051             cli command "exit"
action 052             exit
action 053       end
action 054 end
This script is designed to look for a couple of routes in the IP routing table, and populate two variables (bgpstate and wireless) with the regular expression matching result of the show ip route commands. It uses track 1 to determine the up/down status of Serial0/0/0 which is the primary T1 interface for WAN services on the router. The wireless is "up/1" if the static route to 208.38.154.8 is present in the show ip route output (only when f0/1 is up in this case). The T1 is "up/1" if the default route passed to the IP routing table is present in the show ip route output.
Before the upgrade to 15.1(1)T these scripts ran without issue, and we had no errors. Now after the upgrade, anytime this script fires and the show ip route match for the wireless variable is 1 instead of zero, it begins to run through the else condition starting at action 031, and during the second execution of the script every 10 minutes (I still have not figured out how to force the cron-timer to fire only ONCE per minute, instead of at the beginning and end of the minute), the router will generate spurious memory errors, and sometimes crash or reboot.
This all began with 15.1(1)T, and I have not seen any caveats or other entries that could possibly point to the cause of this problem. Any ideas?
I am also attaching a crash file from one of the routers like this one so you can see what I mean.
All of these devices are running the advipservices k9 version of this IOS.
Thanks for your time.

The problem with cron events running twice in the same minute is bug CSCsz12460 which will be fixed in EEM 3.2 in 15.1(3)T.
The crash you're seeing doesn't appear to be related to EEM at all. It looks like a problem with single-connection TACACS+. The bug appears to be CSCtg40901 which has not yet been fixed in 15.1T.
A workaround was suggested to use multiple-connection TACACS+.

NX-OS EEM script for SVI

Similar Messages

Maybe you are looking for