Veritas™ Resiliency Platform 2.2 Deployment Guide
- Section I. Overview and planning
- Overview of Resiliency Platform
- Recovery to premises using third-party replication technologies
- Recovery to premises using Resiliency Platform Data Mover
- Recovery to AWS using Resiliency Platform Data Mover
- Recovery to vCloud Using Resiliency Platform Data Mover
- System requirements
- Section II. Deploying and configuring the virtual appliances
- Section III. Setting up and managing the resiliency domain
- Setting up the resiliency domain
- Managing Infrastructure Management Servers
- Managing NetBackup and NetBackup Appliances
- Adding NetBackup master server
- Managing Veritas InfoScale Operations Manager Server
- Managing Resiliency Platform Data Mover gateway pairing
- Setting up the resiliency domain
- Section IV. Adding the asset infrastructure
- Managing asset infrastructure
- Preparing and maintaining host assets
- Managing Hyper-V virtualization server assets
- Managing VMware virtualization server assets
- About adding a host for discovery of VMware servers
- Managing enclosure assets
- About the discovery host for enclosures
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Managing asset infrastructure
- Section V. Managing users and global product settings
- Managing licenses
- Managing user authentication and permissions
- Configuring authentication domains
- Managing service objectives
- Managing reports
- Managing settings
- Section VI. Updating or uninstalling the product
- Updating Resiliency Platform
- Using YUM virtual appliance as YUM server
- Uninstalling Resiliency Platform
- Updating Resiliency Platform
- Section VII. Troubleshooting and maintenance
- Troubleshooting and maintenance
- Displaying risk information
- Troubleshooting and maintenance
- Section VIII. Reference
Configuring the VMware vCenter Server to generate SNMP traps
When the VMware vCenter Server is configured for discovery, the IMS automatically registers itself in one of the slots available in the vCenter Server for SNMP trap receiver. If this automatic registration fails, you need to do one of the following:
Remove the vCenter Server configuration from Resiliency Manager, make a SNMP slot receiver available in the vCenter Server, and then reconfigure the vcenter for discovery.
Manually configure IMS in one of the SNMP trap receiver slots in the vCenter Server configuration
In the VMware vCenter Server console, provide the following information to configure the vCenter Server to generate SNMP traps and send them to the IMS:
Configure the Infrastructure Management Server (IMS) manually as the SNMP trap receiver, as follows:
Navigate to the SNMP configuration. Enable one of the SNMP receivers and enter the following details:
Field
Description
Receiver URL
Provide the host name of the IMS which will be connected to the vCenter Server. The vCenter Server sends the SNMP traps to this IMS.
Also, configure port 162 as the SNMP port. Ensure that port 162 is not used by any other application in IMS.
Community String
Provide community string. SNMP versions v1 and v2 are supported.
Configure an alarm for generating SNMP traps when a virtual machine state changes or any virtual infrastructure-related change occurs.
This step includes adding an alarm to monitor the changes related to virtual machine state and vCenter Server infrastructure, and then adding the appropriate action (for example, send a notification trap).
You can set the alarm at an individual virtual machine level, at the data center level, or at the entire VMware vCenter Server level. It is recommended to set it at the vCenter Server level.
For the alarm type details, make sure to specify the following
Set the alarm type to monitor virtual machines
Set the alarm to monitor for specific events occurring on this object, for example, VM powered on
Enable the alarm
Add the required triggers to monitor the states of the virtual machine. For example, VM created, VM migrated, VM powered on, VM powered off, VM suspended, DRS VM powered on (for clustered environment with DRS enabled) and so on. The values of the fields are as follows:
For the following value of an event...
Select the following status...
VM powered on
Unset
VM powered off
Unset
DRS VM powered on
Unset
VM suspended
Unset
VM created
Unset
VM migrated
Unset
VM relocating
Unset
VM renamed
Unset
DRS VM migrated
Unset
Add the required triggers to monitor the states of the hosts. The values of the fields are as follows:
For the following value of an event...
Select the following status...
Host disconnected
Unset
Host connected
Unset
Add a new action to send a notification trap. Specify to send the notification trap as in the following example: