topic Re: lanadmin autosensing? in Operating System - HP-UX

lanadmin autosensing?

Boonchu Ngampairoijpibu_1 — Thu, 10 May 2001 15:33:40 GMT

When I type the command lanadmin, I found the message like below:
# lanadmin -x 1
Current Speed = 100 Full-Duplex Auto-Negotiation-OFF

So, I'm quite not sure what is different the Auto-Negotiation-OFF from PCI 3COM autosensing feature.

Can I turn it on?

Re: lanadmin autosensing?

James R. Ferguson — Thu, 10 May 2001 15:39:02 GMT

Hi:

It is best to nail your switch for the speed you want and leave 'auto-negotiation' OFF. You're assured of getting what you want this way.

...JRF...

Re: lanadmin autosensing?

Peter Van Sant — Fri, 11 May 2001 01:04:48 GMT

By default 100bt lan cards use auto negotiation to set their speed and duplex.
If during boot an entry is found for the
card in the appropriate /etc/rc.config.d/
file that entry will overide auto negotiation.

When you do lanadmin -x you see Auto Negotiation Off if it found an entry,
otherwise you will just see whatever speed and duplex were negotiated with the switch.

For instance;

$ lanadmin -x 1
Current Speed = 100000000 Half-Duplex

Tells me auto negotiation was used.

Re: lanadmin autosensing?

RAJESH GANGADHARAN — Fri, 01 Jun 2001 07:23:35 GMT

it's best u have the same setting in both sitch and hp box
u can change it by
lanadmin -X AUTO_ON 1
this will reset the card and the new settings will take place
better don't make it ON , make changes in switch only

raj

Re: lanadmin autosensing?

Darrell Allen — Mon, 04 Jun 2001 20:07:05 GMT

Hello,

I don't know what it is with auto-negiotiation but I'd never assume it's going to work correctly. My experience is that it usually doesn't. I would always set the speed and duplex settings on both the server and the switch manually. There's not much worse than working an issue only to find the switch and server don't have the same settings.

Darrell

Re: lanadmin autosensing?

Mark Seida — Wed, 06 Jun 2001 20:50:42 GMT

We tried running with autosensing and everytime the switch would have a different setting for duplex than the workstation. If this is on a visualize workstation you will have to stop it at boot and do CO and then LC to check what the settings are for the card. We set all our workstations to LC 100/full_dx. That stopped all our frame size errors and we set the switches to 100 full.