Unable to find a valid certification path to the vCenter”. One of the goals once deployed was to test integration with vCenter 6.5 however, when I attempted to add my test 6.5 vCenter server, I received an error. The error states “Failed to communicate to vCenter. This entry was posted in VMware and tagged vSphere Replication on 12 January 2015 by Fried.On yesterday’s blog, I was able to deploy Avamar Virtual Edition. If you’re interested in such a script, you can find interesting elements here (I found the trick to delay the alarm there) or here. If you need to block the alarm further, the best approach is probably to abandon the integrated alarm system and go for a powershell script that would check the status of the currentRpoViolation counter, and trigger an email as soon as your custom trigger is reached. I guess that the currentRpoViolation counter is not checked every minute! Theoretically, our customizing would trigger the alarm as soon as we reach the second minute of the RPO violation, but in my tests, the alarm was only triggered after 10 to 16 minutes, which could be satisfying.
And don’t look for a “greater than” operator, there is no such thing :(. By saying “not equal to 1”, we will avoid to trigger the alarm immediately. The currentRpoViolation counter contains the number of minutes since the beginning of the RPO violation. Type currentRpoViolation, not equal to, and 1. Click on Advanced in the Conditions column to define our custom condition. Double-click the RPO alarm and go to the Triggers tab. Once connected, go to hosts and clusters, select the vCenter on the left, Alarms and Definition. The good old C# client can do slightly better, but it is limited too as we will see.
Test vcenter 6.5 email alerts how to#
How to mitigate this problem? We should be able to say something like “trigger the alarm only if the RPO is exceeded by more than 10 minutes”, but it’s not possible in the web client. This is caused by how the replication works: it waits as long as it can to start the synchronization (in order to get the latest changes), and often, the RPO gets exceeded by a few minutes.
With your alarm in production, you will notice that you get way too many emails because the RPO was exceeded by a minute. You should immediately receive the email. Done! You can test the alarm by reducing the RPO of a replication to 15 minutes and copying enough new files to the VM to make the replication fail. Let’s send us an email when the alarm is triggered. Don’t forget to change the status to Normal! Next, the alarm actions. Then we add a second event ( RPO restored) to clear the alarm when everything is fine again. The event that we want to monitor is called RPO violated. In the wizard, name you alarm and choose to monitor virtual machines, specific event. From the Hosts and clusters view, select the vCenter, go to Manage, Alarm definitions and click the green “ +” sign to add an alarm. We’ll start by creating a new alarm in our vSphere client. In this article we will create an alarm to send us an email when the RPO of a replication is violated. But on the long run, this is not an efficient way to monitor ongoing replications.
These monitoring possibilities are interesting when you create a new replication, or when you’re in a troubleshooting session.
Test vcenter 6.5 email alerts series#
In our article series about vSphere Replication, we configured new replications and checked the possibilities for monitoring these replications.