vRealize Network Insight 6.3 | 13 Jul 2021| Build 1625072760
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Product Upgrade
- VMware Product Compatibility
- VMware MIB Files
- Resolved Issues
- Known Issues
Here are the key features and capabilities of vRealize Network Insight 6.3:
Network Assurance and Verification
- Introduces new Intent to check for HSRP/VRRP configuration error.
- Provides the ability to view network map in full screen.
NSX-T Monitoring and Troubleshooting
- Provides support for OpenShift 4.x with NSX-T container plug-in when added as an individual OpenShift 4.x cluster using kubeconfig.
- Shows Packets Per Second (PPS) metric on VMware NSX-T manager dashboard. Also, provides PPS-related search queries.
- Around 40 plus NSX-T events are optimized for quick notification under 5 minutes. See NSX-T Events.
VMware Cloud on AWS
- Shows Configuration Maximum alerts and trends related to network and security.
VMware Cloud on Dell EMC
- Provides support for VMware Cloud on Dell EMC.
- Added Sankey chart with traffic insights from source to destination Edge traffic
- Introduction of tunnel topology
- Provides support for 15-node XL clusters.
- Provides the ability to customize polling intervals for physical data sources. The polling interval can be set between 10 mins up to 7 days.
- Shows PPS metrics for the routers and the switches. Also, you can use search queries for PPS.
- Nomenclature changed from VMware Cloud (VMC) on AWS to VMware Cloud (VMC) on the Accounts and Data Sources page, Environments section on the left navigation, and the Homepage banner.
- Network Utilization Widget now shows line charts with coarser data for duration beyond 48 hours, average values beyond 48 hours, friendly names of metrics shown on the widget, and allows CSV data export beyond 48 hours
- vRealize Suite Lifecycle Manager 8.4.1 Product Support Pack 2 supports the installation of vRealize Network Insight 6.3. See VMware vRealize Suite Lifecycle Manager 8.4.1 Release Notes. To install and upgrade vRealize Network Insight by using vRealize Suite Lifecycle Manager, see the vRealize Suite Lifecycle Manager Installation, Upgrade, and Management Guide.
The supported upgrade path is available at https://interopmatrix.vmware.com/#/Upgrade?productId=285.
Refer to the Upgrading vRealize Network Insight section for more information on the upgrade procedure.
For additional information about new features, see the vRealize Network Insight documentation.
- Installing vRealize Network Insight
- Using vRealize Network Insight
- vRealize Network Insight FAQs
- vRealize Network Insight Command Line Interface Guide
- vRealize Network Insight API Guide
Note: As you use the vRealize Network Insight documentation, we want you to know that we value inclusion at VMware. To foster this principle within our customers, partners, and internal communities, we have updated some terminology in our documentation.
The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Network Insight with other VMware products.
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 VMware Knowledge Base Article: 1013445.
HSRP/VRRP Master and STP Root Co-location intent is not supported for Juniper devices.
vRealize Network Insight path search results traversing through switchless F5 BIG-IP Load Balancer platforms (2xxx, 4xxx, i2xxx, i4xxx, and VE) show up as "Blocked” at the F5, as these F5 models do not provide MAC address table output.
Additionally these F5 model devices cannot be used as intermediate hop in the path search.
In F5, port mode is not available when the interface is associated with the trunks interfaces. This causes a port mode mismatch with the switch ports of the neighboring devices.
In the Network Map model, Palo Alto rules with destination zone set to 'any', do not get applied to the same zone pair.
F5 BIG-IP validation fails if TMSH is not enabled from the F5 BIG-IP UI for the user account.
In the Network Map path search, bidirectional path search queries destined to external IP addresses are truncated at the end of the forward path.
For VMware vSphere Distributed Switches (VDS), raw data information is not available in the Network Map UI. If you click on the VDS links from the path search option of the Network Map, the UI becomes unresponsive.
In the Applications on Edges widget of the VeloCloud Enterprise page, you may see the "Encountered an error" message.
In the VM details page, the Path to Internet widget does not show the gateway firewall rule applied to the VPN tunnel interface.
In the SDDC and the NSX Policy Manager Dashboard, the T0 Router Interface metrics show a "No data to show" message. There is an API change in VMware Cloud on AWS version 1.15. Because of the changes, vRealize Network Insight is unable to collect these metrics to display the data in the T0 Router Interface metrics widget.
You could not enable support tunnel by running the offline-registration command.
vRealize Network Insight attempts to connect to the cloud provider specific IP address 100.100.100.200 over port 80.
After upgrade, you observe a high lag in processing data on the new setup.
You could not monitor the latency data in NSX managed vRealize Network Insight setup.
You see the null pointer exception while attempting to connect the HPE 5900 data source.
The LLDP information on vRealize Network Insight and vCenter Server does not match.
The collector does not reuse the SSH connections when gathering data from CISCO UCS and leads to multiple open connections on the management interface of the device.
You did not receive alarm or notification about the High Disk Utilization Event.
Though there is no grid lag. the UI is reporting a high grid lag.
You could not see the flows on the UI when you search with the VM name, but could see the flow data when searching with the IP addresses.
You do not see the BGP Status on the UI after system maintenance.
You could not see any NSX-T related data like flows, path, topology on the UI.
You could not validate the collectors that are reaching platforms.
vRealize Network Insight did not collect some VM data and so it does not show the data flow or resource status of the VM.
You cannot create a log bundle on the UI for one collector.
The pins on a pinboard likeTop Talkers, Network Performance, Micro-segmentation stop working within a week’s time.
Note: The issue is fixed In vRealize Network Insight Cloud only.
[NEW] During vRealize Network Insight 6.3 deployment, the Copy Link on the Add collector VM page incorrectly points to vRealize Network Insight 5.3.0 download page.
Download the vRealize Network Insight 6.3.0 collector OVA file from the Product Download page.
[NEW] The HSRP/VRRP Configuration Error intent is not supported for Cisco ASR 9000 devices.
[NEW] When multiple STP ports configured on a single device that do not have a corresponding co-located HSRP/VRRP active, the HSRP/STP colocation intent raises a violation for only one interface from a set of 'n' interfaces.
[NEW] If you type subnet address as CIDR notation in the Network Map path search, vRealize Network Insight might return an invalid result or traffic header outside the range of the subnet address.
[NEW] Before upgrade, if the VeloCloud Edge Down Alert is open, the following two queries does not work after you upgrade the setup:
- VeloCloud Edge Down Alert where Edge is set
- VeloCloud Edge Down Alert where Edge = <EdgeName>
[NEW] ESXi hosts peered with an uplinked physical switch over an VLAN interface might have misconfigured (Access / Trunk) port tag types. Port mode mismatch intent does not raise an alert when such misconfiguration is detected.
[NEW] You cannot edit the SD-WAN Edge Uplink Utilization intents if you have set the is outside range threshold condition under the exception category.
Re-enter the same values for “is outside range” condition.
[NEW] Certain error messages do not change text as per the browser locale settings.
[NEW] When HSRP/VRRP is configured with different virtual IP addresses for the same HSRP/VRRP group in two devices, the HSRP/VRRP Configuration Error intent misclassifies the misconfiguration as "Single HSRP/VRRP device found" for each of the misconfigured HSRP/VRRP interfaces instead of classifying the misconfiguration as "2 Active Master Interfaces".
[NEW] When two HSRP/VRRP protocol groups are configured with the same matching Virtual IP addresses but have the protocol Group IDs misconfigured, the HSRP/VRRP intent misclassifies that HSRP/VRRP with "2 active interfaces", instead of classifying it as 'Active interface doesn't know Standby'.
[NEW] The Exclude criteria does not work for Console Access Password Protection Intent.
[NEW] When HSRP/VRRP interface on the Active device goes down or is administratively down, the HSRP/VRRP Configuration Error intent does not raise an alert for the violation.
[NEW] Some of the real-time alerts will not be delivered to your Email or SNMP if you get the "Realtime stream processing has failed" error.
To resolve the error, restart the REST API service on all the Platform nodes.
[New] In Network Map, during Paths search, traffic entering access ports may show both untagged traffic and traffic tagged with the access VLAN of the port. The second class of traffic may be incorrect for some data sources.
[NEW] The enable_all and disable_all properties are ignored in the IPFIX request of the post and put calls for adding and updating the vCenter data source via public API.
[NEW] After you upgrade to version 6.3, you may get "Data collection failed due to an error" or "Invalid Credentials" error message for VMC NSX Manager data source.
Contact VMware Support for the resolution.
When the content of an open alert changes, vRealize Network Insight does not show the new value in the alert details.
In the Network Map, the entity details window of the distributed switches does not show alerts that are originated from intents.
While running the RESTAPI service, no users are found in the configuration store. Due to this, the NSX configurations are not created intermittently.
You cannot see the unprotected flows for the Kubernetes service in the Micro-Segmentation Planning page.
After you upgrade to vRealize Network Insight 6.2, you may find some of the manually created applications show zero members. This problem occurs if the application member VM names contain space.
Workaround: To resolve this issue, see KB 85637.