Veritas InfoScale™ Operations Manager 8.0.2 Installation and Configuration Guide

To create SFM_SStore and SFM_Services

1. Install InfoScale 8.0.2 on cluster nodes (Primary and Secondary).
2. Plumb VIP on primary node to configure.

   For example: ifconfig ens192:1 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx up

3. Configure VIOM CMS on primary node using VHN and VIP.

   Note:

   Install VIOM binary and do not configure VIOM CMS on secondary node.

4. Add secondary node (as a Agent) to the configured CMS.
5. Create diskgroup using shared luns on primary node.

   For example: # vxdg init testdg (disk_name)

6. Create volume on created diskgroup.

   For example: # vxassist -g testdg make testvol 10G

7. Create VxFS filesystem on created volume.

   For example: # mkfs -t vxfs /dev/vx/rdsk/testdg/testvol

8. Create empty directory to mount VxFS file system on created volume.

   For example: # mkdir /testvol

9. Mount VxFS file system on created volume.

   For example: # mount -t vxfs /dev/vx/dsk/testdg/testvol /testvol

   After mounted file system, please note down device path, it will require to provide the inputs while creating service group. For example: # df -h /dev/vx/dsk/testdg/testvol

10. Unplumb VIP on primary node.

    For example: # ifconfig ens192:1 down

11. Deport Diskgroup.

    For example: # vxdg deport testdg

12. Run the script.

    For example: # [root@example1 /]# /opt/VRTSsfmcs/config/vcs/createha.pl

    The following script will create the prerequisite VCS resources 
    to configure VIOM in a High Availability configuration:
    
    Please ensure that you have addressed the following items 
    prior to running the script:
    
    1.  The virtual IP to be chosen must be within the same IP subnet,
        and should not be plumbed.
        The VIP Will be brought online using the SFM_Services_IP resource
    2.  A VxVM disk group and volume for the VIOM data must have already
        been created, with a VxFS filesystem written to that volume
    3.  The filesystem should be unmounted, and the disk group 
        should be deported prior to running the script 
        as VCS will import it with cluster reservations.
    4.  The VIOM virtual IP and virtual hostname should be added 
        as a new entry to /etc/hosts on each of the cluster nodes.
    
    VIP :xxx.xxx.xxx.xxx
    NetMask :xxx.xxx.xxx.xxx
    Nic :ens192
    DiskGroup :testdg
    MountPoint :/testvol
    BlockDevice :/dev/vx/dsk/testdg/testvol
    VCS WARNING V-16-1-10364 Cluster already writable.
    VCS NOTICE V-16-1-10136 Group added; populating SystemList and 
    setting the Parallel attribute recommended before adding resources
    /opt/VRTSvcs/bin/hagrp -modify SFM_SStore SystemList  
    example1 0 example2 1
    VCS NOTICE V-16-1-10242 Resource added. Enabled attribute 
    must be set before agent monitors
    VCS NOTICE V-16-1-10136 Group added; populating SystemList 
    and setting the Parallel attribute recommended before adding resources
    VCS NOTICE V-16-1-10242 Resource added. Enabled attribute 
    must be set before agent monitors
    VCS NOTICE V-16-1-10242 Resource added. Enabled attribute 
    must be set before agent monitors
    VCS NOTICE V-16-1-10242 Resource added. Enabled attribute 
    must be set before agent monitors
    [root@example1 /]#
    

13. Verify the created SFM_SStore and SFM_Services service groups.

    # hagrp -state
     [root@example1 /]# hagrp -state
     #Group       Attribute            System      Value
     SFM_SStore   State                example1 |ONLINE|
     SFM_SStore   State                example2 |OFFLINE|
     SFM_Services State                example1 |ONLINE|
     SFM_Services State                example2 |OFFLINE|
     cvm          State                example1 |ONLINE|
     cvm          State                example2 |ONLINE|
    [root@example1.com /]#