From: Aaron Pilcher (apilcher@itgcs.com)
Date: Thu Jun 22 2006 - 11:50:54 ART
In the newer code you can track on IP routing, so being that you have a
routing protocol that is TCP based it would be "like" tracking a remote
IP/Tcp Session.
It would be like " track 1 interface ser 0/2/0 ip routing "
Also there is a feature called Embeded Event Manager that allows you do some
crazy stuff in the event that something happens and is MUCH simpler to use
the TCL scripting. For example, I used it to have the router issue cli
commands, log the event and send a trap when the state of a tracked object
changed. Without doing the research, you might be able to do something that
would give you quicker convergence than BGP there. Like, If the state of
"ip routing" changes on my serial interface decrement my HSRP.
Lots of details there to work out, but it should be fun. Good luck.
-aaron
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Christopher A Jarosz
Sent: Thursday, June 22, 2006 9:26 AM
To: Ccielab@Groupstudy.Com
Subject: HSRP IP question
Hi everyone ...I have a question for you on HSRP. I know that if you track
an interface and if that interface fails (loss of hardware signals) HSRP
will fail over. How ever, there are some conditions where the failure over
won't happen (like shutting down the tracked serial interface). Is there a
way to failover if a tcp peer dies? We are using BGP and instead of
tracking an interface, is there a way to track a remote BGP peer or an IP
address?
Thanks !!!
chrisj
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:33 ART