vcs-rhel5_x86_64-VRTSamf-6.0.3.300
Obsolete
The latest patch(es) : sfha-rhel5_x86_64-6.0.5 

 Basic information
Release type: Patch
Release date: 2013-10-17
OS update support: None
Technote: None
Documentation: None
Popularity: 893 viewed    100 downloaded
Download size: 1.42 MB
Checksum: 1151678614

 Applies to one or more of the following products:
VirtualStore 6.0.1 On RHEL5 x86-64
Cluster Server 6.0.1 On RHEL5 x86-64
Storage Foundation Cluster File System 6.0.1 On RHEL5 x86-64
Storage Foundation for Oracle RAC 6.0.1 On RHEL5 x86-64
Storage Foundation HA 6.0.1 On RHEL5 x86-64

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

This patch is obsolete. It is superseded by: Release date
sfha-rhel5_x86_64-6.0.5 2014-04-15

This patch supersedes the following patches: Release date
vcs-rhel5_x86_64-VRTSamf-6.0.3.200 (obsolete) 2013-07-16
vcs-rhel5_x86_64-VRTSamf_6.0.3.100 (obsolete) 2013-03-28

This patch requires: Release date
sfha-rhel5_x86_64-6.0.3 (obsolete) 2013-02-01

 Fixes the following incidents:
3090243, 3097346, 3230303, 3267240, 3331998

 Patch ID:
VRTSamf-6.0.300.300-GA_RHEL5

Readme file
                          * * * READ ME * * *
                * * * Veritas Cluster Server 6.0.3 * * *
                      * * * Public Hot Fix 3 * * *
                         Patch Date: 2013-10-17


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Cluster Server 6.0.3 Public Hot Fix 3


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL5 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSamf


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation Cluster File System 6.0.1
   * Veritas Storage Foundation High Availability 6.0.1
   * Symantec VirtualStore 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.0.300.300
* 3267240 (3259682) If vxconfigd hangs, then registration thread of imfd trying 
to get diskgroup status from vxconfigd also hangs. Therefore, the amfregister 
command waiting for IMFD gets stuck.
* 3331998 (3341320) Syslog gets flooded with "Cannot delete event (rid %d) in
reaper" error messages.
Patch ID: 6.0.300.200
* 3230303 (3248251) AMF driver panics the machine while monitoring online processes.
Patch ID: 6.0.300.100
* 3090243 (3090229) AMF driver panics the node when vxconfigd is unresponsive.
* 3097346 (3097342) AMF driver panics the node when AMF is being stopped.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: 6.0.300.300

* 3267240 (Tracking ID: 3259682)

SYMPTOM:
Imf registrations for disk group resources fail.

DESCRIPTION:
If vxconfigd is unresponsive, then IMFD becomes unresponsive and
imf registrations fail for disk group resources. Subsequent attempts to
unconfigure AMF will also fail.

RESOLUTION:
The IMFD code is modified to fix this hang.

* 3331998 (Tracking ID: 3341320)

SYMPTOM:
Syslog gets flooded with "Cannot delete event (rid %d) in reaper" error
messages.

DESCRIPTION:
This was a harmless error message which appeared in syslog.

RESOLUTION:
AMF code is modified so that the error message does not appear in
the syslog.

Patch ID: 6.0.300.200

* 3230303 (Tracking ID: 3248251)

SYMPTOM:
AMF driver panics the machine while monitoring online processes.

DESCRIPTION:
For certain Linux kernel versions, when AMF is monitoring an online
process, AMF panics the machine while accessing kernel memory. The panic string
looks something like "BUG: unable to handle kernel paging request".

RESOLUTION:
Symantec has fixed this issue by modifying the AMF code that
accesses kernel memory.

Patch ID: 6.0.300.100

* 3090243 (Tracking ID: 3090229)

SYMPTOM:
AMF driver panics the node when vxconfigd is unresponsive.

DESCRIPTION:
The libusnp_vxnotify.so library used for disk group notifications,
goes into an infinite loop when vxconfigd daemon is unresponsive. This causes
AMF to enter an inconsistent state as a result of which AMF driver panics the node.

RESOLUTION:
Symantec has modified the AMF driver and libusnp_vxnotify.so
library, to address this issue.

* 3097346 (Tracking ID: 3097342)

SYMPTOM:
AMF driver panics the node when AMF is being stopped.

DESCRIPTION:
When AMF driver is being stopped, it stops the IMFD daemon. The
code to handle this sleeps while holding a lock. This causes AMF driver to panic
the node.

RESOLUTION:
Symantec has modified the AMF driver to fix this issue.



INSTALLING THE PATCH
--------------------
1) Unconfigure AMF
#/opt/VRTSamf/bin/amfconfig -Uof

This will disable IMF functionality for all agents.

2) Stop AMF
#/etc/init.d/amf stop

3) Uninstall the older version of AMF
#rpm -e VRTSamf

4) Install AMF Patch using the following command
#rpm -Uvh VRTSamf-6.0.300.300-GA_RHEL5.x86_64.rpm


REMOVING THE PATCH
------------------
1) Unconfigure AMF
#/opt/VRTSamf/bin/amfconfig -Uof

This will disable IMF functionality for all agents.

2) Stop AMF
#/etc/init.d/amf stop

3) Uninstall AMF
#rpm -e VRTSamf


SPECIAL INSTRUCTIONS
--------------------
It is recommended to install VRTSvcsag 6.0.300.200 (or higher) package


OTHERS
------
NONE
Read and accept Terms of Service