Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Linux
  1. Section I. Configuring SF Sybase ASE CE
    1. Preparing to configure SF Sybase CE
      1.  
        About this document
      2.  
        Supported Sybase ASE CE releases
      3.  
        Supported SF Sybase CE configurations
      4.  
        Coordinator disk requirements for I/O fencing
      5.  
        Supported replication technologies for global clusters
      6. About planning to configure I/O fencing
        1.  
          Typical SF Sybase CE cluster configuration with disk-based I/O fencing
      7.  
        Planning for cluster management
    2. Configuring SF Sybase CE
      1.  
        About configuring SF Sybase CE
      2. Configuring the SF Sybase CE components using the script-based installer
        1. Configuring the SF Sybase CE cluster
          1.  
            Configuring the cluster name
          2.  
            Configuring private heartbeat links
          3.  
            Configuring the virtual IP of the cluster
          4. Configuring SF Sybase CE in secure mode
            1.  
              Setting up trust relationships for your SF Sybase CE cluster
          5. Configuring a secure cluster node by node
            1.  
              Configuring the first node
            2.  
              Configuring the remaining nodes
            3.  
              Completing the secure cluster configuration
          6.  
            Adding VCS users
          7.  
            Configuring SMTP email notification
          8.  
            Configuring SNMP trap notification
          9.  
            Configuring global clusters
    3. Configuring SF Sybase CE clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Initializing disks as VxVM disks
        2.  
          Identifying disks to use as coordinator disks
        3.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
        4. Checking shared disks for I/O fencing
          1.  
            Verifying Array Support Library (ASL)
          2.  
            Verifying that the nodes have access to the same disk
          3.  
            Testing the disks using vxfentsthdw utility
        5.  
          Configuring disk-based I/O fencing using installer
    4. Performing an automated SF Sybase CE configuration
      1.  
        Configuring SF Sybase CE using response files
      2.  
        Response file variables to configure SF Sybase CE
      3.  
        Sample response files for configuring SF Sybase CE
    5. Performing an automated I/O fencing configuration using response files
      1.  
        Configuring I/O fencing using response files
      2.  
        Response file variables to configure disk-based I/O fencing
      3.  
        Sample response file for configuring disk-based I/O fencing
    6. Configuring a cluster under VCS control using a response file
      1.  
        Configuring a Sybase cluster under VCS control with a response file
      2.  
        Response file variables to configure SF Sybase CE in VCS
  2. Section II. Post-installation and configuration tasks
    1. Verifying the installation
      1.  
        Upgrading the disk group version
      2.  
        Performing a postcheck on a node
      3.  
        Verifying SF Sybase CE installation using VCS configuration file
      4. Verifying LLT, GAB, and cluster operation
        1.  
          Verifying LLT
        2.  
          Verifying GAB
        3.  
          Verifying the cluster
        4.  
          Verifying the cluster nodes
    2. Performing additional post-installation and configuration tasks
      1. About enabling LDAP authentication for clusters that run in secure mode
        1.  
          Enabling LDAP authentication for clusters that run in secure mode
      2.  
        Configuring Volume Replicator
      3.  
        Running SORT Data Collector to collect configuration information
  3. Section III. Upgrade of SF Sybase CE
    1. Planning to upgrade SF Sybase CE
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Performing a full upgrade of SF Sybase CE using the product installer
      1.  
        About full upgrades
      2.  
        Preparing to perform a full upgrade to SF Sybase CE 7.4.1
      3. Upgrading to SF Sybase CE 7.4.1
        1.  
          Upgrading SF Sybase CE using the Veritas installation program
    3. Performing an automated full upgrade of SF Sybase CE using response files
      1.  
        Upgrading SF Sybase CE using a response file
      2.  
        Response file variables to upgrade SF Sybase CE
      3.  
        Sample response file for upgrading SF Sybase CE
    4. Performing a phased upgrade of SF Sybase CE
      1.  
        About phased upgrade
      2. Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
        1.  
          Step 1: Performing pre-upgrade tasks on the first half of the cluster
        2.  
          Step 2: Upgrading the first half of the cluster
        3.  
          Step 3: Performing pre-upgrade tasks on the second half of the cluster
        4.  
          Step 4: Performing post-upgrade tasks on the first half of the cluster
        5.  
          Step 5: Upgrading the second half of the cluster
        6.  
          Step 6: Performing post-upgrade tasks on the second half of the cluster
    5. Performing a rolling upgrade of SF Sybase CE
      1.  
        About rolling upgrade
      2.  
        Supported rolling upgrade paths
      3.  
        Preparing to perform a rolling upgrade to SF Sybase CE 7.4.1
    6. Performing post-upgrade tasks
      1.  
        Re-joining the backup boot disk group into the current disk group
      2.  
        Reverting to the backup boot disk group after an unsuccessful upgrade
      3.  
        Setting or changing the product license level
      4.  
        Upgrading disk layout versions
      5.  
        Upgrading CVM protocol version and VxVM disk group version
  4. Section IV. Installation and upgrade of Sybase ASE CE
    1. Installing, configuring, and upgrading Sybase ASE CE
      1.  
        Before installing Sybase ASE CE
      2.  
        Preparing for local mount point on VxFS for Sybase ASE CE binary installation
      3.  
        Preparing for shared mount point on CFS for Sybase ASE CE binary installation
      4.  
        Installing Sybase ASE CE software
      5.  
        Preparing to create a Sybase ASE CE cluster
      6.  
        Creating the Sybase ASE CE cluster
      7. Preparing to configure the Sybase instances under VCS control
        1.  
          Language settings for the Sybase agent
        2.  
          Configuring Sybase for detail monitoring
        3.  
          Encrypting passwords for Sybase
        4. About setting up detail monitoring for the agent for Sybase
          1.  
            Enabling detail monitoring for the agent for Sybase
          2.  
            Disabling detail monitoring for the agent for Sybase
      8.  
        Configuring a Sybase ASE CE cluster under VCS control using the SF Sybase CE installer
      9.  
        Upgrading Sybase ASE CE
  5. Section V. Adding and removing nodes
    1. Adding a node to SF Sybase CE clusters
      1.  
        About adding a node to a cluster
      2.  
        Before adding a node to a cluster
      3. Adding the node to a cluster manually
        1.  
          Starting Veritas Volume Manager (VxVM) on the new node
        2.  
          Configuring cluster processes on the new node
        3. Setting up the node to run in secure mode
          1.  
            Configuring the authentication broker on node sys5
        4.  
          Starting fencing on the new node
        5.  
          Configuring Cluster Volume Manager (CVM) and Cluster File System (CFS) on the new node
        6.  
          After adding the new node
        7.  
          Configuring the ClusterService group for the new node
      4.  
        Adding a node to a cluster using the Veritas InfoScale installer
      5. Adding the new instance to the Sybase ASE CE cluster
        1.  
          Creating Sybase user and groups
        2.  
          Preparing the mount point for Sybase resources on the new node
        3.  
          Adding a new Sybase ASE CE instance to the Sybase ASE CE cluster
        4.  
          Bringing the new Sybase ASE CE instance under VCS control
    2. Removing a node from SF Sybase CE clusters
      1.  
        About removing a node from a cluster
      2.  
        Removing a node from a cluster
      3.  
        Modifying the VCS configuration files on existing nodes
      4.  
        Modifying the Cluster Volume Manager (CVM) configuration on the existing nodes to remove references to the deleted node
      5.  
        Removing security credentials from the leaving node
  6. Section VI. Configuration of disaster recovery environments
    1. Configuring disaster recovery environments
      1.  
        Disaster recovery options for SF Sybase CE
      2.  
        About setting up a global cluster environment for SF Sybase CE
      3.  
        About configuring a parallel global cluster using Volume Replicator (VVR) for replication
  7. Section VII. Installation reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. Sample installation and configuration values
      1.  
        SF Sybase CE installation and configuration information
      2.  
        SF Sybase CE worksheet
    3. Appendix C. Tunable files for installation
      1.  
        About setting tunable parameters using the installer or a response file
      2.  
        Setting tunables for an installation, configuration, or upgrade
      3.  
        Setting tunables with no other installer-related operations
      4.  
        Setting tunables with an un-integrated response file
      5.  
        Preparing the tunables file
      6.  
        Setting parameters for the tunables file
      7.  
        Tunables value parameter definitions
    4. Appendix D. Configuration files
      1.  
        About sample main.cf files
      2. Sample main.cf files for Sybase ASE CE configurations
        1.  
          Sample main.cf for a basic Sybase ASE CE cluster configuration under VCS control with shared mount point on CFS for Sybase binary installation
        2.  
          Sample main.cf for a basic Sybase ASE CE cluster configuration with local mount point on VxFS for Sybase binary installation
        3.  
          Sample main.cf for a primary CVM VVR site
        4.  
          Sample main.cf for a secondary CVM VVR site
    5. Appendix E. Configuring the secure shell or the remote shell for communications
      1. About configuring secure shell or remote shell communication modes before installing products
        1.  
          Manually configuring passwordless ssh
        2.  
          Setting up ssh and rsh connection using the installer -comsetup command
        3.  
          Setting up ssh and rsh connection using the pwdutil.pl utility
        4.  
          Restarting the ssh session
        5.  
          Enabling rsh for Linux
    6. Appendix F. High availability agent information
      1. About agents
        1.  
          VCS agents included within SF Sybase CE
        2.  
          VCS agent for Sybase included within SF Sybase CE
      2. CVMCluster agent
        1.  
          Entry points for CVMCluster agent
        2.  
          Attribute definition for CVMCluster agent
        3.  
          CVMCluster agent type definition
        4.  
          CVMCluster agent sample configuration
      3. CVMVxconfigd agent
        1.  
          Entry points for CVMVxconfigd agent
        2.  
          Attribute definition for CVMVxconfigd agent
        3.  
          CVMVxconfigd agent type definition
        4.  
          CVMVxconfigd agent sample configuration
      4. CVMVolDg agent
        1.  
          Entry points for CVMVolDg agent
        2.  
          Attribute definition for CVMVolDg agent
        3.  
          CVMVolDg agent type definition
        4.  
          CVMVolDg agent sample configuration
      5. CFSMount agent
        1.  
          Entry points for CFSMount agent
        2.  
          Attribute definition for CFSMount agent
        3.  
          CFSMount agent type definition
        4.  
          CFSMount agent sample configuration
      6. Process agent
        1.  
          Agent functions
        2.  
          State definitions
        3.  
          Attributes
        4.  
          Resource type definition
        5.  
          Sample configurations
      7.  
        Monitoring options for the Sybase agent
      8. Sybase resource type
        1.  
          Type definition for the Sybase agent
        2.  
          Attribute definitions for the Sybase agent

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

  1. 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.

  2. 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) 
  3. 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)
  4. 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)
    
  5. 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
    
  6. 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)
  7. 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.

  8. 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

  9. 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)
  10. Verify and confirm the information that the installer summarizes.