Veritas InfoScale™ Operations Manager 7.0 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 7.0
- 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 7.0
- Configuring Veritas InfoScale Operations Manager in a high availability and disaster recovery environment
- Configuring Veritas InfoScale Operations Manager in HA 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 HA or DR configurations
- About upgrading the DR configurations
- 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
- Editing the agentless host configuration
- Setting up user access
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication on Management Server
- 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
- Setting up extended attributes
- Downloading price tier information from SORT
- Managing SFHA updates
- Viewing information on the Management Server environment
- Appendix A. Troubleshooting
- Management Server (MS)
- Managed host (MH)
- Management Server (MS)
Upgrading Management Server in DR environment
Before you upgrade Veritas InfoScale Operations Manager in the disaster recovery (DR) environment, keep in mind the following:
The SFM_Services, the SFM_SStore, and the SFM_Xprtld service groups should be online on one of the nodes of Veritas InfoScale Operations Manager in the high availability environment, which is the active node.
Note:
You must upgrade the active node before you upgrade the slave nodes.
To upgrade Management Server in high availability environment
- Follow the steps to upgrade Management Server on the active node, and then, on the slave nodes.
After the upgrade on the active node, the SFM_Services service group, and the SFM_SStore service group, are in a frozen state.
You must upgrade all the slave nodes before you unfreeze the service groups on the active node to prevent issues during failover.
- To unfreeze the service groups on the active node, run the following command:
/opt/VRTSsfmcs/config/vcs/sfmha start
where, installdir is the installation directory.
- You must upgrade all the slave nodes before you unfreeze the service groups on the active node to prevent issues during failover.
- In the console, verify that the SFM_Services, the SFM_SStore, and the SFM_Xprtld service groups are online on the active node.