Itanium ignite recovery error: NERROR: Could not open /tmp/env.vars: No such file or directory (er

[Bob_Vance]

3 rx1600 server's + 11.23.
1 server is Ignite server.

I had Ignite *network* backup and recovery working 6 months ago, with all 3 boxes running Ignite C.6.2.241.

The only change that I can remember since then is that I updated Ignite on the server to C.6.7.79 (but NOT on the other 2 "clients").

When I try an Ignite recovery, the network boot works fine and gets to the point where it asks for the USB keyboard type.
However, when I enter the "26" and expect to get the
.. " Welcome to Ignite-UX!",

I get, instead, the following errors:

NERROR: Could not open /tmp/env.vars: No such file or directory (errno = 2)
.
ERROR: Could not execute net_cfg_prep
NOTE: System rebooting...


Any ideas ?????????

tks
bv

((((((((((((
NOTE:
The MP firmware also had been updated via PHSS_33092 6 months ago and the Ignite was working thereafter. Here are the versions:

Shell> info -a fw
... Firmware Revision: 2.18 [4511]
..... PAL_A: 7.31/5.37
..... PAL_B: 5.69
..... EFI Spec: 1.10
..... EFI Intel Drop: 14.62
..... EFI Build: 2.14
..... SAL Spec: 3.01
..... SAL_A: 2.00
..... SAL_B: 2.15
..... POSSE: 0.10
..... ACPI: 7.00
..... SMBIOS: 2.3.2a:

... BMC Revision: 3.48
..... IPMI: 1.00
... Management Processor Revision: E.03.15
... Updatable EFI Drivers:
..... Floating-Point Software Assistance Handler: 00000118
..... LSI Logic Ultra320 SCSI Driver: 01040200
..... Broadcom Gigabit Ethernet Driver: 00070003.
)))))))))))))))

[Bob_Vance]

Update.


It is actually working on one of the clients.
So that rules out the Ignite version and.or firmware as an issue.

Sumpin' special on the one client.

Still need ideas :-[

bv

[Bob_Vance]

There was finally an update to the firmware on rx16xx servers.

I applied
... PHSS_33094 (which I had supposedly applied before and *not* to be confused with PHSS_33092 which I had also previously applied )
and
... PHSS_35841 (which supersedes previously-applied PHSS_33092)

THAT FIXED IT.

Don't know whether force-re-applying PHSS_33092
would have worked, or if just PHSS_33094 would have worked.


tks
bv