uh oh, I'm getting ready to deploy a new carp-fancy-doohicky router on a VERY busy connection, using quad card fxp's. Should I delay a smidge until Nov?
--Bryan On Tue, 14 Sep 2004 13:34:05 +0200, Claudio Jeker <[EMAIL PROTECTED]> wrote: > On Tue, Sep 14, 2004 at 12:51:26PM +0200, Marco Matarazzo wrote: > > Hi Matthew, > > > > I've the same problem here with 3.4 (and had the same problem with 3.3). The > > 'hole' in communication is always just 20 seconds. In the beginning I > > thought about a Spanning Tree issue, but after careful inspection, > > everything seems fine. Also tried to swap switches, network cards (all fxp > > tough) etc. The same things also happen with pf disabled, and happen only on > > the trunk interface, the management interface is fine. Tried a netstat -w 1, > > and in those 20 seconds, traffic arrives at fxp0, but not a single packet > > exits. The server just quits routing on the trunk interface, and all vlans. > > At the time that happend, I simply didn't have the time to troubleshoot it > > (since I began noticing it when VoIP customers came in... and that REALLY > > disrupts VoIP!), and now have an old Cisco that routes that. But the > > question still remains... > > The only other thing running at the time was Zebra with full bgp tables (and > > it was before the explosion of the tables that rendered the old kernels > > unusable with full bgp peer). > > I can try to reproduce the problems if it helps the community! > > > > I think you got hit by a fxp bug that was fixed after 3.5. The problem was > that somehow the fxp card did no longer generate an interrupt and so the > watchdog timer reseted the card after 20 seconds. This only happened on > havily loaded links (many interrupts). > > -- > :wq Claudio >
