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

 Basic information
Release type: Hot Fix
Release date: 2009-10-06
OS update support: None
Technote: None
Documentation: None
Popularity: 899 viewed    35 downloaded
Download size: 1.23 MB
Checksum: 3405961223

 Applies to one or more of the following products:
Cluster Server 5.0MP3 On AIX 5.3
Cluster Server 5.0MP3 On AIX 6.1
Storage Foundation Cluster File System 5.0MP3 On AIX 5.3
Storage Foundation Cluster File System 5.0MP3 On AIX 6.1
Storage Foundation for DB2 5.0MP3 On AIX 5.3
Storage Foundation for DB2 5.0MP3 On AIX 6.1
Storage Foundation for Oracle 5.0MP3 On AIX 5.3
Storage Foundation for Oracle 5.0MP3 On AIX 6.1
Storage Foundation for Oracle RAC 5.0MP3 On AIX 5.3
Storage Foundation for Oracle RAC 5.0MP3 On AIX 6.1
Storage Foundation HA 5.0MP3 On AIX 5.3
Storage Foundation HA 5.0MP3 On AIX 6.1

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

This patch is obsolete. It is superseded by: Release date
sfha-aix-5.0MP3RP5 2011-05-10
sfha-aix-5.0MP3RP4 (obsolete) 2010-06-21
sfha-aix-5.0MP3RP3 (obsolete) 2010-01-15
vcs-aix-VRTSllt-5.0MP3RP2HF2 (obsolete) 2010-01-04

 Fixes the following incidents:
1831925, 1838546

 Patch ID:
VRTSllt.rte-05.00.0003.0201

 Readme file  [Save As...]
* * * HOTFIX  5.0MP3RP2 HF1 for LLT on VCS 5.0MP3 AIX * * *

                  Patch Date: Oct 5, 2009

   This README provides information on:

   * BEFORE GETTING STARTED
   * FIXES AND ENHANCEMENTS INCLUDED IN THESE PATCHES
   * PACKAGES AFFECTED BY THESE PATCHES
   * INSTALLING THE PATCHES IN VCS ENVIRONMENT
   * UNINSTALLING THE PATCHES IN VCS ENVIRONMENT
   * INSTALLING THE PATCHES IN SFRAC ENVIRONMENT
   * UNINSTALLING THE PATCHES IN SFRAC ENVIRONMENT 


BEFORE GETTING STARTED
----------------------
This patch applies to VRTSllt VCS 5.0MP3 running on AIX 5.3. 
Ensure that you are running the supported configuration before installing this patch.


FIXES AND ENHANCEMENTS INCLUDED IN THIS PATCH
---------------------------------------------
Etrack Incidents: 1831925, 1838546 
1831925:Send hbs from multiple places if it has been too long since we sent a hb
1838546:Cap the time for which we send out of context hbs


PACKAGES AFFECTED BY THE PATCHES
---------------------------------
This patch brings the 
	VRTSllt.rte fileset to 5.0.3.201 level



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

Stopping the cluster:
-------------------
1. Offline all applications, which are configured on CVM/CFS 
   and are outside VCS control.

    After all applications using CFS and CVM have been taken down,
    run 'slibclean' to unload the libraries from memory.

2. Stop VCS on the current node.
	# /opt/VRTSvcs/bin/hastop -local 
   Verify that ports 'f' (CFS), 'v' and 'w' (CVM), 'h' (VCS) have been closed,
	# /sbin/gabconfig -a
   The display should not have port 'f', 'v', 'w' and 'h' listed	

3. If VXFEN is not configured, please go to step 5

4. Unconfigure VxFen:
	#  /sbin/vxfenconfig -U
   Verify that port 'b' has been closed
	# /sbin/gabconfig -a
   The display should not have port 'b' listed	

5. Unconfigure GAB:
	# /sbin/gabconfig -U

6. Unconfigure LLT:
	# /sbin/lltconfig -Uo

7. Unload the GAB driver:
	# /etc/methods/gabkext -stop

   Unload the LLT driver:
	# /usr/sbin/strload -ud /usr/lib/drivers/pse/llt

8. Verify that the LLT driver has been unloaded
	# /usr/sbin/strload -qd /usr/lib/drivers/pse/llt
	/usr/lib/drivers/pse/llt: no
   If llt is still loaded "yes" will show up in the output above.

   Verify that the GAB driver has been unloaded:
	# /etc/methods/gabkext -status
	gab: unloaded

NOTE: If you are unable to successfully unload the LLT driver,
the server must be rebooted AFTER the installation of the patch. 
This is so that the new LLT driver gets loaded in the AIX kernel.

Installing Patch on all nodes:
-----------------------------
1. Change directory to the patch location and install the LLT 
   patch from the bff files from the same location:
	# installp -a -d ./VRTSllt.rte.bff VRTSllt.rte

2. Verify that the new fileset(s) has been installed:
	# lslpp -l VRTSllt.rte

  VRTSllt.rte              5.0.3.201  APPLIED    Veritas Low Latency Transport
                                                 5.0MP3RP2 HF1 by Symantec
                                                 09/30/2009-22:06:40 Build
                                                 Env:AIX ogma 3 5 0001D4CAD300
                                                 IBM, 9115-505

Re-starting the cluster:
-----------------------
1. Verify that the new LLT driver has been loaded:
	# strload -qd /usr/lib/drivers/pse/llt
	/usr/lib/drivers/pse/llt: yes

2. If not already loaded, load the newly installed LLT driver:
	# strload -d /usr/lib/drivers/pse/llt

3. Configure LLT:
	# /sbin/lltconfig -c

4. Verify that LLT has been configured properly
	# /sbin/lltconfig
	LLT is running

5. Configure GAB:
	# sh /etc/gabtab

6. Verify that the GAB membership shows up correctly:
	# /sbin/gabconfig -a
   The display should have Port 'a' listed

7. Configure VxFen (if VxFEN was configured previously)
	# /sbin/vxfenconfig -c
   Verify that vxfen has been configured
	# /sbin/gabconfig -a
   The output should list port 'b'

8. Start VCS:
	# /opt/VRTSvcs/bin/hastart
   Verify that VCS is up and running:
	# /sbin/gabconfig -a
   The display should show port 'f', 'v', 'w' and 'h' listed.
   The 'f', 'v' and 'w' port will be listed if CVM and CFS are configured.

9.  Start applications (stopped earlier), which are outside VCS control.



Committing the Patch:
---------------------
1.  To commit the patch:
(Note: The patch cannot be backed out once it is committed.)
	# installp -c VRTSllt.rte

2.  Verify that the fileset is committed:
	lslpp -l VRTSllt.rte

  VRTSllt.rte              5.0.3.201  COMMITTED  Veritas Low Latency Transport
                                                 5.0MP3RP2 HF1 by Symantec
                                                 09/30/2009-22:06:40 Build
                                                 Env:AIX ogma 3 5 0001D4CAD300
                                                 IBM, 9115-505




UNINSTALLING THE PATCHES IN VCS ENVIRONMENT
-------------------------------------------
The VRTSllt.rte.bff patch can ONLY be backed out if it has not been committed.

NOTE: Before uninstalling patch, make sure that the APAR changing 
DLPI behaviour is not installed on the system by running 
following commands:
  # instfix  -iv | grep "BRING DLPI DRIVER "TO SPEC""

If above mentioned command returns an APAR then backing out
this point patch will move llt to older version, which will 
cause panic or hang.



Steps to Backout the Patch:
--------------------------
1. Follow the steps provided under "Stopping the cluster" section above, 
   to stop the cluster & unload the drivers.


2. Backout the patches by the following command:
	# installp -r VRTSllt.rte 5.0.3.201


3. Verify that the patch has been backed out:
   (Note: The previously installed fileset(s) will be in committed state again.
       It may differ from the mentioned, if a Hotfix was installed on top 
       of VCS 5.0MP3RP2)

	# lslpp -l VRTSllt.rte
  VRTSllt.rte              5.0.3.200   COMMITTED   Veritas Low Latency Transport
                                                   5.0MP3RP2 by Symantec
                                                   07/07/2009-17:19:00 Build
                                                   Env:AIX ogma 3 5 0001D4CAD300
                                                   IBM, 9115-505


4. Restart the cluster following the steps under 
   "Re-Start the cluster" section above.

 Note: The llt driver will now refer to the old one.




INSTALLING THE PATCHES IN SFRAC ENVIRONMENT
-------------------------------------------
The following steps should be run on all nodes in the cluster,
with SFRAC stack installed:

1. Offline all applications, which are configured on CVM/CFS 
   and are outside VCS control.

2. If Oracle database is not configured in VCS, stop it using following command:
	$ srvctl stop instance -d <database name> -i <instance name>

3(a). For Oracle 9iR2, stop 'gsd' using the follwing command as Oracle user
   	$ gsdctl stop
   To check the status of gsdctl, run the following command:
	$ gsdctl stat
   The gsdctl command is typically found in $ORACLE_HOME/bin.

3(b). For Oracle 10gR1 and 10gR2, Stop CRS manually, 
      if CRS is not under VCS control.
         # /etc/init.crs stop

4.  After all the oracle instances and other applications using 
    CFS and CVM have been stopped, run 'slibclean' to unload 
    the libraries from memory.

5. Stop VCS on the current node.
	# /opt/VRTSvcs/bin/hastop -local 

6. Verify that ports 'h', 'f', 'v' and 'w' have been closed
	# /sbin/gabconfig -a
   The display should not have ports 'h', 'f', 'v' and 'w' listed

7. Unconfigure VCSMM:
	# /sbin/vcsmmconfig -U
   Verify that port 'o' has been closed
	# /sbin/gabconfig -a
   The display should not have port 'o' listed.
   If it does ensure that Oracle instances are offline.

8. Unconfigure LMX:
	# /sbin/lmxconfig -U

9. Unconfigure VxFen:
	# /sbin/vxfenconfig -U
    Verify that port 'b' has been closed
	# /sbin/gabconfig -a
    The display should not have port 'b' listed

10. Unmount ODM:
	# umount /dev/odm
    Verify that port 'd' has been closed
	# /sbin/gabconfig -a
    The display should not have port 'd' listed

11. At this point all gab ports except port 'a' should have been closed
    Verify this as follows:
	# /sbin/gabconfig -a

12. Follow steps 5 to 8 of "Stopping the cluster" section from 
    "INSTALLING THE PATCHES IN VCS ENVIRONMENT" chapter above.

13. Follow all the instruction in "Installing the patch" section
    from "INSTALLING THE PATCHES IN VCS ENVIRONMENT" chapter above.

14. Follow steps 1 to 7 of "Re-starting the cluster" section from 
    "INSTALLING THE PATCHES IN VCS ENVIRONMENT" chapter above.

15. Configure LMX:
	# /sbin/lmxconfig -c

16. Configure VCSMM:
	# /sbin/vcsmmconfig -c
    Verify that vxfen has been configured
	# /sbin/gabconfig -a
    The output should list port 'o'

17. Mount ODM:
	# mount /dev/odm

18. Start VCS:
	# /opt/VRTSvcs/bin/hastart

19. Check if all ports are now open
	# /sbin/gabconfig -a
    The output should list ports 
    'a', 'b', 'd', 'f', 'h', 'o', 'v', and 'w'.

20(a). For Oracle 10gR1 and 10gR2, start CRS manually,
       if CRS is not under VCS control.
         # /etc/init.crs start

20(b). For Oracle 9iR2, start 'gsd' using the follwing command as Oracle user
   	$ gsdctl start
   To check the status of gsdctl, run the following command:
	$ gsdctl stat
   The gsdctl command is typically found in $ORACLE_HOME/bin.

21. If Oracle database is not configured in VCS, 
    start it using following procedure.
	$ srvctl start instance -d <database name> -i <instance name>

22. Online all applications, which are configured on CVM/CFS 
    and are outside VCS control (stopped earlier).

23. To commit the patches follow "Committing the Patch" section from 
    "INSTALLING THE PATCHES IN VCS ENVIRONMENT" chapter above.




UNINSTALLING THE PATCHES IN SFRAC ENVIRONMENT
---------------------------------------------
The VRTSllt.rte.bff patch can ONLY be backed out if it has not been committed.


NOTE: Before uninstalling patch, make sure that the APAR 
changing DLPI behaviour is not installed on the system by
running following commands:
   # instfix  -iv | grep "BRING DLPI DRIVER "TO SPEC""

If above mentioned command returns an APAR then backing out
this point patch will move llt to older version, which will 
cause panic or hang.


Steps to Backout the Patch:
---------------------------
1.  Follow the steps outlined 1 through 12 of chapter 
    "INSTALLING THE PATCHES IN SFRAC ENVIRONMENT"
    to stop and unload the drivers.

2. Backout the patches:
	# installp -r VRTSllt.rte 5.0.3.201

3. Verify that the patch has been backed out:
   (Note: The previously installed fileset(s) will be in committed state again.
       It may differ from the mentioned, if a Hotfix was installed on top 
       of VCS 5.0MP3RP2)

	# lslpp -l VRTSllt.rte
  VRTSllt.rte              5.0.3.200   COMMITTED   Veritas Low Latency Transport
                                                   5.0MP3RP2 by Symantec
                                                   07/07/2009-17:19:00 Build
                                                   Env:AIX ogma 3 5 0001D4CAD300
                                                   IBM, 9115-505

4. Next as before go through the process of loading and configuring
   LLT, GAB and bringing up SFRAC (steps 14 through 23 above of 
   chapter "INSTALLING THE PATCHES IN SFRAC ENVIRONMENT").

 Note: The llt driver will now refer to the old one.



Read and accept Terms of Service