Ignite Errors

[Nicky_5]

Hi,

I am trying to install a client through an ignite server but i get the following errors which i have to rectify, and i am not understanding how to do that.

ERROR: There is no software fitting the Core-OS requirements selected for
loading. There must be a software selection (sw_sel) using a software
source (sw_source) with a load_order=0 selected. Check the server's
configuration files. If VUE or CDE has been selected, then verify
that a language has also been chosen.
ERROR: The _hp_os_bitness variable is not set to "32" or "64". This variable
must be set in the config file that supplies the core archive or
depot. If using an archive, make sure you start with the core11.cfg
example config file. When using a depot, make_config will set this
automatically.

I tried going into /var/opt/ignite/clients/0x0060B059E6D7 and modifying the config file to put the bitness as 64. but i still get the error.

For the first error i think i need to run the make_config but again i am not understainding how its run. i even went through the man pages.

Can someone please walk me through this.

[Steven E. Protter]

Ignite builds the machines based on a Core OS cd, which needs to be swcopied to the NFS mount point being used to server ignite.

Have you checked your configuration file syntax with instl_adm -T ??

Syntax:
swcopy -s /cdrom \* @ /location_of_os_image

assumes the core os cd is in the cdrom drive and the name its mounted under is /cdrom

SEP

[Nicky_5]

hi,

i dont have a CD for this OS. Cant i create a depot form my current confuguration or something..

[Peter Nikitka]

No, you cant 'generate' a SW-Depot out of an installation.
You can swcopy another depot locataion, however.

mfG Peter

[Nick W]

Nicky,

The first ERROR is probably where you should be looking first...

The message is saying that the sw_sel area of the config file is suspect - there is, I believe a limit of 80 chars on tag names (including sw_sel description tag)

Check also the install.log file - any errors being reported in there? (eg problems with tftp transfers between Ignite Server and client - preventing eg the config file being pulled over to the client and the client would not be able to access Ignite variables such as _hp_os_bitness...

The second ERROR is indicating theat the Ignite variable _hp_os_bitness has yet to be set (ie is unset) suggesting that the info has not been successfully pulled....

I think you may need to step back and ask the question: Has this ever worked? - if yes then what has changed...?

HTH

Regards,
Nick