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.
llt-hpux1131-5.1SP1RP3P2
Sign in if you want to rate this patch.

 Basic information
Release type: P-patch
Release date: 2017-05-03
OS update support: None
Technote: None
Documentation: None
Popularity: 242 viewed    12 downloaded
Download size: 782.41 KB
Checksum: 1566002615

 Applies to one or more of the following products:
Cluster Server 5.1SP1 On HP-UX 11i v3 (11.31)
Storage Foundation Cluster File System 5.1SP1 On HP-UX 11i v3 (11.31)
Storage Foundation for Oracle RAC 5.1SP1 On HP-UX 11i v3 (11.31)
Storage Foundation HA 5.1SP1 On HP-UX 11i v3 (11.31)

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

This patch supersedes the following patches: Release date
llt-hpux1131-5.1SP1RP3P1 (obsolete) 2014-08-01

 Fixes the following incidents:
3436040, 3904178

 Patch ID:
PHNE_44585

 Readme file  [Save As...]
                          * * * READ ME * * *
         * * * Veritas Low Latency Transport 5.1 SP1 RP3 * * *
                         * * * P-patch 2 * * *
                         Patch Date: 2017-04-26


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 Low Latency Transport 5.1 SP1 RP3 P-patch 2


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
HP-UX 11i v3 (11.31)


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSllt


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 5.1 SP1
   * Veritas Storage Foundation Cluster File System 5.1 SP1
   * Veritas Storage Foundation for Oracle RAC 5.1 SP1
   * Veritas Storage Foundation HA 5.1 SP1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: PHNE_44585
* 3904178 (3916859) Defects resolved by the patch PHNE_44046 will still be 
encountered after patch installation as a result.
Patch ID: PHNE_44046
* 3436040 (3436039) In case of a link failover in an aggregated link, the LLT
protocol keeps transmitting the broadcast packets with an old source MAC address.


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

Patch ID: PHNE_44585

* 3904178 (Tracking ID: 3916859)

SYMPTOM:
The LLT module shipped with patch PHNE_44046 does not load in the 
running kernel following a successful patch install.  Defects resolved by the 
patch will still be encountered after patch installation as a result.

DESCRIPTION:
The LLT module is a dynamic loadable kernel module (DLKM). If the 
module is not unloaded (by stopping the SG-CFS-pkg package in a 
Serviceguard/CFS cluster) before PHNE_44046 is installed, the new, patched LLT 
module will not be loaded in the running kernel even after system reboots. It 
is because some DLKM-related flags are not correctly set in the patch. As a 
result, the issue which is supposed to be fixed in patch still persists.

RESOLUTION:
The patch is modified and the needed DLKM-related flags have been 
set. With these flags set, a reboot will be triggered if the existing LLT 
module is still loaded during patch installation to apply the patched LLT 
module.

Patch ID: PHNE_44046

* 3436040 (Tracking ID: 3436039)

SYMPTOM:
When an aggregated link is configured with the Low Latency Transport
(LLT) protocol using the fast-path mechanism, and a failover happens in this
link, then the LLT continues transmitting the broadcast packets with an old
source MAC address.

DESCRIPTION:
Due to a link failure or some other reason, LLT fails to update the source MAC
address of the link in the broadcast packet header and continues transmitting
the broadcast packets with an old source MAC address.

RESOLUTION:
The LLT source code is modified such that the source MAC address is updated in
the broadcast packet header when the link failover occurs.



INSTALLING THE PATCH
--------------------
Perform the following steps on all the nodes of the cluster:

1) Bring down the VCS stack with the help of corresponding init scripts of the various modules.

2) Unconfigure GAB and LLT modules with:
   # gabconfig -U
   # lltconfig -Uo

3) Unload GAB and LLT modules with:
   # kcmodule gab=unused
   # kcmodule llt=unused

4) Apply the patch with:
   # swinstall -x autoreboot=true -s <patch_directory>   PHNE_44585

5) Start the LLT and GAB modules with the help of init scripts:
   # /sbin/init.d/llt start
   # /sbin/init.d/gab start

6) Start rest of the VCS stack with the help of corresponding init scripts.


REMOVING THE PATCH
------------------
Perform the following steps on all the nodes of the cluster:

1) Bring down the VCS stack with the help of corresponding init scripts of the various modules.

2) Unconfigure GAB and LLT modules with:
   # gabconfig -U
   # lltconfig -Uo

3) Unload GAB and LLT modules with:
   # kcmodule gab=unused
   # kcmodule llt=unused

4) Remove the patch with:
   # swremove -x autoreboot=true PHNE_44585

5) Start the LLT and GAB modules with the help of init scripts:
   # /sbin/init.d/llt start
   # /sbin/init.d/gab start

6) Start rest of the VCS stack with the help of corresponding init scripts.


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE



Read and accept Terms of Service