If it is required to change the boot path of the NPAR so that the latest VPMON boots up we need to follow the following steps as described below.
If it is required to change the boot path of the NPAR so that the latest VPMON boots up we need to follow the following steps as described below.
Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs
The commands vparmodify with specifying –m io:
<HWPATH_Boot_dev>:BOOT and -m io:<HWPATH_Boot_dev>:ALTBOOT
do change the setting as the setboot also does for the VPAR only but it does not effect the boot path setting in the Stable System Storage.
To make changes in the stable system storage we have to do the same by booting the system in NPARs mode and then using the parmodify –b <path_of_boot_disk> or using the setboot command in the NPAR mode followed by reboot in the VAPRS mode.
1) We have to make a note of the present bootpath and the NPAR Details.
#parstatus –w -- this shows the local NPAR no. say that it is 2.
#parstatus –V –p 2 -- note the Primary and the alternate bootpath.
2) On the present NPAR find the First VPAR and check the boot settings in the same and compare with that of the NPAR boot settings. Say the first VPAR is vpar1.
#vparstatus –v –p vpar1 --- this shows the current boot setting this is the same as that of the NPAR.
3) Go to the VPAR that will have the latest VPAR Bundle and the monitor following the update process. Say that this is vpar2
vpar2#parstatus –v –p vpar
In the IO Section of the output look for the entries with the BOOT and the ALTBOOT strings.
Note the boot path and the alternate boot path here. Say that the first boot path is 0/0/0/6/1/0.6.0:BOOT and 0/0/0/6/1/0.6.0:ALTBOOT is the alternate boot path.
4) After the update-ux has run on vpar2 and vpar3 and they have come to the shutdown state, we run the update-ux on vpar1 that is our first VPAR. When vpar1 also comes to a state of shutdown, it is the time that we should reboot the NPAR so that the primary boot path can be changed and also that the latest VPMON boots from the same.
MON> reboot -m npars
PARISC:When the Autoboot is interrupted and the system comes to the ISL,
ISL> boot /stand/vmunix
INTEGRITY: In the EFI Shell
Shell> fs0:
Fso:>boot /stand/vmunix
5) when the system has booted in the NPAR mode,
#parmodify –p 0 –b <new_pry_boot_path> -s <new_HAA_Alternate> -t
<new_secondary_boot_path>
#setboot –b on
#setboot
Enable to boot in the VPAR mode:
#vparenv –m vPars
#shutdown –ry 00
6) boot the new monitor from the newly set boot path
On the PA-RISC platform:
ISL> hpux /stand/vpmon
MON>vparload –all
On the INTEGRITY platform:
EFI Shell> exit
EFI Shell> fs0:
Fs0:>boot vpmon
MON>vparload –all
From the vpars booted condition check for the VPMON version and the bootpath as set to boot the VPMON.
This can be done using the following commands.
vpar1#vparstatus –m
vpar1#vparstatus –V
If it is required to change the boot path of the NPAR so that the latest VPMON boots up we need to follow the following steps as described below.
Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs
The commands vparmodify with specifying –m io:
<HWPATH_Boot_dev>:BOOT and -m io:<HWPATH_Boot_dev>:ALTBOOT
do change the setting as the setboot also does for the VPAR only but it does not effect the boot path setting in the Stable System Storage.
To make changes in the stable system storage we have to do the same by booting the system in NPARs mode and then using the parmodify –b <path_of_boot_disk> or using the setboot command in the NPAR mode followed by reboot in the VAPRS mode.
1) We have to make a note of the present bootpath and the NPAR Details.
#parstatus –w -- this shows the local NPAR no. say that it is 2.
#parstatus –V –p 2 -- note the Primary and the alternate bootpath.
2) On the present NPAR find the First VPAR and check the boot settings in the same and compare with that of the NPAR boot settings. Say the first VPAR is vpar1.
#vparstatus –v –p vpar1 --- this shows the current boot setting this is the same as that of the NPAR.
3) Go to the VPAR that will have the latest VPAR Bundle and the monitor following the update process. Say that this is vpar2
vpar2#parstatus –v –p vpar
In the IO Section of the output look for the entries with the BOOT and the ALTBOOT strings.
Note the boot path and the alternate boot path here. Say that the first boot path is 0/0/0/6/1/0.6.0:BOOT and 0/0/0/6/1/0.6.0:ALTBOOT is the alternate boot path.
4) After the update-ux has run on vpar2 and vpar3 and they have come to the shutdown state, we run the update-ux on vpar1 that is our first VPAR. When vpar1 also comes to a state of shutdown, it is the time that we should reboot the NPAR so that the primary boot path can be changed and also that the latest VPMON boots from the same.
MON> reboot -m npars
PARISC:When the Autoboot is interrupted and the system comes to the ISL,
ISL> boot /stand/vmunix
INTEGRITY: In the EFI Shell
Shell> fs0:
Fso:>boot /stand/vmunix
5) when the system has booted in the NPAR mode,
#parmodify –p 0 –b <new_pry_boot_path> -s <new_HAA_Alternate> -t
<new_secondary_boot_path>
#setboot –b on
#setboot
Enable to boot in the VPAR mode:
#vparenv –m vPars
#shutdown –ry 00
6) boot the new monitor from the newly set boot path
On the PA-RISC platform:
ISL> hpux /stand/vpmon
MON>vparload –all
On the INTEGRITY platform:
EFI Shell> exit
EFI Shell> fs0:
Fs0:>boot vpmon
MON>vparload –all
From the vpars booted condition check for the VPMON version and the bootpath as set to boot the VPMON.
This can be done using the following commands.
vpar1#vparstatus –m
vpar1#vparstatus –V
No comments:
Post a Comment