Monthly Archives: December 2015

vRealize Operations for Horizon View 6.2 upgrade

On 8 Dec, the Horizon team released an updated version of vRealize Operations for Horizon. I’ve worked with customers a few times on this product, and it certainly helps both the Horizon admin (EUC team) and vSphere admin (Platform team) to collaborate. That last one is important. Horizon is tied to vSphere, that you cannot manage it without having end to end visibility into the platform.

There are many articles on a fresh installation, so I will cover upgrade here. Please read the Upgrade section of the Release Notes, as there are things to know. After that, read the Upgrade section of the manual.


Other than what the manual say, take note of the following:

  • Admin Access to Horizon View Connection Server.
  • Root access to vRealize Operations SuSE console. You will either need to enable SSH, or have VM Console access in vCenter.
  • Snapshot access to vCenter. You should take a snapshot before making any changes. You need to snapshot View Connection Server and vRealize Ops.

Step 1: Stop the Broker Agent services

Go to Horizon View Connection Server, and manually stop the service. You have to click it 2x, as it would go from Running to Stop Pending first.


Step 2: Update the solution

Other bloggers have provided good write up, so review this or this for a step by step instruction. I am not going to uninstall existing version since the manual implies that we install on top of existing instance. Also, if you uninstall, you will lose all your customisation and metrics.


To install on top of existing instance, you need to tick the 2 checkboxes, as shown below.


When you do that, you got a warning that it will replace existing changes. This is why I normally clone them, and leave the original intact. For example, if it is an alert, I’d also disable the original alert so I’m not double alerted.

Continue with the installation.


When it’s completed, the old solution is replaced. You can tell that the new build number is now shown.


The manual said to reboot. I’d wait until I modify the firewall port so it’s done together.

Next. Configure licensing information for the vRealize Operations for Horizon solution. Notice that there are 2 license keys required. One for vRealize, one for the Horizon solution. I think this step is actually optional, as you’ve got the existing license configured already.

5 license

Step 2: Update firewall ports

The firewall ports changed. You need to enable the port numbers 3099, 3100, and 3101.

  1. Login as root (the user Admin cannot login anyway)
  2. Edit the /opt/vmware/etc/vmware-vcops-firewall.conf file .
  3. Add the line: TCPPORTS=”$TCPPORTS 3099:3101″ after TCPPORTS=”$TCPPORTS 3091:3095″ . See below for example


Either do the next 2 steps, or just rebooted the VM. As the manual said it needs a reboot after the Solution was installed, I rebooted. It’s easier than typing all these long commands 🙂

  1. Restart the firewall: /etc/init.d/vmware-vcops-firewall restart
  2. Check the status of the firewall: /etc/init.d/vmware-vcops-firewall status

Step 3: Modify TLS

TLS 1.2 is enforced by default in version 6.2. The Adapter cannot communicate with older desktop Agents running with TLS 1.0, which is used in 6.1. Bin Guo from R&D advised me that you don’t need to upgrade them if you continue to use the TLS 1.0. But you must enable TLS1.0 settings on adapter configuration. To do that, add the enforcesslprotocols = false line in the screenshot below to the  /usr/lib/vmware-vcops/user/plugins/inbound/V4V_adapter3/work/ file


Horizon Adapter in View Connection Server has to be restarted.

If you want to use TLS 1.2, you can upgrade the desktop agent independently, or update the whole Horizon View to 6.2.1 (View 6.2.1 disable TLS 1.0 too)

Broker Agent and Horizon Adapter instance pairing might be required.

Step 4: Update the Broker Agent

After the solution is licensed, you must install and configure the new version of broker agent. If you are not familiar, follow this or this for step by step. BTW, you only install it on 1 View CS if you have pairs, not all members. Also, do not install in View Security Server. This is stated in the manual.

If your broker agent is 6.1, you do not have to uninstall. If you are using older version, uninstall it. The 6.2 Broker Agent now requires MS .Net 4.5. It will stop if you do not have one.


During the Broker Agent upgrade process, this is what happened:

  • Broker agent 6.1 service is stopped
  • Its configuration is preserved. This includes data such as Horizon Credentials and Events DB configurations. Nice! No need to re-enter all those passwords
  • Broker agent 6.1 is uninstalled
  • Broker Agent 6.2 is installed.

The 6.2 sports a different UI, but the information that it asks is the same. Take note the version number (6.2.0) and build number. The first stage is to re-pair the adapters. This would fail if you did not add the firewall ports earlier.


In case of upgrade, the Broker Agent service is not started automatically. You need to click the Start button above.

And that’s all you need. If you need to troubleshoot, you can get the log of …..

  • the Broker Agent at C:/ProgramData/VMware/vCenter Operations for View/logs
  • the individual VDI Desktop at C:\ProgramData\VMware\VDM\logs and locate the desktop agent log files. The agent log file names begin with v4v-.

BTW, there is a user guide that was introduced in this blog. The blog shows you the link to the actual guide. For your convenience, here is the actual PDF guide.

VMware NSX 6.2.1 upgrade

Please read the preparation before upgrading. The official manual states the upgrade procedure is as follows:

  1. NSX Manager
  2. NSX Controller
  3. Host Clusters
  4. NSX Edge
  5. Guest Introspection

There is only 1 download, as everything is contained within the Manager.


Stage 1: NSX Manager Upgrade

To update the NSX Manager, login to its UI as Admin. Click on the Upgrade button.


Choose the file that you’ve downloaded earlier.


It will upload the file. It should only take a few minutes. If it’s taking >10 minutes, just cancel it and repeat. Once done, it will show you the following screenshot.


Notice it gives you the choice to enable SSH. Click on Upgrade, and the following progress window appears. Again, this should only take a few minutes.


Once done, it may log you out (it could be due to time out). Login, and you will see 6.2.1 as the version.


Repeat the same step for all your NSX Managers instances. They are upgraded independently.

Stage 2: Controller Upgrade

The next step is upgrading the Controller. What a pleasant surprise! The official manual has screenshot! Please read it first.

Login as the NSX Administrator. That’s the ID you used to deploy the NSX Manager. I normally maintain a separation between the Network admin and the Server admin, so I use different accounts in the lab so I can experience what it will be in actual environment. As you can see here, I login as Server Admin (vCenter) and I do not even see the Manager.


I normally use 2 browsers. Here, I login as the NSX Manager. Can you spot that Upgrade Available button? Essentially, the controller upgrade is a 1-click operation. The Manager will automatically detect that there is a new version, and provide an upgrade button. Thank you Ray and team!

The VMware ASEAN lab has 2 NSX Managers in primary-secondary setup. You do not have to upgrade the secondary controller. Notice the status is Imported Controller Cluster.


Don’t worry if you click the button accidentally. There is a prompt, defaulted to No 🙂


I clicked Yes, and you can see the status changed to In progress.

NSX 10

The entire process takes around minutes, not hours. Along the way, you see update such as below

NSX 11

When it is done, it will show the software version. Notice it has upgraded the Secondary Manager’ Controllers too.

NSX 12

I notice that vCenter recent tasks do not show any activity. I was thinking that VM reboot would show up in the vCenter. If you know why, let me know.

You might notice that the Peers column has issue. It’s showing red, and Controller 3 has no status. Just wait for a few minutes. It will look like this after a while

NSX 123

Stage 3: VMkernel VIB Upgrade on Cluster

Once the controller is upgraded, your next step is to upgrade the cluster. Once again, the manual has screenshots, so I do not have to repeat it. Please take note that ESXi is rebooted.

NSX 13

Again, clicking the Upgrade available button will prompt a dialog box, giving you a chance to confirm. Once you confirm, the UI will show the progress, as shown below.

NSX 15

This time around, vCenter recent tasks shows the progress.

NSX 14

There seems to be 2 pair of Scan + Uninstall for each host. I think this is installing the VIB.

NSX 16

I hit some issue due to my DRS setting, so I will need to spend some time on it. The manual said that ” If hosts require manual intervention to enter maintenance mode (for example, due to HA requirements or DRS rules), the upgrade process stops and the cluster Installation Status displays Not Ready

NSX 17

That’s what I hit, so I will need to fix that first. I manually entered the host into maintenance mode. Once done, I click the upgrade again. I did it on one of the host first, and you can see the status is now showing 6.2.1

NSX 21

I continued on the remaining of the hosts in the cluster.

NSX 34

Stage 4: NSX Edges and Router Upgrade

Once the hosts are upgraded, the next stage is to upgrade the NSX Edge (if you have any). Once again, the manual has the screenshot and it’s a pretty straight forward process. The manual said that “NSX Edges can be upgraded without any dependency on the NSX Controller cluster or host cluster upgrades. You can upgrade an NSX Edge even if you have not yet upgraded the NSX Controller cluster or host clusters.”

NSX 31

You get a warning that there will be service disruption, that’s why it’s important to know the operational impact of the upgrade.

NSX 32

Here is what the activities look like in vCenter recent tasks.

NSX 35

The upgrade was fast, each was less than a minute. The result was below. Notice the version is now 6.2.1

NSX 36

That wraps up the basic upgrade steps of NSX.

NSX Monitoring with Log Insight

BTW, it’s a good practice to have NSX logs analysed. As you can see below, Log Insight captures the errors that I encountered during the upgrade.

NSX 40

Roie Ben Haim, a PSO Consultant in Israel, brought up to me (Thanks Roie!) that NSX 6.2.1 release notes has the following info:

NSX 6.2 does not support Log Insight reporting
Due to an incompatibility in the vRealize Content Pack for NSX, NSX 6.2 does not support vRealize Log Insight Reporting.

It has no workaround.

I’m not sure what “reporting” means. As you can see in the above screenshot, the dashboards got populated. The screenshot below shows that both NSX Managers are sending syslog regularly. In fact, hundreds of syslog messages.

NSX 42

Log Insight has specific knowledge on NSX, and below is one such example.

NSX 41

Below is one of the out of the box dashboard provided by the Content Pack.


BTW, if you want to know how to enable syslog in NSX, this is a great how-to by Steven.

vRealize Operations 6.1 Patch

If you are using vRealize Operations 6.1, there is a patch release. The KB article states that it fixes a number of issues. Since it’s featured prominently in the Release Notes, I thought I’d share how to patch it.

You might think that a patch is a small file, especially if you are used to the small size of the pak files. In this case, the pak file is >1 GB. The patch requires you to be on the 6.1 release. It is not for 6.0 release. Another word, you have to upgrade from 6.0 to 6.1, then apply the patch. You cannot just go straight from 6.0 to this build 3294016.

The first thing you need is to download it. You will find it in the same place where you download vRealize Operations. What you need to is to scroll down, until you see a small heading called Hot Patch.  You can see is on the following screenshot. Yeah, I know, it’s kinda small.

vR Ops patch

From there, what you download naturally depends on what you install. I normally use the appliance, as it’s easier to deploy and manage. I also do not use Windows-based Remote Collector (RC), so the above is what I need.

You can click on the Read More link, and it will expand and show the following. Notice the build number.

vR Ops patch 2

From here, the process is similar to the upgrade from 6.0 to 6.1, which I’ve documented here. So the following series of screenshots is just in case you need to see the actual 6.1 screenshots

vR Ops patch 3

vR Ops patch 4

vR Ops patch 5

vR Ops patch 6

vR Ops patch 61

Once it’s completed, leave the /admin URL and log in back to the main URL.

BTW, if you click the About link at the top, you may not see the new build number reflected in the pop up window. In my case, it’s showing the original build number.

vR Ops patch 7