Storage Foundation and High Availability 8.0.2 Configuration and Upgrade Guide - AIX
- Section I. Introduction to SFHA
- Introducing Storage Foundation and High Availability
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Planning your CP server setup
- Installing the CP server using the installer
- Configuring the CP server cluster in secure mode
- Setting up shared storage for the CP server database
- Configuring the CP server using the installer program
- Configuring the CP server manually
- Configuring CP server using response files
- Verifying the CP server configuration
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Overview of tasks to configure SFHA using the product installer
- Required information for configuring Storage Foundation and High Availability Solutions
- Starting the software configuration
- Specifying systems for configuration
- Configuring the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring SFHA in secure mode
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Completing the SFHA configuration
- About Veritas License Audit Tool
- Verifying and updating licenses on the system
- Configuring SFDB
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Setting up non-SCSI-3 I/O fencing in virtual environments using installer
- Setting up majority-based I/O fencing using installer
- Enabling or disabling the preferred fencing policy
- Manually configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Preparing the CP servers manually for use by the SFHA cluster
- Generating the client key and certificates manually on the client nodes
- Configuring server-based fencing on the SFHA cluster manually
- Configuring CoordPoint agent to monitor coordination points
- Verifying server-based I/O fencing configuration
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring I/O fencing using response files
- Response file variables to configure disk-based I/O fencing
- Sample response file for configuring disk-based I/O fencing
- Response file variables to configure server-based I/O fencing
- Sample response file for configuring server-based I/O fencing
- Response file variables to configure non-SCSI-3 I/O fencing
- Sample response file for configuring non-SCSI-3 I/O fencing
- Response file variables to configure majority-based I/O fencing
- Sample response file for configuring majority-based I/O fencing
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- About the upgrade
- Supported upgrade paths
- Considerations for upgrading SFHA to 8.0.2 on systems configured with an Oracle resource
- Preparing to upgrade SFHA
- Considerations for upgrading REST server
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Moving the service groups to the second subcluster
- Upgrading the operating system on the first subcluster
- Upgrading the first subcluster
- Preparing the second subcluster
- Activating the first subcluster
- Upgrading the operating system on the second subcluster
- Upgrading the second subcluster
- Finishing the phased upgrade
- Performing an automated SFHA upgrade using response files
- Performing post-upgrade tasks
- Optional configuration steps
- Recovering VVR if automatic upgrade fails
- Post-upgrade tasks when VCS agents for VVR are configured
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- Upgrading VxVM disk group versions
- Updating variables
- Setting the default disk group
- About enabling LDAP authentication for clusters that run in secure mode
- Verifying the Storage Foundation and High Availability upgrade
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- About adding a node to a cluster
- Before adding a node to a cluster
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- After adding the new node
- Adding nodes to a cluster that is using authentication for SFDB tools
- Updating the Storage Foundation for Databases (SFDB) repository after adding a node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Verifying the status of nodes and service groups
- Deleting the departing node from SFHA configuration
- Modifying configuration files on each remaining node
- Removing the node configuration from the CP server
- Removing security credentials from the leaving node
- Unloading LLT and GAB and removing Veritas InfoScale Availability or Enterprise on the departing node
- Updating the Storage Foundation for Databases (SFDB) repository after removing a node
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Support for AIX Live Update
- Appendix B. Installation scripts
- Appendix C. SFHA services and ports
- Appendix D. Configuration files
- Appendix E. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling rsh for AIX
- Appendix F. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix G. Changing NFS server major numbers for VxVM volumes
- Appendix H. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Broadcast address in the /etc/llttab file
- The link command in the /etc/llttab file
- The set-addr command in the /etc/llttab file
- Selecting UDP ports
- Configuring the netmask for LLT
- Configuring the broadcast address for LLT
- Sample configuration: direct-attached links
- Sample configuration: links crossing IP routers
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
Configuring the CP server using the installer program
Use the configcps option available in the installer program to configure the CP server.
Perform one of the following procedures:
For CP servers on single-node VCS cluster: | See “To configure the CP server on a single-node VCS cluster”. |
For CP servers on an SFHA cluster: |
To configure the CP server on a single-node VCS cluster
- Verify that the
VRTScpsfileset is installed on the node. - Run the installer program with the configcps option.
# /opt/VRTS/install/installer -configcps - Installer checks the cluster information and prompts if you want to configure CP Server on the cluster.
Enter y to confirm.
- Select an option based on how you want to configure Coordination Point server.
1) Configure Coordination Point Server on single node VCS system 2) Configure Coordination Point Server on SFHA cluster 3) Unconfigure Coordination Point Server
- Enter the option: [1-3,q] 1.
The installer then runs the following preconfiguration checks:
Checks to see if a single-node VCS cluster is running with the supported platform.
The CP server requires VCS to be installed and configured before its configuration.
The installer automatically installs a license that is identified as a CP server-specific license. It is installed even if a VCS license exists on the node. CP server-specific key ensures that you do not need to use a VCS license on the single-node. It also ensures that Veritas Operations Manager (VOM) identifies the license on a single-node coordination point server as a CP server-specific license and not as a VCS license.
- Restart the VCS engine if the single-node only has a CP server-specific license.
A single node coordination point server will be configured and VCS will be started in one node mode, do you want to continue? [y,n,q] (y)
- Communication between the CP server and application clusters is secured by using the HTTPS protocol from release 6.1.0 onwards.
Enter the name of the CP Server.
Enter the name of the CP Server: [b] cps1
- Enter valid virtual IP addresses for the CP Server with HTTPS-based secure communication. A CP Server can be configured with more than one virtual IP address.
Enter Virtual IP(s) for the CP server for HTTPS, separated by a space: [b] 10.200.58.231 10.200.58.232 10.200.58.233
Note:
Ensure that the virtual IP address of the CP server and the IP address of the NIC interface on the CP server belongs to the same subnet of the IP network. This is required for communication to happen between client nodes and CP server.
- Enter the corresponding CP server port number for each virtual IP address or press Enter to accept the default value (443).
Enter the default port '443' to be used for all the virtual IP addresses for HTTPS communication or assign the corresponding port number in the range [49152, 65535] for each virtual IP address. Ensure that each port number is separated by a single space: [b] (443) 54442 54443 54447
- Enter the absolute path of the CP server database or press Enter to accept the default value (/etc/VRTScps/db).
Enter absolute path of the database: [b] (/etc/VRTScps/db)
- Verify and confirm the CP server configuration information.
CP Server configuration verification: ------------------------------------------------- CP Server Name: cps1 CP Server Virtual IP(s) for HTTPS: 10.200.58.231, 10.200.58.232, 10.200.58.233 CP Server Port(s) for HTTPS: 54442, 54443, 54447 CP Server Database Dir: /etc/VRTScps/db ------------------------------------------------- Is this information correct? [y,n,q,?] (y)
- The installer proceeds with the configuration process, and creates a vxcps.conf configuration file.
Successfully generated the /etc/vxcps.conf configuration file Successfully created directory /etc/VRTScps/db on node
- Configure the CP Server Service Group (CPSSG) for this cluster.
Enter how many NIC resources you want to configure (1 to 2): 2
Answer the following questions for each NIC resource that you want to configure.
- Enter a valid network interface for the virtual IP address for the CP server process.
Enter a valid network interface on sys1 for NIC resource - 1: en0 Enter a valid network interface on sys1 for NIC resource - 2: en1
- Enter the NIC resource you want to associate with the virtual IP addresses.
Enter the NIC resource you want to associate with the virtual IP 10.200.58.231 (1 to 2): 1 Enter the NIC resource you want to associate with the virtual IP 10.200.58.232 (1 to 2): 2
- Enter the networkhosts information for each NIC resource.
Veritas recommends configuring NetworkHosts attribute to ensure NIC resource to be always online
Do you want to add NetworkHosts attribute for the NIC device en0 on system sys1? [y,n,q] y Enter a valid IP address to configure NetworkHosts for NIC en0 on system sys1: 10.200.56.22
Do you want to add another Network Host? [y,n,q] n
- Enter the netmask for virtual IP addresses. If you entered an IPv6 address, enter the prefix details at the prompt.
Enter the netmask for virtual IP for HTTPS 192.169.0.220: (255.255.252.0)
- Installer displays the status of the Coordination Point Server configuration. After the configuration process has completed, a success message appears.
For example: Updating main.cf with CPSSG service group.. Done Successfully added the CPSSG service group to VCS configuration. Trying to bring CPSSG service group ONLINE and will wait for upto 120 seconds The Veritas coordination point server is ONLINE The Veritas coordination point server has been configured on your system.
- Run the hagrp -state command to ensure that the CPSSG service group has been added.
For example: # hagrp -state CPSSG #Group Attribute System Value CPSSG State.... |ONLINE|
It also generates the configuration file for CP server (/etc/vxcps.conf). The vxcpserv process and other resources are added to the VCS configuration in the CP server service group (CPSSG).
For information about the CPSSG, refer to the Cluster Server Administrator's Guide.
To configure the CP server on an SFHA cluster
- Verify that the
VRTScpsfileset is installed on each node. - Ensure that you have configured passwordless ssh or rsh on the CP server cluster nodes.
- Run the installer program with the configcps option.
# ./installer -configcps
- Specify the systems on which you need to configure the CP server.
- Installer checks the cluster information and prompts if you want to configure CP Server on the cluster.
Enter y to confirm.
- Select an option based on how you want to configure Coordination Point server.
1) Configure Coordination Point Server on single node VCS system 2) Configure Coordination Point Server on SFHA cluster 3) Unconfigure Coordination Point Server
- Enter 2 at the prompt to configure CP server on an SFHA cluster.
The installer then runs the following preconfiguration checks:
Checks to see if an SFHA cluster is running with the supported platform.
The CP server requires SFHA to be installed and configured before its configuration.
- Communication between the CP server and application clusters is secured by HTTPS from Release 6.1.0 onwards.
Enter the name of the CP server.
Enter the name of the CP Server: [b] cps1
- Enter valid virtual IP addresses for the CP Server. A CP Server can be configured with more than one virtual IP address.
Enter Virtual IP(s) for the CP server for HTTPS, separated by a space: [b] 10.200.58.231 10.200.58.232 10.200.58.233
- Enter the corresponding CP server port number for each virtual IP address or press Enter to accept the default value (443).
Enter the default port '443' to be used for all the virtual IP addresses for HTTPS communication or assign the corresponding port number in the range [49152, 65535] for each virtual IP address. Ensure that each port number is separated by a single space: [b] (443) 65535 65534 65537
- Enter absolute path of the database.
CP Server uses an internal database to store the client information. As the CP Server is being configured on SFHA cluster, the database should reside on shared storage with vxfs file system. Please refer to documentation for information on setting up of shared storage for CP server database. Enter absolute path of the database: [b] /cpsdb
- Verify and confirm the CP server configuration information.
CP Server configuration verification: CP Server Name: cps1 CP Server Virtual IP(s) for HTTPS: 10.200.58.231, 10.200.58.232, 10.200.58.233 CP Server Port(s) for HTTPS: 65535, 65534, 65537 CP Server Database Dir: /cpsdb Is this information correct? [y,n,q,?] (y)
- The installer proceeds with the configuration process, and creates a vxcps.conf configuration file.
Successfully generated the /etc/vxcps.conf configuration file Copying configuration file /etc/vxcps.conf to sys0....Done Creating mount point /cps_mount_data on sys0. ... Done Copying configuration file /etc/vxcps.conf to sys0. ... Done Press Enter to continue.
- Configure CP Server Service Group (CPSSG) for this cluster.
Enter how many NIC resources you want to configure (1 to 2): 2 Answer the following questions for each NIC resource that you want to configure.
- Enter a valid network interface for the virtual IP address for the CP server process.
Enter a valid network interface on sys1 for NIC resource - 1: en0 Enter a valid network interface on sys1 for NIC resource - 2: en1
- Enter the NIC resource you want to associate with the virtual IP addresses.
Enter the NIC resource you want to associate with the virtual IP 10.200.58.231 (1 to 2): 1 Enter the NIC resource you want to associate with the virtual IP 10.200.58.232 (1 to 2): 2
- Enter the networkhosts information for each NIC resource.
Veritas recommends configuring NetworkHosts attribute to ensure NIC resource to be always online
Do you want to add NetworkHosts attribute for the NIC device en0 on system sys1? [y,n,q] y Enter a valid IP address to configure NetworkHosts for NIC en0 on system sys1: 10.200.56.22
Do you want to add another Network Host? [y,n,q] n Do you want to apply the same NetworkHosts for all systems? [y,n,q] (y)
- Enter the netmask for virtual IP addresses. If you entered an IPv6 address, enter the prefix details at the prompt.
Enter the netmask for virtual IP for HTTPS 192.168.0.111: (255.255.252.0)
- Configure a disk group for CP server database. You can choose an existing disk group or create a new disk group.
Veritas recommends to use the disk group that has at least two disks on which mirrored volume can be created. Select one of the options below for CP Server database disk group: 1) Create a new disk group 2) Using an existing disk group Enter the choice for a disk group: [1-2,q] 2
- Select one disk group as the CP Server database disk group.
Select one disk group as CP Server database disk group: [1-3,q] 3 1) mycpsdg 2) cpsdg1 3) newcpsdg
- Select the CP Server database volume.
You can choose to use an existing volume or create new volume for CP Server database. If you chose newly created disk group, you can only choose to create new volume for CP Server database.
Select one of the options below for CP Server database volume: 1) Create a new volume on disk group newcpsdg 2) Using an existing volume on disk group newcpsdg
- Enter the choice for a volume: [1-2,q] 2.
- Select one volume as CP Server database volume [1-1,q] 1
1) newcpsvol
- After the VCS configuration files are updated, a success message appears.
For example: Updating main.cf with CPSSG service group .... Done Successfully added the CPSSG service group to VCS configuration.
- If the cluster is secure, installer creates the softlink
/var/VRTSvcs/vcsauth/data/CPSERVERto/cpsdb/CPSERVERand check if credentials are already present at/cpsdb/CPSERVER. If not, installer creates credentials in the directory, otherwise, installer asks if you want to reuse exsting credentials.Do you want to reuse these credentials? [y,n,q] (y)
- After the configuration process has completed, a success message appears.
For example: Trying to bring CPSSG service group ONLINE and will wait for upto 120 seconds The Veritas Coordination Point Server is ONLINE The Veritas Coordination Point Server has been configured on your system.
- Run the hagrp -state command to ensure that the CPSSG service group has been added.
For example: # hagrp -state CPSSG #Group Attribute System Value CPSSG State cps1 |ONLINE| CPSSG State cps2 |OFFLINE|
It also generates the configuration file for CP server (
/etc/vxcps.conf). The vxcpserv process and other resources are added to the VCS configuration in the CP server service group (CPSSG).
For information about the CPSSG, refer to the Cluster Server Administrator's Guide.