NVGRE Gateway Cluster Not Discovered Completely by the Multi-Tenant RRAS MP

In the past I’ve tried Multi-Tenant RRAS Management Pack with NVGRE Gateway that was not in the cluster. Recently I was able to try the MP with NVGRE Gateway cluster but I’ve met some challenges. Even though I’ve configured the override for Network name dependency discovered as instance of Virtual Server the cluster couldn’t be discovered properly and because of that almost all monitors were not working. After I was able to contact some folks from Microsoft we were able to resolve the issue. When you add your NVGRE Gateway cluster to VMM a new role (HyperV Network Virtualization Gateway) is created in the cluster:


In that Role there is an Public IP address as resource.

Basically the discovery script relays that this Public IP address have Network Name type resource assigned to it but that resource is not created during adding the NVGRE Gateway cluster in VMM. That resource is not needed by VMM but is needed by the MP in order to discover the cluster properly and monitor it. The override above allows that resource to be discovered as Virtual Server instance.

The workaround is simple:

  • Add Client Access Point resource to the HyperV Network Virtualization Gateway role assigned to the Public IP address resource


This information will be added soon the Multi-Tenant MP guide. Thanks to all engineers from Microsoft who helped me on this issue.

4 thoughts on “NVGRE Gateway Cluster Not Discovered Completely by the Multi-Tenant RRAS MP

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.