Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux
- Section I. Configuring SF Sybase ASE CE
- Preparing to configure SF Sybase CE
- Configuring SF Sybase CE
- About configuring SF Sybase CE
- Configuring the SF Sybase CE components using the script-based installer
- Configuring the SF Sybase CE cluster
- Configuring the cluster name
- Configuring private heartbeat links
- Configuring the virtual IP of the cluster
- Configuring SF Sybase CE in secure mode
- Configuring a secure cluster node by node
- Adding VCS users
- Configuring SMTP email notification
- Configuring SNMP trap notification
- Configuring global clusters
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Performing an automated SF Sybase CE configuration
- Performing an automated I/O fencing configuration using response files
- Configuring a cluster under VCS control using a response file
- Section II. Post-installation and configuration tasks
- Section III. Upgrade of SF Sybase CE
- Planning to upgrade SF Sybase CE
- Performing a full upgrade of SF Sybase CE using the product installer
- Performing an automated full upgrade of SF Sybase CE using response files
- Performing a phased upgrade of SF Sybase CE
- About phased upgrade
- Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
- Step 1: Performing pre-upgrade tasks on the first half of the cluster
- Step 2: Upgrading the first half of the cluster
- Step 3: Performing pre-upgrade tasks on the second half of the cluster
- Step 4: Performing post-upgrade tasks on the first half of the cluster
- Step 5: Upgrading the second half of the cluster
- Step 6: Performing post-upgrade tasks on the second half of the cluster
- Performing a rolling upgrade of SF Sybase CE
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Before installing Sybase ASE CE
- Preparing for local mount point on VxFS for Sybase ASE CE binary installation
- Preparing for shared mount point on CFS for Sybase ASE CE binary installation
- Installing Sybase ASE CE software
- Preparing to create a Sybase ASE CE cluster
- Creating the Sybase ASE CE cluster
- Preparing to configure the Sybase instances under VCS control
- Configuring a Sybase ASE CE cluster under VCS control using the SF Sybase CE installer
- Upgrading Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Section V. Adding and removing nodes
- Adding a node to SF Sybase CE clusters
- About adding a node to a cluster
- Before adding a node to a cluster
- Adding the node to a cluster manually
- Starting Veritas Volume Manager (VxVM) on the new node
- Configuring cluster processes on the new node
- Setting up the node to run in secure mode
- Starting fencing on the new node
- Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
- After adding the new node
- Configuring the ClusterService group for the new node
- Adding a node to a cluster using the Veritas InfoScale installer
- Adding the new instance to the Sybase ASE CE cluster
- Removing a node from SF Sybase CE clusters
- Adding a node to SF Sybase CE clusters
- Section VI. Configuration of disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Sample installation and configuration values
- Appendix C. Tunable files for installation
- About setting tunable parameters using the installer or a response file
- Setting tunables for an installation, configuration, or upgrade
- Setting tunables with no other installer-related operations
- Setting tunables with an un-integrated response file
- Preparing the tunables file
- Setting parameters for the tunables file
- Tunables value parameter definitions
- Appendix D. Configuration files
- About sample main.cf files
- Sample main.cf files for Sybase ASE CE configurations
- Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
- Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
- Sample main.cf for a primary CVM VVR site
- Sample main.cf for a secondary CVM VVR site
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. High availability agent information
Configuring private heartbeat links
You now configure the private heartbeat links that LLT uses.
VCS provides the option to use LLT over Ethernet or LLT over UDP (User Datagram Protocol) or LLT over RDMA, or LLT over TCP. Veritas recommends that you configure heartbeat links that use LLT over Ethernet or LLT over RDMA for high performance, unless hardware requirements force you to use LLT over UDP. If you want to configure LLT over UDP, make sure you meet the prerequisites.
You must not configure LLT heartbeat using the links that are part of aggregated links. For example, link1, link2 can be aggregated to create an aggregated link, aggr1. You can use aggr1 as a heartbeat link, but you must not use either link1 or link2 as heartbeat links.
The following procedure helps you configure LLT heartbeat links.
To configure private heartbeat links
Choose one of the following options at the installer prompt based on whether you want to configure LLT over Ethernet or LLT over UDP or LLT over TCP or LLT over RDMA.
Option 1: Configure the heartbeat links using LLT over Ethernet (answer installer questions)
Enter the heartbeat link details at the installer prompt to configure LLT over Ethernet.
Skip to step 2.
Option 2: Configure the heartbeat links using LLT over UDP (answer installer questions)
Make sure that each NIC you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over UDP. If you had not already configured IP addresses to the NICs, the installer provides you an option to detect the IP address for a given NIC.
Skip to step 3.
Option 3: Configure the heartbeat links using LLT over TCP (answer installer questions)
Make sure that the NIC you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over TCP. If you had not already configured IP addresses to the NICs, the installer provides you an option to detect the IP address for a given NIC.
Skip to step 4.
Option 4: Configure the heartbeat links using LLT over RDMA (answer installer questions)
Make sure that each RDMA enabled NIC (RNIC) you want to use as heartbeat link has an IP address configured. Enter the heartbeat link details at the installer prompt to configure LLT over RDMA. If you had not already configured IP addresses to the RNICs, the installer provides you an option to detect the IP address for a given RNIC.
Skip to step 5.
Option 5: Automatically detect configuration for LLT over Ethernet
Allow the installer to automatically detect the heartbeat link details to configure LLT over Ethernet. The installer tries to detect all connected links between all systems.
Make sure that you activated the NICs for the installer to be able to detect and automatically configure the heartbeat links.
Skip to step 8.
Note:
Option 5 is not available when the configuration is a single node configuration.
- If you chose option 1, enter the network interface card details for the private heartbeat links.
The installer discovers and lists the network interface cards.
You must not enter the network interface card that is used for the public network (typically eth0.)
Enter the NIC for the first private heartbeat link on sys1: [b,q,?] eth1 eth1 has an IP address configured on it. It could be a public NIC on sys1. Are you sure you want to use eth1 for the first private heartbeat link? [y,n,q,b,?] (n) y Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) Enter the NIC for the second private heartbeat link on sys1: [b,q,?] eth2 eth2 has an IP address configured on it. It could be a public NIC on sys1. Are you sure you want to use eth2 for the second private heartbeat link? [y,n,q,b,?] (n) y Would you like to configure a third private heartbeat link? [y,n,q,b,?](n)
- If you chose option 2, enter the NIC details for the private heartbeat links. This step uses examples such as private_NIC1 or private_NIC2 to refer to the available names of the NICs.
Enter the NIC for the first private heartbeat link on sys1: [b,q,?] private_NIC1 Some configured IP addresses have been found on the NIC private_NIC1 in sys1, Do you want to choose one for the first private heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 192.168.0.1/24 2) 192.168.1.233/24 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) Enter the UDP port for the first private heartbeat link on sys1: [b,q,?] (50000) Enter the NIC for the second private heartbeat link on sys1: [b,q,?] private_NIC2 Some configured IP addresses have been found on the NIC private_NIC2 in sys1, Do you want to choose one for the second private heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 192.168.1.1/24 2) 192.168.2.233/24 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) 1 Enter the UDP port for the second private heartbeat link on sys1: [b,q,?] (50001) Would you like to configure a third private heartbeat link? [y,n,q,b,?] (n) Do you want to configure an additional low-priority heartbeat link? [y,n,q,b,?] (n) y Enter the NIC for the low-priority heartbeat link on sys1: [b,q,?] private_NIC0 Some configured IP addresses have been found on the NIC private_NIC0 in sys1, Do you want to choose one for the low-priority heartbeat link? [y,n,q,?] (y) Please select one IP address: 1) 10.200.59.233/22 2) 192.168.3.1/22 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) 2 Enter the UDP port for the low-priority heartbeat link on sys1: [b,q,?] (50010) - If you chose option 3, enter the NIC details for the private heartbeat link.
This step uses an example such as private_NIC1 to refer to the available name of the NIC.
Enter the NIC for the private heartbeat link on sys1: [b,q,?] (eth1) private_NIC1 Some configured IP addresses have been found on the NIC private_NIC1 in sys1, Do you want to choose one for the private heartbeat link? [y,n,q,?] (y) y Please select one IP address: 1) 192.168.1.1/24 2) 192.168.2.1/24 b) Back to previous menu Please select one IP address: [1-2,b,q,?] (1) Enter the TCP port for the first private heartbeat link on sys1: [b,q,?] (50000)
- If you chose option 4, choose the interconnect type to configure RDMA.
1) Converged Ethernet (RoCE) 2) InfiniBand b) Back to previous menu Choose the RDMA interconnect type [1-2,b,q,?] (1) 2
The system displays the details such as the required OS files, drivers required for RDMA , and the IP addresses for the NICs.
A sample output of the IP addresses assigned to the RDMA enabled NICs using InfiniBand network. Note that with RoCE, the RDMA NIC values are represented as eth0, eth1, and so on.
System RDMA NIC IP Address ================================================================= sys1 ib0 192.168.0.1 sys1 ib1 192.168.3.1 sys2 ib0 192.168.0.2 sys2 ib1 192.168.3.2
If you chose option 4, enter the NIC details for the private heartbeat links. This step uses RDMA over an InfiniBand network. With RoCE as the interconnect type, RDMA NIC is represented as Ethernet (eth).
Enter the NIC for the first private heartbeat link (RDMA) on sys1: [b,q,?] <ib0> Do you want to use address 192.168.0.1 for the first private heartbeat link on sys1: [y,n,q,b,?] (y) Enter the port for the first private heartbeat link (RDMA) on sys1: [b,q,?] (50000) ? Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) Enter the NIC for the second private heartbeat link (RDMA) on sys1: [b,q,?] (ib1) Do you want to use the address 192.168.3.1 for the second private heartbeat link on sys1: [y,n,q,b,?] (y) Enter the port for the second private heartbeat link (RDMA) on sys1: [b,q,?] (50001) Do you want to configure an additional low-priority heartbeat link? [y,n,q,b,?] (n)
- Choose whether to use the same NIC details to configure private heartbeat links on other systems.
Are you using the same NICs for private heartbeat links on all systems? [y,n,q,b,?] (y)
If you want to use the NIC details that you entered for sys1, make sure the same NICs are available on each system. Then, enter y at the prompt.
If the NIC device names are different on some of the systems, enter n. Provide the NIC details for each system as the program prompts.
For LLT over UDP and LLT over RDMA, if you want to use the same NICs on other systems, you must enter unique IP addresses on each NIC for other systems.
- If you chose option 5, the installer detects NICs on each system and network links, and sets link priority.
If the installer fails to detect heartbeat links or fails to find any high-priority links, then choose option 1 or option 2 to manually configure the heartbeat links.
See step 2 for option 1, or step 3 for option 2, or step 4 for option 3, or step5 for option 4
- Enter a unique cluster ID:
Enter a unique cluster ID number between 0-65535: [b,q,?] (60842)
The cluster cannot be configured if the cluster ID 60842 is in use by another cluster. Installer performs a check to determine if the cluster ID is duplicate. The check takes less than a minute to complete.
Would you like to check if the cluster ID is in use by another cluster? [y,n,q] (y)
- Verify and confirm the information that the installer summarizes.