ltstudiooo - Fotolia
The VMware vRealize Operations Service Discovery Management Pack is currently in version 2.0. This release updates version 1.0.1 with changes and features that primarily impact service discovery.
The deep and shallow discovery feature in earlier VMware Management Pack versions has been replaced with known and user-defined service discovery in version 2.0. This change, in perspective, enables administrators to readily identify well-known and understood services, but administrators can also define exactly which services should be discovered and monitored.
It's important to note that any unknown services discovered by earlier versions of the VMware management pack will be delineated as nonexistent under version 2.0. Similarly, unknown and user-defined services are reset when upgrading to version 2.0. This means administrators moving to version 2.0 will need to reconfigure unknown and user-defined services as part of the update process, so advance planning and careful documentation of earlier definitions will help streamline the reconfiguration.
One caveat: vRealize Operations Service Discovery Management Pack (MP) 2.0 will only discover the relationship between services on VMs managed by the same VMware vCenter Server. The management pack can't discern relationships between VMs managed by different -- distributed -- vCenter Server deployments at this time.
Requirements of the VMware management pack
The vRealize Operations Service Discovery Management Pack isn't a stand-alone product, but a plug-in intended to extend the capabilities of other products -- primarily VMware's vRealize Operations Manager. The management pack can be downloaded from the VMware Solution Exchange, but it requires numerous prerequisites and other elements in the data center.
For example, current prerequisites for version 2.0 of the management pack include VMware vCenter version 5.5 or later, as well as VMware ESXi 6.0 or later and vRealize Operations Manager 6.3 or later. VMware Tools 10.1 or later must be installed and running in the OS of each guest VM to be managed – otherwise, the VMware management pack can't discover services from those VMs. It's also important to synchronize the time between vRealize Operations Manager and vCenter Server.
Take a moment to determine the compatibility between the management pack version and the version of vRealize Operations. For example, the earlier 1.0.1 version of the management pack is compatible with vRealize Operations 6.4 Advanced, 6.5 Enterprise and 6.6 Enterprise. The current 2.0 version of the management pack is compatible with vRealize Operations 6.3 Advanced, 6.3 Enterprise, 6.4 Enterprise, 6.5 Advanced and 6.6 Advanced. This relationship can make the decision to upgrade the management pack somewhat confusing.
Once the VMware management pack is downloaded and installed, administrators will need to create guest user mapping for each VM, and then configure the management pack to discover dependencies and collect workload information from each VM for display and reporting.
Dig Deeper on VMware cloud
Related Q&A from Stephen J. Bigelow
Fog computing vs. edge computing -- while many IT professionals use the terms synonymously, others make subtle but important distinctions between ... Continue Reading
Learn how load balancing in the cloud differs from a traditional network traffic distribution, and explore services available from AWS, Google and ... Continue Reading
Access management is critical to securing the cloud. Understand the differences between AWS IAM roles and users to properly restrict access to AWS ... Continue Reading