README VERSION		: 1.1
README CREATION DATE	: 2012-09-20
PATCH-ID 		: PHNE_43151 
PATCH NAME		: VRTSllt 5.1 SP1RP2
BASE PACKAGE NAME	: Veritas Low Latency Transport by Symantec
BASE PACKAGE VERSION	: VRTSllt 5.1SP1
SUPERSEDED PATCHES	: NONE
REQUIRED PATCHES	: NONE
INCOMPATIBLE PATCHES	: NONE
SUPPORTED PADV		: hpux1131
(P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION)
PATCH CATEGORY		:  CORE
PATCH CRITICALITY       : OPTIONAL
HAS KERNEL COMPONENT    : NO
ID                      : NONE
REBOOT REQUIRED		: NO

PATCH INSTALLATION INSTRUCTIONS:
--------------------------------


Please refer the release notes for installation instructions

PATCH UNINSTALLATION INSTRUCTIONS:
----------------------------------

Please refer the release notes for un-installation instructions.

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

SUMMARY OF FIXED ISSUES:
-----------------------------------------
2818222 (2804891)  lltconfig on boot up core dump and unable to send packets using sendto() 
2818573 (2818567)  LLT ARP flood issue. 


SUMMARY OF KNOWN ISSUES:
-----------------------------------------


KNOWN ISSUES : 
--------------


FIXED INCIDENTS: 
----------------


 PATCH ID:PHNE_43151

 * INCIDENT NO:2818222	 TRACKING ID:2804891

SYMPTOM: When you configure the Low Latency Transport (LLT) module in the verbose mode,
an incorrect error message may appear on the console with the message ID
V-14-2-15300.
LLT then encounters a segmentation fault, and the I18N module dumps a core file. 

DESCRIPTION: This behaviour occurs due to a buffer allocation failure during the sendto()
system call. The call fails and returns the error code ENOBUF. The lltconfig
utility tries to print an error message indicating the same. An argument type
mismatch occurs between the LLT and I18N modules, which in turn affects the
printing of the error message. This mismatch further leads to a segmentation
fault, and the I18N module then dumps a core file. 

RESOLUTION: Symantec has introduced, in the LLT code, a new message related to the sendto()
system call failure. This fixes the argument mismatch between the LLT and I18N
modules. 

 * INCIDENT NO:2818573	 TRACKING ID:2818567

SYMPTOM: During Low Latency Transport (LLT) configuration, an internal check for 
duplicate cluster IDs may lead to either a private network slowdown, or panic 
in the Veritas Cluster Server (VCS) cluster. 

DESCRIPTION: During LLT configuration, LLT broadcasts a packet to detect duplicate cluster 
IDs, if any. 

In some cases,  LLT may broadcast multiple packets in quick succession. This 
may slow down the private network (cluster network). This irregular behavior 
usually occurs on Linux systems due to the Linux poll() system call 
functionality.

In other cases, LLT broadcasts a single packet to detect duplicate cluster IDs. 
However, the packet may not reach the desired node, especially if you configure 
LLT soon after a system reboot. As a result, a duplicate cluster ID may go 
undetected. When the Group Atomic Broadcast module (GAB) comes online, the 
duplicate cluster ID case leads to panic in the cluster. 

RESOLUTION: Symantec has modified LLT to generate multiple broadcast packets to detect 
duplicate cluster IDs, during LLT configuration. As a result, if one packet is 
lost, the next packet may detect a duplicate cluster ID, if any. To prevent the 
packets from flooding the private network, LLT broadcasts only one packet per 
second on each private link. 

INCIDENTS FROM OLD PATCHES:
---------------------------
NONE