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.
The latest patch(es) : sfha-sles10_x86_64-5.0MP4 
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2009-10-26
OS update support: None
Technote: 337212
Documentation: None
Popularity: 356 viewed    7 downloaded
Download size: 2.81 MB
Checksum: 210921678

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

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

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

This patch supersedes the following patches: Release date
vcs-sles10_x86_64-VRTSvxfen-5.0MP3RP2HF1 (obsolete) 2009-08-21

 Fixes the following incidents:
1779129, 1822731

 Patch ID:

 Readme file  [Save As...]
OS: Linux
OS Version: SLES10 (x86_64)
Fixes Applied for Products:
	VRTSvxfen - Veritas I/O Fencing by Symantec

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

 PATCH VxFEN 5.0 MP3 RP2 HF2 for VxFEN 5.0 MP3 RP2 (Linux)

 Patch Date:  October, 2009

This README provides information on:

This patch only applies to:
	VxFEN 5.0 MP3 RP2 running on Linux (SLES10 x86_64)

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

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 VRTSvxfen-
1812355855	2956465	VRTSvxfen-

Etrack Incidents: 1779129, 1822731

SDR's of Fixed Symantec Incidents:
Symantec Incident : 1822731
	vxfenswap(1m) utility logs the following message in the utility's 
	log file even though I/O fencing is configured:
	"I/O fencing does not appear to be configured on node."
Defect Description:
	vxfenswap(1m) utility is not invoking command on remote host with 
	proper syntax. Because of this, it could not collect correct 
	status of I/O fencing module, whether it is running or not.
	The code has been added to invoke command with 
	appropriate syntax/argument.

Symantec Incident : 1779129
	The command "/etc/init.d/vxfen stop" fails with the error in console:
	"ERROR: failed to stop vxfen" 
	and the following error appears in /var/VRTSvcs/log/vxfen/vxfen.log:
	"VXFEN vxfenconfig ERROR V-11-2-1071 Ioctl VXFEN_IOC_CLUSTSTAT failed!"
Defect Description:
	VxFEN was using a variable without proper memory allocation. 
	The problem occurred when, the variable failed to store a 
	large amount of data, due to its size limitation. Hence, 
	recovering information correctly from the variable was 
	not possible and the error messages are seen.
	The variable now have proper memory allocation.

This patch updates the following VCS package(s) 
	VxFEN from 5.0MP3RP2 ( or higher 
		to 5.0MP3RP2HF2 ( for SLES10 (x86_64)

The following steps should be run on all nodes in the VCS cluster:

Stopping VCS on the cluster node:
1. Verify that /opt/VRTSvcs/bin is set in the PATH variable 
   so you can execute all VCS commands.

2. Ensure that none of the service groups are online on this system.
2a. For each failover group online on this sytem, switch over 
    the service group to a node that is running:
        # hagrp -switch [service_group] -to [node]
2b. Offline every parallel group online on this system:
	# hagrp -offline [service_group] -sys [this_node]

3. Make the VCS configuration writable. On a node that you want 
   to upgrade, type:
        # haconf -makerw

4. Freeze the service group operations. Perform this task on each node 
   if you had selected a group of nodes to upgrade:
        # hasys -freeze -persistent [node]

5. Make the VCS configuration read-only:
        # haconf -dump -makero

6. Stop VCS, using the following command, in each node in 
   the group that is being upgraded:
        # hastop -local

7. Stop the VCS command server:
       # killall CmdServer

8. Stop VxFEN module using the following command:
	# /etc/init.d/vxfen stop

9. If the above command fails to stop VxFen module with symptoms
   documented in the "Symptom" section, then follow the steps mentioned
   below for the same:
   To remove vxfen script from all the run-levels for next boot, 
   run the following command as appropriate on all nodes:
	For RHEL:
		# chkconfig --del vxfen
	For SUSE:
		# insserv -r vxfen
   Reboot the node, which will stop vxfen from running in any run-level.
   Note that a forced reboot may be necessary. Also, if VCS was
   configured to make use of fencing (Cluster Attribute "UseFence" set to
   "SCSI3"), the "had" process will not come up immediately after the
   reboot. This is expected.

Installing the Patch:
1. Un-compress the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VxFEN 5.0MP3RP2HF2 patch using the following command:
	# rpm -Uvh VRTSvxfen-

2. Verify that the new patch has been installed:
	# rpm -qa | grep VRTSvxfen
   You will find the following output on display with the patch 
   installed properly:

Re-starting VCS on the cluster node:
1. Re-start VxFEN on the node using the command :
	# /etc/init.d/vxfen start

2. If VCS was configured to make use of fencing, a re-start of VCS is
   required :
	# /etc/init.d/vcs start

3. Make the VCS configuration writable. Run the following command 
   from any node in the upgraded group.
	# haconf -makerw

4. Unfreeze the service group operations. Perform this task on 
   each node if you had upgraded a group of nodes.
	# hasys -unfreeze -persistent [node]

5. Make the configuration read-only.
	# haconf -dump -makero

6. Start the parallel service groups that were stopped as part of step 2a.
	# hagrp -online [service_group] -sys [this_node]

7. Switch back the service group to the original node.
	# hagrp -switch [service_group] -to [node]

For each cluster node, repeat all the steps above, starting with Step 1
of subsection "Stopping VCS on the cluster node".

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 to 8, provided under "Stopping VCS on the 
   cluster node" section above, to stop VCS on the node & 
   unload any drivers, as required.

2. Remove the package by the following command:
	# rpm -e VRTSvxfen

3. Verify that the patch has been removed from the system:
	# rpm -qa | grep VRTSvxfen
   There will be no result displayed at the console.

4. Install VRTSvxfen package from VCS 5.0MP3 Installer CD 
   and upgrade to VxFEN 5.0MP3RP2 or higher.

5. Restart the node following the steps under 
   "Re-starting VCS on the cluster node" section above.

Read and accept Terms of Service