Date: Mon, 16 May 2005 23:22:38 +0300 From: "Donatas" <donatas@lrtc.net> To: "Gleb Smirnoff" <glebius@FreeBSD.org> Cc: freebsd-net@freebsd.org Subject: Re: flood with ng_bridge Message-ID: <03c301c55a55$0145d180$9f90a8c0@DONATAS> References: <002001c54702$d2c500c0$9f90a8c0@DONATAS><20050513145255.GA53894@cell.sick.ru> <008701c559da$a9e1b050$9f90a8c0@DONATAS> <20050516130820.GA83360@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
hello, > D> 3. Monitorring traffic with mrtg on ngethxxx and hatm0 interfaces we can se interesting output amplitude fluctations: > D> ftp://temp:temp@217.9.241.242/hatm0.png > D> seems that origin of those fluctations is ng_bridge. > What is the timescale? How long one peak/pit lasts in time? I doubt that this > is related to ng_bridge. crontab: ### Regular MRTG monitoring 0,10,20,30,40,50 * * * * root /usr/local/etc/mrtg/exec_mrtg.sh > /dev/null 2>&1 we have ng_bridge, (bridged: fxp0, ngeth(1-xxx), hatm0) ngethxxx are linked with hatm0 in the following way: hatm0<->atmllc<->ng_vlan<->ng_eiface<-> we've tried tens of variuos configurations on determining the couse of those fluctuations. They seems to be not only in ng_bridge but in kernel.bridge as well. We've tried to change all 3 parameters in ng_bridge and still - those parameters doesn't seems to affect fluctuations. Currently used parameters on ng_bridge are: # ngctl msg ng_bridge: getconfig Rec'd response "getconfig" (2) from "[10f]:": Args: { debugLevel=1 loopTimeout=1 maxStaleness=900 minStableAge=10 } as you see, no loops or loop drops are detected on any ngeth interafce as well: # ngctl msg ng_bridge: getstats 6 Rec'd response "getstats" (4) from "[10f]:": Args: { recvOctets=3036543055 recvPackets=9193928 recvMulticast=75871 recvBroadcast=26 xmitOctets=9532655926 xmitPackets=51347925 xmitMulticasts=43833729 xmitBroadcasts=2174530 }
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03c301c55a55$0145d180$9f90a8c0>