Point Patch for Veritas Cluster Server Management Console 5.1
========================================================================
Name:                           5.1+e1144918

Date:                           07 Feb 2008

VCS Management Console Release:    5.1


PROBLEM DESCRIPTION:
--------------------

This point patch addresses the following known issues in the 5.1
release of the VCS Management Console:

* Management server crashes after creating report which has Japanese
 text in "Report Description." (1132801)

* Management server runs out of memory for large environments. (1142963)

* If a cluster is deleted from the local management server, the cluster
 is still present in the peer management server. (1131263)

* Online Help does not display .png files. (1134337)

* The date field is not internationalized under the Log tab. (1141872)

* The "Assign Privileges on Clusters" wizard does not remove old
 privileges when assigning new ones. (1121315)

* Adding remote clusters fails for certain secure clusters. (1129642)

* It takes a long time to log on to the console for large environments.
 (1144143)

* "Enterprise -> All Users -> All VCS Users" page takes a long time for
 large environments. (1144143)

* Some cluster logs may be lost on upgrade. (1134936)

* Error in reconnection logic when cluster restarts while Cluster
 Connector is waiting to synchronize with the management server.
 (1143714)

* Some user privilege assignment operations may fail for clusters
 managed by a peer management server. (1129489)

* Console will show Japanese text in some cases even if the user logs
 in with the English locale. (1133894)

Apply this point patch on the management server. If you want to address
the issue of "Adding remote clusters fails for certain secure clusters.
(1129642)" then apply part of this point patch on the VCS cluster that
is experiencing the problem.

For the latest information on updates, patches, and software issues
regarding Veritas Cluster Server Management Console, see the following
TechNote on the Symantec Technical Support web site:

http://entsupport.symantec.com/docs/290657

 
FILES AFFECTED BY THIS PATCH
---------------------------

* Management Server:

 Solaris:
     /opt/VRTScmcm/webapp/cmc.war

 Windows:
     C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5\ROOT5.war
   
* Cluster Connector (For 1129642 only):

 All Unix platforms:
     /opt/VRTScmccc/lib/Common.jar

 Windows:
     C:\Program Files\Symantec\VRTScmccc\lib\Common.jar


VERIFYING CRC AND BYTE COUNT
----------------------------

Use the cksum command to ensure that the file you have downloaded
matches the following cksum and byte count:

# cksum cmc.war Common.jar

364612631      28110123        cmc.war
632094981      940655          Common.jar

The output displays the CRC value (first value), the byte count
(second value), and the file name (third value).


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

DOWNLOAD THE PATCH:

1. Download the file 1144918d_302963.zip from the link below.
2. Extract the files by right-clicking the .zip file in Windows Explorer.

Windows:
--------

1. Do the following to verify that the system has correct version of VCS MC
  management server installed:

  - Click Start > Control Panel > Add or Remove Programs
  - Search the list for "VCS Management Console 5.1 for Windows"

2. Stop the management server.
 
  For a standalone management server, obtain a command prompt and enter the
  following command:

  C:\>net stop cmcweb

  For a clustered management server, obtain a command prompt and enter the
  following command:
 
  C:\>hagrp -offline CMC_MS -any

NOTE: For the clustered management server environment, repeat steps 3-5
     on each clustered system.

3. Do the following to make a backup of the original ROOT5.war file.

  - Open a command prompt.

  - Use the following command to change directory to the "root5" directory for
    the VCS MC server:
 
    C:\>cd "C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5"

  - Use the following command to make a copy of the ROOT5.war file:

    C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5>copy ROOT5.war ROOT5.war.orig

  NOTE: The above location might be different for your machine. For
  example, on a 64-bit OS, the default location is
  C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5

4. Do the following to delete the previous ROOT5 folder:

  - Open a command prompt

  - Use the following command to change directory to the "root5" directory for
    the VCS MC server:
 
    C:\>cd "C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5"

  - Delete the "ROOT5" folder:

    C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5>rd /s ROOT5

5. Do the following to replace the original ROOT5.war file with one provided in
  this point patch.
 
  NOTE: The file provided in the patch is called cmc.war, while the
  file to be replaced is called ROOT5.war.

  - Open a command prompt.

  - Change directory to "root5" directory for the VCS MC server:

    C:\>cd "C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5"
 
  - Replace the original ROOT5.war with patch file cmc.war:

    C:\Program Files\Symantec\VRTScmcm\VRTSweb\admin\root5>copy <patch_folder>\cmc.war ROOT5.war

6. If you plan to manage more than 25 clusters using the management server, use
  the following command to give more memory to the java process:

  C:\> "C:\Program Files\Symantec\VRTScmcm\VRTSweb\bin\webgui.exe" maxheap 1500

  NOTE: This assumes you have at least 2 GB ram on your server. The argument
  "1500" to the command above is in MBs. You can give more or less ram to your
  java process based on your environment. Setting value to 1500 will let you
  manage upto 15,000 cluster objects, which is equivalent to about 75 clusters,
  each with 2 systems, 10 service groups, and 100 resources.

7. Restart the management server.
 
  For a standalone management server, obtain a command prompt and enter the
  following command:
   
  C:\>net start cmcweb

  For a clustered management server, obtain a command prompt and enter the
  following command:

  C:\>hagrp -online CMC_MS -any

8. Wait for several minutes and then do the following to confirm that the server
  has restarted:

  - Open a command prompt.

  - Issue the following command:

    C:\>net start

  - Confirm that "Veritas Cluster Server Management Console Web Server"
    is listed as a running service.


For 1129642 only
----------------

On each cluster with systems requiring the fix for #1129642, do the following:

1. Use the following command to offline the CMC group and stop the Cluster
  Connector:

  C:\> hagrp -offline CMC -any

2. On each cluster system, use the following commands to backup the existing
  Common.jar file:

  C:\> cd C:\Program Files\Symantec\VRTScmccc\lib
  C:\> copy .\Common.jar .\Common.jar.orig

3. On each cluster system, use the following command to replace the existing
  Common.jar file with the Common.jar included in the hotfix archive:

  C:\> copy <patch_folder>\Common.jar Common.jar

4. On any cluster system, use the following command to bring the CMC group
  online and start the Cluster Connector:

  C:\> hagrp -online CMC -any

5. Verify the cluster has reattached to the management server by checking status
  on the VCS Management console.





DISCLAIMER
This is a supported fix that has not been fully regression tested and must
be applied only to systems that are severely affected by the problem. For
other situations, we recommend that you wait for the next Maintenance
Pack that will contain this fix. Contact Symantec Technical Support for
more information.