Operating System - HP-UX
1826507 Members
3174 Online
109693 Solutions
New Discussion

Default Gateway Problem For LAN

 
roobala
Frequent Advisor

Default Gateway Problem For LAN

Hi All,

It's again me....
In our L1000 server having HP-11.00
the Default Gateway is not getting saved.
We had tried this using SAM and
through commands also. When ever we
are rebooting the server the gateway
is missing.

Checked /etc/rc.config.d/netconf file also.

Can anyone tell what may be the reason?

Thanks in Advance.
4 REPLIES 4
Alex Glennie
Honored Contributor

Re: Default Gateway Problem For LAN

check for old copies of netconf in /etc/rc.config.d directory and move them out of this dir to elsewhere ?
Berlene Herren
Honored Contributor

Re: Default Gateway Problem For LAN

Do you mean by not being set upon reboot (check /etc/rc.log), or is it going away after awhile? If the former, then I agree with Alex, please ensure you only have one netconf under /etc/rc.config.d >> this includes any with extensions.

If the latter, take a look at the attached document and check for dead gateway.

Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
Dan Hetzel
Honored Contributor

Re: Default Gateway Problem For LAN

Hi Roobala,

If it's the same server which is giving you some troubles with root login, the same answer applies as your /etc/nsswitch.conf has nis maps for networks, protocols, ... (I don't remember exactly) although you're not running NIS or NIS+

Best regards,

Dan

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xcf7937f45ef7d4118fef0090279cd0f9,00.html
Everybody knows at least one thing worth sharing -- mailto:dan.hetzel@wildcroft.com
Brian Hackley
Honored Contributor

Re: Default Gateway Problem For LAN

Roobala,

I have three suggestions. The first is to try using the IP address in /etc/rc.config.d/netconf. For example:
ROUTE_GATEWAY[0]="192.111.154.254"
ROUTE_COUNT[0]="1"
ROUTE_DESTINATION[0]="default"

The second is to tell /etc/nsswitch.conf to look in "files" first, especially for things which are required at boot time to operate correctly. Have all these look at "files"
first: hosts, services, protocols, automount.

If all else fails, I often debug startup script problems by editing the script and adding a "set -x" after the shell identifier in the startup script. For example, edit the /sbin/init.d/net sciprt (also known as the target of the symlink from /sbin/rc2.d/S340net):
#!/sbin/sh
set -x # <---- You can always comment out or remove after testing!

The debug logging goes to stderr, which at boot time is redirected to /etc/rc.log.

After testing is done, comment out the set -x.

Hope this helps,

Brian Hackley
Ask me about telecommuting!