vRealize Network Insight 4.1.1 | 11 JUNE 2019 | Build 1559730670

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New?

This release resolves performance and other issues that are documented in the Resolved Issues section.

vRealize Suite Life Cycle Manager 2.1 Product Support Pack 2 supports the installation of vRealize Network Insight 4.1.1. For more information, see VMware vRealize Suite Lifecycle Manager 2.1 Release Notes. For information about install and upgrade Network Insight by using vRealize Suite Lifecycle Manager, see the vRealize Suite Lifecycle Manager Installation, Upgrade, and Management Guide.

Product Upgrade

vRealize Network Insight 4.1.1 supports a direct upgrade from the 3.9, 4.0, and 4.1 versions.

Refer to the Upgrading vRealize Network Insight section for more information on upgrade options.

The upgrade path is available at https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#upgrade&solution=285.

Documentation

For additional information about new features, see the vRealize Network Insight documentation.

VMware Product Compatibility

The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Network Insight with other VMware products.

VMware MIB Files

For MIB information, see Determining the MIB module listing, name, and type of an SNMP OID. You can download the SNMP MIB module file from the 1013445 KB article.

Resolved Issues

  • vRealize Network Insight displays incorrect physical IP count on the License Usage page.

  • You might encounter performance issues with vRealize Network Insight 4.1 intermittently.

  • An out-of-memory error might occur during range based masking computation.

  • You see an Unexpected Error on the VM path Topology widget.

  • ACIRouteStoreConfigProcessor takes a lot of grid time.

  • vRealize Network Insight 4.1 might not allow you to enable SNMP intermittently.

  • If two datacenters with the same name exist when you search for plan datacenter, vRealize Network Insight does not allow you to select the data center on the search result.

  • vRealize Network Insight 4.1 does not allow member users to access the Property Template page under Settings.

  • vRealize Network Insight VMs fails to start when the host CPU clock speed is less than 2.6 GHz.

  • vRealize Network Insight takes a long time to display the license and usage information.

  • In vRealize Network Insight, sometimes the elastic search is not responsive under heavy load.

  • DeviceNeighborhoodComputation takes a long time to process.

  • vRealize Network Insight shows timeout exception when you add switches using API.

  • The FlowHostDVPortProcessorProgram consume more processing power as the number of flows increases.

  • If you have added several switches, vRealize Network Insight stops responding when you search for "Switches".

  • If you have added several switches, vRealize Network Insight stops responding when you search for "Vrfs".

  • Some of the flows do not have any reporters associated, except for 'NI collector'.

  • Elastic search restarts and out of memory error appears in vRealize Network Insight 4.1 intermittently.

  • On the Add Application page, though the physical IPs exist, the count under the Tier section shows zero.

  • vRealize Network Insight allows you to select the Analyze Flows option on the Add Application page even when the application is not saved.

  • While creating Application tier, when you add IPs using the comma separator, vRealize Network Insight does not save all the mentioned IPs.

Known Issues

  • If you have more than 5000 members in an application, then you might not see flow information in the Application Topology pinboard.

  • In vRealize Network Insight 4.1, the Application list might show incorrect numbers of VM.

  • If you modify an existing application, the Virtual Machines / IP Addresses field shows an incorrect count of physical IPs.

  • The Saved Application page does not show the created application details in vRealize Network Insight 4.1.

  • Discovered App list shows incorrect tier count for unclassified VMs.

  • When you search for Kubernetes Nodes in vRealize Network Insight, the search result displays the list of Master Nodes for native kubernetes cluster and not for VMware PKS.

  • In absence of a firewall rule on a VM, default connectivity strategy applies to a VM in VMC.
    In such a case, the firewall icon isn't present in VM-VM path on VMC side as we do not get enough information about the realization of the default rule from the VMC SDDC.

  • If you are using the Firefox browser and viewing the NSX-T VM path Topology, after you expand the ECMP group, you do not see the collapse option to minimize the detail view.

  • When you attempt to export a pinboard in which the pinboard name contains a Non-ASCII character, vRealize Network Insight shows the incorrect file name on the Export to PDF window.

  • When the count of VMs associated to a firewall rule’s source or destination gets updated from a non-zero value to zero, and if you run firewall rule query with source VM or destination VM as a filter, it may give an incorrect result.

  • When you add a filter in the query result, the count shown in the filter are approximate.

  • If OpenID Connect (OIDC) authenticator is used for PKS or Native Kubernetes Cluster, then contact VMware Support.

  • vRealize Network Insight does not detach the NSX-T logical ports from the unhealthy pods or nodes.

  • When you set the home page from My Preferences, it requires a page refresh to reflect that information in UI.

  • After upgrade, the system takes about two to three hours to settle down and to reflect the correct data in the UI.

  • When you attempt to add a Cisco ASA data source, you see a message to contact support with the following error: 

    Message missing required fields: vendorId

  • vRealize Network Insight reports proxy communication failure when the postgres service on the proxy server does not start automatically and the CollectorMain javaservice keeps restarting.

  • If the disk is full on a zookeeper leader node, check-service-health.sh command states that zookeeper is healthy while it is actually unhealthy. To fix this issue, restart zookeeper.

  • The auto-refresh counter restarts and keeps showing incorrect data even though auto-refresh is paused.

  • vRealize Network Insight may not be able to detect an out-of-sync system clock sometimes. If the clock is not in sync with NTP, some services may become unhealthy or stop working.

  • The bundle upload or extraction and the subsequent upgrade steps may fail if there is insufficient space in the /tmp directory. For single-click offline upgrade and online upgrade, ensure that there is a certain amount of disk space available in the /tmp directory.

  • The disk may run out of space for the vRealize Network Insight Platform VM. In large environments, the partition /var may become full and additional storage may be needed. See KB article 53550 for instructions on how to increase disk space.

  • The vRealize Network UI is not available when the partition /var is more than 85% full in the Platform VM. For validation and fix, contact VMware support.

  • An unwanted default rule is applied to certain NSX IPFIX flows. This is because sometimes, NSX IPFIX reports reverse packet in which client and server are flipped and the firewall rule is applied as per the flipped source and destination IP.

  • The Export to CSV feature for the flow data takes more than 30 minutes for 180,000 flows when all the fields are selected.

  • The Export to PDF feature for the PCI dashboard has the following known issues:

    • The changes that you make in the NetFlow flow diagram dashboard are not visible in the PDF.
    • For a particular widget, the number of properties that are exported as PDF is more than the number of properties that are actually selected in that widget.
    • The non-ASCII characters are not being exported correctly to the PDF. The workaround for this issue is to run the sudo apt-get install fonts-wqy-zenhei command on the vRealize Network Insight server to install the additional fonts.​
    • The metric properties are not exported in the PDF.

  • When you create a logical subnet or logical router, a new edge VM is dynamically created to serve this request. The events for this kind of VM are shown.

  • If issues such as upload failure or UI failure come up while performing the centralized upgrade, please contact VMware support.

  • The Plan Security page for the last 2 days takes around 3 minutes to load. A higher response time is seen while executing queries for about 24 hours after migration of a data source between collectors. This is because the same flows are reported, opened, and closed from two different collectors within a span of 24 hours. It leads to multiple versions created for the same flows.

  • Sometimes, the Export to CSV feature fails with the 502 error in the browser. The workaround is to retry the operation.

  • vRealize Network Insight does not support rollback or product downgrade. It is recommended that you take a backup.

  • The datastore metrics of a VM are not shown on vRealize Network Insight if it is hosted on vSAN Datastore.

  • If the vCenter and the associated NSX manager data sources are not attached to the same proxy server, you will not see the denied flows (when NSX IPFIX is enabled) and the Applied Firewall Rule will be missing in some flows.

  • The NAT rules on the NSX Edge version 5.5 or the previous versions are not supported.

  • The firewall rule section of the PCI Compliance dashboard may show incorrect rules if the selected scope is a nested security group in NSX or an application when multiple NSX managers are added as a data source.

  • In the Applied To grouping criteria, the NSX edge is not supported.

  • The platform cluster does not support the high availability configuration. All the platform nodes need to be up and running for the cluster to work at optimal performance levels.

  • The recommended firewall rules support only global rules creation. The creation of universal rules is not supported.

  • The plan topology widget has options to select all flows, all protected flows, and so on. The flows that are solely captured from VDS and not from NSX IPFIX only show up when the all flows option is selected because their protection status is classified as unknown not as protected or unprotected.

  • The Export as CSV option is not supported for advanced searches that use group by, sum, max, and min functionality.

  • Some events such as Host network control plane mismatch are not raised if the datacenter is not at the top level and is located inside a folder in vCenter.

  • The product update notifications are supported only for the single-platform node deployment that is connected to Internet.

  • The support bundle creation on a medium sized system can take in excess of fifteen minutes.

  • There is a known issue in the list view for events search where sometimes facet counts are incorrect upon selection and no events are shown.

  • vRealize Network Insight shows the older version after the upgrade. Once the product upgrade is complete, refresh the browser after clearing the browser cache.

  • Upon the expiry of the Evaluation license, the data providers are disabled and they stop collecting data. After renewing the license, the data providers must be enabled again from the UI to start data collection.

  • To use Gmail® server as the choice of e-mail server, additional configuration settings as listed on Google Support are required.

  • After you remove a data source from the system, you can add the same data provider back only after two or more hours.

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