Massive amounts of packet collisions caused by Novell 4.11

[msdonb]

I've got a Novell 4.11 server on a 10mb Cisco EtherFast switch. When trying to upgrade the switch to an HP ProCurve 2600 10/100/1000mb auto-sensing switch, I get massive collisions and all communications to the Novell server crash. The indicator lights on the Cisco show 2/8 live ports with a solid amber color, rather than green. Since it is not a speed sensing device and ONLY 10mb, I'm guessing this means packet collisions. When the Novell server was plugged directly into the new HP switch, I looked at the stats on the switch and it said, "Excessive amount of Giant/Undersized packets detected on port ##". Is there something that needs to be changed on the Novell server to make it work on the new switch? Any ideas on what could be causing this? How do I get to the ethernet/lan settings in 4.11? The inetcfg module doesn't show me what anything regarding the speed/duplex settings on the NIC.

Thanks all.

 

[marvhuffaker]

If your server NIC is hardset to 100MB/Full, and your switch is autosensing, it won't be able to negotiate the link correctly. If it is not possible to hardset the switch port, you'll have to set the server NIC to AUTO detect.

Depending on the NIC, this may be done in INETCFG, but some older NICS (3com) are hardset on the device itself and require a utility from the manufacturer to make the change.

What type of NIC is it?

 

[msdonb]

When I load inetcfg it shows the NIC as "3C980". How do I determine what mode the NIC is running? If it's set to 100/full why can't the hub detect that speed? Furthermore, how is it that the server can function while being set to 100mb/full on a 10mb switch? I haven't come across any settings to set the NIC speeds.

Thanks in advance for your help.

 

[JockMullin]

Are you sure that switch supports IPX?

I don't see RFC 1234 or 1132 in the specs (but just had a quick look). I couldn't immediately find what an amber color means in their mass of manuals, but maybe that is why it is refusing the traffic and Novell is interpreting it as collisions.

A guess out of left field, here.

Jock

 

[msdonb]

The new switch is an HP ProCurve 2626, the old one is a Cisco Netbeyond EtherSwitch 1220. The Cisco is what the Novell server is currently plugged into. The amber lights are on the Cisco device... I'm pretty sure the new HP device supports IPX.

 

[sstoppel]

IP, IPX, none of that have to do with framing. Autonegotiation problems are pretty common, especially in older hardware running NetWare.

I always use INETCFG, which is a utility that allows quick configuration of network components. Warning: If you are loading it for the first time you will have to reboot before you can use it.

Going from memory, I think you choose Boards and in a submenu there is a SPEED setting where you can force the link speed.

 

[msdonb]

I know what screen you are talking about, I've seen it on other Novell systems. However, the interface on this Novell 4.11 looks different and doesn't give me a speed/duplex option to view/modify:

 

[marvhuffaker]

That card is probably managed by the firmware, not the driver. That is common on older 3Com cards.

You "MIGHT" be able to tell what it's running at just by unplugging the cable, then plugging it back in. Watch the Server console and it should tell you that it's unplugged, then connected at 100/Full (or whatever).

The point is, if you need to change it, there must be a utility from 3COM that will do it.

Regarding "How can the server function" question.. The server is most likely functioning fine. The NIC is a modular component that has no real effect on the functionality of the server.

Regarding "Why can't the hub detect it"? Thats a complicated discussion to have, but a rule of thumb is that BOTH NIC and SWITCH port need to be set the same way, otherwise the negotiation won't happen correctly. So either have both set to AUTO or both set to 100/FULL. In your case, you probably need to get the NIC set to AUTO. When a NIC is hardset to 100/Full, there is no negotiation. It just happens. So the switch can't figure out what speed to run at and defaults to the lowest possible option, probably 10/Half.

Another solution, get a new NIC that is controlled from the driver, not the hardware.

 

[msdonb]

If it's functioning fine, plugged into a 10mb switch, then the only possible speeds the NIC could be at would be 10mb half/full right? I've tried setting the new HP switch to 10mb half/auto, but it still crashes. :\ Thanks for your help though.

 

[marvhuffaker]

No. That's not correct.

If the NIC is hard set to 100/Full, it doesn't matter what you plug it into, you're going to have problems.

You need to identify the actual NIC speed (see reference above), then determine what to do from there.

Marvin

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[msdonb]

What I'm saying is that for the server to be functioning fine plugged into a 10mb ONLY switch, one would think that the NIC would have to be set to either 10mb/full or 10mb/half setting, right? If it were hardset @ 100mb/FULL, the server would crap out if it were plugged into a 10mb switch. It's functioning fine as we speak connected to the older Cisco switch. I'll search 3COM for a utility to help me determine the speed settings... thanks for the help.

 

[sstoppel]

I looked at the manual for your card. To force a link speed you need to use the dos utility "3com DOS configuration and diagnostic reports" utility.

Utility download - 2nd from the bottom

http://www.3com.com/products/en_US/...d=5&fname=&sort=prodname&prodcat=all&pgnum=71

Card manual

ftp://ftp.mpccorp.com/support/Server/NIC/NWO1145.PDF

 

[msdonb]

Thank you very much, will try and post results as soon as I have them. I cannot down the server right now as it is mid-day and too many users are connected.

 

[marvhuffaker]

I'm saying 100/full as an example. I don't know what yours is set to. The point is, if one is hardset and one is auto, your negotiation will fail.