VMware vRealize Operation 6.7 upgrade experience

I have upgraded our vRealize Operation 6.6.1 test environment to version 6.7. Please let me share my experience about the test.

Our test environment consists of one Remote Connector and one Data node.

First of all, I checked this blog articles:



vRealize Operations Upgrade Assessment Tool

From my.vmware.com site (under 6.7 download page) you can download vRealize Operations Upgrade Assessment Tool. “APUAT-”

Install was very easy, just install pak file on the admin page. Install created a log file automatically. Download it, and browse to \apuat-data\report\ folder, and open the index.html file. As you can red in the VMware’s blog article, you are able to check your dashes, widgets and so on. Fortunately, I didn’t have to worry about metrics, tools find only one matric witch should be a problem.


vRealize Operations Upgrade Assessment Tool
vRealize Operations Upgrade Assessment Tool

I downloaded OS (vRealize_Operations_Manager-VA-OS- and VA (vRealize_Operations_Manager-VA- upgrade pak files, from my.vmware.com site.

vRealize Operation OS update process

I opened vRealize Operation’s admin page (“https://FQDNorIP/admin”) on System Status page hit “TAKE OFFLINE” button. Wait a few minutes.

Take Offline vRealize
Take Offline vRealize

After the nodes went to offline mode, switch to vSphere client and take snapshot from VM-s (deselect: Snapshot the virtual machine’s memory).


Then go back vRealize Operation admin page and click “System Updates” link. Click “INSTALL A SOFTWARE UPDATE” blue icon and browse OS upgrade pak file (vRealize_Operations_Manager-VA-OS- Select Install the PAK file is already to upload and install option. Then click “UPLOAD” button.


Wait approximately 5-10 minutes, and you will see similar the picture below. The PAK file signature is valid. Next.


Accept EULA, and go next.


Read update information and click Next.


Click “INSTALL” button.

You see the OS update process on the screen.


Click the icon next to Status column for details.


Wait 30-45 min for the end of the process. If you did everything right you will see a similar screen on your monitor. Status Completed. Don’t worry, under the update process admin page will disappear. Be patient, and hit the refresh button, the page will be returned. You have to relogin.


vRealize Operation VA update process

Ok, now we can upgrade vRealize Operation, the OS upgrade process is done. Similar steps as OS upgrade, except you can browse the vRealize_Operations_Manager-VA- file and you can select “Reset Default Content…” option. After you fill the box, a warning message will appear. Read it and select I understood button 🙂



The admin page under this upgrade process will disappear too, don’t panic.


It’s time to login to the new vRealize Operation Manager.



The OS and vRealize Operation upgrade process is done. Now I go and discover new features in vRealize Operation 6.7 🙂

If U have any question, don’t hesitate to contact me.

vRealize Orchestrator Management Pack for vRealize Operations

I have red an interesting blog article from John Dias about VMware vRealize Operation Manager and vRealize Orchestrator integration capability. Link below.


John shows us an example of an alert recommendation that launches a vRO workflow to decommission a host. It is amazing, we are able to create a workflow to alerts. The operator just pushes the “RUN ACTION” button and the pre-implemented flow will guide her. I like it! 🙂


Log Analytics by VMware Log Insight – VMUG presentation

I would like to share my VMUG presentation about VMware Log Insight.

Advice for installation:

  • Install one medium size appliance, use different IP wich U use to cluster
  • Use Eager Zeroed DS because of avoiding performance issues
  • End of configuration don’t configure vSphere hosts
  • Create VIP despite of you don’t want a cluster!!!
  • Use DNS name resolution
  • Now U can integrate Log Insight with your vSphere environment

If you miss creating VIP address for Log Insight, and you integrate it with your vSphere environment, the IP address of Log Insight node will write to Syslog.global.logHost value. If you want to change your IP of Log Insight, or you want to create cluster environment (eg.: scaling) you should change log value on every vSphere host.

In case of you rerun vSphere integration process in Log Insight, it does not solve your problem, because of Log Insight will add the new address to value (don’t overwrite it).

Yes, I know, you can change it by script, but I think it is a better solution, isn’t it? 🙂

Sizing: http://www.vmware.com/go/loginsight/calculator

I’m planning to create a new article series, where I will share more details about the install process and content packs integration. I have created more than 100+ page documentation in this topic under introduction. It is not finished yet! 🙂


vThing has created a great new blog post, you can reach details of the event on this link:

If you have any question, don’t hesitate to contact me!

Change vRealize Operation Agent’s log level and file size

As I promised in my previous blog article, I will show you how do you can change vRealize Operation Manager Agent’s log level and file size limit. If you want to debug a problem these two changes are helpful because you can store log information for a longer time than default 5Mb. Ok, let’s go.

The default location of bin files of the agent is “C:\ep-agent\conf\” on Windows environment. Under this folder, you will find “agent.properties” file. Open it by Notepad or your favorite editor.



Search for “agent.logLevel” config, and change from INFO to DEBUG. Save the file and restart agent’s service. Ok, you will see more details in the log file, but the file size will grow fast, and if it will be higher then 5Mb the agent overwrite the old data. You can prevent it, so change the file size limit. The file size setting is very close to log level settings.

Change the value (in KB) end of the line, and save the file, and restart agent’s service.



If you want to know more about agent property, click the link below:


vRealize Log Insight alert integrate with Operation Manager

First of all, you can install and configure Veeam Backup and Replication content pack in vRealize Log Insight. Follow instructions of this document.


  • In Log Insight jump to Content Packs / Veeam Backup & Replication / Alerts menu
  • Click “vbr – Backup job failed”


The content pack will create a query of failed backups.

  • Change the name of alert as you wish or leave default
  • You can edit Description and Recommendation
  • Fill “Sent to vRealize Operation Manager” checkbox
  • Hit the “Select…” button and select your Veeam Backup&Replication server (VM or Windows layer)
  • Set criticality to Critical
  • Check Auto Cancel option


  • Click “Send test alert” button
  • Save to my alerts

If you do everything right you will see the test alert in vRealize Operation Manager (wait 5 minutes before you start troubleshooting)


You can see the alert on VM or Windows layer dash or if you select Alert button, you will see the alert under it.



The alert comes as Notification event so you can create Notification settings under Alerts / Notification settings if you want to receive an e-mail alert.


vmware failed to read header on stream tcp n7vmacore15systemexceptione connection reset by peer

As I mentioned we have introduced VMware Log Insight application. I really like this VMware product, but the others too 🙂 Simple and it is working well.


Today I find this error message on our one host:

Hostd: error hostd[66282B70] [Originator@6876 sub=SoapAdapter.HTTPService.HttpConnection] Failed to read header on stream <io_obj p:0x64b7765c, h:42, <TCP ‘’>, <TCP ‘’>>: N7Vmacore15SystemExceptionE(Connection reset by peer)

I started to Google it, and I find this VMware Kb Article:


So this is known issue and no solution yet.

ICMP ping issue by Windows base End Point Operations Agent

As you know vRealize Operation Manager can monitor remote devices by ICMP check. It is a simple checking method, we use it to monitor at basic level, our remote routers or switches.

Implementation process:

  1. Go Environment / All Objects / EP OPS Adapter / Remote Cheks Word
  2. From Actions menu select “Monitor this object remotely”
    • Add Display nama E.g.: WAN-1
    • Monitored from select your Agent
    • Under Check Method select ICMP check
    • Hostname: IP address of device
  3. Under Advanced settings you can change “sotimeout” and “Collection Interval” (we use one minute)
  4. Click OK

Under Environment / All Objects / EP OPS Adapter / ICMP Check tree you will find all your ICMP checked objects, and you can select one of them for details or All Metrics data.

Now, you are able to create an Alert, base on resource availability state. Yes, but we received lots of alert from vROps, becouse the resources wasn’t available many times. We tried rise up sotimeout. Not worked.

We changed Agent log level to Debug and we saw many of this messages.

26-09-2017 20:23:36,043 CEST DEBUG [pool-1-thread-11] [Collector] name=ICMP Check, thread=pool-1-thread-11, result=Tue Sep 26 20:23:36 CEST 2017 (/192.168.xxx.xxx) null values={Availability=0.0, ResponseTime=19969.0}

(In my next Article I will show you how you can change EP OPS Agent’s log level and file size.)


We opened a new case at GSS (VMware Global Service Support) about this problem, but fortunetly in the maintime (under weeks – waited for GSS) we find a Release Note for vRealize Operation Manager 6.2. The subscription in this note looks like very similar as our problem 🙂

No data returned when running ICMP check
When attempting to run an ICMP check for remote monitoring from an Agent running on a Windows platform, no data is returned.
Workaround: Do not use ICMP checking from an agent that is deployed on a Windows platform.

Link: http://pubs.vmware.com/Release_Notes/en/vrops/62/vrops-62-release-notes.html

We changed the Agent from Windows base OS to Linux OS, and in the last weeks we didn’t revecive fals alerts. I’m really sad becouse we use vRealize Operation 6.6.1 and the problem, wich was discovered in 6.2,  is still exists in the latest release.