HP BA322 90087 - Manual (Page 209)

info cpu command or the EFI cpuconfig command to display current settings, such as the
setting of the Hyper-Threading feature.
You might need to restore boot options, such as if they get lost during a firmware upgrade. You
can save and restore your EFI boot path settings on Integrity servers by using the OpenVMS
Integrity servers Boot Manager (SYS$MANAGER:BOOT_OPTIONS.COM) utility. You can also
use the EFI variable -s command to save boot option variables and the variable -r
command to restore them. After using the variable command to restore boot options, a reset
might be required. Use the EFI Shell reset command.
You can use the OpenVMS-specific EFI utility vms_bcfg (\efi\vms\vms_bcfg) to set boot
options, and the vms_show utility (\efi\vms\vms_show) to display them; however, these utilities
are more limited in scope than the OpenVMS Integrity servers Boot Manager utility. For example,
they cannot work with Fibre Channel boot paths as can the OpenVMS Integrity servers Boot
Manager utility. You can use the EFI variable command to restore the boot options list from
a previously saved file.
You could also use the EFI Shell variable command to restore variables such as boot path
options; you must have first saved them in a known location by using the variable -save
command. For more information, see the service manual provided for your Integrity servers.
B.5.3 Writing a New Boot Block
The boot block structures on the system disk contain the size and location of the boot partition
and other details relevant to the bootstrap of OpenVMS Integrity servers. The size and location
of the boot partition stored within the boot block structures must be maintained and must
reference the current location of the OpenVMS file SYS$EFI.SYS.
Current versions of BACKUP maintain the boot block structures as well as the size and location
of the boot partition during image operations (analogous to the similar BACKUP/IMAGE
operations that maintain the boot block on OpenVMS Alpha disks). Older versions of BACKUP
do not maintain these structures and do not correctly locate core OpenVMS Integrity servers
bootstrap files.
If the boot partition file SYS$EFI.SYS is manually replaced or relocated, you must use the DCL
command SET BOOTBLOCK or the SYS$SETBOOT image to rewrite the boot block structures.
The SET BOOTBLOCK command and SYS$SETBOOT are analogous to the OpenVMS Alpha
Writeboot utility; they provide OpenVMS Integrity servers with the equivalent of what the
Writeboot utility provides on OpenVMS Alpha.
NOTE: Do not use the OpenVMS Alpha Writeboot utility to rewrite boot block structures on
an OpenVMS Integrity servers system disk.
The SET BOOTBLOCK command enables you to establish the boot block pointers necessary for
the EFI console to find and bootstrap an OpenVMS Integrity servers system disk. You must use
this command if the target OpenVMS Integrity servers system disk was originally created by
one of the following methods:
•
A version of BACKUP that does not support the OpenVMS Integrity servers system disk
structure. HP recommends that you do not use these versions of BACKUP for archiving or
restoring an OpenVMS Integrity servers system disk.
• A nonimage backup of an OpenVMS Integrity servers system disk (possibly corrupting the
boot block and various directory backlinks that must be manually reset). HP recommends
that you do not use nonimage backups.
• A nonimage restore of an OpenVMS Integrity servers system disk from an image save set.
HP recommends that you do not use a nonimage restoration.
B.5 Configuring and Managing OpenVMS Booting on Integrity servers 209