topic Re: Problems with network configuration in Operating System - HP-UX

Problems with network configuration

Carles Viaplana — Wed, 14 Dec 2005 06:50:15 GMT

Hello,

I've a system with HP-UX 11.11 and it has network adapter as 10 half duplex when I want 100 full duplex.

I changed it manually using the following command:

lanadmin -X 100FD 2

But when system is rebooted it lose network configuration.

Is there any way to configure network adapter to 100 full duplex?

Note that there's a package running on system and I can't stop it.

Thanks in advance for your help.
Regards,

Carles

Re: Problems with network configuration

Eric SAUBIGNAC — Wed, 14 Dec 2005 06:54:11 GMT

Hi Carles,

U need to modify a config file under /etc/rc.config.d

In order to tell you wich file, please give the type of your network adapter (ioscan and lanscan)

Eric

Re: Problems with network configuration

RAC_1 — Wed, 14 Dec 2005 06:54:41 GMT

Yes. You need to update config file in /etc/rc.config.d/*lan* depending upon what drives is used for card. If drives is btlan, you need to update /etc/rc.config.d/hpbtlanconf file.

Re: Problems with network configuration

Mark Nieuwboer — Wed, 14 Dec 2005 06:58:26 GMT

Hi Charles,

You can configur this in /etc/rc.confi.d/hpbtlanconf

HP_BTLAN_SPEED[0]=100FD

grtz. Mark

Re: Problems with network configuration

Muthukumar_5 — Wed, 14 Dec 2005 07:06:13 GMT

Permanent setting will be enabled on configuring /etc/rc.config.d/*lan* file.

-Muthu

Re: Problems with network configuration

Luk Vandenbussche — Wed, 14 Dec 2005 07:10:58 GMT

Hi Carles,

If you modify it through sam then al the configuration files are put up to date, so it remains 100FD after rebooting

Re: Problems with network configuration

Carles Viaplana — Wed, 14 Dec 2005 08:42:51 GMT

That's just the file I need to modify.

Thanks to all for your help.
Regards,

Carles

Re: Problems with network configuration

rick jones — Thu, 15 Dec 2005 13:30:02 GMT

If the NIC dropped all the way to 10 Mbit half-duplex, it suggests that the other side of the link was incapable of doing 100 Mbit and may be incapable of doing full duplex.

Forcing one side to 100FD does not automagically make the otherside accept it, so it may not actually fix anything.

Some boilerplate I use:

How Autoneg is supposed to work:

When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full duplex if both sides can do
full-duplex.

If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
half-duplex mode.

If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.

So, the following table shows what will happen given various settings
on each side:

Auto Half Full

Auto Happiness Lucky Sorrow

Half Lucky Happiness Sorrow

Full Sorrow Sorrow Happiness

Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
mis-match.

When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of late collisions. On
the side running full-duplex you will see things like FCS errors.
Note that those errors are not necessarily conclusive, they are simply
indicators.

Further, it is important to keep in mind that a "clean" ping (or the
like - eg "linkloop") test result is inconclusive here - a duplex
mismatch causes lost traffic _only_ when both sides of the link try to
speak at the same time. A typical ping test, being synchronous, one at
a time request/response, never tries to have both sides talking at the
same time.