NIC Duplex mode problem

[gillis]

We just installed new HP Procurve switches on a Netware 5.1 LAN. It appears all ports (except the Server port) are negotiating at 100FDx. However, for some reason the port the server is plugged into is dropping to 100H(alf)Dx and causing constant errors (collisions / CRC). Any port we plug the server into does the same. The switches are set to AUTO but I cannot figure out how to tell what the NIC is doing. Gateway (server maker) tells me we have an integrated Intel NIC that relies on the NOS (Netware 5.1) to force the NIC into a mode.

Can someone please tell me 1) where is the command language for this stored so we can see what is currently happening? and 2) how can I change it to force 100Fdx?

Thanks much, JGiles

 

[salserocito]

Try using SPEED=100 DUPLEX=FULL in the load statement of the card in the AUTOEXEC.NCF. If you are using INETCFG, then go into the BOARDS section and locate the options. If you see that it is greyed out, that means that there is not an option to set the speed and duplex mode for this combination of card and driver.

Good Luck!

 

[gillis]

salserocito.......thanks! I'll go looking for what you've suggested.

jgiles

 

[Warped]

Hi

If you go to the server console and start inetcfg and choose the first options "boards" then choose the appropriate card you have installed and hit Enter you can go down to option "media and line speed" and choose " and hit Enter again and choose "media line speed - option "FULL DUPLEX - 100MBPS" Hit enter and then escape out of it and save options and then reinitialize system. This will force your nic to go full duplex.

Also is your procurve switch a managed switch? If so you can use either the browser, or telnet or HP Toptools(free software from HP) to manage your switch.

Sincerely

Vaughn Bender

Novell CNE 5.x

 

[gillis]

Thanks to all for help - I was able to use inetcfg to find the current board setting; which happened to be 100Fdx. However, apparently if the device (server) is forced to Fdx and the switch port is set to auto, the switch drops back to Hdx. We reconfigured the port to force 100Fdx and they seem to be talking OK now.

Thanks again,

jg