Veritas InfoScale™ Operations Manager 8.0.2 Installation and Configuration Guide
- Section I. Installing and configuring Veritas InfoScale Operations Manager
- Planning your Veritas InfoScale Operations Manager installation
- Downloading Veritas InfoScale Operations Manager 8.0.2
- Typical Veritas InfoScale Operations Manager deployment configuration
- System requirements
- Installing, upgrading, and uninstalling Veritas InfoScale Operations Manager
- About installing Management Server
- About installing managed host
- About upgrading Management Server
- About backing up and restoring Veritas InfoScale Operations Manager data
- About upgrading managed hosts to Veritas InfoScale Operations Manager 8.0.2
- Configuring Veritas InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring the high availability feature in Veritas InfoScale Operations Manager
- Configuring a new Veritas InfoScale Operations Manager installation in high availability environment
- Configuring an existing Veritas InfoScale Operations Manager installation in high availability environment
- Configuring a new Veritas InfoScale Operations Manager installation in high availability environment
- Configuring Management Server in one-to-one DR environment
- Configuring Veritas InfoScale Operations Manager in high availability and disaster recovery environment
- About upgrading the high availability configurations
- About upgrading the high availability and disaster recovery configurations
- Configuring the high availability feature in Veritas InfoScale Operations Manager
- Installing and uninstalling Veritas InfoScale Operations Manager add-ons
- Uploading a Veritas InfoScale Operations Manager add-on to the repository
- Installing a Veritas InfoScale Operations Manager add-on
- Uninstalling a Veritas InfoScale Operations Manager add-on
- Removing a Veritas InfoScale Operations Manager add-on from the repository
- Canceling deployment request for a Veritas InfoScale Operations Manager add-on
- Installing a Veritas InfoScale Operations Manager add-on on a specific managed host
- Uninstalling a Veritas InfoScale Operations Manager add-on from a specific managed host
- Planning your Veritas InfoScale Operations Manager installation
- Section II. Setting up the Management Server environment
- Basic Veritas InfoScale Operations Manager tasks
- Adding and managing hosts
- Overview of host discovery
- Overview of agentless discovery
- About installing OpenSSH on a UNIX host
- Adding the managed hosts to Management Server using an agent configuration
- Adding the managed hosts to Management Server using an agentless configuration
- Adding Agentless hosts to the Management Server using Profile
- Editing the agentless host configuration
- Setting up user access
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication on Management Server
- Configuring LDAP using CLI
- Setting up fault monitoring
- Creating rules in the Management Server perspective
- Editing rules in the Management Server perspective
- Deleting rules in the Management Server perspective
- Enabling rules in the Management Server perspective
- Disabling rules in the Management Server perspective
- Suppressing faults in the Management Server perspective
- Suppressing a fault definition in the Management Server perspective
- Setting up virtualization environment discovery
- Setting up near real-time discovery of VMware events
- Requirements for discovering the Solaris zones
- Adding a virtualization server
- Editing a virtualization discovery configuration
- Refreshing a virtualization discovery configuration
- Deploying hot fixes, packages, and patches
- Installing a Veritas InfoScale Operations Manager hot fix, package, or patch
- Configuring Management Server settings
- Configuring SNMP trap settings for alert notifications
- Setting up extended attributes
- Viewing information on the Management Server environment
- Appendix A. Troubleshooting
- Management Server (MS)
- Managed host (MH)
- Management Server (MS)
Creating the base service groups for HA configuration
For HA configuration, you need to create some base service groups and resources, and add some dependencies between the resources.
To perform this task, your user group must be assigned the Admin role on the cluster or the Availability perspective. The permission on the cluster may be explicitly assigned or inherited from a parent Organization.
You need to create following service groups with their respective resources:
Table:
Service group | Resource |
---|---|
SFM_SStore |
|
SFM_Services |
|
Note:
You need to use the service group names and resource names as suggested. Failure to do so will result in configuration failure.
For the resources that you can create on the SFM_SStore service group for Windows cluster, refer to the following table:
Resource name
Resource type
Attributes
SFM_SStore_DG
VMDg
Diskgroup: Disk group that is specified for the failover.
Note:
You must create a clustered disk group.
For the resources that you can create on the SFM_SStore service group for Linux cluster, refer to the following table:
Resource name
Resource type
Attributes
SFM_SStore_DG
Disk group
Diskgroup: Disk group that is specified for the failover.
For the resources that you can create on the SFM_Services service group for a Windows cluster, refer to the following table:
Resource name
Resource type
Attributes
SFM_Services_IP
IP
Address: Virtual IP address.
MACAddress: Physical address of NIC, to which virtual IP address is assigned. This address is always local and different for each system.
SubNetMask: Subnet mask that is associated with the IP address.
SFM_Services_NIC
NIC
Device: Name of the NIC where virtual IP is plumbed.
SFM_Services_Mount
Mountv
MountPath: The drive letter that is assigned to the volume being mounted.
VMDGResName: Name of the disk group resource (SFM_SStore_DG).
Volume Name: Name of the volume to be mounted.
For the resources that you can create on the SFM_Services service group for a Linux cluster, refer to the following table:
Resource name
Resource type
Attributes
SFM_Services_IP
IP
Address: Virtual IP address, which you have configured along with the virtual host name.
Device: Name of the NIC where virtual IP is plumbed.
NetMask: Subnet mask that is associated with the virtual IP address.
SFM_Services_NIC
NIC
Device: Name of the NIC where virtual IP is plumbed.
SFM_Services_Mount
Mount
MountPoint: Mount point name of the file system that is specified for failover.
Block Device: Complete path of the storage device that is specified for failover. For example,
/dev/vx/dsk/disk group/volume name
.FSType: Type of the file system (VxFS).
FsckOpt: File check option (fsckpt = -n or -y).
For more information on configuring resources, refer to the Veritas Cluster Server Bundled Agents Reference Guide.
After creating the base service groups and resources, you need to link those base service groups and resources as following:
SFM_Services | Parent Group |
SFM_SStore | Child Group |
Relationship | Online Local |
Dependency Type | Hard |
For
service group, link the resource as parent and as child resource.Note:
You need to setup the autostart list for
and service groups to make the services start on a particular node in case of reboot of both the nodes at the same time.