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-sol_sparc-VRTSvcsag-5.0MP3RP1HF1
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2010-02-10
OS update support: None
Technote: None
Documentation: None
Popularity: 669 viewed    62 downloaded
Download size: 204.18 KB
Checksum: 3026098204

 Applies to one or more of the following products:
Cluster Server 5.0MP3 On Solaris 10 SPARC
Storage Foundation Cluster File System 5.0MP3 On Solaris 10 SPARC
Storage Foundation for DB2 5.0MP3 On Solaris 10 SPARC
Storage Foundation for Oracle 5.0MP3 On Solaris 10 SPARC
Storage Foundation for Oracle RAC 5.0MP3 On Solaris 10 SPARC
Storage Foundation for Sybase 5.0MP3 On Solaris 10 SPARC
Storage Foundation HA 5.0MP3 On Solaris 10 SPARC

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

This patch requires: Release date
sfha-sol_sparc-5.0MP3RP1 (obsolete) 2008-12-17

 Fixes the following incidents:
1950516

 Patch ID:
143699-01

 Readme file  [Save As...]
Patch Date:  February, 2010

OS: Solaris
OS Version: Sparc 5.10
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.0MP3RP1HF1 for VCS Bundled Agents 5.0MP3RP1 or higher
=======================================================================

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


GETTING STARTED
---------------
This patch only applies to:
	VRTSvcsag 5.0MP3RP1 or higher running on Solaris Sparc 5.10.

Patch IDs for the appropriate SunOS Versions:
        For SunOS Sparc Release 5.10, 143699-01.

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

FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH 
--------------------------------------------
Etrack Incident: 1950516

SDR's of Fixed Symantec Incidents
---------------------------------
Symantec Incident: 1950516
Symptom:
   In a zone, if there are multiple IPMultiNICB resources on the same subnet, then there are issues with the source address of the IP packets.

Defect Description:
   In Solaris, ifconfig addif assigns the IP address to the next available logical interface. When packets are sent from the zone, if there are multiple interfaces for the same subnet, it selects the one that is the lowest number in the logical interface. The VIP revealed using ifconfig -a establishes VIP iterations with the interface such as: nxge0:1, nxge0:2, nxge0:3, nxge0:4...., nxge0:12  (so on).
The first VIP seen by the zone is designated as OPSA
(outgoing-packet-source-address). The problem occurs when the iteration train is broken. For example, when a service group is taken offline and its VIPs--let's say are nxge0:2, nxge0:3--then there is now a "gap" in the original train sequence. This gap apparently changes the OPSA for other service groups.

Resolution:
  After applying this patch, use the newly added attribute "Options" to set the deprecated flag for the IPMultiNICB resources.


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

INSTALLING THE PATCH
--------------------
The following steps should be run on all nodes in the VCS cluster:
1. Stop VCS on the cluster node.
2. Install the patch.
3. Restart VCS on the node.

Stopping VCS on the cluster node:
--------------------------------
To stop VCS on the cluster node:

1. Ensure that the "/opt/VRTS/bin" directory is included in your PATH
   environment variable so that you can execute all the VCS commands.     
   For more information, refer to the Veritas Cluster Server 
   Installation Guide.

2. Verify that the version of VRTSvcs is 5.0MP3RP1 or higher for 
   Solaris Sparc.

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. 

5. Log in as the super user into the system where the patch is to be 
   installed.

6. Run the preceding steps on all nodes in the VCS cluster.

Installing the Patch
--------------------
To install the patch:

1. Un-compress the downloaded patch from Symantec.
   Change the directory to the unzipped patch location. 
   Install the VRTSvcsag 5.0MP3RP1HF1 patch using the following 
   command:
    # patchadd [patch-id]
   where [patch-id] is either of the following depending on 
   system configuration,
	For SunOS Release 5.10, [patch-id] is 143699-01.

2. Verify that the new patch has been installed:
    # showrev -p | grep [patch-id]
   If the patch installs correctly, the following output displays:
   For Solaris Sparc 5.10:
	Patch: 143699-01 Obsoletes:  Requires: 139358-01 Incompatibles:  
	Packages: VRTSvcsag

3. Run the preceding steps on all nodes in the VCS cluster.

Re-starting VCS on the cluster node
-----------------------------------
To restart VCS on the cluster node:

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 the hastart command 
   after the first node goes to LOCAL_BUILD or RUNNING state.

2. Unfreeze all the groups:
    # haconf -makerw
    # hagrp -unfreeze <group> -persistent
    # haconf -dump -makero

3. Add the attribute Options for IPMultiNICB:
    # haconf -makerw
    # haattr -add IPMultiNICB Options
    # hatype -modify IPMultiNICB ArgList -add Options
    # haconf -dump -makero

4. Run the preceding steps on all nodes in the VCS cluster.


UNINSTALLING THE PATCH
----------------------
To uninstall the patch:

1. To stop VCS on the node, follow the steps given in the section 
   "Stopping VCS on a node" above.

2. Remove the patch by using the following command:
    # patchrm [patch-id]
   where [patch-id] is either of the following depending on 
   system configuration,
	For SunOS Release 5.10, [patch-id] is 143699-01.

3. Verify that the patch has been removed from the system:
    # showrev -p | grep [patch-id]
   There is no display on the output for the patch.

4. Restart VCS on the node following the steps given in the section   
   "Re-Starting VCS on a node" above.

5. Run the preceding steps on all nodes in the VCS cluster.



Read and accept Terms of Service