topic Re: Problem about NIC duplex in Operating System - HP-UX

Problem about NIC duplex

Ryan Gu — Tue, 24 Jun 2003 04:03:51 GMT

Yestoday,HP has replaced my L1000's nic card.But I found a strange problem.When I telnet or ftp to the IP of this nic.ftp is been refused.And telnet cannot loggin.I found the nic's duplex is half.

If I change the duplex mode of nic from sam.It needs reboot?

Re: Problem about NIC duplex

Fragon — Tue, 24 Jun 2003 04:15:08 GMT

Hi,
you can modify it by using command "lanadmin"!
I haven't change it before so you can get help yourself "#man lanadmin"!
I think reboot is not necessary!

-ux

Re: Problem about NIC duplex

Karthik S S — Tue, 24 Jun 2003 04:16:16 GMT

You are right. It will require a reboot. The following link describes how to set full duplex mode using lanadmin,

http://www.unixadm.net/howto/fulld_hpux11.html

regards,
Karthik S S

Re: Problem about NIC duplex

Con O'Kelly — Tue, 24 Jun 2003 04:16:53 GMT

No you won't need a reboot but you will need to do it from the console.

Ensure that SAM updates the required file (probably hpbase100conf)in /etc/rc.config.d
so that settings are maintained when the system next boots.

Also - Are you sure the duplex setting is causing the ftp & telnet problems?

Cheers
Con

Re: Problem about NIC duplex

Michael Tully — Tue, 24 Jun 2003 04:27:15 GMT

You don't need to reboot when changing the duplex settings. It can be done online, there is a small delay whilst the card resets of around 11 seconds.

# lanadmin -X 100FD 0

Make sure you make the necessary changes to the /etc/rc.config.d/hpbase100conf file. Seeing that you can't telnet to the system, you must do it from the console. Also check that your routing table is still okay and you can telnet to another system on the same subnet.

Re: Problem about NIC duplex

Ron Kinner — Tue, 24 Jun 2003 14:52:36 GMT

Very unlikely that the duplex would keep telnet from logging in or would refuse ftp. Are you sure the card is up? Can you ping it from another PC?

Assuming you run 11.0 or better, on the L1000 run
lanadmin
lan
ppa x
display

Where x is the ppa of your NIC. If you don't know which it is, 0 is usually the builtin LAN and 1 is the separate card. If you have more than two you can run ioscan or just look at the output of netstat -rn it will talk about lan0, lan1, lan2 etc. and usually the ppa is the same as the digit at the end.

Anyway you should get a display which contains the following two lines:

Administration Status (value) = up(1)
Operation Status (value) = up(1)

IF you don't see "up" twice then it is not working. Perhaps the new card's driver is not installed on your PC.

IF that is working then run a linkloop test. That will verify that there is nothing wrong with the card or its MAC. You will need to know the MAC of another device on the same LAN.
See man linkloop for details.

Check your switch that it does not have a static entry for the old MAC. Ditto for the router's arp table.

Finally check your routing tables
netstat -rn
and make sure the IP address has not gotten changed and the default gateway is shown. See if you can ping the default gateway.

Ron

Re: Problem about NIC duplex

Steven E. Protter — Tue, 24 Jun 2003 14:59:08 GMT

check that /var/adm/inet.sec doesn't have something blocked.

Check your switch, especially if its CISCO that it is not set to autonegotiate. HP nics don't like that.

lanadmin -x 0 to check,

replace 0 with the actual number.

You may need to hard code your preferred duplex and speed in a file called, /etc/rc.config.d/hpbtlanconf

Here is mine as an example.

There is already an example of resetting the speed and duplex while the system is running in an earlier reponse.

SEP

Re: Problem about NIC duplex

David_246 — Tue, 24 Jun 2003 15:16:43 GMT

Hi Jason,

The change should be no problem as long as your cisco does not go into stress. Normaly a cisco and HP are always in conflict when both are in auto-negotiate mode. So therefor , or set yours into forced 100fx or the CISCO.
In the worst case your cisco will disable the port beacause of to many errors on the line.

Check you network statistics using "netstat -s" when retransmitions are 10% or above you have a problem (broken cable, one side full the other half). You will spot the problem very clear when the machine has a high network use.

I doubt this will cause the refused error.
Better look at it's arp table ( arp -a) and maybe it should be flushed on both sides.
Ping should at least tell you if it can be reached, telnet can go into the security problems.

Good luck !

If any more help is needed please let us know.

Regs David

Re: Problem about NIC duplex

Caesar_3 — Tue, 24 Jun 2003 19:11:52 GMT

Hello!

No need to reboot, do this
lanadmin -X 100FD
the ID you get from lanscan

And that in the feature this will be the default use /usr/sab/lbin/laninfo
there you will see the type of the card in the end of line, then in /etc/rc.config.d/hp
set the parameters for your card to FD.

Caesar