Spurrious Ignite Errors

[Niall K Watts]

I have an Ignite/UX server configured with a golden for installations. It all works, it is just that I never get a green icon at the end :-(

I think that the errors can be ignored, but I would like to get things nice and neat and with a green icon at the end :-)

I am using HPUX 11i with Ignite B.3.6 to install (And re-install) HPUX 11i clients on rp7400 servers. The errors I get during the installs are -

1. * Could not get DHCP information. No host specific network defaults
will be supplied. (dhcpclient returned: 5)
ERROR: Hostname and/or IP address was not set with instl_adm(1M), and not
obtainable via DHCP.
ERROR: Failed to Start networking.
Failed to startup networking, user interaction required

Now, all my clients are known to the Ignite server and the networking details are all permanent so how do I get around this without setting up a DHCP server ?

2. WARNING: The instance number request for 0/0/4/0 cannot be assigned due to lack
of driver name information. You may need to update your config files
by using the latest save_config command - or by specifying the driver
name on the hw_instance_num keyword (see instl_adm(4)).

I have tried redoing the save_config but with no effect .... and I don't really get where or what I do with hw_instance_num ?

3. WARNING: No such device, tunable, or cdio pbc.
Ignoring the following line.
pbc

Now I have been told that this is a 'non-issue' but I don't have pbc in the kernel on the 'donor' system so why do I get it when installing from the golden image ?

Any help gratefully received,

Cheers

Niall

[Paul McCleary]

Hi,

I've used golden images quite a lot, mainly for installing 11.0 and 11i, on L/N-Class type machines.

I have had several problems but not the one you are experiencing. If I have a system I'm going to Ignite, then I boot it off the Ignite Server ^C when it starts looking for DHCP. Then I setup system parameters like hostname and the networking details - I set this as permanent. I then install from the Ignite GUI and it picks up these previous settings. I then have no problems getting a successful 'green' install.

Dunno whether this will be any help - but I can't see why you're getting the problem you are.

Rgds, Paul

[Bill McNAMARA_1]

The instance number comes from ioscan.

ioscan -fnkClan

for example:
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX
Core
/dev/diag/lan0 /dev/ether0
lan 1 0/2/0/0/4/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100
Base-TX 4 port
/dev/diag/lan1 /dev/ether1 /dev/lan1
lan 2 0/2/0/0/5/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100
Base-TX 4 port
/dev/diag/lan2 /dev/ether2 /dev/lan2
lan 3 0/2/0/0/6/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100
Base-TX 4 port
/dev/diag/lan3 /dev/ether3 /dev/lan3
lan 4 0/2/0/0/7/0 btlan CLAIMED INTERFACE HP A5506B PCI 10/100
Base-TX 4 port
/dev/diag/lan4 /dev/ether4 /dev/lan4

Instances 0, 1, 2, 3, 4

the instance number relates to the device file: lan0...
ifconfig lan0 etc...

The hardware path corresponds to the physical location of the io interface.

Hope that helps some, never saw this error, but assume that your /etc/rc.config.d/netconf or lan settings are incorrect because hardware is not identical on backed up and restored system, and that you have more than one lan i/f on your system.

Later,
Bill

[Hooi Siew Hoong_1]

Hi,

I see all of your warning messages in all my successfully ignited systems. There are readly nothing to worry about.

In order to disable DHCP, at the main menu, choose advance options first, instead of Install HPUX, then there is a option to disable DHCP. Or alternatively, you could add the line disable_dhcp=true in your INSTALLFS.

/opt/ignite/bin/instl_adm -d > tmpfile
echo "disable_dhcp=true" >> tmpfile
/opt/ignite/bin/instl_adm -f tmpfile

You might want to check what is the hardware at 0/0/0/4 and see whether you have a driver installed for it.

cheers
Siewhoong

[Niall K Watts]

Apologies for not posting this sooner, I've been somewhat sidetracked, anyway here's the solutions .....

1. As detailed by Siewhoong I needed to turn off DHCP (Thanks for your help Seiwhoong) and the ignite clients booted quite happily picking up there ip addresses.

2. This took my ages to sort but now I understand it :-) The problem was with a device at 0/0/4/0 which infact was the console, UPS & remote ports on the coreIO. The fix was to add the required kernel driver next to the h/w path in the save_config output such as - hw_instance_num += 0/0/4/0 "tty" "func0" 1 - The messages about h/w instances were somewhat misleading.

3. I never got a fix to this as such but since resolving the other problems this one didn't cause the icon to change from green. From what I have been lead to believe "pbc" was a 'fix' HP used to differentiate between 32bit and 64bit versions of HP-UX that is no longer required ....

I hope someone finds this info of use, laters Niall