How Do I De-Install NetWorking on an HP ?

[Alzhy]

Is it possible to run HP-UX just using the loopback interface? Am an HP-UX neophyte and am trying to install the FDDI drivers on a System that was installed with just the 100BT ethernet. Whenever I do a swinstall, it is complaining that the target host is not available... Or am I just missing a few swinstall parameters to bypass this impasse?

[Sachin Patel · Accepted solution]

Hi Nelson,

If you just want to use loop back address then edit following files

/etc/hosts
/etc/rc.config.d/netconf

Or run
#set_parms ip_address

But this will not solve your problem to solve your problem do the following and then try to run swinstall.

1. kill your named process
2. temportarily change you /etc/hosts entry
127.0.0.1 localhost lopback
to
127.0.0.1 your_host_name loopback

put other entry in comment.

with these settings you can run swinstall now ,
if you still has problem then
you should use the swinstall option
(???x use_alternate_source=true)

Sachin

[Steven E. Protter]

The box/OS needs networking isntalled to run right.

You can modify the startup daemons in /sbin/rc3.d and /sbin/rc2.d by removing or renaming links to not start with S

That will stop networking from starting.

But you are limiting severely what HP-UX can do for you.

swagentd is the daemon that allows swinstall and swremove to work.

I don't think its a good idea to start uninstalling core network technology. Better off pulling the cable out of the NIC card.

SEP

[Michael Steele_2]

'swinstall' requires network configurations or it will fail with an error similar to what you've indicated.

Since you're 100BaseT connection is already installed..., it's likely you've got a /etc/nsswitch.conf problem.

1) Verify nsswitch.conf:

/etc/nsswitch.conf:
...
hosts: files nis dns

2) Verify hostname and ip:

nslookup ip (* returns files: hostname *)

nslookup hostname (* returns files: ip *)

3) 'set_parms initial' will run you through all of your network parameters and allow you to accept or re-enter different values. Reboot follows.

4) The loop back work around Sachin provided is also commonly used and will work.

5) With anything other than a reboot:

swagentd -k
rm /var/adm/sw/products/swlock
rm /var/spool/sw/catalog/swlock
swagentd -r

[Todd Whitcher]

Hi Nelson,

Sounds like you want to set your system up in Standalone mode so you can get swinstall to work and install that FDDI driver. As mentioned HPUX doesnt operate so well w/ out networking, it expects it. If you want to set up your system as a standalone then reference
this doc on ITRC: KBRC00002373

Revert changes after you install the fddi.

Todd

[Alzhy]

After finding out thar swinstall is dependent on networking (whatever type) being up. I did this:

ifconfig lan0 down
ifconfig lan0 unplumb
blanked out netconf
killed swagentd
set hostname to localhost "#hostname localhost"
Now localhost pingable - start swagentd
run SAM
install FDDI drivers
reboot
fix swagentd once more
run SAM.. finally config'd networking on lan1

BTW, any trick to have "set_parms inititial" use lan1 instead of defaulting to lan0?

Thanks all!