topic Re: netcard problem in Operating System - HP-UX

netcard problem

thebeatlesguru — Tue, 25 Jun 2002 06:06:18 GMT

i have a hpux box ,it has three netcards ,ip:
192.168.20.15
192.168.26.15
192.168.27.15
i can ping 26.15 and 27.15 well use itself,but i cant ping these two ip use another hpux box which has ip 192.168.26.20 or 192.168.27.20
however can ping 192.168.20.15

whats the matter

Re: netcard problem

Michael Tully — Tue, 25 Jun 2002 06:16:29 GMT

Hi,

Is your lan card actually up so it can be pinged? Use 'ifconfig' on your lan card to find out. If it is 'down' change the status to up

# ifconfig lan0
lan0: flags=1843
inet 10.33.10.13 netmask ffff0000 broadcast 10.33.255.255

# ifconfig lan0 up

HTH
Michael

Re: netcard problem

Peter Kloetgen — Tue, 25 Jun 2002 06:18:28 GMT

Hi Guru,

this has to be a problem with subnetmask settings in my opinion, or a gateway problem. Are the other computers, from which you tried the ping in the same subnet? Or is a router between the computers?

Have a look to your configuration settings there.

Allways stay on the bright side of life!

Peter

Re: netcard problem

thebeatlesguru — Tue, 25 Jun 2002 06:42:20 GMT

i have check the netcard with ifconfig command,and i find all netcards are up,and still cant ping.

Re: netcard problem

Duncan Edmonstone — Tue, 25 Jun 2002 06:46:25 GMT

Hi,

More info required I think...

can you post the output of:

lanscan

netstat -in

netstat -rn

Thanks

Duncan

Re: netcard problem

thebeatlesguru — Tue, 25 Jun 2002 06:51:51 GMT

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 0x001083FAD5FC 0 UP lan0 snap0 1 ETHER Yes 119
0/3/0/0 0x001083F67E59 1 UP lan1 snap1 2 ETHER Yes 119
0/4/0/0 0x001083F67E5E 2 UP lan2 snap2 3 ETHER Yes 119
0/6/0/0 0x00306E06202A 4 UP lan4 snap4 4 ETHER Yes 119
0/7/0/0 0x001083F67E33 3 UP lan3 snap3 5 ETHER Yes 119

netstat -in
Name Mtu Network Address Ipkts Opkts
lan2 1500 192.168.24.0 192.168.24.15 6172 5787
lan1 1500 192.168.26.0 192.168.26.15 0 0
lan0 1500 192.168.27.0 192.168.27.15 0 0
lo0 4136 127.0.0.0 127.0.0.1 3583 3583
netstat -rn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 3583 lo0 4136
192.168.27.15 192.168.27.15 UH 0 0 lan0 4136
192.168.26.15 192.168.26.15 UH 0 0 lan1 4136
192.168.24.15 192.168.24.15 UH 0 1669 lan2 4136
192.168.27.0 192.168.27.15 U 2 0 lan0 1500
192.168.24.0 192.168.24.15 U 2 0 lan2 1500
192.168.26.0 192.168.26.15 U 2 0 lan1 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 192.168.24.254 UG 0 0 lan2 1500

Re: netcard problem

Peter Kloetgen — Tue, 25 Jun 2002 07:14:55 GMT

Hi Guru,

same opinion as in first posting.... It is a problem with subnet mask or gateway. You can have a look into: /etc/rc.config.d/netconf and check the entries for your NICs. Have a look to subnet mask and gateway there.

Allways stay on the bright side of life!

Peter

Re: netcard problem

thebeatlesguru — Tue, 25 Jun 2002 07:17:52 GMT

hi peter???i dont think there are some mistakes with submask ,look here :
lan1: flags=843
inet 192.168.26.15 netmask ffffff00 broadcast 192.168.26.255

lan0: flags=843
inet 192.168.27.15 netmask ffffff00 broadcast 192.168.27.255

Re: netcard problem

Ian Dennison_1 — Tue, 25 Jun 2002 07:22:35 GMT

Does the Switch or Router that the IP Addresses are connected to know about these NICs?

The problem may be that the other hpux servers cannot identify a route to the server.

On your workstation (PC) try a 'tracert [IP Address]'.

Share and Enjoy! Ian

Re: netcard problem

Peter Kloetgen — Tue, 25 Jun 2002 07:24:47 GMT

Hi Guru,

the problem is indeed not the subnet mask, if the settings are the same on the other computers in your network. The problem is the gateway, which is needed to connect computers in different subnets. You have to add the routes to your unreachable NICs on the computer from which you want to connect! I am sure, there is no route configured to the subnets in which you placed your NICs. Am i right?

Allways stay on the bright side of life!

Peter

Re: netcard problem

sven verhaegen — Tue, 25 Jun 2002 07:36:24 GMT

if I understand the issue correctly this is purely a routing issue , a cleint machine vcna point the .20 inbterface from your machien but not the .26 or .27 network interfaces also attached to it , a HP-UX will surely receive the request but as long as it doesn't see then as being needed to route to other networks will ignore them , they are useless to him , you indeed feel no trouble reaching the 192.168.20.15 address from the remote clients as they are on the same .20 subnet , however a remote client needs to know how to reach the 192.168.26 or 192.168.27 network trough your system of via a default gateway which has acces to that networks , you won't be seeing anything in this systems routing table on that , best way to get to these other nets is to check that client failing to ping the 2 other lan interfaces has a default gateway set tot the 192.168.20 interface of your machine or a direct host route to the .26 or .27 IP of your client
or a specific network route to .26 or .27 trough your .20.15 interface....