This section provides details of the known issues.

Hierarchy mismatch in case of multi-tenancy

The vRealize Operations Management Pack for NSX Advanced Load Balancer collects all the resources of a tenant. However, if the same cloud is used across tenants, the relationship hierarchy lists all the child objects of the cloud collected across all tenants. This affects the count of virtual services displayed when the service engine group is shared across tenants.

Workaround: None

Certain objects are not collected

Upgrade of the NSX Advanced Load Balancer or the addition or removal of a tenant by the user, leads to collection cycles that do not work as expected.

Workaround: Reconfigure the vRealize Operations Management Pack for NSX Advanced Load Balancer.

Some metrics/properties may return incorrect results

In some versions of the NSX Advanced Load Balancer, because of a bug in the API exposed by the NSX Advanced Load Balancer, the following metrics/properties may return incorrect results:
  • VS VIP, Virtual Hosting, Application Domain Name
  • Client RTT and Server RTT for Virtual Service
  • Pool metrics in some cases

In some cases, intermittent API failures from the NSX Advanced Load Balancer occur, because of which metrics may not be collected for that particular collection cycle.

Workaround: None

The service engine object type may be associated with the wrong machine

In rare scenarios, when a service engine such as an EC2 Instance/virtual machine/Azure VM/Compute Instance in vRealize Operations is created with the same name and within the same cloud, the service engine object type may be associated with the wrong machine.

Workaround: Use different name prefixes if multiple cloud accounts of the same type are used.