EEM script to Reload router 1 Time if Dial Fails
We have a script we use to track objects and if access to these objects fails we reload the router 1 time (see it below). We want to now apply the same script in a different capacity for another customer for dial. If the router fails to connect after trying to round robin thru 4 toll free 800 numbers then reload the router.
event manager applet vpn_tunnel_rebooter
event none
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "no event manager applet vpn_tunnel_unreachable"
action 4.0 cli command "end"
action 5.0 cli command "write mem"
action 6.0 reload
event manager applet vpn_tunnel_up
event track 456 state up
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "event manager applet vpn_tunnel_unreachable"
action 004 cli command "event track 456 state down"
action 005 cli command "action 1.0 policy vpn_tunnel_rebooter"
action 006 cli command "end"
Any ideas on how we might accomplish this? I have very little EEM experience :)
1) Current Object tracking tracks 3 objects, If access to all three is down we go into a 180 sec delay down timer. If they remain down we switch over to dial backup.
2) We round robin between 4 dial numbers and if access to all 4 fails, we want to reload router "ONE" time
3) When it comes back up and objects are still unavailable we attempt to dial the 4 numbers again and if it also fails to connect "DO NOT" reload this time.
Okay, these policies should do what you want. They are all untested as I do not have a dial backup setup. First, you need to register the following applets:
event manager applet remove-dial-backup-watch
event syslog pattern "SYS-5-RESTART"
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "no event manager policy tm_check_dial_backup.tcl"
action 4.0 cli command "end"
event manager applet watch-track-down
event track 456 state down
action 1.0 syslog msg "Track 456 is down, waiting to see if dial backup comes up"
action 2.0 cli command "enable"
action 3.0 cli command "config t"
action 4.0 cli command "event manager policy tm_check_dial_backup.tcl"
action 5.0 cli command "end"
event manager applet watch-track-up
event track 456 state up
action 1.0 syslog msg "Track 456 is up, removing dial backup watcher"
action 2.0 cli command "enable"
action 3.0 cli command "config t"
action 4.0 cli command "no event manager policy tm_check_dial_backup.tcl"
action 5.0 cli command "end"
Then, you need to set an environment variable for the Tcl policy:
dial_backup_numbers : Comma-separated list of numbers to check
For example:
event manager environment dial_backup_numbers 18667143757,18003179379,18886601039,18004434603
Then INSTALL but do NOT register the attached Tcl policy. That is, copy the attached Tcl policy to your EEM user policy directory, but do not register it.
Then everything should just work.
Similar Messages
-
EEM Script to reload router only once after tracked object is down.
event manager applet vpn_tunnel_unreachable
event track 456 state down
action 1.0 reload
I need it to reload only once if tracked object 456 is down. It should reload the router and then if the tracked object is still down it should go into dial backup as it normally would if it did not have the reload script.I suggest reposting this question at the other Network Management subforum under Network Infrastructure to get the attention of the resident EEM guru.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_messages%26mode%3Dnew%26location%3D.ee71a02 -
EEM Script (TCL) to run 3 times in a day
HI All,
Need your kind help..
I am just new to EEM. I want run a script through which router automatically sends formated outputs thrice in a day ( 00:00 hrs,08:00 hrs and 16:00 hrs)
Can anyone help me out how to register the script so that i will get desred output.
i just modified the script downloaded from cisco [PFA]
after running the script mannually am getting the below log on console
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: no such file or directory
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: "source [file join $dir tclIndex]"
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: "$slave eval $Contents"
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: (procedure "eval_script" line 7)
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: "eval_script slave $scriptname"
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: "if {$security_level == 1} { #untrusted script
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: interp create -safe slave
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: interp share {} stdin slave
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: interp share {} stdout slave
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: ..."
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: (file "tmpsys:/lib/tcl/base.tcl" line 50)
*Mar 13 05:05:00.259: %HA_EM-6-LOG: cpu-test.tcl: Tcl policy execute failed: EEM Policy Error: Variable Execution-time has not been definedHI Joseph,
I am getting below msg on console.
IST: %HA_EM-6-LOG: cpu-test.tcl: invalid command name "else"
IST: %HA_EM-6-LOG: cpu-test.tcl: while executing
IST: %HA_EM-6-LOG: cpu-test.tcl: "else "
IST: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
IST: %HA_EM-6-LOG: cpu-test.tcl: "$slave eval $Contents"
IST: %HA_EM-6-LOG: cpu-test.tcl: (procedure "eval_script" line 7)
IST: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
IST: %HA_EM-6-LOG: cpu-test.tcl: "eval_script slave $scriptname"
IST: %HA_EM-6-LOG: cpu-test.tcl: invoked from within
IST: %HA_EM-6-LOG: cpu-test.tcl: "if {$security_level == 1} { #untrusted script
IST: %HA_EM-6-LOG: cpu-test.tcl: interp create -safe slave
IST: %HA_EM-6-LOG: cpu-test.tcl: interp share {} stdin slave
IST: %HA_EM-6-LOG: cpu-test.tcl: interp share {} stdout slave
IST: %HA_EM-6-LOG: cpu-test.tcl: ..."
IST: %HA_EM-6-LOG: cpu-test.tcl: (file "tmpsys:/lib/tcl/base.tcl" line 50)
IST: %HA_EM-6-LOG: cpu-test.tcl: Tcl policy execute failed: invalid command name "else"
Below is the configuration on Switch
============================
XXXXXXXXXX#sh run | in event
event manager environment email_server x.x.x.x
event manager environment email_from [email protected]
event manager environment email_to [email protected]
event manager directory user policy "bootflash:/"
event manager policy cpu-test.tcl type user
thanks and regards.
DBN -
EEM scripting assistance: Switch, router and AP CDP
We would like to create an EEM script which will let the switch populate the interface description based on the CDP neighbour, however, we want the script to only populate the interface if (and only if) the CDP is a Cisco wireless access point (AP), a Cisco Catalyst switch and a Cisco router. We DO NOT want the interface description to be edited if the CDP neighbour is a Cisco phone or a Cisco DMP (for example).
This is our EEM script:
event manager applet update-port
event none
event neighbor-discovery interface regexp GigabitEthernet.* cdp add
action 100 if $_nd_cdp_capabilities_string eq "Router" goto 200
action 110 elseif $_nd_cdp_capabilities_string eq "Switch" goto 200
action 120 if $_nd_cdp_capabilities_string eq "Switch" goto 200
action 200 cli command "enable"
action 210 cli command "config t"
action 220 cli command "interface $_nd_local_intf_name"
action 230 cli command "description $_nd_cdp_entry_name"
action 400 else
action 500 end
And this is a sample of our “sh cdp neighbor” output:
Switch#sh cdp n d
Device ID: Wireless
Entry address(es):
IP address: <REMOVED>
Platform: cisco AIR-CAP3602I-N-K9 , Capabilities: Router Trans-Bridge
Interface: GigabitEthernet0/8, Port ID (outgoing port): GigabitEthernet0.1
Holdtime : 146 sec
Version :
Cisco IOS Software, C3600 Software (AP3G2-K9W8-M), Version 15.2(2)JB, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Mon 10-Dec-12 23:52 by prod_rel_team
advertisement version: 2
Duplex: full
Power drawn: 15.400 Watts
Power request id: 19701, Power management id: 2
Power request levels are:15400 0 0 0 0
Power Available TLV:
Power request id: 0, Power management id: 0, Power available: 0, Power management level: 0
Management address(es):
Device ID: 00:0f:44:02:c5:29
Entry address(es):
IP address: <REMOVED>
Platform: Cisco DMP 4310G, Capabilities: Host
Interface: GigabitEthernet0/3, Port ID (outgoing port): eth0
Holdtime : 157 sec
Version :
5.4
advertisement version: 2
Duplex: full
Power Available TLV:
Power request id: 0, Power management id: 0, Power available: 0, Power management level: 0
Management address(es):
Device ID: CALM040.mgmt.educ
Entry address(es):
IP address: <REMOVED>
Platform: cisco WS-C3750E-24PD, Capabilities: Switch IGMP
Interface: GigabitEthernet0/10, Port ID (outgoing port): GigabitEthernet1/0/22
Holdtime : 126 sec
Version :
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.0(2)SE, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Fri 27-Jul-12 23:26 by prod_rel_team
advertisement version: 2
Protocol Hello: OUI=0x00000C, Protocol ID=0x0112; payload len=27, value=00000000FFFFFFFF010221FF0000000000000023AC075300FF0000
VTP Management Domain: 'ACTEducation'
Native VLAN: 99
Duplex: full
Power Available TLV:
Power request id: 0, Power management id: 1, Power available: 0, Power management level: -1
Management address(es):
IP address: <REMOVED>
Device ID: 00:0f:44:02:b6:31
Entry address(es):
IP address: <REMOVED>
Platform: Cisco DMP 4310G, Capabilities: Host
Interface: GigabitEthernet0/2, Port ID (outgoing port): eth0
Holdtime : 169 sec
Version :
5.4
advertisement version: 2
Duplex: full
Power Available TLV:
Power request id: 0, Power management id: 0, Power available: 0, Power management level: 0
Management address(es):
Best Regards/Leoaction 221 regexp "^([^\.])\." $_nd_cdp_entry_name match hostaction 230 cli command "description $host"
Hi Joe,
So the EEM is going to look like this:
event manager applet update-port
event neighbor-discovery interface regexp GigabitEthernet.* cdp add
action 100 regexp "(Switch|Router)" $_nd_cdp_capabilities_string
action 110 if $_regexp_result eq 1
action 200 cli command "enable"
action 210 cli command "config t"
action 220 cli command "interface $_nd_local_intf_name"
action 230 regexp "^([^\.])\." $_nd_cdp_entry_name match host
action 240 cli command "description $host"
action 500 end
Is this correct? -
EEM applet to reload router after ip is unreachable over time
Hi
I am trying to create an EEM applet that will track the reachability of a group of IP addresses. The condition needs to be as followed:
If the IP addresses become unreachable for about an 1 hour 15 minutes then reload the router. I have looked at the delay command using the IP SLA option but it only delays up to 180 seconds. Any Ideas?The applet that tracks your IP SLA objects (I'm guessing you have a tracked object that tracks a list of other objects) should configure another timer applet that counts down the time you want. For example:
event manager applet track-down event track 3 state down action 1.0 cli command "enable" action 2.0 cli command "config t" action 3.0 cli command "event manager applet countdown" action 3.1 cli command "event timer countdown time 4500" action 3.2 cli command "action 1.0 reload" action 4.0 cli command "end"!event manager applet track-up event track 3 state up action 1.0 cli command "enable" action 2.0 cli command "config t" action 3.0 cli command "no event manager applet countdown" action 4.0 cli command "end" -
I have an EEM script which runs on a track when it goes down, within the actions i have different other things to check and take actions accordingly and they are working fine. I want to include a router reload within the same applet which should only trigger once within 24 hrs., no matter how many times the EEM runs during 24 hrs.
Here is my current applet:
event manager applet MyApplet authorization bypass
event track 10 state down maxrun 3600
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "service internal"
action 3.1 cli command "do test cellular 0 modem-power-cycle"
action 3.2 cli command "no service internal"
action 4.0 wait 720
action 5.0 track read 10
action 6.0 if $_track_state eq "down"
action 6.1 cli command "int cell0"
action 6.2 cli command "shut"
action 6.3 cli command "controller cell 0"
action 6.4 cli command "lte radio off"
action 6.5 wait 60
action 6.6 cli command "no lte radio off"
action 6.7 cli command "int cell0"
action 6.8 cli command "no shut"
action 6.9 end
At the end i want to add another wait of 10 sec. and check the track state again, if it is still Down I want to trigger a reload, but when router comes back after reload and my EEM triggers again, i don't want to reload if the last reload was triggered within last 24 hrs.The way you're using wait in this applet is not ideal. It would be better, especially for the long wait, to have this broken up into multiple applets so that they can run asynchronously. In fact, given what you want to do for this reload, that would be the better way to go. If you configured a second applet at the end of this applet like:
event manager environment q "
action 7.0 cli command "event manager applet reload-countdown"
action 7.1 cli command "event timer countdown 10"
action 7.2 cli command "action 1.0 cli command enable"
action 7.3 cli command "action 2.0 cli command $q config t$q"
action 7.4 cli command "action 3.0 cli command $q no event manager applet reload-countdown$q"
action 7.5 cli command "action 4.0 cli command end"
action 7.6 cli command "action 5.0 cli command $q write mem$q"
action 7.7 cli command "action 1.0 reload"
Then you could have another applet that reacts to the tracked object coming up. This applet would simply unconfigure the reload-countdown applet. Thus, if the track comes back up, the reload will not happen. -
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,
LaurentI 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" -
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 -
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+. -
EEM script not running in WS-C4900M switch
Hello,
I am having two WS-C4900M switches which were giving high cpu spikes hence we have configured EEM script in it to capture switch behaviour during cpu spikes.when CPU goes high script do get hit but the commands under script doesn't run and we are not able fecth command outputs during high cpu.
Pleas find script uploaded and show version of switch attached.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" -
Most Basic EEM Script to Send E-mails
I have read through various blogs and Cisco posts and still cannot seem to get this to work. I am simply trying to get the router to send the "show ip int br" info via e-mail from a G-Mail account to a G-Mail account. I am wondering if this is unsupported because G-mail uses TLS/SSL and different ports and I can't seem to defined this anywhere. Can anyone confirm?
I manually run the EEM script via "event manager run IPAddressNotify". I have made sure that the router can ping "smtp.gmail.com" (IE IP reachability and name-lookups are successful).
event manager environment _email_to [email protected]
event manager environment _email_server gmailusername:[email protected]
event manager environment _email_from [email protected]
event manager applet IPAddressNotify
event none
action 1.0 info type routername
action 1.5 cli command "enable"
action 2.0 cli command "show ip int br"
action 8.0 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Router reload - IP Address info for $_info_routername" body "$_cli_result"
action 9.0 syslog msg "E-mail was sent"Joseph,
Thanks for the info! This is perfect. Can you verify that my logic is clear, just so I know I am interpreting this correctly.
Right now, my IOS version does NOT support the "secure" and "port" parameters for EEM. Since G-Mail does NOT support unencrypted SMTP (verified), there is no way that I can use EEM or TCL to e-mail myself messages. Correct?
When you state that my username cannot have an '@' in it, is this referring to the 'from' field which would be "[email protected]"? Or, is this referring to the 'server' field which would be "gmailusername:[email protected]". Luckily, Google lets me authenticate by specifying 'gmailusername', rather than '[email protected]'. This should work then correct? -
Hi- Please help out this newbie...
I am looking for an example EEM script/applet that would cause my router to change a path selection, based on a triggered event. I usually employ Policy Based Routing on my networks which makes next hop decisions based on the source IP. I want to do something similar with EEM, but rather than a simple source address based decision, I want a next hop selection to be based on an event. (for the example, it could be anything...bandwidth threshold, or at a certain time of day, or whatever). First I want to know if this can be done, and second I would appreciate it if someone could share a simple example configuration with me. -it's the best way I learn it.
Also, in the example, how is the applet or script applied to the router?
Thanks!You can adjust routes or add class-maps based on EEM events. However, you can't match on something that can be controlled by an EEM event (i.e., match within a route-map). However, you can create a route-map on the fly when an event occurs. That is, when your event occurs, you can define a route-map to match on the interesting traffic and adjust the IP next-hop. Bottom line is if you can do something manually on the CLI, you can automate it with EEM.
Without knowing more specifics, I'll provide an example that will allow you to run CLI at a specific time (at midnight). You can adapt this to meet your specific needs. This applet can be copy and pasted directly into config t mode:
event manager applet timed-cli
event timer cron cron-entry "0 0 * * *"
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "route-map TEST"
action 4.0 cli command "match interface gi0/0"
action 5.0 cli command "set ip next-hop 10.1.1.1"
action 6.0 cli command "end" -
Objects show up even when nothing plugged into port - EEM Script
After a reboot my cisco shows the objects it tracks as up even when nothing is plugged into the interface used to track the objects. I have an EEM script that reboots the router 1 time when it finds that 4 dial numbers it round robins thru are unavialable and this works. The problem is after the reboot it see's the objects as available and re-inserts the reboot script and when they finally show down as they should be the reboot hapens over and over. Any Ideas on how to get the router to not show the tracked objects up after a reboot if the interface is down?
As I said in the other thread, I suspect the "delay down" is causing the behavior you are seeing.
-
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,
~SergioHi,
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> -
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
Maybe you are looking for
-
Hi friends, I am facing a problem in triggering the event. My problem is " When a form is created in the EP and when the SUBMIT button is clicked i am calling a RFC in which i am using the function module "SWE_EVENT_CREATE" where the exporting parame
-
Questions on Initial MARS setup
I have a question on the ?Topology Discovery? piece in MARS. I will be using SNMP to discover and poll all devices in the network. What I don?t want is the MARS box to scan entire subnets looking for devices. I want to control exactly what MARS is do
-
Installer failed to initialise
Just signed up for the creative cloud and when I try to download the app I get a error message (installer failed to initialize) and will not go any further
-
Dear all, Is is possible to cal perl scripts from OWB?. Thanks in advance Mehdi
-
How do I uninstall firefox 3.6 from my mac osx 10.6
I absolutely do NOT WANT firefox to keep interfering when I am on google. How do DELETE firefox from my mac?