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

ping problem

sheevm — Thu, 11 Apr 2002 15:24:46 GMT

We have two Lboxes has two lancards one token ring and one ehernet. Token ringcard is attached to the company network it has a default gateway set up.

The ehernet card we want to use it just to communicate between the two unix boxes. We connected two boxes thro' the hub. gave two local IP addresses. 192.10.10.10 and 192.10.10.11

I cannot ping from one to other.

As soon as I ping when I do netstat -rn. I see the entry of a default gateway of my token ring card. It is going thro' the default gateway.

Can some shed some light? Thanks

Re: ping problem

Sridhar Bhaskarla — Thu, 11 Apr 2002 15:40:33 GMT

Hi Raji,

Use traceroute command to find out if the packets are really trying to go through the default gateway. Theoritically, they should not go through the gateway as the other IP address falls in the same broadcast domain.

There are few things to look at.

1. On each system, make sure the interfaces are up by doing ifconfig lan#
2. Ping to the local 192 IP and make sure it works.
3. Check your hub.
4. Use linkloop command to ping to the hardware addr. Run lanscan and get the hardware addresses on both the systems. From one system try this way..

#linkloop -n 1 -i 2 -v hardware_addr

where 2 is the ppa (if lan2 is your lancard) and hardware_addr is the physical addr of the remote system corresponding to the lan card having the same subnet.

5. If you couldn't find the problem still, listout the follwoing outputs.

#lanscan
#netstat -rn
#ifconfig lan?

-Sri

Re: ping problem

Craig Rants — Thu, 11 Apr 2002 15:41:50 GMT

Do you have a route establishe for the lan?

I think you need to add a static route.

route add 192.10.0.0 netmask 255.255.0.0 192.10.10.11 1

I think that I gave you the right syntax

GL,
C

Re: ping problem

Jeff Schussele — Thu, 11 Apr 2002 15:42:06 GMT

Hi Raji,

Yes it probably is.
You'll need to set static routes up:

# route add 192.10.10.10 192.10.10.11 0

Do a #man route for further info on the route command.

And vice-versa on the other system to force them to route thru those NICs.

You'll also want to add the
ROUTE_DESTINATION[x]=192.10.10.11
ROUTE_GATEWAY[x]=192.10.10.10 entries to /etc/rc.config.d/netconf on both systems to make changes permanent.

See the following doc for more info on configuring the netconf file:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90748/B2355-90748_top.html&con=/hpux/onlinedocs/B2355-90748/00/00/23-con.html&toc=/hpux/onlinedocs/B2355-90748/00/00/23-toc.html&searchterms=netconf&queryid=20020411-093733

HTH,
Jeff

Re: ping problem

pap — Thu, 11 Apr 2002 15:42:30 GMT

check /etc/rc.config.d/netconf
in both machines.

-pap

Re: ping problem

Helen French — Thu, 11 Apr 2002 15:47:35 GMT

Hi Raji,

It should not use the gateway as the other network card is falling on the same subnet. Check your configurations properly.

Check this too:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=57d91a93012e263ca9/screen=ckiDisplayDocument?docId=200000009872320

HTH,
Shiju

Re: ping problem

Ron Kinner — Thu, 11 Apr 2002 15:48:31 GMT

Does the hub show Link lights for both devices?

What does your netstat -rn show?

Default should be present and it should point toward your Token Ring Gateway.

There should be an entry for your 192.10.10 network and it should go through the eth0 (or whatever it shows up as)

Try:

lanadmin
lan
display

and it will show you the first card. You may have to change to ppa n+1 to see the Ethernet. It should show you if it's running or not. Packets in/out etc.

Did you install this with SAM or manually enter the changes in your netconf?

Ron

Re: ping problem

Christopher McCray_1 — Thu, 11 Apr 2002 15:51:38 GMT

Are you trying to ping via hostname or by IP address? What does you /etc/hosts file say?

You might have duplicate entries for you servers hostnames with the different IP addresses and the hosts file will only take the first entry. The way I set it up is by modifying the name of you host entry in /etc/hosts to something diffrent (see attached). This was to facilitate private networks for my dedicated heartbeat networks for MCSG.

Hope this helps

Chris

Re: ping problem

sheevm — Thu, 11 Apr 2002 17:20:57 GMT

RON KINNER:

YES BOTH THE LIGHTS ARE UP ON THE HUB.
PINGING ON THE SAME BOX WORKS.
NETSTAT OUTPUT:
-------------------

#Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 274169 lo0 4136
10.10.10.1 10.10.10.1 UH 0 19 du0 1500
192.10.10.10 192.10.10.10 UH 0 0 lan0 4136
172.21.128.48 172.21.128.48 UH 0 3130 lan2 4136
172.21.150.48 172.21.150.48 UH 0 0 lan1 4136
10.10.10.100 10.10.10.1 UH 2 0 du0 1500
172.21.150.0 172.21.150.48 U 2 0 lan1 1500
172.21.128.0 172.21.128.48 U 2 0 lan2 4500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 172.21.128.1 UG 0 0 lan2 4500
#

I tried everything what all you said. When I entered static route entry it said

192.10.10.11 is unreachable cannot add route:

The following is from lanadmin. It says operation status is down??

----------------------------------------------
Lanadmin output

Description = lan0 Hewlett-Packard 10/100 TX Half-Duplex Manual TT = 1500
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e03c930
Administration Status (value) = up(1)
Operation Status (value) = down(2)
Last Change = 26904830
Inbound Octets = 0
Inbound Unicast Packets = 0
Inbound Non-Unicast Packets = 0
Inbound Discards = 0
Inbound Errors = 0
Inbound Unknown Protocols = 0
Outbound Octets = 2460
Outbound Unicast Packets = 60
Outbound Non-Unicast Packets = 0
Outbound Discards = 62
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

-----------------------------------------

linkloop output I did this on one machine:

for both machines

# linkloop -n 1 -i 0 -v 0x00306E0CACF7
Link connectivity to LAN station: 0x00306E0CACF7
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
# linkloop -n 1 -i 0 -v 0x00306E03C930
Link connectivity to LAN station: 0x00306E03C930
error: expected primitive 0x30, got DL_ERROR_ACK
dl_error_primitive = 0x2d
dl_errno = 0x04
dl_unix_errno = 57
error - did not receive data part of message
#

Re: ping problem

Jeff Schussele — Thu, 11 Apr 2002 17:30:36 GMT

What does
#ifconfig lan0
report?

If down, then do
#ifconfig lan0 up

On both systems (if both lan0) & retry.
Also make sure both systems show the SAME speed & duplex settings. Use lanadmin to match them if not.

HTH,
Jeff

Re: ping problem

Ron Kinner — Thu, 11 Apr 2002 18:41:53 GMT

OK, LANADMIN says it's down so you can believe it. You will note that it has not yet received a single packet. It also appears happy with the administration so we don't have to worry about that. What does it say on the other PC?

First question:

Do you have more than one NIC card? Are you sure you have it plugged into the correct card? Sometimes UNIX's idea of lan0 is different than yours. If you have another card or a built-in network connection that you aren't using try plugging your cable in there.

Second Question:

Is there a link light on the HP? Some NICs don't have it but most do. Does it light?
(Does it go out if you unplug it?)

Third question:

Lanadmin says you have Speed = 100000000. Does your hub even do 100 meg? Perhaps you need to set the speed back to 10hd?

4th:

Tried a new cable? If no new cable can you reverse the one you have and see if you still get a link light.

5th:

Tried a crossover cable between the two PCs?

6th:

Replaced the NIC?

Ron

Re: ping problem

Sridhar Bhaskarla — Thu, 11 Apr 2002 18:47:56 GMT

Hi Raji,

Your operation status on lan0 is showing as "down". Also your linkloop if failing. This shows that there is a connectivity problem. Try a crossover cable instead of the hub.

Can you give your ifconfig lan0 on both the systems?

-Sri

Re: ping problem

sheevm — Thu, 11 Apr 2002 19:24:05 GMT

RON:

Answer to your fist question resolved the problem.

It was pluuged into the wrong card.

Thanks to all of you. It is great!!!