* * * READ ME * * *
            * * * Veritas Cluster Server Agents 6.1.1 * * *
                     * * * Hot Fix 6.1.1.000 * * *
                         Patch Date: 2014-10-15


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 Cluster Server Agents 6.1.1 Hot Fix 6.1.1.000


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Linux


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSucsutil


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server Agents 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.1.1.0
* 3626018 (3640824) Clean entry point of the CiscoUCS resource is invoked 
when the ucsha refresh command is executed with invalid data in the UCS 
configuration file.
* 3628129 (3635281) Disassociation and association operations of a faulted 
service profile fails during AUTOMATIC failover.
* 3639125 (3640818) During intelligent failover, an available blade server 
with a fault code specified in the UCS configuration file gets chosen as a 
target for failover.


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

Patch ID: 6.1.1.0

* 3626018 (Tracking ID: 3640824)

SYMPTOM:
Clean operation of the CiscoUCS agent fails after agent reports 
unexpected offline of CiscoUCS resource during the refresh operation.

DESCRIPTION:
UCSHA refresh operation stops the UCSHA utility from monitoring 
the service profiles and also removes the existing service profile data. The 
utility then proceeds with validating the UCS configuration file. For an 
invalid UCS configuration file, the validation fails and the UCSHA refresh 
operation exits without starting UCSHA for monitoring the service profiles. 
Subsequent monitor entry points report unexpected offline due to 
unavailability of UCS service profile data that results in invoking the 
Clean entry point. The Clean entry point fails to stop UCSHA since it was 
already stopped.

RESOLUTION:
Symantec has updated the UCSHA utility to validate UCSHA 
configuration file before stopping the monitoring of service profile in 
CiscoUCS.

* 3628129 (Tracking ID: 3635281)

SYMPTOM:
Disassociation and association operations of the faulted service 
profile fails and a message is logged in the UCSHA log file that indicates
the corresponding failure.

DESCRIPTION:
During automatic failover, the UCSHA performs disassociation 
and association operation of the faulted service profile. In absence of 
cookie,
these operations fail due to enforced security on the UCS manager.

RESOLUTION:
Symantec has modified the UCSHA utility to pass the cookie with 
the disassociation and association commands during disassociation and 
association operations respectively.

* 3639125 (Tracking ID: 3640818)

SYMPTOM:
Intelligent failover mechanism chooses the available server for 
service profile failover even though it has a fault with the same fault code 
as specified in the UCS configuration file.

DESCRIPTION:
During intelligent failover, the UCSHA utility goes through the 
list of available blade servers to pick an appropriate target for service 
profile failover. But UCSHA does not checks if the potential target blade 
server has an existing fault with the fault code specified in the UCS 
configuration file.

RESOLUTION:
Symantec has modified the UCSHA utility to select an available 
blade server as a potential target only when the server does not have any 
fault code specified in the UCS configuration file.



INSTALLING THE PATCH
--------------------
1) Save the VCS configuration and take backup of main.cf
# haconf -dump 

2) Stop UCSHA and probe the resource to make sure that CiscoUCS resource is offline 
# /opt/VRTSagents/ha/bin/CiscoUCS/ucsha -stop 
# hares -probe <res_name>  -sys <system_name>  
# hares -state <res_name>  -sys <system_name>  

3) Take backup of UCSConfiguration file provided in the UCSConfigFile attribute of CiscoUCS resource

4) Stop the CiscoUCS agent using following commands 
# haagent -stop CiscoUCS -force -sys <system_name>  
# haagent -display CiscoUCS 

5) Uninstall old CiscoUCS agent rpm using following command 
# rpm -e VRTSucsutil 

6) Install new CiscoUCS agent rpm using following command 
# rpm -ivh VRTSucsutil-6.1.1.0-GA_GENERIC.noarch.rpm 

7) Start CiscoUCS agent using following commands 
# haagent -start CiscoUCS -sys <system_name>  
# haagent -display CiscoUCS 


Refer to the CiscoUCS agent documentation for more details on install/uninstall instructions.


REMOVING THE PATCH
------------------
1) Save the VCS configuration and take backup of main.cf 
# haconf -dump 

2) Stop UCSHA and probe the resource to make sure that CiscoUCS resource is offline
# /opt/VRTSagents/ha/bin/CiscoUCS/ucsha -stop 
# hares -probe <res_name>  -sys <system_name>  
# hares -state <res_name>  -sys <system_name>  

3) Take backup of UCSConfiguration file provided in the UCSConfigFile attribute of CiscoUCS resource

4) Stop CiscoUCS agent using following commands 
# haagent -stop CiscoUCS -force -sys <system_name>  
# haagent -display CiscoUCS 

5) Uninstall CiscoUCS agent rpm using following command 
# rpm -e VRTSucsutil 

Refer to the CiscoUCS agent documentation for more details on install/uninstall instructions


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


OTHERS
------
NONE