Re: issues with Intel Pro/1000 and 1000baseTX
Better yet, just let them autoneg and you won't have these problems :) Jack On Fri, May 15, 2009 at 9:15 AM, Steven Hartland wrote: > Never only set one end manually, always set both the machine and the > switch. > > Regards > Steve > > - Original Message - From: "James Tanis" > To: "FreeBSD Questions" ; < > freebsd-sta...@freebsd.org> > Sent: Thursday, May 14, 2009 4:12 PM > Subject: issues with Intel Pro/1000 and 1000baseTX > > > I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in >> question is: >> >> em1: port >> 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at >> device 0.1 on pci4 >> >> what we get after boot is: >> >> em1: flags=8943 metric 0 >> mtu 1500 >> options=19b >> ether 00:30:48:xx:xx:xx >> inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> >> The problem is that the NIC refuses to connect at 1000baseTX. >> >> It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX >> on ports 23 and 24. This particular computer is connected on port 24. I have >> a much older end user system which uses the same card (but earlier >> revision), runs Windows XP and is plugged in to port 23. The end user system >> has no problem connecting at 1000baseTX. I have of course tried switching >> ports. >> >> Attempting to force 1000baseTX via: >> >> ifconfig em1 media 1000baseTX mediaopt full-duplex >> >> gets me: >> >> status: no carrier >> >> After forcing the NIC to go 1000baseTX the LEDs on the backpane are both >> off. I can only come to the conclusion that this is a driver issue based on >> previous experience and the simple fact that the end user system is capable >> of connecting at 1000baseTX. Anybody have any suggestions? I'm hoping I'm >> wrong. I'd rather not do an in-place upgrade, this is a production system >> and the main gateway for an entire school, when I do not even know for sure >> whether this will fix the problem. It's worth it to me though, having a >> 1000baseTX uplink from the switch would remove a major bottleneck for me. >> >> Any help would be appreciated. >> >> -- >> James Tanis >> Technical Coordinator >> Computer Science Department >> Monsignor Donovan Catholic High School >> >> ___ >> freebsd-sta...@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> >> > > This e.mail is private and confidential between Multiplay (UK) Ltd. and the > person or entity to whom it is addressed. In the event of misdirection, the > recipient is prohibited from using, copying, printing or otherwise > disseminating it or any information contained in it. > In the event of misdirection, illegible or incomplete transmission please > telephone +44 845 868 1337 > or return the E.mail to postmas...@multiplay.co.uk. > > ___ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
Never only set one end manually, always set both the machine and the switch. Regards Steve - Original Message - From: "James Tanis" To: "FreeBSD Questions" ; Sent: Thursday, May 14, 2009 4:12 PM Subject: issues with Intel Pro/1000 and 1000baseTX I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in question is: em1: port 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at device 0.1 on pci4 what we get after boot is: em1: flags=8943 metric 0 mtu 1500 options=19b ether 00:30:48:xx:xx:xx inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active The problem is that the NIC refuses to connect at 1000baseTX. It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX on ports 23 and 24. This particular computer is connected on port 24. I have a much older end user system which uses the same card (but earlier revision), runs Windows XP and is plugged in to port 23. The end user system has no problem connecting at 1000baseTX. I have of course tried switching ports. Attempting to force 1000baseTX via: ifconfig em1 media 1000baseTX mediaopt full-duplex gets me: status: no carrier After forcing the NIC to go 1000baseTX the LEDs on the backpane are both off. I can only come to the conclusion that this is a driver issue based on previous experience and the simple fact that the end user system is capable of connecting at 1000baseTX. Anybody have any suggestions? I'm hoping I'm wrong. I'd rather not do an in-place upgrade, this is a production system and the main gateway for an entire school, when I do not even know for sure whether this will fix the problem. It's worth it to me though, having a 1000baseTX uplink from the switch would remove a major bottleneck for me. Any help would be appreciated. -- James Tanis Technical Coordinator Computer Science Department Monsignor Donovan Catholic High School ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
On Thu, May 14, 2009 at 11:54:00AM -0400, Bill Moran wrote: > In response to James Tanis : > > > I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in > > question is: > > > > em1: port > > 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at > > device 0.1 on pci4 > > > > what we get after boot is: > > > > em1: flags=8943 metric 0 > > mtu 1500 > > options=19b > > ether 00:30:48:xx:xx:xx > > inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 > > media: Ethernet autoselect (100baseTX ) > > status: active > > > > The problem is that the NIC refuses to connect at 1000baseTX. > > > > It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX > > on ports 23 and 24. This particular computer is connected on port 24. I > > have a much older end user system which uses the same card (but earlier > > revision), runs Windows XP and is plugged in to port 23. The end user > > system has no problem connecting at 1000baseTX. I have of course tried > > switching ports. > > > > Attempting to force 1000baseTX via: > > > > ifconfig em1 media 1000baseTX mediaopt full-duplex > > > > gets me: > > > > status: no carrier > > > > After forcing the NIC to go 1000baseTX the LEDs on the backpane are both > > off. I can only come to the conclusion that this is a driver issue based > > on previous experience and the simple fact that the end user system is > > capable of connecting at 1000baseTX. Anybody have any suggestions? I'm > > hoping I'm wrong. I'd rather not do an in-place upgrade, this is a > > production system and the main gateway for an entire school, when I do > > not even know for sure whether this will fix the problem. It's worth it > > to me though, having a 1000baseTX uplink from the switch would remove a > > major bottleneck for me. > > While it's _possible_ that this is a driver issue, it's much more likely > (in my experience) that it's a mismatch between the two network devices > (the HP and the NIC). > > Try forcing on both ends (I assume the Procurve will allow you to do that). > One thing I've seen consistently is that if you force the speed/duplex on > one end, the other end will still try to autoneg, and will end up with > something stupid like 100baseT/half-duplex, or will give up and disable No, this is not a stupid thing, it's result of parallel detection. See IEEE 802.3 Std 28.2.3.1 for more details. This is one of reason why users should always use 'auto-negotiation' on 1000baseT media. > the port. > > Also, try autoneg on both ends. Make absolutely sure the Procurve is set > to autoneg. > > Replace the cable. If the cable is marginal, autoneg will downgrade the > speed to ensure reliability. Use a cable that you know will produce > 1000baseTX because you've tested it on other systems. > > Try switching out the NIC. Manufacturing QA isn't 100% reliable, sometimes > you get a card that's just flaky. > > Hope this helps. > > -- > Bill Moran > http://www.potentialtech.com > http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
On Thu, May 14, 2009 at 12:29:17PM -0400, James Tanis wrote: > Bill Moran wrote: > >In response to James Tanis : > > > > > > > >><.. snip ..> > >>Attempting to force 1000baseTX via: > >> > >>ifconfig em1 media 1000baseTX mediaopt full-duplex > >> > >>gets me: > >> > >>status: no carrier > >> > >>After forcing the NIC to go 1000baseTX the LEDs on the backpane are both > >>off. I can only come to the conclusion that this is a driver issue based > >>on previous experience and the simple fact that the end user system is > >>capable of connecting at 1000baseTX. Anybody have any suggestions? I'm > >>hoping I'm wrong. I'd rather not do an in-place upgrade, this is a > >>production system and the main gateway for an entire school, when I do > >>not even know for sure whether this will fix the problem. It's worth it > >>to me though, having a 1000baseTX uplink from the switch would remove a > >>major bottleneck for me. > > > > > >Try forcing on both ends (I assume the Procurve will allow you to do that). > >One thing I've seen consistently is that if you force the speed/duplex on > >one end, the other end will still try to autoneg, and will end up with > >something stupid like 100baseT/half-duplex, or will give up and disable > >the port. > > > Ok, I just did that -- I have now attempted to force 1000baseTX on both > sides and on one side while the other was left auto, all three possible > combinations resulted in the same behavior (no carrier). > >Also, try autoneg on both ends. Make absolutely sure the Procurve is set > >to autoneg. > > > This was the original set up. It is also how I have it set up currently, > it results in 100baseTX full-duplex on both sides. > >Replace the cable. If the cable is marginal, autoneg will downgrade the > >speed to ensure reliability. Use a cable that you know will produce > >1000baseTX because you've tested it on other systems. > > > Well, I don't have any verified working cable of the appropriate length > so I simply switched out the cables for the main server and the backup > server. They are both cat6 cables crimped with cat5e modules by me. For > what reason (bad crimp job?) that seemed to fix the issue. > This is clear indication of cabling issue. PHY of em(4) will try to fix all cabling problem with auto MDI/MDIX/polarity correction. If the PHY couldn't establish a 1000baseT link with link partner it would downshift to 100baseTX as establishing a 1000baseT link was not possible due to cabling problems(probably missing wiring). > Thanks for the advice! > > -- > James Tanis > Technical Coordinator > Computer Science Department > Monsignor Donovan Catholic High School ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
> Well, I don't have any verified working cable of the appropriate length > so I simply switched out the cables for the main server and the backup > server. They are both cat6 cables crimped with cat5e modules by me. For > what reason (bad crimp job?) that seemed to fix the issue. On stranded cable, it often happens that some wire will swap when you insert the connector. Remember that to work at gigabit, you need the four twisted pairs to be properly set: more risks to make a mistake... I know I prefer to buy my patch cords (stranded cables) ready made, while I can do the wall wiring (solid cable) by myself. Bests, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
In response to James Tanis : > Bill Moran wrote: > > > Replace the cable. If the cable is marginal, autoneg will downgrade the > > speed to ensure reliability. Use a cable that you know will produce > > 1000baseTX because you've tested it on other systems. > > > Well, I don't have any verified working cable of the appropriate length > so I simply switched out the cables for the main server and the backup > server. They are both cat6 cables crimped with cat5e modules by me. For > what reason (bad crimp job?) that seemed to fix the issue. QC on patch cables is sketchy. Most places are usually good, but even the best companies will have a bad crimp every now and again. Add to that how they are generally handled ... I mean, statistically there's a good chance that cable was on the floor and someone stepped on it or something ... -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
Bill Moran wrote: In response to James Tanis : <.. snip ..> Attempting to force 1000baseTX via: ifconfig em1 media 1000baseTX mediaopt full-duplex gets me: status: no carrier After forcing the NIC to go 1000baseTX the LEDs on the backpane are both off. I can only come to the conclusion that this is a driver issue based on previous experience and the simple fact that the end user system is capable of connecting at 1000baseTX. Anybody have any suggestions? I'm hoping I'm wrong. I'd rather not do an in-place upgrade, this is a production system and the main gateway for an entire school, when I do not even know for sure whether this will fix the problem. It's worth it to me though, having a 1000baseTX uplink from the switch would remove a major bottleneck for me. Try forcing on both ends (I assume the Procurve will allow you to do that). One thing I've seen consistently is that if you force the speed/duplex on one end, the other end will still try to autoneg, and will end up with something stupid like 100baseT/half-duplex, or will give up and disable the port. Ok, I just did that -- I have now attempted to force 1000baseTX on both sides and on one side while the other was left auto, all three possible combinations resulted in the same behavior (no carrier). Also, try autoneg on both ends. Make absolutely sure the Procurve is set to autoneg. This was the original set up. It is also how I have it set up currently, it results in 100baseTX full-duplex on both sides. Replace the cable. If the cable is marginal, autoneg will downgrade the speed to ensure reliability. Use a cable that you know will produce 1000baseTX because you've tested it on other systems. Well, I don't have any verified working cable of the appropriate length so I simply switched out the cables for the main server and the backup server. They are both cat6 cables crimped with cat5e modules by me. For what reason (bad crimp job?) that seemed to fix the issue. Thanks for the advice! -- James Tanis Technical Coordinator Computer Science Department Monsignor Donovan Catholic High School ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
In response to James Tanis : > I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in > question is: > > em1: port > 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at > device 0.1 on pci4 > > what we get after boot is: > > em1: flags=8943 metric 0 > mtu 1500 > options=19b > ether 00:30:48:xx:xx:xx > inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > > The problem is that the NIC refuses to connect at 1000baseTX. > > It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX > on ports 23 and 24. This particular computer is connected on port 24. I > have a much older end user system which uses the same card (but earlier > revision), runs Windows XP and is plugged in to port 23. The end user > system has no problem connecting at 1000baseTX. I have of course tried > switching ports. > > Attempting to force 1000baseTX via: > > ifconfig em1 media 1000baseTX mediaopt full-duplex > > gets me: > > status: no carrier > > After forcing the NIC to go 1000baseTX the LEDs on the backpane are both > off. I can only come to the conclusion that this is a driver issue based > on previous experience and the simple fact that the end user system is > capable of connecting at 1000baseTX. Anybody have any suggestions? I'm > hoping I'm wrong. I'd rather not do an in-place upgrade, this is a > production system and the main gateway for an entire school, when I do > not even know for sure whether this will fix the problem. It's worth it > to me though, having a 1000baseTX uplink from the switch would remove a > major bottleneck for me. While it's _possible_ that this is a driver issue, it's much more likely (in my experience) that it's a mismatch between the two network devices (the HP and the NIC). Try forcing on both ends (I assume the Procurve will allow you to do that). One thing I've seen consistently is that if you force the speed/duplex on one end, the other end will still try to autoneg, and will end up with something stupid like 100baseT/half-duplex, or will give up and disable the port. Also, try autoneg on both ends. Make absolutely sure the Procurve is set to autoneg. Replace the cable. If the cable is marginal, autoneg will downgrade the speed to ensure reliability. Use a cable that you know will produce 1000baseTX because you've tested it on other systems. Try switching out the NIC. Manufacturing QA isn't 100% reliable, sometimes you get a card that's just flaky. Hope this helps. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: issues with Intel Pro/1000 and 1000baseTX
On Thu, May 14, 2009 at 9:12 AM, James Tanis wrote: > I have a FreeBSD v7.0 box it has two Intel Pro/1000 NICs, the one in > question is: > > em1: port > 0x2020-0x203f mem 0xd806-0xd807,0xd804-0xd805 irq 19 at > device 0.1 on pci4 > > what we get after boot is: > > em1: flags=8943 metric 0 > mtu 1500 > options=19b > ether 00:30:48:xx:xx:xx > inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > > The problem is that the NIC refuses to connect at 1000baseTX. > > It's connected to a HP Procurve 1700-24 switch which supports 1000baseTX on > ports 23 and 24. This particular computer is connected on port 24. I have a > much older end user system which uses the same card (but earlier revision), > runs Windows XP and is plugged in to port 23. The end user system has no > problem connecting at 1000baseTX. I have of course tried switching ports. > > Attempting to force 1000baseTX via: > > ifconfig em1 media 1000baseTX mediaopt full-duplex > > gets me: > > status: no carrier > > After forcing the NIC to go 1000baseTX the LEDs on the backpane are both > off. I can only come to the conclusion that this is a driver issue based on > previous experience and the simple fact that the end user system is capable > of connecting at 1000baseTX. Anybody have any suggestions? I'm hoping I'm > wrong. I'd rather not do an in-place upgrade, this is a production system > and the main gateway for an entire school, when I do not even know for sure > whether this will fix the problem. It's worth it to me though, having a > 1000baseTX uplink from the switch would remove a major bottleneck for me. > > Any help would be appreciated. > > -- > James Tanis > Technical Coordinator > Computer Science Department > Monsignor Donovan Catholic High School > I'm going to point the finger at the possibility of the Ethernet cable itself. Gigabit link requires CAT5e or better (CAT6). A CAT5 alone is NOT enough to give gigabit speeds. Check the markings on the cable, replace if it's not a 5e or 6 and try again. This includes the discussion of proper terminating and twist requirements. --Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
