topic Re: network interface in Operating System - HP-UX

network interface

Amit Manna_6 — Wed, 20 Jul 2005 04:36:21 GMT

HI.

There are two servers in a clustered environment in which two packages are running on one server and one package is running on another server.

We have to change the network card settings for one of the interfaces from half duplex to full duplex

The interface has two logical interfaces: lan1, lan1:1 and lan1:2

netstat -ni
Name Mtu Network Address Ipkts Opkts
lan1:1 1500 10.221.51.0 10.221.51.109 194255240 96761901
lan1 1500 10.221.51.0 10.221.51.61 1300499804 1780481211
lan1:2 1500 10.221.51.0 10.221.51.63 448803833 56064331

Lan1 is the heartbeat IP:

NETWORK_INTERFACE lan1
HEARTBEAT_IP 10.221.51.61
Following is the properties of the lan card.

lan 1 0/5/0/0/4/0 btlan CLAIMED INTERFACE HP A5506A PCI 10/100Base-TX 4 port

Can anybody answer the following:

1) Do we need to shutdown the packages and do we have to do a cmhaltnode?
2) Does the card support full duplex
3) What are steps for carrying out the changes.

Thanks

Re: network interface

RAJESH GANGADHARAN — Wed, 20 Jul 2005 04:56:00 GMT

Amit,

You may directly reset the lan card with lanadmin command with -X option. For this you need to bring down the cluster. For safer side you may bring down just package with cmhaltpkg command.

Steps:

cmhaltpkg -v < package name >
lanadmin -X 100FD

you can get the ppa number of the card from the lanascan command output, please see the value under the Card Inst#.

I hope ths will help you.

Thanks...........Hisham

Re: network interface

Duncan Edmonstone — Wed, 20 Jul 2005 05:00:37 GMT

1) To be safe, I would failover the packages and cmhaltnode the server to be changed.
2) Yes this card does support full-duplex, but you'd better make sure your network switch does as well...you will need to hard code the switch to 100FD too to make sure it doesn't try to auto-negotiate.
3) You've already been given these.

HTH

Duncan

Re: network interface

D Block 2 — Wed, 20 Jul 2005 05:06:16 GMT

Amit-

re: 2) & 3) above..

The FullDuplex setting will be made for the physcial card itself, so this change should apply for all the logical interfaces using this card.

Did you verify your interface card's attributes by running 'landadmin' ? Use the PPA of 1 for your settings.

see sample attached, which shows
how to verify what settings you have, but use Card Instance or PPA '1': lanadmin 1

you can always use # sam under network settings to change this interface to Full-Duplex. (Sam might be the right choice). Another option is to use # lanadmin.

also, have a network engineer verify the same settings on server's connected Switch to this interface.

The issue at hand could be the swith if you see: FD,AUTO, then your interface card is setup as AUTO negotiate with the 'switch'. It could be that the 'switch' is set to Half-Duplex. Verify this before doing anything!
-

re: 1) above..
I would play it safe, and move the packages off this server. Take the node out of the cluster, then apply you modifications.. you might want to even reboot the server and then verify the Full-Duplex settings and that you can Ping each IP before joing it back to the cluster.

my 2-cents,
Tom

Re: network interface

Mahesh Kumar Malik — Wed, 20 Jul 2005 23:35:56 GMT

Hi Amit

Suggest following steps:

1. Halt the packages on the node
2. Halt the node
3. Make changes in lan card setting
4. Start node
5. start package

Since device file related to lan card does not get affected by changing from half duplex to full duplex, it is safe to follow above steps

Regards
Mahesh