changing ipaddress on hpux10.20

[bhavin asokan]

dear all,

i have to change the server ipaddress

OS: hpux 10.20

current ip address : 128.1.*.*
netmask 255.255.0.0

new ip address: 10.1.*.*
netmask 255.255.0.0

i think there will be problem with netmask.so i have to disable the netmask subnet checking by the command

nettune -s ip_check_subnet_addr 0

shall i have to put any entry on the files to make this change permanant.(like in hpux 11.0 we have to add entry in nddconf.)

regds,

[Steven E. Protter]

I do not think ther is a problem with the netmask.

255.255.0.0 is a valid class B address.

10.1 is a private, unroutable network, but there should be no resistance to changing the ip address.

For temporary changes in ip address, use ifconfig.

For permanent: /etc/rc.config.d/netconf

/sbin/init.d/net stop;/sbin/init.d/net start;

restarts the network. Best to do this from the console and not use sam.

SEP

[Ranjith_5]

Hi Bhavin,

Eventhough initial byte: 0 - 127 comes in Class A IP range, I think 255.255.0.0 netmask will work. There shouldnt be a problem. Do you face any problem by asigning this IP.

Any way go through this earlier post.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=99116

Regards,
Syam

[Hanwant Verma_1]

/sbin/set_parms shell script modifies the system configuration file /etc/rc.config.d/netconf. set_parms does not backup the netconf file, so it's a good idea to back it up yourself before running set_parms:

# cd /etc/rc.config.d
# cp -p netconf netconf.prev

To print the usage for set_parms, run the script with no arguments:

# /sbin/set_parms

After modifying netconf, set_parms will ask you whether you want to reboot the system; this is necessary in order to apply the configuration changes.

You can answer "Yes, Reboot", or you can answer "No, Do Not Reboot" and reboot at a later time.

Hanwant

[Bill Hassell]

Oops, /etc/rc.config.d must NEVER have extra files, previous copies, etc. This is a special directory where the ENTIRE contents will be always be sourced during startup and shutdown, so any previous copies (mistakes and all) will also be run in alphabetical order. So netconf.prev will be run after netconf, thus leading to:

nothing seems to have changed

because the old copy is run after the new one. If you need to save an old copy, put it into a separate directory.