IP SLA Monitor /Tracking 2921

I am looking or IOS code for a Cisco 2921/K9 that will allow me to do IP SLA Tracking. The current code "c2900-universalk9-mz.SPA.151-4.M.bin" will only allow me to sset up IP SLA responder or IP SLA Server but NOT IP SLA Monitor or IP SLA RTR.
I have used the Cisco feature set research tool and chose what it recommended but to no avail.
Am I missing something? Will the Server or Responder perform tracking?
Thanks in advance to anyone who can assist..
~g

Dear All,
I have the same problem with C2921. I want to config IP SLA for my C2921 but it seems do not support. The below for your reference.
####### Do not have option monitor
ip sla ?
key-chain Use MD5 Authentication for IP SLAs Control Messages
responder Enable IP SLAs Responder
server     IPPM server configuration
Show version
System image file is "flash0:c2900-universalk9-mz.SPA.151-4.M1.bin"
License Info:
License UDI:
Device#   PID                   SN
*0        CISCO2921/K9          FGL153913PM
Technology Package License Information for Module:'c2900'
Technology    Technology-package           Technology-package
              Current       Type           Next reboot
ipbase        ipbasek9      Permanent      ipbasek9
security      None          None           None
uc            None          None           None
data          None          None           None
Please kindly advise what ios I can use for configuring IP SLA. there're any problem with my licence for that
Best Regards,
Binh

Similar Messages

ASA5510 sla monitor does not fail back

I've been down this path before and never got a resolution to this issue.
ASA5510 Security Plus
Primary ISP conn is Comcast cable
Secondary ISP conn is fract T1
I duplicated the SLA code from http://www.cisco.com/en/US/partner/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml
When I pull the conn from primary ISP the default route to the secondary comes up
When I reconnect the primary the default route to the secondary does not go away.
I must either reload the ASA or remove/readd the two default outside routes.
Anyone have this same experience and could lend a hand?
Are there any commands I might have in my config that break SLA?
If so I would have hoped either the Configuration Guide or Command Reference for 8.2 would say so, but I don't see any mentioned.
I'm working remotely with my customer so I can't play with this except on off-hours.
ASA running 8.2(2) so as to use AnyConnect Essentials.
Thx,
Phil

Pls. read and try the workaround.
CSCtc16148 SLA monitor fails to fail back when ip verify reverse is applied
Symptom:
Route Tracking may fail to fail back to the primary link/route when restored.
Conditions:
SLA monitor must configured along with ip verify reverse path on the tracked interface.
Workaround:
1. Remove ip verify reverse path off of the tracked interface
or
2. add a static route to the SLA target out the primary tracked interface.
[Wrap text] [Edit this enclosure]
Release-note: Added 09/23/2009 20:28:24 by kusankar
[Unwrap text] [Edit this enclosure]
Release-note: Added 09/23/2009 20:28:24 by kusankar
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-8.3.1.1_interim-by-cl104097&ext=&type=FILE
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-8.3.1.1_interim-by-cl104097: Added 03/23/2010 11:54:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850&ext=&type=FILE
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-8.3.1_fcs_throttle-by-cl103850: Added 03/22/2010 15:48:05 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-bennu-by-cl101314&ext=&type=FILE
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-bennu-by-cl101314: Added 02/18/2010 19:06:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-idfw-by-cl101317&ext=&type=FILE
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-idfw-by-cl101317: Added 02/18/2010 19:09:07 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-logging-ng-by-cl101311&ext=&type=FILE
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-logging-ng-by-cl101311: Added 02/18/2010 19:03:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-broadview-main-by-cl101300&ext=&type=FILE
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-broadview-main-by-cl101300: Added 02/18/2010 18:27:07 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-64bit-by-cl101362&ext=&type=FILE
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-64bit-by-cl101362: Added 02/19/2010 04:52:24 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-bv64-by-cl101426&ext=&type=FILE
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-bv64-by-cl101426: Added 02/19/2010 11:42:41 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-sedona-main-by-cl101297&ext=&type=FILE
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-sedona-main-by-cl101297: Added 02/18/2010 18:24:15 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-8.2.2_fcs_throttle-by-cl101307&ext=&type=FILE
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-8.2.2_fcs_throttle-by-cl101307: Added 02/18/2010 18:57:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-bennu-by-cl101294&ext=&type=FILE
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-bennu-by-cl101294: Added 02/18/2010 18:24:08 by perforce
[Uwrap text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=fixed-in-titan-main-by-cl101282&ext=&type=FILE
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
[Wrap Text] [Edit this enclosure]
fixed-in-titan-main-by-cl101282: Added 02/18/2010 16:48:04 by perforce
[Uwrap text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankarCan not view this .log file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=sla-mon-sh-tech&ext=log&type=FILE
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankarCan not view this .log file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
[Wrap Text] [Edit this enclosure]
sla-mon-sh-tech: Added 09/23/2009 20:43:52 by kusankar
[Uwrap text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://cdetsweb-prd.cisco.com/apps/dumpcr_att?identifier=CSCtc16148&title=static-analysis-titan-main&ext=&type=FILE
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforceCan not view this . file attachment inline, please click on the following link to view the attachment.
http://
[UnWrap text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
[Wrap Text] [Edit this enclosure]
static-analysis-titan-main: Added 02/18/2010 16:48:07 by perforce
-KS

IP SLA Monitor

Hi all!
We are using IP SLA to monitor the WAN IP from a client:
ip sla monitor 1
type echo protocol ipIcmpEcho 192.168.251.206 source-interface GigabitEthernet0/1
request-data-size 10
timeout 2000
threshold 4000
frequency 5
ip sla monitor schedule 1 life forever start-time now
track 104 rtr 1 reachability
delay down 8 up 30
When the link is down, traffic is switched to another link. The problem is that when we are doing maintenance with the problem link, any oscillation (up/down) causes the link to be switched back to the link with problem. The only solution we found for this case is to give a shutdown on the interface that is being repaired.
Does anyone know what I can do to prevent traffic is switched to the link that is being repaired?
Appreciate any help

Hi Sachin!
I think it would be interesting to increase the monitoring time, if the main link becomes down. You know I can how do this without using load balancing (HSRP, VRRP, GLBP ...)? Because we are monitoring the wan interface of the client, ie, on the other end of the cloud.
Thanks.

SLA Monitoring

I have 2 static routes from source to destination on ASA. I want to give preference to first path and the second path will be the backup path. In case if first path will goes down only then the second path will be used. For this I want to enable SLA monitoring. If i will set number of packets=100, Frequency=20 sec, Timeout= 2sec. I want that when all the 100 packets will be dropped only the backup path will be used.
How can i set this requirement?
Regards,
Mukesh Kumar
Network Engineer
Spooster IT Services

Hello Mukesh ,
I understand that you are trying to achieve redundancy using ipsla track feature and at the same time you want some delay ( you said untill 100 packets are dropped ) in installing secondary route in RIB .
Kindly correct me if wrong .
As a simpler solution , I think you can add delay in number of seconds under track statement , that will achieve same thing but in terms of seconds . So lets say if you have threshold to 20 seconds and delay of 60 seconds , in case of failure condition router will wait untill IPSLA is triggered 3 times with consecutive failures ( as per frequency ) .
Anyways , in case you still need IPSLA track feature based on number of packets drop , please see below as per my understanding :
As you say you will set number of packets = 100 , i assume you are using ICMP-jitter based IPSLA and that can report such drops in reaction configuration . you can use "traponly" keyword to have a log generated when configured number of drop threshold is reached ( kindly ensure to have ip sla logging trap configured ) .
Now you can use this log ( threshold exceeded ) as trigger for an EEM script and do whatever changes are needed in configuration ( eg, static route AD manipulation etc ) .
hope to help .
For any further help please let me know .
Regards
Sunil Bhadauria

Cisco ASA5505 sla monitoring

Hello,
I'm not sure how does the SLA monitoring works...
Example:
sla monitor 123
type echo protocol ipIcmpEcho 10.0.0.1 interface outside
num-packets 3
frequency 10!--- Configure a new monitoring process with the ID 123. Specify the
!--- monitoring protocol and the target network object whose availability the tracking
!--- process monitors. Specify the number of packets to be sent with each poll.
!--- Specify the rate at which the monitor process repeats (in seconds).
When does the routing table change the default route?
If the 3 send packets will get 3x timeout response or it's enought that just one of those 3 packets dont respond?
I would like to set up that the routing table (default route) will rebuild after 30 second of timeout the primary default gateway.
Many thanks
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtml

Hi Martin,
You are missing the track configuration. Track 1 rtr 123 reachability
And then:
sla monitor schedule 123 life forever start-time now
The track is attached to the SLA, so when you pick one default route to monitor (The one with the lower administrative distance) you add the track command, for example:
route outside 0.0.0.0 0.0.0.0 200.20.20.1 1 track 1
route outside2 0.0.0.0 0.0.0.0 200.30.30.1 254
The firewall will be monitoring the first route and when it fails, it will remove it from the routing table.
If the 3 send packets will get 3x timeout response or it's enought that just one of those 3 packets dont respond?
There is a threshold that can be configured to say how many packets you will expect.
Mike
Mike

Cisco ASA SLA monitoring

I'm trying to configure an SLA on some of our ASAs and I want to monitor the hostname of a destination rather than the IP address. The CLI gives me an option to enter IP or hostname, but when I try and use a name rather than an IP address I get:
(config-sla-monitor)# type echo protocol ipIcmpEcho ?
sla-monitor mode commands/options:
Hostname or A.B.C.D IP address or hostname
(config-sla-monitor)# type echo protocol ipIcmpEcho google.com
^
ERROR: % Invalid Hostname
(config)# ping google.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 173.194.37.128, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/46/50 ms
Any ideas or suggestions? I've tried local hostnames just to make sure it wasn't a resolution issue. Substituting with the IP address works fine. We just have a particluar vendor we depend on that has a propensity to change IP addresses to a cloud app we depend on and not tell us.
If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

Hi,
Always used the IP address so I have no previous expirience of configuring with hostname.
The Command Reference is very vague with regards to the definition of the hostname.
Initially I thought that he problem might be that the DNS lookups are not enabled on the ASA so it is not able to determine the IP address itself.
This didnt seem to make a difference.
Then I configured the following
name 1.1.1.1 test
After which it accepted the command with the hostname configured as "test".
So I am guessing the hostname refers to the "name" configurations of the ASA and if that is the case then I would consider it a pretty useless option.
I tried to configure an "object network GOOGLE" that uses "fqdn www.google.com" but it doesnt accept this "object" as the value for the hostname. So I am not really sure if I am missing something with regards to what else could be entered there other than something referenced in the "name" configuration.
On a quick search I could not find anything online in which someone is actually using a hostname instead of the IP address.
Also slightly adding to the confusion is the fact that the Configuration Guide makes no mention of hostname when giving instructions on configuring the target which to monitor for route tracking.
Starting to seem to me that there is no option to use a DNS name as the target for monitoring.
- Jouni

IP SLA Monitor on Cisco 2911

Dear all,
I have a cisco 2911 router that is located in my head office LAN and I use this router to connect to my branch networks. I want to configure IP SLA Monitor on this router to track my WAN Links but it does not support the command IP SLA Monitor. My IOS VERSION is c2900-universalk9-mz.SPA.151-2.T1.bin. Please help tell me how I can configure IP SLA on my router.
Any assistance will be highly appreciated.

The Data Technology Package License part number SL-29-DATA-K9 was changed to the AppX Technology Package License that includes DATA and WAAS features with part number SL-29-APP-K9.
SL-29-APP-K9 (AppX License for Cisco 2900 Series) - USD 1,000.00
Please check the Change in Product Part Number Announcement for the Cisco 2900 Series Integrated Services Routers Data Technology Package Licenses link below for your reference(s):
http://www.cisco.com/c/en/us/products/collateral/routers/2900-series-integrated-services-routers-isr/eos-eol-notice-c51-730946.html

SLA Ping Tracking on 3750 SMI

Hi -
My network is as follows:
Two Cat 3750 running SMI with HSRP at a main site (let's call them s1
and s2 - w/ s1 as the primary).
s1 is connected to a remote site via metro enet to a router r1
s2 is connected to the same remote site via a router r2 connected to a
T1 to r1
r1 and r2 are 1700s w/ IP feature set.
At r1, my default route is to s1 w/ another default route to r2 as a
backup with a higher metric.
Here's what I'm trying to accomplish (this is mainly going to require
configuration on r1 and s1 I think).
The metro enet interface on r1 and s1 NEVER goes down, even if the
circuit does. As a result, I was using SLA tracking on r1 to ping s1.
Works fine - the route fails over and back (although slowly on the
failback).
Problem is on s1. With SMI, how do I say: route traffic to the remote
site via s2 if r1 is not pingable?
I set up SLA monitoring (rtr) on s1, but the tracking functionality
doesn't seem to be in the SMI.
I know this is easily fixed by running EIGRP, but I'm trying to NOT buy
the EMI.
Thanks

the following are the tools for monitoring tools for SLA
1.CiscoWorks Internetworking Performance Monitor (IPM)
2.Cisco Network Service Performance Engine (CNS PE)
3.VPN Solution Center (VPN SC)

Problem with an application running Adobe Flex. Tech people say they cannot monitor, track or catch the problem.

Problem with an application running Adobe Flex. tech people say they cannot monitor, track or catch the problem. Application shuts down and give the following erre:
Failure of server APACHE bridge:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

<moved from Downloading, Installing, Setting Up to Flex>

ASA /Router -SNMP Trap when IP SLA monitored (ICMP timeout)

Hi,
I am looking for some solution for my below requirment
Requirment is :
How do I configure ASA or Router to send SNMP Trap when IP SLA monitored features enabled (ICMP request or 900 millisecond delay from destination IP)
Thanks in advance..

Hi,
Maybe this thread might help you?
https://supportforums.cisco.com/thread/2039293
I have not personally configured these type of SLA configurations on an ASA other than for testing purposes. We handle Dual ISP setups outside the ASA firewalls.
- Jouni

Ip sla monitoring on asa ver 7.0 (6)

how to configure ip sla monitoring on asa ver 7.0 (6) ?

Hello,
In fact was introduced on 7.2.(1)
Components Used
The information in this document is based on these software and hardware versions:
Cisco PIX Security Appliance 515E with software version 7.2(1) or later
Cisco Adaptive Security Device Manager 5.2(1) or later
Related Products
You can also use this configuration with the Cisco ASA 5500 Series Security Appliance version 7.2(1).
Please rate helpful posts,
Julio

Cisco ASA sla and track commands

Cisco ASA 5520's running 8.2.5 and using sla and track commands
Am I right in thinking that sla and track can be used for any pair of routes using diverse routes between 2 locations, these commands are NOT just restricted to being sued for a default route?
Example: I have 2 MPLS carriers between the 2 sites, the networks advertised by the MPLS carriers would be idnetical
e.g.Site A has
route outside 172.16.0.0 255.255.0.0 2.2.2.2 1 track 1
route outside 172.16.0.0 255.255.0.0 3.3.3.3 128
There would of course be the track 1 rtr...command and some corresponding sla commands

Matthew
Am I right in thinking that sla and track can be used for any pair of routes
As far as I know, yes, they don't need to be default routes, it's just that they usually are.
I would have thought if both routes are pointing via the outside interface though the next hop IPs would be in the same subnet ?
Jon

Outlook 2007 Calendar Monitoring: track send event for recurring meetings

Hi,
I'm working on an Outlook 2007, VSTO 2010, .NET 3.5 add-in which monitors AppointmentItem objects changed on the user's calendar. Specifically I'm tracking the send event of the currently selected appointment in the calendar view. Currently my add-in is
set to cancel the send event and call Display() on the selected appointment instead.
I'm testing with Outlook 2007 SP3. The event handler is fired correctly for non-recurring meetings when the user changes the start or end time of the meeting and for recurring meeting occurrences / exceptions when the user changes the end time, but not when
the user changes the start time of a recurring meeting occurrence / exception. These are the specific steps:
Create a recurring appointment with e.g. 3 occurrences, add at least one attendee and send the invitation.
Set the Calendar to display a Week View.
Select the top edge of the first occurrence of the appointment created in step 1 and drag it upwards to increase the length of the appointment by half an hour.
Release the mouse button and press enter to confirm the change.
Answer 'Save changes and send update' in the popup.
At this point the addin should cancel the send event and display the appointment, but actually the event handler is not called. This behavior occurs only when I change the start time of an occurrence / exception. When I change the end time the event handler
is called correctly.
Do you have any clue why the event handler is only called for the one change and not for the other? How could I work around this issue?

Hi Eugene,
Thanks for your reply. Here is my code:
public class ExplorerMonitor {private Explorer explorer;private AppointmentItem selectedAppointment;
public ExplorerMonitor()
this.explorer = Globals.ThisAddIn.Application.ActiveExplorer();
this.explorer.SelectionChange += new ExplorerEvents_10_SelectionChangeEventHandler(Explorer_SelectionChange);
private void Explorer_SelectionChange()
Selection selection = null;
object selectedItem = null;
bool eventsHookedUp = false;
try
// first remove the listeners from the previously selected item
this.StopSelectedItemMonitor();
selection = this.explorer.Selection;
if (selection.Count == 1)
selectedItem = selection[1];
AppointmentItem appointment = selectedItem as AppointmentItem;
if (appointment != null)
this.selectedAppointment = appointment;
((ItemEvents_10_Event)this.selectedAppointment).Send
+= new ItemEvents_10_SendEventHandler(SelectedAppointment_Send);
// Stop monitoring when the item is opened in an explorer window.
this.selectedAppointment.Open
+= new ItemEvents_10_OpenEventHandler(SelectedAppointment_Open);
eventsHookedUp = true;
catch (System.Exception exception)
logger.Error("Caught in Explorer_SelectionChange", exception);
finally
if (!eventsHookedUp)
// only release if we didn't start monitoring it
ComMarshaler<object>.releaseComObject(ref selectedItem);
ComMarshaler<Selection>.releaseComObject(ref selection);
private void SelectedAppointment_Open(ref bool Cancel)
this.StopSelectedItemMonitor();
private void SelectedAppointment_Send(ref bool Cancel)
Cancel = true;
this.selectedAppointment.Display();
private void StopSelectedItemMonitor()
if (this.selectedAppointment != null)
this.selectedAppointment.Open -= new ItemEvents_10_OpenEventHandler(SelectedAppointment_Open);
((ItemEvents_10_Event)this.selectedAppointment).Send
-= new ItemEvents_10_SendEventHandler(SelectedAppointment_Send);
ComMarshaler<AppointmentItem>.releaseComObject(ref this.selectedAppointment);
public static class ComMarshaler<T>
public static void releaseComObject(ref T anObject)
if (anObject != null && Marshal.IsComObject(anObject))
Marshal.ReleaseComObject(anObject);
anObject = default(T);

IP SLA and Tracking for alerting

Hi,
I configured IP SLAs for sites that connect to the Internet via a 2911 router
Config:
ip sla 199
icmp-echo 4.2.2.2 source-interface GigabitEthernet0/2
ip sla schedule 199 life forever start-time now
ip sla logging traps
track 199 ip sla 199
delay down 120 up 120
Works great - sends a syslog message to the Solarwinds box and message sets off an email alert.
We have a couple of smaller sites that connect to the Internet via a 5510. I'm trying to accomplish the same thing but, it doesn't seem to have the options to set a "delay down and delay up"
Below seems to be my only option:
"track 199 rtr 199 reachability"
Will this tracking-config log the ping fail and if so, is there a way to delay the logging for 120 secs - for Up and Down events?
Thanks, Pat

Hello Pat,
Have you tried entering the command "track 199 rtr 199 reachability"
The prompt should look like this after:
Router(config-track)#
Here you should be able to enter the command "delay down 120 up 120" to my recollection.

Oracle Service Bus: Monitoring/Tracking Consumer Services?

Hi,
since we have a Oracle Service Bus and a Oracle Service Registry, is there any standard solution for tracking which consumer services/applications are accessing which provider services? What we need is monitoring the applications (consumer) which are accessing an specific service (provider) registered in the OSB. Is it possible to have this information as monitoring/statistical data in the Oracle Service Bus console? if not, any suggestion to implement such behaviour ?
Thank you in advance,
Antonio.

I would like to have (don't know where) a list with all my consumer services (outside OSB) and so map them with the accessed proxy services (providers on OSB). The aim for this functionality is being able to monitor which consumer services from outside the OSB (then I need a place where these services can be identified and listed) are accessing specific proxy services published as providers on the OSB. Is like "well, I have my proxies published on the OSB, but I need to know WHO (consumers outside the OSB) is accessing to them?". I don't know if such functionality is provided by the Oracle Service Registry or the Service Bus, or it's just a custom implementation without any Oracle product.
Thank you for your help Manoj!
Antonio.

IP SLA Monitor /Tracking 2921

Similar Messages

Maybe you are looking for