6.7
Table Of Contents
- vSphere Availability
- Contents
- About vSphere Availability
- Business Continuity and Minimizing Downtime
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- How Fault Tolerance Works
- Fault Tolerance Use Cases
- Fault Tolerance Requirements, Limits, and Licensing
- Fault Tolerance Interoperability
- Preparing Your Cluster and Hosts for Fault Tolerance
- Using Fault Tolerance
- Best Practices for Fault Tolerance
- Legacy Fault Tolerance
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- vCenter High Availability
- Plan the vCenter HA Deployment
- Configure the Network
- Configure vCenter HA With the Basic Option
- Configure vCenter HA With the Advanced Option
- Manage the vCenter HA Configuration
- Set Up SNMP Traps
- Set Up Your Environment to Use Custom Certificates
- Manage vCenter HA SSH Keys
- Initiate a vCenter HA Failover
- Edit the vCenter HA Cluster Configuration
- Perform Backup and Restore Operations
- Remove a vCenter HA Configuration
- Reboot All vCenter HA Nodes
- Change the Appliance Environment
- Collecting Support Bundles for a vCenter HA Node
- Troubleshoot Your vCenter HA Environment
- Patching a vCenter High Availability Environment
- Using Microsoft Clustering Service for vCenter Server on Windows High Availability
Set up SNMP traps for the Active node and the Passive node. You tell the agent where to send related
traps, by adding a target entry to the snmpd configuration.
Procedure
1 Log in to the Active node by using the Virtual Machine Console or SSH.
2 Run the vicfg-snmp command, for example:
vicfg-snmp -t 10.160.1.1@1166/public
In this example, 10.160.1.1 is the client listening address, 1166 is the client listening port, and
public is the community string.
3 Enable the SNMP agent (snmpd) by running the following command.
vicfg-snmp -e
What to do next
You also might find these commands useful.
n
To view the complete help for the command, run vicfg-snmp -h.
n
To disable the SNMP agent, run vicfg-snmp -D.
n
To show the SNMP agent's configuration, run vicfg-snmp -s.
n
To reset the configuration to the default, run vicfg-snmp -r.
Set Up Your Environment to Use Custom Certificates
The machine SSL certificate on each node is used for cluster management communication and for
encryption of replication traffic. If you want to use custom certificates, you have to remove the vCenter HA
configuration, delete the Passive and Witness nodes, provision the Active node with the custom
certificate, and reconfigure the cluster.
If possible, replace certificates in the vCenter Server Appliance that will become the Active node before
you clone the node.
Procedure
1 Edit the cluster configuration and select Remove.
2 Delete the Passive node and the Witness node.
3 On the Active node, which is now a standalone vCenter Server Appliance, replace the machine SSL
Certificate with a custom certificate.
See the Platform Services Controller Administration documentation.
4 Reconfigure the cluster.
vSphere Availability
VMware, Inc. 83