Date: Wed, 25 Apr 2001 22:21:57 -0400 From: "Dave VanAuken" <dave@hawk-systems.com> To: <freebsd-isp@FreeBSD.ORG> Subject: RE: FreeBSD w 3C905 cannot connect to/through Cisco 3524XL switch Message-ID: <DBEIKNMKGOBGNDHAAKGNMEAPFCAA.dave@hawk-systems.com> In-Reply-To: <Pine.BSF.4.21.0104251457070.24519-100000@workhorse.iMach.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes tried another 3c905... unfortunately we have a mitfull of them over here (in just about all workstations and a bunch of spares to boot). Since no other solutions present themself, will replace the NIC with another brand and see what results. Dave -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Forrest W. Christian Sent: Wednesday, April 25, 2001 5:06 PM To: Dave VanAuken Cc: freebsd-isp@FreeBSD.ORG Subject: RE: FreeBSD w 3C905 cannot connect to/through Cisco 3524XL switch I'm sorry, anyone who uses 3com nics get what they deserve. Throw the @(#*$ 3com card away and get another (any other) nic. :) Even a $10 realtec would be preferrable. Athough the nic of choice seems to be the Intel Pro 100, and I can't say I've had any problems with them. I've just had my fill of problems with 3coms. I'm assuming you have tried another 3c905? I know for a fact that 3com believes in customer testing of their products. I have a friend who worked for a company who was acquired by 3com. He was one of the people who did test and rework. Basically, every unit would be powered on and would be run through a minimal set of tests to at least verify it functioned. 3com management was pissed off that they were failing too many of the units (or better put, they were catching too many problems before they sent them to the customer) and told them that if they weren't able to improve their post-test yeild they would have to just ship the products without doing the electrical testing. On Wed, 25 Apr 2001, Dave VanAuken wrote: > Date: Wed, 25 Apr 2001 16:03:07 -0400 > From: Dave VanAuken <dave@hawk-systems.com> > To: freebsd-isp@FreeBSD.ORG > Subject: RE: FreeBSD w 3C905 cannot connect to/through Cisco 3524XL switch > > Have the environments for the NIC and the Switch port > manually set as you indicated... on both ends. > > Again, the bootup cycle (from the switch's perception) when > the interface is activated, the switch light for the port > goes amber for about 10-15 seconds then green. during this > time, FreeBSD bootup(ifconfig portions) reports the > no-carrier... one entry, still no pings from the switch to > the server or vice versa. Damn annoying. > > Other ideas? > > Dave > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Sean > Chittenden > Sent: Wednesday, April 25, 2001 12:21 PM > To: Dave VanAuken > Cc: freebsd-isp@FreeBSD.ORG > Subject: Re: FreeBSD w 3C905 cannot connect to/through Cisco > 3524XL > switch > > > On Wed, Apr 25, 2001 at 07:57:15AM -0400, Dave VanAuken > wrote: > > router(also cisco) speaks to switch just fine Win2K > workstations > > using 3C905 cards speak to switch just fine FreeBSD > servers using > > 3C905 cards have problems... > > Autonegotiation of network speeds and duplexes is horribly > unreliable. I have administered clusters of FreeBSD systems > that plug > into 6006's and 3524's and there wasn't rhym or reason as to > which > boxes autonegotiated correctly. 100% of the time, with > maybe the > exception of a workgroup environment, you want to manually > set it's > speed to 100 and duplex to full. > > Cisco: > > in if-conf: > speed 100 > duplex full > > on server in /etc/rc.conf: > ifconfig_foo0=".... media 100baseTX mediaopt full-duplex" > > > > ping and other network utils respond with "host is down" > > That's because the switch doesn't see the computer as up. > > > > am wondering if it is not picking up the switch during > boot > > or something. > > Maybe, but auto-neg is bad in every way shape and form and > was > designed for workgroup environments, not servers. If a > server doesn't > negotiate at 100 full, then I've got a problem and I want > the server > to disappear from the network. > > > > using unroutables, here is what the network looks like: > > Network 192.168.1.0/26 > > Router 192.168.1.1 255.255.255.192 WAN (upstream IP addr) > > Switch 192.168.1.5 255.255.255.192 Network 192.168.1.1 > > Workstations 192.168.1.20-24 255.255.255.192 Gateway > > 192.168.1.1 > > FreeBSD1 192.168.1.10 255.255.255.192 Gateway Router > > 192.168.1.1 > > aliased 192.168.1.15-17 255.255.255.192 > > FreeBSD2 192.168.1.11 255.255.255.192 Gateway Router > > 192.168.1.1 > > This won't matter, the 3524XL doesn't, by and large, see > layer > three traffic. They're great switches though, I've only had > one > problem a cluster of 5 of them in over a year of > peration. -sc > > > -- > Sean Chittenden > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > - Forrest W. Christian (forrestc@imach.com) AC7DE ------------------------------------------------------------ ---------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ------------------------------------------------------------ ---------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBEIKNMKGOBGNDHAAKGNMEAPFCAA.dave>