Vsphere cluster, and a DR ESXi host, piggyback and labeling, as host spun up in DR affect things

General
1

So, we have a VxRail (essentially a hyperconverged VSphere cluster) and a standalone ESXi with independent network. Using Veeam, we can bring up VMs that are in our VxRail over and into the standalone ESXi which is part of a recovery process. A single Checkmk monitors both the VxRail and ESXi today. As the VMs are spun up on the ESXi, their entries in Checkmk get an add for new host label, and possibly there could be piggyback confusion/collision. The VMs on the standalone ESXi are not being monitored by Checkmk.

Anyway to keep the “new label” requests from coming through on the “same name match” VMs that are already monitored on the VxRail? Any piggyback risks here as well?

It’s possible that I’ll have to divorce the standalone ESXI env away from our singular Checkmk (is that THE solution?) and deploy a different (maybe independent) Checkmk there.

2

One thing i would consider is the usage of the “Hostname translation for piggybacked hosts” rule to add a prefix to the names from the standalone ESXi. Something like “DR_” as prefix to the piggybacked names from the DR host.
Then there should be no mix of labels or piggyback data anymore.

1 Like
3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.