Gateway : software or hardware problem

[Mike_108]

Hi all,


I done all the solutions given, but I still cannot get that default gateway defined on my system.

other than "/etc/rc.config.d/netconf" file, via SAM and 'route' command, is there any possible solution for this problem?

attach is the output of "ifconfig lan0" and netconf file.

[Corthouts Carlo]

Hi,

Have you tried a traceroute to another system?
Maybe if you provide us with the routing table.
You can get this by running netstat -rn.

[Duncan Edmonstone]

This gaetway is not a firewall by any chance is it?

Does it respond to pings?

HTH

Duncan

[Sanjay_6]

Hi,

your default gateway netmask is missing.

Hope this helps.

Regds

[Darrell Allen]

Hi,

So others can see what you've tried so far:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x2ca18cc5e03fd6118fff0090279cd0f9,00.html

Can you telnet, ftp, rlogin, etc between your 3 HP boxes ( 192.168.1.1, 192.168.1.2, and 192.168.1.3)?

You write:
"route add net 192.168.2.0 192.168.1.251 1" I already tried, still cannot view the default gateway when i run "netstat -rn"

Does that mean that netstat -rn doesn't list the route to net 192.168.2.0? Do you mean you don't see a route with "default" for the destination?

Earlier you posted the following netstat -rn output:
s01amy02 #>netstat -rn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 2815 lo0 4136
192.168.1.2 192.168.1.2 UH 0 925877 lan0 4136
192.168.1.0 192.168.1.2 U 2 0 lan0 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136

Is this still what you have? There is not a route for 192.168.2.0 nor default listed.

Do "route add default 192.168.1.251 1" and post what you get. Then immediately run "netstat -nr" and post the output. Also "ifconfig lan0" output.

I'm running out of ideas.

Darrell

[Duncan Edmonstone]

Sanjay,

Don't think that a missing subnet mask would cause this problem for the default gateway, as:

a) the default gateway will always be in the same subnet as the host

b) If a subnet mask is not given to a route command then the system will assign the longest subnet mask of the configured network interfaces to this route (in this case lan0 with a mask of ffffff00)

Cheers

Duncan

[Johan Gjestvang]

Hi,

If a ping to 192.168.1.251 faile, you may have an firewall as router. Or your
gateway-router is broken.
A firewall is normally set up
not to reply on ICMP messages.

In HP-UX 11.x thereis an failover mechanism for the default router. You can have
an alternate path to achive
redundance. Only one path can
be active at one time so the nr.2 gateway are put in the standby mode. It needs a technich to detect a failure in the comunication with the
"primary" router. This is achived by sending icmp messages to the router on regulary intervals. The absence of ICMP reply will tell HP-UX that the comunication to the primary router is broken. And then, if you have a firewall as router, It will by default not
do reply on ICMP message and therefor the HP-UX will consider this router path as dead.
Thereis,of course, an command to annul this mechanism.

#ndd -set /dev/ip ip_ire_gw_probe 0

It calls Disable Dead Gateway Detection:

To make it permanent; update
your /etc/rc.config.d/nddconf
file.

Add this 3 lines to the file:

TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe
NDD_VALUE[0]=0

NB! the numbers in the brackets like [0] is the
variable index. If you allready have entry in the file,the index must be incremented by one.

Best Regards,
Johan

[Duncan Edmonstone]

Thanks for posting the link Darrell...

Having read through the earlier posts this isn't making any sense! as Darrell stated, I think we need to see an up-to date copy of your routing tables... can you post the output of netstat -rn again, and also the output of 'ndd -get /dev/ip ip_ire_status'

(as an after though... have you checked there are no strange characters in your netconf file? try running it through cat -v to make sure there are no non-printable characters in the config)

HTH

Duncan

[Mike_108]

Hi all,

Thanks a lot on all your effort trying to solve this problem.
Actually I just solved this problem. this problem cause by "/usr/sbin/route" file in this server is corrupted. so, I replaced it back by copying from another server into this server.

This was detected by my senior where he compare the size of this file in this server with another server. and he discover that the file size in this server was 0 byte and the modified date is on 3 march 2002 (I don't know who did this)

once again.
thanks a lot on all your efford

regards

Mike