NSX-vRO Plug-In 1.2.0 Release Notes

NSX-vRO Plugin 1.2.0 | 10 August 2017 | Build 6004830

What's in the Release Notes

The release notes cover the following topics:

What's New

The NSX-vRO Plug-In 1.2.0 includes resolved issues and new capabilities with the addition of the following new workflow functions:

  • Load Balancer as a Service (LBaaS), which supports creating and updating of all Edge Load Balancer features, such as monitors, application profiles, application rules, pools and virtual servers.

  • Standalone workflow to add or remove members from Load Balancer pools.

  • Get application profiles, rules, monitors and pools for a specific load balancer virtual server.

  • Workflows to add and remove security tags from a security group.

  • Workflows to create, read, update and delete operations for NSX Layer 3 firewall.

  • Workflow to delete rules from NSX Layer 3 firewall.

  • Create, read, update and delete edge parameters such as edge interfaces, appliance sizing, edge default gateway settings, edge CLI settings, edge syslog and edge high availability.

  • Standalone workflow for re-deploying edge.

System Requirements

  • Verify that you are running a vRealize Orchestrator instance.

  • Verify that you have credentials for an account with permission to install vRealize Orchestrator plug-ins and to authenticate through vCenter Single Sign-On.

  • Verify that you have installed vRealize Orchestrator Client and that you can log in with Administrator credentials.

Installation

See “Upgrade Procedure” if you are upgrading the plug-in from a previous release.

 

  • Download the plug-in file to a location accessible from the vRealize Orchestrator server. The plug-in installer filename is o11nplugin-nsx-1.2.0.vmoapp. The plug-in installation file for networking and security is available from the VMware product download site at http://vmware.com/web/vmware/downloads under the VMware NSX link.

  • Open a browser and launch the vRealize Orchestrator Configuration interface. An example of the URL format is https://orchestrator_server.com:8283/vco-controlcenter.

  • Click the Plug-ins item in the left pane and scroll down to the Install new plug-in section.

  • In the Plug-in file text box, browse to the plug-in installer file and click Upload and install. The file must be in .vmoapp format.

  • Accept the license agreement in the Install a plug-in pane, when prompted.

  • Go to the Plug-ins section and confirm that NSX 1.2.0.XXXXXXX is listed, where XXXXXXX is the build number.

  • Restart the vRealize Orchestrator Server service.

  • Relaunch the vRealize Orchestrator Configuration interface.

  • Click the Plug-ins item and verify that the status changed to Installation OK.

Upgrade Procedure

If you have a vRealize Orchestrator 7.x instance running with the NSX-vRO plug-in 1.0.5, 1.1.0 installed, and you have credentials for an account with permission to install vRealize Orchestrator plug-ins and to authenticate through vCenter Single Sign-On, you can upgrade to the new NSX-vRO plug-in 1.2.0 as described below:

  1. Download the plug-in file to a location accessible from the vRealize Orchestrator server. The plug-in installer filename is o11nplugin-nsx-1.2.0.vmoapp. The plug-in installation file for networking and security is available from the VMware product download site at http://vmware.com/web/vmware/downloads under the VMware NSX link.

  2. Open a browser and launch the vRealize Orchestrator Configuration interface. An example of the URL format is <https://orchestrator_server.com:8283/vco-controlcenter>.

  3. Go to the Plug-ins section and confirm that NSX 1.1.0.4968437 is listed, where 4968437 is the build number for NSX-vRO plug-in 1.1.0.

  4. In the Plug-in file text box, browse to the plug-in installer file and then click Upload and install. The file must be in .vmoapp format.

  5. Accept the license agreement in the Install a plug-in pane when prompted.

  6. The status message “NSX (1.2.0 build XXXXXXX) Plug-in with same name was already installed (1.1.0 build 4968437) : overwriting existing plug-in,” displays, which confirms that the NSX-vRO plug-in has been upgraded to version 1.2.0.

  7. Restart the vRealize Orchestrator Server service.

  8. Relaunch the vRealize Orchestrator Configuration interface.

  9. Click the Plug-ins item and verify that the status changed to “Installation OK.”

These instructions assume that NSX-vRO plug-in 1.1.0 is installed and is to be upgraded to NSX-vRO plug-in 1.2.0. Similar steps must be followed for upgrading to NSX-vRO plug-in 1.2.0 from any other plug-in version that supports  upgrades.

Resolved Issues

  • Fixed Issue 1807926: NSXAdvancedEdgeLBManager class does not implement get methods for LB Virtual Server(s)

    NSXAdvancedEdgeLBManager class does not implement get methods for LB Virtual Server(s)

  • Fixed Issue 1819245: Registering an NSX endpoint in vRO with a user different than "admin" returns error

    Registering an NSX endpoint in vRO with a user different than "admin" returns error

  • Fixed Issue 1825737: [Embedded vRO]vRA Converged Blueprint Provisioning fails with vRO Workflow "vshield.edge.Firewall.dto.trinity.FirewallConfigTrinityDto"

    [Embedded vRO]vRA Converged Blueprint Provisioning fails with vRO Workflow "vshield.edge.Firewall.dto.trinity.FirewallConfigTrinityDto"

  • Fixed Issue 1836778: Add/Delete Members in Load Balancer Pool failing for Pool with no monitors added

    Add/Delete Members in Load Balancer Pool failing for Pool with no monitors added

  • Fixed Issue 1839829: Workflow "Configure edge CLI settings" failed due to type converting error

    Workflow "Configure edge CLI settings" failed due to type converting error

  • Fixed Issue 1839835: Workflow "Configure Edge Appliance" failed due to type converting error

    Workflow "Configure Edge Appliance" failed due to type converting error

  • Fixed Issue 1840680: Edge is in "Undeployed" status after "Create Edge" completed

    Edge is in "Undeployed" status after "Create Edge" completed

  • Fixed Issue 1843541: Failed to retrieve Edge object

    Failed to retrieve Edge object

  • Fixed Issue 1844111: Add an option to use vNIC index in "Configure Default Gateway" workflow

    Add an option to use vNIC index in "Configure Default Gateway" workflow

  • Fixed Issue 1845311: Workflow "Create logical switch" failed due to java.lang.NullPointerException

    Workflow "Create logical switch" failed due to java.lang.NullPointerException

  • Fixed Issue 1848113: Workflow "Connect logical switch to router" failed due to converting type error

    Workflow "Connect logical switch to router" failed due to converting type error

  • Fixed Issue 1848123: Workflow "Delete Rules From Firewall Section" failed to delete 2 rules

    Workflow "Delete Rules From Firewall Section" failed to delete 2 rules

  • Fixed Issue 1856219: Input value for VDNSCOPE value fetches null value for NSX-vRO plug-in

    Input value for VDNSCOPE value fetches null value for NSX-vRO plug-in

  • Fixed Issue 1860023: Need to add Firewall rule for Virtual Server in Edge Firewall

    Need to add Firewall rule for Virtual Server in Edge Firewall

  • Fixed Issue 1886763: Update Firewall Layer3 Section workflow does not update/change Position of Firewall Layer3 Section in NSX

    Update Firewall Layer3 Section workflow does not update/change Position of Firewall Layer3 Section in NSX

  • Fixed Issue 1889319: Not able to configure Syslog, HA and Default Route from Compose Edge Workflow

    Not able to configure Syslog, HA and Default Route from Compose Edge Workflow

  • Fixed Issue 1890801: Workflow "Apply security policy on security group" failed due to java.lang.NullPointerException

    Workflow "Apply security policy on security group" failed due to java.lang.NullPointerException

  • Fixed Issue 1899560: Quick Workflow: Add-Delete Members from LB Pool not working for Ip Address inputs for Members in case of Deletion

    Quick Workflow: Add-Delete Members from LB Pool not working for Ip Address inputs for Members in case of Deletion

  • Fixed Issue 1912230: Get Nat rules workflow fails for Edge with No Nat rules configured

    Get Nat rules workflow fails for Edge with No Nat rules configured