Month: September 2016

Set Edge Default Route / Default Gateway using vRealize Orchestrator


As part of some workflow I am building for a customer, I need to automate assigning the default route (default gateway) for an vCNS Edge appliance, using vRealize Orchestrator.


The provided NSXDefaultRoute, which can be used with NSXEdgeManager.setDefaultRoute() per the documentation, has read-only properties and the NSX Orchestrator Plugin 1.0.4 provides no further documentation to my knowledge on how to use this scripting object:


There are two accessors available as part of the NSXDefaultRoute scripting object.  To my knowledge, these are not documented.

  • NSXDefaultRoute.setvNicIndex(string vnicindex)
  • NSXDefaultRoute.setGatewayIpAddress(string ip)

Note, there is no accessor for MTU, although as shown below that is an option in the default gateway config.

This example code works with vRealize Automation 7.1 and the embedded Orchestrator service.

Setup a new workflow with these variables as input, and the below code in a scripting task, and it should work for you too.

Input Parameters

  • Variable nsx is a NSX:Connection object specifying my vCNS Manager in vRO inventory
  • Variable edgeId is a string object specifying the edge objectId, such as edge-28

Here’s the results after running this code

FitBit HR Data Raw

Excited by the Fitbit Charge 2’s second by second heart rate data, but frustrated by the lack of an easy export function for accessing this data in raw form, I rolled a very quick Node.js app to give me CSV-formatted raw data from Fitbit.  Note that to access the APIs I am using, you either need special approval, or a Personal application registered on the Fitbit developer portal.

It looks like this, after the app is initially authorized:

Clicking the “Get HR for Today” link gives me this raw CSV:

And so on.

Here’s the bare bones code, posted as a gist on GitHub:

vRealize Automation 7.0 to 7.1 Upgrade the SQL Database Manually



Following the installation instructions for manual SQL database upgrade using vRealize Automation 7.0 to 7.1, the vRA VAMI installation download page didn’t have a link for, only  I manually created the path https://<vra>:5480/installers/ and continued with the upgrade.

Problem Details

Doing a manual update of the vRealize Automation IaaS MS SQL database, the vRealize 7.0 to 7.1 upgrade guide has this instruction:

I thought I followed the directions, but had errors and was missing the key utility DBUpgrade.exe in the ZIP file.  I eventually logged on the vRA server, found the file in /opt/vmware/share/htdocs/service/iaas/ to confirm it was there.  Only then did I realize I had been downloading the wrong file.  Apparently I do not have a link to download the database upgrade scripts on the installation interface.


Clearly, the file exists:

So I used the URL https://<vRA-appliance>:5480/installer/ and followed the install instructions from there.

Recent Posts



GiottoPress by Enrique Chavez