NSX for vSphere 6.3.1 Release Notes

Document updated 10 April 2017
NSX for vSphere 6.3.1   |   Released 28 February 2017  |   Build 5124716

What's in the Release Notes

The release notes cover the following topics:

What's New in 6.3.1

NSX for vSphere 6.3.1 is a bug-fix release addressing specific customer bugs. See Resolved in 6.3.1 for more information.

What's New in 6.3.0(Click to expand or collapse)

Versions, System Requirements, and Installation

Note:

  • This information is current as of the publication date of this document.

  • For the minimum recommended versions of NSX, refer to VMware knowledge base article 2144295. VMware advises running at least the minimum recommended releases. These minimums are general and should not replace or override environment-specific recommendations.

  • For the minimum supported version of NSX and other VMware products, see the VMware Product Interoperability Matrix. VMware declares minimum supported versions based on internal testing.

  • The latest NSX version contains enhancements not included in the minimum recommended version.

The table below lists minimum recommended and supported versions of vSphere that are compatible with NSX.

NSX for vSphere

Minimum Supported vSphere Versions

Minimum Recommended vSphere Versions

Latest NSX Version 6.3.1
  • vSphere 5.5.0.

    Note: vSphere 5.5.0 does not support Cross-vCenter NSX.

  • vSphere 6.0.0
  • vSphere 6.5a
  • vSphere 5.5U3 and later
  • vSphere 6.0U2 and later
  • vSphere 6.5a and later. The earlier 6.5.0 version is not supported.



The table below lists the minimum supported and minimum recommended versions of NSX components.


NSX for vSphere

Guest Introspection for Windows

Guest Introspection for Linux

vRealize Orchestrator

Latest NSX Version

6.3.1 All versions of VMware Tools (VMTools) are supported. Some Guest Introspection-based features require newer VMTools versions:
  • Use VMware Tools 10.0.9 and 10.0.12 to enable the optional Thin Agent Network Introspection Driver component packaged with VMware Tools.
  • Upgrade to VMware Tools 10.0.8 and later to resolve slow VMs after upgrading VMware Tools in NSX / vCloud Networking and Security (see VMware knowledge base article 2144236).
  • Use VMware Tools 10.1.0 and later for Windows 10 support.

This NSX version supports the following Linux versions:
  • RHEL 7 GA (64 bit)
  • SLES 12 GA (64 bit)
  • Ubuntu 14.04 LTS (64 bit)
NSX-vRO plugin 1.1.0.

Note: VMware currently does not support NSX for vSphere 6.3.x with vRealize Networking Insight 3.2.

System Requirements and Installation

For the complete list of NSX installation prerequisites, see the System Requirements for NSX section in the NSX Installation Guide.

For installation instructions, see the NSX Installation Guide or the NSX Cross-vCenter Installation Guide.

Deprecated and Discontinued Functionality

End of Life and End of Support Warnings

For information about NSX and other VMware products that must be upgraded soon, please consult the VMware Lifecycle Product Matrix.

  • NSX for vSphere 6.1.x: End of Availability (EOA) and End of General Support (EOGS) has been reached for NSX for vSphere 6.1.x on January 15, 2017. (See also VMware knowledge base article 2144769.)

  • NSX Data Security removed: As of NSX 6.3.0, the NSX Data Security feature has been removed from the product.

  • NSX Activity Monitoring (SAM) deprecated: As of NSX 6.3.0, Activity Monitoring is no longer a supported feature of NSX. As a replacement, please use Endpoint Monitoring. For more information see Endpoint Monitoring in the NSX Administration Guide.

  • Web Access Terminal removed: Web Access Terminal (WAT) has been removed from NSX 6.3.0. You cannot configure Web Access SSL VPN-Plus and enable the public URL access through NSX Edge. VMware recommends using the full access client with SSL VPN deployments for improved security. If you are using WAT functionality in an earlier release, you must disable it before upgrading to 6.3.0.

  • IS-IS removed from NSX Edge: From NSX 6.3.0, you cannot configure IS-IS Protocol from the Routing tab.

API Removals and Behavior Changes

Deleting firewall configuration or default section:

  • Request to delete firewall section is now rejected if the default section is specified: DELETE /api/4.0/firewall/globalroot-0/config/layer2sections|layer3sections/sectionId
  • New method introduced to get default configuration. Use output of this method to replace entire configuration or any of the default sections:
    • Get default configuration with GET api/4.0/firewall/globalroot-0/defaultconfig
    • Update entire configuration with PUT /api/4.0/firewall/globalroot-0/config
    • Update single section with PUT /4.0/firewall/globalroot-0/config/layer2sections|layer3sections/{sectionId}

defaultOriginate parameter removed from the following methods for logical (distributed) router NSX Edge appliances only:

  • GET/PUT /api/4.0/edges/{edge-id}/routing/config/ospf
  • GET/PUT /api/4.0/edges/{edge-id}/routing/config/bgp
  • GET/PUT /api/4.0/edges/{edge-id}/routing/config

Setting defaultOriginate to true on an NSX 6.3.0 or later logical (distributed) router edge appliance will fail.

All IS-IS methods removed from NSX Edge routing.

  • GET/PUT/DELETE /4.0/edges/{edge-id}/routing/config/isis
  • GET/PUT /4.0/edges/{edge-id}/routing/config

Upgrade Notes

Note: If you use SFTP for NSX backups, see Backup and Restore for a list of supported security algorithms starting in 6.3.x.

Note: For a list of known issues affecting installation and upgrades see the section, Installation and Upgrade Known Issues.

Upgrade Notes related to NSX and vSphere

  • To upgrade NSX, you must perform a full NSX upgrade including host cluster upgrade (which upgrades the host VIBs). For instructions, see the NSX Upgrade Guide including the Upgrade Host Clusters section.

  • System Requirements: For information on system requirements while installing and upgrading NSX, see the System Requirements for NSX section in NSX documentation.

    In NSX 6.3.0, the NSX Edge appliance disk sizes have changed:

    • Compact, Large, Quad Large: 1 disk 584MB + 1 disk 512MB

    • XLarge: 1 disk 584MB + 1 disk 2GB + 1 disk 256MB

  • Upgrade path from NSX 6.x: The VMware Product Interoperability Matrix provides details about the upgrade paths from VMware NSX. Cross-vCenter NSX upgrade is covered in the NSX Upgrade Guide.

  • Downgrades are not supported:

    • Always capture a backup of NSX Manager before proceeding with an upgrade.

    • Once NSX has been upgraded successfully, NSX cannot be downgraded.

  • To validate that your upgrade to NSX 6.3.x was successful see knowledge base article 2134525.

  • There is no support for upgrades from vCloud Networking and Security to NSX 6.3.0.

  • Upgrading to vSphere 6.5a: When upgrading from vSphere 5.5 or 6.0 to vSphere 6.5a, you must first upgrade to NSX 6.3.0. See Upgrading vSphere in an NSX Environment in the NSX Upgrade Guide.

    Note: NSX 6.2.x is not compatible with vSphere 6.5.

  • Partner services compatibility: If your site uses VMware partner services for Guest Introspection or Network Introspection, you must review the  VMware Compatibility Guide before you upgrade, to verify that your vendor's service is compatible with this release of NSX.
  • If you have a hardware gateway (hardware VTEP) installed in your environment, upgrade to NSX 6.3.0 is blocked. You must contact VMware support to proceed with the upgrade. See VMware Knowledge Base article 2148511 for more information.

  • Reset vSphere web client: After upgrading NSX Manager, you must reset the vSphere web client server as explained in the NSX Upgrade documentation. Until you do this, the Networking and Security tab may fail to appear in the vSphere web client. You also may need to clear your browser cache or history.

  • Stateless environments: NSX upgrades in a stateless host environment use new VIB URLs: In NSX upgrades in a stateless host environment, the new VIBs are pre-added to the Host Image profile during the NSX upgrade process. As a result, NSX on stateless hosts upgrade process follows this sequence:

    1. Manually download the latest NSX VIBs from NSX Manager from a fixed URL.

    2. Add the VIBs to the host image profile.

    Prior to NSX 6.2.0, there was a single URL on NSX Manager from which VIBs for a certain version of the ESX Host could be found. (Meaning the administrator only needed to know a single URL, regardless of NSX version.) In NSX 6.2.0 and later, the new NSX VIBs are available at different URLs. To find the correct VIBs, you must perform the following steps:

    • Find the new VIB URL from https://<NSX-Manager-IP>/bin/vdn/nwfabric.properties.
    • Fetch VIBs of required ESX host version from corresponding URL.
    • Add them to host image profile.
  • Rebootless upgrade and uninstall on hosts: On vSphere 6.0 and later, once you have upgraded to NSX 6.3.0, any subsequent NSX VIB changes will not require a reboot. Instead hosts must enter maintenance mode to complete the VIB change.

    A host reboot is not required during the following tasks:

    • NSX 6.3.0 to NSX 6.3.x upgrades on ESXi 6.0 or later.
    • The NSX 6.3.x VIB install that is required after upgrading ESXi from 6.0 to 6.5.0a or later.

      Note: The ESXi upgrade still requires a host reboot.

    • NSX 6.3.x VIB uninstall on ESXi 6.0 or later.

    A host reboot is required during the following tasks:

    • NSX 6.2.x or earlier to NSX 6.3.x upgrades (any ESXi version).
    • NSX 6.3.0 to NSX 6.3.x upgrades on ESXi 5.5.
    • The NSX 6.3.x VIB install that is required after upgrading ESXi from 5.5 to 6.0 or later.
    • NSX 6.3.x VIB uninstall on ESXi 5.5.

Upgrade Notes related to NSX Components

Upgrade Notes related to FIPS

Known Issues

Known issues are grouped as follows:

General Known Issues

Issue 1740625, 1749975: UI problems on Mac OS in Firefox and Safari
If you are using Firefox or Safari in Mac OS, the Back navigation button will not work in NSX Edge from the Networking and Security page in the vSphere 6.5 Web Client, and sometimes the UI freezes in Firefox.

Workaround: Use Google Chrome on Mac OS or click on the Home button then proceed as required.

Issue 1700980: For security patch CVE-2016-2775, a query name which is too long can cause a segmentation fault in lwresd

NSX 6.2.4 has BIND 9.10.4 installed with the product, but it does not use lwres option in named.conf, hence the product is not vulnerable.

Workaround: As the product is not vulnerable, no workaround is required.

Issue 1558285: Deleting cluster with Guest Introspection from vCenter results in null pointer exception
Services such as Guest Introspection must be removed first before a cluster is removed from vCenter

Workaround: Delete the EAM Agency for the service deployment with no associated cluster.

Issue 1629030: The packet capture central CLI (debug packet capture and show packet capture) requires vSphere 5.5U3 or higher
These commands are not supported on earlier vSphere 5.5 releases.

Workaround: VMware advises all NSX customers to run vSphere 5.5U3 or higher.

Issue 1568180: Feature list incorrect for NSX when using vCenter Server Appliance (vCSA) 5.5
You can view the features of a license in the vSphere Web Client by selecting the license and clicking Actions > View Features. If you upgrade to NSX 6.2.3, your license is upgraded to an Enterprise license, which enables all features. However, if NSX Manager is registered with vCenter Server Appliance (vCSA) 5.5, selecting View Features will display the list of features for the license used before the upgrade, not the new Enterprise license.

Workaround: All Enterprise licenses have the same features, even if they are not displayed correctly in the vSphere Web Client. See the NSX Licensing Page for more information.

Installation and Upgrade Known Issues

Before upgrading, please read the section Upgrade Notes, earlier in this document.

Issue 1734245: Data Security causes upgrades to 6.3.0 to fail
Upgrades to 6.3.0 will fail if Data Security is configured as part of a service policy. Ensure you remove Data Security from any service policies before upgrading.

Issue 1801685: Unable to see filters on ESXi after upgrade from 6.2.x to 6.3.0 because of failure to connect to host
After you upgrade from NSX 6.2.x to 6.3.0 and cluster VIBs to 6.3.0 bits, even though the installation status shows successful and Firewall Enabled, the "communication channel health" will show the NSX Manager to Firewall Agent connectivity and NSX Manager to ControlPlane Agent connectivity as down. This will lead to Firewall rules publish, Security Policy publish failures and VXLan configuration not being sent down to hosts.

Workaround: Run the message bus sync API call for the cluster using the API POST https://<NSX-IP>/api/2.0/nwfabric/configure?action=synchronize.
API Body:

<nwFabricFeatureConfig>
 <featureId>com.vmware.vshield.vsm.messagingInfra</featureId>
 <resourceConfig>
   <resourceId>{Cluster-MOID}</resourceId>
 </resourceConfig>
</nwFabricFeatureConfig>

Issue 1791371: When upgrading ESXi hosts to vSphere 6.5a, if Guest Introspection and VXLAN VIBs are upgraded in parallel, an alarm is raised
The Guest Introspection and VXLAN VIBs are different for vSphere 6.5a and when you upgrade these in parallel, the VXLAN VIB upgrade raises an alarm asking for a host reboot.

Workaround: First install the VXLAN VIBs and then the Guest Introspection VIBs when upgrading to vSphere 6.5a.

Issue 1805983: When you upgrade to NSX 6.2.5, 6.2.6 or 6.3.0, Virtual Servers do not work if they do not contain a server pool.
Virtual servers without server pools can only serve HTTP/HTTPS redirection. No other functionality works.

Workaround: Create a dummy pool without any members in it and assign it to the virtual server.

Issue 1797307: NSX Edge may run into split-brain after upgrade or redeploy
On the standby NSX Edge, the show service highavailability CLI command shows high availability status as "Standby" but the config engine status as "Active".

Workaround: Reboot the standby NSX Edge.

Issue 1789989: During a host cluster upgrade, you may experience packet loss in the data plane
During the VIB upgrade, the password file of VSFWD (vShield Firewall Daemon), which is kept in the VIB is removed so VSFWD cannot use the old password to connect to the NSX manager and has to wait until the new password is updated. This process takes some time to complete after host reboot, however, in a fully automated DRS cluster VMs are moved immediately once the prepped host comes up and because the VSFWD process is not ready at that time, there is a chance of packet loss in the data plane for a brief time.

Workaround: Instead of failing back as soon as the host comes back on, delay the failback to the newly prepped host of these VMs.

Issue 1797929: Message bus channel down after host cluster upgrade
After a host cluster upgrade, vCenter 6.0 (and earlier) does not generate the event "reconnect", and as a result, NSX Manager does not set up the messaging infrastructure on the host. This issue has been fixed in vCenter 6.5.

Workaround: Resync the messaging infrastructure as below:
POST https://<ip>:/api/2.0/nwfabric/configure?action=synchronize

    <nwFabricFeatureConfig>
        <featureId>com.vmware.vshield.vsm.messagingInfra</featureId>
        <resourceConfig>
            <resourceId>host-15</resourceId>
        </resourceConfig>
    </nwFabricFeatureConfig>

Issue 1802688: Upgrade from NSX 6.2.x to 6.3.0 does not reflect updated DFW enabled status
After you upgrade NSX from 6.2.x to 6.3.0 and cluster VIBs to 6.3.0 bits, when you add a new host to the upgraded cluster, the firewall status of the concerned host and the cluster keep spinning busy and the status does not get updated, even though the new VIBs have been installed on the new host.

Workaround: Do the following:

  1. Run the Message Bus Sync API call for the host using the API POST:https://<NSX-IP>/api/2.0/nwfabric/configure?action=synchronize. This will bring that host and cluster firewall status to "Disabled".

    API Body:

        <nwFabricFeatureConfig>
         <featureId>com.vmware.vshield.vsm.messagingInfra</featureId>
         <resourceConfig>
           <resourceId>{HOST-ID}</resourceId>
         </resourceConfig>
        </nwFabricFeatureConfig>
    
    
  2. Now Enable Firewall for that cluster from UI Installation > Hostprep page. This should bring all the hosts in that cluster to DFW enabled mode.

Issue 1768144: Old NSX Edge appliance resource reservations that exceed new limits may cause failure during upgrade or redeployment
In NSX 6.2.4 and earlier, you could specify an arbitrarily large resource reservation for an NSX Edge appliance. NSX did not enforce a maximum value.
 After NSX Manager is upgraded to 6.2.5 or later, if an existing Edge has resources reserved (especially memory) that exceed the newly enforced maximum value imposed for the chosen form factor, it would fail during Edge upgrade or redeploy (which would trigger an upgrade). For example, if the user has specified a memory reservation of 1000MB on a pre-6.2.5 LARGE Edge and, after upgrade to 6.2.5, changes the appliance size to COMPACT, the user-specified memory reservation will exceed the newly enforced maximum value, in this case 512 for a COMPACT Edge, and the operation will fail.
See Upgrading Edge Service Gateway (ESG) for information on recommended resource allocation starting in NSX 6.2.5.

Workaround: Use the appliance REST API: PUT https://<NSXManager>/api/4.0/edges/<edge-Id>/appliances/ to reconfigure the memory reservation to be within values specified for the form factor, without any other appliance changes. You can change the appliance size after this operation completes.

Issue 1685894: VMs migrated (with DRS) from hosts with installed newer release VIBs to hosts with older release VIBs lose network connectivity
This scenario is not supported as NSX does not support downgrades.

  • With a DRS-enabled cluster, change DRS mode to Manual during the upgrade until all hosts in the cluster are upgraded to the newer NSX version.

  • On a non-DRS-enabled cluster, do not migrate VMs created or powered off/on from a host with newer VIB version to a host with older VIB version.

Issue 1600281: USVM Installation Status for Guest Introspection shows as Failed in the Service Deployments tab

If the backing datastore for the Guest Introspection Universal SVM goes offline or becomes inaccessible, the USVM may need to be rebooted or re-deployed to recover.

Workaround: Reboot or re-deploy USVM to recover.

Issue 1660373: vCenter enforces expired NSX license

As of vSphere 5.5 update 3 or vSphere 6.0.x vSphere Distributed Switch is included in the NSX license. However, vCenter does not allow ESX hosts to be added to a vSphere Distributed Switch if the NSX license is expired.

Workaround: Your NSX license must be active in order to add a host to a vSphere Distributed Switch.​

Issue 1569010/1645525: When upgrading from 6.1.x to NSX for vSphere 6.2.3 on a system connected to vCenter 5.5, the Product field in the "Assign License Key" window displays the NSX license as a generic value of "NSX for vSphere" and not a more specific version such as "NSX for vSphere - Enterprise."

Workaround: None.

Issue 1465249: Installation status for Guest Introspection shows Succeeded even though the host is offline
After installing Guest Introspection on the cluster that has one host offline, the host that is offline shows Installation Status as Succeeded and Status Unknown.

Workaround: None.

Issue 1636916: In a vCloud Air environment, when the NSX Edge version is upgraded from vCNS 5.5.x to NSX 6.x, Edge firewall rules with a source protocol value of "any" are changed to "tcp:any, udp:any"
As a result, ICMP traffic is blocked, and packet drops may be seen.

Workaround: Before upgrading your NSX Edge version, create more specific Edge firewall rules and replace "any" with specific source port values.

Issue 1660355: VMs which are migrated from 6.1.5 to 6.2.3 and later will not have support for TFTP ALG
Even though the host is enabled, VMs which are migrated from 6.1.5 to 6.2.3 and later will not have support for TFTP ALG.

Workaround: Add and remove the VM from the exclusion list or restart the VM, so that new 6.2.3 (and later) filter gets created which will have support for TFTP ALG.

Issue 1474238: After vCenter upgrade, vCenter might lose connectivity with NSX
If you are using vCenter embedded SSO and you are upgrading vCenter 5.5 to vCenter 6.0, vCenter might lose connectivity with NSX. This happens if vCenter 5.5 was registered with NSX using the root user name. In NSX 6.2, vCenter registration with root is deprecated.
Note: If you are using external SSO, no change is necessary. You can retain the same user name, for example admin@mybusiness.mydomain, and vCenter connectivity will not be lost.

Workaround: Reregister vCenter with NSX using the admininstrator@vsphere.local user name instead of root.

Issue 1332563: Shutdown Guest OS for agent VMs (SVA) before powering OFF
When a host is put into maintenance mode, all service appliances are powered-off, instead of shutting down gracefully. This may lead to errors within third-party appliances.

Workaround: None.

Issue 1473537: Unable to power on the Service appliance that was deployed using the Service Deployments view

Workaround: Before you proceed, verify the following:

  • The deployment of the virtual machine is complete.

  • No tasks such as cloning, reconfiguring, and so on are in progress for the virtual machine displayed in vCenter task pane.

  • In the vCenter events pane of the virtual machine, the following events are displayed after the deployment is initiated:
     
    Agent VM <vm name> has been provisioned.
    Mark agent as available to proceed agent workflow.
     

    In such a case, delete the service virtual machine. In service deployment UI, the deployment is seen as Failed. Upon clicking the Red icon, an alarm for an unavailable Agent VM is displayed for the host. When you resolve the alarm, the virtual machine is redeployed and powered on.

If not all clusters in your environment are prepared, the Upgrade message for Distributed Firewall does not appear on the Host Preparation tab of Installation page
When you prepare clusters for network virtualization, distributed firewall is enabled on those clusters. If not all clusters in your environment are prepared, the upgrade message for Distributed Firewall does not appear on the Host Preparation tab.

Workaround: Use the following REST call to upgrade Distributed Firewall:
PUT https://<nsxmgr-ip>/api/4.0/firewall/globalroot-0/state/<nsxmgr-ip>

Issue 1215460: If a service group is modified after the upgrade to add or remove services, these changes are not reflected in the firewall table
User created service groups are expanded in the Edge Firewall table during upgrade - i.e., the Service column in the firewall table displays all services within the service group. If the service group is modified after the upgrade to add or remove services, these changes are not reflected in the firewall table.

Workaround: Create a new service group with a different name and then consume this service group in the firewall rule.

Issue 1088913: vSphere Distributed Switch MTU does not get updated
If you specify an MTU value lower than the MTU of the vSphere distributed switch when preparing a cluster, the vSphere Distributed Switch does not get updated to this value. This is to ensure that existing traffic with the higher frame size isn't unintentionally dropped.

Workaround: Ensure that the MTU you specify when preparing the cluster is higher than or matches the current MTU of the vSphere distributed switch. The minimum required MTU for VXLAN is 1550.

Issue 1413125: SSO cannot be reconfigured after upgrade
When the SSO server configured on NSX Manager is the one native on vCenter server, you cannot reconfigure SSO settings on NSX Manager after vCenter Server is upgraded to version 6.0 and NSX Manager is upgraded to version 6.x.

Workaround: None.

Issue 1266433: SSL VPN does not send upgrade notification to remote client
SSL VPN gateway does not send an upgrade notification to users. The administrator has to manually communicate that the SSL VPN gateway (server) is updated to remote users and they must update their clients.

Workaround: Users need to uninstall the older version of client and install the latest version manually.

Issue 1402307: If vCenter is rebooted during NSX vSphere upgrade process, incorrect Cluster Status is displayed
When you do host prep in an environment with multiple NSX prepared clusters during an upgrade and the vCenter Server gets rebooted after at least one cluster has been prepared, the other clusters may show Cluster Status as Not Ready instead of showing an Update link. The hosts in vCenter may also show Reboot Required.

Workaround: Do not reboot vCenter during host preparation.

Issue 1498376: Host error message appears while configuring distributed firewall
While configuring distributed firewall, if you encounter an error message related to the host, check the status of fabric feature "ttcom.vmware.vshield.nsxmgr.messagingInfra". If the status is red, perform the following workaround.

Workaround: Use the following REST API call to reset communication between NSX Manager and a single host or all hosts in a cluster.

POST https://<NSX Manager IP>/api/2.0/nwfabric/configure?action=synchronize

<nwFabricFeatureConfig>
    <featureId>com.vmware.vshield.vsm.messagingInfra</featureId>
    <resourceConfig>
        <resourceId>{HOST/CLUSTER MOID}</resourceId>
    </resourceConfig>
</nwFabricFeatureConfig>

Issue 1474066: The NSX REST API call to enable or disable IP detection seems to have no effect
If host cluster preparation is not yet complete, the NSX REST API call to enable or disable IP detection (https://<nsxmgr-ip>/api/2.0/xvs/networks/universalwire-5/features) has no effect.

Workaround: Before issuing this API call, make sure the host cluster preparation is complete.

Issue 1459032: Error configuring VXLAN gateway
When configuring VXLAN using a static IP pool (at Networking& Security>Installation> Host Preparation>Configure VXLAN) and the configuration fails to set an IP pool gateway IP on the VTEP(because the gateway is not properly configured or is not reachable), the VXLAN configuration status enters the Error (RED) state at for the host cluster.

The error message is VXLAN Gateway cannot be set on host and the error status is VXLAN_GATEWAY_SETUP_FAILURE. In the REST API call, GET https://<nsxmgr-ip>/api/2.0/nwfabric/status?resource=<cluster-moid>, the status of VXLAN is as follows:

<nwFabricFeatureStatus>
  <featureId>com.vmware.vshield.nsxmgr.vxlan</featureId>
  <featureVersion>5.5</featureVersion>
  <updateAvailable>false</updateAvailable>
  <status>RED</status>
  <message>VXLAN Gateway cannot be set on host</message>
  <installed>true</installed>
  <enabled>true</enabled>
  <errorStatus>VXLAN_GATEWAY_SETUP_FAILURE</errorStatus>
</nwFabricFeatureStatus>

Workaround: To fix the error, there are two options.

  • Option 1: Remove VXLAN configuration for the host cluster, fix the underlying gateway setup in the IP pool by making sure the gateway is properly configured and reachable, and then reconfigure VXLAN for the host cluster.

  • Option 2: Perform the following steps.

    1. Fix the underlying gateway setup in the IP pool by making sure the gateway is properly configured and reachable.

    2. Put the host (or hosts) into maintenance mode to ensure no VM traffic is active on the host.

    3. Delete the VXLAN VTEPs from the host.

    4. Take the host out of maintenance mode. Taking hosts out of maintenance mode triggers the VXLAN VTEP creation process on NSX Manager. NSX Manager will try to re-create the required VTEPs on the host.

Issue 1463767: In a cross vCenter deployment, a universal firewall configuration section might be under (subordinate to) a local configuration section
If you move a secondary NSX Manager to the standalone (transit) state and then change it back to the secondary state, any local configuration changes that you made while it was temporarily in the standalone state might be listed above the replicated universal configuration sections inherited from the primary NSX Manager. This produces the error condition universal section has to be on top of all other sections on secondary NSX Managers.

Workaround: Use the UI option to move sections up or down so that the local section is below the universal section.

Issue 1462319: The esx-dvfilter-switch-security VIB is no longer present in the output of the "esxcli software vib list | grep esx" command.
Starting in NSX 6.2, the esx-dvfilter-switch-security modules are included within the esx-vxlan VIB. The only NSX VIBs installed for 6.2 are esx-vsip and esx-vxlan. During an NSX upgrade to 6.2, the old esx-dvfilter-switch-security VIB gets removed from the ESXi hosts.
Starting in NSX 6.2.3, a third VIB, esx-vdpi, is provided along with the esx-vsip and esx-vxlan NSX VIBs. A successful installation will show all 3 VIBs.

Workaround: None.

Issue 1481083: After the upgrade, logical routers with explicit failover teaming configured might fail to forward packets properly
When the hosts are running ESXi 5.5, the explicit failover NSX 6.2 teaming policy does not support multiple active uplinks on distributed logical routers.

Workaround: Alter the explicit failover teaming policy so that there is only one active uplink and the other uplinks are in standby mode.

Issue 1485862: Uninstalling NSX from a host cluster sometimes results in an error condition
When using the Uninstall action on the Installation: Host Preparation tab, an error might occur with the eam.issue.OrphanedAgency message appearing in the EAM logs for the hosts. After using the Resolve action and rebooting the hosts, the error state continues even though the NSX VIBs are successfully uninstalled.

Workaround: Delete the orphaned agency from the vSphere ESX Agent Manager (Administration: vCenter Server Extensions: vSphere ESX Agent Manager).

Issue 1411275: vSphere Web Client does not display Networking and Security tab after backup and restore in NSX vSphere 6.2
When you perform a backup and restore operation after upgrading to NSX vSphere 6.2, the vSphere Web Client does not display the Networking and Security tab.

Workaround: When an NSX Manager backup is restored, you are logged out of the Appliance Manager. Wait a few minutes before logging in to the vSphere Web Client.

Issue 1493777: After upgrade to NSX 6.2, NSX Manager has more than 100 percentage of physical memory allocated
Starting in NSX 6.2, NSX Manager requires 16 GB of reserved memory. The former requirement was 12 GB.

Workaround: Increase the NSX Manager virtual appliance's reserved memory to 16 GB.

Issue 1716619: vNIC modification of NSX 5.x.x Edges fails on NSX 6.x.x Manager due to missing feature 'systemControl'
Configuring vNICs for NSX 5.x.x on NSX 6.x.x fails because there is no 'systemControl' entry for Edges created on vCNS (vCloud Networking and Security) manager. SystemControl feature was introduced in 6.1.5 and is not available on vCNS or vShield 5.5.x Manager. This issue is seen when editing interface configuration for older Edge appliances (vCNS or vShield 5.5.x) using NSX 6.1.5 onwards or NSX 6.2.x manager.

Workaround: Contact VMware customer support.

Service virtual machine deployed using the Service Deployments tab on the Installation page does not get powered on

Workaround: Follow the steps below.

  1. Manually remove the service virtual machine from the ESX Agents resource pool in the cluster.
  2. Click Networking and Security and then click Installation.
  3. Click the Service Deployments tab.
  4. Select the appropriate service and click the Resolve icon.
    The service virtual machine is redeployed.

Issue 1764460: After completing Host Preparation, all cluster members appear in ready state, but cluster level erroneously appears as "Invalid"
After you complete Host Preparation, all cluster members correctly appear in "Ready" state, but cluster level appears as "Invalid" and the reason displayed is that you need a host reboot, even though the host has already been rebooted.

Workaround: Click on the red warning icon and select Resolve.

NSX Manager Known Issues

Issue 1770436: Alerts generated even when duplicate IP is not present
Sometimed the arping command reports that the NSX Manager IP address is duplicated in the network even though that is not the case. This generates a false positive event.

Workaround: Contact VMware customer support.

Issue 1772911: NSX Manager performing very slowly with disk space consumption, and task and job table sizes increasing with close to 100% CPU usage
You will experience the following:

  • NSX Manager CPU is at 100% or is regularly spiking to 100% consumption and adding extra resources to NSX Manager appliance does not make a difference.
  • Running the show process monitor command in the NSX Manager Command Line Interface (CLI) displays the Java process that is consuming the highest CPU cycles.
  • Running the show filesystems command on the NSX Manager CLI shows the /common directory as having a very high percentage in use, such as > 90%.
  • Some of the configuration changes time out (sometimes taking over 50 minutes) and are not effective.

See VMware Knowledge Base article 2147907 for more information.

Workaround: Contact VMware customer support for a resolution of this problem.

Issue 1785142: Delay in showing 'Synchronization Issues' on primary NSX manager when communication between Primary and Secondary NSX manager is blocked.
When communication between Primary and Secondary NSX Manager is blocked, you will not immediately see 'Synchronization Issues' on the primary NSX Manager.

Workaround: Wait for about 20 minutes for communication to be reestablished.

Issue 1786066: In a cross-vCenter installation of NSX, disconnecting a secondary NSX Manager may render that NSX Manager unable to reconnect as secondary
In a cross-vCenter installation of NSX, if you disconnect a secondary NSX Manager, you may be unable to re-add that NSX Manager later as a secondary NSX Manager. Attempts to reconnect the NSX Manager as secondary will result in the NSX Manager being listed as "Secondary" in the Management tab of the vSphere Web Client, but the connection to the primary is not established.

Workaround: Do the following:

  1. Disconnect the secondary NSX Manager from the primary NSX Manager.
  2. Add the secondary NSX Manager again to the primary NSX Manager.

Issue 1713669: NSX Manager fails due to full disk when database table ai_useripmap grows too large
This issue causes the NSX Manager appliance disk to become full, resulting in the failure of the NSX Manager. The postgres process cannot be started after a reboot. The "/common" partition is full. This occurs most commonly in sites that place a heavy load on the Event Log Server (ELS) and in sites with a large amount of Guest Introspection (GI) traffic. Sites that use Identity Firewall (IDFW) are frequently affected. See VMware Knowledge Base article 2148341 for more information.

Workaround: Contact VMware customer support for help in recovering from this issue.

Issue 1787542: Exceptions in secondary NSX manager(s) log after DB restore on primary NSX manager
After restoring DB on primary, reinstated Universal DFW sections not seen on secondary NSX Manager(s).

Workaround: None. Reboot the secondary NSX manager to recover.

Issue 1715354: Delay in availability of the REST API
The NSX Manager API takes some time to be up and running after NSX Manager restarts when FIPS mode is toggled. It may appear as if the API is hung, but this occurs because it takes time for the controllers to re-establish connection with the NSX Manager. You are advised to wait for the NSX API server to be up and running and ensure all controllers are in the connected state before doing any operations.

Issue 1441874: Upgrading a single NSX Manager in a vCenter Linked Mode Environment displays an error message
In an environment with multiple VMware vCenter Servers with multiple NSX managers, when selecting one or more NSX Managers from the vSphere Web Client > Networking and Security > Installation > Host Preparation, you see this error:
Could not establish communication with NSX Manager. Please contact administrator.

Workaround: See VMware Knowledge Base article 2127061 for more information.

Issue 1696750: Assigning an IPv6 address to NSX Manager via PUT API requires a reboot to take effect
Changing the configured network settings for NSX Manager via https://{NSX Manager IP address}/api/1.0/appliance-management/system/network requires a system reboot to take effect. Until the reboot, pre-existing settings will be shown.

Workaround: None.

Issue 1486403: NSX Manager does not accept DNS search strings with a space delimiter
NSX Manager does not accept DNS search strings with a space delimiter. You may only use a comma as a delimiter. For example, if the DHCP server advertises eng.sample.com and sample.com for the DNS search list, NSX Manager is configured with eng.sample.com sample.com.

Workaround: Use comma separators. NSX Manager only accepts comma separator as DNS search strings.

Issue 1529178: Uploading a server certificate which does not include a common name returns an "internal server error" message

If you upload a server certificate that does not have any common name, an "internal server error" message appears.

Workaround: Use a server certificate which has both a SubAltName and a common name, or at least a common name.

Issue 1655388: NSX Manager 6.2.3 UI displays English language instead of local language when using IE11/Edge browser on Windows 10 OS for JA, CN, and DE languages

When you launch NSX Manager 6.2.3 with IE11/Edge browser on Windows 10 OS for JA, CN, and DE languages, English language is displayed.

Workaround:

Perform the following steps:

  1. Launch the Microsoft Registry Editor (regedit.exe), and go to Computer > HKEY_CURRENT_USER > SOFTWARE > Microsoft > Internet Explorer > International.
  2. Modify the value of AcceptLanguage file to native language. For example, If you want to change language to DE, change value and make the DE show the first position.
  3. Restart the browser, and log in to the NSX Manager again. Appropriate language is displayed.

Issue 1446649/1445281: Change in Secondary NSX Manager IP / Thumbprint results into Replication errors of Universal objects in a Cross-vCenter setup

If there is any change in the Secondary NSX Manager IP / Thumbprint, it would result into Replication errors of Universal objects in a Cross-vCenter setup as the Primary NSX Manager would not be aware of the latest IP/Thumbprint of the Secondary NSX Manager.

Workaround: If you click the Universal sync status of a Universal object and see exception like "Peer not authenticated;nested exception is javax.net.ssl.SSLPeerUniverifiedException", you can realize that the IP/Thumbprint has been changed.

Issue 1435996: Log files exported as CSV from NSX Manager are timestamped with epoch not datetime
Log files exported as CSV from NSX Manager using the vSphere Web Client are timestamped with the epoch time in milliseconds, instead of with the appropriate time based on the time zone.

Workaround: None.

Issue 1644297: Add/delete operation for any DFW section on the primary NSX creates two DFW saved configurations on the secondary NSX
In a cross-vCenter setup, when an additional universal or local DFW section is added to the primary NSX Manager, two DFW configurations are saved on the secondary NSX Manager. While it does not affect any functionality, this issue will cause the saved configurations limit to be reached more quickly, possibly overwriting critical configurations.

Workaround: None.

Issue 1534877: NSX management service doesn't come up when the hostname's length is more than 64 characters
Certificate creation via OpenSSL library requires a hostname less than or equal to 64 characters.

Issue 1537258: NSX Manager list slow to display in Web Client
In vSphere 6.0 environments with multiple NSX Managers, the vSphere web client may take up to two minutes to display the list of NSX Managers when the logged-in user is being validated with a large AD Group set. You may see a data service timeout error when attempting to display the NSX Manager list. There is no workaround. You must wait for the list to load/relogin to see the NSX Manager list.

Issue 1534622: NSX controller shows as disconnected
NSX Manager logs report disconnection to controllers via a message similar to "ERROR http-nio-127.0.0.1-7441-exec-16908 BaseRestController:339 - Exception : 'I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out'". This condition occurs when an intermediate firewall on the network blocks the TCP/IP FIN message after the idle timeout value is reached. When this condition is occurring, the number of connections to the NSX Manager will increase.

Issue 1534606: Host Preparation Page fails to load
When running vCenter in linked mode, each vCenter must be connected to an NSX Manager on the same NSX version. If the NSX versions differ, the vSphere Web Client will only be able to communicate with the NSX Manager running the higher version of NSX. An error similar to "Could not establish communication with NSX Manager. Please contact administrator," will be displayed on the Host Preparation tab.

Workaround: All NSX managers should be upgraded to the same NSX software version.

Issue 1386874: Networking and Security Tab not displayed in vSphere Web Client
After vSphere is upgraded to 6.0, you cannot see the Networking and Security Tab when you log in to the vSphere Web Client with the root user name.

Workaround: Log in as administrator@vsphere.local or as any other vCenter user which existed on vCenter Server before the upgrade and whose role was defined in NSX Manager.

Issue 1415480: After NSX Manager backup is restored, REST call shows status of fabric feature com.vmware.vshield.nsxmgr.messagingInfra as Red
When you restore the backup of an NSX Manager and check the status of fabric feature com.vmware.vshield.nsxmgr.messagingInfra using a REST API call, it is displayed as Red instead of Green.

Workaround: Use the following REST API call to reset communication between NSX Manager and a single host or all hosts in a cluster.
POST https://<nsxmgr-ip>/api/2.0/nwfabric/configure? action=synchronize
<nwFabricFeatureConfig>
<featureId>com.vmware.vshield.nsxmgr.messagingInfra</featureId>
<resourceConfig&gt
    <resourceId>HOST/CLUSTER MOID</resourceId>
</resourceConfig>
</nwFabricFeatureConfig>

Issue 1027066: vMotion of NSX Manager may display the error message, "Virtual ethernet card Network adapter 1 is not supported"
You can ignore this error. Networking will work correctly after vMotion.

Issue 1406471: Syslog shows host name of backed up NSX Manager on the restored NSX Manager
If a second NSX Manager is installed with the same IP address and a unique hostname as the first NSX Manager, restoring the configuration will show the first NSX Manager’s hostname after a restore and the second NSX Manager’s hostname after reboot.

Workaround: Host name of second NSX Manager should be configured to be same as the backed up NSX Manager.

Issue 1477041: NSX Manager virtual appliance summary page shows no DNS name
When you log in to the NSX Manager virtual appliance, the Summary page has a field for the DNS name. This field remains blank even though a DNS name has been defined for the NSX Manager appliance.

Workaround: You can view the NSX Manager's hostname and the search domains on the Manage: Network page.

Issue 1492880: NSX Manager UI do not automatically log out after changing password using NSX Command Line Interface
If you are logged in to NSX Manager and recently changed your password using CLI, you might continue to stay logged in to the NSX Manager UI using your old password. Typically, NSX Manager client should automatically log you out if the session times out for being inactive.

Workaround: Log out from the NSX Manager UI and log back in with your new password.

Issue 1468613: Unable to edit a network host name
After you login to NSX Manager virtual appliance and navigate to the Appliance Management, click Manage Appliance Settings, and click Network under Settings to edit the network host name, you might receive an invalid domain name list error. This happens when the domain names specified in the Search Domains field are separated with whitespace characters, instead of commas. NSX Manager only accepts domain names that are comma separated.
Workaround: Perform the following steps:

  1. Log in to the NSX Manager virtual appliance.

  2. Under Appliance Management, click Manage Appliance Settings.

  3. From the Settings panel, click Network.

  4. Click Edit next to DNS Servers.

  5. In the Search Domains field, replace all whitespace characters with commas.

  6. Click OK to save the changes.

Issue 1436953: False system event is generated even after successfully restoring NSX Manager from a backup
After successfully restoring NSX Manager from a backup, the following system events appear in the vSphere Web Client when you navigate to Networking & Security: NSX Managers: Monitor: System Events.

  • Restore of NSX Manager from backup failed (with Severity=Critical).

  • Restore of NSX Manager successfully completed (with Severity=Informational).

Workaround: If the final system event message shows as successful, you can ignore the system generated event messages.

Issue 1489768: Change in behavior of NSX REST API call to add a namespace in a datacenter
In NSX 6.2, the POST https://<nsxmgr-ip>/api/2.0/namespace/datacenter/ REST API call returns a URL with an absolute path, for example http://198.51.100.3/api/2.0/namespace/api/2.0/namespace/datacenter/datacenter-1628/2. In previous releases of NSX, this API call returned a URL with a relative path, for example: /api/2.0/namespace/datacenter/datacenter-1628/2.

Workaround: None.

Logical Networking Known Issues and NSX Edge Known Issues

Issue 1791264: Double clicking on a Transport Zone fails to enable/disable CDO mode.
If you try to enable or disable CDO mode from the Summary page that you reach after double-clicking a Transport Zone from the vSphere web client, there is no effect.

Workaround: Do the following:

  1. Go back to the Transport Zone listing page: Installation > Logical Network Preparation > Transport Zones and select the desired Transport Zone.
  2. Select Enable CDO mode/Disable CDO mode from the Actions dropdown menu.
  3. The selected action will take effect.

Issue 1773500: Invalid route (0.0.0.0/32) causes NSX to crash
If you push the route 0.0.0.0/32 on the NSX DLR, it does not support this route and rejects it. However, this still causes a crash (PSOD) when the associated LIF is deleted and re-added with an IP address on the same subnet.

Workaround: 0.0.0.0/32 is not a valid route. Do not configure it, or use routemap to reject it.

Issue 1769941: L2VPN bridge table "poisoned" by DLR PMAC with duplicate ARP reply
The L2VPN server vxlan trunk port on the host does not drop the ARP reply coming from the client virtual machine with destination MAC as pMAC, which causes the MAC table on bridge getting poisoned resulting in traffic drop.

Workaround: To work around this issue, add a traffic filter for the VXLAN trunk dvport to drop the ARP reply destined to pMAC.

To add a traffic qualifier:

  1. Go to the dvport where the NSX Edge is connected.
  2. Navigate to Edit settings > Traffic Filtering and Marking.
  3. Add a MAC qualifier with destination set to pMAC.

Issue 1764258: Traffic blackholed for upto eight minutes post HA failover or Force-Sync on NSX Edge configured with sub-interface
If an HA failover is triggered or you start a Force-Sync over a sub-interface, traffic is blackholed for upto eight minutes.

Workaround: Do not use subinterfaces for HA.

Issue 1771760: SNMP response packets containing OID type Counter64 will get dropped by NSX Edge when NAT is enabled.
SNMP ALG in NSX Edge is unable to process Counter64 types from SNMP response packet, and the packet will get dropped. As a result, the client does not get a response for the request.

Workaround: Contact VMware customer support if you encounter this problem.

Issue 1767135: Errors when trying to access certificates and application profiles under Load Balancer
Users with Security Admin privileges and Edge scope are unable to access certificates and application profiles under Load Balancer. The vSphere Web Client shows error messages.

Workaround: None.

Issue 1792548: NSX Controller may get stuck at the message: 'Waiting to join cluster'
NSX Controller may get stuck at the message: 'Waiting to join cluster' (CLI command:show control-cluster status). This occurs because the same IP address has been configured for eth0 and breth0 interfaces of the controller while the controller is coming up. You can verify this by using the following CLI command on the controller: show network interface

Workaround: Contact VMware customer support.

Issue 1747978: OSPF adjacencies are deleted with MD5 authentication after NSX Edge HA failover
In an NSX for vSphere 6.2.4 environment where the NSX Edge is configured for HA with OSPF graceful restart configured and MD5 is used for authentication, OSPF fails to start gracefully. Adjacencies forms only after the dead timer expires on the OSPF neighbor nodes.

Workaround: None

Issue 1803220: Loss of VXLAN connectivity to CDO-enabled hosts when controller to host connection goes down
Controller Disconnected Operation(CDO) feature ensures VXLAN connectivity when the whole Controller cluster is down/unreachable. However, in cases where the Controller cluster is Up, but a host loses connectivity with it, data plane traffic destined to that host from other hosts which are connected with the Controller may still be dropped. When this condition occurs, the host has been removed from the per-VNI VTEP list, and ARPs sent by remote hosts will be dropped. For traffic originating from the host which has lost connectivity with the Controller, CDO feature ensures that it will be able to reach the right destination.

Issue 1804116: Logical Router goes into Bad State on a host that has lost communication with the NSX Manager
If a Logical Router is powered on or redeployed on a host that has lost communication with the NSX Manager (due to NSX VIB upgrade/install failure or host communication issue), the Logical Router will go into Bad State and continuous auto-recovery operation via Force-Sync will fail.

Workaround: After resolving the host and NSX Manager communication issue, reboot the NSX Edge manually and wait for all interfaces to come up. This workaround is only needed for Logical Routers and not NSX Edge Services Gateway (ESG) because the auto-recovery process via force-sync reboots NSX Edge.

Issue 1783065: Cannot configure Load Balancer for UDP port along with TCP by IPv4 and IPv6 address together
UDP only supports ipv4-ipv4, ipv6-ipv6 (frontend-backend). There is a bug in NSX Manager that even IPv6 link local address is read and pushed as an IP address of the grouping object, and you cannot select IP protocol to use in LB configuration.

Here is an example LB configuration demonstrating the issue:
In the Load Balancer configuration, pool "vCloud_Connector" is configured with a grouping object (vm-2681) as pool member and this object contains both IPv4 and IPv6 addresses, which cannot be supported by LB L4 Engine.

  {
              "algorithm" : {
                 ...
              },
              "members" : [
                 {
                    ...  ],
                    ...
                 }
              ],
              "applicationRules" : [],
              "name" : "vCloud_Connector",
              "transparent" : {
                 "enable" : false
              }
        }

  {
              "value" : [
                 "fe80::250:56ff:feb0:d6c9",
                 "10.204.252.220"
              ],
              "id" : "vm-2681"
            }
          

Workaround:

  • Option 1: Enter the IP address of the pool member instead of grouping objects in pool member.
  • Option 2: Do not use IPv6 in the VMs.

Issue 1773127: On setups with a significant number of hosts and logical switches, the screen that displays hosts related to a given logical switch fails to load correctly.
When you select Logical Switch > Related Objects > Hosts from your setup with a significant number of hosts, the vSphere Web Client fails to load after waiting for a couple of minutes and the following error appears: The data service timed out because a back-end task took more than 120 seconds. This occurs because the remote API call to NSX Manager takes too long to return.

Workaround: There are two ways to work around this problem:

  • The first option: You can avoid this issue by increasing the API timeout as described in the VMware Knowledge Base article 2040626. You may need to restart the vSphere Web Client after increasing this timeout. The likely outcome of increasing the timeout is that there will be no error, but you will have to wait for about 2-4 minutes for the page to reload.
  • The second option: If you only want to see the related hosts correctly, you can go to Home > Networking > Port group > Related Objects > Hosts to see the list of hosts associated with the logical switch.

Issue 1777792: Peer Endpoint set as 'ANY' causes IPSec connection to fail
When IPSec configuration on NSX Edge sets remote peer endpoint as 'ANY', the Edge acts as an IPSec "server" and waits for remote peers to initiate connections. However, when the initiator sends a request for authentication using PSK+XAUTH, the Edge displays this error message: "initial Main Mode message received on XXX.XXX.XX.XX:500 but no connection has been authorized with policy=PSK+XAUTH" and IPsec can't be established.

Workaround: Use specific peer endpoint IP address or FQDN in IPSec VPN configuration instead of ANY.

Issue 1770114: Error message at cluster level is not cleared after successful host preparation.
When you assign an IP pool to a cluster that does not have enough IP addresses, and then try to add a host to this cluster, you get the error "Insufficient IP addresses". Even after you change this pool to add additional IP addresses, and you can successfully add hosts to this cluster, the error message remains at the cluster level.

Workaround: Contact VMware customer support.

Issue 1789088: NSX Edge stuck in the grub command line prompt
NSX Edge may fail to boot up and can get stuck at the grub command line prompt.

Workaround:

  • First, investigate:
    1. Check the existing environment with the set command.

    2. Use the ls and cat commands to locate and dump the /boot/grub/grub.cfg file.

    3. grub> ls /boot
      grub> ls /boot/grub
      grub> cat /boot/grub/grub.cfg

    4. Capture the host logs at this time (as close to the problem occurring as possible). There may be some NFS logs that indicate an NFS storage issue.

  • Next, boot the NSX Edge manually. Try the following, in this order (try the next option only if the previous one does not successfully boot the Edge):

    1. Reboot the Edge VM by selecting the Power Reset option in the vSphere Web Client.

    2. OR Specify the grub config file again, which should load up the menu being boot up the Edge immediately.
      Invoke the following command at the grub prompt:
      grub> configfile /boot/grub/grub.cfg

    3. OR Use the following commands at the grub prompt :
      grub> insmod ext2
      grub> set root=(hd0,1)
      grub> linux /boot/vmlinuz loglevel=3 root=/dev/sda1
      grub> boot

Issue 1741158: Creating a new, unconfigured NSX Edge and applying configuration can result in premature Edge service activation.
If you use the NSX API to create a new, unconfigured NSX Edge, then make an API call to disable one of the Edge services on that Edge (for example, set dhcp-enabled to "false"), and finally apply configuration changes to the disabled Edge service, that service will be made active immediately.

Workaround: After you make a configuration change to an Edge service that you wish to keep in disabled state, immediately issue a PUT call to set the enabled flag to "false" for that service.

Issue 1758500: Static route with multiple next-hops does not get installed in NSX Edge routing and forwarding tables if at least one of the next-hop configured is the Edge's vNIC IP address
With ECMP and multiple next-hop addresses, NSX allows the Edge's vNIC's IP address to be configured as next-hop if at least one of the next-hop IP addresses is valid. This is accepted without any errors or warnings but route for the network is removed from the Edge's routing/forwarding table.

Workaround: Do not configure the Edge's own vNIC IP address as a next-hop in static route when using ECMP.

Issue 1716464: NSX Load Balancer will not route to VMs newly tagged with a Security tag.
If we deploy two VMs with a given tag, and then configure an LB to route to that tag, the LB will successfully route to those two VMs. But if we then deploy a third VM with that tag, the LB only routes to the first two VMs.

Workaround: Click "Save" on the LB Pool. This rescans the VMs and will start routing to newly tagged VMs.

Issue 1753621: When Edge with private local AS sends routes to EBGP peers, all the private AS paths are stripped off from the BGP routing updates sent.
NSX currently has a limitation that prevents it from sharing the full AS path with eBGP neighbors when the AS path contains only private AS paths. While this is the desired behavior in most cases, there are cases in which the administrator may want to share private AS paths with an eBGP neighbor.

Workaround: No workaround available to make the Edge announce all the AS paths in the BGP update.

Issue 1733146: Under certain conditions, creating or modifying LIFs for a Universal DLR fails when no control VM exists

This issue is known to manifest under the following conditions:

  • ECMP with two static default routes
  • Static routes with local egress flag
This issue results from a full synchronization being requested instead of a delta update, resulting in the rejection of duplicate entities and a failed operation. A message similar to the following will be seen:
2016-09-22 20:18:58.080 GMT ERROR TaskFrameworkExecutor-24 NvpRestClientManagerImpl:774 - NVP API returns error: [409] Route with the same prefix and priority already exist on router dc5e541a-d7a6-4cb9-8d8a-9334a9c51127

Workaround:

  1. Delete the universal logical router.
  2. Deploy a new universal logical router. Enable local egress and uncheck “Deploy Edge Appliance”. Configure two uplink interfaces and a default gateway IP address via the first uplink using the locale-id on the primary DLR (for example, 1111xxxx).
  3. Do not add a static route of 0.0.0.0/0 with the locale id used on the secondary site (for example, 2222xxxx).
  4. Add the following two static routes with the expected next-hop IP address and locale id of the secondary site (for example, 222xxxx).
  5. Route #1: 0.0.0.0/1
    Route #2: 128.0.0.0/1

Issue 1461421: "show ip bgp neighbor" command output for NSX Edge retains the historical count of previously established connections

The “show ip bgp neighbor” command displays the number of times that the BGP state machine transitioned into the Established state for a given peer. Changing the password used with MD5 authentication causes the peer connection to be destroyed and re-created, which in turn will clear the counters. This issue does not occur with an Edge DLR.

Workaround: To clear the counters, execute the "clear ip bgp neighbor" command.

Issue 1676085: Enabling Edge HA will fail if resource reservation fails

Starting with NSX for vSphere 6.2.3, enabling high availability on an existing Edge will fail when sufficient resources cannot be reserved for the second Edge VM appliance. The configuration will roll back to the last known good configuration. In previous releases, if HA is enabled after Edge deployment and resource reservation fails, the Edge VM still is created.

Workaround: This is an expected change in behavior.

Issue 1656713: IPsec Security Policies (SPs) missing on the NSX Edge after HA failover, traffic cannot flow over tunnel

The Standby > Active switchover will not work for traffic flowing on IPsec tunnels.

Workaround: Disable/Enable IPsec after the NSX Edge switchover.

Issue 1354824: When an Edge VM becomes corrupted or becomes otherwise unreachable due to such reasons as a power failure, system events are raised when the health check from NSX Manager fails

The system events tab will report "Edge Unreachability" events. The NSX Edges list may continue to report a Status of Deployed.

Workaround: Use the https://NSX-Manager-IP-Address/api/4.0/edges/edgeId/status API with detailedStatus=true.

Issue 1556924: L3 connectivity loss with VXLAN would block error

When DLR LIF's are configured on the host but underlying VXLAN layer is not fully prepared, connectivity through some of DLR LIF's may be affected. Some of the VMs belonging to DLR are not reachable. There might be "Failed to Create VXLAN trunk status: Would block" logs in /var/log/vmkernel.log file.

Workaround: You may delete the LIF's and recreate them. Another option is rebooting the affected ESX hosts.

Issue 1647657: Show commands on an ESXi host with DLR (Distributed Logical Router) display no more than 2000 routes per DLR instance

Show commands on an ESXi host with DLR enabled will not show more than 2000 routes per DLR instance, although more than this maximum may be running. This issue is a display issue, and the data path will work as expected for all routes.

Workaround: None.

Issue 1634215: OSPF CLI commands output does not indicate whether routing is disabled

When OSPF is disabled, routing CLI commands output does not show any message saying "OSPF is disabled". The output is empty.

Workaround: The show ip ospf command will display the correct status.

Issue 1647739: Redeploying an Edge VM after a vMotion operation will cause the Edge or DLR VM to be placed back on the original cluster.  

Workaround: To place the Edge VM in a different resource pool or cluster, use the NSX Manager UI to configure the desired location.

Issue 1463856: When NSX Edge Firewall is enabled, existing TCP connections are blocked
TCP connections are blocked through the Edge stateful firewall as the initial three-way handshake cannot be seen.

Workaround: To handle such existing flows, do the following. Use the NSX REST API to enable the flag "tcpPickOngoingConnections" in the firewall global configuration. This switches the firewall from strict mode to lenient mode. Next, enable the firewall. Once existing connections have been picked up (this may take a few minutes after you enable the firewall), set the flag "tcpPickOngoingConnections" back to false to return the firewall to strict mode. (This setting is persistent.)

PUT /api/4.0/edges/{edgeId}/firewall/config/global

    <globalConfig>
        <tcpPickOngoingConnections>true</tcpPickOngoingConnections>
    </globalConfig>

Issue 1374523: Reboot ESXi, or run [services.sh restart] after installation of VXLAN VIB to make the VXLAN commands available using esxcli

After installation of VXLAN VIB, you must reboot ESXi or run the [services.sh restart] command, so that the VXLAN commands becomes available using esxcli.

Workaround: Instead of using esxcli, use localcli.

Issue 1604514: Editing/Configuring default gateway on an unmanaged DLR fails after clicking Publish

When a default gateway is added to an unmanaged DLR, the publish will fail with error "Routing Distance is support only on NSX Edge version 6.2.0 and later with NSX Edge VMs deployed". This is due to the default admin distance "1" populated on the UI.

Workaround: Remove the admin distance "1" which is populated by default.

Issue 1642087: After modifying the securelocaltrafficbyip parameter value in the IPsec VPN Extension, forwarding to destination networks fails

When using an NSX Edge Services Gateway, you experience this symptom:

  • After changing the securelocaltrafficbyip value to 0 in the NSX UI (Edit IPsec VPN screen), forwarding to a remote subnet of the IPsec VPN tunnel no longer works
  • After changing this parameter, you no longer see the correct information for a remote subnet in the IP routing table

Workaround: Disable and re-enable the IPSec VPN service. Then validate that the expected routing information is shown in the CLI and the UI.

Issue 1525003: Restoring an NSX Manager backup with an incorrect passphrase will silently fail as critical root folders cannot be accessed

Workaround: None.

Issue 1637639: When using the Windows 8 SSL VPN PHAT client, the virtual IP is not assigned from the IP pool
On Windows 8, the virtual IP address is not assigned as expected from the IP pool when a new IP address is assigned by the Edge Services Gateway or when the IP pool changes to use a different IP range.

Workaround: This issue occurs only on Windows 8. Use a different Windows OS to avoid experiencing this issue.

Issue 1628220: DFW or NetX observations are not seen on receiver side
Traceflow may not show DFW and NetX observations on receiver side if switch port associated with the destination vNIC changed. It will not be fixed for vSphere 5.5 releases. For vSphere 6.0 and up, there is no such issue.

Workaround: Do not disable vNIC. Reboot VM.

Issue 1534603: IPsec and L2 VPN service status shows as down even when the service is not enabled
Under the Settings tab in the UI, the L2 service status is displayed as down, however the API shows the L2 status as up. L2 VPN and IPsec service always shows as down in the Settings tab unless the UI page is refreshed.

Workaround: Refresh the page.

Issue 1562767: Delays in connecting to NSX load balancer do not provide consistent connections over multiple VIPs
When the load balancer is configured to use Source IP Hash load balancing, a connected client session receives a consistent connection to a backend server. The load balancer should also be able to provide, for a given connected client, consistent connections over multiple VIPs if those VIPs are backed by the same server pool. That is, when one backend server serves multiple VIPs, a given client's connection to one of that backend server's VIPs should guarantee that that client will use the same backend server when connecting to other VIPs served by that backend server. A known issue prevents the NSX load balancer from providing such consistent connections over multiple VIPs.

Issue 1553600: Delays in connecting to RIB and FIB after assigning IP address to interface
When you attempt to assign an IP address to an interface, typically, the interface information is updated immediately. However, when waiting for a polling event, you may observe a delay in seeing the assigned IP address. (The NSX logical router polls periodically to get changes in the interfaces.)

Issue 1534799: Slow convergence when OSPF area border router with highest IP address is shut down
Convergence takes a long time when the NSX-based, OSPF area border router (ABR) with highest IP address is shut down or rebooted. If an ABR that does not have the numerically highest IP address is shut down or rebooted, traffic converges quickly to another path. However, if the ABR with the highest IP address is shut down or rebooted, a multi-minute re-convergence time is seen. The OSPF process can be cleared manually to reduce the convergence time.

Issue 1446327: Some TCP-based applications may time out when connecting through NSX Edge
The default TCP established connection inactivity timeout is 3600 seconds. The NSX Edge deletes any connections idle for more than the inactivity timeout and drops those connections.

Workaround:
  1. If the application has a relatively long inactivity time, enable TCP keepalives on the hosts with keep_alive_interval set to less than 3600 seconds.
  2. Increase the Edge TCP inactivity timeout to greater than 2 hours using the following NSX REST API. For example, to increase the inactivity timeout to 9000 seconds. NSX API URL:
    /api/4.0/edges/{edgeId}/systemcontrol/config PUT Method <systemControl> <property>sysctl.net.netfilter.nf_conntrack_tcp_timeout_established=9000</property> </systemControl>

Issue 1534602: UI does not display Edge management plane mode (VIX/MSGBUS), and does not provide the option to change from VIX to MSGBUS
When an Edge appliance is in VIX mode, it is not eligible to be selected for inclusion in DFW, and centralized CLI commands take much longer to run compared to MSGBUS mode
Workaround: Make sure that the cluster where the Edge is deployed is prepared for NSX and its "NSX Manager to Firewall Agent" is in "Up" state, and redeploy the Edge.

  • Action: DENY
  • Network: ANY
  • Direction: OUT

Workaround: None.

Issue 1089745: Cannot configure OSPF on more than one DLR Edge uplink
Currently it is not possible to configure OSPF on more than one of the eight DLR Edge uplinks. This limitation is a result of the sharing of a single forwarding address per DLR instance.

Workaround: This is a current system limitation and there is no workaround.

Issue 1498965: Edge syslog messages do not reach remote syslog server
Immediately after deployment, the Edge syslog server cannot resolve the hostnames for any configured remote syslog servers.

Workaround: Configure remote syslog servers using their IP address, or use the UI to Force Sync the Edge.

Issue 1494025: Logical router DNS Client configuration settings are not fully applied after updating REST Edge API

Workaround: When you use REST API to configure DNS forwarder (resolver), perform the following steps:

  1. Specify the DNS Client XML server's settings so that they match the DNS forwarder setting.

  2. Enable DNS forwarder, and make sure that the forwarder settings are same as the DNS Client server's settings specified in the XML configuration.

Issue 1243112: Validation and error message not present for invalid next hop in static route, ECMP enabled
When trying to add a static route, with ECMP enabled, if the routing table does not contain a default route and there is an unreachable next hop in the static route configuration, no error message is displayed and the static route is not installed.

Workaround: None.

Issue 1288487: If an NSX Edge virtual machine with one sub interface backed by a logical switch is deleted through the vCenter Web Client user interface, data path may not work for a new virtual machine that connects to the same port
When the Edge virtual machine is deleted through the vCenter Web Client user interface (and not from NSX Manager), the VXLAN trunk configured on dvPort over opaque channel does not get reset. This is because trunk configuration is managed by NSX Manager.

Workaround: Manually delete the VXLAN trunk configuration by following the steps below:

  1. Navigate to the vCenter Managed Object Browser by typing the following in a browser window:
    https://<vc-ip>/mob?vmodl=1
  2. Click Content.
  3. Retrieve the dvsUuid value by following the steps below.
    1. Click the rootFolder link (for example, group-d1(Datacenters)).
    2. Click the data center name link (for example, datacenter-1).
    3. Click the networkFolder link (for example, group-n6).
    4. Click the DVS name link (for example, dvs-1)
    5. Copy the value of uuid.
  4. Click DVSManager and then click updateOpaqueDataEx.
  5. In selectionSet, add the following XML.
    <selectionSet xsi:type="DVPortSelection">
        <dvsUuid>value</dvsUuid>
        <portKey>value</portKey> <!--port number of the DVPG where trunk vnic got connected-->
    </selectionSet>
  6. In opaqueDataSpec, add the following XML
    <opaqueDataSpec>
        <operation>remove</operation>
        <opaqueData>
          <key>com.vmware.net.vxlan.trunkcfg</key>
          <opaqueData></opaqueData>
        </opaqueData>
    </opaqueDataSpec>
  7. Set isRuntime to false.
  8. Click Invoke Method.
  9. Repeat steps 5 through 8 for each trunk port configured on the deleted Edge virtual machine.

Issue 1637939: MD5 certificates are not supported while deploying hardware gateways
While deploying hardware gateway switches as VTEPs for logical L2 VLAN to VXLAN bridging, the physical switches support at minimum SHA1 SSL certificates for OVSDB connection between the NSX controller and OVSDB switch.

Workaround: None.

Issue 1637943: No support for hybrid or multicast replication modes for VNIs that have a hardware gateway binding
Hardware gateway switches when used as VTEPs for L2 VXLAN-to-VLAN bridging support Unicast replication mode only.

Workaround: Use Unicast replication mode only.

Issue 1493611: No connectivity on VLAN ID 0 in L2 VPN
NSX L2 VPN configuration incorrectly allows the user to configure an L2 VPN with VLAN ID 0. Once configured, no traffic can flow on this VPN.

Workaround: Workaround: Use a valid VLAN ID in the range from 1 to 4094.

Security Services Known Issues

Issue 1474650: For NetX users, ESXi 5.5.x and 6.x hosts experience a purple diagnostic screen mentioning ALERT: NMI: 709: NMI IPI received
When a large number of packets are transmitted or received by a service VM, DVFilter continues to dominate the CPU resulting in heartbeat loss and a purple diagnostic screen. See VMware Knowledge Base article 2149704 for more information.

Workaround: Upgrade the ESXi host to any of the following ESXi versions that are the minimum required to use NetX:

  • 5.5 Patch 10
  • ESXi 6.0U3
  • ESXi 6.5

Issue 1676043: VM removed from Exclusion List after two simultaneous additions
Two simultaneous additions of the same VM to the Exclude List by two users without refreshing the UI results in the already added VMs being removed from the excluded list.

Workaround: Refresh the UI before adding the VM to the Exclude List.

Issue 1770259: The appliedTo field for the DFW rule cannot be modified to have multiple appliedTo objects
When you apply the DFW rule to a set of vNICs or VMs, or clusters or datacenter, publish it and later want to modify by adding additional objects to the appliedTo field, the new changes will not be effective even though the publish succeeds.

Workaround: None.

Issue 1798779: After you upgrade NSX from 6.2.x to 6.3.0, the GUI of vSphere Web Client) erroneously allows you to add Universal Security Tag
6.3.0 introduces Universal Security Tags. When you try to add a Universal Security Tag to a Universal Security Group that was created on 6.2.x before the upgrade to NSX 6.3.0, the operation will fail with the error "The requested member is not a valid member". This error is correct because you cannot add a Universal Security Tag to an NSX 6.2.x Universal Security Group. The GUI is misleading.

Workaround: After upgrading, create an NSX 6.3.0 Universal Security Group and add the Universal Security Tags to that group.

Issue 1799543: After upgrading from NSX 6.2.x to NSX 6.3.0, the vSphere Web Client erroneously shows and allows you to select NSX 6.2.x Universal Security Groups and non Active-Standby Universal Security Groups when you are creating the first Active-Standby Universal Security Group.
When you create the very first ActiveStandby Universal Security Group, the vSphere Web Client UI shows and allows you to add a Universal Security Group which was created on NSX 6.2.x. The operation will fail with the error "The requested member is not a valid member".

Workaround: Create at least one Active-Standby Universal Security Group, then while creating the next ActiveStandby Universal Security Group, this problem will not occur.

Issue 1786780: Reordering/moving Policies in the Service Composer UI take a long time with high CPU utilization
The reordering or re-positioning of Policies from the Service Composer UI may take a very long time with high CPU utilization.

Workaround: The following steps are helpful:

  • While creating the Policy, try to give the right precedence (weight) to the Policy, so that it lands at the right position in the first attempt, and you do not need to reorder Policies again.
  • If you must move a Policy to another position, edit the Policy to be moved and change the precedence (weight) to an appropriate value. This will result in the modification of a single Policy and finish quickly.

Issue 1787680: Deleting Universal Firewall Section fails when NSX Manager is in Transit mode
When you try to delete a Universal Firewall Section from the UI of an NSX Manager in Transit mode, and publish, the Publish fails and as a result you are not able to set the NSX Manager to Standalone mode.

Workaround: Use the Single Delete Section REST API to delete the Universal Firewall Section.

Issue 1741844: Using ARP snooping to detect address of vNIC with multiple IP addresses results in 100% CPU consumption
This issue occurs when a virtual machine's vNIC is configured with multiple IP addresses and ARP snooping is enabled for IP detection. The IP discovery module keeps sending vNIC-IP updates to the NSX Manager continuously to change the vNIC-IP mapping for all VMs configured with multiple IP addresses.

Workaround: There is no workaround. Currently the ARP snooping feature supports only one IP address per vNIC. For more information, see the section IP Discovery for Virtual Machines in the NSX Administration Guide.

Issue 1689159: The Add Rule feature in Flow Monitoring does not work correctly for ICMP flows.
When adding a rule from Flow Monitoring, the Services field will remain blank if you do not explicitly set it to ICMP and as a result, you may end up adding a rule with the service type "ANY".

Workaround: Update the Services field to reflect ICMP traffic.

Issue 1632235: During Guest Introspection installation, network drop down list displays "Specified on Host" only
When installing Guest Introspection with the NSX anti-virus-only license and vSphere Essential or Standard license, the network drop down list will display only the existing list of DV port groups. This license does not support DVS creation.

Workaround: Before installing Guest Introspection on a vSphere host with one of these licenses, first specify the network in the "Agent VM Settings" window.

Issue 1652155: Creating or migrating firewall rules using REST APIs may fail under certain conditions and report HTTP 404 error

Adding or migrating firewall rules using REST APIs is not supported under these conditions:

  • Creating firewall rules as a bulk operation when the autosavedraft=true is set.
  • Adding firewall rules in sections concurrently.

Workaround: Set the autoSaveDraft parameter to false in the API call when performing bulk firewall rule creation or migration.

Issue 1509687: URL length supports up to 16000 characters when assigning a single security tag to many VMs at a time in one API call
A single security tag cannot be assigned to a large number of VMs simultaneously with a single API if the URL length is more than 16,000 characters.

Workaround: To optimize performance, tag up to 500 VMs in a single call.

Issue 1662020: Publish operation may fail resulting in an error message "Last publish failed on host host number" on DFW UI in General and Partner Security Services sections

After changing any rule, the UI displays "Last publish failed on host host number". The hosts listed on the UI may not have correct version of firewall rules, resulting in lack of security and/or network disruption.

The problem is usually seen in the following scenarios:

  • After upgrade from older to latest NSXv version.
  • Move a host out of cluster and move it back in.
  • Move a host from one cluster to another.

Workaround: To recover, you must force sync the affected clusters (firewall only).

Issue 1481522: Migrating firewall rule drafts from 6.1.x to 6.2.3 is not supported as the drafts are not compatible between the releases

Workaround: None.

Issue 1628679: With identity-based firewall, the VM for removed users continues to be part of the security group

When a user is removed from a group on the AD server, the VM where the user is logged-in continues to be a part of the security-group. This retains firewall policies at the VM vNIC on the hypervisor, thereby granting the user full access to services.

Workaround: None. This behavior is expected by design.

Issue 1462027: In cross vCenter NSX deployments, multiple versions of saved firewall configurations get replicated to secondary NSX Managers
Universal Sync saves multiple copies of universal configurations on secondary NSX Managers. The list of saved configurations contains multiple drafts created by the synchronizing across NSX Managers with the same name and at the same time or with a time difference of 1 second.

Workaround: Run the API call to delete duplicate drafts.

DELETE : https://<nsxmgr-ip>/api/4.0/firewall/config/drafts/

Find the drafts to be deleted by viewing all drafts:

GET: https://<nsxmgr-ip>/api/4.0/firewall/config/drafts

In the following sample output, drafts 143 and 144 have the same name and were created at the same time and are therefore duplicates. Likewise, drafts 127 and 128 have the same name are off by 1 second and are also duplicates.

<firewallDrafts>
    <firewallDraft id="144" name="AutoSaved_Wednesday, August 5, 2015 11:08:40 PM GMT" timestamp="1438816120917">
        <description>Auto saved configuration</description>
        <preserve>false</preserve>
        <user>replicator-1fd96022-db14-434d-811d-31912b1cb907</user>
        <mode>autosaved</mode>
    </firewallDraft>
    <firewallDraft id="143" name="AutoSaved_Wednesday, August 5, 2015 11:08:40 PM GMT" timestamp="1438816120713">
        <description>Auto saved configuration</description>
        <preserve>false</preserve>
        <user>replicator-1fd96022-db14-434d-811d-31912b1cb907</user>
        <mode>autosaved</mode>
    </firewallDraft>
   <firewallDraft id="128" name="AutoSaved_Wednesday, August 5, 2015 9:08:02 PM GMT" timestamp="1438808882608">
        <description>Auto saved configuration</description>
        <preserve>false</preserve>
        <user>replicator-1fd96022-db14-434d-811d-31912b1cb907</user>
        <mode>autosaved</mode>
    </firewallDraft>
    <firewallDraft id="127" name="AutoSaved_Wednesday, August 5, 2015 9:08:01 PM GMT" timestamp="1438808881750">
        <description>Auto saved configuration</description>
        <preserve>false</preserve>
        <user>replicator-1fd96022-db14-434d-811d-31912b1cb907</user>
        <mode>autosaved</mode>
    </firewallDraft>
</firewallDrafts>

Issue 1449611: When a firewall policy in the Service Composer is out of sync due to a deleted security group, the firewall rule cannot be fixed in the UI

Workaround: In the UI, you can delete the invalid firewall rule and then add it again. Or, in the API, you can fix the firewall rule by deleting the invalid security group. Then synchronize the firewall configuration: Select Service Composer: Security Policies, and for each security policy that has associated firewall rules, click Actions and select Synchronize Firewall Config. To prevent this issue, modify firewall rules so that they do not refer to security groups before deleting the security groups.

Issue 1557880: Layer 2 (L2) rules may be missing if the MAC address of a VM used in the rules is modified
Because L2 rule optimization is ON by default, L2 rules with both source and destination fields specified (other than "any") will be applied to vNICs(or filters) only if the vNIC MAC address matches the source or destination MAC address list. Hosts with VMs not matching the source or destination MAC addresses will not have those L2 rules applied.

Workaround: To have L2 rules applied to all vNICs(or filters), set one of the source or destination fields to "any".

Issue 1505316: NSX NetX rule not published to host when selected service is a Service Group
When creating an L3 Redirection rule in the Partner Services tab in DFW, selecting a Service Group doesn't create the rule correctly.

Workaround: Use individual services when creating the rule instead of using a Service Group.

Issue 1496273: UI allows creation of in/out NSX firewall rules that cannot be applied to Edges
The web client incorrectly allows creation of an NSX firewall rule applied to one or more NSX Edges when the rule has traffic traveling in the 'in' or 'out' direction and when PacketType is IPV4 or IPV6. The UI should not allow creation of such rules, as NSX cannot apply them to NSX Edges.

Workaround: None.

Issue 1534574: There is no support for Cipher 3C (SHA-256) encryption algorithms for SSLVPN-Plus

Issue 1557924: Universal logical switch is allowed to be consumed in the appliedTo field of a local DFW rule
When a universal logical switch is used as a security group member, the DFW rule can use that security group in AppliedTo field. This indirectly applies the rule on the universal logical switch, which should not be allowed because it may cause unknown behavior of those rules.

Workaround: None.

Issue 1559971: Cross-vCenter NSX firewall exclude list not published if firewall is disabled on one cluster
In cross-vCenter NSX, firewall exclude list is not published to any cluster when the firewall is disabled on one of the clusters.

Workaround: Force sync the affected NSX Edges.

Issue 1407920: Firewall rule republish fails after DELETE API is used
If you delete the entire firewall configuration through the DELETE API method and then try to republish all the rules from a previously saved firewall rules draft, then the rule publish will fail.

Issue 1494718: New universal rules cannot be created, and existing universal rules cannot be edited from the flow monitoring UI

Workaround: Universal rules cannot be added or edited from the flow monitoring UI. EditRule will be automatically disabled.

Issue 1442379: Service composer firewall configuration out of sync
In the NSX service composer, if any firewall policy is invalid (for example of you deleted a security group that was currently in use in a firewall rule), deleting or modifying another firewall policy causes the service composer to become out of sync with the error message Firewall configuration is not in sync.

Workaround: Delete any invalid firewall rules and then synchronize the firewall configuration. Select Service Composer: Security Policies, and for each security policy that has associated firewall rules, click Actions and select Synchronize Firewall Config. To prevent this issue, always fix or delete invalid firewall configurations before making further firewall configuration changes.

Issue 1066277: Security policy name does not allow more than 229 characters
The security policy name field in the Security Policy tab of Service Composer can accept up to 229 characters. This is because policy names are prepended internally with a prefix.

Workaround: None.

Issue 1443344: Some versions of 3rd-party Networks VM-Series do not work with NSX Manager default settings
Some NSX 6.1.4 or later components disable SSLv3 by default. Before you upgrade, please check that all third-party solutions integrated with your NSX deployment do not rely on SSLv3 communication. For example, some versions of the Palo Alto Networks VM-series solution require support for SSLv3, so please check with your vendors for their version requirements.

Issue 1660718: Service Composer policy status is shown as "In Progress" at the UI and "Pending" in the API output

Workaround: None.

Issue 1620491: Policy-level Sync status in Service Composer does not show publishing status of the rules within a policy

When a policy is created or modified, Service Composer will display a success status which indicates only the persistence state. It does not reflect whether the rules were published to the host successfully.

Workaround: Use the firewall UI to view publish status.

Issue 1317814: Service Composer goes out of sync when policy changes are made while one of the Service Managers is down
When a policy changes is made when one of multiple Service Managers is down, the changes will fail, and Service Composer will fall out of sync.

Workaround: Ensure the Service Manager is responding and then issue a force sync from Service Composer.

Issue 1070905: Cannot remove and re-add a host to a cluster protected by Guest Introspection and third-party security solutions
If you remove a host from a cluster protected by Guest Introspection and third-party security solutions by disconnecting it and then removing it from vCenter Server, you may experience problems if you try to re-add the same host to the same cluster.

Workaround: To remove a host from a protected cluster, first put the host in maintenance mode. Next, move the host into an unprotected cluster or outside all clusters and then disconnect and remove the host.

Issue 1648578: NSX forces the addition of cluster/network/storage when creating a new NetX host-based service instance
When you create a new service instance from the vSphere Web Client for NetX host-based services such as Firewall, IDS, and IPS , you are forced to add cluster/network/storage even though these are not required.

Workaround: When creating a new service instance, you may add any information for cluster/network/storage to fill out the fields. This will allow the creation of the service instance and you will be able to proceed as required.

Issue 1772504: Service Composer does not support Security Groups with MAC Set
Service Composer allows use of Security Groups in Policy configurations. In case there is a Security Group which contains MAC Set, Service Composer accepts that Security Group without complaining, but fails to enforce rules for that specific MAC Set. This is because Service Composer works on Layer3 and does not support Layer2 constructs. Note that if a Security Group has IP Set and MAC Set both, the IP set will still be effective, but the MAC Set will be ignored. There is no harm in referencing a Security Group containing MAC Set - user must be aware that the MAC Set will be ignored.

Workaround: If the user's intent is to create Firewall rules using a MAC Set, then the user should use DFW Layer2/Ethernet configuration instead of Service Composer.

Issue 1718726: Cannot force-sync Service Composer after a user has manually deleted the Service Composer's policy section using DFW REST API

In a cross-vCenter NSX environment, a user's attempt to force sync NSX Service Composer configuration will fail if there was only one policy section and that policy section (the Service Composer-managed policy section) was deleted earlier via a REST API call.

Workaround: Do not delete the Service Composer-managed policy section via a REST API call. (Note that the UI already prevents deletion of this section.)

Monitoring Services Known Issues

Issue 1466790: Unable to choose VMs on bridged network using the NSX traceflow tool
Using the NSX traceflow tool, you cannot select VMs that are not attached to a logical switch. This means that VMs on an L2 bridged network cannot be chosen by VM name as the source or destination address for traceflow inspection.

Workaround: For VMs attached to L2 bridged networks, use the IP address or MAC address of the interface you wish to specify as destination in a traceflow inspection. You cannot choose VMs attached to L2 bridged networks as source. See the knowledge base article 2129191 for more information.

Issue 1626233: When NetX service virtual machine (SVM) drops packets, traceflow does not generate dropped observation

The traceflow session exits after packet is sent to the NetX service virtual machine (SVM). When the SVM drops packets, traceflow does not generate dropped observation.

Workaround: There is no workaround. If the traceflow packet is not injected back, it can be assumed that the SVM dropped the packet.

Solution Interoperability Known Issues

Issue 1568861: The NSX Edge deployment fails during any edge deployment from a vCloud Director cell that does not own the vCenter listener

The NSX Edge deployment fails during any Edge deployment from a vCloud Director cell that does not own the vCenter listener. Also, NSX Edge actions, including a redeploy, fail from vCloud Director.

Workaround: Deploy an NSX Edge from the vCloud Director cell which owns the vCenter listener.

NSX Controller Known Issues

Issue 1765354: <deployType> is a required property but it is not used
<deployType> is a required property but it is not used and does not mean anything.

Issue 1516207: Controller(s) may become isolated after IPsec communication is re-enabled on an NSX controller cluster
If an NSX controller cluster is set to allow controller-to-controller communications in the clear (IPsec is disabled), and IPsec-based communication is later re-enabled, one or more controllers may become isolated from the cluster majority due to a mismatched pre-shared key ("PSK"). When this occurs, the NSX API may become unable to change the IPsec settings of the controllers.

Workaround:

Follow these steps to address this issue:

  1. Disable IPSec using the NSX API.

    PUT: /2.0/vdn/controller/node <controllerNodeConfig>
    <ipSecEnabled>false</ipSecEnabled>
    </controllerNodeConfig>

  2. Re-enable IPsec using the NSX API.

    PUT: /2.0/vdn/controller/node <controllerNodeConfig>
    <ipSecEnabled>true</ipSecEnabled>
    <controllerNodeConfig>

Follow these best practices to avoid this issue:

  • Always use the NSX API to disable IPsec. Using the NSX Controller CLI to disable IPsec is not supported.
  • Always verify that all controllers are active before you use the API to change the IPsec setting.

Issue 1306408: NSX Controller logs must be downloaded sequentially
NSX Controller logs cannot be downloaded simultaneously. Even when downloading from multiple controllers, you must wait for the download from the current controller to finish before you start the download from the next controller. Note also that you cannot cancel a log download once it has started.

Workaround: Wait for the current controller log download to finish before starting another log download.

Resolved Issues

New Issues Resolved in NSX 6.3.1

Fixed Issue 1808478: vsfwd service fails to start if vmvisor memory cannot be allocated after upgrading from NSX 6.2.x to NSX 6.3.0
The vsfwd service fails to start if vmvisor memory cannot be allocated after upgrading from NSX 6.2.x to NSX 6.3.0. See VMware knowledge base article 2148974 for more information. Fixed in 6.3.1

Fixed Issue 1818257: VTEP information is not reported to controllers when Enhanced LACP is used for VXLAN post host-upgrade from NSX 6.2.x to NSX 6.3.0 with ESXi 6.0
While upgrading from NSX 6.2.x to 6.3.0 with ESXi 6.0, after host-upgrade, VTEP information is not reported to controllers when Enhanced LACP is used. See VMware knowledge base article 2149210 for more information. Fixed in 6.3.1.

Issues Resolved in NSX 6.3.0 (Click to Expand or Collapse)

Document Revision History

2 February 2017: First edition for NSX 6.3.0.
3 February 2017: Second edition for NSX 6.3.0. Added known issue 1799543
22 February 2017: Third edition for NSX 6.3.0. Updated CDO info
27 February 2017: Fourth edition for NSX 6.3.0. Added known issues 1808478 and 1818257
28 February 2017: First edition for NSX 6.3.1.
30 March 2017: Second edition for NSX 6.3.1. Added known issue 1474650.
10 April 2017: Third edition for NSX 6.3.1. Added information to the Upgrade Notes section.