This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
vcs-rhel4_x86_64-VRTSvcsag-5.0MP3RP2HF6
Obsolete
The latest patch(es) : sfha-rhel4_x86_64-5.0MP4 
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2009-10-27
OS update support: None
Technote: None
Documentation: None
Popularity: 573 viewed    10 downloaded
Download size: 451.46 KB
Checksum: 3786978642

 Applies to one or more of the following products:
Cluster Server 5.0MP3 On RHEL4 i686
Cluster Server 5.0MP3 On RHEL4 x86-64
Storage Foundation Cluster File System 5.0MP3 On RHEL4 i686
Storage Foundation Cluster File System 5.0MP3 On RHEL4 x86-64
Storage Foundation Cluster File System for Oracle RAC 5.0MP3 On RHEL4 i686
Storage Foundation Cluster File System for Oracle RAC 5.0MP3 On RHEL4 x86-64
Storage Foundation for DB2 5.0MP3 On RHEL4 i686
Storage Foundation for DB2 5.0MP3 On RHEL4 x86-64
Storage Foundation for Oracle 5.0MP3 On RHEL4 i686
Storage Foundation for Oracle 5.0MP3 On RHEL4 x86-64
Storage Foundation for Oracle RAC 5.0MP3 On RHEL4 i686
Storage Foundation for Oracle RAC 5.0MP3 On RHEL4 x86-64
Storage Foundation HA 5.0MP3 On RHEL4 i686
Storage Foundation HA 5.0MP3 On RHEL4 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch is obsolete. It is superseded by: Release date
sfha-rhel4_x86_64-5.0MP4 2010-04-11

This patch supersedes the following patches: Release date
vcs-rhel4_x86_64-VRTSvcsag-5.0MP3RP2HF4 (obsolete) 2009-07-03
vcs-rhel4_x86_64-VRTSvcsag-5.0MP3RP2HF2 (obsolete) 2009-05-29
vcs-rhel4_i686-VRTSvcsag-5.0MP3RP2HF2 (obsolete) 2009-05-29
vcs-rhel4_x86_64-VRTSvcsag-5.0MP3RP2HF1 (obsolete) 2009-04-20
vcs-rhel4_i686-VRTSvcsag-5.0MP3RP2HF1 (obsolete) 2009-04-20
vcs-rhel4_x86_64-5.0MP3HF2 (obsolete) 2008-11-19

 Fixes the following incidents:
1557126, 1638428, 1665814, 1676451, 1723347, 1730192, 1789008, 1852510

 Patch ID:
VRTSvcsag-5.0.30.26-MP3RP2HF6_RHEL4

 Readme file  [Save As...]
OS: Linux
OS Version: RHEL4 (i686/x86_64)
Fixes Applied for Products:
	VRTSvcsag - Veritas Cluster Server Bundled Agents by Symantec

Additional Instructions:
Please read the instructions below before installing the patch.

 PATCH VRTSvcsag 5.0MP3RP2HF6 for VCS Bundled Agent 5.0MP3RP2
===============================================================

 Patch Date:  October, 2009

This README provides information on:
 * BEFORE GETTING STARTED
 * CRC AND BYTE COUNT
 * FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH
 * PACKAGES AFFECTED BY THE PATCH
 * INSTALLING THE PATCH
 * UNINSTALLING THE PATCH


BEFORE GETTING STARTED:
----------------------
This patch only applies to:
	VRTSvcsag 5.0MP3RP2 running on RHEL4 (i686/x86_64)

Ensure that you are running the supported configurations before
installing this patch.


CRC AND BYTE COUNT:
------------------
Ensure that the patch file you have downloaded matches the following
checksum and byte count.

The following command can be used to ascertain this:
# cksum VRTSvcsag-5.0.30.26-MP3RP2HF6_RHEL4.i686.rpm
1141389890      478260  VRTSvcsag-5.0.30.26-MP3RP2HF6_RHEL4.i686.rpm


FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: 
--------------------------------------------
Etrack Incidents: 1852510, 1789008, 1730192, 1723347, 1557126, 1638428, 1665814, 1676451

SDR's of Fixed Symantec Incidents:
--------------------------------
Symantec Incident : 1852510
Symptom:
	DiskGroupSnap resource failed to come online.
Defect Description:
	The agent currently assumes that all nodes in the cluster would
be involved in the campus cluster configuration.
Resolution:
	Removed the assumption that all nodes in the cluster participate in the campus cluster setup as well.

Previous Patch Fixes:
Symantec Incident : 1789008
Symptom:
        Presence of file /var/lib/nfs/etab, upon panic reboot causes 
        incorrect operation of Share agent.
Defect Description:
        When the system panics, the /var/lib/nfs/etab file is not cleared 
        at boot-time. This results in VCS incorrectly seeing share resources 
        as online. The Share agent service group cannot be failed over to 
        the other node as the service group goes into partial state. 
        The NFS client receives an "Stale NFS File Handle" error.
Resolution:
        A new mandatory attribute is added to Share agent type definition 
        named 'NFSRes'. This attribute is the NFS Resource configured on 
        the system. This ensures that the /var/lib/nfs/etab file is 
        cleared during the First Probe of Share resource, 
        if NFS resource is not yet up.

        Description of NFSRes attribute:
                NFSRes, the NFS resource be configured on the system. 
                This attribute is required to determine the current 
                state of the NFS Resource.
        Type and dimension: string-scalar
        Sample Configuration:
                NFS nfs (
                        Address = "[ip-address]"
                        )
                Share share (
                        NFSRes = nfs
                        PathName = "/nfs_mnt"
                        Options = "rw"
                        )

Symantec Incident: 1730192
Symptom:
        DNS clean never used to succeed.
Defect Description:
        The DNS clean entry point was not parsing the argument 
        list correctly. Hence, it always reported the clean operation 
        as failed. VCS kept on re-attempting clean operation and 
        this sequence never used to end.
Resolution:
        Fixed the clean entry point code to parse the argument 
        list correctly. Now the DNS resource's clean operation 
        should succeed, if there is no fault.

Symantec Incident: 1723347
Symptom:
        Mount agent returns offline even when the resource is mounted.
Defect Description:
        Mount agent did not support large file systems. Thus statvfs(3P)
        call within large file systems used to fail. Due to this, 
        the monitor entry point used to return offline status.
Resolution:
        Fixed the Mount agent to support large file systems 
        and return correct status.

Symantec Incident: 1557126
        The VCS Application agent was not able to recognize a 
        running process containing special characters like round brackets.
Symantec Incident: 1638428
        Mount agent doesn't support NFS version 4 in Linux, even though NFS
        agent supports it.
Symantec Incident: 1665814
        The offline entry point of NFSRestart does not stop NFS daemons.
Symantec Incident: 1676451
        NFS clients were getting "permission denied" errors 
        after NFS service group failover.


PACKAGES AFFECTED BY THE PATCH:
-------------------------------
This patch updates the following VCS package(s) 
	VRTSvcsag from 5.0MP3RP2 or higher to 5.0MP3RP2HF6


INSTALLING THE PATCH:
--------------------
The following steps should be run on all nodes in the VCS cluster:

Stopping VCS on the cluster node:
--------------------------------
1. Ensure that "/opt/VRTS/bin" directory is included in your PATH
   environment variable so you can execute all the VCS commands. Refer
   to Veritas Cluster Server Installation Guide for more information.

2. Verify that the version of VRTSvcs and VRTSvcsag is 5.0MP3RP2 
   or higher for Linux.

3. Freeze all the service groups persistently.
    # haconf -makerw
    # hagrp -freeze [group] -persistent
    # haconf -dump -makero

4. Stop the cluster on all nodes. If the cluster is writable, you may
   close the configuration before stopping the cluster.
    # haconf -dump -makero

   From any node, execute the following command.
    # hastop -all
    or
    # hastop -all -force

   Verify that the cluster is stopped on all nodes 
   by running the ha command.
    # hasys -state

   On all nodes, make sure that both had and hashadow processes are
   stopped.
   Also, stop the VCS CmdServer on all nodes.
    # CmdServer -stop

5. Move /etc/VRTSvcs/conf/config/types.cf file to 
   /etc/VRTSvcs/conf/config/types.cf.orig.

Installing the Patch:
--------------------
1. Un-compress the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VRTSvcsag 5.0MP3RP2HF6 patch using the following command:
	# rpm -Uvh VRTSvcsag-5.0.30.26-MP3RP2HF6_RHEL4.i686.rpm

2. Verify that the new patch has been installed:
	# rpm -q VRTSvcsag
   You will find the following output on display with the patch installed properly:
	VRTSvcsag-5.0.30.26-MP3RP2HF6_RHEL4

Re-starting VCS on the cluster node:
-----------------------------------
Manual configuration update steps:
1. Adding NFSRes attribute to all the systems:
   Add NFSRes attribute to every Share resource configuration in main.cf.
   Sample Configuration, that need to be added :
        NFS nfs (
                Address = "[ip-address]"
                )
        Share share (
                NFSRes = nfs
                PathName = "/nfs_mnt"
                Options = "rw"
                )

   Verify consistency of main.cf file after updation:
      # hacf -verify /etc/VRTSvcs/conf/config/

Note: Please make sure that the NFSRes attribute is added to every Share 
      resource that is configured on the system, after applying this patch.
      In case of attribute mismatch error for NFSRes attribute, 
      please verify the types.cf is upgraded properly.

2. At this time, you can start the cluster services on all cluster 
   nodes. First start VCS on one node:
    # hastart

   On all the other nodes, start VCS by issuing hastart after the 
   first node goes to LOCAL_BUILD or RUNNING state.

3. Unfreeze all the groups.
     # haconf -makerw
     # hagrp -unfreeze [group] -persistent
     # haconf -dump -makero

OR Runtime configuration update steps:
1. At this time, you can start the cluster services on all cluster 
   nodes. First start VCS on one node:
    # hastart

   On all the other nodes, start VCS by issuing hastart after the 
   first node goes to LOCAL_BUILD or RUNNING state.

2. Make VCS cluster Writable:
     # haconf -makerw

3. To modify the configuration at run-time, instead of modifying 
   main.cf manually please execute the following commands:
NOTE: Please make sure that the Service groups are freezed.

      # for res in `hatype -resources Share`; do 
            hares -modify $res NFSRes [NFS_Resource_Name]
        done

Note: Please make sure that the NFSRes attribute is added to every Share 
      resource that is configured on the system, after applying this patch.
      In case of attribute mismatch error for NFSRes attribute, 
      please verify the types.cf is upgraded properly.

4. Unfreeze all the groups.
     # hagrp -unfreeze [group] -persistent
     # haconf -dump -makero


UNINSTALLING THE PATCH:
-----------------------
Removal of the patch will result in removing whole package 
from the system/node. To go back to a previous installed version 
of the package, you may need to re-install the package again.
Following steps need to be run on all the VCS cluster node:
Steps to remove the Patch from a cluster node:
---------------------------------------------
1. Follow the steps 1-4 provided under "Stopping VCS on the cluster node" 
   section above, to stop VCS on the node.

2. Remove the patch by the following command:
        # rpm -e VRTSvcsag

3. Verify that the patch has been removed from the system:
        # rpm -qa | grep VRTSvcsag 
   The package VRTSvcsag should not be displayed, which confirms 
   that the package is removed.

4. Install VRTSvcsag package from VCS 5.0MP3 Installer CD/DVD 
   and upgrade to VCS 5.0MP3RP2.

5. At this time, you can start the cluster services on all cluster 
   nodes. First start VCS on one node:
    # hastart

   On all the other nodes, start VCS by issuing hastart after the 
   first node goes to LOCAL_BUILD or RUNNING state.

6. Unfreeze all the groups.
     # haconf -makerw
     # hagrp -unfreeze [group] -persistent
     # haconf -dump -makero



Read and accept Terms of Service