On 05/14/98 15:19:12 you wrote:
How are the NICs on the F520 configured? How are the switch ports configured?
Make sure that the duplexes match on both ends.
And, after checking that, I would double-check your setup in terms of routing. Perhaps configurations and netstat -r for each BSD system and filer would be helpful.
Bruce
On Thu, 14 May 1998 18:15:29 CDT, sirbruce@ix.netcom.com wrote:
On 05/14/98 15:19:12 you wrote:
How are the NICs on the F520 configured? How are the switch ports configured?
Make sure that the duplexes match on both ends.
And, after checking that, I would double-check your setup in terms of routing. Perhaps configurations and netstat -r for each BSD system and filer would be helpful.
This turned out to be the problem (and I feel stupid).
I would have sworn up and down and back and forth that I doublechecked everything on the networking side thoroughly --- but I didn't.
The NetApp works fine.
The FreeBSD box, though reporting that it was operating at 100bTX full-duplex, apparently wasn't.
The Catalyst to which the FreeBSD box terminates was manually set to 100bTX fd, but when I switched it to half duplex, things took right off.
The odd part is that there weren't substantial errors reported by the Cat with the differing duplex between the FreeBSD box and the Cat. That confuses me a bit -- I would have expected frame errors and whatnot. I'm not certain if I've got a bad NIC (Intel EtherExpress Pro 10/100B) in the machine or if I've misconfigured it, but I can sort all that out on my own.
My apologies for the goose chase ... I really thought I had looked heavily at the network side before sending the post.
Brett
--- Brett Rabe Email : brett@uswest.net Systems Administrator - U S West Phone : 612.664.3078 Interact - 3S Pager : 612.613.2549 600 Stinson Blvd. Pager : page-brett@uswest.net Minneapolis, MN USA Fax : 612.664.4770
All those who believe in psychokinesis, raise my hand!
On Fri, 15 May 1998, Brett Rabe wrote:
The FreeBSD box, though reporting that it was operating at 100bTX full-duplex, apparently wasn't.
The Catalyst to which the FreeBSD box terminates was manually set to 100bTX fd, but when I switched it to half duplex, things took right off.
2.2.6 should allow you to force certain link negotiation options, rather than relying on autodetect. Use the "media" and "mediaopt" link specifiers to the ifconfig(8) command.
# ifconfig -a fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 10.35.5.203 netmask 0xffffff00 broadcast 10.35.5.255 ether 00:a0:c9:77:34:ca media: 100baseTX <full-duplex> supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000