Strange behavior of interface lan0

[Alex_133]

We have a 9000/778/B180L(11.00) workstation where we recently replace its faulty mainbord, all the configuration remains same as we use back the original harddisk without reinstalling the OS.

Then we experince strange behavior of the lan0, for example: No other machine is able to ping this machine, but this machine is able to ping everyone.

When this machine establish a connection with some other machine(e.g. Telent/FTP session), then everyone is able to ping it.

I suspect when no TCP/UDP session is establish with other nodes, the OS will bring down the lan0, this may not be the case at all...

Anyone has experience this before?

[Ravi_8]

Hi Alex

can you make lan0 as full duplex.

[John Palmer]

Have you checked for either a duplicate MAC or IP address?

Regards,
John

[Eugeny Brychkov]

Alex,
check 'lanscan' to see if it's reporting card as operational (UP) and correct MAC address. Check 'ifconfig lan0' to see that interfance is up. Check hpetherconf file if there's MAC address assigned to lan0 (HP_ETHER_STATION_ADDRESS)
Eugeny

[T G Manikandan]

I think the interface card is built with the main board.

did you check whether the MAC ADDRESS is specified in the interface configuration files located at /etc/rc.config.d directory.

Having the card replaced the new MAC address is there for the card but still takes the old mac address from the interface card configuration files.

check that out

[Eugeny Brychkov]

TG is right. LAN interface is built into mainboard. And again he's right, hpetherconf file is in /etc/rc.init.d directory. Remove old MAC address for lan0 in this file because this one in the file takes over station's native MAC address. You can check if address is changing by comparing output of PDC (there's a command to display station lan address) and hpux 'lanscan' output
Eugeny

[Eugeny Brychkov]

Sorry, of course /etc/rc.config.d
:o))
Eugeny

[Alex_133]

Hi guys, thanks for all your valuable input, I will be checking the machine tomorrow with these suggestions, thanks again

[Alex_133]

Unfortunately, setting the lan0 to FULL DUPLEX didn't solve the problem. Also, the MAC address is not configured in the /etc/rc.conifg.d/hpbase100conf or /etc/rc.conifg.d/hpetherconf

We can isolate the problem from duplicate IP, DNS, cable or routers, because as long as I establish a TCP(e.g. telnet) to another node in the LAN, the others start getting PING response from this machine, whenever I terminate the session, then the others start having PING timeout.

[T G Manikandan]

Just do a lanscan and find out the MAC address.
DO a ping from this server to a remote PC.

On the remote PC
Do a arp -a and find out the MAC address for the specified ip address.

check whether both the address are same.

REvert

[Eugeny Brychkov]

Alex,
which address PDC and lanscan show? Post here
Eugeny

[Alex_133]

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/20/0 0x001083B81BCB 0 UP lan0 snap0 1 ETHER Yes 119
#


arp cache on other remote machine:
-----------------------------------
00-10-83-b8-1b-cb dynamic


There are they same .....