Monthly Archives: February 2018

Configure An HTTP Internet Proxy In vRealize Network Insight

Well, we’re up to vRealize Network Insight 3.7 and still no GUI way of setting an internet proxy.  Usually you would configure an HTTP Internet proxy via the VAMI but that also doesn’t exist for reasons I don’t quite understand???  Never the less the process to configure an HTTP Internet proxy can be performed via the CLI easy enough.  Reasons why we might want to do this, apart from the obvious of gaining internet access where none exist without a proxy, is so we can check for software updates and connect to support.

The command we use is set-web-proxy

(cli) set-web-proxy -h
usage: set-web-proxy [-h] {show,enable,disable} …

set the web http proxy (for Internet access)

positional arguments:
show show current configured http proxy state
enable enable http proxy
disable disable http proxy

optional arguments:
-h, --help show this help message and exit

1. First thing we do is connect up to an interactive console session or SSH into our vRNI boxes with the consoleuser account.  The default password for consoleuser if you haven’t changed it is ark1nc0ns0l3

2. Type in set-web-proxy show

You will see something similar to below.

(cli) set-web-proxy show
Http proxy connection disabled

3. Next we set our HTTP proxy using set-web-proxy enable.  This will stop and start a few services but not cause any disruption the to running of vRNI.  Below is an example with a proxy address and port.

(cli) set-web-proxy enable --ip-fqdn vrni-platform.mydomain.local --port 3128
Stopping services
* Stopping DNS forwarder and DHCP server dnsmasq [ OK ]
nginx stop/waiting
launcher-service stop/waiting
* Starting DNS forwarder and DHCP server dnsmasq [ OK ]
Enabling http proxy connections…
Http proxy connection enabled
Connected to http proxy vrni-platform.mydomain.local:3128
* Stopping DNS forwarder and DHCP server dnsmasq [ OK ]
Starting services
* Starting DNS forwarder and DHCP server dnsmasq [ OK ]
nginx start/running, process 5337
launcher-service start/running, process 5415

4. We run set-web-proxy show again.

(cli) set-web-proxy show
Http proxy connection enabled
Connected to http proxy vrni-platform.mydomain.local:3128

5. Finally we can run show-connectivity-status

A bunch of network information will be returned along with connectivity status of a few URLs.

Upgrade connectivity status ( Passed
Support connectivity status ( Disabled
Registration connectivity status ( Passed

Web Proxy connectivity status: Passed

Over in the settings page of vRNI you should now see some green icons indicating Upgrade Server Reachable.


Offline Upgrade vRealize Network Insight

Earlier this week VMware release the latest update to vRealize Network Insight, version 3.7.  If you jumped on this new update as I did you might have been caught out by a bad build (  Upgrading to this version had a DNS issue that caused a communication issue between the Platform appliance and the Proxy appliance.  The version was quickly pulled and replaced a day later with a new and working build,  It’s unlikely that you will have this old build but before upgrading it’s best to check.

vRNI can be updated in two ways.  An Online upgrade via the GUI and an Offline upgrade via the CLI.  There are a few reasons why you might want to perform an Offline upgrade.  Cluster upgrades can only be performed via an Offline upgrade.  Your vRNI appliance might not have internet access.  Or like me you have configured a proxy server on your vRNI appliances but because vRNI wants to make your life difficult it doesn’t detect new updates.

The Offline upgrade can only be performed on version 3.5 or 3.6 and is very similar to previous upgrades.

1. Download the ZIP bundle from VMware.

2. Snapshot both your Platform and Proxy appliances or live life like a cowboy.

3. Copy (SCP) the ZIP bundle to both appliances (Platform & Proxy).

I had difficulties using WinSCP due to the limited console access given by the appliance so I used pscp.exe that comes with the Putty package.  The location to where you can copy the bundle to can also be a bit of a challenge.  I chose /home/consoleuser/downloads/ using user consoleuser.

Below is the command I ran from a PowerShell prompt from my Windows box.

PS C:\Program Files (x86)\PuTTY> .\pscp.exe -scp E:\temp\VMware-vRealize-Network-Insight. [email protected]:~/home/consoleuser/downloads/

4. SSH over to the Platform appliance with the user account consoleuser which has to be upgraded first. The default password for consoleuser in vRNI is ark1nc0ns0l3

5. Run the package-installer command to upgrade the appliance.

Below is an example of the command I ran.

package-installer upgrade --name /home/consoleuser/downloads/VMware-vRealize-Network-Insight.

The upgrade process can take a while so be patient.  A successful upgrade should look similar to below.

login as: consoleuser
[email protected]’s password:
vRealize Network Insight Command Line Interface
(cli) package-installer upgrade --name /home/consoleuser/downloads/VMware-vRealize-Network-Insight.
Do you want to continue with upgrade? (y/n) y
It will take some time…
Successfully upgraded

6. SSH over to the Proxy appliance now with the same user account consoleuser.

7. Run the same command as on the Platform appliance.

package-installer upgrade --name /home/consoleuser/downloads/VMware-vRealize-Network-Insight.

As with the Platform upgrade it will take some time and the output after the upgrade should look the same

8. (Optional) Run show-version and confirm you are running the latest version build on each appliance.

That’s all there is to it.  Stopping and Starting services aren’t necessary.  As with no need to reboot appliances.

You can now open up a web browser and login to your upgraded vRNI platform appliance. Check that everything looks over in settings.