SFHA Solutions/InfoScale: How to clean up the operating system device tree
A device tree is a data structure that describes the LUNs in your environment. When you remove LUNs dynamically from an existing target ID, the operating system SCSI device tree must be cleaned up. This is to release the SCSI target ID for reuse if a new LUN is added to the host later. In Storage Foundation/InfoScale, there are two ways to do this: one if you are using Storage Foundation and High Availability (SFHA) version 6.0 or earlier you must clean up the device tree manually. In SFHA 6.0.1 and later, the device tree is cleaned up dynamically. For SFHA 6.0 and earlier For SFHA 6.0 and earlier, you need to clean up the operation system device tree manually after you remove LUNs from an existing target ID. To completely remove LUNs from an existing target ID, you need to perform the following steps: Remove LUNs. Clean up the operating system device tree. Scan the operating system device tree. The following diagram shows the process of removing LUNs dynamically from an existing target ID. For SFHA 6.0.1 and later, and InfoScale Since SFHA 6.0.1, the Dynamic Reconfiguration operations option (DR tool) is introduced in the vxdiskadm menu to simplify the removal of LUNs from an existing target ID. It saves the manual work of device scanning and cleaning up. Through the DR tool, Dynamic Multi-pathing (DMP) updates and cleans up the operating system device tree automatically. For more information about using DR tool to remove LUNs, please see: Removing LUNs dynamically from an existing target ID. The following diagram shows the process of using DR tool to remove LUNs dynamically from an existing target ID. The process is simplified by using this tool. Related links: Reconfiguring a LUN online that is under DMP control. (SFHA 6.0.1 and later) Reconfiguring a LUN online that is under DMP control. (SFHA 6.0 and earlier) The links in this article are specific to Linux platform. You can find SFHA Solutions/InfoScale documents for other versions and platforms on the SORT documents page.590Views0likes0CommentsVeritas InfoScale 7.0.1 (for AIX/Linux/Solaris): Documentation Available
The Veritas InfoScale 7.0.1 patch for AIX/Linux/Solaris is a maintenance-level release, which provides several updates on top of the InfoScale 7.0 products. The highlights of this release are: Upgrade bundled OpenSSL from 1.0.1m to 1.0.1p IPM protocol is no longer supported for CP server and InfoScale Availability clusters. The following platforms are newly supported: Linux: SLES11SP4 and RHEL6u7, OL 6u7 Solaris: Solaris10x64 is supported on InfoScale Availability Virtualization: VMware vSphere 6.0 u1 The documentation for Veritas InfoScale 7.0.1 is now available at the following locations: PDF and HTML versions: SORT documentation page Late Breaking News: http://www.symantec.com/docs/TECH230620 Hardware Compatibility List: http://www.symantec.com/docs/TECH230646 Software Compatibility List: http://www.symantec.com/docs/TECH230619513Views0likes0CommentsSymantec Dynamic Multi-Pathing 6.2 on VMware: Documentation Available
Documentation for Symantec Dynamic Multi-Pathing 6.2 on VMware is now available at the following locations: PDF and HTML versions: SORT documentation page HCL: http://www.symantec.com/docs/TECH211575 LBN: http://www.symantec.com/docs/TECH226775 The Symantec Dynamic Multi-Pathing 6.2 on VMware documentation set includes the following manuals: Symantec Dynamic Multi-Pathing Release Notes Symantec Dynamic Multi-Pathing Installation Guide Symantec Dynamic Multi-Pathing Administrator's Guide For information on how to use Symantec Dynamic Multi-Pathing 6.2 on VMware with the Storage Foundation High Availability Solutions 6.2 products, see Symantec Storage Foundation and High Availability Solutions Virtualization Guide – Linux on ESXi. You can also learn about the DMP on ESXi by taking up the course at LearnCentral- DMP 6.2 for VMware. Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.385Views0likes0CommentsVeritas Cluster Server 6.0 -- hauser -update
Dear All, I had added a new administrator user on vcs , like that, (#hauser -add clusteruser -pirv -Administrator ), but I cannot use the command (#hauser -update), because doesnt have that option, Do you know how can I get a password? I am trying using Veritas Cluster Manager Java Console to manage the cluster. I am using VCS 6.0 on RedHat Linux 6.1. Thanks in advance AlejandroSolved1.6KViews2likes4CommentsSFHA Solutions 6.0: How to Install Veritas SFHA Solutions 6.0 Products
Veritas Storage Foundation and High Availability (SFHA) Solutions 6.0 includes products such as DMP, SF, SFHA, SFCFSHA, SF Oracle RAC, SF Sybase CE, VCS, and VirtualStore. Got questions about downloading, licensing, or installing the SFHA Solutions 6.0 products? The following HOWTO articles provide an overview and guide you through the procedures: SFHA Solutions products 6.0 licensing About Veritas SFHA Solutions product licensing Setting or changing the Veritas SFHA Solutions product level for keyless licensing Installing Veritas SFHA Solutions product license keys How to install Veritas SFHA Solutions 6.0 products SFHA Solutions installation and configuration methods SFHA Solutions installation scripts SFHA Solutions product installer Downloading the SFHA Solutions software Mounting the SFHA Solutions product disc Setting the PATH and MANPATH environment variables Installing the SFHA Solutions products using the installer Installing language packages on Solaris systems846Views1like0CommentsSFHA Solutions 6.0: Use case for performing a rolling upgrade of an SF Oracle RAC global cluster
This HOWTO article describes the step-by-step process for performing a rolling upgrade of a Storage Foundation (SF) for Oracle RAC global cluster from 5.1 and later, to SF Oracle RAC 6.0. The strategy for performing a rolling upgrade on a two-node SF Oracle RAC global cluster includes the following: Phase 1: Split the cluster into two subclusters and upgrade the nodes on each subcluster. Phase 2: Upgrade all the nodes of the cluster on the site. http://www.symantec.com/docs/HOWTO64401712Views0likes0Comments