Ignite Server recovery for Itanium fail with Enviroment message

[Jimmy Aulestia_2]

I have a ignite server with the ignite netwotk backup of a client. Both have the same ignite and hpux version.

The client boot from ignite server, the client hast the UI for install, but when use GO! for install i have this message and can´t install(recovery the system)

"The currently selected configuration does not contain any environments. You may want to select another configuration"


In the UI the enviroment title is disable.

What is the problem?

Thanks,

[sen_ux]

What is there in the "Configurations" field.?

sen

[Jozef_Novak]

Check whether you have the correct IP address / hostname of the client configured in /etc/bootparams on the Ignite server. Check also other parameter definitions for possible mistakes.

[Jannik]

http://docs.hp.com/en/5992-5230/ch02s03.html

Common Errors

Note:

The currently selected configuration does not contain any environments. You may want to select another configuration.

Diagnosis: The default configuration does not have an OE depot in it.

Correction: This does not affect the configuration you created. Select the cfg clause you created as described above.

[Jimmy Aulestia_2]

Thank for the ansver.

There is a file /etc/bootptab and the IP configuration is correct because the client is booting for the ignite server.

In the ignite server there is a recovery image of the client, the make_net_recovery wa sucessful from the GUI ignite-ux.

I don´t understad why there isn´t enviroment. I suppose that the instalation UI could search the recovery image file,

How the instalation UI find the image recovery?

[Jimmy Aulestia_2]

The recovery is OK, there was another ignite server that booted the client, when the client find the correct server the enviroment is "recovery archive" and the install is ok.

Thanks

[Jimmy Aulestia_2]

Thanks

[Tim Nelson]

FYI,

To avoid this or another dhcp server from getting in the way use dbprofiles. This feature is availble from the EFI shell prompt to configure direct booting to/from one specific Ignite server ( also allows booting across a router ).

You can then create a boot option as a menu option using this dbprofile.