OpenBGPd stability issue on FreebBSD 9-PRERELEASE

Hi! I'm having issues with OpenBGPd openbgpd-4.9.20110612_1 running on FreebBSD 9-PRERELEASE. BGP sessions flap for no reason every ~4hours, bgp sessions itself receive only default form cisco router. FreeBSD 8.2 is not affected. How can I troubleshot this? ___

Re: OpenBGPd stability issue on FreebBSD 9-PRERELEASE

the bce works. What else can be done to debug this ? 27.11.2011, 21:59, "Kevin Oberman" : > On Sun, Nov 27, 2011 at 7:10 AM, Darren Baginski wrote: > >>  Hi! >> >>  I'm having issues with OpenBGPd  openbgpd-4.9.20110612_1 running on   >> FreebBSD 9-PR

Re: OpenBGPd stability issue on FreebBSD 9-PRERELEASE

All RX, not a single packet arrives. 28.11.2011, 04:59, "Adrian Chadd" : > Hi, > > Are all RX frames dropped at that point, or just the BGP TCP session > related IP frames? > > Adrian ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mai

Re: OpenBGPd stability issue on FreebBSD 9-PRERELEASE

So your idea to disable MSI and test? If it's the same issue, it should disappear but would cost performance loss? Am I right ? 30.11.2011, 13:13, "Emil Muratov" : > On 28.11.2011 21:28, Darren Baginski wrote: > >>  All RX, not a single packet arrives. > > I hav

IGB freezes after about 2 weeks of uptime

Hi! After about 2 weeks of uptime I'm getting messages like that: igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 16, hw tdt = 20 igb0: TX(0) desc avail = 1020,Next TX to Clean = 16 igb0: link state changed to DOWN igb0: link state changed to UP Reboot helps, for the next ~2 weeks. Kern

IGB freezes after about 2 weeks of uptime

: Hi! After about 2 weeks of uptime I'm getting messages like that: igb0: Watchdog timeout -- resetting igb0: Queue(0) tdh = 16, hw tdt = 20 igb0: TX(0) desc avail = 1020,Next TX to Clean = 16 igb0: link state changed to DOWN igb0: link state changed to UP Reboot helps, for the next ~2 weeks.

Re: IGB freezes after about 2 weeks of uptime

Same problem on FreeBSD srv-4-2.lab.local 9.0-STABLE FreeBSD 9.0-STABLE #2: Wed Feb 22 18:10:53 UTC 2012 r...@srv-4-2.lab.local:/usr/obj/usr/src/sys/GENERIC amd64 16.02.2012, 02:27, "Jack Vogel" : > And assuming its from the release, please upgrade it to HEAD and try again. > > Jack > > On W

Re: IGB freezes after about 2 weeks of uptime

C'd to 9.x.  Only to 8.x        ---Mike On 2/22/2012 1:23 PM, Darren Baginski wrote: > Same problem on > FreeBSD srv-4-2.lab.local 9.0-STABLE FreeBSD 9.0-STABLE #2: Wed Feb 22 18:10:53 UTC 2012     mailto:r...@srv-4-2.lab.local";>r...@srv-4-2.lab.local:/usr/obj/usr/src/sys/GENER

Re: IGB freezes after about 2 weeks of uptime

has a number of fixes in it to both the > igb and em drivers that is not yet in RELENG_9 nor 8 > > http://lists.freebsd.org/pipermail/svn-src-head/2012-March/035888.html > > ---Mike > > On 4/3/2012 10:19 AM, Darren Baginski wrote: > >>  Still getting same error

Re: IGB freezes after about 2 weeks of uptime

p://lists.freebsd.org/pipermail/svn-src-head/2012-March/035888.html >> >>      ---Mike >> >>  On 4/3/2012 10:19 AM, Darren Baginski wrote: >>>   Still getting same errors on >>>    FreeBSD srv-4-2.lab.local 9.0-STABLE FreeBSD 9.0-STABLE #3: Mon Apr  2 >

PF and ipv6 strange behavior on FreeBSD

Hi! I've noticed rather strange pf behavior on FreeBSD box (8.2 and 7.4 in particular) Consider this rule pass out proto tcp from self to any flags S/SA keep state despite the fact pf starts after netif if doesn't not create rule pass out inet6 proto tcp from 2001:xxx:xxx:xxx::::ff26

Re: PF and ipv6 strange behavior on FreeBSD

Thank you! You are right, exactly the same issue as in PR you mentioned. 09.05.2011, 19:53, "Mike Oliver" : > On Mon, May 9, 2011 at 11:02, Darren Baginski ; wrote: > >>  Hi! >> >>  I've noticed rather strange pf behavior on FreeBSD box (8.2 and 7.4 in

excessive duplicate ACKs

Hi! Could please some tell me if bug http://lists.freebsd.org/pipermail/freebsd-net/2011-February/027895.html was fixed in any release? If not is there any workaround? I'm still facing with it 8.2-RELEASE. Sorry if that question was answered already. Can't find an answer.