|
---|
Release type: | Patch |
Release date: | 2017-11-16 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 677 viewed downloaded |
Download size: | 7.12 MB |
Checksum: | 1271408492 |
InfoScale Availability 7.1 On Windows x64
|
None.
|
3900172, 3904226, 3905743, 3909814, 3919626, 3929324
|
None.
|
* * * READ ME * * * * * * InfoScale Availability 7.1 * * * * * * Patch 100 * * * Patch Date: 2017-11-14 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 ---------- InfoScale Availability 7.1 Patch 100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Windows Server 2008 R2 X64 Windows 2012 X64 Windows Server 2012 R2 X64 BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Availability 7.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: IA 7.1 CP1 * 3900172 (3900171) The notifier process fails to work when a hostname is provided as the SNMPConsoles attribute value. * 3904226 (3904225) The NativeDisks agent crashes when Microsoft VDS API fails. * 3905743 (3905498) RegRepMonitor.exe keeps failing unexpectedly. * 3909814 (3890392) ISSUE 1: After every 49.7 days, VCS logs report that the GlobalCounter VCS attribute is not updated. ISSUE 2: WAC resource stops sending IAmAlive messages after a certain duration of time and reports the TCP/IP connection as unresponsive * 3929324 (3924750) Attempts to connect to a node using Java GUI fail if the node is in a remote cluster and is configured with a loopback or non-routable IP. * 3919626 (3918876) The NIC and IP agents cannot monitor the network adapter based on the GUID value. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: IA 7.1 CP1 * 3900172 (Tracking ID: 3900171) SYMPTOM: The notifier process fails to work when a hostname is provided as the SNMPConsoles attribute value. DESCRIPTION: When hostname is specified as SNMPConsole, notifier fails to send SNMP notifications to the SNMP console. RESOLUTION: This hotfix updates the notifier process so that it works as expected when a hostname is provided as the SNMPConsoles attribute value. FILE / VERSION: notifier.exe / 7.1.00001.169 * 3904226 (Tracking ID: 3904225) SYMPTOM: The NativeDisks agent crashes when Microsoft VDS API fails. DESCRIPTION: When Microsoft VDS API fails to execute successfully, it causes the NativeDisks agent to crash and restart multiple times. RESOLUTION: This hotfix updates the NativeDisks agent to appropriately handle errors when the Microsoft VDS API fails. If the API fails, NativeDisks agent changes the state of the resource to UNKNOWN. FILE / VERSION: NativeDisks.dll / 7.1.00002.169 * 3905743 (Tracking ID: 3905498) SYMPTOM: RegRepMonitor.exe keeps getting restarted if there is configuration issue. DESCRIPTION: When RegRepMonitor.exe keeps getting restarted, due to which the expected registry data does not get created at the configured location. This issue occurs when an incorrect registry key is specified in the configuration. RESOLUTION: The registry replication monitor is updated to handle the situation when certain types of incorrect registry keys are entered. FILE / VERSION: RegRepMonitor.exe / 7.1.3.169 * 3909814 (Tracking ID: 3890392) SYMPTOM: ISSUE 1: After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated. This error is reported on all nodes in the cluster, except the node with the lowest node ID value. The 'GloablCounter not updated' error also appears in the Event Viewer. ISSUE 2: WAC resource stops sending IAmAlive messages after a certain duration of time and reports the TCP/IP connection as hung. DESCRIPTION: ISSUE 1: The error indicates that there could be communication issues between the cluster nodes. VCS resets the GlobalCounter attribute every 49.7 days, but a delay might occur in synchronizing this change across all the cluster nodes. The error is reported if this delay occurs, but no communication issues actually occur. ISSUE 2: VCS incorrectly calculates the current time for a WAC resource due to the limitation of a Microsoft API (GetTickCount()). This current time is further used to control the sending of IAmAlive messages betweeen the WAC resources. Therefore, after a certain duration of time, the WAC resource stops sending IAmAlive messages to its peer and causes the connection to become unresponsive. RESOLUTION: ISSUE 1: This issue has been fixed by increasing the buffer size to hold the GlobalCounter attribute value, so that it does not need to be reset. ISSUE 2: This hotfix addresses the issue by correctly calculating the current time for a WAC resource using of a different API (GetTickCount64()). FILE / VERSION: had.exe/7.1.00004.169 hacf.exe/7.1.00004.169 wac.exe/7.1.00004.169 * 3929324 (Tracking ID: 3924750) SYMPTOM: Attempts to connect to a node using Java GUI fail if the node is in a remote cluster and is configured with a loopback or non-routable IP. DESCRIPTION: When a loopback adapter is configured on a remote cluster node, the VCS engine incorrectly returns the loopback IP address as the broker IP. Instead, it should return the IP address of the ethernet adapter that is used for remote access. RESOLUTION: The VCS engine has been updated so that it returns the correct IP address of a remote cluster node and lets you successfully connect to the node using Java GUI. FILE / VERSION: had.exe / 7.1.00005.169 hacf.exe / 7.1.00005.169 haconf.exe / 7.1.00005.169 * 3919626 (Tracking ID: 3918876) SYMPTOM: The NIC and IP agents cannot monitor the network adapter based on the GUID value. DESCRIPTION: Consider the following scenario about the public network used for a VCS cluster: - The NIC interface name is used for the MACAddress attribute on physical systems that use NIC teaming. - The NIC interface name is controlled by a tenant, and it may be changed for various reasons without knowing how it impacts VCS clusters. - It is not possible to enforce the use of a naming convention for the interface or to prevent a person or a system from renaming the NIC. To work around these limitations, it is necessary to be able to use the network adapter GUID to monitor the NIC and the IP resources. RESOLUTION: This hotfix addresses these limitations by updating the NIC and the IP agents to monitor the network adapter based on its GUID as well. You can now set the MACAddress attribute of the NIC and the IP agents to the GUID of the network adapter. The agents can then monitor the resource based on the GUID. In scenarios like the one mentioned earlier, you can use the GUID, instead of the interface name, to monitor the public network in a VCS cluster. FILE / VERSION: IP.dll / 7.1.00006.169 NIC.dll / 7.1.00006.169 INSTALLING THE PATCH -------------------- What's new in this CP =====================| The following hotfixes have been added in this CP: - Hotfix_7_1_00001_3900172 - Hotfix_7_1_00001_3904226 - Hotfix_7_1_00003_3905743 - Hotfix_7_1_00004_3909814 - Hotfix_7_1_00005_3929324 - Hotfix_7_1_00006_3919626 For more information about these hotfixes, see the "FIXED_INCIDENTS" section in this Readme. Note: Create the cluster before you install this CP. If you have already installed the CP before the cluster was created, then create the cluster and execute the C:\Program Files (x86)\Common Files\Veritas Shared\WxRTPrivates\Hotfix_6_1_00014_3820750\InstallVMwareDisksType.bat batch file. Install instructions ====================| Download the appropriate cumulative public patch (CP) executable file to a temporary location on your system. Note: You can install the CP directly on the host machine without downloading the executable file using the Veritas InfoScale Operations Manager (VIOM) Server Each cumulative public patch includes the individual hotfixes that contain enhancements and fixes related to reported issues. See the "FIXED_INCIDENTS" section for details. Before you begin ----------------: [1] Ensure that the logged-on user has privileges to install the CP on the systems. [2] One or more hotfixes that are included with this CP may require a reboot. Before proceeding with the installation ensure that the system can be rebooted. [3] Veritas recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this CP. [4] Ensure that you close the Windows Event Viewer before proceeding with the installation. [5] Before installing CP, ensure that the Startup type of the VCS Authentication Service is set to Automatic. This is applicable only if you have configured a secure cluster. [6] Ensure Veritas InfoScale Operations Manager server (VIOM) is deployed. [7] In case of installing the CP using Veritas InfoScale Operations Manager (VIOM) Server, ensure that the machines are be added as host on which you want to install the CP. To install the CP in the silent mode -----------------------------------: Perform the following steps: [1] Double-click the CP executable file to start the CP installation. The installer performs the following tasks: - Extracts all the individual hotfix executable files The files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName> - Runs the pre-install tasks - Installs all the hotfixes sequentially - Runs the post-install tasks The installation progress status is displayed in the command window. [2] After all the hotfixes are installed, the installer prompts you to restart the system. Type Y to restart the system immediately, or type N to restart the system later. You must restart the system for the changes to take effect. Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. To install the CP using the command line ----------------------------------------: Use the VxHFBatchInstaller.exe utility to install a CP from the command line. The syntax options for this utility are as follows: vxhfbatchinstaller.exe /Patch:<CPName> [/PreInstallScript:<PreInstallScript.pl>] [/silent [/forcerestart]] where, - CPName is the cumulative patch executable file name without the platform, architecture, and .exe extension. For example, if CP executable name is CP1_IA_71_W2K12_x64.exe, specify it as CP1_IA_71. - PreInstallScript.pl is the Perl script that includes the pre-installation steps. These steps forcefully kill the required services and processes in case a graceful stop request does not succeed. Veritas recommends that you use this option and script only in case the CP installer fails repeatedly while performing the pre-installation tasks. - /silent indicates the installation is run in a non-verbose mode; the installer does not prompt for any inputs during the installation. - /forcerestart indicates that the system is automatically restarted, if required, after the installation is complete. Perform the following steps: [1] From the command prompt, navigate to the directory where the CP executable file is located and then run the file to extract the contents to a default location on the system. The installer displays a list of hotfixes that are included in the CP. - On 64-bit systems, the hotfixes executable files are extracted to: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>" [2] In the same command window, run the following command to begin the CP installation in the silent mode: vxhfbatchinstaller.exe /Patch:<CPName> /silent For example, to install a IA 7.1 CP for Windows Server 2012, the command is: vxhfbatchinstaller.exe /Patch:CP1_IA_71 /silent The installer performs the following tasks: - Extracts all the individual hotfix executable files The files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName> - Runs the pre-install tasks - Installs all the hotfixes sequentially - Runs the post-install tasks The installation progress status is displayed in the command window. [3] After all the hotfixes are installed, the installer displays a message for restarting the system. You must restart the system for the changes to take effect. Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. The installer automatically restarts the system if you had specified the /forcerestart option in step 2 earlier. VxHFBatchInstaller usage example ---------------------------------: [+] Install CP in silent mode, restart automatically: vxhfbatchinstaller.exe /Patch:CP1_IA_71 /silent /forcerestart Known issues ============| There are no known issues identified in this CP. -------------------------------------------------------+ REMOVING THE PATCH ------------------ NO SPECIAL INSTRUCTIONS -------------------- This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Veritas disclaims all liability relating to or arising out of this fix. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into a Storage Foundation for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Veritas Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available if you sign up for notifications from the Veritas support site http://www.veritas.com/support and/or from Veritas Operations Readiness Tools (SORT) https://sort.Veritas.com. Additional notes ================| [+] To confirm the list of cumulative patches installed on a system, run the following command from the directory where the CP files are extracted: vxhfbatchinstaller.exe /list The output of this command displays a list of cumulative patches and the hotfixes that are installed as part of a CP. This command also displays the hotfixes that are included in a CP but are not installed on the system. [+] To confirm the installation of the hotfixes, perform one of the following: - Run the following command: vxhf.exe /list The output of this command lists the hotfixes installed on the system. - In the Windows Add/Remove program, click "View installed updates" to view the list of the hotfixes installed on the system. [+] To confirm the latest cumulative patch installed on a system, run the following command from the directory where the CP files are extracted: vxhfbatchinstaller.exe /patchlevel The output of this command displays the latest CP that is installed, the CP status, and a list of all hotfixes that were a part of the CP but not installed on the system. [+] The CP installer (vxhfbatchinstaller.exe) creates and stores logs at: "%allusersprofile%\Veritas\VxHF\VxHFBatchInstaller.txt" [+] The hotfix installer (vxhf.exe) creates and stores logs at: "%allusersprofile%\Veritas\VxHF\VxHF.txt" [+] For general information about the hotfix installer (vxhf.exe), please refer to the following technote: http://www.veritas.com/docs/000039694 [+] To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote: http://www.veritas.com/docs/000039691 [+] For information on uninstalling a hotfix, please refer to the following technotes: http://www.veritas.com/docs/000039693 [+] For general information about the CP installer (VxHFBatchInstaller.exe), please refer to the following technote: http://www.veritas.com/docs/000023795 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.