I’ve fought with this for an embarrassingly long time. Had a failed PAS (Pivotal Application Services) deployment (missed several of the NSX configuration requirements) but removed the cruft and tried again and again and again. In each case, PAS and NCP would deploy, but fail on the PAS smoke_test errand. The error message said more detail is in the log.
Which Log?!
I ssh’d into the clock_global VM and found the smoke_test logs. They stated that the container for instance {whatever} could not be created and an error of NCP04004. This pointed me to the Diego Cells (where the containers would be created) and I poked around in the /var/vcap/sys/log/garden logs there. They stated that the interface for the instance could not be found. Ok, this is sounding more like an NSX problem.
I ended up parsing through the NSX Manager event log and found this gem:
IP Block Error
Ah-ha! Yup, I’d apparently allocated a couple of /28 subnets from the IP Block. So when the smoke test tried to allocate a /24, the “fixed” subnet size had already been set to /28, causing the error.
Resolution was to simply remove all of the allocated subnets from the IP block. This could have been avoided by either not reusing an existing IP Block or using the settings in the NCP configuration to create a new IP Block with a given CIDR.
After upgrading to NSX-T 2.2, my environment began throwing this error in the GUI when I tried to navigate to the firewall section or any router. In addition, the nsx-cli shell script for cleanup was failing every time with a similar firewall-rule-related error.
Searching for a bitm I stumbled onto KB 56611: Upgrading NSX-T manager from 2.1.0.0 to 2.2.0.0 reports “General Error has occurred” on Firewall’s General UI section.
Down at the bottom of the KB, it essentially states that if you’ve already upgraded to 2.2 from 2.1, you’ll have to replace a jar file in order to resolve the problem. Oh, and you have to open a ticket to get the .jar.
So, if you run into this – and you receive the nsx-firewall-1.0.jar file – here’s the steps for resolution:
SSH into the NSX Manager as root (not admin)
Navigate to /opt/vmare/proton-tomcat/webapps/nsxapi/WEB-INF/lib
Copy the existing nsx-firewall-1.0.jar file elsewhere (I copied it to home and SCP’d it out from there)
Copy the new nsx-firewall-1.0.jar file into this folder. (I put it on an local webserver and pulled it down with wget)
Change the owner of the jar to uproton:
chown uproton:uproton nsx-firewall-1.0.jar
Change the permissions to match the other files:
chmod o-r nsx-firewall-1.0.jar
Reboot the NSX Manager
Enjoy being able to see and edit firewall rules again!
I’ve fought with PKS and NSX-T for a month or so now. I’ll admit it: I did everything wrong, several times. One thing for certain, I know how NOT to configure it. So, now that I’ve finally gotten past my configuration issues, it makes sense to share the pain lessons learned.
Set your expectations correctly. PKS is literally a 1.0 product right now. It’s getting a lot of attention and will make fantastic strides very quickly, but for now, it can be cumbersome and confusing. The documentation is still pretty raw. Similarly, NSX-T is very young. The docs are constantly referring you to the REST API instead of the GUI – this is fine of course, but is a turn-off for many. The GUI has many weird quirks. (when entering a tag, you’ll have to tab off of the value field after entering a value, since it is only checked onBlur)
Use Chrome Incognito NSX-T does not work in Firefox on Windows. It works in Chrome, but I had issues where the cache would problems (the web GUI would indicate that backup is not configured until I closed Chrome, cleared cache and logged in again)
Do not use exclamation point in the NSX-T admin password Yep, learned that the hard way. Supposedly, this is resolved in PKS 1.0.3, but I’m not convinced as my environment did not wholly cooperate until I reset the admin password to something without an exclamation point in it
Tag only one IP Pool with ncp/external I needed to build out several foundations on this environment and wanted to keep them in discrete IP space by created multiple “external IP Pools” and assigning each to its own foundation. Currently the nsx-cli.sh script that accompanies PKS with NSX-T only looks for the “ncp/external” tag on IP Pools, if more than one is found, it quits. I suppose you could work around this by forking the script and passing an additional “cluster” param, but I’m certain that the NSBU is working on something similar
Do not take a snapshot of the NSX Manager This applies to NSX for vSphere and NSX-T, but I have made this mistake and it was costly. If your backup solution relies on snapshots (pretty much all of them do), be sure to exclude the NSX Manager and…
Configure scheduled backups of NSX Manager I found the docs for this to be rather obtuse. Spent a while trying to configure a FileZilla SFTP or even IIS-FTP server until it finally dawned on me that it really is just FTP over SSH. So, the missing detail for me was that you’ll just need a linux machine with plenty of space that the NSX Manager can connect to – over SSH – and dump files to. I started with this procedure, but found that the permissions were too restrictive.
Use concourse pipelines This was an opportunity for me to really dig into concourse pipelines and embrace what can be done. One moment of frustration came when PKS 1.0.3 was released and I discovered that the parameters for vSphere authentication had changed. In PKS 1.0 through 1.0.2, there was a single set of credentials to be used by PKS to communicate with vCenter Server. As of 1.0.3, this was split into credentials for master and credentials for workers. So, the pipeline needed a tweak in order to complete the install. I ended up putting in a conditional to check the release version, so the right params are populated. If interested, my pipelines can be found at https://github.com/BrianRagazzi/concourse-pipelines
Count your Load-Balancers In NSX-T, the load-balancers can be considered a sort of empty appliance that Virtual Servers are attached to and can itself attach to a Logical Router. The load-balancers in-effect require pre-allocated resources that must come from an Edge Cluster. The “small” load-balancer consumes 2 CPU and 4GB RAM and the “Large” edge VM provides 8 CPU and 16GB RAM. So, a 2-node Edge Cluster can support up to FOUR active/standby Load-Balancers. This quickly becomes relevant when you realize that PKS creates a new load-balancer when a new K8s cluster is created. If you get errors in the diego databse with the ncp job when creating your fifth k8s cluster, you might need to add a few more edge nodes to the edge cluster.
Configure your NAT rules as narrow as you can. I wasted a lot of time due to mis-configured NAT rules. The log data from provisioning failures did not point to NAT mis-configuration, so wild geese were chased. Here’s what finally worked for me:
Router
Priority
Action
Source
Destination
Translated
Description
Tier1 PKS Management
512
No NAT
[PKS Management CIDR]
[PKS Service CIDR]
Any
No NAT between management and services
[PKS Service CIDR]
[PKS Management CIDR]
1024
DNAT
Any
[External IP for Ops Manager]
[Internal IP for Ops Manager]
So Ops Manager is reachable
[External IP for PKS Service]
[Internal IP for PKS Service] (obtain from Status tab of PKS in Ops Manager)
So PKS Service (and UAA) is reachable
SNAT
[Internal IP for PKS Service]
Any
[External IP for PKS Service]
Return Traffic for PKS Service
2048
[PKS Management CIDR]
[Infrastructure CIDR] (vCenter Server, NSX Manager, DNS Servers)
[External IP for Ops Manager]
So PKS Management can reach infrastructure
[PKS Management CIDR]
[Additional Infrastructure] (NTP in this case)
[External IP for Ops Manager]
Tier1 PKS Services
512
No NAT
[PKS Service CIDR]
[PKS Management CIDR]
Any
No NAT between management and services
[PKS Management CIDR]
[PKS Service CIDR]
1024
SNAT
[PKS Service CIDR]
[Infrastructure CIDR] (vCenter Server, NSX Manager, DNS Servers)
[External IP] (not the same as Ops Manager and PKS Service, but in the same L3 network)
Ran into a difficulty trying to use the self-signed certificate that comes pre-configured on the manager for NSX-T. In my case, Pivotal Operations Manager refused to accept the self-signed certificate.
So, for NSX-T 2.1, it looks like the procedure is:
Log on to the NSX Manager and navigate to System|Trust
Click CSRs tab and then “Generate CSR”, populate the certificate request details and click Save
Select the new CSR and click Actions|Download CSR PEM to save the exported CSR in PEM format
Submit the CSR to your CA to get it signed and save the new certificate. Be sure to save the root CA and any subordinate CA certificates too<. In this example, certnew.cer is the signed NSX Manager certificate, sub-CA.cer is the subordinate CA certificate and root-CA.cer is the Root CA certificate
Open the two (or three) cer files in notepad or notepad++ and concatenate them in order of leaf cert, (subordinate CA cert), root CA cert
Back in NSX Manager, select the CSR and click Actions|Import Certificate for CSR. In the Window, paste in the concatenated certificates from above and click save
Now you’ll have a new certificate and CA certs listed under Certificates. The GUI only shows a portion of the ID by default, click it to display the full ID and copy it to the clip board
Launch RESTClient in Firefox.
Click Authentication|Basic Authentication and enter the NSX Manager credentials for Username and Password, click “Okay”
For the URL, enter https://<NSX Manager IP or FQDN>api/v1/node/services/http?action=apply_certificate&certificate_id=<certificate ID copied in previous step>
Set the method to POST and click SEND button
check the Headers to confirm that the status code is 200
Refresh browser session to NSX Manager GUI to confirm new certificate is in use
Notes:
I was concerned that replacing the certificate would break the components registered via the certificate thumbprint; this process does not break those things. They remain registered and trust the new certificate
I’d wanted to revert my environment from (an incomplete install of) NSX-T v2.0 back to NSX for vSphere v6.3.x, but found that the hosts would not complete preparation. The logs indicated that something was “claimed by multiple non-overlay vibs”.
Error in esxupdate.log
I found that the hosts still had the NSX-T VIBs loaded, so to remove them, here’s what I did:
Put the host in maintenance mode. This is necessary to “de-activate” the VIBs that may be in use
Edit – 2/1/17 – Updated with OpenSSL configuration detail
Edit – 3/20/17 – Updated SubjectAltNames in config
Preparation
SSL Certificate. You’ll need the signed public cert for your URL (certnew.cer), the associated private key (pcf.key) and the public cert of the signing CA (root64.cer).
Download and install OpenSSL
Create a config file for your request – paste this into a text file:
[ req_distinguished_name ]
countryName = US
stateOrProvinceName = State
localityName = City
0.organizationName = Company Name
organizationalUnitName = PCF
commonName = *.pcf.domain.com
Replace the values in red with those appropriate for your environment. Be sure to specify the server name and IP address as the Virtual IP and its associated DNS record. Save the file as pcf.cfg. You’ll want to use the wildcard “base” name as the common name and the server name, as well as the *.system, *.apps, *.login.system and *.uaa.system Subject Alt Names.
Use OpenSSL to create the Certificate Site Request (CSR) for the wildcard PCF domain.
Use OpenSSL to convert the key to RSA (required for NSX to accept it)
openssl rsa -in pcf.key -out pcfrsa.key
Submit the CSR (pcf.csr) to your CA (Microsoft Certificate Services in my case), retrieve the certificate (certnew.cer) and certificate chain (certnew.p7b) base-64 encoded.
Double-click certnew.p7b to open certmgr. Export the CA certificate as 64-bit encoded x509 to a file (root64.cer is the file name I use)
Networks. You’ll need to know what layer 3 networks the PCF components will use. In my case, I set up a logical switch in NSX and assigned the gateway address to the DLR. Probably should make this a 24-bit network, so there’s room to grow, but not reserving a ridiculous number of addresses. We’re going to carve up the address space a little, so make a note of the following:
Gateway and other addresses you typically reserve for network devices. (eg: first 9 addresses 1-9)
Address that will be assigned to the NSX load balancer. Just need one (eg: 10)
Addresses that will be used by the PCF Routers. At least two. These will be configured as members in the NSX Load Balancer Pool.
DNS, IP addresses. PCF will use “system” and “apps” subdomains, plus whatever names you give any apps deployed. This takes some getting used to – not your typical application. Based on the certificate we created earlier, I recommend just creating a “pcf” subdomain. In my case, the network domain (using AD-DNS) is ragazzilab.com and I’ve created the following:
pcf.ragazzilab.com subdomain
*.pcf.ragazzilab.com A record for the IP address I’m going to assign to the NSX Load-Balancer
NSX
Assuming NSX is already installed and configured. Create or identify an existing NSX Edge that has an interface on the network where PCF will be / is deployed.
Assign the address we noted above to the inteface under Settings|Interfaces
Under Settings|Certificates, add the our SSL certificates
Click the Green Plus and select “CA Certificate”. Paste the content of the signing CA public certificate (base64.cer) into the Certificate Contents box. Click OK.
Click the Green Plus and select “Certificate”. Paste the content of the signed public cert (certnew.cer) into the Certificate Contents box and paste the content of the RSA private key (pcfrsa.key) into the Private Key box. Click OK.
Under Load Balancer, create an Application Profile. We need to ensure that NSX inserts the x-forwarded-for HTTP headers. To do that, we need to be able to decrypt the request and therefore must provide the certificate information. I found that Pool Side SSL had to be enabled and using the same Service and CA Certificates.
Router Application Profile
Create the Service Monitor. What worked for me is a little different from what is described in the GoRouter project page. The key points are that we want to specify the useragent and look for a response of “ok” with a header of “200 OK”.
Service Monitor for PCF Router
Create the Pool. Set it to ROUND-ROBIN using the Service Monitor you just created. When adding the routers as members, be sure to set the port to 443, but the Monitor Port to 80.
Router Pool
Create the Virtual Server. Specify the Application Profile and default Pool we just created. Obviously, specify the correct IP Address.
Virtual Server Configuration
PCF – Ops Manager
Assuming you’ve already deployed the Ops Manager OVF, use the installation dashboard to edit the configuration for Ops Manager Director. I’m just going to highlight the relevant areas of the configuration here:
Networks. Under “Create Networks”, be sure that the Subnet specified has the correct values. Pay special attention to the reserved IP ranges. These should be the addresses of the network devices and the IP address assigned to the load-balancer. Do not include the addresses we intend to use for the routers though. Based on the example values above, we’ll reserve the first 10 addresses.
Ops Manager Network Config
Ops Manager Director will probably use the first/lowest address in range that is not reserved.
PCF – Elastic Runtime
Next, we’ll install Elastic Runtime. Again, I’ll highlight the relevant sections of the configuration.
Domains. In my case it’s System Domain = system.pcf.ragazzilab.com and Apps Domain = apps.pcf.ragazzilab.com
Networking.
Set the Router IPs to the addresses (comma-separated) you noted and added to as members to the NSX load-balancer earlier.
Leave HAProxy IPs empty
Select the point-of-entry option for “external load balancer, and it can forward encrypted traffic”
Paste the content of the signed certificate (certnew.cer) into the Certificate PEM field. Paste the content of the CA public certificate (root64.cer) into the same field, directly under the certificate content.
Paste the content of the private key (pcf.key) into the Private Key PEM field.
Check “Disable SSL Certificate verification for this environment”.
Resource Config. Be sure that the number of Routers is at least 2 and equal to the number of IP addresses you reserved for them.
Troubleshooting
Help! The Pool Status is down when the Service Monitor is enabled.
This could occur if your routers are behaving differently from mine. Test the response by sending a request to one of the routers through curl and specifying the user agent as HTTP-Monitor/1.1
curl -v -A “HTTP-Monitor/1.1” “http://{IP of router}”
Testing router with curl
The value in the yellow box should go into the “Expected” field of the Service Monitor and the value in the red box should go into the “Receive” field. Note that you should not get a 404 response, if you do, check that he user agent is set correctly.
Notes
This works for me and I hope it works for you. If you have trouble or disagree, please let me know.
If you’re here, you’ve probably already found VMKB2092228 and been frustrated by the lack of an easy and consistent way to configure all the NSX components to send log data. Me too.
I put together a vRO workflow to help configure (and reconfigure) syslog on NSX.
It prompts for the NSX manager connection info and Syslog server info
Creates a REST host for the NSX manager using the admin super-user account
Adds several REST operations to the NSX Manager REST host
Deletes and readds the syslog configuration on the NSX Manager
Optionally configures Activity Monitoring on the NSX Manager
Identifies each running Controller; deletes and readds the syslog config on each
Identifies each deployed and “Green” Edge (including DLRs); deletes and readds the syslog config on each
Removes the NSX Manager REST host created earlier
Notes
It must use the NSX Manager admin account – it’s the only superuser account that can update teh manager config.
If a Controller is not running when the workflow runs, its syslog config will not be updated
If an Edge’ state is not “green” or is not fully deployed, its syslog config will not be updated
By downloading any code, package or file, you acknowledge that:There is no explicit or implied warranty or support for the code. Neither Brian Ragazzi, his employer nor anyone else is responsible for any problems, errors, omissions, unexpected behavior, breakage, trauma, outage, fatigue, lost time, lost work or incontinence that may occur as a result of using the code or package.
Import package into vRO
Run the ConfigureSyslogNSX workflowWorkflow Step 1
I’ve spent the past several weeks testing, trying to understand Cross-vCenter NSX and make it work in a useful way. Here’s what I’ve learned so far.
Environment and Set up:
I knew I needed two “sites” with discrete storage, but had a few physical limitations. I.e; I only own one managed router (Cisco C2821) and one managed switch (Force 10 S50). I trunked the management and vtep network to all the hosts, but configured a discrete transit network for each “site”. I hope to work with a much larger lab environment and do a thorough review of the setup and configuration. In the meantime, here’s the basics.
Two-host cluster, NSX manager and vCenter Server for primary site
1 host cluster, NSX manager and vCenter Server for recovery site
vSphere 6.0 U1b
NSX for vSphere 6.2.1
Universal Transport Zone includes both clusters, configured for Local Egress.
VTEPs in same L3 network (for simplicity’s sake)
Edge per site, discrete transit networks
Universal DLR for tenant networks, uplinked to both site ESGs
OSPF area for each ESG->UDLR
Partial Lab Network
Objectives
Eliminate need for manual synchronization between sites/NSX instances
Success! The distributed firewall and universal objects are respected by the NSX manager at both sites. Universal Security Groups and Logical Switches are usable at either end.
Span VXLANs between sites
Success! This is not really a surprise. As long as the clusters share a Transport Zone and teh VTEPs can route to each other, this works great.
Minimize network alterations when used with Site Recovery Manager to failover protected VMs between vCenter Servers.
Partial success. A placeholder/recovered VM will be in the same Universal Security Groups as the protected VM and the distributed firewall rules will apply as expected without any changes needed. However, even with Local Egress enabled, you’ll have to apply some sort of route updates so that traffic destined for the recovered VMs can get there. It looks like the route redistribution for egress us handled automatically though. This configuration pushed the limits of what I can do with my lab.
Make use of site-to-site microsegmentation (my definition: application of security policy regardless of L3 network scope)
Partial Success. I was really disappointed here. When the document states that you can add IP Sets, MAC Sets and other Universal Security Groups to a Universal Security Group, it means that’s ALL you can add. I’ve blogged a few times about adding VMs to a Security Group – even doing it as a Resource Action in vRA. That won’t work with Universal Security Groups! The only workaround I see is to add the desired VM’s IP or MAC to a Set and include the Set in the Security group. Blech!
Retain ability to assign security policy via security group membership through vRA
FAILURE. As noted above, we cannot assign Universal security group membership to a VM using any of the existing custom properties.
Notes and Observations
I guess I get it. The vm id between vCenter Servers will differ, so saying that “vm-123 is a member of securitygroup-456” is not valid on a different vCenter Server. But a table of IPs and MACs would be universally valid. I’m hoping that in a near-future version, the universal security group membership capabilities can be extended; perhaps with a shared or replicated vCenter Inventory Service.
***UPDATE*** The download link is currently broken. I seem to have lost the file, will fix the link as soon as I find or recreate it. Sorry about that. 😦
In part 1 of this series, we created a list of security groups and displayed that list to users during the request. In this post, we want to enhance that functionality by adding these features.
Creation of Security Groups and inclusion in Dropdown lists
Add a VM to a Security Group post-provisioning
Import existing Security Groups into vRA inventory
Add a Security Group to a Dropdown list
We’re going to do that by importing a vCO package with some new workflows and actions, then link up the workflows to Advanced Services and Resource Actions. As before, we’ll require the NSX and vCAC/vRA plugins for Orchestrator.
Preparation
Complete the creation of the VCNS.SecurityGroup.Names.production property dictionary and valuelist attribute from Part 1. We’re going to reuse those items. so make a note of the exact name of the property dictionary and the valuelist attribute. In my case, I’ve named the Property Dictionary VCNS.SecurityGroup.Names.production and also named the valuelist attribute for it VCNS.SecurityGroup.Names.production
Make sure vRA Advanced Services Server Configuration is complete and test the connection to the Orchestrator server. The default, built-in VCO is fine.
Login to vCO client as a vCO Admin. Set the mode to “Design” and navigate to the Inventory tab. Make sure that you have a connection listed under “vCAC Infrastructure Administration” and a connection listed under “NSX”.
Confirm that you have the necessary connections on the inventory tab
Get the Package
I’ve put together a handful of workflows and actions that use or expand the NSX plugin to provide information of functionallity back to vRA. Where possible, I reused existing library workflows, but in some cases, I had to use the API to create a REST call and consume that in an action.
By downloading any code, package or file, you acknowledge that:
There is no explicit or implied warranty or support for the code. Neither Brian Ragazzi, his employer nor anyone else is responsible for any problems, errors, omissions, unexpected behavior, breakage, trauma, outage, fatigue, lost time, lost work or incontinence that may occur as a result of using the code or package.
Download the zip file. It contains the package and a couple of images that can be used for the advanced services
Import the Package
Extract the zip file
In the vCO Client, navigate to the packages tab.
Click the “import package” button and select the extracted .package file
On the Package Import Information step, click “Import”
Package Import Information
On the Import package… step, check the “Select/Deselect all” box to check all of the items. Please note the server path, these should not be duplicates of anything else you have in your vCO inventory (unless you’ve already imported this package previously). Click “Import Selected elements”.
Select all items
Review the workflows and actions added to your inventory.
Configure Advanced Services – Create Security Group
This service enables the user to create a new NSX Security Group and automatically adds its name to the appropriate dropdown list of security groups. It can be added once for each different list of security groups. You’ll need to know the exact name of the Property Dictionary and valuelist attribute you created in Part 1.
NSX Management ServicesNSX Security Groups in vRA Items
While logged into vRA as a service architect, navigate to the Advanced Services tab, click “Custom Resources“
We need to make vRA aware of NSX Security Groups. Click the Add button.
In the Orchestrator Type field, enter “NSX:SecurityGroup“; for the Name, I suggest “NSX Security Group“, click Next
Add NSX Security Group as Custom Resource
On the details form, we’re not going to make any changes, but if you wanted to hide certain properties, you could here. Click “Add“.
Click “Service Blueprints”, then the “Add” button.
On the Workflow tab, select the AddNewSecurityGrouptoDropdown workflow, click next.
Select “AddNewSecurityGrouptoDropdown” workflow
On the Details tab, set the name to something like “Create new Production NSX Security Group“, because we’re going to create the security group and add its name to the “production”dropdown list. Click Next.
Set the Service Item Name
On the Blueprint Form tab, under the “Step” Form page (default), mouseover the text field labelled “Name of Custom Property Dictionary in vCAC/vRA”. Click the pencil “edit” icon when it appears.
Edit the Form Fields
Click the Constraints tab of the “Edit Form Field” window. On the Value field, select “Constant” and enter “VCNS.SecurityGroup.Names.Production” (or whatever suffix you used) for the Property Dictionary. Set the Visible value to “No” so it doesn’t show up. Click Submit on the Edit Form Field window.
Set the name of the Property Dictionary to be updated
Using the same method, set the Name of the Attribute appropriately and its visibility to no
Edit the “Value to be appended to the ValueList attribute” field. Set the label to “New Security Group Name“. Do not set a value or make this one invisible, we need the user to enter a value, submit to save.
Edit the vCACIaaSHost field – using the Constraints tab again– when setting the value, choose constant, then click Add by the green plus, to display a treeview, where you can choose your connection to the IaaS Server. Visible: No, submit to save.
Select connection to IaaS host
Edit the “NSX endpoint” field in the same way, selecting the NSX connection.
When done, all fields except “New Security Group Name” will have a value. Click Next.
On the Provisioned Resource tab, select “securityGroup [NSX Security Group]“. Click Add to save the service blueprint.
Repeat steps 5-15 for any other dropdown lists containing security groups; say “Non-Production” for instance
Highlight the Service Blueprint and click “Publish” to make the blueprint available for entitlements
Navigate to Administration, Services.
Add a new Service named “NSX Management” (for example) – I included a nifty image in the zip file
Under Catalog Items, click the “Create new Production NSX Security Group” item to edit it.
The Catalog item should inherit the Security Group icon from vCO, set its Service to “NSX Management”,click update to save.
Create or Edit an entitlement to include the new Service and/or catalog item.
Try it out, confirm that the Security Group was created in NSX, is visible in vCAC items and it name was added to the Property Dictionary
Configure Advanced Services – Import Security Group
This service allows you to make existing security groups visible as items in the vCAC Items view. Once this is done, we’ll add actions that allow you to add the security group to a dropdown list.
Click “Service Blueprints”, then the “Add” button.
Select the “GetNSXSecurityGroup” workflow, click Next
On the details tab, set the name to “Import NSX Security Group“, click Next
On the Blueprint form, set the “connection” to the NSX connection in vCO, then hide the field. Security Group Name will be a dropdown list of existing NSX Security Groups for the user to choose from. Click Next
On the Provisioned Resource tab, select “securityGroup [NSX Security Group]“. Click Add to save the service blueprint.
Just as before, publish the service blueprint, add it to a service and an entitlement.
Configure Advanced Services – Add Security Group to Dropdown list
With this service, we’ll let the user add the name of an existing Security Group to a drop down list. Unlike the first two, this is implemented as a Resource Action, meaning it’ll be executed against an existing item (a Security Group in this case)
Under Resource Actions, click “Add”
For the Workflow, select the “AddExistingSecurityGrouptoDropdown“, click Next
On the “Input Resource” tab, keep NSX Security Group, click Next
On the Details tab, set the Name to “Add Security Group to Production list” or similar, set the description, leave the Type options unchecked. click Next
Set Action Name and Description
On the Form tab, just like the first service blueprint, set the Property Dictionary and Attribute names as appropriate. VCNS.SecurityGroup.Names.production in my example, set visible to no on both.
Again, we’ll set the vCACIaaSHost to the connection to the Server and hide the field
Click Add to save the action.
Repeat steps 1-6 for each security group dropdown list (say “non-production” for instance)
Publish the action and add it to an entitlement
Add Action to Entitlement
Test by navigating toNSX under Items, highlight a Security group and Select “Add Security Group to…” from the Actions menu.
Yay! A Resource Action
Configure Advanced Services – Add VM to a Security Group
This service lets you add a provisioned VM to additional Security Groups. So, at provisioning-time, the VM is added to the Security Group selected by the user, but we may need to refine the security by adding that VM to additional Security Groups.
Under Resource Actions, click “Add“
For the Workflow, select the “AddVMtoSecurityGroup“, click Next
On the “Input Resource” tab, keep IaaS VC VirtualMachine, click Next
On the Details tab, set the name to “Add VM to a Security Group“, click Next
On the Form tab, set the connection Value to the NSX connection.
Leave the NSX Security Group field visible, click Add to save the action
Publish the action and add it to an entitlement
Test by selecting a machine under Items and “Add VM to a Security Group” from the Actions menu
VM Resource Action for Security Groups
You’ll be presented with the list of allNSX Security Groups to which you can add the selected VM
Select Security Group
Conclusion
This part of the series should help streamline the management of VMs and their membership in Security Groups. Obviously, items like removing a VM from a Security Group or even removing a Security Group are not included here. The NSX plugin is missing quite a bit of functionality available in the API, so those additional functions require significantly more configuration.
Thanks to John Dias for his information and examples posted here.
In this series, I’ll document how to automate the creation and (some of) the management of NSX security groups within NSX.
First, what’s the use case? Why is this interesting? Let’s assume that you’ve decided to use large “flat” networks instead of many small networks. One reason you may make that decision is because of the challenges with either having many blueprints (one per network!) or making changes to the workflows to reliably set the appropriate properties.
Background
In this solution, we’ll have to have vCAC 6.1 or vRealize Automation 6.2, NSX 6.x and vCenter/vRealize Orchestrator with the vCAC and NSX plugins installed and configured. We have two Logical Switches, one for Production and one for Non-Production. In addition, there’s a corresponding network profile and the business groups have reservations. Now, we have to ensure that there are security boundaries within the flat networks. We’ll accomplish this through Security Groups.
Caveats
We’ll create security groups and nod in the direction of security profiles, but will not be automating the creation of security profiles nor their assignment to the Security Group(s). That can be done by the security admins through the NSX interface or maybe later we’ll add that capability too. 😉
Procedure
Create Security Groups.
Open vSphere Web Client and navigate to Networking and Security, then Service Composer.
Click the “New Security Group” icon
Enter a Name and Description for your new Security Group and click Next
If you want to create rules for dynamic membership or include/exclude existing VMs, you can do so in the subsequent steps. Finish the wizard.
Repeat to create all of your security groups
Create Security Groups in NSX
Create Property Dictionaries invCAC/vRA.
Log into vCAC as an Infrastructure Admin and navigate to Infrastructure|Blueprints|Property Dictionary
Click “New Property Definition”, for the name enter “VCNS.SecurityGroup.Names.Production“. You can replace “Production” with a name of your choosing, so you can have multiple lists.
Select “DropDownList” as the control type and check to make it required, click the green check to save.
Create Property Dictionary
Click the “Edit” link in the Property Attributes column
Click “New Property Attribute”, select “ValueList” as the attribute type
Set the name to something appropriate, such as the same name as the Property Definition or “ValueList” or “SecurityGroups”
In the Value field, enter the names of the security groups you want included. Separate the group names by commas (no spaces). If you have groups whose names include spaces or commas, put them in quotes. Click the green check to save.
Repeat to create another property dictionary and attribute for the Non-Production list
Update Blueprints.
Edit your “production” blueprints by adding the “VCNS.SecurityGroup.Names.Production” custom property. Set the value to your default security group or leave it blank to require a selection. Be sure to check the “Prompt User” box. Click the green check to save.
Add Custom Property to Blueprint
Test
Submit a request for the affected blueprint and verify that the dropdown list of security groups looks like you expect it to. Remember, that unlike many other custom properties in vCAC (eg: Network Profiles), you CAN have multiple versions of this one and display different lists.
Dropdown list of Security Groups
After a VMis provisioned, verify in the vSphere Web Client that ithas been assigned to the expected security group
VM added to Security Group
Next
In the next parts of this series, I plan to address the problems of maintaining the dropdown list manually and having a single security group per machine.
I’ve fought with PKS and NSX-T for a month or so now. I’ll admit it: I did everything wrong, several times. One thing for certain, I know how NOT to configure it. So, now that I’ve finally gotten past my configuration issues, it makes sense to share the 
Brian Ragazzi 