RE: EEM not working

Thanks guys for quick response....

I tried with \. But it didn't work. i.e. "%DUAL-5-NBRCHANGE:
IP-EIGRP(0) 1: Neighbor 192/.168/.3/.2 (FastEthernet0/0) is down:
holding time expired"

But this message pattern is working "event syslog pattern
".*192.168.3.2.*down.*"

Regards,

Girish

From: Lloyd Ardoin [mailto:Lloyd_at_TheWizKid.biz]
Sent: Wednesday, May 20, 2009 2:28 PM
To: Malla, Girish; ccielab_at_groupstudy.com; nobody_at_groupstudy.com
Subject: RE: EEM not working

I fought this for a long time once. Here is the answer...basic regular
expression formatting issue on the ip address, since the period is a
meta character it has to be escaped like this - 192\.168\.1\.0

HTH,

Lloyd

________________________________

From: Malla, Girish
Sent: Wed 5/20/2009 12:37 PM
To: ccielab_at_groupstudy.com; nobody_at_groupstudy.com
Subject: EEM not working

Experts,

 I am facing problem with below configuration. Anything wrong in this
configuration? The EEM is not able to match this syslog message. Does
the EEM match only specific syslog messages?

event manager applet test

 event syslog pattern "%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor
192.168.2.1 (Serial1/0) is down: holding time expired"

 action 1.0 cli command "enable"

 action 1.1 cli command "configure terminal"

 action 1.2 cli command "no ip route 192.168.1.0 255.255.255.0
fastEthernet 0/0 192.168.3.2"

 action 1.3 syslog msg "Static route removed"

below are the output of "debug event manager all"

*Mar 1 03:56:34.431: fh_fd_syslog_event_match: num_matches = 0

*Mar 1 03:56:34.431: fh_fd_data_syslog: num_matches = 0

Regards,

Girish

Blogs and organic groups at http://www.ccie.net
Received on Thu May 21 2009 - 23:47:03 ART