Veritas Access 7.2 Installation Guide : Linux

Veritas Access 7.2 Installation Guide : Linux
Veritas Access 7.2
Installation Guide
Linux
April 2017
Veritas Access Installation Guide
Last updated: 2017-04-17
Document version: 7.2 Rev 2
Legal Notice
Copyright © 2016 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, Veritas InfoScale, and NetBackup are trademarks or registered
trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other
names may be trademarks of their respective owners.
This product may contain third party software for which Veritas is required to provide attribution
to the third party (“Third Party Programs”). Some of the Third Party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the third party legal notices document accompanying this
Veritas product or available at:
https://www.veritas.com/about/legal/license-agreements
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS
SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043
http://www.veritas.com
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:
https://www.veritas.com/support
You can manage your Veritas account information at the following URL:
https://my.veritas.com
If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:
Worldwide (except Japan)
CustomerCare@veritas.com
Japan
CustomerCare_Japan@veritas.com
Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. The document version appears on page 2 of each
guide. The latest documentation is available on the Veritas website:
https://sort.veritas.com/documents
Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:
doc.feedback@veritas.com
You can also see documentation information or ask a question on the Veritas community site:
http://www.veritas.com/community/
Veritas Services and Operations Readiness Tools (SORT)
Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:
https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
Contents
Chapter 1
Introducing Veritas Access ............................................... 7
About Veritas Access ...................................................................... 7
Chapter 2
System requirements
....................................................... 10
Important release information ..........................................................
System requirements ....................................................................
Linux requirements .................................................................
Veritas InfoScale Operations Management Server requirements
.....................................................................................
Veritas InfoScale Operations Management Server Console
requirements ...................................................................
Management Server Web browser support ..................................
Supported NetBackup versions .................................................
Supported OpenStack versions .................................................
Supported Oracle versions and host operating systems ..................
Supported IP version 6 Internet standard protocol ........................
Network and firewall requirements ...................................................
NetBackup ports ....................................................................
CIFS protocols and firewall ports ..............................................
Maximum configuration limits ..........................................................
Chapter 3
10
10
11
17
17
17
18
18
19
19
19
22
22
23
Preparing to install Veritas Access ............................... 25
Overview of the installation process .................................................
Hardware requirements for the nodes ...............................................
About using LLT over the RDMA network for Veritas Access .................
RDMA over InfiniBand networks in the Veritas Access clustering
environment ....................................................................
How LLT supports RDMA for faster interconnections between
applications .....................................................................
Configuring LLT over RDMA for Veritas Access ............................
How the Veritas Access installer configures LLT over RDMA ...........
LLT over RDMA sample /etc/llttab ..............................................
Connecting the network hardware ...................................................
About obtaining IP addresses .........................................................
25
27
27
28
28
29
30
30
31
33
Contents
About calculating IP address requirements ........................................ 34
About checking the storage configuration .......................................... 37
Chapter 4
Installing and configuring a cluster
............................. 39
Installation overview ......................................................................
Summary of the installation steps ....................................................
Before you install ..........................................................................
Installing the operating system on each node of the cluster ...................
About the driver node ..............................................................
Installing the operating system on the target Veritas Access cluster
.....................................................................................
Registering your cluster to RHSM to get yum updates ....................
Configuring your own yum repository on each node of the cluster
.....................................................................................
Installing Veritas Access on the target cluster nodes ............................
Installing the required Red Hat Enterprise Linux operating system
RPMs ............................................................................
Installing and configuring the Veritas Access software on the
cluster ............................................................................
Veritas Access 7.2 Graphical User Interface (GUI) ........................
About NIC bonding and NIC exclusion ..............................................
Excluding a NIC .....................................................................
Including a NIC ......................................................................
Creating a new NIC bond .........................................................
Removing a NIC bond .............................................................
Removing a NIC from the bond list .............................................
Replacing an Ethernet interface card ................................................
Configuring I/O fencing ..................................................................
About configuring Veritas NetBackup ...............................................
About enabling kdump during an Veritas Access configuration ...............
Reconfiguring the Veritas Access cluster name and network .................
Chapter 5
39
40
41
42
42
43
45
46
47
47
48
54
55
56
60
62
68
71
73
74
75
75
76
Automating Veritas Access installation and
configuration using response files .......................... 78
About response files .....................................................................
Performing a silent Veritas Access installation ....................................
Response file variables to install and configure Veritas Access ..............
Sample response file for Veritas Access installation and configuration
...........................................................................................
78
79
79
88
5
Contents
Chapter 6
Displaying and adding nodes to a cluster .................. 92
About the Veritas Access installation states and conditions ................... 92
Displaying the nodes in the cluster ................................................... 93
Before adding new nodes in the cluster ............................................. 95
Adding a node to the cluster ........................................................... 97
Deleting a node from the cluster .................................................... 100
Shutting down the cluster nodes .................................................... 102
Chapter 7
Upgrading Veritas Access ............................................. 103
About types of Veritas Access patches ............................................
Downloading Veritas Access 7.2 release .........................................
Upgrading to Veritas Access 7.2 release ..........................................
About upgrading Veritas Access patches .........................................
Displaying the current version of Veritas Access ................................
Displaying upgrade history of Veritas Access ....................................
Downloading an Veritas Access patch release ..................................
Displaying all Veritas Access releases that are available in the
repository ............................................................................
About installing patches ...............................................................
Installing Veritas Access patches ...................................................
Automatically execute your customized script before or after upgrade
..........................................................................................
Uninstalling patches ....................................................................
Synchronizing software upgrades on a node ....................................
Chapter 8
Uninstalling Veritas Access
Installation reference
107
108
108
114
115
115
.......................................... 116
Before you uninstall Veritas Access ................................................
Uninstalling Veritas Access using the installer ...................................
Removing Veritas Access 7.2 RPMs .........................................
Running uninstall from the Veritas Access 7.2 disc ......................
Appendix A
103
104
105
105
106
106
106
116
118
118
119
...................................................... 120
Installation script options .............................................................. 120
Appendix B
Configuring the secure shell for communications
.......................................................................................... 122
Manually configuring passwordless secure shell (ssh) ........................ 122
Setting up ssh and rsh connection using the pwdutil.pl utility ................ 125
Index
.................................................................................................................. 130
6
Chapter
1
Introducing Veritas Access
This chapter includes the following topics:
■
About Veritas Access
About Veritas Access
Veritas Access is a software-defined scale-out network-attached storage (NAS)
solution for unstructured data that works on commodity hardware. Veritas Access
provides resiliency, multi-protocol access, and data movement to and from the
public cloud based on policies.
Table 1-1 describes the features of Veritas Access.
Table 1-1
Veritas Access key features
Feature
Description
Simple administration
through a CLI or a GUI
interface
CLI interface that provides a single point of administration for the
entire cluster.
Multi-protocol access
Veritas Access includes support for the following protocols:
GUI interface that provides a centralized dashboard with operations
for creating file systems, shares, and storage pools.
■
Amazon S3
■
CIFS
■
FTP
■
NFS
■
Oracle Direct NFS
■
SMB 3
Flexible Storage Sharing Enables cluster-wide network sharing of local storage.
(FSS)
Introducing Veritas Access
About Veritas Access
Table 1-1
Veritas Access key features (continued)
Feature
Description
Scale-out file system
The following functionality is provided for a scale-out file system:
■
File system that manages a single namespace spanning over
both on-premises storage as well as cloud storage, which
provides better fault tolerance for large data sets.
■
Highly available NFS shares.
Cloud as a tier for a
scale-out file system
Veritas Access supports adding a cloud service as a storage tier
for a scale-out file system. You can move data between the tiers
based on file name patterns and when the files were last accessed
or modified. Use scheduled policies to move data between the
tiers on a regular basis.
SmartIO
Veritas Access supports read caching on solid state drives (SSDs)
for applications running on Veritas Access file systems.
SmartTier
Veritas Access's built-in SmartTier feature can reduce the cost of
storage by moving data to lower-cost storage. Veritas Access
storage tiering also facilitates the moving of data between different
drive architectures.
Replication
Periodic replication of data over IP networks.
Snapshot
Veritas Access supports snapshots for recovering from data
corruption. If files, or an entire file system, are deleted or become
corrupted, you can replace them from the latest uncorrupted
snapshot.
Deduplication
You can run post-process periodic deduplication in a file system,
which eliminates duplicate data without any continuous cost.
Compression
You can compress files to reduce the space used, while retaining
the accessibility of the files and having the compression be
transparent to applications. Compressed files look and behave
almost exactly like uncompressed files: the compressed files have
the same name, and can be read and written as with
uncompressed files.
NetBackup integration
Built-in NetBackup client for backing up your file systems to a
NetBackup master or media server. Once data is backed up, a
storage administrator can delete unwanted data from Veritas
Access to free up expensive primary storage for more data.
8
Introducing Veritas Access
About Veritas Access
Table 1-1
Veritas Access key features (continued)
Feature
Description
OpenStack plug-in
Integration with OpenStack:
■
OpenStack Cinder integration that allows OpenStack instances
to use the storage hosted by Veritas Access.
■
OpenStack Manila integration that lets you share Veritas
Access file systems with virtual machines on OpenStack
Manila.
Quotas
Support for setting file system quotas, user quotas, and hard
quotas.
Support for LDAP, NIS,
and AD
Veritas Access uses the Lightweight Directory Access Protocol
(LDAP) for user authentication.
Partition Directory
With support for partitioned directories, directory entries are
redistributed into various hash directories. These hash directories
are not visible in the name-space view of the user or operating
system. For every new create, delete, or lookup, this feature
performs a lookup for the respective hashed directory and performs
the operation in that directory. This leaves the parent directory
inode and its other hash directories unobstructed for access, which
vastly improves file system performance.
By default this feature is not enabled. See the storage_fs(1)
manual page to enable this feature.
Isolated storage pools
Enables you to create an isolated storage pool, which contains its
own configuration files. An isolated storage pool protects the pool
from losing the associated metadata if a disk in another storage
pool fails.
Performance and tuning Workload-based tuning for the following workloads:
■
Media server
■
Virtual machine
9
Chapter
2
System requirements
This chapter includes the following topics:
■
Important release information
■
System requirements
■
Network and firewall requirements
■
Maximum configuration limits
Important release information
Review the Veritas Access Release Notes for the latest information before you
install the product.
The hardware compatibility list contains information about supported hardware and
is updated regularly. You can use any commodity hardware that is certified and
mentioned in the hardware compatibility list. For the latest information on supported
hardware, visit the following URL:
http://www.veritas.com/docs/000019707
For important updates regarding this release, review the Late-Breaking News
TechNote on the Veritas Technical Support website:
http://www.veritas.com/docs/000116052
System requirements
Table 2-1 lists the per-node system requirements for running the Veritas Access
system software.
System requirements
System requirements
Table 2-1
System requirements for Veritas Access
Minimum
Recommended
Each Veritas Access node using a Two nodes of dual or quad core processors at 2.0 GHz
64-bit Intel-based server
or above for optimal performance.
architecture that is compatible with
Redhat Enterprise Linux 6 Update
6 and Update 7 for AMD64 and
Intel EMT. Itanium is not
supported.
32 GB error-correcting code (ECC) The recommended values depend on the expected
random-access memory (RAM).
workload.
One internal drive with size equal
to size of RAM + 60GB.
Dual drivers each with size of RAM + 60GB or more
capacity. In the FSS-based environment, more number
of the internal drives (SSD + HDD) are recommended.
Two gigabit Ethernet interfaces
Embedded Ethernet interfaces are recommended.
Two additional gigabit Ethernet
N/A
interfaces (embedded or Ethernet
adapters for the peripheral
component interconnect (PCI)
bus).
One Fibre Channel Host Bus
Adapters (HBA).
Two Fibre Channel Host Bus Adapters (HBAs) are
recommended, but only one is required. Having only
one Fibre Channel HBA enables all the operations of
the Fibre Channel (except high availability).
Internal/external USB DVD-ROM
DVD drive.
N/A
Redundant power supply.
Recommended, but not required.
SmartIO caching feature
Recommended to have a PCI based SSD card if you
want to use the SmartIO caching feature.
Linux requirements
Veritas does not support any operating systems on which Veritas Access runs.
There are strict operating system versioning requirements for each release of Veritas
Access.
The Veritas Access 7.2 release requires Red Hat Enterprise Linux. It supports both
RHEL 6 Update 6 and RHEL 6 Update 7. The minimum operating system
requirements are enforced during the Veritas Access installation. A Kickstart file is
11
System requirements
System requirements
also available on request for Veritas Access 7.2 to assist partners with the operating
system installation requirements. Operating system patches, including security
vulnerability patches, can be installed without requiring certification from Veritas.
However, operating system Kernel RPMs should not be patched without specific
approval from Veritas.
The certification of the Red Hat Enterprise Linux (RHEL) operating system updates
can require a new minor version of Veritas Access. RHEL operating system updates
cannot be installed without prior agreement with Veritas.
Veritas Access can be integrated into a network that consists of computers running
the following:
Requirement
Version
Version
Red Hat
RHEL 6 Update 6
Enterprise Linux
version
RHEL 6 Update 7
Kernel version
2.6.32-504.el6
2.6.32-573.el6
See “Kernel RPMs that are required
to be installed with exact predefined
RPM versions” on page 13.
See “Kernel RPMs that are
required to be installed with exact
predefined RPM versions”
on page 13.
See “Required Red Hat Enterprise
Linux operating system RPMs for
RHEL 6.6” on page 14.
See “Required Red Hat Enterprise
Linux operating system RPMs for
RHEL 6.7” on page 15.
Other required
RPMs
Operating system RPM installation requirements and
operating system patching limitations
Veritas has categorized the operating system RPMs that are required before you
install Veritas Access into four groups:
Category 1
■
This set of RPMs are kernel RPMs that are required to be installed with exact
predefined RPM versions only.
■
The required RPM versions are different for RHEL6.6 and RHEL6.7.
■
The RPMs in this category should not be patched without specific approval from
Veritas.
■
See “Kernel RPMs that are required to be installed with exact predefined RPM
versions” on page 13.
Category 2
12
System requirements
System requirements
■
This set of RPMs include the OS libs and OS packages that must be installed
with minimum predefined RPM versions.
■
The required RPM versions are different for RHEL6.6 and RHEL6.7.
■
The RPMs in this category can be patched using official Red Hat patches.
■
An approval or certification from Veritas is not required to patch these RPMs.
■
See “Required Red Hat Enterprise Linux operating system RPMs for RHEL 6.6”
on page 14.
■
See “Required Red Hat Enterprise Linux operating system RPMs for RHEL 6.7”
on page 15.
Category 3
■
This set of RPMs are required by Category 2 RPMs as dependencies, their
installation is enforced by Red Hat.
■
Veritas Access does not require any specific versions of these RPMs to be
installed.
■
The versions of these RPMs are determined by Red Hat.
■
The RPMs in this category can be patched using official Red Hat patches.
■
An approval or certification from Veritas is not required to patch these RPMs.
■
Veritas does not document these RPMs as required RPMs for Veritas Access.
Category 4
■
This set of RPMs are third-party RPMs that are included in the Veritas Access
ISO.
■
These RPMs are not operating system RPMs. It includes Samba, Ganesha,
and other third party products.
■
The RPMs in this category should not be patched without specific approval from
Veritas.
■
Veritas installs these RPMs as they are included in the Veritas Access ISO.
Kernel RPMs that are required to be installed with exact
predefined RPM versions
After you install Red Hat Enterprise Linux operating system, install the following
RPMs and then restart the system. Use the specified links to download the RPMs
from the Red Hat site. The links require a Red Hat registration ID (user name and
password).
The RHEL 6 Update 6 kernel packages:
13
System requirements
System requirements
■
kernel-2.6.32-504.el6.x86_64
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1006010
■
kernel-debuginfo-2.6.32-504.el6.x86_64.rpm
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1005367
■
kernel-debuginfo-common-x86_64-2.6.32-504.el6.x86_64.rpm
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1006274
■
kernel-headers-2.6.32-504.el6.x86_64.rpm
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1006768
■
kernel-firmware-2.6.32-504.el6.noarch.rpm
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1005320
The RHEL 6 Update 7 kernel packages:
■
kernel-2.6.32-573.el6.x86_64
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1072387.
■
kernel-debuginfo-2.6.32-573.18.1.el6.x86_64
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1072442
■
kernel-debuginfo-common-x86_64-2.6.32-573.18.1.el6.x86_64
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1072385
■
kernel-firmware-2.6.32-573.el6.noarch
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1012920
■
kernel-headers-2.6.32-573.el6.x86_64
https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=1072371
Required Red Hat Enterprise Linux operating system RPMs
for RHEL 6.6
The RPM version numbers specified in these lists are the minimum required version
numbers for these operating system RPMs.
Required OS lib rpms for RHEL6.6:
coreutils-8.4-37.el6.x86_64
findutils-4.4.2-6.el6.x86_64
glibc-2.12-1.166.el6_7.7.x86_64
ed-1.1-3.3.el6.x86_64
glibc-2.12-1.166.el6_7.7.i686
ksh-20120801-21.el6.x86_64
libacl-2.2.49-6.el6.x86_64
libgcc-4.4.7-11.el6.x86_64
libstdc++-4.4.7-11.el6.x86_64
mksh-39-9.el6_4.1.x86_64
ncurses-libs-5.7-3.20090208.el6.x86_64
openssl-1.0.1e-48.el6_8.1.x86_64
perl-5.10.1-136.el6.x86_64
libgcc-4.4.7-11.el6.i686
libstdc++-4.4.7-11.el6.i686
libudev-147-2.57.el6.i686
module-init-tools-3.9-24.el6_4.x86_64
nss-softokn-freebl-3.14.3-17.el6.i686
parted-2.1-25.el6.x86_64
policycoreutils-2.0.83-19.47.el6.x86_64
14
System requirements
System requirements
readline-6.0-4.el6.x86_64
Required OS packages for RHEL6.6:
apr-devel 1.3.9-5.el6_2
apr-util-devel 1.3.9-3.el6_0.1
bash 4.1.2-29.el6
glibc-common 2.12-1.166.el6_7.7
glibc-devel.x86_64 2.12-1.166.el6_7.7
glibc-headers 2.12-1.166.el6_7.7
glibc-utils 2.12-1.166.el6_7.7
glibc.i686 2.12-1.166.el6_7.7
glibc.x86_64 2.12-1.166.el6_7.7
hal 0.5.14-14.el6
httpd 2.2.15-54.el6_8
httpd-devel 2.2.15-54.el6_8
httpd-manual 2.2.15-54.el6_8
httpd-tools 2.2.15-54.el6_8
infiniband-diags 1.0.0
iscsi-initiator-utils 6.2.0.873-13.el6
libibumad 1.3.9-1.el6
libibverbs-devel 1.1.8-3.el6
libibverbs-utils 1.1.8-3.el6
libpcap 1.4.0
libtirpc 0.2.1-10.el6
libyaml 0.1.3-4
lsscsi 0.23
memcached 1.4.4-3.el6
mod_ssl 2.2.15-39.el6_5
mod_wsgi 3.2-7.el6
nc 1.84-22.el6
net-snmp 5.5-49.el6
net-snmp-libs 5.5-49.el6
net-snmp-utils 5.5-49.el6
nfs-utils 1.2.3-54.el6
nscd 2.12-1.166.el6_7.7
nss-pam-ldapd 0.7.5-18.2.el6_4
openldap 2.4.39-8.el6
openldap-clients 2.4.39-8.el6
opensm 3.3.5
opensm-libs 3.3.5
openssh 5.3p1-111.el6
openssh-askpass 5.3p1-111.el6
openssh-clients 5.3p1-111.el6
openssh-server 5.3p1-111.el6
openssl 1.0.1e-48.el6_8.1
openssl-devel 1.0.1e-48.el6_8.1
perl 5.10.1
perl-Net-Telnet 3.03
python-backports 1.0-5.el6
python-backports-ssl_match_hostname 3.4.0.2-2.el6
python-chardet 2.2.1-1.el6
python-memcached 1.43-6.el6
python-paramiko 1.7.5-2.1.el6
python-requests 2.6.0-3.el6
python-six 1.9.0-2.el6
python-urllib3 1.10.2-1.el6
rdma 1.0
rrdtool 1.3.8-7.el6
sg3_utils 1.28-6.el6
sg3_utils-libs 1.28-6.el6
sysstat 9.0.4-27.el6
telnet 0.17-48.el6
vsftpd 2.2.2-12.el6
wireshark 1.8.10-7.el6
Required Red Hat Enterprise Linux operating system RPMs
for RHEL 6.7
The RPM versions numbers specified in these lists are the minimum required version
numbers for these operating system RPMs.
Required OS lib rpms for RHEL6.7:
coreutils-8.4-37.el6.x86_64
findutils-4.4.2-6.el6.x86_64
ed-1.1-3.3.el6.x86_64
glibc-2.12-1.166.el6_7.7.i686
15
System requirements
System requirements
glibc-2.12-1.166.el6_7.7.x86_64
libacl-2.2.49-6.el6.x86_64
libgcc-4.4.7-16.el6.x86_64
libstdc++-4.4.7-16.el6.x86_64
mksh-39-9.el6.x86_64
module-init-tools-3.9-25.el6.x86_64
nss-softokn-freebl-3.14.3-22.el6_6.i686
parted-2.1-29.el6.x86_64
policycoreutils-2.0.83-24.el6.x86_64
ksh-20120801-28.el6.x86_64
libgcc-4.4.7-16.el6.i686
libstdc++-4.4.7-16.el6.i686
libudev-147-2.63.el6.i686
mksh-39-9.el6_4.1.x86_64
ncurses-libs-5.7-4.20090207.el6.x86_64
openssl-1.0.1e-48.el6_8.1.x86_64
perl-5.10.1-141.el6.x86_64
readline-6.0-4.el6.x86_64
Required OS packages for RHEL6.7:
apr-devel 1.3.9-5.el6_2
apr-util-devel 1.3.9-3.el6_0.1
bash 4.1.2-33.el6
glibc-common 2.12-1.166.el6_7.7
glibc-devel.x86_64 2.12-1.166.el6_7.7
glibc-headers 2.12-1.166.el6_7.7
glibc-utils 2.12-1.166.el6_7.7
glibc.i686 2.12-1.166.el6_7.7
glibc.x86_64 2.12-1.166.el6_7.7
hal 0.5.14-14.el6
httpd 2.2.15-54.el6_8
httpd-devel 2.2.15-54.el6_8
httpd-manual 2.2.15-54.el6_8
httpd-tools 2.2.15-54.el6_8
infiniband-diags 1.0.0
iscsi-initiator-utils 6.2.0.873-14.el6
libibumad 1.3.9-1.el6
libibverbs-devel 1.1.8-4.el6
libibverbs-utils 1.1.8-4.el6
libpcap 1.4.0
libtirpc 0.2.1-10.el6
libyaml 0.1.3-4
lsscsi 0.23
memcached 1.4.4-3.el6
mod_ssl 2.2.15-45.el6
mod_wsgi 3.2-7.el6
nc 1.84-24.el6
net-snmp 5.5-54.el6
net-snmp-libs 5.5-54.el6
net-snmp-utils 5.5-54.el6
nfs-utils 1.2.3-64.el6
nscd 2.12-1.166.el6_7.7
nss-pam-ldapd 0.7.5-20.el6_6.3
openldap 2.4.40-5.el6
openldap-clients 2.4.40-5.el6
opensm 3.3.17-1.el6
opensm-libs 3.3.17-1.el6
openssl 1.0.1e-48.el6_8.1
openssl-devel 1.0.1e-48.el6_8.1
perl 5.10.1
perl-Net-Telnet 3.03
python-backports 1.0-5.el6
python-backports-ssl_match_hostname 3.4.0.2-2.el6
python-chardet 2.2.1-1.el6
python-memcached 1.43-6.el6
python-paramiko 1.7.5-2.1.el6
python-requests 2.6.0-3.el6
python-six 1.9.0-2.el6
python-urllib3 1.10.2-1.el6
rdma 1.0
rrdtool 1.3.8-7.el6
sg3_utils 1.28-8.el6
sg3_utils-libs 1.28-8.el6
sysstat 9.0.4-27.el6
telnet 0.17-48.el6
vsftpd 2.2.2-14.el6
wireshark 1.8.10-17.el6
16
System requirements
System requirements
Veritas InfoScale Operations Management Server requirements
This section lists the amount of CPU cores, memory, and disk space that Veritas
InfoScale Operation Manager requires.
Table 2-2
For a management server
Environment Size
CPU cores
Memory
Disk space
Small (up to 300 managed hosts)
4
4 GB
5 GB
Medium (up to 1500 managed hosts)
8
16 GB
20 GB
Large (up to 3500 managed hosts)
16
32 GB
40 GB
Table 2-3
For a managed host
CPU cores
Memory
Disk space
1
1 GB
2 GB
Veritas InfoScale Operations Management Server Console
requirements
Veritas Access Add-on is supported only on the Linux platform.
Management Server Web browser support
The following are the supported Web browsers for Veritas Access:
Table 2-4
Browser
Version
Internet Explorer
■
IE 8
JavaScript: Enabled
■
IE 9
Cookies: Enabled
■
IE 10
■
IE 11
FireFox
FireFox 4.x and later
Comments
JavaScript: Enabled
Cookies: Enabled
Chrome
Chrome 10 and later version JavaScript: Enabled
Cookies: Enabled
Additional considerations for supported Web browsers:
17
System requirements
System requirements
■
Your browser must support JavaScript 1.2, or later.
■
If you use pop-up blockers (including Yahoo Toolbar or Google Toolbar), either
disable them or configure them to accept pop-ups from the Veritas Infoscale
Operations Manager Web server to which you connect.
■
For Internet Explorer 8.0 on Windows Server 2003, download and install the
hot fix from the following location:
http://support.microsoft.com/kb/938397/en-gb
■
If you are unable to download the gendeploy script using Internet Explorer 9.0,
visit the following location to resolve the issue:
http://support.microsoft.com/kb/2549423
■
For Internet Explorer, enable the play animations in web pages option in the
multimedia category of Advanced Internet options.
■
For Internet Explorer, when popup-blocker is turned on, make sure that the filter
Level is set to Medium or lower.
■
For Internet Explorer, ensure that the site is included in the list of trusted sites.
■
If you cannot add the site to the list of trusted sites, enable the Binary and script
Behaviors option in security settings.
■
You must install Adobe Flash plug-in version 10, or later.
Supported NetBackup versions
Veritas Access supports NetBackup versions 7.6 and 7.7.
Supported OpenStack versions
The OpenStack drivers, Cinder and Manila, are supported on the Red Hat Enterprise
Linux (RHEL) 7 OS and the OpenStack Kilo release.
The Cinder and Manila drivers were tested with the following:
■
OpenStack Kilo version from the DevStack repository
■
OpenStack RDO
Note: The Manila driver works only with kernel NFS. It will not work with
NFS-Ganesha.
18
System requirements
Network and firewall requirements
Supported Oracle versions and host operating systems
Veritas Access supports Oracle using Direct NFS. Veritas Access Direct NFS
supports only NFS protocol version 3.
Veritas Access supports Oracle single instance only. OracleRAC is not supported.
The following are the supported Oracle versions for Veritas Access:
■
Oracle version 11gR2 (11.2.0.4 or above)
■
Oracle 12c (12.1.0.1)
The following are the supported Oracle host operating systems in the order of
importance for Veritas Access:
■
Linux
■
AIX
■
Solaris
■
HP-UX
■
Oracle Linux
Supported IP version 6 Internet standard protocol
Table 2-5 describes the IP version 6 (IPv6) Internet standard protocol.
Table 2-5
IPv6 Internet standard protocol
Description
Example format
Preferred form
ABCD:EF01:2345:6789:ABCD:EF01:2345:6789
Compressed form
FF01::101
Mixed form
0:0:0:0:0:FFFF:129.144.52.38
Network and firewall requirements
Table 2-6 displays the default ports that Veritas Access uses to transfer information.
19
System requirements
Network and firewall requirements
Table 2-6
Default Veritas Access ports
Port
Protocol or
Service
Purpose
Impact if blocked
21
FTP
Port where the FTP
server listens for
connections.
FTP features are
blocked.
Note: Users can
configure another port
if desired.
22
SSH
Secure access to the Veritas Access is not
Veritas Access server accessible.
25
SMTP
Sending SMTP
messages.
The SMTP messages
that are sent from
Veritas Access are
blocked.
53
DNS queries
Communication with
the DNS server
Domain name
mapping fails.
111
rpcbind
RPC portmapper
services
RPC services fail.
123
NTP
Communication with
the NTP server
Server clocks are not
synchronized across
the cluster.
NTP-reliant features
(such as DAR) are
not available.
139
CIFS
CIFS client to server
communication
CIFS clients cannot
access the Veritas
Access cluster
161
SNMP
Sending SNMP alerts SNMP alerts cannot
be broadcast.
445
CIFS
CIFS client to server
communication
CIFS clients cannot
access the Veritas
Access cluster.
514
syslog
Logging program
messages
Syslog messages are
not recorded.
20
System requirements
Network and firewall requirements
Table 2-6
Default Veritas Access ports (continued)
Port
Protocol or
Service
Purpose
Impact if blocked
756, 757, 755
statd
NFS statd port
NFS v3 protocol
cannot function
correctly.
2049
NFS
NFS client to server
communication
NFS clients cannot
access the Veritas
Access cluster.
3172, 3173
ServerView
ServerView port
ServerView cannot
work.
4001
mountd
NFS mount protocol
NFS clients cannot
mount file systems in
the Veritas Access
cluster.
4045
lockd
Processes the lock
requests
File locking services
are not available.
5634
HTTPS
Management Server
connectivity
Web GUI may not be
accessible.
56987
Replication
File synchronization,
Veritas Access
replication
Veritas Access
replication daemon is
blocked. Replication
cannot work.
8088
REST server
REST client to server REST client cannot
communication
access REST API of
Veritas Access.
11211
Memcached port
CLISH framework
CLISH cannot
function correctly, and
cluster configuration
may get corrupted.
30000:4000
FTP
FTP passive port
FTP passive mode
fails.
14161
HTTPS
Access Veritas
Access GUI
User is unable to
access Veritas
Access GUI
51001
UDP
LLT over RDMA
LLT is not working.
21
System requirements
Network and firewall requirements
Table 2-6
Default Veritas Access ports (continued)
Port
Protocol or
Service
Purpose
Impact if blocked
51002
UDP
LLT over RDMA
LLT is not working.
NetBackup ports
NetBackup uses TCP/IP connections to communicate between one or more TCP/IP
ports. Depending on the type of operation and configuration on the environment,
different ports are required to enable the connections. NetBackup has different
requirements for operations such as backup, restore, and administration.
Table 2-7 shows some of the most-common TCP and UDP ports that Veritas Access
NetBackup uses to transfer information. For more information, see the NetBackup
Security and Encryption Guide.
Table 2-7
Default NetBackup TCP and UDP ports
Port Range
Protocol
1556
TCP, UDP
13701-13702, 13705-13706
TCP
13711, 13713, 13715-13717, 13719
TCP
13720-13722
TCP, UDP
13723
TCP
13724
TCP, UDP
13782-13783
TCP, UDP
13785
TCP
CIFS protocols and firewall ports
For the CIFS service to work properly in an Active Directory (AD) domain
environment, the following protocols and firewall ports need be allowed or opened
to enable the CIFS server to communicate smoothly with Active Directory Domain
Controllers and Windows/CIFS clients.
Internet Control Message Protocol (ICMP) protocol must be allowed through the
firewall from the CIFS server to the domain controllers. Enable "Allow incoming
echo request" is required for running the CIFS service.
22
System requirements
Maximum configuration limits
Table 2-8 lists additional CIFS ports and protocols.
Table 2-8
Additional CIFS ports and protocols
Port
Protocol
Purpose
53
TCP, UDP
DNS
88
TCP, UDP
Kerberos
139
TCP
DFSN, NetBIOS Session Service, NetLog
445
TCP, UDP
SMB, CIFS, SMB2, DFSN, LSARPC, NbtSS,
NetLogonR, SamR, SrvSvc
464
TCP, UDP
Kerberos change or set a password
3268
TCP
LDAP GC
4379
TCP
CTDB in CIFS
Table 2-9 lists the ports that are required for LDAP with SSL.
Table 2-9
LDAP with SSL ports
Port
Protocol
Purpose
636
TCP
LDAP SSL
3269
TCP
LDAP GC SSL
Maximum configuration limits
The maximum configuration limits for configuring the Veritas Access system software
are as follows:
Table 2-10
Maximum configuration limits
Veritas Access
system software
Configuration limit
File system size
512 TB
Veritas Access nodes
16
Note: Flexible Storage Sharing (FSS) only supports cluster
configurations with up to 8 nodes.
23
System requirements
Maximum configuration limits
Table 2-10
Maximum configuration limits (continued)
Veritas Access
system software
Configuration limit
Supported LUNs
The maximum number of disks is theoretically limited to the number
that can be attached to the operating system. However, it has only
be tested in the thousands.
Supported file systems
500
Tiers within a file system 2 (primary tier and secondary tier)
24
Chapter
3
Preparing to install Veritas
Access
This chapter includes the following topics:
■
Overview of the installation process
■
Hardware requirements for the nodes
■
About using LLT over the RDMA network for Veritas Access
■
Connecting the network hardware
■
About obtaining IP addresses
■
About calculating IP address requirements
■
About checking the storage configuration
Overview of the installation process
The Veritas Access cluster is a set of connected servers called "nodes." Together
these nodes form a unified entity called a cluster.
Figure 3-1 shows an example of an Veritas Access cluster.
Preparing to install Veritas Access
Overview of the installation process
Figure 3-1
Sample of Veritas Access cluster overview
Client
Client
Public network
eth0 eth3
eth0 eth3
eth1
eth1
Node 2
Node 1
Private network
eth2
eth2
Fibre channel switch
Storage array
Note: The NIC names mentioned in Figure 3-1 are only for examples. You need
to determine the usage of your NICs during the installation.
An overview of the Veritas Access software installation includes the following steps:
■
Gather network information from your network administrator.
■
Connect your network hardware.
■
Install the operating system on each of the nodes.
■
Install Veritas Access on the node. If the driver node is one of the nodes of the
cluster, you must start the installer from the console of the node. If the driver
node is not part of the cluster, the installer can be run from the driver node to
install and configure the cluster over an ssh connection.
From the Veritas Access 7.2 release, the installer can be run from any node of
the cluster.
See “Installing and configuring the Veritas Access software on the cluster”
on page 48.
See “About the driver node” on page 42.
26
Preparing to install Veritas Access
Hardware requirements for the nodes
■
Run the installation and configuration on the node to configure the entire cluster.
Installation times may vary depending on your configuration.
Hardware requirements for the nodes
The following table summarizes the hardware requirements for each node.
Table 3-1
Hardware requirements for the nodes
Item
Requirements
Network interface card
(NIC)
At least four NICs are required for each node.
Two NICs connected to a private network.
■
■
For a two-node cluster, either cross connect two private NICs
on each node or use a switch.
If there are more than two nodes in the cluster, make sure that
you have a dedicated switch (or a public or private switch with
a dedicated VLAN) and that all the private NICs are connected
to the switch.
Connect two public NICs from each node to the public network.
The gateway must be reachable to each public NIC.
IP address
For a two-node cluster, make sure that you have nine IP addresses
available.
■
Four IP addresses are used to configure physical IPs.
■
Four IP addresses are used to configure virtual IPs.
■
One IP address is used to configure the Veritas InfoScale
Operations Manager console.
One IP address is used for replication, which is optional.
■
Make sure that these nine IP addresses are different from the IP
addresses that are already assigned to the target cluster nodes
to install Veritas Access over Secure Shell (ssh).
About using LLT over the RDMA network for
Veritas Access
Remote direct memory access (RDMA) allows server-to-server data movement
directly between application memories with minimal CPU involvement. RDMA
provides fast interconnection between user-space applications or file systems
between nodes over InfiniBand networks with RDMA-enabled network cards and
27
Preparing to install Veritas Access
About using LLT over the RDMA network for Veritas Access
switches. In a clustering environment, RDMA allows applications on separate nodes
to transfer data at a faster rate with low latency and less CPU usage.
RDMA over InfiniBand networks in the Veritas Access clustering
environment
Veritas Access uses Low Latency Transport (LLT) for data transfer between
applications on nodes. LLT functions as a high-performance, low-latency
replacement for the IP stack, and is used for all cluster communications. It distributes
(load balances) internode communication across all available private network links.
This distribution means that all cluster communications are evenly distributed across
all private network links (maximum eight) for performance and fault resilience. If a
link fails, traffic is redirected to the remaining links. LLT is also responsible for
sending and receiving heartbeat traffic over network links. Using LLT data transfer
over an RDMA network boosts performance of both file system data transfer and
I/O transfer between nodes.
Network interface cards (NICs) and network switches that support RDMA are
required to enable the faster application data transfer between nodes. You also
need to configure the operating system and LLT for RDMA.
See “Configuring LLT over RDMA for Veritas Access” on page 29.
How LLT supports RDMA for faster interconnections between
applications
Low Latency Transport (LLT) maintains two channels (RDMA and non-RDMA) for
each of the configured RDMA links. Both RDMA and non-RDMA channels can
transfer data between the nodes. LLT provides separate Application Program
Interfaces (APIs) to the clients (such as CFS and CVM) to use these channels. The
RDMA channel is mainly used for data transfer by the client; while the non-RDMA
channel is created over the UDP layer, and LLT uses it mainly for sending and
receiving heartbeats. Group Membership Services/Atomic Broadcast (GAB) decides
cluster membership for the cluster according to the health of the non-RDMA channel.
The connections of the RDMA and non-RDMA channels are under separate
management, while the connect and disconnect operations for the RDMA channel
are triggered based on the status of the non-RDMA channel.
If the non-RDMA channel is up while the RDMA channel is down, the data is
transferred over the non-RDMA channel with lower performance until the RDMA
channel is fixed. The system logs display a message when the RDMA channel is
up or down.
LLT uses the Open Fabrics Enterprise Distribution (OFED) layer and the drivers
on the operating system to communicate with the hardware. LLT over RDMA allows
28
Preparing to install Veritas Access
About using LLT over the RDMA network for Veritas Access
applications running on one node to directly access the memory of an application
running on another node over an RDMA-enabled network. While over a non-RDMA
network, LLT clients have to create intermediate data copies to complete the read
or write operation on the application. RDMA network brings low latency, higher
throughput, and minimized CPU host usage, and boosts application performance.
LLT and GAB clients CFS and CVM can use LLT over RDMA.
Configuring LLT over RDMA for Veritas Access
During the Veritas Access installation, the installer automatically configures LLT
over RDMA if there are InfiniBand NICs on the cluster nodes, unless the InfiniBand
NICs are excluded.
This section describes the required hardware and configuration for LLT to support
RDMA for Veritas Access. The high-level steps to configure LLT over RDMA are
as follows:
1. Choose NICs, network switches, and cables that support RDMA.
Table 3-2
RDMA-enabled hardware
Hardware Supported types
Reference
Network
card
Mellanox-based Host Channel Adapters
(HCAs) (VPI, ConnectX, ConnectX-2 and
3)
For detailed installation
information, refer to the hardware
vendor documentation.
Network
switch
Mellanox, InfiniBand switches
For detailed installation
information, refer to the hardware
vendor documentation.
Cables
Copper and Optical Cables, InfiniBand
cables
Ethernet switches must be Data Center
Bridging (DCB) capable
For detailed installation
information, refer to the hardware
vendor documentation.
2. Connect the first two non-excluded InfiniBand NICs as private NICs.
Note: Cross-links connection is not supported for private NICs in an RDMA
environment.
3. Make sure that the required packages to enable RDMA, InfiniBand drivers, and
utilities are installed with the base operating system. Or they can be installed from
the yum repository.
See “Registering your cluster to RHSM to get yum updates” on page 45.
29
Preparing to install Veritas Access
About using LLT over the RDMA network for Veritas Access
Table 3-3
Drivers and utilities required for RDMA, InfiniBand, or an Ethernet
network
Packages
Drivers and utilities
Device drivers for RDMA
operations
■
libmthca
■
libmlx4
■
rdma
■
librdmacm-utils
■
opensm
■
opensm-libs
■
libibumad
■
ibutils
■
infiniband-diags
■
perftest
OpenSM-related package
InfiniBand troubleshooting and
performance tests
libibverbs packages for InfiniBand ■
operations
■
libibverbs-devel
libibverbs-utils
How the Veritas Access installer configures LLT over RDMA
At a high level, the Veritas Access installer configures the InfiniBand NICs as LLT
over RDMA for Veritas Access by the following steps:
1
After the InfiniBand NICs are detected, the installer installs the required
operating system packages.
2
Choose InfiniBand NICs as private NICs, if the NIC is not excluded.
3
Assign static private IPs and configure LLT to use InfiniBand NICs.
LLT over RDMA sample /etc/llttab
The following is a sample of LLT over RDMA in the etc/llttab file.
rdma_01:~ # cat /etc/llttab
set-node rdma_01
set-cluster 54791
link priveth0 udp - rdma 51001 - 172.16.0.3 172.16.0.255
link priveth1 udp - rdma 51002 - 172.16.1.3 172.16.1.255
set-flow highwater:1000
set-flow lowwater:800
30
Preparing to install Veritas Access
Connecting the network hardware
Connecting the network hardware
Before you install the Veritas Access software, you must assemble a cluster by
configuring all the nodes with the required network hardware, and connecting the
Ethernet interfaces to the private and the public networks.
To assemble the cluster, do the following:
■
Determine a preferred location for the cluster.
■
Make sure that each node has at least two redundant Ethernet interfaces (gigabit
Ethernet) to connect to a private network for cluster internal control.
■
Make sure that each node has at least two additional Ethernet interfaces (gigabit
Ethernet) to connect to the public network. You can use the public Ethernet
interfaces from the embedded interfaces on the motherboard or from the add-on
(PCI) network adapter interfaces.
■
To connect the public NICs, connect one end of the Ethernet cables to the
Ethernet interfaces on the back of the nodes. Connect the other end of the
Ethernet cables to your corporate network so that they can reach the gateway.
At least two public interfaces are required for each node.
■
To connect the private NICs, use the first two available NICs when sorted by
NIC name. An available NIC is not connected to the public network or excluded
from the node.
For example,if your NICs are eth1, eth2, eth3, and eth4, and none of the NICs
are connected to the public network or excluded, then use eth1 and eth2 as the
private NICs.
Connect one end of the Ethernet cables to Ethernet interface 1 and 2 on the
back of the nodes. For a 2-node cluster, connect the other end of the Ethernet
cables to the corresponding Ethernet interfaces on the second node. For a
cluster with more than 2 nodes, connect the other end of the Ethernet cables
to a dedicated switch or VLAN.
Note: It is recommended to use InfiniBand NICs to configure LLT over RDMA
for Veritas Access. Connect InfiniBand NICs as private or exclude the NICs
when you install Veritas Access.
See “About using LLT over the RDMA network for Veritas Access” on page 27.
See “Excluding a NIC” on page 56.
■
Ask your network administrator for a range of IP addresses to use in the Veritas
Access installation. The number of IP addresses you need depends on the
number of nodes and number of network interface cards in your cluster. You
31
Preparing to install Veritas Access
Connecting the network hardware
need two IP addresses per node per public interface (one for the physical IP
addresses, one for the virtual IP addresses), and one IP address for the console
IP per cluster.
Veritas Access supports both Internet Protocol version 4 (IPv4) or Internet
Protocol version 6 (IPv6), but they cannot be mixed.
Physical IP
address
An IP address that is associated with a specific Ethernet interface
address and cannot automatically be failed over.
Virtual IP address
(VIP)
An IP address whose association to a specific Ethernet interface
(VIP) can be failed over to other interfaces on other nodes by the
Veritas Access software.
Console IP
address
A dedicated virtual IP address that is used to communicate with the
Veritas Access cluster Management Console. This virtual IP address
is assigned to the master node. If the master node fails, the Veritas
Access software automatically selects a new master node from the
cluster and fails the console IP address over to it.
Figure 3-2 shows a diagram of a four-node cluster.
32
Preparing to install Veritas Access
About obtaining IP addresses
Figure 3-2
Client
Private network setups: four-node cluster
Client
Client
Public network
Node
1
Node
3
Node
2
Node
4
Ethernet switch
Private network
Fibre channel switch
Storage array
About obtaining IP addresses
The Veritas Access installation process lets you configure IP addresses for 1 to 8
nodes. The default is two nodes.
Note: You can configure either IPv4 addresses or IPv6 addresses (depending on
what you use when installing Veritas Access), but not both. Do not use IP addresses
starting with 172.16.0.X either as physical IP addresses or virtual IP addresses
since this range of IP addresses are used for the private network.
You need to obtain a contiguous range of physical IP addresses, a contiguous
range of virtual IP addresses, and a netmask for the chosen public network from
the network administrator in charge of the facility where the cluster is located. All
33
Preparing to install Veritas Access
About calculating IP address requirements
IP addresses (both physical and virtual) must be part of the same subnet and use
the same netmask as the node's access IP.
By design, the installer does not support the use of the localhost (127.0.0.1) IP
address during installation
Note: Netmask is used for IPv4 addresses. Prefix is used for IPv6 addresses.
Accepted ranges for prefixes are 0-128 (integers) for IPv6 addresses.
The information you obtained from the network administrator is used to configure
the following:
■
Physical IP addresses
■
Virtual IP addresses
■
Console IP address
■
Replication IP address (optional)
■
IP address for the default gateway
■
IP address for the Domain Name System (DNS) server
■
DNS domain name
■
IP address for the Network Time Protocol (NTP) server (optional)
■
Virtual IP address for Veritas NetBackup (optional)
About calculating IP address requirements
This section provides an example of how to calculate IP addresses for a two-node
cluster. In this example, all the nodes in the cluster have the same hardware
configuration. Therefore, the number of network interface cards (NICs) is the same
for all the nodes in the cluster.
■
Two private NICs and two public NICs should be connected to respective
networks.
■
One public IP address should be assigned to one of the public interface for
installation over ssh. None of the private interfaces should have the IP address
in the same network segment.
■
The public IP address must be made permanent by writing it to the network
configuration file /etc/sysconfig/network-scripts/ifcfg-ethX.
Consider the cluster configuration that is shown in Table 3-4.
34
Preparing to install Veritas Access
About calculating IP address requirements
Example configuration
Table 3-4
Number
Item
2
Number of nodes in the cluster
4
Number of interfaces on each node
2
Number of the private interfaces that are required for each node
After two private interfaces on each node are selected, all remaining interfaces act
as public interfaces.
To calculate the number of public interfaces per node
◆
The total number of interfaces on the node, minus the number of private
interfaces that are required on a node, is equal to the remaining number of
public interfaces on the node.
Total number of interfaces (4)
- Number of private interfaces (2)
= Number of public interfaces
4 - 2 = 2
35
Preparing to install Veritas Access
About calculating IP address requirements
To calculate the physical and the virtual IP addresses for the cluster
1
The total number of physical IP addresses that are required for the cluster
installation is equal to the number of nodes in the cluster multiplied by the
number of public interfaces on each node:
Total number of nodes (2)
x Number of public interfaces per node (2)
= Total number of physical IP addresses
= 2 x 2 = 4
2
The number of nodes in the cluster multiplied by the number of public interfaces
on each node is equal to the total number of virtual IP addresses that are
required for the cluster installation:
Total number of nodes (2)
x Number of public interfaces per node (2)
= Total number of virtual IP addresses
= 2 x 2 = 4
3
The number of IP addresses required for the Veritas Access Operations
Manager is equal to one (1).
To calculate the total number of public IP addresses for the cluster
◆
The number of physical IP addresses for the cluster, plus the number of virtual
IP addresses for the cluster, plus the number of IP addresses for the Operations
Manager is equal to the total number of public IP addresses that are required
for the cluster.
Total number of physical IP addresses/cluster (4)
+ Total number of virtual IP addresses/cluster (4)
+ Number of IP addresses for the Management Console (1)
= Total number of public IP addresses required for the cluster
= 4 + 4 + 1 = 9
36
Preparing to install Veritas Access
About checking the storage configuration
To request and specify IP addresses
1
Request the public IP addresses that you need from your Network Administrator.
2
For example, if the Network Administrator provides you with IP addresses
10.209.105.120 through 10.209.105.128, you can allocate the resources in
the following manner:
Start of Physical IP address: 10.209.105.120
Start of Virtual IP address: 10.209.105.124
Management Console IP:"10.209.105.128"
This entry gives you four physical IP addresses (10.209.105.120 to
10.209.105.123), four virtual IP addresses (10.209.105.124 to
10.209.105.127), and one IP address for the Operations Manager
(10.209.105.128).
10.209.105.120 and 10.209.105.121 are assigned to pubeth0 and pubeth1
as physical IP addresses on the first node.
10.209.105.122 and 10.209.105.123 are assigned to pubeth0 and pubeth1
as physical IP addresses on the second node.
10.209.105.124 to 10.209.105.127 are assigned to pubeth0 and pubeth1 as
virtual IP addresses on the two nodes.
About checking the storage configuration
Warning: Do not connect the Fibre Channel HBAs until you finish installing the
operating system. If the local disks are bad, connecting the Fibre Channel HBAs
prevents the operating system from being installed on the local disks. Because the
disk is scanned, it takes longer to install the software on a local disk.
Veritas Access supports Flexible Storage Sharing (FSS), which allows the users
to configure and manage direct-attached storage on the Veritas Access appliance.
After you install the operating system, check the storage configuration. If you don't
want to use FSS, make sure that each node has the following:
■
One or two Fibre Channel Host Bus Adapters (HBAs) for connection to the
Storage Area Network (SAN) switch.
Two Fibre Channel HBAs are recommended, but only one is required. Having
only one Fibre Channel HBA enables all the operations of the Fibre Channel
(except high availability).
37
Preparing to install Veritas Access
About checking the storage configuration
■
An internal boot disk. Make sure that one is in place before you install the Veritas
Access software.
If you want to use FSS, make sure that each node has attached at least two extra
local data disks besides the internal boot disk.
38
Chapter
4
Installing and configuring
a cluster
This chapter includes the following topics:
■
Installation overview
■
Summary of the installation steps
■
Before you install
■
Installing the operating system on each node of the cluster
■
Installing Veritas Access on the target cluster nodes
■
About NIC bonding and NIC exclusion
■
Replacing an Ethernet interface card
■
Configuring I/O fencing
■
About configuring Veritas NetBackup
■
About enabling kdump during an Veritas Access configuration
■
Reconfiguring the Veritas Access cluster name and network
Installation overview
Initially, you can install a two-node Veritas Access cluster. You can increase the
cluster by adding nodes up to the maximum of 8 nodes. The recommended minimum
value is two nodes. Adding nodes to the cluster does not disrupt service.
Installing and configuring a cluster
Summary of the installation steps
Summary of the installation steps
The Veritas Access software installation consists of two main pieces:
■
Operating system installation.
Veritas Access requires Red Hat Enterprise Linux.
See See “System requirements” on page 10.
■
Veritas Access software installation.
Table 4-1 provides a brief summary of the installation steps. The summary includes
cross references to where you can find more information about each task.
Table 4-1
Summary of installation steps
Task
Steps
For more information
Task 1: Install the operating
system on each node of the
cluster.
Steps include:
See “Installing the operating
system on the target Veritas
Access cluster” on page 43.
■
■
■
■
■
■
■
■
Automatic system
discovery of USB devices,
hard disk controllers, and See “Configuring your own
so on.
yum repository on each node
of the cluster” on page 46.
Select the installation
device.
Set the clock and the time
zone.
System preparation for
automated installation.
Automatic disk
partitioning.
Automatic package
installation.
Install the Red Hat
Enterprise Linux kernel
update.
Configuration of yum after
the operating system is
installed successfully.
40
Installing and configuring a cluster
Before you install
Table 4-1
Summary of installation steps (continued)
Task
Steps
For more information
Task 2: Install the Veritas
Access software on the
cluster.
Steps include:
See “Installing the required
Red Hat Enterprise Linux
operating system RPMs”
on page 47.
■
■
■
■
Install the required Red
Hat Enterprise Linux
operating system RPMs.
If yum is configured, then
the installer helps to install
the required RPMs during
the precheck.
Extract the Veritas Access
tar file and run the
installer.
Enter network
configuration information
(cluster name, IP
addresses, bond interface
information, DNS
information, and so on).
Verify installation on the
node.
See “Installing and
configuring the Veritas
Access software on the
cluster” on page 48.
Before you install
Before you install the Veritas Access software:
■
Make sure that no DHCP servers are running in the private network.
■
Disable the USB Ethernet interface in BIOS for all nodes in the cluster.
■
Make sure that there are at least two private and two or more public links between
cluster nodes.
■
Connect the Fibre Channel cable before installing Veritas Access on any node
in the cluster.
■
Prepare one public IP address for each cluster node. This IP address is used
by the installer, so it should not be in the public or virtual IP pool that is used for
the Veritas Access cluster later.
Note: The public IP addresses are not available after the configuration of Veritas
Access, as they get replaced with the physical IP addresses provided at the
configuration level.
41
Installing and configuring a cluster
Installing the operating system on each node of the cluster
■
Configure the newly prepared IP on the public NIC and in the network config
file, /etc/sysconfig/network-scripts/ifcfg-XX to make it as persistent.
For example:
TYPE=Ethernet
HWADDR=00:50:56:3d:f1:3e
DEVICE=eth2
BOOTPROTO=none
IPADDR=10.200.56.214
NETMASK=255.255.252.0
NM_CONTROLLED=no
ONBOOT=yes
Installing the operating system on each node of
the cluster
Before you install the Veritas Access software, you must install the Red Hat
Enterprise Linux operating system and kernel version. The following procedure
includes the instructions and download links.
To install the Red Hat Enterprise Linux operating system on each node of the
cluster
1
Meet the requisite system requirements. Ensure that you have the correct
version of the Red Hat Linux operating system and the kernel version.
2
Use the following information to install Red Hat Enterprise Linux operating
system:
Refer to Chapter 1. Obtaining Red Hat Enterprise Linux in the Red Hat
Enterprise Linux 6 Install guide:
https://access.redhat.com/downloads/
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/pdf/
Installation_Guide/Red_Hat_Enterprise_Linux-6-Installation_Guide-en-US.pdf
About the driver node
If you do not plan to install Veritas Access from the console of the nodes in the
cluster (the local management console of your nodes), you need another server
that is not a target node in the Veritas Access cluster to use in the Veritas Access
installation. This server is called the driver node.
42
Installing and configuring a cluster
Installing the operating system on each node of the cluster
When you run the Veritas Access installation script, the Veritas Access installer
helps set up the ssh connection between the driver node and the target Veritas
Access cluster nodes.
The driver node platform can be: RHEL 6, SLES 11 SP2, and SLES 11 SP3.
Installing the operating system on the target Veritas Access cluster
This first task in the installation process is to install the Red Hat Enterprise Linux
operating system on each node of the cluster.
To install the operating system
1
Insert the Red Hat Enterprise Linux operating system installation DVD, and
boot the server from the DVD.
See See “Linux requirements” on page 11.
You can also use an external USB DVD-ROM.
2
Disable the consistent network device naming feature when installing the Red
Hat Enterprise operating system.
Note: By default, the consistent network device naming feature is enabled on
Dell systems. To disable the feature, enter the following option on the boot
command line: linux biosdevname=0
3
At the boot prompt, select the Install and upgrade an existing system option.
Press Enter.
4
The installer asks you if you want to perform a media check or if you want to
skip this option. Select Skip and continue with the installation.
5
The installation starts with the Red Hat Enterprise Linux banner, click Next to
continue installation.
6
The installation displays a language selection screen. Veritas Access only
supports English. Select English. English is used for the installation and as the
system default. Click Next to continue.
7
Select the correct layout type for the keyboard you would prefer to use for the
installation and as the system default. Once you have made your selection,
click Next to continue.
8
You can install Red Hat Enterprise Linux on a large variety of storage devices.
This screen lets you select either basic or specialized storage devices. Click
Next to continue.
43
Installing and configuring a cluster
Installing the operating system on each node of the cluster
9
The installer automatically detects any existing installations of Red Hat
Enterprise Linux. It asks you to choose whether you want to perform a Fresh
Installation or Upgrade an Existing Installation.
If your system contains a Red Hat Enterprise Linux installation, a dialog appears
asking whether you want to upgrade that installation. To perform an upgrade
of an existing system, choose the appropriate installation from the drop-down
list and select Next.
10 The installer prompts you to set the host name for the root user. It also asks if
you want to configure the network. Set the IP address to a proper public NIC
so that you can access the NIC through that IP after a restart. Click Next to
proceed.
11 In the Time Zone Configuration screen, set your time zone by selecting the
city closest to your computer's physical location. Click Next to proceed.
12 The installer prompts you to set a root password for your system. You cannot
proceed to the next stage of the installation process without entering a root
password. Enter the root password into the Root Password field. Red Hat
Enterprise Linux displays the characters as asterisks for security. Type the
same password into the Confirm field to ensure that it is set correctly. After
you set the root password, select Next to proceed.
13 The installer asks you to choose the type of installation. Depending on your
need, select the layout for installation.
14 In the Disk Partitioning Setup screen, you can choose to create the default
partition layout in one of four different ways. Or you can choose to partition
storage devices manually to create a custom layout.
15 If you selected the Encrypt System option, the installer prompts you for a pass
phrase with which to encrypt the partitions on the system.
16 If you selected more than one storage device on the storage devices selection
screen, the installer asks you to select which of these devices should be
available for installation of the operating system, and which should only be
attached to the file system for data storage. If you selected only one storage
device, the installer does not present you with this screen. During installation,
the devices that you identify as being for data storage only are mounted as
part of the file system, but are not partitioned or formatted. When you have
finished identifying devices to be used for installation, click Next to continue.
17 If no readable partition tables are found on existing hard disks, the installation
program asks to initialize the hard disk. Click Re-initialize drive.
44
Installing and configuring a cluster
Installing the operating system on each node of the cluster
18 The installer prompts you to create a custom layout or modify the default layout.
The installer also prompts you to confirm the partitioning options that you
selected. Click Write changes to disk to allow the installer to partition your
hard drive and install Red Hat Enterprise Linux.
19 The Package Installation Defaults screen appears and details the default
packages for your Red Hat Enterprise Linux installation. This screen varies
depending on the version of Red Hat Enterprise Linux you want to install.
Configure the boot loader (GRUB) and select the installation packages as per
the requirements. The installer searches for the required packages from the
installation media and installs those packages. Select the Basic Server option
for installation.
20 Once the package installation gets completed, you have to restart your system
for post-installation tasks. Remove the install media and click on Reboot to
continue.
21 Your Red Hat Enterprise Linux installation is now complete. You can follow
the same steps that are shown in this section to install the operating system
on other nodes of the cluster.
See the Red Hat Enterprise Linux documentation for the detailed procedure.
22 Disable SELinux on all nodes in the cluster.
Registering your cluster to RHSM to get yum updates
After you install the operating system on all the nodes of the cluster, register your
cluster to Red Hat Subscription Manager (RHSM) to get the packages update from
the official yum repository. The yum repository configuration file
/etc/yum.repos.d/rhel-source.repo is configured by default after the operating
system installation.
To register your cluster to RHSM
1
Enter the following command:
# subscription-manager register
2
After you input the user name and the password as prompted, enter the
following command:
# subscription-manager subscribe --auto
45
Installing and configuring a cluster
Installing the operating system on each node of the cluster
Configuring your own yum repository on each node of the cluster
After you install the operating system on all the nodes of the cluster, you can
configure your own yum repository on each target node of the Veritas Access cluster.
Veritas recommends that you configure the local repository, which reduces half of
the installation time.
Before you configure yum, set up a package repository for use by yum. You can
use the release server of Red Hat Enterprise Linux or your own yum repository
server. If the you use the Red Hat Enterprise Linux release server, then you must
have the registered credentials from Red Hat Enterprise Linux. Otherwise, set up
a yum repository server before you configure the yum client. Make sure that you
have Veritas Access required rpms or higher versions in your yum repository.
To configure yum on each node
1
Add a .repo file to your yum configuration on each target node of the Veritas
Access cluster.
Create a new file in /etc/yum.repos.d/ on the node where you want to use
this repository.
The file can have any name but the file needs to be named with the suffix
.repo. For example: myrepo.repo.
2
In the new .repo file, include the following:
[myrepo]
name = This is my repo
baseurl = url://to/get/to/srv/my/repo/
where the baseurl line is the path that the system uses to get to the repository.
If the node has direct access to it or mounts it as a file system, you can use a
baseurl line like:
baseurl = file:///srv/my/repo/
If you access the file using an HTTP or https server, you can use a baseurl
line like the following:
baseurl = http://servername/my/repo
For more information on the client-side repository configuration, see the
yum.conf man page.
46
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
Installing Veritas Access on the target cluster
nodes
Installing the cluster is a one-time activity. You can install up to a 8-node cluster.
Before you continue, be aware of the following parameters:
■
If you do not allocate enough IP addresses for the cluster, the installation cannot
proceed.
Note: You cannot mix IPv4 and IPv6 addresses; new IP addresses must be of
the same version that you initially used when installing Veritas Access.
See “About obtaining IP addresses” on page 33.
It takes about 40 minutes to install a two-node cluster. Installation times may vary
depending on your configuration and the number of nodes.
Installing the required Red Hat Enterprise Linux operating system
RPMs
You have to install the required RPMs.
47
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
To install the required RPMs
1
Install the required RPMs that cannot be found in the RHN yum repository.
You need to manually install some RPMs that cannot be found in the RHN
repository.
For RHEL 6 Update 6, install:
kernel-debuginfo-common-x86_64 2.6.32-504.el6.x86_64.rpm
kernel-debuginfo 2.6.32-504.el6
For RHEL 6 Update 7, install:
kernel-debuginfo-common-x86_64 2.6.32-573.el6.x86_64.rpm
kernel-debuginfo 2.6.32-573.el6
2
Install other operating system RPMs required by the installer.
If you configured yum correctly, the installer automatically installs the required
operating system RPMs which can be found in the yum repository. If you use
your own yum repository, add all the required RPMs into your yum repository.
The installer also installs the RPMs that Veritas Access provides. For example,
third-party RPMs, like the Samba [SMB] RPMs.
See “Required Red Hat Enterprise Linux operating system RPMs for RHEL 6.6”
on page 14.
Installing and configuring the Veritas Access software on the cluster
To install and configure Veritas Access, you can either run the installer from the
driver node, or any node of the cluster, or the cluster node's console.
See “To run the installer from the cluster node's console” on page 48.
A driver node refers to a node that is not one of the cluster nodes on which you
want to install Veritas Access. You have to ensure that the driver node can ssh to
all the cluster nodes.
To run the installer from the cluster node's console
1
Log into the cluster node's console.
2
From the console, log into the cluster node.
48
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
3
Mount the ISO image manually using these commands:
# mkdir /accessmnt
# mount -o loop ACCESS-7.2-<image> /accessmnt
4
Enter the directory in which the installer is located.
# cd /accessmnt/
To run the installer from a driver node or any node in the cluster
1
Use the root user and password to log into the node on which you want to
install the ISO image.
2
Mount the ISO image manually using these commands:
# mkdir /accessmnt
# mount -o loop ACCESS-7.2-<image> /accessmnt
3
Enter the directory in which the installer is located.
# cd /accessmnt/
To install and configure the cluster
Note: During the installation, the installer log is located at /var/tmp.
49
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
1
50
Enter the following command to start the installation.
# ./installaccess node1_ip node2_ip
Where node1_ip and node2_ip are the public physical IP addresses that are
already assigned to the target cluster nodes to install Veritas Access over ssh.
These are the current IPs assigned to the nodes for installation communication.
The example is used to install two nodes. To install another target node cluster,
add node3_ip to the command line that is used in this step.
2
The installer prompts you to choose how you want to install OS rpms – either
using native methods, like yum, or manually install the OS rpms. Some of the
required OS rpms only exist on Red Hat public YUM repositories, and you are
required to set up Red Hat subscription first to install these OS rpms.
1) Install the required OS rpms with yum. If yum repository is not
configured on the systems, set up Red Hat subscription first
2) Install the required OS rpms manually
3) Do not install the required OS rpms and quit
How do you want to install the required OS rpms? [1-3,q,?] (1) 1
3
The installer checks the operating system dependencies and automatically
installs the required operating system RPMs and any missing third-party RPMs.
4
The installer installs the Veritas Access RPMs.
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
5
The installer displays the firewall ports to be opened after the configuration,
and asks if you want to open them:
Veritas Access needs to open the following ports:
111 Rpcbind (NFS)
11211 Memcached Port
123 NTP Service
139 CIFS Service
161 SNMP Service
2049 NFS Service
21 FTP Port
22 SSH Service
25 SMTP Port
30000:40000 FTP Passive Port Range
3172,3173 Server View Ports
4001 Mountd (NFS)
4045 NLM (NFS)
4379 CTDB Port
445 CIFS TCP Service
51001,51002 RDMA Service
514 Syslog Service
53 DNS Service
5634 VIOM
56987 Replication Service
756,757,755 Statd (NFS)
8088 REST Server
8143 Object Access Gateway
Do you want to proceed? [y,n,q] (y)
6
The installer automatically configures the RDMA environment on the cluster
nodes if there are InfiniBand NICs.
51
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
7
52
The installer asks the following information to configure the cluster:
The Veritas Access Cluster name:
The public IP starting address:
The netmask for public IP address
The virtual IP starting address:
The number of VIPs per interface:
The default gateway IP address:
The DNS server IP address:
The DNS server domain name:
The console virtual IP address:
Do you want to use the separate console port?
Note: The cluster name can contain only alpha characters, numbers, or
underscores. The cluster name must start with a letter of the alphabet and can
have a length of maximum 15 characters. Also, if a separate console port is
chosen, the first public NIC is chosen to work exclusively as a console port.
8
The installer asks if you want to configure the Network Time Protocol (NTP)
server.
Do you want to configure the Network Time Protocol(NTP) server to
synchronize the system clocks? [y,n,q] y
Enter the Network Time Protocol server: [q,?]
If you enter y, you can type in your NTP server. If you enter n, the NTP server
is not configured.
9
The installer detects the network devices. The installer asks if you want to
configure NIC bonding or exclude NICs.
Do you want to configure NIC bonding or exclude NICs? [y,n,q] (n)
If you do not want to configure NIC bonding or exclude NICs, enter n. Go to
step 10.
If you do want to configure NIC bonding or exclude NICs, enter y.
See “Excluding a NIC” on page 56.
See “Creating a new NIC bond” on page 62.
Note: After this step, the temporary IP addresses assigned to the target Veritas
Access nodes are no longer accessible. You should access the nodes using
the new set of IP addresses assigned during Veritas Access installation.
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
53
10 The installer prompts to verify the network configuration.
Verify that the configuration information such as the new IP addresses, host
name, and other details are correct.
Configuration checklist:
System
Hostname
New Hostname
============================================================
192.168.10.1 oldhostname01.example.com newhostname01.example.com
192.168.10.2 oldhostname02.example.com newhostname02.example.com
System
Gateway IP
DNS IP
Domain name
================================================================
192.168.10.1 192.168.10.3 192.168.10.0 hostname.example.com
192.168.10.2 192.168.10.3 192.168.10.0 hostname.example.com
System
NIC name(previous name) Physical IP
====================================================
192.168.10.1 pubeth0(eth10)
192.168.10.5
192.168.10.1 pubeth1(eth11)
192.168.10.6
192.168.10.2 pubeth0(eth10)
192.168.10.7
192.168.10.2 pubeth1(eth11)
192.168.10.8
Virtual IP
=========================================================
192.168.10.10 192.168.10.11 192.168.10.12 192.168.10.13
System
NIC name(previous name)
======================================
192.168.10.1 priveth0(eth8)
192.168.10.1 priveth1(eth9)
192.168.10.2 priveth0(eth8)
192.168.10.2 priveth1(eth9)
Is this information correct? [y,n,q] (y)
Installing and configuring a cluster
Installing Veritas Access on the target cluster nodes
54
11 The installer renames the NICs and host name, and assigns the IPs for the
systems after the confirmation. The installer also checks the Low Latency
Transport (LLT) link status and automatically selects them.
Note: The installer does not check the LLT link status if the InfiniBand NICs
are chosen as private NICs. See “About using LLT over the RDMA network
for Veritas Access” on page 27.
12 If you are installing the ISO image on any node of the cluster (not the driver
node), your session will get disconnected due to the network configuration.
Re-login using the IP address prompted by the installer to resume installation.
The system is performing network configuration tasks. The current
session will be temporarily disconnected. Re-login with 10.209.193.248
to resume installation.
13 The installer prompts to ask if you want to configure I/O fencing during the
installation.
Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)
If you do not want to configure I/O fencing, enter n. If you plan to use both
shared disks and local disks in your cluster, we recommend that you do not
configure I/O fencing with the installer. Go to step 15.
To configure I/O fencing, enter y.
See “Configuring I/O fencing” on page 74.
14 The installer automatically restarts the cluster nodes to enables the Kdump
function for each node.
15 Check the log file to confirm the installation and configuration. Logs can be
found in /opt/VRTS/install/logs/.
Note: After the installation, connect to the Veritas Access console using the console
IP address you assigned earlier, then log on using the default user name master
and the default password master.
Veritas Access 7.2 Graphical User Interface (GUI)
Veritas Access 7.2 introduces a new Graphical User Interface (GUI). The GUI
provides a dashboard for a specific Veritas Access cluster, as well as views for
shares, storage infrastructure, reports, and settings. The GUI lets the administrator
Installing and configuring a cluster
About NIC bonding and NIC exclusion
perform tasks for the cluster and monitor the results. In this release, the GUI is part
of Veritas Access.
After you complete I/O fencing configuration successfully, the link to the GUI appears
on the screen.
Open the https://<console IP>:14161 URL
in your browser to start the Veritas Access GUI application.
About NIC bonding and NIC exclusion
When you install Veritas Access on a cluster, you can perform the following
operations using the NICs:
■
Exclude a NIC
See “Excluding a NIC” on page 56.
■
Include a NIC
See “Including a NIC” on page 60.
■
Create a new NIC bond and add a NIC to a bond
See “Creating a new NIC bond” on page 62.
■
Remove a bond
See “Removing a NIC bond” on page 68.
■
Remove a NIC from the bond list
See “Removing a NIC from the bond list” on page 71.
Note: The NIC bonding and NIC exclusion configuration options support both a
single NIC or bond, and multiple NICs or bonds.
Note: When using the NIC exclusion feature, you can exclude any NIC on the first
node. But if you want to exclude any NIC on the other nodes, you can choose to
exclude NICs per node.
See “Excluding a NIC” on page 56.
Note: If you want to use the NIC bonding feature, make sure that the PCI IDs of
the slave bond NICs of the first node is the same as the PCI IDs of the slave bond
NICs of the other nodes.
55
Installing and configuring a cluster
About NIC bonding and NIC exclusion
Excluding a NIC
When you install Veritas Access on a cluster, you may want to use some of the
NICs for other storage purposes. You can use the Exclude a NIC functionality to
exclude some NICs that you do not want to use for Veritas Access.
Note: The NIC bonding/NIC exclusion configuration options support both a single
NIC or bond, and multiple NICs or bonds.
56
Installing and configuring a cluster
About NIC bonding and NIC exclusion
57
To exclude a NIC
1
During Veritas Access installation, the installer asks if you want to configure
NIC bonding or exclude NICs. Enter y if you want to exclude a NIC.
Do you want to configure NIC bonding or exclude NICs? [y,n,q] (n) y
2
The installer prompts you to enter your selection. Enter 1 to exclude a NIC.
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) N
eth3 0000:02:04.0 (physical NIC) N
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 1
Installing and configuring a cluster
About NIC bonding and NIC exclusion
3
The installer prompts you to select the NIC that you want to exclude. Enter
your choice.
Choose NICs for exclusion
1)
2)
3)
4)
5)
6)
7)
b)
eth2 0000:02:03.0 (physical
eth3 0000:02:04.0 (physical
eth4 0000:02:05.0 (physical
eth5 0000:02:06.0 (physical
eth6 0000:02:07.0 (physical
eth7 0000:02:08.0 (physical
Exclude NICs per node
Back to previous menu
Choose NICs: [1-7,b,q] 1 2(1,2)
NIC)
NIC)
NIC)
NIC)
NIC)
NIC)
58
Installing and configuring a cluster
About NIC bonding and NIC exclusion
4
59
The installer goes back to the previous menu. You can choose another NIC
for exclusion. Enter 1 to exclude another NIC. Or you can save your
configurations and continue with the installation of Veritas Access.
If you want to save your configurations, enter 7 :
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) Y
eth3 0000:02:04.0 (physical NIC) Y
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 7
Installing and configuring a cluster
About NIC bonding and NIC exclusion
5
If you want to exclude NICs per node, in Step 3 enter 7. The NICs with
inconsistent PCI IDs are listed:
Choose NICs for exclusion
1)
2)
3)
4)
5)
6)
7)
b)
eth2 0000:02:03.0 (physical
eth3 0000:02:04.0 (physical
eth4 0000:02:05.0 (physical
eth5 0000:02:06.0 (physical
eth6 0000:02:07.0 (physical
eth7 0000:02:08.0 (physical
Exclude NICs per node
Back to previous menu
NIC)
NIC)
NIC)
NIC)
NIC)
NIC)
Choose NICs: [1-7,b,q] 7
Choose items: [1-1,b,q] 1
1
0000:02:00.0 (10.198.95.214)
2
0000:02:01.0 (10.198.95.214)
3
0000:02:06.0 (10.198.95.212)
4
0000:02:09.0 (10.198.95.214)
5
0000:02:14.0 (10.198.95.212)
6
0000:02:15.0 (10.198.95.212)
b) Back to previous menu
Choose NICs: [1-6,b,q] 1 2 3 4 5 6
Note: NIC exclusion function is supported on InfiniBand NICs, but all the NICs with
the same PCI ID are excluded during the exclusion operation. See “About using
LLT over the RDMA network for Veritas Access” on page 27.
Including a NIC
When you install Veritas Access on a cluster, you may want to include one or more
NICs that you had previously excluded. You can use the Include a NIC functionality
to include NICs that you want to use for Veritas Access.
60
Installing and configuring a cluster
About NIC bonding and NIC exclusion
61
To include a NIC
1
If you have excluded some NICs and not saved your configuration, it is possible
to include a NIC again. When the installer asks you to select the NIC option
that you want to configure in the cluster, enter 2 if you want to include a NIC.
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) Y
eth3 0000:02:04.0 (physical NIC) Y
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 2
2
The installer prompts you to select the NIC that you want to include. Enter your
choice.
Choose NICs for inclusion
1)
2)
3)
b)
eth2 0000:02:03.0 (excluded NIC)
eth3 0000:02:04.0 (excluded NIC)
Include NICs per node
Back to previous menu
Choose NICs: [1-6,b,q] 1
Installing and configuring a cluster
About NIC bonding and NIC exclusion
3
62
The installer goes back to the previous menu. You can choose another NIC
for inclusion. Enter 2 to include another NIC. Or you can save your
configurations and continue with the installation of Veritas Access.
If you want to save your configurations, enter 7
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network..
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) N
eth3 0000:02:04.0 (physical NIC) Y
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q]
4
If you want to include NICs per node, in Step 2 enter 3.
Note: NIC inclusion function is supported on InfiniBand NICs, but all the NICs with
same PCI ID are included during the include operation. See “About using LLT over
the RDMA network for Veritas Access” on page 27.
Creating a new NIC bond
An administrator can create a bond NIC interface from a given list of public NIC
interfaces during Veritas Access installation. This feature allows an administrator
Installing and configuring a cluster
About NIC bonding and NIC exclusion
to save a number of physical IP addresses that are used for installation and
post-installation bond creation.
■
The bond interface feature is available for network interface card (NIC) bonding
of public interfaces only. Bonding of private interfaces is not supported.
■
You cannot bond InfiniBand NICs since the PCI IDs are identical. See “About
using LLT over the RDMA network for Veritas Access” on page 27.
■
You can create a bond interface for public NICs only if the PCI IDs of the public
NICs are correspondingly same among the nodes.
If you do not want to create a bond interface, continue with the installation.
See “About obtaining IP addresses” on page 33.
See “About calculating IP address requirements” on page 34.
63
Installing and configuring a cluster
About NIC bonding and NIC exclusion
64
To create a bond
1
During the Veritas Access installation, the installer asks if you want to configure
NIC bonding or exclude NICs. Enter y if you want to configure a NIC bond.
Do you want to configure NIC bonding or exclude NICs? [y,n,q] (n) y
2
The installer prompts you to enter your selection. Enter 3 to create a new bond.
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) N
eth3 0000:02:04.0 (physical NIC) N
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 3
Installing and configuring a cluster
About NIC bonding and NIC exclusion
3
The installer prompts you to select the bond mode of the new bond. Enter your
choice.
Configure the mode for the NIC bonding:
1)
2)
3)
4)
5)
b)
balance-rr
active-backup
balance-xor
broadcast
802.3ad
Back to previous menu
Select the mode of bond: [1-5,b,q] 3
bond0 is created.
Press [Enter] to continue
4
If you choose 3 or 5, the installer prompts you to choose the bond option for
the bond mode:
1) layer2
2) layer3+4
3) default
Select the bonding option: [1-3,b,q] 1
65
Installing and configuring a cluster
About NIC bonding and NIC exclusion
5
66
The installer prompts you to select the NIC option that you want to configure
in the cluster.
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
=============================================
eth2 0000:02:03.0 (physical NIC) N
eth3 0000:02:04.0 (physical NIC) N
eth4 0000:02:05.0 (physical NIC) N
eth5 0000:02:06.0 (physical NIC) N
eth6 0000:02:07.0 (physical NIC) N
eth7 0000:02:08.0 (physical NIC) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 4
6
The installer prompts you to select the NIC.
1)
2)
3)
4)
5)
6)
b)
eth2
eth3
eth4
eth5
eth6
eth7
Back
0000:02:03.0 (physical
0000:02:04.0 (physical
0000:02:05.0 (physical
0000:02:06.0 (physical
0000:02:07.0 (physical
0000:02:08.0 (physical
to previous menu
Choose NICs: [1-6,b,q] 1
NIC)
NIC)
NIC)
NIC)
NIC)
NIC)
Installing and configuring a cluster
About NIC bonding and NIC exclusion
7
67
The installer prompts you to choose a bond name to which you want to add
the NIC.
1)
b)
bond0
Back to previous menu
Choose a bond: [1-1,b,q] 1
Adding 0000:02:03.0 to bond0 was successful
Press [Enter] to continue:
8
The installer prompts you to select the NIC option that you want to configure
in the cluster.
Enter 4 if you want to add another NIC to the bond . Or you can enter 7 to save
your configurations and continue with the installation of Veritas Access.
Veritas Access 7.2 Configure Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
bond status
If excluded
===============================================
eth2 0000:02:03.0 (Slave of bond0) N
eth3 0000:02:04.0 (Slave of bond0) N
eth4 0000:02:05.0 (physical NIC)
N
eth5 0000:02:06.0 (physical NIC)
N
eth6 0000:02:07.0 (physical NIC)
N
eth7 0000:02:08.0 (physical NIC)
N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 7
Installing and configuring a cluster
About NIC bonding and NIC exclusion
Removing a NIC bond
An administrator can remove a bond that has been already created.
68
Installing and configuring a cluster
About NIC bonding and NIC exclusion
69
To remove a NIC bond
1
During the Veritas Access installation, the installer prompts you to enter your
selection. Enter 5 to remove an existing bond.
Veritas Access 7.2 Install Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
BOND status
If excluded
===============================================
eth0 0000:02:01.0 (physical NIC)
N
eth1 0000:02:02.0 (physical NIC)
N
eth2 0000:02:03.0 (Slave of bond0) N
eth3 0000:02:04.0 (Slave of bond0) N
eth4 0000:02:05.0 (Slave of bond2) N
eth5 0000:02:06.0 (Slave of bond1) N
eth6 0000:02:07.0 (Slave of bond1) N
eth7 0000:02:08.0 (Slave of bond2) N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 5
Installing and configuring a cluster
About NIC bonding and NIC exclusion
2
The installer prompts you to select the bond which you want to remove. Enter
your choice.
1)
2)
3)
b)
bond0
bond1
bond2
Back to previous menu
Choose bonds: [1-3,b,q] 3
Deleting NIC bonding bond2 succeeded
Press [Enter] to continue:
70
Installing and configuring a cluster
About NIC bonding and NIC exclusion
3
71
The installer prompts you to select the NIC option that you want to configure
in the cluster. Enter 5 if you want to remove another bond . Or you can enter
7 to save your configurations and continue with the installation of Veritas
Access.
Veritas Access 7.2 Install Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
BOND status
If excluded
===============================================
eth0 0000:02:01.0 (physical NIC)
N
eth1 0000:02:02.0 (physical NIC)
N
eth2 0000:02:03.0 (Slave of bond0) N
eth3 0000:02:04.0 (Slave of bond0) N
eth4 0000:02:05.0 (physical NIC)
N
eth5 0000:02:06.0 (Slave of bond1) N
eth6 0000:02:07.0 (Slave of bond1) N
eth7 0000:02:08.0 (physical NIC)
N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q]
Removing a NIC from the bond list
During installation, an administrator can remove a NIC which is already a slave of
a bond before the configuration is saved.
Installing and configuring a cluster
About NIC bonding and NIC exclusion
72
To remove a NIC from the bond list
1
During the Veritas Access installation, the installer prompts you to enter your
selection. Enter 6 to remove a NIC from the bond list.
Note: The NIC bonding/NIC exclusion configuration options support both a
single NIC or bond, and multiple NICs or bonds.
Veritas Access 7.2 Install Program
10.200.114.45 10.200.114.46
NIC bonding/NIC exclusion configuration
NIC bonding supports only public NICs. Make sure the NICs you choose
are connected to public network.
NIC PCI ID
BOND status
If excluded
===============================================
eth0 0000:02:01.0 (physical NIC)
N
eth1 0000:02:02.0 (physical NIC)
N
eth2 0000:02:03.0 (Slave of bond0) N
eth3 0000:02:04.0 (Slave of bond0) N
eth4 0000:02:05.0 (Slave of bond0) N
eth5 0000:02:06.0 (Slave of bond1) N
eth6 0000:02:07.0 (Slave of bond1) N
eth7 0000:02:08.0 (physical NIC)
N
1)
2)
3)
4)
5)
6)
7)
Exclude NICs
Include NICs
Create a new bond
Add NICs to a bond
Remove bonds
Remove NICs from the bond list
Save and Continue
Select the NIC option to be configured in this Cluster: [1-7,q] 6
Installing and configuring a cluster
Replacing an Ethernet interface card
2
The installer prompts you to select the NIC that you want to delete from the
NIC bonding. Enter your choice.
Choose a NIC to be deleted from the NIC bonding
1)
2)
3)
4)
5)
b)
eth2
eth3
eth4
eth5
eth6
Back
0000:02:03.0 (Slave
0000:02:04.0 (Slave
0000:02:05.0 (Slave
0000:02:06.0 (Slave
0000:02:07.0 (Slave
to previous menu
of
of
of
of
of
bond0)
bond0)
bond0)
bond1)
bond1)
Choose a NIC: [1-8,b,q] 5
The NICs with the PCI id 0000:02:05.0 has been removed from /
the NIC bonding
Press [Enter] to continue:
3
The installer prompts you to select the NIC option that you want to configure
in the cluster. Enter 6 if you want to remove another NIC from the bond list .
Or you can enter 7 to save your configurations and continue with the installation
of Veritas Access.
Replacing an Ethernet interface card
In some cases, you may need to replace an Ethernet interface card on a node. This
section describes the steps to replace the card.
Note: This procedure works for replacing an existing Ethernet interface card. It
does not work for adding an Ethernet interface card to the cluster. If the Ethernet
interface card you add needs a new device driver, install the new device driver
before installing the Ethernet interface card on the node.
73
Installing and configuring a cluster
Configuring I/O fencing
74
To replace an Ethernet interface card
1
Use the Cluster> shutdown command to shut down the node.
For example:
Cluster> shutdown access_03
Stopping Cluster processes on access_03.......done
Sent shutdown command to access_03
2
Use the Cluster> del command to delete the node from the cluster.
For example:
Cluster> del access_03
3
Install the replacement Ethernet interface card on the node.
4
Turn on the node.
5
Make sure that the Ethernet interface card is active and online.
6
Use the Cluster> add command to add the node back into the cluster.
For example:
Cluster> add 172.16.113.118
For details on the Cluster> add and Upgrade> commands that are described in
this section, see the Veritas Access Command-Line Administrator’s Guide.
Configuring I/O fencing
Veritas Access supports two fencing modes: disk-based fencing for a cluster with
shared disks, and majority-based fencing for a cluster with local DAS disks.
If you intend to use both shared disks (SAN) and local disks, majority-based fencing
must be used. Veritas recommends that you do not configure I/O fencing through
the installer.
For more information about FSS and configuring I/O fencing, see the Veritas Access
Command-Line Administrator’s Guide.
1
During the Veritas Access configuration, after the product is started, the installer
asks whether to configure fencing:
Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)
2
Enter y to configure fencing.
Installing and configuring a cluster
About configuring Veritas NetBackup
■
If the cluster does not include initialized shared disks, majority-based fencing
mode is configured.
The I/O fencing would be configured in majority mode.
■
If shared disks are connected and initialized, disk-based I/O fencing is
configured. You are prompted to choose disks.
Note: You can choose three available VxVM disks or initialize three disks
as VxVM disks to form the fencing disk group. You must choose exactly
three disks.
3
The installer stops the product, and applies the fencing configuration before
restart.
About configuring Veritas NetBackup
If you use Veritas NetBackup, to comply with the NetBackup End-User License
Agreement (EULA), you have to purchase and enter valid license keys on the
external NetBackup master server before you configure NetBackup to work with
Veritas Access. For more information on entering the NetBackup license keys on
the NetBackup master server, see the Veritas NetBackup Installation Guide.
If you use NetBackup, configure the virtual IP address using the Backup>
virtual-ip command so that it is different from all of the virtual IP addresses,
including the console server IP address and the physical IP addresses that are
used to install the Veritas Access software.
See the Veritas Access Command-Line Administrator's Guide for more information
on this feature.
About enabling kdump during an Veritas Access
configuration
During the Veritas Access configuration, the Veritas Access installer tries to enable
kdump on your cluster node. To meet the Veritas Access software requirements,
the installer modifies the /etc/kdump.conf and /boot/grub/grub.conf files by
using the following options:
■
/boot/grub/grub.conf
crashkernel = 512M-2G:64M, 2G-:256M
75
Installing and configuring a cluster
Reconfiguring the Veritas Access cluster name and network
■
/etc/kdump.conf
path /opt/SYMCsnas/core/kernel/
core_collector makedumpfile -c --message-level 1 -d 31
Reconfiguring the Veritas Access cluster name
and network
After you install and configure Veritas Access, you can reconfigure the cluster name
and network, if required.
Before you reconfigure the cluster, you have to enable the support user for the
nodes because the root user access authority is forbidden. The support user default
password is veritas. You can change the password after you log on the first time.
To reconfigure the Veritas Access cluster name and network
1
Log on to the host console using the support user name and password.
2
Ensure that all the service groups are offline. Enter the following command:
/opt/VRTS/install/installaccess72 -updateparameter
76
Installing and configuring a cluster
Reconfiguring the Veritas Access cluster name and network
3
Enter the private IPs of the systems.
172.16.0.3 172.16.0.4
Note: Only the private IPs of the systems must be entered. Public IPs should
not be used here.
4
Enter the cluster name and network information.
The Veritas Access Cluster name:
The public IP starting address:
The netmask for public IP address
The virtual IP starting address:
The number of VIPs per interface:
The default gateway IP address:
The DNS server IP address:
The DNS server domain name:
The console virtual IP address:
Do you want to use the separate console port?
Do you want to configure the Network Time Protocol(NTP)
server to synchronize the system clocks? [y,n,q] (n)
The installer confirms that the information that you entered is correct. The
configuration is completed and the new cluster and IPs are configured on the
cluster.
The installer displays the location of the log and summary files. If required,
view the files to confirm the configuration status.
Note: The cluster name can contain only alpha characters, numbers, or
underscores. The cluster name must start with a letter of the alphabet and can
have a length of maximum 15 characters. Also, if a separate console port is
chosen, the first public NIC is chosen to work exclusively as a console port.
Note: If your cluster has FSS disks, limit the cluster name to 10 characters.
After formatting the FSS disks, do not change the cluster name.
77
Chapter
5
Automating Veritas Access
installation and
configuration using
response files
This chapter includes the following topics:
■
About response files
■
Performing a silent Veritas Access installation
■
Response file variables to install and configure Veritas Access
■
Sample response file for Veritas Access installation and configuration
About response files
The installer script generates a response file during any installation, configuration,
upgrade, or uninstall procedure. The response file contains the configuration
information that you entered during the procedure. When the procedure completes,
the installation script displays the location of the response files.
You can use the response file for future installation procedures by invoking an
installation script with the -responsefile option. The response file passes
arguments to the script to automate an installation or uninstallation.
See “Installation script options” on page 120.
Automating Veritas Access installation and configuration using response files
Performing a silent Veritas Access installation
Performing a silent Veritas Access installation
A silent installation and configuration is based on a response file that you prepare
so that the Veritas Access software can be installed without prompts. This feature
is useful if you want to install the Veritas Access software on a large number of
nodes.
Before performing a silent Veritas Access installation and configuration, you have
to manually configure a secure shell (ssh) communication between the nodes.
See “Manually configuring passwordless secure shell (ssh)” on page 122.
You can get the Veritas Access example response file from the root directory of
the ISO image.
To use the Veritas Access silent installation feature
◆
Enter the following command:
# ./installaccess -responsefile access.responsefile
To generate the access.response example file
1
Install and configure the Veritas Access software without any errors.
2
Get the access.response example file from the log directory.
To use the access.response example file
1
Rename the Veritas Access example response file to access.responsefile.
2
Modify the file by changing the cluster name, IP address ranges, and other
parameters, as necessary for your configuration.
Installation times may vary depending on your configuration.
See “Installing and configuring the Veritas Access software on the cluster”
on page 48.
Response file variables to install and configure
Veritas Access
Table 5-1 lists the response file variables that you can define to install and configure
Veritas Access.
79
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access
Variable
Description
CFG{bondmode}{bond<n>}
Defines the bond modes for BOND.
List or scalar: list
Optional or required: optional
CFG{bondname}
List of bond names for BOND.
List or scalar: list
Optional or required: optional
CFG{bondpool}{bond<n>}
List of the PCI IDs of the slave NICs.
List or scalar: list
Optional or required: optional
CFG{config_majority_based_fencing}
Enables majority fencing. The value is 1. It
cannot be used with I/O fencing variables
'fencing_scsi3_disk_policy',
'fencing_newdg_disks', and
'fencing_dgname'.
List or scalar: scalar
Optional or required: required for
majority-based fencing
CFG{exclusion}
List of PCI IDs of exlcluded NICs.
List or scalar: list
Optional or required: optional
CFG{fencing_dgname}
Specifies the disk group for I/O fencing. The
value is sfscoorddg.
List or scalar: scalar
Optional or required: required for I/O fencing
CFG{fencing_newdg_disks}
Defines the fencing disks.
List or scalar: list
Optional or required: required for I/O fencing
80
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{fencing_option}
Specifies the I/O fencing configuration mode.
The value is 2 for disk-based I/O fencing.
List or scalar: scalar
Optional or required: required for I/O fencing
CFG{fencing_scsi3_disk_policy}
Specifies the SCSI-3 disk policy to use I/O
fencing. The value is dmp.
List or scalar: scalar
Optional or required: required for I/O fencing
CFG{fencingenabled}
Defines whether fencing is enabled. The
value is 1 if enabled.
List or scalar: scalar
Optional or required: required for I/O fencing
CFG{keys}{"node_ip"}
Specifies the Veritas Access license for each
node.
List or scalar: scalar
Optional or required: required
CFG{newnodes}
Specifies the new access IP for the cluster
nodes. The value should be the first public
IP address for each node.
List or scalar: list
Optional or required: required
CFG{opt}{comcleanup}
Cleans up the ssh connection that is added
by the installer after the configuration. The
value is 1.
List or scalar: scalar
Optional or required: required
CFG{opt}{confignic}
Performs the NIC configuration with all the
network variable values. The value is 1.
List or scalar: scalar
Optional or required: required
81
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{opt}{configure}
Performs the configuration if the packages
are already installed.
List or scalar: scalar
Optional or required: required
CFG{opt}{install}
Installs Veritas Access RPMs. Configuration
can be performed at a later time using the
-configure option.
List or scalar: scalar
Optional or required: optional
CFG{opt}{installallpkgs}
Instructs the installer to install all the Veritas
Access RPMs based on the variable that
has the value set to 1.
List or scalar: scalar
Optional or required: required
CFG{opt}{noipc}
Disables the connection to SORT for
updates check. The value is 0.
List or scalar: scalar
Optional or required: required
CFG{opt}{ssh}
Determines whether to use ssh for
communication between systems. The value
is 1 if enabled.
List or scalar: scalar
Optional or required: required
CFG{opt}{updatekeys}
Updates the keyless license to the current
version.
List or scalar: scalar
Optional or required: optional
CFG{opt}{vfr}
Enables the VFR for Veritas Access. The
value is 1 if enabled.
List or scalar: scalar
Optional or required: required
82
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{opt}{vxkeyless}
Installs the product with a keyless license.
List or scalar: scalar
Optional or required: optional
CFG{prod}
Defines the product to be installed or
uninstalled.
List or scalar: scalar
Optional or required: required
CFG{publicbond}
List of PCI IDs of the bonded NICs.
List or scalar: list
Optional or required: optional
CFG{publicnetmaskarr}
List of netmasks that are assigned to public
NICs or bonds.
List or scalar: list
Optional or required: required
CFG{publicparr}
List of public IPs that are assigned to public
NICs or bonds.
List or scalar: list
Optional or required: required
CFG{redhat_subscription_username}
Specifies the user name to register with Red
Hat subscription management.
List or scalar: scalar
Optional or required: required if some
required OS rpms are missing on the
systems
The user name should be enclosed in single
quotes (for example : ‘1234@abc’) if it
contains any special character.
83
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{redhat_subscription_password}
Specifies the password to register with Red
Hat subscription management.
List or scalar: scalar
Optional or required: required if some
required OS rpms are missing on the
systems
The password should be enclosed in single
quotes (for example : ‘1234@abc’) if it
contains any special character.
CFG{snas_clustername}
Defines the cluster name of the product.
List or scalar: scalar
Optional or required: required
CFG{snas_consoleip}
Defines the console IP of the product.
List or scalar: scalar
Optional or required: required
CFG{snas_defgateway}
Defines the gateway of the product.
List or scalar: scalar
Optional or required: required
CFG{snas_dnsdomainname}
Defines the DNS domain name of the
product.
List or scalar: scalar
Optional or required: required
CFG{snas_dnsip}
Defines the DNS IP of the product.
List or scalar: scalar
Optional or required: required
CFG{snas_ntpserver}
Defines the NTP server name of the product.
List or scalar: scalar
Optional or required: required
84
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{snas_nvip}
Defines the number of VIPs on each NIC.
List or scalar: scalar
Optional or required: required
CFG{snas_pipprefix}
Defines the prefix of public IPs (only in IPV6
environments).
List or scalar: scalar
Optional or required: required
CFG{snas_pipstart}
Defines the the initial IP of the public IPs.
List or scalar: scalar
Optional or required: required
CFG{snas_pnmaskstart}
Defines the netmask of public IPs (only in
IPV4 environments).
List or scalar: scalar
Optional or required: required
CFG{snas_sepconsoleport}
Defines if use of separate console port. 1
for yes, 0 for no.
List or scalar: scalar
Optional or required: required
CFG{snas_vipprefix}
Defines the prefix of virtual IPs (only in IPV6
environments).
List or scalar: scalar
Optional or required: required
CFG{snas_vipstart}
Defines the the initial IP of the virtual IPs.
List or scalar: scalar
Optional or required: required
CFG{snas_vnmaskstart}
Defines the netmask of virtual IPs (only in
IPV4 environments).
List or scalar: scalar
Optional or required: required
85
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{systems}
List of systems on which the product is to
be installed or uninstalled.
List or scalar: list
Optional or required: required
CFG{vcs_allowcomms}
Indicates whether to start LLT or GAB when
the user wants to set up a single node
cluster.
List or scalar: scalar
Optional or required: required
CFG{vcs_clusterid}
Defines the unique cluser ID with a string
number.
List or scalar: scalar
Optional or required: required
CFG{vcs_clustername}
Defines the cluster name with a string.
List or scalar: scalar
Optional or required: required
CFG{vcs_lltlink<n>}{"new_node_ip"}
Defines the NIC name for the first heartbeat
link.
List or scalar: scalar
Optional or required: required
CFG{vcs_rdmalink1_address}{"new_node_ip"} Specifies the RDMA private link1 IP address,
the value follows that node_01 is
172.17.0.3, node_02 is 172.17.0.4,
and so on.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
CFG{vcs_rdmalink1_netmask}{"new_node_ip"} Specifies the RDMA private link1 IP
netmask, the value is 255.255.255.0.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
86
Automating Veritas Access installation and configuration using response files
Response file variables to install and configure Veritas Access
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{vcs_rdmalink1_port}{"new_node_ip"}
Specifies the port number for the RDMA
private link1, the value is 51001.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
CFG{vcs_rdmalink2_address}{"new_node_ip"} Specifies the RDMA private link2 IP address,
the value follows that node_01 is
172.16.1.3, node_02 is 172.16.1.4,
and so on.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
CFG{vcs_rdmalink2_netmask}{"new_node_ip"} Specifies the RDMA private link2 IP
netmask, the value is 255.255.255.0.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
CFG{vcs_rdmalink2_port}{"new_node_ip"}
Specifies the port number for the RDMA
private link2, the value is 51002.
List or scalar: scalar
Optional or required: required for RDMA
NICs as private NICs
CFG{vcs_userenpw}
Defines the encrypted user password.
List or scalar: scalar
Optional or required: required
CFG{vcs_username}
Defines the added username for VCS.
List or scalar: scalar
Optional or required: required
CFG{vcs_userpriv}
Defines the user privilege.
List or scalar: scalar
Optional or required: required
87
Automating Veritas Access installation and configuration using response files
Sample response file for Veritas Access installation and configuration
Table 5-1
Response file variables for installing Veritas Access (continued)
Variable
Description
CFG{virtualiparr}
List of virtual IPs that will be assigned to
public NICs or bonds.
List or scalar: list
Optional or required: required
CFG{virtualnetmaskarr}
List of netmasks that will be assigned to
public NICs or bonds.
List or scalar: list
Optional or required: required
Sample response file for Veritas Access
installation and configuration
The following example shows a response file for installing and configuring Veritas
Access.
####################################################
our %CFG;
#Installs Product packages.
$CFG{opt}{install}=1;
$CFG{opt}{installallpkgs}=1;
$CFG{opt}{updatekeys}=1;
$CFG{opt}{comsetup}=1;
$CFG{opt}{noipc}=1;
$CFG{opt}{ssh}=1;
$CFG{opt}{vxkeyless}=1;
$CFG{opt}{vfr}=1;
$CFG{prod}="SNAS72";
#Performs the configuration if the packages are already installed
$CFG{opt}{configure}=1;
#the PCI IDs of slave NICs
$CFG{bondpool}{bond0}=[ qw(0000:02:09.0 0000:02:07.0) ];
$CFG{bondpool}{bond1}=[ qw(0000:02:04.0 0000:02:08.0) ];
#mode of each bond
$CFG{bondmode}{bond0}=5;
88
Automating Veritas Access installation and configuration using response files
Sample response file for Veritas Access installation and configuration
89
$CFG{bondmode}{bond1}=6;
#names of bond
$CFG{bondname}=[ qw(bond0 bond1) ];
#the PCI IDs of excluded NICs
$CFG{exclusion}=[ qw(0000:02:03.0 0000:02:0a.0) ];
#the PCI IDs of all the bonded NICs
$CFG{publicbond}=[ qw(0000:02:03.0 0000:02:04.0 0000:02:07.0
0000:02:08.0) ];
#public IPs
$CFG{publiciparr}=[ qw(10.200.58.100 10.200.58.101 10.200.58.102
10.200.58.103 10.200.58.104 10.200.58.105 10.200.58.106 10.200.58.107) ];
#netmask for public IPs
$CFG{publicnetmaskarr}=[ qw(255.255.255.0 255.255.255.0 255.255.255.0
255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0) ];
#the user name to register with Red Hat subscription management
$CFG{redhat_subscription_username}="rhel_user";
#the password to register with Red Hat subscription management
$CFG{redhat_subscription_password}="rhel_password";
#clustername of SNAS
$CFG{snas_clustername}="testsnas";
#console IP of SNAS
$CFG{snas_consoleip}="10.200.58.220";
#default gateway of SNAS
$CFG{snas_defgateway}="10.200.58.1";
#domain name of DNS
$CFG{snas_dnsdomainname}="cdc.veritas.com";
#IP of DNS
$CFG{snas_dnsip}="10.200.58.3";
#NTP server name
$CFG{snas_ntpserver}="ntp.veritas.com";
Automating Veritas Access installation and configuration using response files
Sample response file for Veritas Access installation and configuration
90
#number of VIPs on each NIC
$CFG{snas_nvip}=1;
#netmask of public IPs(only ipv4 environment)
$CFG{snas_pnmaskstart}=255.255.255.0;
#the initial IP of public IPs
$CFG{snas_pipstart}="10.200.58.100";
#if use separate console port, 1 for yes, 0 for no
$CFG{snas_sepconsoleport}="0";
#netmask of virutal IPs(only ipv4 environment)
$CFG{snas_vnmaskstart}=255.255.255.0;
#the initial IP of virtual IPs
$CFG{snas_vipstart}="10.200.58.108";
#virtual IPs
$CFG{virtualiparr}=[ qw(10.200.58.108 10.200.58.109
10.200.58.110 10.200.58.111 10.200.58.112
10.200.58.113 10.200.58.114 10.200.58.115) ];
#netmask for virual IPs
$CFG{virtualnetmaskarr}=[ qw(255.255.255.0 255.255.255.0 255.255.255.0
255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0) ];
#target systems
$CFG{systems}=[ qw(10.200.58.66 10.200.58.82) ];
#indicates whether to start llt/gab when user wants to setup a single
node cluster
$CFG{vcs_allowcomms}=1;
#define the unique cluser id with a string number
$CFG{vcs_clusterid}=325;
#define the cluster name with a string
$CFG{vcs_clustername}="testsnas";
#define the nic name for the first heartbeat link.
$CFG{vcs_lltlink1}{"10.200.58.100"}="priveth0";
Automating Veritas Access installation and configuration using response files
Sample response file for Veritas Access installation and configuration
$CFG{vcs_lltlink1}{"10.200.58.104"}="priveth0";
$CFG{vcs_lltlink2}{"10.200.58.100"}="priveth1";
$CFG{vcs_lltlink2}{"10.200.58.104"}="priveth1";
#define the encrypted user password
$CFG{vcs_userenpw}=[ qw(GPQiPKpMQlQQoYQkPN) ];
#define the added username for VCS
$CFG{vcs_username}=[ qw(admin) ];
#define the user privilege
$CFG{vcs_userpriv}=[ qw(Administrators) ];
1;
####################################################
91
Chapter
6
Displaying and adding
nodes to a cluster
This chapter includes the following topics:
■
About the Veritas Access installation states and conditions
■
Displaying the nodes in the cluster
■
Before adding new nodes in the cluster
■
Adding a node to the cluster
■
Deleting a node from the cluster
■
Shutting down the cluster nodes
About the Veritas Access installation states and
conditions
Table 6-1 describes the Veritas Access installation states.
Table 6-1
Veritas Access installation states
Installation
state
Description
RUNNING
Node is part of the cluster and the Veritas Access processes are running
on it.
FAULTED
Node is down and/or the Veritas Access processes are not running on
it.
LEAVING
Node is leaving the cluster gracefully
Displaying and adding nodes to a cluster
Displaying the nodes in the cluster
Table 6-1
Veritas Access installation states (continued)
Installation
state
Description
EXITED
Node has exited the cluster gracefully
UNKNOWN
Exact state of the node cannot be determined
Depending on the cluster condition as described in Table 6-2, output for the
Cluster> show command changes.
Table 6-2
Condition
Cluster conditions and states
Description
If the node is configured and State displays as FAULTED, and there is no installation state
part of the cluster, but the
or network statistics.
node is powered off.
If the node is configured and State displays as FAULTED, and there is no installation state
part of the cluster, but the
or network statistics.
node is physically removed
from the cluster.
If the node is configured and State changes from LEAVING to EXITED.
part of the cluster, but the
node is shutdown using the
Cluster> shutdown
command.
If the node is configured and Node is deleted from the cluster, and information about the
part of the cluster, and you
deleted node is no longer available.
use the Cluster> del
command.
Displaying the nodes in the cluster
You can display all the nodes in the cluster, their states, CPU load, and network
load during the past 15 minutes.
If you use the Cluster> show currentload option, you can display the CPU and
network loads collected from now to the next five seconds.
93
Displaying and adding nodes to a cluster
Displaying the nodes in the cluster
94
To display a list of nodes in the cluster
1
To display a list of nodes that are part of a cluster, and the systems that are
available to add to the cluster, enter the following:
Cluster> show
Command output includes the following information. See examples below.
Node
Displays the node name if the node has already been added to
the cluster. Displays the IP address of the node if it is still in the
process of being added to the cluster.
Example:
node_01
or
10.200.58.202
State
Displays the state of the node or the installation state of the system
along with an IP address of the system if it is installed.
See “About the Veritas Access installation states and conditions”
on page 92.
2
CPU
Indicates the CPU load.
pubethX
Indicates the network load for the Public Interface X.
bondX
Indicates the network load for bond NIC X.
For nodes already in the cluster, the following is displayed:
Node
State
-----snas_01
snas_02
------RUNNING
RUNNING
CPU(15 min) pubeth0(15 min)
%
rx(MB/s) tx(MB/s)
----------- -------- -------1.35
0.00
0.00
1.96
0.00
0.00
pubeth1(15 min)
rx(MB/s) tx(MB/s)
-------- -------0.00
0.00
0.00
0.00
Displaying and adding nodes to a cluster
Before adding new nodes in the cluster
3
95
For the nodes that are being added to the cluster, for the nodes that are being
deleted from the cluster, and for the nodes that is getting upgraded, the following
progress is displayed:
Nodes in Transition
Node/IP
Operation
State
Description
------
---------
-----
-----------
10.200.58.202
Add node
FAILED
Installing packages
snas_03
Delete node
ONGOING
Removing node
snas_01,snas_02
Rolling upgrade ONGOING
Rolling upgrade phase 2
Note: The add node and delete node operations cannot be performed at the
same time.
4
To display the CPU and network loads collected from now to the next five
seconds, enter the following:
Cluster> show currentload
Example output:
Node
State
---snas_01
snas_02
snas_03
----RUNNING
RUNNING
RUNNING
CPU(5 sec)
%
---------0.26
0.87
10.78
pubeth0(5 sec)
pubeth1(5 sec)
rx(MB/s) tx(MB/s) rx(MB/s) tx(MB/s)
-------- -------- -------- -------0.01
0.00
0.01
0.00
0.01
0.00
0.01
0.00
27.83
12.54
0.01
0.00
Statistics for network interfaces are shown for each public interface available
on the cluster nodes.
Before adding new nodes in the cluster
After you have installed the operating system, you can install and configure a multiple
node Veritas Access cluster at one time. If you want to add additional nodes to the
cluster after that, you need to complete the following procedures:
Displaying and adding nodes to a cluster
Before adding new nodes in the cluster
■
Install the appropriate operating system software on the additional nodes.
See “Installing the operating system on each node of the cluster” on page 42.
■
Disable SELinux on the new node.
■
You do not need to install the Veritas Access software on the additional node
before you add the node. The Veritas Access software is installed when you
add the nodes. If the Veritas Access software is already installed, it is uninstalled
and the product (same version as the cluster) is installed after that. The reason
to uninstall and then install the product is to make sure that the new node is
installed with exactly the same version, and patch level (if any) as the other
cluster nodes. The packages are stored in the cluster nodes so the product
image is not needed during the addition of the new node.
■
Verify that the existing cluster has sufficient physical IP addresses for the new
nodes. You can add additional IP addresses with the CLISH command: .
96
Network> ip addr add command
For example:
Network> ip addr add 10.200.58.107 255.255.252.0 physical
ACCESS ip addr SUCCESS V-288-1031 ip addr add successful.
Network> ip addr show
IP
-10.200.58.101
10.200.58.102
10.200.58.103
10.200.58.104
10.200.58.105
10.200.58.107
10.200.58.231
10.200.58.62
10.200.58.63
10.200.58.64
Netmask/Prefix
-------------255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
Device
-----pubeth0
pubeth1
pubeth0
pubeth1
pubeth0
pubeth1
pubeth1
pubeth1
Node
Type
Status
-----------snas_01
Physical
snas_01
Physical
snas_02
Physical
snas_02
Physical
( unused ) Physical
( unused ) Physical
snas_01
Virtual ONLINE (Con IP)
snas_01
Virtual ONLINE
snas_01
Virtual ONLINE
snas_01
Virtual
In the example the unused IP addresses 10.200.58.105, and 10.200.58.107
can be used by the new node as physical IP addresseses.
■
If you want to add nodes to a cluster that has RDMA-based LLT links, disable
iptables on the cluster nodes using the service iptables stop command.
For example:
# service iptables stop
iptables: Setting chains to policy ACCEPT: filter
[
OK
]
Displaying and adding nodes to a cluster
Adding a node to the cluster
iptables: Flushing firewall rules:
iptables: Unloading modules:
[
[
OK
OK
Note: Before proceeding, make sure that all of the nodes are physically
connected to the private and public networks.
■
Add the node to your existing cluster.
See “Adding a node to the cluster” on page 97.
Adding a node to the cluster
The operating system has to be installed on the nodes before you add nodes to a
cluster.
If you use disk-based fencing, the coordinator disks must be visible on the newly
added node as a prerequisite for I/O fencing to be configured successfully. Without
the coordinator disks, I/O fencing will not load properly and the node will not be
able to obtain cluster membership.
If you use majority-based fencing, the newly added node doesn't have to have
shared disks.
If you want to add a new node and want to exclude some unique PCI IDs, add the
unique PCI IDs to the /opt/SYMCsnas/conf/net_exclusion_dev.conf file on each
cluster node manually. For example:
[root@bob_01 ~]# cat /opt/SYMCsnas/conf/net_exclusion_dev.conf
0000:42:00.0 0000:42:00.1
Note: Writeback cache is supported for two-node clusters only, so adding nodes
to a two-node cluster changes the caching to read-only.
Note: Newly added nodes should have the same configuration of InfiniBand NICs.
See “About using LLT over the RDMA network for Veritas Access” on page 27.
If your cluster has a configured the FSS pool, and the FSS pool's node group is
missing a node, then the newly added node is added into the FSS node group, and
the installer adds the new node's local data disks into the FSS pool.
To add the new node to the cluster
1
Log in to Veritas Access using the master or the system-admin account.
2
In CLISH, enter the Cluster command to enter the Cluster> mode.
97
]
]
Displaying and adding nodes to a cluster
Adding a node to the cluster
3
To add the new nodes to the cluster, enter the following:
Cluster> add node1ip, node2ip.....
where node1ip, node2ip, .... are the IP address list of the additional nodes for
the ssh connection.
It is important to note that:
■
The node IPs should not be the IPs which are allocated to the new nodes
as physical IPs or virtual IPs.
■
The physical IPs of new nodes are usable IPs found from the configured
public IP starting addresses.
■
The virtual IPs are re-balanced to the new node but additional virtual IPs
are not assigned.
Go to step 7 to add new virtual IP addresses to the cluster after adding a
node.
■
The IPs that are accessible to the new nodes should be given.
■
The accessible IPs of the new nodes should be in the public network, they
should be able to ping the public network's gateway successfully.
For example:
Cluster> add 10.200.114.56
4
When you add nodes to a two-node cluster and writeback caching is enabled,
the installer asks the following question before adding the node:
CPI WARNING V-9-30-2164 Adding a node to a two-node cluster
that has writeback caching enabled will change the caching
to read-only. Writeback caching is only supported for two nodes.
Do you want to continue adding new node(s)? [y,n,q](n)
Enter y to continue adding the node. Enter n to exit from the add node
procedure.
5
If a cache exists on the original cluster, the installer prompts you to choose the
ssd disks to create cache on the new node when CFS is mounted.
1) emc_clariion1_242
2) emc_clariion1_243
b) Back to previous menu
Choose disks separate by spaces to create cache on 10.198.89.164
[1-2,b,q] 1
Create cache on snas_02 .....................Done
98
Displaying and adding nodes to a cluster
Adding a node to the cluster
6
If the cluster nodes have created FSS pool, and there are more than two local
data disks on the new node, the installer asks you to select the disks to add
into the FSS pool. Make sure that you select at least two disks for stripe volume
layout. The total selected disk size should be no less than the FSS pool’s
capacity size.
Following storage pools need to add disk from the new node:
1) fsspool1
2) fsspool2
3) Skip this step
Choose a
1)
2)
3)
4)
b)
pool to add disks [1-3,q] 1
emc_clariion0_1570 (5.000 GB)
installres_03_sdc (5.000 GB)
installres_03_sde (5.000 GB)
sdd (5.000 GB)
Back to previous menu
Choose at least 2 local disks with minimum capacity of 10 GB [1-4,b,q] 2 4
Format disk installres_03_sdc,sdd ................................ Done
The disk name changed to installres_03_sdc,installres_03_sdd
Add disk installres_03_sdc,installres_03_sdd to storage pool fsspool1
7
Done
If required, add the virtual IP addresses to the cluster. Adding the node does
not add new virtual IP addresses or service groups to the cluster.
To add additional virtual IP addresses, use the following command in the
Network mode:
Network> ip addr add ipaddr virtual
For example:
Network> ip addr add 10.200.58.66 255.255.252.0 virtual
ACCESS ip addr SUCCESS V-288-1031 ip addr add successful.
If a problem occurs while you are adding a node to a cluster (for example, if the
node is temporarily disconnected from the network), do the following to fix the
problem:
To recover the node:
■
Power off the node.
99
Displaying and adding nodes to a cluster
Deleting a node from the cluster
■
Use the Cluster> del nodename command to delete the node from the cluster.
■
Power on the node.
■
Use the Cluster> add nodeip command to add the node to the cluster.
Deleting a node from the cluster
This command deletes a node from the cluster. Use the node name that is displayed
in the Cluster> show command.
Note: This command is not supported in a single-node cluster.
If the deleted node was in the RUNNING state prior to deletion, after you reboot
the node, that node is assigned to the original IP address that can be used to add
the node back to the cluster. The original IP address of the node is the IP address
that the node used before it was added into the cluster.
If your cluster has configured a FSS pool, you cannot use the installer to delete
nodes that would result in a single node in the node group of the FSS pool.
Deleting a node from a two-node cluster that has writeback caching enabled changes
the caching to read-only. Writeback caching is only supported for two nodes.
The IP address that was used by the node before it was deleted from the cluster
is still accessible until you perform a restart operation.
After the node is deleted from the cluster and you perform a reboot operation, the
IP addresses associated with the node are free for use by the cluster for new nodes.
100
Displaying and adding nodes to a cluster
Deleting a node from the cluster
To delete a node from the cluster
1
To show the current state of all nodes in the cluster, enter the following:
Cluster> show
2
To delete a node from a cluster, enter the following:
Cluster> del nodename
where nodename is the node name that appeared in the listing from the
Cluster> show command. You cannot specify a node by its IP address.
For example:
Cluster> del snas_01
3
After a node is deleted from the cluster, the physical IP addresses that it used
are marked as unused physical IP addresses. The IP addresses are available
for use if you add new nodes. The virtual IP addresses used by a node which
has been deleted are not removed. Deleting a node moves the virtual IP
addresses on the deleted node to the remaining nodes in the cluster.
For example:
Network> ip addr show
IP
-10.209.86.232
10.209.86.233
10.209.86.234
10.209.86.235
10.209.86.240
10.209.86.236
10.209.86.237
10.209.86.238
10.209.86.239
Netmask/Prefix
-------------255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
255.255.252.0
Device
-----pubeth0
pubeth1
pubeth0
pubeth0
pubeth0
pubeth1
pubeth1
Node
---source_30a_01
source_30a_01
( unused )
( unused )
source_30a_01
source_30a_01
source_30a_01
source_30a_01
source_30a_01
Type
---Physical
Physical
Physical
Physical
Virtual
Virtual
Virtual
Virtual
Virtual
Status
------
ONLINE (Con IP)
ONLINE
ONLINE
ONLINE
ONLINE
If the physical or virtual IP addresses are not going to be used, they can be
removed using the following command:
Network> ip addr del ipaddr
For example:
Network> ip addr del 10.209.86.234
ACCESS ip addr SUCCESS V-288-1031 ip addr del successful.
101
Displaying and adding nodes to a cluster
Shutting down the cluster nodes
Note: If the cluster has configured NIC bonding, you also need to delete the
configuration of the deleted node on the switch.
Shutting down the cluster nodes
You can shut down a single node or all of the nodes in the cluster. Use the node
name that is displayed in the Cluster> show command.
To shut down a node or all the nodes in a cluster
1
To shut down a node, enter the following:
Cluster> shutdown nodename
nodename indicates the name of the node you want to shut down. You cannot
specify a node by its IP address.
For example:
Cluster> shutdown snas_04
Stopping Cluster processes on snas_04
Sent shutdown command to snas_04. SSH sessions to
snas_04 may terminate.
2
To shut down all of the nodes in the cluster, enter the following:
Cluster> shutdown all
Use all as the nodename to shut down all of the nodes in the cluster.
For example:
Cluster> shutdown all
Stopping Cluster processes on all
SSH sessions to all nodes may terminate.
Sent shutdown command to snas_02
Sent shutdown command to snas_03
Sent shutdown command to snas_04
Sent shutdown command to snas_01
102
Chapter
7
Upgrading Veritas Access
This chapter includes the following topics:
■
About types of Veritas Access patches
■
Downloading Veritas Access 7.2 release
■
Upgrading to Veritas Access 7.2 release
■
About upgrading Veritas Access patches
■
Displaying the current version of Veritas Access
■
Displaying upgrade history of Veritas Access
■
Downloading an Veritas Access patch release
■
Displaying all Veritas Access releases that are available in the repository
■
About installing patches
■
Installing Veritas Access patches
■
Automatically execute your customized script before or after upgrade
■
Uninstalling patches
■
Synchronizing software upgrades on a node
About types of Veritas Access patches
Depending on whether a patch requires a restart of the cluster or not, the Veritas
Access patches can be divided into two types:
■
Patches that do not require a cluster restart.
These patches upgrade the Veritas Access packages and non-critical packages
using the direct upgrade method. The direct upgrade method does not bring
Upgrading Veritas Access
Downloading Veritas Access 7.2 release
down any nodes or resources while the patch is applied. The upgrade applies
the patch on all the nodes in parallel. The cluster remains in a RUNNING state
and clients are served while the upgrade process is running.
■
Patches that require a cluster restart.
These patches upgrade the critical packages that require a one-time cluster
restart using the rolling upgrade method. You can use the rolling upgrade method
to install the Veritas Access releases in a guided manner on all the clusters
nodes. The rolling upgrade minimizes downtime for highly available clusters by
limiting the upgrade time to the amount of time that it takes to perform a service
group failover
Note: Updating these patches on a single node cluster causes service downtime,
because both the kernel RPMs and VCS agent RPMs are upgraded in a single
phase.
The rolling upgrade has two main phases. The installer upgrades kernel RPMs
in phase 1 and VCS agent RPMs in phase 2. The upgrade process divides the
cluster into two subclusters, called the first subcluster and the second subcluster.
First, the upgrade is performed on the first subcluster. The upgrade process
stops all services and resources on the nodes of the first subcluster. All services
(including the VIP groups) fail over to the second subcluster. During the failover
process, the clients that are connected to the VIP groups of the first subcluster
nodes are intermittently interrupted. For those clients that do not time out, the
service is resumed after the VIP groups become online on one of the nodes of
the second subcluster.
While the upgrade process is running on the nodes of the first subcluster, the
nodes of the second subcluster nodes continue to serve the clients. After the
first subcluster node has been upgraded, it restarts the services and resources
on first stage nodes. Immediately after the first subcluster comes up, the upgrade
process stops the services and resources on the remaining nodes. All services
and resources are online and serve clients. Meanwhile, the rolling upgrade starts
the upgrade process on the remaining nodes. After the upgrade is complete on
the remaining nodes, the cluster recovers and services are balanced across the
cluster.
Downloading Veritas Access 7.2 release
You can download Veritas Access 7.2 and store it in the repository using the
Upgrade> get command. To download Veritas Access 7.2 and place it in the
repository:
104
Upgrading Veritas Access
Upgrading to Veritas Access 7.2 release
■
To download the Veritas Access patch release and place it in the repository,
enter the following:
Upgrade> get URL
where URL is the URL location from where you can download the software. The
URL supports HTTP, FTP, and SCP protocols for download. The user name
and password for the HTTP and FTP protocols are also supported.
For example:
You can download the Veritas Access release from an HTTP server with
authentication from http://admin@veritas.example.com/VA7.2.0.0.tar.gz.
Upgrade> get http://admin@veritas.example.com/VA7.2.0.0.tar.gz
Upgrading to Veritas Access 7.2 release
You can use the Upgrade> install 7.2.0.0 to upgrade to Veritas Access 7.2
from older release on your system.
To Upgrade to Veritas Access 7.2 on your system
1
Make sure that the Veritas Access 7.2 is available in the repository. You can
use the Upgrade> repository command to view the release that are available
on the cluster node.
See “Displaying all Veritas Access releases that are available in the repository”
on page 107.
2
If Veritas Access 7.2 does not display, download it. You can use the Upgrade>
get command to download the Veritas Access 7.2 and place it in the repository.
See “Downloading Veritas Access 7.2 release” on page 104.
About upgrading Veritas Access patches
The Veritas Access Upgrade> mode commands perform a direct upgrade or a
guided rolling upgrade on all of the cluster nodes based on the patch type. Before
you perform an upgrade, ensure that all the cluster nodes are in RUNNING state and
have the same Veritas Access software version. If one of the nodes has a lower
version, you need to upgrade the software version for that node. To upgrade the
version, delete the node from the cluster, upgrade the node, and add it back to the
cluster.
See “Adding a node to the cluster” on page 97.
See “Deleting a node from the cluster” on page 100.
To access the Upgrade> mode commands, log into the administrative console (for
master or system-admin) and enter the Upgrade> mode.
105
Upgrading Veritas Access
Displaying the current version of Veritas Access
Note: To avoid potential upgrade issues, stop all workloads from clients, and then
re-initiate the upgrade.
Displaying the current version of Veritas Access
You can display the current version of Veritas Access and the patch level using the
Upgrade> version command.
To display the current version of Veritas Access
◆
To display the current version of Veritas Access and the patch level, enter the
following:
Upgrade> version
For example:
Upgrade> version
ACCESS 7.2.0.0
(Mon Apr 18 07:04:07 2016)
Displaying upgrade history of Veritas Access
You can display the upgrade history of Veritas Access using the Upgrade> history
command.
To display the upgrade history of Veritas Access
◆
To display the upgrade history of Veritas Access, enter the following:
Upgrade> history
For example:
Upgrade> history
ACCESS 7.1.0.0
(Mon Apr 18 07:04:07 2016),
Installed on Sat May 14 19:24:17 EDT 2016
Downloading an Veritas Access patch release
You can download an Veritas Access patch release and store it in the repository
according to the patch type using the Upgrade> get command.
106
Upgrading Veritas Access
Displaying all Veritas Access releases that are available in the repository
To download the Veritas Access patch release and place it in the repository
◆
To download the Veritas Access patch release and place it in the repository,
enter the following:
Upgrade> get URL
where URL is the URL location from where you can download the software
patch. The URL supports HTTP, FTP, and SCP protocols for download. The
user name and password for the HTTP and FTP protocols are also supported.
For example:
You can download the Veritas Access release from an HTTP server with
authentication from http://admin@veritas.example.com/VA7.2.0.0.tar.gz
Upgrade> get http://admin@veritas.example.com/VA7.2.0.0.tar.gz
Note: The patch release is distributed to all RUNNING nodes in the cluster after
the patch is downloaded.
Displaying all Veritas Access releases that are
available in the repository
You can display all the patch releases that are available in the repository using the
Upgrade> repository command.
To display all Veritas Access releases that are available in the repository
◆
To display all Veritas Access releases that are available in the repository, enter
the following:
Upgrade> repository
For example:
Upgrade> repository
ACCESS VERSION| INSTALLED(y/n)| UPGRADABLE(y/n)
7.2.0.0
n
y
7.1.0.0
y
n
107
Upgrading Veritas Access
About installing patches
About installing patches
Table 7-1
Patch commands
Command
Definition
patch install
Downloads the patch from a specified URL and install it on all of the
nodes. The Upgrade> patch install command first synchronizes
the nodes that have different software versions compared to the other
nodes.
Note: After you have installed, uninstalled, or synchronized a new
Veritas Access patch into your cluster, the list of available commands
may have changed. Please re-login to the CLI to access the updated
features.
See “Installing Veritas Access patches” on page 108.
patch
uninstall-upto
Uninstalls the software upgrade from all of the nodes up to the specified
version. You must specify the versions of software up to the version
that you want to uninstall. This command first synchronizes the nodes
that have different software versions compared to other nodes in the
cluster.
See “Installing Veritas Access patches” on page 108.
patch sync
Forcefully synchronizes the specified node, bringing it up to the currently
installed software version of the remaining nodes in the cluster.
You only need to install the patch on one node, and then run the
Upgrade> patch sync command to synchronize all of the nodes.
See “Installing Veritas Access patches” on page 108.
Installing Veritas Access patches
You can use the Upgrade> install to install the latest Veritas Access patch on
your system.
108
Upgrading Veritas Access
Installing Veritas Access patches
To install the latest patches on your system
1
Make sure that the patch you want to install is available in the repository. You
can use the Upgrade> repository command to view the patch releases that
are available on the cluster node
See “Displaying all Veritas Access releases that are available in the repository”
on page 107.
2
If the release you want to install does not display, download the patch release.
You can use the Upgrade> get command to download the Veritas Access
patch release and place it in the repository.
See “Downloading an Veritas Access patch release” on page 106.
109
Upgrading Veritas Access
Installing Veritas Access patches
3
110
To install the latest patches, enter the following:
Upgrade> install version
where <version> is the Veritas Access patch version you want to install. The
patch should be already downloaded and stored in the repository.
An example of a patch upgrade that does not require a cluster restart:
Upgrade> install 7.2.0.0
Veritas Access 7.2 Upgrade Program
Copyright (c) 2016 Veritas Technologies LLC. All rights reserved. Verita
and the Veritas Logo are trademarks or registered trademarks of Veritas
Technologies LLC or its affiliates in the U.S. and other countries. Other
names may be trademarks of their respective owners.
The Licensed Software and Documentation are deemed to be "commercial
computer software" and "commercial computer software documentation" as
defined in FAR Sections 12.212 and DFARS Section 227.7202.
Logs are being written to /var/tmp/installaccess-201610031759uxY while
installaccess is in progress.
Veritas Access 7.2 Upgrade Program
isaA_01 isaA_02
Logs are being written to /var/tmp/installaccess-201610031759uxY while
installaccess is in progress
Verifying systems: 100%
Estimated time remaining: (mm:ss) 0:00
7 of 7
Checking system communication ................................. Done
Checking release compatibility ................................ Done
Checking installed product .................................... Done
Checking platform version ..................................... Done
Checking prerequisite patches and rpms ...................... Failed
Checking file system free space ............................... Done
Performing product prechecks .................................. Done
System verification checks completed
Upgrading Veritas Access
Installing Veritas Access patches
111
The systems give the following warnings:
CPI WARNING V-9-30-1650 The supported version of openssl is
1.0.1e-48.el6_8.1. Its current version on isaA_01 is 1.0.1e-42.el6. Upgrad
the openssl version before you proceed
CPI WARNING V-9-30-1650 The supported version of openssl-devel is
1.0.1e-48.el6_8.1. Its current version on isaA_01 is 1.0.1e-42.el6. Upgrad
the openssl-devel version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd is 2.2.15-54.el6_8.
Its current version on isaA_01 is 2.2.15-45.el6. Upgrade the httpd version
before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-devel is
2.2.15-54.el6_8. Its current version on isaA_01 is 2.2.15-45.el6. Upgrade
the httpd-devel version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-manual is
2.2.15-54.el6_8. Its current version on isaA_01 is 2.2.15-45.el6. Upgrade
the httpd-manual version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-tools is
2.2.15-54.el6_8. Its current version on isaA_01 is 2.2.15-45.el6. Upgrade
the httpd-tools version before you proceed
CPI WARNING V-9-30-1650 The supported version of mod_ssl is 2.2.15-54.el6_
Its current version on isaA_01 is 2.2.15-45.el6. Upgrade the mod_ssl versi
before you proceed
CPI WARNING V-9-30-1651 The following required OS rpms were not found on
isaA_01:
openssl-1.0.1e-48.el6_8.1 openssl-devel-1.0.1e-48.el6_8.1
httpd-2.2.15-54.el6_8 httpd-devel-2.2.15-54.el6_8
httpd-manual-2.2.15-54.el6_8 httpd-tools-2.2.15-54.el6_8
mod_ssl-2.2.15-54.el6_8
CPI WARNING V-9-30-1652 The following required third party rpms or their
higher version were not found on isaA_01:
ctdb samba-common samba-libs samba-client samba-winbind samba
samba-winbind-clients samba-winbind-krb5-locator samba-winbind-modules
nfs-ganesha nfs-ganesha-vxfs psutil python-crontab libuv
Upgrading Veritas Access
Installing Veritas Access patches
112
CPI WARNING V-9-30-1650 The supported version of openssl is
1.0.1e-48.el6_8.1. Its current version on isaA_02 is 1.0.1e-42.el6. Upgrad
the openssl version before you proceed
CPI WARNING V-9-30-1650 The supported version of openssl-devel is
1.0.1e-48.el6_8.1. Its current version on isaA_02 is 1.0.1e-42.el6. Upgrad
the openssl-devel version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd is 2.2.15-54.el6_8.
Its current version on isaA_02 is 2.2.15-45.el6. Upgrade the httpd version
before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-devel is
2.2.15-54.el6_8. Its current version on isaA_02 is 2.2.15-45.el6. Upgrade
the httpd-devel version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-manual is
2.2.15-54.el6_8. Its current version on isaA_02 is 2.2.15-45.el6. Upgrade
the httpd-manual version before you proceed
CPI WARNING V-9-30-1650 The supported version of httpd-tools is
2.2.15-54.el6_8. Its current version on isaA_02 is 2.2.15-45.el6. Upgrade
the httpd-tools version before you proceed
CPI WARNING V-9-30-1650 The supported version of mod_ssl is 2.2.15-54.el6_
Its current version on isaA_02 is 2.2.15-45.el6. Upgrade the mod_ssl versi
before you proceed
CPI WARNING V-9-30-1651 The following required OS rpms were not found on
isaA_02:
openssl-1.0.1e-48.el6_8.1 openssl-devel-1.0.1e-48.el6_8.1
httpd-2.2.15-54.el6_8 httpd-devel-2.2.15-54.el6_8
httpd-manual-2.2.15-54.el6_8 httpd-tools-2.2.15-54.el6_8
mod_ssl-2.2.15-54.el6_8
CPI WARNING V-9-30-1652 The following required third party rpms or their
higher version were not found on isaA_02:
ctdb samba-common samba-libs samba-client samba-winbind samba
samba-winbind-clients samba-winbind-krb5-locator samba-winbind-modules
nfs-ganesha nfs-ganesha-vxfs psutil python-crontab libuv
The installer provides some guidance on installing OS rpms using native
Upgrading Veritas Access
Installing Veritas Access patches
113
methods, like yum, and manually installing the required OS rpms.
Some of the required OS rpms only exist on Red Hat public YUM repositories
it is required to set up Red Hat subscription first to install these OS
rpms.
The installation may take a few minutes.
Installing the required OS rpms ............................... Done
System verification checks completed successfully
The systems discovered the following information:
CPI NOTE V-9-30-1405 ACCESS version 7.1.0.0 will be upgraded to ACCESS
version 7.2.0.000 on isaA_01
CPI NOTE V-9-30-1405 ACCESS version 7.1.0.0 will be upgraded to ACCESS
version 7.2.0.000 on isaA_02
Checking release compatibility on isaA_01 ..................... Done
Checking rolling upgrade prerequisites on isaA_01 ............. Done
Checking service group status on isaA_01 ...................... Done
Checking release compatibility on isaA_02 ..................... Done
Checking rolling upgrade prerequisites on isaA_02 ............. Done
Checking service group status on isaA_02 ...................... Done
The following service group(s) are online in the cluster:
Service Groups Online on isaA_01: CanHostConsole CanHostNLM
ManagementConsole Phantomgroup_pubeth0 Phantomgroup_pubeth1 RESTgroup
ReconfigGroup TCPConnTrack VIPgroup1 VIPgroup3 cvm iSCSI_INIT
Service Groups Online on isaA_02: CanHostConsole CanHostNLM NLMGroup
Phantomgroup_pubeth0 Phantomgroup_pubeth1 ReconfigGroup TCPConnTrack
VIPgroup2 VIPgroup4 cvm iSCSI_INIT
The upgrade has started. Run 'cluster show' to see the progress of the
upgrade. Upgrade details are saved at /opt/SYMCsnas/log/upgrade_output.
installaccess log files and summary file are saved at:
/opt/VRTS/install/logs/installaccess-201610031759uxY
Upgrading Veritas Access
Automatically execute your customized script before or after upgrade
114
Automatically execute your customized script
before or after upgrade
An interface is provided to automatically perform customized script before or after
the upgrade. Put your executable script in the specified folder for the auto-execution.
If you want the script to be run before the upgrade
1
Create a folder /var/tmp/prestop on the master node.
2
Copy the script into the folder.
3
If the script exits with error (exit code of the script executing is not zero), you
are prompted to confirm whether to continue the upgrade:
CPI WARNING V-9-0-0 Prestop script /var/tmp/prestop/test.sh failed \
to be executed on test_02, the return code is 2.
Do you want to continue? [y,n,q]
If you want the script to be run after the upgrade
1
Create a folder /var/tmp/poststart on the master node.
2
Copy the script into the folder.
3
If the script exits with error (exit code of the script executing is not zero), you
can see a warning message similar to the following:
CPI WARNING V-9-0-0 Poststart script /var/tmp/poststart/test.sh \
failed to be executed on test_02, the return code is 2.
The script would be automatically copied to other nodes and executed on each
node.
Note that there should be only one executable script in the /var/tmp/prestop or
/var/tmp/poststart folder, otherwise the upgrade fails with the following error
messages:
CPI ERROR V-9-0-0 Don't know how to execute prestop or poststart \
script, please check the scripts.
Only 1 script is supported and it should be executable.
Upgrading Veritas Access
Uninstalling patches
Note: Make sure there is no node rebooting operations in the customized script,
because Veritas Access doesn’t support node rebooting during upgrade.
Uninstalling patches
To uninstall patches
◆
To uninstall the software upgrades, enter the following:
Upgrade> patch uninstall-upto version
where version specifies the versions of software up to the version that you
want to uninstall.
For example:
Upgrade> patch uninstall-upto 7.2P1
OK Completed
Synchronizing software upgrades on a node
The Upgrade> patch sync command checks that all the nodes are on the same
patch level or not. If not, Veritas Access brings the nodes that are on different patch
levels to the same patch level as for the console node.
To forcefully synchronize software upgrades on a node
◆
To forcefully synchronize software upgrades on a node, enter the following:
Upgrade> patch sync nodename
where nodename specifies the node that needs to be synchronized to the same
software version as the one currently installed in the cluster.
For example:
Upgrade> patch sync node2
...............
Syncing software upgrades on node2...
SFS patch SUCCESS V-288-122 Patch sync completed.
115
Chapter
8
Uninstalling Veritas
Access
This chapter includes the following topics:
■
Before you uninstall Veritas Access
■
Uninstalling Veritas Access using the installer
Before you uninstall Veritas Access
Perform the following steps before uninstalling Veritas Access:
■
Before you remove Veritas Access from any node (but not in all the nodes) in
a cluster, make sure the node has already been deleted from the running cluster.
You can use the Cluster> show command to view the cluster node state, and
use the Cluster> delete command to delete a running node from the Veritas
Access cluster.
See the Veritas Access Command-Line Administrator's Guide for more
information on the Cluster> show and Cluster> delete commands.
■
Stop all the applications that access the file system over NFS, CIFS, or FTP.
■
Destroy all the replication jobs from the cluster.
Use the Replication> job show command to list all the replication jobs on the
cluster.
Replication> job show
Job Name Role Job Type Encryption Debug Schedule
======== ====== ======== ========== ===== ========
job1 SOURCE DATA OFF ON sch1
State CKPT Count Exclunit Source repunit Target repunit(s)
======== ========== ======== ============== =================
Uninstalling Veritas Access
Before you uninstall Veritas Access
117
ENABLED 1 -- scr1 trg1
Link name(s)
============
link1
Use the Replication> job destroy command to destroy the replication jobs.
Replication> job destroy job1
ACCESS replication SUCCESS V-288-0 Removing bandwidth limit on the
link: link1
ACCESS replication SUCCESS V-288-0 Job 'job1' disabled successfully.
ACCESS replication SUCCESS V-288-0 Job 'job1' deleted successfully.
■
Stop the NFS, CIFS, FTP, GUI, and the replication service on the cluster using
the appropriate CLISH command.
CLISH> cifs server stop
Stopping CIFS Server.....Success.
CLISH>
CLISH> nfs server stop
Success.
CLISH>
CLISH> ftp server stop
Success.
CLISH>
CLISH.Support> gui server stop
GUI service is OFFLINE.
CLISH>
CLISH> replication service stop
ACCESS replication SUCCESS V-288-0 Replication service stopped
CLISH>
■
Run the following command to stop AMF:
# /etc/init.d/amf stop
Stopping AMF...
AMF: Module unloaded
■
Run the following command and wait for a couple of minutes:
# /opt/VRTS/bin/hastop -all
■
Run the following command and verify that you only see Port a and Port b:
Uninstalling Veritas Access
Uninstalling Veritas Access using the installer
# gabconfig -a
GAB Port Memberships
==================================
Port a gen 7f2d0a membership 01
Port b gen 7f2d09 membership 01
Uninstalling Veritas Access using the installer
You can perform an uninstallation of Veritas Access. The Veritas Access uninstall
program lets you uninstall Veritas Access without requiring a reinstallation of the
operating system. You can also use the uninstall program in cases where there
was an incomplete installation of Veritas Access.
Before you use the uninstall program to uninstall Veritas Access on all nodes in the
cluster at the same time, make sure that communication exists between the nodes.
By default, Veritas Access cluster nodes can communicate with each other using
ssh.
If the nodes cannot communicate with each other, then you must run the uninstall
program on each node in the cluster. The uninstall program removes all Veritas
Access RPMs.
Removing Veritas Access 7.2 RPMs
The uninstall program stops the Veritas Access processes that are currently running
during the uninstallation process.
To uninstall Veritas Access 7.2
1
Log in as the support user from the node where you want to uninstall Veritas
Access.
2
Start the uninstall program.
# cd /opt/VRTS/install
# ./uninstallaccess72
The program specifies the directory where the logs are created. The program
displays a copyright notice and a description of the cluster.
118
Uninstalling Veritas Access
Uninstalling Veritas Access using the installer
3
Enter the IP addresses of the nodes from which you want to uninstall Veritas
Access.
The program performs node verification checks and asks to stop all running
Veritas Access processes.
4
Enter y to stop all the Veritas Access processes.
The program stops the Veritas Access processes and uninstalls the software.
The uninstall program does the following tasks:
■
Verifies the communication between nodes.
■
Checks the installations on each node to determine the RPMs to be
uninstalled.
■
Unloads kernel modules, and removes the RPMs.
Review the output as the uninstaller stops processes, .
You can make a note of the location of the summary, response, and log files
that the uninstaller creates after removing all the RPMs.
Running uninstall from the Veritas Access 7.2 disc
You may need to use the uninstall program on the Veritas Access 7.2 disc in one
of the following cases:
■
You need to uninstall Veritas Access after an incomplete installation.
■
The uninstall program is not available in /opt/VRTS/install.
If you mounted the installation media to /mnt, access the uninstall program by
changing the directory.
cd /mnt/
./uninstallaccess
119
Appendix
A
Installation reference
This appendix includes the following topics:
■
Installation script options
Installation script options
Table A-1 lists the available command line options for the Veritas Access installation
script. For an initial install or upgrade, options are not usually required.
Table A-1
Available command line options
Command Line Option
Function
-configure
Configures an unconfigured product after it
is installed.
-precheck
Performs checks to confirm that systems have
met the products installation requirements
before installing the product.
-requirements
Displays the required operating system
version, required patches, file system space,
and other system requirements to install the
product.
-responsefile response_file
Performs automated installations or
uninstallations using information stored in a
file rather than prompting for the information.
response_file is the full path of the file that
contains the configuration definitions.
-prestop_script
Executes the customized script provided by
user on each host before stop processes
during the upgrade procedure.
Installation reference
Installation script options
Table A-1
Available command line options (continued)
Command Line Option
Function
-poststart_script
Executes the customized script provided by
user on each host after start processes during
the upgrade procedure.
-updateparameter
Updates the network parameter for a running
cluster.
121
Appendix
B
Configuring the secure
shell for communications
This appendix includes the following topics:
■
Manually configuring passwordless secure shell (ssh)
■
Setting up ssh and rsh connection using the pwdutil.pl utility
Manually configuring passwordless secure shell
(ssh)
The secure shell (ssh) program enables you to log into and execute commands on
a remote system. ssh enables encrypted communications and an authentication
process between two untrusted hosts over an insecure network.
In this procedure, you first create a DSA key pair. From the key pair, you append
the public key from the source system to the authorized_keys file on the target
systems.
Configuring the secure shell for communications
Manually configuring passwordless secure shell (ssh)
To create the DSA key pair
1
On the source system (sys1), log in as root, and navigate to the root directory.
sys1 # cd /root
2
To generate a DSA key pair on the source system, type the following command:
sys1 # ssh-keygen -t dsa
System output similar to the following is displayed:
Generating public/private dsa key pair.
Enter file in which to save the key (/root/.ssh/id_dsa):
3
Press Enter to accept the default location of /root/.ssh/id_dsa.
4
When the program asks you to enter the pass phrase, press the Enter key
twice.
Enter passphrase (empty for no passphrase):
Do not enter a pass phrase. Press Enter.
Enter same passphrase again:
Press Enter again.
5
Output similar to the following lines appears.
Your identification has been saved in /root/.ssh/id_dsa.
Your public key has been saved in /root/.ssh/id_dsa.pub.
The key fingerprint is:
1f:00:e0:c2:9b:4e:29:b4:0b:6e:08:f8:50:de:48:d2 root@sys1
123
Configuring the secure shell for communications
Manually configuring passwordless secure shell (ssh)
To append the public key from the source system to the authorized_keys file
on the target system using secure file transfer
1
From the source system (sys1), move the public key to a temporary file on the
target system (sys2).
Use the secure file transfer program.
In this example, the file name id_dsa.pub in the root directory is the name for
the temporary file for the public key.
Use the following command for secure file transfer:
sys1 # sftp sys2
If the secure file transfer is set up for the first time on this system, output similar
to the following lines is displayed:
Connecting to sys2 ...
The authenticity of host 'sys2 (10.182.00.00)'
can't be established. DSA key fingerprint is
fb:6f:9f:61:91:9d:44:6b:87:86:ef:68:a6:fd:88:7d.
Are you sure you want to continue connecting (yes/no)?
2
Enter yes.
Output similar to the following is displayed:
Warning: Permanently added 'sys2,10.182.00.00'
(DSA) to the list of known hosts.
root@sys2 password:
3
Enter the root password of sys2.
4
At the sftp prompt, type the following command:
sftp> put /root/.ssh/id_dsa.pub
The following output is displayed:
Uploading /root/.ssh/id_dsa.pub to /root/id_dsa.pub
5
To quit the SFTP session, type the following command:
sftp> quit
124
Configuring the secure shell for communications
Setting up ssh and rsh connection using the pwdutil.pl utility
6
Add the id_dsa.pub keys to the authorized_keys file on the target system.
To begin the ssh session on the target system (sys2 in this example), type the
following command on sys1:
sys1 # ssh sys2
Enter the root password of sys2 at the prompt:
password:
Type the following commands on sys2:
sys2 # cat /root/id_dsa.pub >> /root/.ssh/authorized_keys
sys2 # rm
7
/root/id_dsa.pub
Run the following commands on the source installation system. If your ssh
session has expired or terminated, you can also run these commands to renew
the session. These commands bring the private key into the shell environment
and make the key globally available to the root user.
sys1 # exec /usr/bin/ssh-agent $SHELL
sys1 # ssh-add
Identity added: /root/.ssh/id_dsa
This shell-specific step is valid only while the shell is active. You must execute
the procedure again if you close the shell during the session.
To verify that you can connect to a target system
1
On the source system (sys1), enter the following command:
sys1 # ssh -l root sys2 uname -a
where sys2 is the name of the target system.
2
The command should execute from the source system (sys1) to the target
system (sys2) without the system requesting a pass phrase or password.
3
Repeat this procedure for each target system.
Setting up ssh and rsh connection using the
pwdutil.pl utility
The password utility, pwdutil.pl, is bundled in the 6.2 release under the scripts
directory. The users can run the utility in their script to set up the ssh and rsh
connection automatically.
125
Configuring the secure shell for communications
Setting up ssh and rsh connection using the pwdutil.pl utility
126
# ./pwdutil.pl -h
Usage:
Command syntax with simple format:
pwdutil.pl check|configure|unconfigure ssh|rsh <hostname|IP addr>
[<user>] [<password>] [<port>]
Command syntax with advanced format:
pwdutil.pl [--action|-a 'check|configure|unconfigure']
[--type|-t 'ssh|rsh']
[--user|-u '<user>']
[--password|-p '<password>']
[--port|-P '<port>']
[--hostfile|-f '<hostfile>']
[--keyfile|-k '<keyfile>']
[-debug|-d]
<host_URI>
pwdutil.pl -h | -?
Table B-1
Options with pwdutil.pl utility
Option
Usage
--action|-a 'check|configure|unconfigure'
Specifies action type, default is 'check'.
--type|-t 'ssh|rsh'
Specifies connection type, default is 'ssh'.
--user|-u '<user>'
Specifies user id, default is the local user id.
--password|-p '<password>'
Specifies user password, default is the user
id.
--port|-P '<port>'
Specifies port number for ssh connection,
default is 22
--keyfile|-k '<keyfile>'
Specifies the private key file.
--hostfile|-f '<hostfile>'
Specifies the file which list the hosts.
-debug
Prints debug information.
-h|-?
Prints help messages.
Configuring the secure shell for communications
Setting up ssh and rsh connection using the pwdutil.pl utility
Table B-1
Options with pwdutil.pl utility (continued)
Option
Usage
<host_URI>
Can be in the following formats:
<hostname>
<user>:<password>@<hostname>
<user>:<password>@<hostname>:
<port>
You can check, configure, and unconfigure ssh or rsh using the pwdutil.plutility.
For example:
■
To check ssh connection for only one host:
pwdutil.pl check ssh hostname
■
To configure ssh for only one host:
pwdutil.pl configure ssh hostname user password
■
To unconfigure rsh for only one host:
pwdutil.pl unconfigure rsh hostname
■
To configure ssh for multiple hosts with same user ID and password:
pwdutil.pl -a configure -t ssh -u user -p password hostname1
hostname2 hostname3
■
To configure ssh or rsh for different hosts with different user ID and password:
pwdutil.pl -a configure -t ssh user1:password1@hostname1
user2:password2@hostname2
■
To check or configure ssh or rsh for multiple hosts with one configuration file:
pwdutil.pl -a configure -t ssh --hostfile /tmp/sshrsh_hostfile
■
To keep the host configuration file secret, you can use the 3rd party utility to
encrypt and decrypt the host file with password.
For example:
127
Configuring the secure shell for communications
Setting up ssh and rsh connection using the pwdutil.pl utility
### run openssl to encrypt the host file in base64 format
# openssl aes-256-cbc -a -salt -in /hostfile -out /hostfile.enc
enter aes-256-cbc encryption password: <password>
Verifying - enter aes-256-cbc encryption password: <password>
### remove the original plain text file
# rm /hostfile
### run openssl to decrypt the encrypted host file
# pwdutil.pl -a configure -t ssh `openssl aes-256-cbc -d -a
-in /hostfile.enc`
enter aes-256-cbc decryption password: <password>
■
To use the ssh authentication keys which are not under the default $HOME/.ssh
directory, you can use --keyfile option to specify the ssh keys. For example:
### create a directory to host the key pairs:
# mkdir /keystore
### generate private and public key pair under the directory:
# ssh-keygen -t rsa -f /keystore/id_rsa
### setup ssh connection with the new generated key pair under
the directory:
# pwdutil.pl -a configure -t ssh --keyfile /keystore/id_rsa
user:password@hostname
You can see the contents of the configuration file by using the following command:
# cat /tmp/sshrsh_hostfile
user1:password1@hostname1
user2:password2@hostname2
user3:password3@hostname3
user4:password4@hostname4
# all default: check ssh connection with local user
hostname5
The following exit values are returned:
0
1
2
3
Successful completion.
Command syntax error.
Ssh or rsh binaries do not exist.
Ssh or rsh service is down on the remote machine.
128
Configuring the secure shell for communications
Setting up ssh and rsh connection using the pwdutil.pl utility
4
5
255
129
Ssh or rsh command execution is denied due to password is required.
Invalid password is provided.
Other unknown error.
Index
Symbols
/etc/llttab
sample 30
connecting
network hardware 31
D
A
about
installing patches 108
NIC bonding 55
NIC exclusion 55
types of patches 103
B
bond
creating 62
bond interface
creating 62
C
calculating
IP address 34
checking
storage configuration 37
cluster
adding the new node to 97
configuring 48
deleting a node from 100
displaying a list of nodes 93
including new nodes 95
installing 48
shutting down a node or all nodes in a cluster 102
cluster installation
overview 39
Configuration
LLT 29
configuration limits 23
configuring
NetBackup (NBU) 75
on the cluster 48
yum 46
configuring passwordless ssh 122
deleting
a node from the cluster 100
displaying
current version 106
list of nodes in a cluster 93
patches in repository 107
upgrade history 106
displaying current version 106
displaying patches in repository 107
displaying upgrade history 106
downloading
patch 106
downloading patch 106
driver node 42
E
excluding
NIC 56
H
Hardware requirements
Veritas Access 27
I
including
new nodes in the cluster 95
NIC 60
install
silent 79
installation
response files 78
response files variables 79
installation script options 120
installation states and conditions
about 92
Index
Installer
configure 30
installing
cluster 39
cluster node's console 48
driver node 48
on the cluster 48
operating system on each node of the cluster 42
operating system on Veritas Access cluster 43
operating system package 47
prerequisites 41
steps 40
target cluster nodes 47
installing patches 108
about 108
IP address
calculation 34
IP addresses
calculate 62
obtain 33
IPv6 48
IPv6 protocol 19
L
Linux requirements
Veritas Access 11
list of nodes
displaying in a cluster 93
LLT
RDMA 28, 30
M
Management Server requirements
Veritas Access 17
N
NetBackup (NBU)
configuring 75
network and firewall requirements
Veritas Access 19
network hardware
connecting 31
network interface card (NIC) bonding 62
NIC
excluding 56
including 60
node
adding to the cluster 95, 97
O
obtain
IP addresses 33
operating system
installing 43
installing on each node of the cluster 42
overview
Veritas Access installation 25
P
patches
installing 108
synchronizing 115
types of 103
uninstalling 115
upgrading 105
R
RDMA
Hardware 29
InfiniBand 28
LLT 27
reconfiguring
Veritas Access cluster name and network 76
release information 10
removing
bond 68
NIC from bond list 71
replacing
Ethernet interface card 73
S
sample response file 88
server requirements
Veritas Access 17
shutting down
node or all nodes in a cluster 102
silent installation and configuration 79
storage configuration
checking 37
supported IPv6 protocol 19
synchronizing patches 115
system requirements
Veritas Access 10
131
Index
U
uninstalling
patches 115
uninstalling Veritas Access
before 116
upgrading
patches 105
V
Veritas Access
about 7
key features 7
Linux requirements 11
network and firewall requirements 19
server requirements 17
system requirements 10
web browser requirements 17
Veritas Access cluster name and network
reconfigure 76
Veritas Access installation
overview 25
Y
yum
configuration 46
132
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising