topic Re: duplex mode in Operating System - HP-UX

duplex mode

John_1005 — Mon, 09 May 2005 09:31:55 GMT

Hello

Following is a quote from a document I am referring about installation on an HPUX system

In order to burn the boot path in the PATH partition of the ReCC PROM., the system has to be duplexed.

Could someone tell what does duplex and simplex systems mean? How to verify their state?

Re: duplex mode

Kent Ostby — Mon, 09 May 2005 09:41:57 GMT

Anand --

What document are you using ? That doesn't sound like any HP-UX install document that I've run into in the past.

Re: duplex mode

Robert Bennett_3 — Mon, 09 May 2005 09:52:50 GMT

I imagine that "duplexed" means "full duplex".

You can check your lan configuration using lanadmin.

# netstat -i (to see which lan is being used for the largest # of inbound/outbound packets)

# lanscan ( to get the ppa or nmid# needed)

# lanadmin
> lan
> ppa # (change to # you found in lanscan)
> d (display info)

hope this helps

B

Re: duplex mode

Steven E. Protter — Mon, 09 May 2005 09:58:59 GMT

full duplex allows for full two way communicaton through a lan interface.

half duplex means traffic can only go one way or the other. It switchs back and forth very quickly, but its slower.

SEP

Re: duplex mode

John_1005 — Mon, 09 May 2005 10:01:39 GMT

Kent, You are correct. I am referring to the vendor specific hardware document.

Robert, Thanks. Which of the following (from lanadmin display) tell if a system is duplex or simplex. Whats the way to change a system from simplex to duplex if its simplex?

PPA Number
Description
Type (value)
MTU Size
Speed
Station Address
Administration Status (value)
Operation Status (value)
Last Change
Inbound Octets
Inbound Unicast Packets
Inbound Non-Unicast Packets
Inbound Discards
Inbound Errors
Inbound Unknown Protocols
Outbound Octets
Outbound Unicast Packets
Outbound Non-Unicast Packets
Outbound Discards
Outbound Errors
Outbound Queue Length
Specific

Ethernet-like Statistics Group

Index
Alignment Errors
FCS Errors
Single Collision Frames
Multiple Collision Frames
Deferred Transmissions
Late Collisions
Excessive Collisions
Internal MAC Transmit Errors
Carrier Sense Errors
Frames Too Long
Internal MAC Receive Errors

Thanks for the help.

Re: duplex mode

Pete Randall — Mon, 09 May 2005 10:06:50 GMT

Just run landadmin -x 0 (where 0 is the PPA or instance number of your NIC, determined from lanscan):

# lanadmin -x 0
Current Config = 100 Full-Duplex MANUAL

Pete

Re: duplex mode

Patrick Wallek — Mon, 09 May 2005 10:07:19 GMT

It would actually be easier with the 'lanadmin -x' command.

Do a lanscan and note the card instance number (Crd In#). The use that as the argument to 'lanadmin -x'. That will tell you the speed and duplex of the lan card.

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x00306E1BFC4C 0 UP lan0 snap0 1 ETHER Yes 119
0/10/0/0/6/0 0x00306E25BB8A 1 UP lan1 snap1 2 ETHER Yes 119
0/10/0/0/7/0 0x00306E25BB8B 2 UP lan2 snap2 3 ETHER Yes 119
0/12/0/0/6/0 0x00306E25BB78 3 UP lan3 snap3 4 ETHER Yes 119
0/12/0/0/7/0 0x00306E25BB79 4 UP lan4 snap4 5 ETHER Yes 119

# lanadmin -x 0
Current Config = 100 Full-Duplex MANUAL

The above tells you that the card instance #0 is at 100 Mbits Full-Duplex and that it has been manually set (most likely in one of the /etc/rc.config.d/hp*conf files).

Re: duplex mode

John_1005 — Mon, 09 May 2005 10:17:02 GMT

lan2 has highest number of i/p and o/p packets.

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
13/0/ Hexaddress 0 UP lan0 snap0 1 ETHER Yes 52
13/0/1 Hexaddress 1 UP lan1 snap1 2 ETHER Yes 52
13/0/2 Hexaddress 2 UP lan2 snap2 3 ETHER Yes 52

I then used lanadmin to change ppa display variable from from 0 to 2 and obtained display values (I posted the parameters earlier)

Since my nmid is 2 (and so the ppa I thought)

# lanadmin -x 2
Error: This option is not supported for this hardware.

Any ideas?

Also, could you please tell what should I do to convert it to duplex if I see it as simplex?

Thanks again

Re: duplex mode

Robert Bennett_3 — Mon, 09 May 2005 10:24:08 GMT

Anand -
Please note that you will have to configure your switch to coincide with any changes you make on the server.

The lanadmin -x n (where n is nmid 10.xx or ppa for 11.xx) will give you your duplex.

to set half to full:
lanadmin -X 100FD n

- or -

lanadmin -S 1 n (where 1 means 100FD)

For 1000:
lanadmin -X auto_on n (where n is nmid for 10, ppa for 11)

need to vi /etc/rc.config.d/hpgelanconf and change 100fd to auto_on

Hey - thanks for the points

B

Re: duplex mode

Patrick Wallek — Mon, 09 May 2005 10:26:28 GMT

Do a

# lanadmin -x 0

# lanadmin -x 1

# lanadmin -x 2

Those are your 3 lan cards. You can use 'lanadmin -X' to change the duplex mode and speed of the card. What you can do depends entirely on what the card supports though. There were some NIC's (for R & D machines for example) that only supported half-duplex.

You will not see simplex for the card. You will see either half-duplex (HD) or full-duplex (FD). If this happens to be a gigabit card then you may see AUTO. Gigabit cards must be set to AUTO to allow for full speed.

Re: duplex mode

Steven E. Protter — Mon, 09 May 2005 10:27:33 GMT

Note:

Older built in lan interfaces are not capable of anything else other than 10 BaseT half duplex.

A built in nic for a D class server is a good example of that.

I once spent a frustrating afternoon trying to get lanadmin to display speed and duplex on one of those and it didn't work out very well.

SEP

Re: duplex mode

John_1005 — Mon, 09 May 2005 11:50:42 GMT

Hello all,

lanadmin -x on this system is returning an error. Is there an alternate way?

Re: duplex mode

Pete Randall — Mon, 09 May 2005 11:59:00 GMT

In that case, the description in the full display should indicate your mode. Mine looks like this:

Description = lan0 HP PCI 10/100Base-TX Core [100BASE-TX,FD,MANUAL,TT=1500]

You could also try "lanadmin -s "

Pete

Re: duplex mode

Himanshu_3 — Mon, 09 May 2005 12:22:05 GMT

Hi Anand,

First of all Can you please check whether your switch has been configured to comminicate with your server in the desired speed and mode in which you want.

Secondly, I would agree with many of my friends here that lanadmin is a nice way to configure the lan card, but in your case since its not working why not try to edit the file in ...

cd /etc/rc.config.d
Here you would find many different files suiting your hardware and select something like hpsppci100conf and edit this file.

Thirdly, check out any latest patches on the HP site for the particular hardware you want to install.

Fourthly, there is one more easy way to find out the lan configuration detail

/usr/sam/lbin/laninfo .

I think it should solve your problems.

Cheers,
Himanshu

Re: duplex mode

John_1005 — Mon, 09 May 2005 12:34:44 GMT

Couple of more points:

1) netstat -i shows lan2 having max i/p o/p packets

lan2 has nmid = 3

I use ppa=3 in lanadmin. These parameter values are "Zeroes".

Last Change
Inbound Octets
Inbound Unicast Packets
Inbound Non-Unicast Packets
Inbound Discards
Inbound Errors
Inbound Unknown Protocols
Outbound Octets
Outbound Unicast Packets

For other ppas they are not zeroes.

2) Description for all ppas is same.

for ppa 0:

Description = lan0 Rockwell LAN Interface Hw Rev 0

Speeds:

ppa 0: Speed = 100000000
ppa 1: Speed = 10000000
ppa 2: Speed = 100000000
ppa 3: Speed = 10000000

Thanks again!!

Re: duplex mode

Pete Randall — Mon, 09 May 2005 12:41:58 GMT

What version of HP-UX are you running? Can you post the output of "ioscan -ifnClan"?

Thanks,

Pete

Re: duplex mode

Pete Randall — Mon, 09 May 2005 12:48:32 GMT

Oops - typo - try this instead:

What version of HP-UX are you running? Can you post the output of "ioscan -kfnClan"?

Thanks,

Pete

Re: duplex mode

John_1005 — Mon, 09 May 2005 12:49:41 GMT

Hi,

This is HP-UX 11.00.01.

ioscan -funC o/p:

# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
lan 0 13/0/0 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan0 /dev/ether0
lan 1 13/0/1 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan1 /dev/ether1
lan 2 13/0/2 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan2 /dev/ether2
lan 3 13/0/3 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan3 /dev/ether3
lan 4 13/0/4 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan4 /dev/ether4
lan 5 13/0/5 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan5 /dev/ether5
lan 6 13/0/6 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan6 /dev/ether6
lan 7 13/0/7 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan7 /dev/ether7
lan 9 13/0/9 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan9 /dev/ether9
lan 10 13/0/10 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan10 /dev/ether10
lan 11 13/0/11 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan11 /dev/ether11
lan 12 13/0/12 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan12 /dev/ether12
lan 13 13/0/13 lan2 CLAIMED INTERFACE Lan Adapter

Re: duplex mode

Pete Randall — Mon, 09 May 2005 12:55:10 GMT

OK, let's back up a step or two, when you ran "lanadmin -x 0", what error did you get?

Pete

Re: duplex mode

John_1005 — Mon, 09 May 2005 12:56:16 GMT

ioscan -kfnClan
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
lan 0 13/0/0 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan0 /dev/ether0
lan 1 13/0/1 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan1 /dev/ether1
lan 2 13/0/2 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan2 /dev/ether2
lan 3 13/0/3 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan3 /dev/ether3
lan 4 13/0/4 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan4 /dev/ether4
lan 5 13/0/5 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan5 /dev/ether5
lan 6 13/0/6 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan6 /dev/ether6
lan 7 13/0/7 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan7 /dev/ether7
lan 9 13/0/9 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan9 /dev/ether9
lan 10 13/0/10 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan10 /dev/ether10
lan 11 13/0/11 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan11 /dev/ether11
lan 12 13/0/12 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan12 /dev/ether12
lan 13 13/0/13 lan2 CLAIMED INTERFACE Lan Adapter
/dev/diag/lan13 /dev/ether13