 DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | reply to luckied
Re: Wierd Netgear switch issue said by luckied:Hi there,
You mentioned changed the NIC on the server to 1000/FD and 100/FD which slowed things down. Did you also make the same change on the switch?
If not, that could be causing your problem since there are collisions on the switchport. I don't know much about Netgear since I'm a Cisco guy, but if there's any way to check for errors, try changing the cable (make sure you are using a straight-through)
Best of luck!
-D
There aren't collisions in a FD switched network
At most the interface buffers could get full but if you check the interface usage and its not 100% then thats not happening. |
|
Reviews:
 ·Videotron
 ·ELECTRONICBOX
·TekSavvy DSL
| said by DarkLogix 
There aren't collisions in a FD switched network
At most the interface buffers could get full but if you check the interface usage and its not 100% then thats not happening.
[/BQUOTE :He didn't say the switch was unmanaged until after my reply. You could still get collisions on a managed switch if one side is auto and the other is forced (hence my recommendation to try and configure the switch port since there were still issues after configuring the system, but you're right.  |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | As long as both sides are FD and not HD then it wouldn't be an issue. |
|
Reviews:
·Videotron
·ELECTRONICBOX
·TekSavvy DSL
| said by DarkLogix:As long as both sides are FD and not HD then it wouldn't be an issue.
You are correct but if the switch was left in auto (the default on most devices)and he hard-coded the end-device then it would negotiate as HD. I work for an ISP and this is incredibly common... |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | Sounds to me like a crapy switch if it does that.
I know on the cisco's I've worked with that when I set the client to HD then look at the interface info on the switch it drops to HD. |
|
Reviews:
·Videotron
·ELECTRONICBOX
·TekSavvy DSL
| said by DarkLogix:Sounds to me like a crapy switch if it does that.
I know on the cisco's I've worked with that when I set the client to HD then look at the interface info on the switch it drops to HD.
Nope, we use a mix of Juniper and Cisco here and it happens all the time when we configure the port as 100/FD or 10FD for a circuit and the customer leaves theirs in auto....their side gets HD and collisions while we see input and CRC errors. |
|
 tubbynetreminds me of the danse russePremium,MVM
join:2008-01-16
Chandler, AZ
kudos:1 | said by luckied:Nope, we use a mix of Juniper and Cisco here and it happens all the time when we configure the port as 100/FD or 10FD for a circuit and the customer leaves theirs in auto....their side gets HD and collisions while we see input and CRC errors.
yes.
there is a fundamental difference in autonegotiation standards between 802.3u and 802.3ab.
q.
--
"...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..." |
|
DarkLogixTexan and ProudPremium
join:2008-10-23
Baytown, TX
kudos:3 | reply to luckied
said by luckied:said by DarkLogix:Sounds to me like a crapy switch if it does that.
I know on the cisco's I've worked with that when I set the client to HD then look at the interface info on the switch it drops to HD.
Nope, we use a mix of Juniper and Cisco here and it happens all the time when we configure the port as 100/FD or 10FD for a circuit and the customer leaves theirs in auto....their side gets HD and collisions while we see input and CRC errors. Odd on my cisco I haven't seen that. |
|
