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 Message-ID: <DBEIKNMKGOBGNDHAAKGNAEOOFBAA.dave@hawk-systems.com> In-Reply-To: <20010425092122.F13545@rand.tgd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBEIKNMKGOBGNDHAAKGNAEOOFBAA.dave>