Please enter search query.
Search <book_title>...
Veritas Access Installation Guide
Last Published:
2018-12-07
Product(s):
Access (7.4.1)
Platform: Linux
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- Important release information
- System requirements
- Linux requirements
- Operating system RPM installation requirements and operating system patching
- Kernel RPMs that are required to be installed with exact predefined RPM versions
- OL kernel RPMs that are required to be installed with exact predefined RPM versions
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 7.3
- Required operating system RPMs for RHEL 7.4
- Software requirements for installing Veritas Access in a VMware ESXi environment
- Hardware requirements for installing Veritas Access virtual machines
- 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
- Linux requirements
- Network and firewall requirements
- Maximum configuration limits
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- 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 managing the NICs, bonds, and VLAN devices
- About VLAN tagging
- 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
- Configuring a KMS server on the Veritas Access cluster
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading Veritas Access and operating system
- Upgrading Veritas Access using a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Configuring the secure shell for communications
- Appendix C. Manual deployment of Veritas Access
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}{comsetup}=1;
$CFG{opt}{noipc}=1;
$CFG{opt}{ssh}=1;
$CFG{prod}="SNAS73";
$CFG{opt}{licensefile}="<absolute_path_of_licfile>";
#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;
$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(192.168.30.10 192.168.30.11 192.168.30.12
192.168.30.13 192.168.30.14 192.168.30.15 192.168.30.16 192.168.30.17) ];
#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}="192.168.30.40";
#default gateway of SNAS
$CFG{snas_defgateway}="192.168.30.1";
#domain name of DNS
$CFG{snas_dnsdomainname}="cdc.veritas.com";
#IP of DNS
$CFG{snas_dnsip}="192.168.30.2";
#NTP server name
$CFG{snas_ntpserver}="ntp.veritas.com";
#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}="192.168.30.10";
#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}="192.168.30.18";
#virtual IPs
$CFG{virtualiparr}=[ qw(192.168.30.18 192.168.30.19 192.168.30.20
192.168.30.21 192.168.30.22 192.168.30.23 192.168.30.24 192.168.30.25) ];
#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(192.168.30.80 192.168.30.81) ];
#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}{"192.168.30.10"}="priveth0";
$CFG{vcs_lltlink1}{"192.168.30.13"}="priveth0";
$CFG{vcs_lltlink2}{"192.168.30.10"}="priveth1";
$CFG{vcs_lltlink2}{"192.168.30.13"}="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;
####################################################