VMware vRealize Operations Management Pack for NSX-T | 17 OCT 2019 | Build 14793972

What's in the Release Notes

The release notes cover the following topics:

What's New

NSX-T security configurations are added to calculate the compliance for NST-T Manager.

Compatibility

For compatibility between products, please refer to the VMware Product Interoperability Matrices.

Known Issues

  • Openstack's NSX-T upgrade fails if you first install the Management Pack for NSX-T on vRealize Operations Manager

    If the vRealize Operations Manager is already installed with the Management Pack for NSX-T 2.1 first, the Openstack Management Pack upgrade fails when you install the Management Pack for Openstack 5.0 on the same vRealize Operations Manager setup.

    The Openstack's NSX-T will not display latest details of NSX-T 2.1 as the override fails.

     

    Workaround:

    Install the Management Pack for Openstack 5.0 before installing the Management Pack for NSX-T 2.1.

  • Management Pack for NSX-T contains the NSS service resource type

    The Management Pack for NSX-T display the details of NSS services resources under its inventory. However, the Management Pack for NSX-T does not collect data for NSS services.

    Workaround:None

  • Management Pack for NSX-T does not collect data for Edge Nodes

    The Management Pack for NSX-T displays the details of the resource type 'Edge Nodes' under its inventory. However, the Management Pack for NSX-T does not collect data for Edge Nodes.

    Workaround:None

  • Automatic configuration of NSX-T adapter instance when you re-install the Management Pack for NSX-T

    When the Management Pack for NSX-T and the Management Pack for Openstack are installed on same vRealize Operations Manager setup, uninstalling the Management Pack for NSX-T will successfully uninstall the NSX-T management pack, but does not remove it from the Management Pack for OpenStack. Due to this, re-installing the Management Pack for NSX-T will automatically configure the NSX-T adapter instance.

    Workaround:

    1. Delete the NSX-T adapter instance from the Management Pack for NSX-T.
    2. Delete the NSX-T adapter instance from the Management Pack for Openstack, if it is not already deleted.  
    3. Uninstall the Management Pack for NSX-T.
    4. Re-install the Management Pack for NSX-T on the same setup.
  • An Edge Node that does not belong to any Edge Cluster is not discovered.

    An edge node has to be a part of edge cluster to be consumed by logical routers/gateways. One edge node can be part of only one edge cluster. Only those edge nodes that belong to a cluster are discovered by the Management Pack for NSX-T.

    Workaround: Add the edge node to any one of the available edge clusters.

  • Upgrading from Management Pack for NSX-T 2.0 to 2.1 recreates objects for the existing resources

    After upgrading the Management Pack for NSX-T from 2.0 to 2.1, most of the objects are recreated for the existing resources. The existing objects go into non-existing state after certain time.

    Workaround: None

  • VMware SDDC Health Monitoring Solution 6.0 does not monitor hierarchy for the Management Pack for NSX-T​ 2.1

    For VMware SDDC Health Monitoring Solution 6.0, the health for NSX-T is not updated for the child objects with serious/critical alerts.

    Workaround: None

  • vRealize Operations Management Pack for VMware Cloud Provider Pod 2.0 does not monitor hierarchy for the Management Pack for NSX-T 2.1

    For vRealize Operations Management Pack for VMware Cloud Provider Pod 2.0, the health for NSX-T is not updated for the child objects that have serious/critical alerts.

    Workaround: None

  • Test connection for NSX-T adapter instance fails with VMware Identity Manager's user credentials

    If the Management Pack for NSX-T is configured with the VMware Identity Manager, then the NSX-T adapter instance cannot be configured with the imported VMware Identity Manager's user credentials.

    Workaround:None

  • Management Pack for NSX-T 2.1 does not discover the LB Service/Load Balancer that is not connected to any LB virtual server 

    The Management Pack for NSX-T 2.1 collects data only when the LB Service/Load Balancer is connected to the LB virtual server. Also, the LB Virtual Server has to be connected to the LB Service/Load Balancer to collect data.

    Workaround:

    Attach the LB virtual server to the LB Service/Load Balancer.

  • Management Pack for NSX-T 2.1 fails to collect data on vRealize Operations Manager 7.0

    When you configure the adapter instance for NSX-T 2.1 on vRealize Operations Manager 7.0, the data collection status changes to None.

    The NSX-T adapter's collector logs in the vRealize Operations Manager displays the following exception after the adapter instance is configured:

     java.lang.NoSuchMethodError:com.vmware.ops.api.client.Client.productLicensingClient()Lcom/vmware/ops/api/client/controllers/ProductLicensingClient;

    Workaround:

    Login to the vRealize Operations Manager and upgrade the Management Pack for NSX-T with the latest build

check-circle-line exclamation-circle-line close-line
Scroll to top icon