|
---|
Release type: | Patch |
Release date: | 2016-09-13 |
OS update support: | None |
Technote: | None |
Documentation: | None |
Popularity: | 480 viewed downloaded |
Download size: | 3.61 MB |
Checksum: | 4166611551 |
InfoScale Availability 7.1 On SLES11 x86-64
InfoScale Enterprise 7.1 On SLES11 x86-64 InfoScale Storage 7.1 On SLES11 x86-64 |
None.
|
3893802
|
VRTSgab-7.1.0.100-SLES11
|
* * * READ ME * * * * * * Veritas Group Membership and Atomic Broadcast 7.1 * * * * * * Patch 100 * * * Patch Date: 2016-09-07 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 Group Membership and Atomic Broadcast 7.1 Patch 100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- SLES11 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSgab BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * InfoScale Availability 7.1 * InfoScale Enterprise 7.1 * InfoScale Storage 7.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 7.1.0.100 * 3893802 (3893801) In some cases, when a node joins a large cluster, few GAB directed messages are delivered in the wrong order. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: 7.1.0.100 * 3893802 (Tracking ID: 3893801) SYMPTOM: In large clusters, a node join for a gab port gets stuck. DESCRIPTION: When a node joins a cluster, a few GAB directed messages might be delivered in the incorrect order to the GAB clients. This incorrect message order is because of a bug in code where the messages are added to the GAB delivery queue in incorrect order. RESOLUTION: The program is modified to ensure that during a node join scenario, the GAB directed messages are inserted in the various GAB queues in the correct order. INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- Please be noted that the installation of this P-Patch will cause downtime. To install the patch perform the following steps on at least one node in the cluster: 1. Copy the patch gab-sles11_x86_64-Patch-7.1.0.100.tar.gz to /tmp 2. Untar gab-sles11_x86_64-Patch-7.1.0.100.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/gab-sles11_x86_64-Patch-7.1.0.100.tar.gz # tar xf /tmp/gab-sles11_x86_64-Patch-7.1.0.100.tar 3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.) # pwd /tmp/hf # ./installVRTSgab710P100 [<host1> <host2>...] You can also install this patch together with 7.1 base release using Install Bundles 1. Download this patch and extract it to a directory 2. Change to the Veritas InfoScale 7.1 directory and invoke the installer script with -patch_path option where -patch_path should point to the patch directory # ./installer -patch_path [<path to this patch>] [<host1> <host2>...] Install the patch manually: -------------------------- Install the patch manually: -------------------------- Perform the following steps on all the nodes: 1. Take backup of your configurations 2. Stop VCS on all nodes 3. Install the patch 4. Restart VCS on Stopping VCS on all the cluster nodes -------------------------------- 1. Ensure that the "/opt/VRTSvcs/bin" directory is included in your PATH environment variable so that you can execute all the VCS commands. Refer to Veritas Cluster Server Installation Guide for more information. 2. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 3. If the cluster is writable, you may close the configuration before stopping the cluster. Stop the cluster: # haconf -dump -makero Run the following command to stop vcs on all nodes of the cluster: # hastop -all Verify that the cluster is stopped by running the ha command: # hasys -state Make sure that both had and hashadow processes are stopped. Also, stop the VCS CmdServer: # CmdServer -stop 4. Stop the cluster services in order: - For AMF: # /etc/init.d/amf stop - For VxFEN: # /etc/init.d/vxfen stop - For GAB: # /etc/init.d/gab stop Note: Stop any other services depending on GAB before stopping gab. Installing the Patch -------------------- 1. Un-compress the downloaded patch from Veritas and change the directory to the uncompressed patch location. Install the patch using the following command: - For GAB: # rpm -Uvh VRTSgab-7.1.0.100-SLES11.x86_64.rpm 2. Run the following command to verify if the new patch has been installed: - For GAB: # rpm -q VRTSgab If the proper patch is installed, the following output is displayed: - For GAB: VRTSgab-7.1.0.100-SLES11.x86_64 Re-starting the cluster services: -------------------------------- 1. To start the cluster services in order run the following command: - For GAB: # /etc/init.d/gab start - For VxFEN: # /etc/init.d/vxfen start - For AMF: # /etc/init.d/amf start - For VCS: # hastart # /opt/VRTSvcs/bin/CmdServer 2. Make VCS cluster writable: # haconf -makerw 3. Unfreeze all the groups: # hagrp -unfreeze [group] -persistent # haconf -dump -makero REMOVING THE PATCH ------------------ Removal of the patch will result in removing the whole package from the system/node. To go back to a previous installed version of the package, you may need to re-install the package. Run the following steps on the node where the patch is being uninstalled: To remove the patch from a cluster node: --------------------------------------------- 1. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 2. Stop VCS on the node by running the following command: - Follow the stop sequence as mentioned in the PATCH INSTALLATION section. 3. Remove the patch by using the following command: - For GAB: # rpm -e VRTSgab 4. Verify that the patch has been removed from the system: - For GAB: # rpm -qa|grep VRTSgab Ensure that the package is not be displayed. This confirms that the package is removed. 5. Install the relevant package from the VCS base media. Also refer to SORT for any applicable patches. 6. To start the cluster service, run the following command first on one node: - Follow the start sequence as mentioned in the PATCH INSTALLATION section. 7. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero 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.