|
---|
Release type: | Hot Fix |
Release date: | 2012-04-13 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 598 viewed downloaded |
Download size: | 70.81 MB |
Checksum: | 2342616503 |
Cluster Server Management Console 5.5.1 On RHEL5 x86-64
Cluster Server Management Console 5.5.1 On Solaris SPARC Cluster Server Management Console 5.5.1 On Windows |
None.
|
2680108
|
None.
|
Date: 2012-02-17 OS: ALL SUPPORTED PLATFORMS OS Version: ALL SUPPORTED VERSIONS Etrack Incidents: 2680108 Errors: VCS MC console does not support SFHA/SFWHA secure clusters 6.0 onwards (pre-6.0 secure clusters are supported). Problems Fixed: Now VCSMC can manage SFHA/SFWHA secure clusters 6.0 onwards in addition to pre-6.0 ones. Install Instructions: --------------------- Follow below instructions to apply the patch for WINDOWS VCS Management Console: -------------------------------------------------------------------------------- 1) Extract the files from the patch to your local machine in a directory. E.g. c:\PATCH_VCSMC 2) Ensure that the extracted patch has ROOT5.war file. 3) Navigate to the install directory of VCS MC via command line and stop the VCS MC webserver using the following command: "<Install directory of VCS MC>\VRTSweb\bin\webgui.exe stop" E.g. C:\Program Files(x86)\Symantec\VRTScmcm\VRTSweb\bin\webgui.exe stop 4) If it does not work, use "<Install directory of VCS MC>\VRTSweb\bin\webgui.exe stop force". 5) Go to <Install directory of VCS MC>\VRTSweb\admin\root5. E.g. C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5 6) Take a backup(cut and paste) of the ROOT5.war file to another directory (e.g. C:\VCSMCBackUp\) in your machine since this is the file you will be replacing to apply this patch. Delete the entire C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5\ROOT5 folder, including all its subdirectories. 7) Copy the ROOT5.war file from Step 2 to the VCS MC install location. In this case Copy the ROOT5.war from "c:\PATCH_VCSMC" to "C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5". 8) Start the webserver using the following command: "<Install directory of VCS MC>\VRTSweb\bin\webgui.exe start". 9) In order to ensure successful discovery of your VCS 6.0 clusters, you must setup a trust between the authentication brokers of the machine on which you are running VCS MC and each of the cluster nodes. Follow the steps given below to setup AT trust. 10) On the machine in which VCS MC is running, navigate to the install directory of AT via command line and run the following command to setup trust: "<Install directory of AT>\Authentication\bin\vssat.exe setuptrust --broker <IP Address of cluster node>:14149 --securitylevel medium" E.g. C:\Program Files (x86)\VERITAS\Security\Authentication\bin\vssat.exe setuptrust --broker <IP Address of cluster node>:14149 --securitylevel medium Note: Do this for every cluster node. 11) On each of the VCS 6.0 secure cluster nodes (if the cluster node is a Windows machine), do the following: a) Navigate to the install directory of AT via command prompt. E.g. navigate to C:\Program Files\Veritas\cluster server\eat\bin\ b) set the environment variable "EAT_DATA_DIR" using the command: "set EAT_DATA_DIR=C:\Program Files\Veritas\cluster server\EAT\datadir\HAD" c) Then run the following command to setup trust between the cluster node and the VCS MC server: "<Install directory of AT>\bin\vssat.bat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium" E.g. C:\Program Files\Veritas\cluster server\eat\bin\vssat.bat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium On each of the VCS 6.0 secure cluster nodes (if the cluster node is a unix machine), do the following: a) Navigate to the install directory of AT via command prompt. E.g. /opt/VRTSvcs/bin/ b) set the environment variable "EAT_DATA_DIR" using the command: "export EAT_DATA_DIR=/var/VRTSvcs/vcsauth/data/HAD" c) Then run the following command to setup trust between the cluster node and the VCS MC server: "<Install directory of AT>/bin/vcsat setuptrust -b <IP Address of VCS MC machine> -s medium" E.g. /opt/VRTSvcs/bin/vcsat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium 12) Try adding the cluster from VCS MC. Make sure that you select the correct port on the "Specify access credentials." page. Here you will see a new dropdown menu next to the "Use Authentication Broker on each cluster" radio button. You should select port 14149 if you are adding 6.0 clusters and port 2821 if you are adding clusters with pre 6.0 engine versions. Follow below instructions to apply the patch for VCS Management Console on all UNIX based platforms: ---------------------------------------------------------------------------------------------------- 1) Extract the files from the patch to your local machine in a directory. E.g. /var/PATCH_VCSMC 2) Ensure that the extracted patch has ROOT5.war file. 3) Navigate to the install directory of VCS MC and stop the VCS MC webserver using the following command: #<Install directory of VCS MC>/bin/webgui stop E.g.: #/opt/VRTSweb/bin/webgui stop 4) Go to /opt/VRTScmcm/webapp/ 5) Take a backup(cut and paste) of the cmc.war file to another directory (e.g. /var/VCSMCBackUp/) in your machine since this is the file you will be replacing to apply this patch. Delete the entire /opt/VRTSweb/admin/root5/ROOT5 folder, including all its subdirectories. 6) Copy the ROOT5.war file from Step 2 to the VCS MC install location. In this case copy "/var/PATCH_VCSMC/ROOT5.war" to "/opt/VRTScmcm/webapp/cmc.war". 7) Start the webserver using the following command: #/opt/VRTSweb/bin/startApp cmc /opt/VRTSweb/VERITAS/ 8) In order to ensure successful discovery of your VCS 6.0 clusters, you must setup a trust between the authentication brokers of the machine on which you are running VCS MC and each of the cluster nodes. Follow the steps given below to setup AT trust. 9) On the machine in which VCS MC is running, navigate to the install directory of AT via command line and run the following command to setup trust: #<Install directory of AT>/bin/vssat setuptrust --broker <IP Address of cluster node>:14149 --securitylevel medium E.g.: #/opt/VRTSat/bin/vssat setuptrust --broker <IP Address of cluster node>:14149 --securitylevel medium Note: Do this for every cluster node. 10) On each of the VCS 6.0 secure cluster nodes (if the cluster node is a unix machine), do the following: a) Navigate to the install directory of AT via command prompt. E.g. /opt/VRTSvcs/bin/ b) set the environment variable "EAT_DATA_DIR" using the command: "export EAT_DATA_DIR=/var/VRTSvcs/vcsauth/data/HAD" c) Then run the following command to setup trust between the cluster node and the VCS MC server: "<Install directory of AT>/bin/vcsat setuptrust -b <IP Address of VCS MC machine> -s medium" E.g. /opt/VRTSvcs/bin/vcsat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium On each of the VCS 6.0 secure cluster nodes (if the cluster node is a Windows machine), do the following: a) Navigate to the install directory of AT via command prompt. E.g. navigate to C:\Program Files\Veritas\cluster server\eat\bin\ b) set the environment variable "EAT_DATA_DIR" using the command: "set EAT_DATA_DIR=C:\Program Files\Veritas\cluster server\EAT\datadir\HAD" c) Then run the following command to setup trust between the cluster node and the VCS MC server: "<Install directory of AT>\bin\vssat.bat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium" E.g. C:\Program Files\Veritas\cluster server\eat\bin\vssat.bat setuptrust -b <IP Address of VCS MC machine>:2821 -s medium 11) Try adding the cluster from VCS MC. Make sure that you select the correct port on the "Specify access credentials." page. Here you will see a new dropdown menu next to the "Use Authentication Broker on each cluster" radio button. You should select port 14149 if you are adding 6.0 clusters and port 2821 if you are adding clusters with pre 6.0 engine versions. Uninstall Instructions: ---------------------- 1) Stop the webserver ("webgui stop" or "webgui stop force") on the node where you want to uninstall the patch. 2) Revert the copy of ROOT5.war from the directory where you stored the backup(e.g. C:\VCSMCBackUp\ or /var/VCSMCBackUp/) to the install directory (e.g. C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5 or /opt/VRTScmcm/webapp/). 3) Delete the entire ROOT5 folder (located at "C:\Program Files (x86)\Symantec\VRTScmcm\VRTSweb\admin\root5\ROOT5" or "/opt/VRTSweb/admin/root5"), including all its subdirectories. 4) Start the webserver. Note: ----- 1) If the connection between VCS MC and the cluster is broken at any point of time you will have to re-add the cluster using the "Discover/Add Clusters" wizard. 2) If adding pre-6.0 clusters to VCS MC fails during configuration, use the setuptrust command to establish a trust between the authentication brokers of the VCS MC machine and the cluster nodes and try re-adding the cluster. 3) If you upgrade any of your existing clusters in VCS MC to version 6.0, you will have to re-add the cluster using the "Discover/Add Clusters" after setuptrust. |
Why Register?
Get notifications about ASLs/APMs, HCLs, patches, and high availability agents
As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs in released versions, Array Support Libraries (ASLs)/Array Policy Modules (APMs), hardware compatibility lists (HCLs), patches and high availability agents. In addition, you can create system-specific notifications customized to your environment.
Compare configurations
The Compare Configurations feature lets you compare different system scans by the data collector. When you sign in, you can choose a target system, compare reports run at different times, and easily see how the system's configuration has changed.
Save configurations
After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. Anonymous users cannot access these features.
Bulk uploader
As a registered user,you can upload multiple reports, using the Bulk Uploader.