The Update Process: Step by Step
The following steps should be
done from the console:
1. Make sure that all the
virtual partitions are up. You can check this with vparstatus.
Example:
vpar1# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State
Attributes Kernel Path Opts
===================== =====
============ ======================= =====
vPar1 Up Dyn,Auto,Asr /stand/vmunix
vPar2_ Up Dyn,Auto,Nsr /stand/vmunix
vpar3 Up Dyn,Auto,Asr /stand/vmunix
vPar4 Up Dyn,Auto,Asr /stand/vmunix
2. Record the current
autoboot and autosearch settings of all the virtual partitions. The update
process sets autoboot to manual, so you will need to restore these settings
later. To find the current settings, use vparstatus.
Virtual Partition Name State
Attributes Kernel Path Opts
===================== =====
============ ======================= =====
vPar1 Up Dyn,Auto,Asr /stand/vmunix
vPar2_ Up Dyn,Auto,Nsr /stand/vmunix
vpar3 Up Dyn,Auto,Asr /stand/vmunix
vPar4 Up Dyn,Auto,Asr /stand/vmunix
NOTE :
In a mixed HP-UX 11i v2/v3
vPars environment, the vPars running A.04.xx must be running version A.04.02 or
later. Therefore, the “Revision” field in the depot should be A.04.02 or
greater.
In our Scenario, all the vPars
are running on A.04.05.07. That’s why we are updating only one virtual
partition(vpar4).
Rebuilding the kernel
The update can fail if the
HP-UX kernel build fails in the starting environment. To ensure that
you have a reliable starting
point, rebuild the kernel before you update:
1. As root, enter:
/usr/sbin/mk_kernel –o
/stand/vmunix
2. Fix any problems listed in the mk_kernel output.
3. Reboot your system to ensure that your new kernel
boots.
Protect One Disk for all vPars
#pvchange
–a N
Stop
the LVM to access secondary disk and remove it.
For
example (output):
# pvchange -a N /dev/dsk/c14t0d0s2
Warning:
Detaching a physical volume reduces the availability of data
within
the logical volumes residing on that disk.
Prior
to detaching a physical volume or the last available path to it,
verify
that there are alternate copies of the data
available
on other disks in the volume group.
If
necessary, use pvchange(1M) to reverse this operation.
Physical
volume "/dev/dsk/c14t0d0s2" has been successfully changed.
Check
vg status--- (disk should show unavailable)
#vgdisplay
–v
---
Physical volumes ---
PV
Name /dev/dsk/c6t0d0s2
PV
Status available
Total
PE 4346
Free
PE 1901
Autoswitch
On
Proactive
Polling On
PV
Name /dev/dsk/c14t0d0s2
PV Status unavailable à Search for this information in output.
Total
PE 4346
Free
PE 1901
Autoswitch
On
Proactive
Polling On
è Then boot the server with primary disk .
Renaming your log files in vpar4
You should also rename your log
files to make it easier to find problems encountered during an
update.
1. Enter:
cd /var/adm/sw
2. As root, rename each log file. For example:
mv swagent.log
swagent_old.log
3. cd /var/opt/swm
4. mv swm.log swm_old.log
3. Install the latest Update-UX bundle onto each virtual partition (use
Ctrl-A to switch between consoles).
Note that this does not update the operating system, only
the Update-UX bundle.
From the DVD media
To install the Update-UX
product from the Operating Environment DVDs:
1. Mount the DVD :
à Insert the DVD into the DVD drive.
à Find the DVD-ROM device file name:
#ioscan -C disk -f -n -k |
more
A typical device name is
/dev/dsk/c1t2d0
à Create a directory under root (/). For
example:
#mkdir /dvdrom
à Mount the DVD onto the new directory as a file
system. For example:
#mount /dev/dsk/c1t2d0
/dvdrom
2. Using swinstall, install the
latest version of the Update-UX product on the target system:
#swinstall -s /dvdrom
Update-UX
NOTE: Make sure you use the correct case to install the
Update-UX product (in title case).
This product contains the
update-ux command (lowercase).
4. Determine if you need to
change the PRI boot path and perform accordingly:
If the current nPartition’s PRI
boot path currently points to a virtual partition that will be updated to only
A.04.xx and not A.05.01, you will need to change the nPartition’s PRI boot path
such that it points to the boot disk of a virtual partition that will be
updated to A.05.01
In our Scenario, the first virtual
partition vpar1 running
A.04.05 (on 11.23) . so we need to change the nPartition PRI boot path
and can proceed to the next step.
a. Find the nPartition partition number for the current nPartition:
#parstatus –w
The local partition number is 1
The nPartition number is 1.
Record this information.
b. Find the boot path of the
boot disk of a future vPars A.05.01 virtual partition. This boot path will
become the nPartition’s new PRI boot path.
Since vpa4 is being updated to A.05.01, let’s chose to
change the nPartition’s PRI path to the boot disk of vpa4 . Since we have
chosen vpa4 as the future A.05.01
virtual partition, we need to find the boot path of vpa4 :
# vparstatus -v -p vpar4
...
IO Details]
4.0.4.1.0
5.0.9.1.0
4.0.8.1.0
5.0.14.1.0
4.0.6.1.0
5.0.4.1.0
4.0.4.1.0.4.0.0.0.0.0.0.0 BOOT
5.0.4.1.0.4.0.0.0.0.0.0.0,
ALTBOOT
BOOT attribute identifies the
boot path for the virtual partition vpa4 (pproxy01) as
4.0.4.1.0.4.0.0.0.0.0.0.0
Record this information.
c. Set the mode for the next
nPartition reboot:
• on Integrity, set the mode to
nPars for the next reboot:
# vparenv -m nPars
The remainder of the steps to
change the PRI boot path will be done later, while in nPars/standalone mode.
5. For each virtual
partition, except the first virtual partition, use Update-UX to install the
latest OE and vPars bundle.
where
target OS will be 11.31, which implies vPars A.05.xx:
run this command on vPar4:
From dvdrom:
# update-ux –p -s /dvdrom HPUX11i-VSE-OE T1335DC
# update-ux -s /dvdrom HPUX11i-VSE-OE T1335DC
NOTE Be sure that both the OE and vPars bundles are
specified on the update-ux command line. When using Update-UX to update vPars,
you must update in this manner, in which case
you are updating both the
OS and vPars version with the same command line.
6. After the all updates for
the above virtual partitions have completed, use shutdown –hy0 command to halt
all the vpars.
Shutdown all the vpars in the
given npar using below command
#shutdown –hy 0
7. Reboot the nPartition.
On Integrity, if you need to
change the PRI boot path, reboot in nPars mode:
MON> reboot npars
8. If you need to change the
PRI boot path, follow the procedure below. Otherwise, proceed to the next step.
a. Interrupt the boot up
process and enter into standalone nPars (Integrity) mode:
For Integrity:
Shell> fs0:
fs0:\> ls
fs0:> cd EFI
fs0:\>cd hpux
fs0:\> hpux
HPUX> boot vmunix
b. Change the nPartition’s
PRI path to the boot path of the future A.05.01 partition recorded earlier.
# parmodify –p1 -b
4.0.4.1.0.4.0
where
the syntax of parmodify is
-p nPartition_number
-b primary_boot_path
c. Verify the new PRI path
using parstatus:
# parstatus -p0 -V
[Partition]
Partition Number : 1
Partition Name : npar1
Status : active
IP address : 0.0.0.0
PrimaryBoot Path :
4/0/4/1/0/4.0
d. Once the PRI path has been successfully changed, set the mode to back
to vPars:
# vparenv -m vPars
e. Reboot the nPartition:
# shutdown -ry 0
9. If needed (depending upon
how your nPartition’s autoboot configuration is set up), interrupt the
nPartition boot process and load the vPars Monitor.
Shell>map -r
Shell> fs0: select the
correct file system .
fs0:\> ls
fs0:> cd EFI
fs0:\>cd hpux
fs0:\> hpux
HPUX> boot vpmon
10. Boot the virtual
partitions. First we boot the updated vPar the we boot the other vPars one by
one .
MON> vparload –p
When the virtual partitions are
booted, they will continue and complete their update processes (the virtual
partitions can be booed in any order). After this is completed, you should
arrive at the login: prompt for each virtual partition. Login as root and
continue to the next step.
11. Turn autoboot and autosearch settings back to their original
settings that you recorded earlier above.
Vpar4 # vparmodify -p vpar4 -B
auto
12. Verification of Virtual
Partitions
The virtual partitions should
now be running the latest vPars version. To verify this, you can login to each
virtual partition and use the vparstatus command with the -P option.
#vparstatus -P
13. Verification of Correct
vPars Monitor
If you changed the nPartition’s
PRI boot path, you can also verify that the vPars monitor has been booted from
the correct boot disk:
# vparstatus -m
Console path: No path as
console is virtual
Monitor boot disk path:
0.0.6.0.0.5.0
Monitor boot filename:
/stand/vpmon
Database filename: /stand/vpdb
Then
insert the secondary disk .
#
pvchange -a y /dev/dsk/cXtXdXs2
For
example (output):
#
pvchange -a y /dev/dsk/c14t0d0s2
Physical volume
"/dev/dsk/c14t0d0s2" has been successfully changed.
Sync
primary and secondary disk
# vgsync vg00
Set
the boot path :
# setboot –p -b on
No comments:
Post a Comment