vCNS / NSX + vCenter(s) + Single PSC potential license issues

During the course of upgrades/installs/adding capacity people hit many different errors. One such error or issue came up and I just want to make people aware going forward about it.

If you are thinking about adding NSX to your environment and are currently running vCNS please be careful if you are using a SINGLE PSC that your vCenters are connected to. Once you add a NSX license(EVAL or full license) it will AUTO UN-SELECT your vCNS license!vspherelicense1

Then if you are using something like vCloudDirector you might see errors like the following: “VSM response error (214): Not licensed for Entity : vcloud-netsec feature : vxlan : add on :”


To resolve this and revert back to your vCNS licenses, under Licenses click the Assets Tab, click on Solutions, select the license you want to assign again and then under the All Action gear dropdown you can click assign license. vspherelicense3.PNG


This is a short post but hopefully it will save some people frustration in the future.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s