You may want to look in to code that has, if it's shipping yet, bfd triggered HSRP.
Rodney On Mon, Jun 25, 2007 at 01:00:01PM -0500, [EMAIL PROTECTED] wrote: > Sorry the delay..out of office. > No, no tracking. It seems like a process problem. HSRP compete with > other process during WAN failure (like OSPF convergence, MPLS FRR > actions...) on CPU request and some HSRP packets seems to be lost > causing the HSRP state change. > > Rgds, > Alaerte > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
