Home > Blogs > Support Insider

NSXv License Versions

In NSX 6.2.2 VMware introduced 3 different license editions; Standard, Advanced, and Enterprise. These license editions allow you align NSX with your company’s use case.

Standard Edition: Automates IT workflows, bringing agility to the data center network and reducing network operating costs and complexity.

Advanced Edition: Standard Edition plus a fundamentally more secure data center with micro-segmentation. Helps secure the data center to the highest levels, while automating IT provisioning of security.

Enterprise Edition: Advanced Edition plus networking and security across multiple domains. Enables the data center network to extend across multiple sites and connect to high-throughput physical workloads.

new nsx offerings

If you are an existing NSX customer the upgrade to 6.2.3 will not impact your license type and components you are entitled to.

For vCNS customers you can upgrade to NSX, however when doing so you will get an Endpoint for NSX only license. You can enable the additional features by purchasing the NSX license that fits your business requirements.

installation and upgrade

License Capacity Usage 

NSX capacity usage calculation method only reports for clusters prepared and enabled with DFW and VXLAN. CPU count is number of CPUs (sockets) of all prepared hosts. VM count and Concurrent Users is the count of all powered on VMs in the cluster. This VM count does not include system VMs (service VMs, partner VMs, edge appliances etc).

NSX usage is reported correctly under the NSX Manager in NSX vSphere Webclient Plugin. Please note under license management in VC the NSX license will report Usage as ZERO.

nsx usage

vShield Endpoint License in NSX 6.2.3

vShield Endpoint is a component of vCloud Network and Security (vCNS). This component allows you to offload antivirus and anti-malware agent processing to a dedicated secure virtual appliance. With the release of NSX 6.2.3 the default license is NSX for vShield Endpoint allowing you to manage you vShield Endpoint environment with NSX. Customers who purchased vSphere with vShield Endpoint (Essential Plus and above) will be able to download NSX. This means that NSX will appear on the vSphere download site, just like vCNS does today. To ensure customers do not use any other unlicensed NSX features (eg. VXLAN, DFW, Edge services), the license key will have hard enforcement to prevent NSX host preparation and block Edge creation. If you require an evaluation license key, please request this through VMware sales.

 

Log Insight License in NSX 6.2.2 and above

VMware vRealize Log Insight 3.3.2 for NSX provides intelligent log analytics for NSX. Log Insight provides monitoring and troubleshooting capabilities and customizable dashboards for network virtualization, flow analysis, and alerts. The 3.3.2 version of Log Insight accepts NSX Standard/Advanced/Enterprise edition license keys issued for NSX 6.2.2 and above. This means you will have an enterprise level Log Insight license for very license of NSX.

log analytics for NSX

About the authors:

Top 20 vRealize Automation articles for June 2016

Top 20Here is our Top 20 vRealize Automation (vRA) articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. vRealize Automation 7.X Manager Service extensibility callouts to Event Broker fails
  2. Changing the VMware vRealize Automation IaaS service account or updating the vRealize Automation IaaS service account password
  3. Deleting an endpoint in vRealize Automation fails with the error: This endpoint is being used by # compute resources and # storage paths and cannot be deleted
  4. Certificate troubleshooting, supportability, and trust requirements for vRealize Automation 6.2
  5. VMware vRealize Automation loses storage information after manually migrating a virtual machine in a Storage DRS cluster
  6. Reconfiguring a VMware vRealize Automation managed virtual machine fails with the error: [Error code: 42000 ] – [Error Msg: Infrastructure service provider error]
  7. Log locations for VMware vRealize Automation 7.x
  8. Provisioning Virtual Machine from catalog fails in vRealize Automation 6.2.x
  9. Services take a long time or fail to start in vRealize Automation High Availability environment
  10. Installing the Model Manager Data in vRealize Automation fails with the error: 500 – Internal Server Error
  11. Moving the VMware vRealize Automation 6.x SQL database to a new server
  12. Using JXplorer to update the LDAP string for an identity source for VMware vRealize Automation 6.0.x, 6.1.x
  13. Migrating to a new SSO or recovering from a reinstallation of SSO in VMware vRealize Automation
  14. Logging in to the VMware vRealize Automation 6.2.x Appliance Management website fails with the error: Unable to authenticate user. Please try again
  15. Using the vRealize Certificate Generation tool to assist with creating signed certificates
  16. Upgrading VMware vRealize Automation from vCenter SSO 5.5 to Platform Services Controller (PSC) 6.0 makes Tenants inaccessible (Linux-based SSO only)
  17. Provisioning multiple virtual machines in VMware vRealize Automation with external workflows fail with Timeout on signal errors
  18. Hard disks and NICs are removed unexpectedly in vRealize Automation
  19. Deploying a virtual machine using a clone workflow in vRealize Automation 6.x fails with the error: The object has already been deleted or has not been completely created
  20. Delegating permissions across domains using Domain Local groups does not work as expected with vCenter Server or vRealize Automation

Top 20 vRealize Operations Manager articles for June 2016

Top 20Here is our Top 20 vRealize Operations Manager articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Creating low disk space alerts for the virtual machine guest file systems in VMware vRealize Operations Manager 6.0.x
  2. Modifying the name resolution settings of the VMware vRealize Operations Manager vApp
  3. VMware vRealize Operations Manager 6.x displays the critical alert: FSDB file corrupted for resourceInternalId
  4. VMware vCenter Log Insight vRealize Operations 6.x content pack dashboards display no data
  5. Important information before upgrading to vSphere 6.0 Update 1
  6. vRealize Operations Manager 6.0 displays erroneous alarm: Virtual Machine is experiencing high number of receiver packets dropped
  7. Mappings between End Point Operations operating systems and virtual machines are not created in VMware vRealize Operations Manager 6.1
  8. High garbage collection occurs on the VMware vRealize Operations Manager (vROps) Master node
  9. After upgrading to VMware vRealize Operations 6.2.0a, vCenter adapters remain in Starting state
  10. vRealize Operations Manager health badges are missing from vSphere Web Client
  11. VMware vRealize Operations UI sessions time out after 30 minutes of inactivity
  12. Configure a certificate for use with vRealize Operations Manager
  13. Suppressing or suspending an alert in VMware vRealize Operations Manager 5.x / 6.0.x fails with the error: Operation Not Completed
  14. Collections against one or more vCenter Server data centers fail
  15. Changing a custom certificate in VMware vRealize Operations 6.0 after initial deployment
  16. Accessing the VMware vRealize Operations Manager 6.0 API by LDAP users fails with the error: HTTP/1.1 401 Unauthorized
  17. The system audit report in VMware vRealize Operations Manager 6.x reports high metrics
  18. Removing a node from a VMware vRealize Operations Manager 6.x cluster
  19. Change the date, time, or time zone of a vApp-based vRealize Operations Manager node
  20. Understanding Feature Accommodation between VMware vSphere 6.0 and vRealize Operations 5.8.x and 6.0.1 Feature Accommodation

Top 20 vSAN articles for June 2016

Top 20Here is our Top 20 vSAN articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. vSphere 5.5 Virtual SAN requirements
  2. Adding a host back to a Virtual SAN cluster after an ESXi host rebuild
  3. Support statement for 512e and 4K Native drives for VMware vSphere and VSAN
  4. VMware Virtual SAN 6.1 health plugin reports the error: Unexpected status code: 503
  5. Following maintenance, hosts in a Virtual SAN cluster may erroneously report the error: Host cannot communicate with all other nodes in virtual SAN enabled cluster
  6. Requirements and considerations for the deployment of VMware Virtual SAN (VSAN)
  7. Virtual SAN Health Service – Physical Disk Health – Metadata Health
  8. Consolidating disks in VMware Virtual SAN fails with the error: An error occurred while consolidating disks: msg.disklib.NOSPACE
  9. Using Oracle RAC on vSphere 6.x VSAN Datastore
  10. Replacing VMware vCenter Server Certificates with SSL Certificate Automation Tool causes the vSAN health check plugin to stop functioning with the error: Error HTTP status 503
  11. Network port diagram for vSphere 6.x
  12. Shutting down and powering on a VSAN 6.x Cluster when vCenter Server is running on top of VSAN
  13. Virtual SAN Health Service – Performance Service – Stats DB object check
  14. VMware Virtual SAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
  15. Upgrading Virtual SAN On-Disk Format from 2.5 to 3.0 with only one disk group per host in a stretched cluster fails
  16. Understanding Virtual SAN on-disk format versions
  17. Creating a VSAN Disk Group fails with the error: General Virtual SAN error
  18. Enabling or capturing performance statistics using Virtual SAN Observer for VMware Virtual SAN
  19. Removing a VMware Virtual SAN-enabled cluster and detaching the VMware ESXi host from the cluster fails
  20. Changing the multicast address used for a VMware Virtual SAN Cluster

Top 20 Horizon View articles for June 2016

Top 20Here is our Top 20 Horizon View articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

 

  1. Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View
  2. Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions
  3. Poor virtual machine application performance may be caused by processor power management settings
  4. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  5. VMware View ports and network connectivity requirements
  6. Using Microsoft Certreq to generate signed SSL certificates in VMware Horizon View
  7. Forcing replication between ADAM databases
  8. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in
  9. Provisioning View desktops fails due to customization timeout errors
  10. Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, 5.1, 5.2, 5.3, 6.0, and 6.1
  11. Manually deleting replica virtual machines in VMware Horizon View 5.x
  12. Removing a standard (replica) connection server or a security server from a cluster of connection/security servers
  13. Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines
  14. Dual monitors configured using PCoIP does not span both the monitors for VMware View
  15. Finding and removing unused replica virtual machines in the VMware Horizon View
  16. Connecting to the View ADAM Database
  17. Configuring security protocols on components to connect the View Client with desktops
  18. Troubleshooting USB redirection problems in VMware View Manager
  19. Administration dashboard in VMware Horizon View reports the error: Server’s certificate cannot be checked
  20. Recommended restart cycle of the VMware Horizon View environment

Top 20 NSX articles for June 2016

Top 20Here is our Top 20 NSX articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. NSX is unavailable from the vSphere Web Client Plug-in after taking a backup of NSX Manager with quiesced snapshot
  2. vCenter Server 6.0 restart/reboot results in duplicate VTEPs on VXLAN prepared ESXi hosts
  3. NSX Edge is unmanageable after upgrading to NSX 6.2.3
  4. vCenter Server or Platform Services Controller certificate validation error for external VMware Solutions in vSphere 6.0
  5. vSphere Web Client performance is slow when using NSX Manager
  6. Installing VXLAN Agent fails with ESX Agent Manager displaying the error: Agent VIB module not installed
  7. Troubleshooting vSphere ESX Agent Manager (EAM) with NSX
  8. Oracle connections time out when forwarded through the VMware NSX for vSphere 6.1.x Edge
  9. NSX Controller becomes isolated or disconnects intermittently
  10. Licensing VMware vSphere 5.5.x/6.0.x and VMware NSX for vSphere 6.x
  11. vCenter Server access gets blocked after creating a Deny All rule in NSX Distributed Firewall (DFW)
  12. No Flow Records displayed in NSX Manager flow monitoring
  13. VMware NSX Manager virtual appliance installation fails with the error: Operation timed out
  14. Registering NSX Manager to Lookup Service with External Platform Service Controller (PSC) fails with the error: server certificate chain not verified
  15. In VMware NSX for vSphere 6.x, modifying an NSX Transport zone through the vSphere Web Client (add/edit/delete/connect/disconnect) fails with the error: Internal server error has occurred
  16. When adding a previously provisioned ESXi host to a cluster in VMware NSX for vSphere 6.1.x, the cluster status for VXLAN displays an error: Error Unconfigure
  17. Migration of Service VM (SVM) may cause ESXi host issues in VMware NSX for vSphere 6.x
  18. NSX User Interface (UI) is grayed out for several seconds and exhibits slow performance on NSX for vSphere 6.2.0
  19. Slow VMs after upgrading VMware tools in NSX / vCloud Networking and Security
  20. NSX Edge logs show Memory Overloaded warnings

Top 20 vCenter Server articles for June 2016

Top 20Here is our Top 20 vCenter articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Purging old data from the database used by VMware vCenter Server
  2. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  3. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  4. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  5. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  6. Upgrading to vCenter Server 6.0 best practices
  7. Correlating build numbers and versions of VMware products
  8. Update sequence for vSphere 6.0 and its compatible VMware products
  9. Stopping, starting, or restarting VMware vCenter Server services
  10. In vCenter Server 6.0, the vmware-dataservice-sca and vsphere-client status change from green to yellow continually
  11. Enabling EVC on a cluster when vCenter Server is running in a virtual machine
  12. The vpxd process becomes unresponsive after upgrading to VMware vCenter Server 5.5
  13. Migrating the vCenter Server database from SQL Express to full SQL Server
  14. Reducing the size of the vCenter Server database when the rollup scripts take a long time to run
  15. Consolidating snapshots in vSphere 5.x/6.0
  16. Back up and restore vCenter Server Appliance/vCenter Server 6.0 vPostgres database
  17. Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
  18. Build numbers and versions of VMware vCenter Server
  19. Increasing the size of a virtual disk
  20. Determining where growth is occurring in the VMware vCenter Server database

Top 20 ESXi articles for June 2016

Top 20Here is our Top 20 ESXi articles list for June 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  3. Commands to monitor snapshot deletion in VMware ESXi/ESX
  4. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  5. Restarting the Management agents on an ESXi or ESX host
  6. Recreating a missing virtual machine disk descriptor file
  7. Identifying and addressing Non-Maskable Interrupt events on an ESX/ESXi host
  8. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  9. Snapshot consolidation in VMware ESXi 5.5.x and ESXi 6.0.x fails with the error: maximum consolidate retries was exceeded for scsix:x
  10. Powering off a virtual machine on an ESXi host
  11. Correlating build numbers and versions of VMware products
  12. Updating an ESXi/ESX host using VMware vCenter Update Manager 4.x and 5.x
  13. Update sequence for vSphere 6.0 and its compatible VMware products
  14. ESXi 5.5 or 6.0 host disconnects from vCenter Server with the syslog.log error: Unable to allocate memory
  15. Enabling or disabling VAAI ATS heartbeat
  16. ESXi 6.0 hosts become unresponsive when joined to an Active Directory domain
  17. Enabling EVC on a cluster when vCenter Server is running in a virtual machine
  18. Unable to delete the virtual machine snapshot due to locked files
  19. Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions)
  20. Reverting to a previous version of ESXi

NSX for vSphere Field Advisory – June 2016 Edition

End of General Support for VMware NSX for vSphere 6.1.x has been extended by 3 months to January 15th, 2017. This is to allow customers to have time to upgrade from NSX for vSphere 6.1.7, which contains an important security patch improving input validation of the system, to the latest 6.2.x release. For recommended upgrade paths, refer to the latest NSX for vSphere 6.2 Release Notes and the VMware Interoperability Matrix.
Migration of Service VM (SVM) may cause ESXi host issues in VMware NSX for vSphere 6.x (2141410). See also the CAUTION statement in the 6.2.3 Administration Guide.

Do not migrate the Service VM (SVM) manually (vMotion/SvMotion) to another ESXi host in the cluster.
The latest versions of vSphere 5.5 and 6.0 inhibit vMotion migration. However, storage vMotion is not blocked, and such movement may lead to unpredictable results on the destination host.

vCenter Server 6.0 restart/reboot results in duplicate VTEPs on VXLAN prepared ESXi hosts (2144605). The NSX-side update to protect against this issue is available in 6.2.3. This issue will be resolved fully in a future version of vCenter.

Top Issues:

Important new and changed KBs with NSX for vSphere 6.2.3. For more information, see Troubleshooting VMware NSX for vSphere 6.x (2122691).

Important new and changed documentation with NSX for vSphere 6.2.3 – see the NSX Documentation Center

How to track the top field issues

Windows 2008+ incremental backups become full backups in ESXi 6.0 b3825889

vmware_tools_iconVMware is actively working to address a recently discovered issue wherein an incremental backup becomes a full backup when backing up Windows 2008 (or higher) virtual machines with VSS-based application quiesced snapshot.

This recent CBT (Changed Block Tracking) issue does not cause any data loss or data corruption.

This issue is well understood and VMware engineering is actively working on a fix.

For more details on this issue and latest status on resolution, please refer to KB article: After upgrading to ESXi 6.0 Build 3825889, incremental virtual machine backups effectively run as full backups when application consistent quiescing is enabled (2145895)

Subscribe to the rss feed for the KB article to ensure you do not miss any update by using this link.