From: Joseph Brunner (joe@affirmedsystems.com)
Date: Wed Oct 17 2007 - 18:58:37 ART
Try this, Mr. Steer;
track 5 ip route 141.162.140.0 255.255.255.0 reachability
you'll get (via syslog)
*Aug 18 23:21:55 EDT: %TRACKING-5-STATE: 5 ip route 141.162.140.0/24
reachability Up->Down
You can check with...
r1neaext01#sh track
Track 5
IP route 141.162.140.0 255.255.255.0 reachability
Reachability is Down (no route)
2 changes, last change 00:03:11
First-hop interface is unknown
(when the route comes back)
r1neaext01#sh track
Track 5
IP route 141.162.140.0 255.255.255.0 reachability
Reachability is Up (BGP)
3 changes, last change 00:00:10
First-hop interface is FastEthernet0/0
A cool thing is you can also use these for hsrp/vrrp track. As you probably
know VRRP can't track an interface state, only a tracked objected. Which is
a minor technicality as tracked object can be an interface...
Such as
track 2 int f0/0 line-protocol
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Alex
Steer
Sent: Wednesday, October 17, 2007 4:47 PM
To: Aminul Siddiqui; Ryan Morris
Cc: ccielab@groupstudy.com
Subject: RE: Logging routing table changes
I was looking at monitoring route changes for a customer.
(Un)fortunately they have a very resilient network and devices don't
become unreachable upon failure of pretty much anything. Typically they
have 2 main MPLS circuits and a backup mesh VPN (not adjacent to
customer equipment).
I looked at using SNMP to report routing table changes, its pretty
static unless we make changes. The best I could do was monitor a mib
route change counter. This counter starts at 0 and just keeps going up.
Never does it go back down to 0 after a certain period, so pretty
useless. I'm sure there must be a way without doing something daft like
rmon but I'm not a CCIE and don't know how.
Used different loopback interfaces in the end to determine when the
primary network was down. Still can't tell if we loose one of the main
circuits though as they are connected behind CPEs. I hope the SP can.
Ooow look, the lights off
Alex
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Aminul Siddiqui
Sent: 17 October 2007 21:23
To: Ryan Morris
Cc: ccielab@groupstudy.com
Subject: Re: Logging routing table changes
Hi Ryan,
How about informational logging? If that doesn't help, I can think of
'sh ip
route summary' will give you a list of your subnets. So, if you
maintain
that you can get the difference as a new addition or deletion.
Thanks.
Amin
On 10/17/07, Ryan Morris <ryan@egate.net> wrote:
>
> Hi group,
>
> I have a production network on which I would like to log when changes
to
> the routing table occur (i.e. NOT debug IP routing on my production
> network). Just a basic log message that says "x.x.x.x route
> added/removed". I can't find any documentation for a feature like
this in
> the Cisco documentation.
>
> Any thoughts?
>
> Ryan Morris
> CCIE #18953
>
>
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:15 ART