[BUGS] freebsd ethernet traffic load

jonathan michaels jlm at caamora.com.au
Thu Nov 8 00:05:11 EST 2007


On Wed, Nov 07, 2007 at 09:20:19PM +1100, Andrew wrote:
> 
> 
> On Wed, 7 Nov 2007, jonathan michaels wrote:
> 
> > running at 33k6 bits/s. these collisions have only started
> > since the rest of teh network was upgraded to 100 mhz
> > operating (switch 10/100 mhz telesys "centrecom fs708").
 
> I would check your duplex settings then - make sure the switch and your 
> FreeBSD box both agree as to full or half duplex. Auto-negotiation doesn't 
> seem to be that reliable.

the fs708 was a cheap 8 port 10/100 switch back in 1997ish
$1100rrp i got a discount), it was good for its time but not
what is called 'intelegent' it is basically an on/off type
switch.

another datapoint, i was looking over teh maintenance reports
and discovered that while teh gw box has a small collision
increment (daily) the mailserver (a similar, actually an
identical machine brought from teh same vendor and it too
reports collisions with a daily increment avg 100, peak 270,
min 40, total 700

the rest of teh machines, are 5500r/6400r class machines using
intel 10/100 nics and don't have any collisions even at aprox 10
times teh traffic from earlier reboots.

all teh switches i have now are "intelligent" with i think web
interfaces and fortunately for me serial console ports. i don't
know how to use browser to access teh internal web thingie to
get at teh internal management stuff .. i tried looking at 1..
those rfc addresses that are not routable that i cannot recal
at teh moment.
 
> When I used to have to worry about such things I would set both the switch 
> and the ethernet card to full duplex and so avoid using auto-negotiation at 
> all. On the FreeBSD end it will be something like:

thats what i was trying to do, but i only can get to teh
computer side nic via ifconfig(8)
 
> ifconfig dc0 media 100baseTX mediaopt full-duplex
> 
> (this is assuming your card and switch support 100Mb full-duplex - use the 
> fastest capabilities they have in common if one or both don't).
> 
> Different switches will be configured differently but hopefully its 
> obvious for yours - otherwise someone on this list may have used the same 
> model you have and can give you a hint

here is teh list ...

d-link		dfe-2624x/dfe-2426ix (this pair makes a 48 port switch)
nortel		baystack 350-24t switch
cabletron	smart switch router ssr-2  

these are all 10/100 mhz switchs with ethernet and serial ports
for management 

any infromation would be greatly appreciated, esp how to use
teh ethernet port and teh internet web interface. as far as i
know all three have same type of managment.

> If you can't configure your switch (cheap ones don't support much more 
> than on and off) then make sure you _don't_ set media and mediaopt on the 

yes, thats what i discovered on teh fs708 beastie.. hopefully i
can discover how to crack teh code of eht master switch
maintaners .. grin

> FreeBSD end as the switch will be using auto-negotiation and if your 
> FreeBSD box doesn't then it will definitely get it wrong in my experience.


are digital chipsets any more prevelant to this kind 'madness'
?? than intel nic's ?? or is this something to do with 10 mhz
operating a opposed to 100 mhz operatings ?? it seems odd to me
that only the 10 mhz nics are collisionings when fro t10 plus
years they were stable reliable no coll's and as soon as i add
3 100 mhz boxa bing collis's whni i take them off no more
collisions ?? this behavioue seems odd to me shomehow ??

sorry getting tired my thinking/typing getting poorer than
usual ...

appologies/kind regards

jonathan

-- 
================================================================
powered by ..
QNX, OS9 and freeBSD  --  http://caamora com au/operating system
==== === appropriate solution in an inappropriate world === ====


More information about the BUGS mailing list