|
---|
Release type: | Hot Fix |
Release date: | 2016-02-29 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 275 viewed downloaded |
Download size: | 21.36 MB |
Checksum: | 2027710988 |
Risk Advisor 7.0.1 On Windows 64-bit
|
None.
|
3870148
|
None.
|
* * * READ ME * * * * * * Veritas Risk Advisor VRA_7.0.1 * * * * * * Patch 1 * * * Patch Date: 2016-02-29 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 * KNOWN ISSUES PATCH NAME ---------- Veritas Risk Advisor VRA_7.0.1 Patch 1 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Windows Server 2012 R2 X64 and IA64 Windows Server 2008 R2 X64 and IA64 BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Risk Advisor 7.0.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 7.0.1_HF1 * 3870148 (3870146) * IBM XIV cluster name collection issue * HP 3PAR volume not always identified during host scan * Incorrect IBM SVC replication direction * Security issue when using unsupported authentication method * Incorrect minimum number of LUN Maps SLA violation tickets * Unable to save Business Entity in specific circumstances * Report Scheduling GUI issue * Gap Id 301 accuracy issue * Scan troubleshooting may impact performance * Ticket symptoms module inconsistency * Agent disconnect may impact host scan * Agent master connection issue * Incorrect Agent scan file name * Agent housekeeping issue * Import from CMDB fails * Unable to delete worksheets in Comparison tab * Gap Id 392 may open non-impactful tickets * The Disks Set enrichment may fail * Gap Id 00251HSNA ticket accuracy issues * Gap Id 459 stability issue * Gap Id 301 ticket accuracy issue * Gap Id 444 may open non-impactful tickets * Gap Id 447 may open non-impactful tickets * Gap Id 430 ticket accuracy issue DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 7.0.1_HF1 * 3870148 (Tracking ID: 3870146) SYMPTOM: * IBM XIV cluster name collection issue * HP 3PAR volume not always identified during host scan * Incorrect IBM SVC replication direction * Security issue when using unsupported authentication method * Incorrect minimum number of LUN Maps SLA violation tickets * Unable to save Business Entity in specific circumstances * Report Scheduling GUI issue * Gap Id 301 accuracy issue * Scan troubleshooting may impact performance * Ticket symptoms module inconsistency * Agent disconnect may impact host scan * Agent master connection issue * Incorrect Agent scan file name * Agent housekeeping issue * Import from CMDB fails * Unable to delete worksheets in Comparison tab * Gap Id 392 may open non-impactful tickets * The Disks Set enrichment may fail * Gap Id 00251HSNA ticket accuracy issues * Gap Id 459 stability issue * Gap Id 301 ticket accuracy issue * Gap Id 444 may open non-impactful tickets * Gap Id 447 may open non-impactful tickets * Gap Id 430 ticket accuracy issue DESCRIPTION: * XIV mapping is not collected when the XIV host or cluster name contains white space. * In certain conditions, HP 3PAR volumes are not correctly identified during the host scan. * The source and target volumes of IBM SVC remote replication are not updated correctly after fail-over. * When unsupported Windows authentication method is used and scan fails, the password is printed in the log files. * Incorrect minimum number of LUN Maps SLA violation tickets opened for hosts using HP 3PAR LUNs. * Unable to save Business Entity when duplicate entities assigned to the Business Entity. * 'Add Report Task' doesn't work. * Gap Id 301 may open incorrect tickets regarding storage device inconsistency for volume groups suffering from partial replication. * The generation of the SAN PV Without HBA Performance scan troubleshooting message may lead to prolonged risk analysis. * Under specific circumstances, the system may fail to open individual symptoms. * Agent fails to perform subsequent scans if master-agent connection was disrupted during a scan (agent restart required). * Agent may occasionally fail to connect to the master server and require a restart. * Agent incorrectly names zipped scan files transferred to the master server. * Agent releases the space of deleted temporary files only upon service restart. * If the imported VM name is different than the hostname, then the system enters a duplicate entry in a database, thus failing the import process. * * Non-impactful Gap Id 392 (HBA configuration inconsistency) opened for unused HBAs. * The Disks Set enrichment fails while reporting an exception in the log file. * Occasionally false Gap Id 00251HSNA (Insufficient number of hot spare drives at NetApp) tickets are opened. * Gap Id 459 (Management VMotion Network Redundancy) may fail reporting an exception in the log file. * Gap Id 301 (Replica data inconsistency) may open incorrect tickets when the storage volumes of the reported VG/File System are partially replicated. * Gap Id 444 (Mounted CD-ROM on an HA protected VM) may open non-impactful tickets when the CD-ROM is not currently connected but set to be connected at boot. * Non-impactful Gap Id 447 (Suboptimal NFS MaxQueueDepth) tickets when SIOC is enabled. * 00430VMWCOI - False positive due to case sensitivity. RESOLUTION: Veritas has modified the code to resolve these issues. INSTALLING THE PATCH -------------------- 1. Download the patch VRA_7.0.1.1.exe and copy it to the master VRA server. 2. On the master VRA server, stop the VRA web server using the following steps: a. Open a command line window running with administrator privileges. b. Enter the following commands: # net stop TomcatWatchDog # net stop tomcat8 3. Locate the VRA folder. By default, it is in the path: C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 4. Make a copy of the VRA folder and store it in another location. (Do not store the copy under the tomcat tree.) The patch updates files in this folder, so if you need to revert to the unpatched version of VRA, you need the original folder. 5. Go to the folder where you downloaded the patch. Find VRA_7.0.1.1.exe and double-click it. 6. Follow the steps in the wizard to install the patch. 7. On the master VRA server, start the VRA web server using the following steps: a. Open a command line window running with administrator privileges. b. Enter the following commands: # net start tomcat8 # net start TomcatWatchDog 8. Login to VRA. 9. Verify that the build number is correct. On the VRA main screen, click About. The build number should be 39322. REMOVING THE PATCH ------------------ Veritas strongly recommends that you install the patch. However, if after installing it you need to revert to the unpatched version of VRA 7.0.1, use the following procedure: 1. Make sure you still have the backed up copy of the pre-patched, version 7.0.1 VRA folder 2. On the master VRA server, stop the VRA web server using the following steps: a. Open a command line window running with administrator privileges. b. Enter the following commands: # net stop TomcatWatchDog # net stop tomcat8 3. Locate the VRA folder. By default, it is in the path: C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\ 4. Delete the VRA folder 5. Copy the backed up folder to its original location. If you have changed the name of the copied folder, make sure to rename it to VRA . 6. On the master VRA server, start the VRA web server using the following steps: a. Open a command line window running with administrator privileges. b. Enter the following commands: # net start tomcat8 # net start TomcatWatchDog KNOWN ISSUES ------------ * Tracking ID: 3870162 SYMPTOM: No Symptom Found WORKAROUND: No WorkAround Found SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE |
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.