Home > Blogs > VMware TAM Blog > Category Archives: Support

Category Archives: Support

vROPS 6.1 and the New End Point Operations Monitoring Feature

Vegard-bw2By Vegard Sagbakken

In the 6.1 release of vRealize Operations, VMware merged the Hyperic Monitoring solutions into vROPS. This makes it a lot easier to get a full holistic view through the vROPS management interface all the way down to services, processes and the application layer.

To use the OS Monitoring feature described here you need vRealize Operations Advanced licensing.

Currently we support the following OSs with this End Point Operations agent:

Operating System

Processor Architecture


Scaling Considerations

Red Hat Enterprise Linux (RHEL) 5.x, 6.x, 7.x x86_64, x86_32 Oracle Java SE7
CentOS 5.x, 6.x, 7.x x86_64, x86_32 Oracle Java SE7
SUSE Enterprise Linux (SLES) 11.x, 12.x x86_64 Oracle Java SE7
Windows 2003 Server R2 x86_64, x64_32 Oracle Java SE7
Windows 2008 Server, 2008 Server R2 x86_64, x64_32 Oracle Java SE7
Windows 2012 Server, 2012 Server R2 x86_64, x64_32 Oracle Java SE7
Solaris 10, or higher x86_64, x86_32 Oracle Java SE7
HP-UX 11.11 or higher PA-RISC Oracle Java SE7
AIX 6.1, 7.1 Power PC IBM Java SE7
Ubuntu 10.11 x86_64, x86_32 Oracle Java SE7 For development environments only.

Here is an excellent example of what you can do with this dashboard; it shows the status of a Windows vCenter Server and the status of all services running. This gives your operations team a great way of making sure all vCenter services are up and running so they can take action on any anomalies early before they escalate into bigger issues. This example was created by Peter Tymbel, Sr.Consultant, PSO, VMware.

Some of my colleagues at VMware have already documented the installation and use of this new functionality within vROPS. Please see the following blogs to get started with this new functionality, and don´t forget to use the official documentation as well.

vROPS 6.1 – EPO Agents Installation Guide


vRealize Operations 6.1 End Point with existing JRE


vROPS 6.1 – How to Monitor any Windows Service


vRealize Operations 6.1 End Point: how to add metrics


If you would like to dig further into this I suggest you head over to the VMworld Hands-On Labs and launch, “HOL-SDC-1601 Cloud Management with vRealize Operations Insight.” Here you can play around in a pre-installed environment and look at how the End Point Operations agents are working.

Vegard Sagbakken is a Senior Technical Account Manager working out of Oslo, Norway. He currently holds multiple VMware certifications, VCP 2-6 and VCAP-DCD 4-5

Are You a Type 1 or Type 2 NSX Customer?

Curtis-Badge-PhotoBy Curtis Miller

As a VMware NSX TAM—one who compliments standard TAMs and specializes in VMware NSX technology—I see two general types of NSX customers:

  • Type 1: A company that brings in a consultant to implement NSX
  • Type 2: A company that wants to implement NSX on its own

In either case, an NSX TAM provides support and guidance to help ensure the success of the installation. But that’s just the beginning of the value we provide.

During a consultant-led (Type 1) deployment, companies often find it challenging to get the information needed to move effectively into the operations stage. Operational success requires that employees in every functional area in the organization (i.e., developers, users, and their own customers, if they’re a service provider) learn how to consume NSX – not just the IT department. NSX TAMs make sure that happens, paving the way to a seamless transition to operations.

During an internally-led (Type 2) deployment, NSX TAMs provide a host of important information and coordination support. For example, we help interface between the company and their implementation-related vendors (e.g., firewall, switch, or router vendors); of course, we also help coordinate interactions with VMware and its third-party partners.

Helping both types of companies run NSX after implementation is perhaps an NSX TAM’s most important role. This kind of ‘day 2’ support includes expert help with troubleshooting, patching and upgrading (of NSX and third-party functionality such as security, firewalling and automation), getting customer-needed features added to future versions of NSX, and much more.

Bottom line: NSX TAMs exist to help you reduce risk, maximize the value of your NSX investment, and meet and exceed the goals you set when you chose NSX.

Click here to learn more about VMware TAM services.

Curtis Miller is a Technical Account Manager for VMware


VMworld 2015: Day 3 –TAM Customer Central Sessions

It’s tough to believe that VMworld US 2015 has nearly come to a close. Tonight, we’ll celebrate our experience with our customers at AT&T Park during the Customer Appreciation Event. Throughout the conference, we’ve had some great sessions and Wednesday was no exception. Today we heard from experts regarding the newly announced EVO SDDC solution, as well as discussed current and future options for vCenter High Availability.

EVO SDDC Best Practices

Presented by Anil Kapur, EVO SDDC Product Management and Jason Lochhead, EVO SDDC CTO, this session focused on the processes and automated best practice configurations that are built into EVO SDDC. Anil presented to a small, but very engaged group, and collected feedback from the audience throughout the presentation that will be used to prioritize the next round of automated services.

Anil highlighted the major challenges for customers implementing SDDC as the up-front setup, the bring-up and lifecycle management. The problem is that configuring a workload domain is non-trivial and complex, and that’s where EVO automation comes in. EVO SDDC is designed to work with EVO Racks, and automates the more common and time-consuming configuration activities. During the session, he showed a demo illustrating the process for creating an IaaS workload domain. The current built-in best practices handles IaaS, Big Data and VDI workload domain configurations.

Utilizing the EVO SDDC Manager UI, Anil was able to quickly define the availability, performance and security requirements from a list of dropdown parameters. These parameters, in turn, select, acquire and deploy the correct resources to meet the defined requirements automatically. Policies are then set automatically from the standard choices. For example, availability can be configured from simple requirements like Low redundancy, Normal redundancy and two levels of High redundancy. Behind the scenes, the automation allocates, configures and enables the appropriate resources to meet these availability requirements.

Anil also went through scenarios showing examples for a typical EVO Rack configuration and how to scale out the workload domains.

It appears the first workload domain automated best practices were right on the mark, as a poll of the attendees revealed that IaaS and SQL configurations were identified as the first and second most time intensive tasks, respectively.

Anil asked for suggestions from the audience about what other tasks they would consider their next challenges on SDDC. The number one response was Internet App Logic workloads, and overwhelmingly, the audience agreed that the ability to standardize and maintain consistent workload builds was the most important to them.

Keep EVO SDDC on your radar! More best practices for automation to standardize and save time are on the way!

vCenter High Availability

Madhup Gulati, VMware Product Manager for vCenter, discussed the current toolset and options for providing High Availability to vCenter in vSphere 6. There were quite a few interesting exchanges between Madhup and the audience regarding who was comfortable with the current options and who wanted better tools and capabilities. This initial discussion also showed that very few customers are using Oracle as the external database for vCenter, and also that quite a few customers are at least testing the vCenter Server Appliance (vCSA). In general, however, customers agreed that they wanted more capabilities to protect their vCenters.

Throughout the session we also discussed High Availability, specifically for the Platform Services Controller (PSC). The PSC is a critical component because it contains the Single Sign On (SSO) feature. Therefore, if there is a PSC failure, user and solution authentication will not be possible creating substantial usability issues within vSphere. Madhup reviewed PSC replication capabilities and the high availability topologies included supported load balancers. Finally, he provided a roadmap of what will be coming in future releases, which were very well received.

This session was very interactive and provided many insights into customers’ requirements and challenges as the criticality of vCenter and the Platform Services Controller has steadily increased. The audience learned how to better protect these components in vSphere 6 as well as the exciting new features coming in future releases.

Be sure to follow @VMwareTAM for all of the latest news, tips, and event information!