10-25-2018 06:49 PM
Hi,
Trying to find out how to get a Cisco 4331 EEM to trigger on IP SLA RTT threshold instead of timeout. I found a configuration that seems like it might work, tested it on 1841 and it took the command (event ipsla operation-id 11 reaction-type rtt), but my 4331 doesn't have the EEM applet "event ipsla..." option. Is there another method? Why would a much more expensive router have less options when it comes to event types to trigger EEM?
Solved! Go to Solution.
10-27-2018 07:45 AM
It may depend on your license or perhaps the IPSLA event detector wasn't compiled into your image. This has happened before due to resource concerns or simple oversight. You could still make this work by triggering a syslog message with the threshold violation and have EEM react to that syslog:
ip sla enable reaction-alerts
ip sla logging traps
I don't have an example syslog off hand, but when you configure that, you should see the message generated, and then you can craft a syslog regexp for it.
10-26-2018 01:13 PM
can you post show version of the device.
10-26-2018 01:26 PM
Cisco IOS XE Software, Version 03.16.04b.S - Extended Support Release
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S4b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Mon 17-Oct-16 20:23 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2016 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
uptime is 3 weeks, 4 days, 3 hours, 51 minutes
Uptime for this control processor is 3 weeks, 4 days, 3 hours, 53 minutes
System returned to ROM by reload at 09:37:33 PDT Fri Sep 7 2018
System restarted at 09:32:36 PDT Mon Oct 1 2018
System image file is "bootflash:/isr4300-universalk9.03.16.04b.S.155-3.S4b-ext.SPA.bi"
Last reload reason: PowerOn
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
export@cisco.com.
Suite License Information for Module:'esg'
--------------------------------------------------------------------------------
Suite Suite Current Type Suite Next reboot
--------------------------------------------------------------------------------
FoundationSuiteK9 None None None
securityk9
appxk9
AdvUCSuiteK9 AdvUCSuiteK9 RightToUse AdvUCSuiteK9
uck9
cme-srst
cube
Technology Package License Information:
-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
appxk9 None None None
uck9 None None None
securityk9 securityk9 Permanent securityk9
ipbase ipbasek9 Permanent ipbasek9
cisco ISR4331/K9 (1RU) processor with 1648789K/6147K bytes of memory.
Processor board ID
3 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
3223551K bytes of flash memory at bootflash:.
Configuration register is 0x2102
10-26-2018 01:32 PM
you can check the feature supported for your version
http://cfn.cloudapps.cisco.com/ITDIT/CFN/jsp/SearchBySoftware.jsp
10-26-2018 01:39 PM
10-26-2018 01:50 PM
i looked at ipbase have EEM feature supported in 4331
can you post EEM script and what is the error you getting when you creating EEM event ?
10-26-2018 04:20 PM
Yes, we have EEM set up on the 4331, so I know that is supoorted. On an 1841 I can enter event trigger "event ipsla operation-id 11 reaction-type rtt". But on the 4331, event trigger "ipsla" is no longer an option.
1841
(config-applet)#event ?
application Application specific event
cli CLI event
config Configuration policy event
counter Counter event
env Environmental event
identity Identity event
interface Interface event
ioswdsysmon IOS WDSysMon event
ipsla IPSLA Event
neighbor-discovery Neighbor Discovery event
nf NF Event
none Manually run policy event
oir OIR event
resource Resource event
routing Routing event
rpc Remote Procedure Call event
snmp SNMP event
snmp-notification SNMP Notification Event
snmp-object SNMP object event
syslog Syslog event
tag event tag identifier
timer Timer event
track Tracking object event
4331
(config-applet)#event ?
application Application specific event
cli CLI event
config Configuration policy event
counter Counter event
env Environmental event
gold GOLD event
interface Interface event
ioswdsysmon IOS WDSysMon event
neighbor-discovery Neighbor Discovery event
none Manually run policy event
oir OIR event
resource Resource event
rf Redundancy Facility event
routing Routing event
rpc Remote Procedure Call event
snmp SNMP event
snmp-notification SNMP Notification Event
snmp-object SNMP object event
syslog Syslog event
tag event tag identifier
timer Timer event
track Tracking object event
10-27-2018 07:45 AM
It may depend on your license or perhaps the IPSLA event detector wasn't compiled into your image. This has happened before due to resource concerns or simple oversight. You could still make this work by triggering a syslog message with the threshold violation and have EEM react to that syslog:
ip sla enable reaction-alerts
ip sla logging traps
I don't have an example syslog off hand, but when you configure that, you should see the message generated, and then you can craft a syslog regexp for it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide