README VERSION		: 1.0
README Creation Date	: 2011-09-14
Patch-ID 		: 5.1.132.000 
Patch Name		: VRTSllt-5.1SP1RP2-SLES10
BASE PACKAGE NAME	: Veritas Low Latency Transport by Symantec
BASE PACKAGE VERSION	: VRTSllt 5.1SP1
Obsolete Patches	: NONE
Superseded Patches	: NONE
Required Patches	: NONE
Incompatible Patches	: NONE
Supported PADV		: sles10_x86_64
(P-Platform , A-Architecture , D-Distribution , V-Version)
Patch Category		:  PERFORMANCE
Reboot Required		: YES


KNOWN ISSUES : 


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


 Patch Id::5.1.132.000

* Incident no::2405391	 Tracking ID ::2405387

  Symptom::When the Low Latency Transit (LLT) module starts up, the 'lltconfig' command 
may fail to detect a duplicate cluster ID.

  Description::When LLT starts up, then the underlying code tries to determine whether the 
cluster ID that you specified is already in use by another running cluster. If 
yes, then the command fails and prevents panic in the future. In some cases, 
this check fails.

  Resolution::Symantec has modified the LLT code to ensure that duplicate cluster IDs are 
detected.

* Incident no::2439895	 Tracking ID ::2434732

  Symptom::When the Low Latency Transport (LLT) module starts, the 'lltconfig' command 
fails and an error message appears. For example, the following error message:
-----------------
Starting LLT...
LLT lltconfig ERROR V-14-2-15245 cluster id 345 is already being used by nid 0
and has the address - 00:03:BA:CB:F6:D2
LLT lltconfig ERROR V-14-2-15664 LLT could not configure any link
----------------
Where the node with nid 0 is part of the same cluster.

  Description::When you run the 'lltconfig' command in a cluster, the underlying code tries to 
determine if the cluster ID that you specified is already in use by another 
running cluster. If yes, then the command fails and prevents panic in the 
future.
However, in the present case, the code incorrectly detects the peer node to be 
part of a duplicate cluster.  This is due to the unexpected behavior of certain 
NIC drivers that add a few extra bytes at the end of every packet. 
The 'lltconfig' command fails to handle these extra bytes, and incorrectly 
displays the error message.

  Resolution::Symantec has modified the code for the 'lltconfig' command to truncate the 
extra bytes received along with LLT packets.

* Incident no::2477372	 Tracking ID ::2251045

  Symptom::A user may witness excessive CPU usage in the 'lltd' process of the Low Latency 
Transport (LLT) module.

  Description::During packet transmission, LLT on a receiving node receives packets in the 
interrupt context, and queues them in separate queues for every port. 
The 'lltd' process delivers these queued packets to LLT clients by using any one
of the available 'lltd' threads.  During heavy packet traffic, more than one
thread may attempt to serve a single port. Repeated attempts by various threads
to serve a port that is already served by another thread lead to high CPU
consumption.

  Resolution::Symantec has modified the LLT code to prevent LLT from invoking multiple 'lltd' 
threads for a given port.

Incidents from old Patches:
---------------------------
NONE