Volume Manager 5.0.1.0 (5.0 Maintainance Patch 1 )
==================================

Patch Information:
==================

Release level: VxVM 5.0.1.0
Description: VERITAS Volume Manager (VxVM) 5.0MP1


Snapshot Info:
==============

vm:     cvs co -P -r ga5_0_maint -D "2006-12-12 16:43:00" unixvm-cvs
vras:   cvs co -d vras_aix -r ga5_0_maint  -D "2006-12-12 16:43:00" vras-cvs

siglic: siglic/3
ted:    ted/3

Pre-requisites:
===============

1. VxVM release level 5.0.0.0 (minimum)
2. AIX release level 5.1.0.61 (minimum) - ***** To confirm



Installation Procedure:
=======================

1. Since the patch process will configure the new kernel extensions, it
   has to be ensured that no VxVM volumes are in use/open/mounted before
   starting the installation procedure. Applications using VxVM volumes
   have to be stopped (unmount any mounted filesystems on VxVM volumes
   etc). If any VxVM volumes are in use, the installation process will
   be aborted.

2. Use the installp or Smit to install the patch image.

   Using installp:

   1. To apply this patch, use following command.

        installp -ag -d ./VRTSvxvm.bff VRTSvxvm

   2. To apply and commit this patch, use following command

        installp -acg -d ./VRTSvxvm.bff VRTSvxvm


   NOTE: Please refer installp(1M) man page for clear understanding
   on APPLY & COMMIT state of the package/patch.


   Using Smit:

        Software Installation and Maintenance ->
        Install and Update Software ->
        Update Installed Software to Latest Level


3. Reboot the system after the installation is complete.


Deinstallation Procedure:
=========================

If patch installation is in "APPLY" state, patch image can be rejected
or deinstalled. For rejecting the patch image, please use following
command

     installp -r -V 5.0.1.0 VRTSvxvm

This command will reject/deinstall the VRTSvxvm 5.0.1.0 (MP1) patch
Patch contents cannot be rejected/deinstalled if it is in COMMITed state.
Note that rejecting the patch will stop the vxconfigd(1M) (VxVM configuration
Daemon). Please start vxconfigd manually or reboot the system.

VRAS Incident
Etract Num : Abstract
-------- -------- ------------------------------------------------------------
613938 VRAS:secondary is not in a proper state after rolling back from delsec
645085 VRAS: PROV: GUI: Current Logging shows SRL when it should be DCM
641444 When sec is up-to-date, updates_behind_in_time should be set to
    0 instead of -1
641439 VRAS: vradmind can crash due to an attach on VVR  service post, TCP/8199
645023 VRAS and vrpro reports incorrect size for the SRL and vols in
    4.x to 5.0 rep on hp-ux
614504 VRAS:syncrvg should display more error messages on console, syslog,
    terminal
595718 VRAS: fixing new coverity errors
591515 VRAS:Need to fix " freeing mismatched memory" error
776721 CVR:VRAS:migrate is not allowed after one node of primary cluster panics
784952 VRAS: replicating from bunker to secondary generated startrep
    notification continously
784042 VRAS: After shuting down the primary, bring it back up, and
    deport/import the DGs, the bus is messed up.