CA Spectrum. Virtual Host Manager Solution Guide. Release 9.3

(1)

Virtual Host Manager Solution Guide

Release 9.3

(2)

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

(3)

CA Technologies Product References

This document references the following CA Technologies products: ■ CA Spectrum® (CA Spectrum)

■ CA Spectrum® Virtual Host Manager (Virtual Host Manager) ■ _{CA Spectrum® Report Manager (Report Manager)}

■ CA Spectrum® Active Directory and Exchange Server Manager (ADES Manager) ■ _{CA Spectrum® Cluster Manager (Cluster Manager)}

■ _{CA Virtual Assurance for Infrastructure Managers (CA Virtual Assurance for} Infrastructure Managers)

■ CA SystemEDGE

■ _{CA Mediation Manager (CAMM)}

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ _{Information about user communities and forums} ■ Product and documentation downloads

■ CA Support policies and guidelines

■ _{Other helpful resources appropriate for your product}

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

(4)

(5)

Contents 5

Chapter 1: Virtual Host Manager

9

About Virtual Host Manager ... 9

Who Should Use Virtual Host Manager ... 9

Virtual Technologies Supported by Virtual Host Manager ... 10

System Requirements ... 10

How Virtual Host Manager Works ... 11

CA SystemEDGE Agent with CA Virtual Assurance for Infrastructure Managers AIMs ... 12

CA Mediation Manager ... 13

Overlapping Virtual Technologies ... 14

Virtual Device Management and Multiple CA Spectrum AIM Solutions ... 15

Chapter 2: Getting Started

17

How to Install Virtual Host Manager ... 17

How to Model Your Environment When Using Multiple AIM Solutions ... 19

Viewing the Virtual Environment ... 20

Icons for Virtual Devices... 21

Locating Virtual Models in CA Spectrum ... 22

Information Tab and Subviews ... 24

Updating the Views ... 25

Searches ... 25

Alarms and Fault Isolation... 26

Creating Event Reports ... 26

Deleting Models When Using Multiple AIM Solutions ... 27

Chapter 3: VMware

29

How Virtual Host Manager Works with VMware ... 29

Models Created for VMware ... 32

Discovering VMware Networks ... 35

How to Configure Discovery Options ... 35

How to Discover and Model Your Virtual Environment ... 43

Viewing Your VMware Virtual Environment ... 52

Viewing Your VMware Virtual Network ... 52

Understanding the VMware Virtual Topology ... 55

How the VMware Data is Updated in Virtual Host Manager ... 56

Custom Subviews for Virtual Entity Types ... 58

(6)

6 Virtual Host Manager Solution Guide

Status Monitoring Options ... 61

How to Configure Management Options ... 64

Configure the vCenter Server AIM ... 64

Configure and Monitor Resource Status ... 68

Controlling vCenter Server AIM Polling ... 69

Configure the vCenter Server Polling Interval ... 70

Disable vCenter Server Polling ... 70

Deleting Virtual Host Manager Models ... 71

Distributed and Selective Management ... 72

Selective Data Center Modeling ... 72

Distributed Management of Your Virtual Environment ... 74

Alarms and Fault Isolation for VMWare ... 77

Virtual Host Manager Alarms for VMware ... 77

Fault Management for Virtual Networks ... 83

Determining Virtual Machines Affected by ESX Outages ... 90

Chapter 4: Solaris Zones

91

How Virtual Host Manager Works with Solaris Zones... 91

Models Created for Solaris Zones ... 93

Getting Started with Solaris Zones ... 94

Controlling Solaris Zones AIM Polling ... 112

Viewing Your Solaris Zones Virtual Environment ... 115

Understanding the Virtual Topology ... 115

Icons for Virtual Devices... 118

How the Solaris Zones Data is Updated in Virtual Host Manager ... 119

Locater Tab for Solaris Zones ... 122

Alarms and Fault Isolation for Solaris Zones ... 126

Virtual Host Manager Alarms for Solaris Zones ... 126

Determining Solaris Zones Affected by Solaris Zones Host Outages ... 138

Chapter 5: Microsoft Hyper-V

141

How Virtual Host Manager Works with Hyper-V ... 141

Models Created for Hyper-V ... 143

(7)

Contents 7

Viewing Your Hyper-V Virtual Environment ... 158

Viewing Your Hyper-V Virtual Network ... 158

Understanding the Hyper-V Virtual Topology ... 160

How the Hyper-V Data is Updated in Virtual Host Manager ... 160

Locater Tab for Hyper-V Searches ... 163

Controlling Hyper-V AIM Polling ... 167

Configure the Hyper-V AIM Polling Interval ... 168

Disable Hyper-V AIM Polling ... 169

Alarms and Fault Isolation for Hyper-V ... 170

Virtual Host Manager Alarms for Hyper-V ... 170

Determining Hyper-V Virtual Machines Affected by Hyper-V Host Outages ... 179

Chapter 6: IBM LPAR

181

How Virtual Host Manager Works with IBM LPARs ... 181

Models Created for IBM LPARs ... 183

Discovering IBM LPAR Networks ... 184

Viewing Your IBM LPAR Virtual Environment ... 199

Viewing Your IBM LPAR Virtual Network ... 199

Understanding the IBM LPAR Virtual Topology ... 200

How the IBM LPAR Data is Updated in Virtual Host Manager ... 201

Locater Tab for IBM LPAR Searches ... 204

Configure the IBM LPAR AIM ... 207

Controlling IBM LPAR AIM Polling ... 210

Configure the IBM LPAR Polling Interval ... 211

Disable IBM LPAR Polling ... 212

(8)

Virtual Host Manager Alarms for IBM LPAR ... 213

Determining IBM LPARs Affected by Host Outages ... 224

Chapter 7: Huawei SingleCLOUD

227

How Virtual Host Manager Works with Huawei SingleCLOUD... 227

Models Created for Huawei SingleCLOUD ... 228

Discovering Huawei SingleCLOUD Networks ... 230

Define CA Mediation Manager Presenters ... 231

Configure Discovery Options ... 232

Discover and Model Your Huawei SingleCLOUD Environment ... 237

Viewing Your Huawei SingleCLOUD Virtual Environment ... 244

Viewing Your Huawei SingleCLOUD Virtual Network ... 245

Understanding the Huawei SingleCLOUD Virtual Topology ... 247

How the Huawei SingleCLOUD Data is Updated in Virtual Host Manager ... 248

Custom Subviews ... 250

Locater Tab for Huawei SingleCLOUD Searches ... 251

Alarms and Fault Isolation for Huawei SingleCLOUD ... 253

Traps for Huawei SingleCLOUD ... 253

Fault Management for Huawei SingleCLOUD ... 255

Determining Virtual Machines Affected by Host Outages ... 261

Appendix A: Troubleshooting

263

Duplicate Models Created After SNMP and vCenter Discovery ... 263

Duplicate Models Created After Solaris Zones Discovery ... 264

Duplicate MAC, Different IP Address Alarm Generated on Solaris Zones Models ... 265

Duplicate Model Alarm on Huawei SingleCLOUD Models ... 265

Connections Do Not Appear in Huawei SingleCLOUD Topology ... 266

Glossary

269 Index

275

(9)

Chapter 1: Virtual Host Manager 9

Chapter 1: Virtual Host Manager

This section contains the following topics: About Virtual Host Manager (see page 9)

Who Should Use Virtual Host Manager (see page 9)

Virtual Technologies Supported by Virtual Host Manager (see page 10) System Requirements (see page 10)

How Virtual Host Manager Works (see page 11) Overlapping Virtual Technologies (see page 14)

Virtual Device Management and Multiple CA Spectrum AIM Solutions (see page 15)

About Virtual Host Manager

Virtual Host Manager is an application that is provided with CA Spectrum that models

and monitors the health of your virtual network environment. With this application, you can view details about your virtual networking components and the relationships between your physical and virtual components.

This broad view helps you better monitor the health of your network infrastructure, preventing service interruptions to your virtual components. Monitoring your virtual environment, such as monitoring resource utilization on hosts and virtual devices, can help you identify potential performance issues. Virtual Host Manager also helps you pinpoint and effectively troubleshoot problems within your entire network by applying CA Spectrum fault isolation techniques to virtual environments.

A key challenge when monitoring your virtual environment is keeping the data updated. Virtual environments are designed to optimize resource allocation as needed, so the relationship between the virtual and physical networks can change rapidly. Virtual Host Manager keeps up with these changes and continuously monitors the current state of your virtual network to detect any changes.

Who Should Use Virtual Host Manager

(10)

Virtual Technologies Supported by Virtual Host Manager

Virtual Host Manager can model and manage virtual networks that are created with the following virtual network technologies:

■ VMware vCenter Server (part of VMware Infrastructure and vSphere) ■ _{Solaris Zones}

■ Microsoft Hyper-V

■ IBM logical partitions (LPARs) ■ _{Huawei SingleCLOUD}

More information:

Overlapping Virtual Technologies (see page 14)

System Requirements

Virtual Host Manager is an application that works within CA Spectrum when all required components are configured properly. Virtual Host Manager requires the following components by solution.

VMware

■ CA Spectrum r9.1 or later

■ _{VMware vCenter Server release 2.x or later} ■ CA SystemEDGE agent with vCenter Server AIM

Solaris Zones

■ CA Spectrum r9.1.2 or later

■ _{CA SystemEDGE agent with Solaris Zones AIM installed on a computer running} Windows 2003 Server (32-bit)

Hyper-V

■ _{CA Spectrum Release 9.2.1 or later}

(11)

How Virtual Host Manager Works

Chapter 1: Virtual Host Manager 11 IBM LPAR

■ _{CA SystemEDGE agent with IBM LPAR AIM installed on a Windows server separate} from the HMC (see definition on page 270) managing the IBM LPARs

Huawei SingleCLOUD

■ CA Mediation Manager with Huawei SingleCLOUD Device Pack

Note: For more information about the CA SystemEDGE agent and AIM system

requirements, see the CA Virtual Assurance for Infrastructure Managers Implementation

Guide. For more information about CA Mediation Manager, see the CA Mediation

Manager documentation.

How Virtual Host Manager Works

Virtual Host Manager monitors your virtual network entities seamlessly beside your physical network entities within CA Spectrum. You get a full view of your network, which facilitates troubleshooting for both types of entities. Although your virtual network entities behave like physical components, the process for monitoring those entities differs from the general CA Spectrum monitoring process. Understanding how this process works can help you locate and resolve networking issues that are related to your virtual network.

(12)

The process to gather information about your virtual network environment is as follows: 1. The proxy manager communicates directly with entities in your virtual

environment.

Note: The proxy manager resides on a server in your network. The location of the server depends on the virtual technology.

2. Using SNMP, CA Spectrum retrieves this information from the proxy manager and uses it to model and monitor your virtual entities.

Depending on the solution, Virtual Host Manager uses either of the following proxy managers, which are described in the following sections:

■ _{CA SystemEDGE agent with a CA Virtual Assurance for Infrastructure Managers AIM} module (see page 12)

■ CA Mediation Manager with a solution-specific device pack (see page 13)

CA SystemEDGE Agent with CA Virtual Assurance for Infrastructure Managers

AIMs

The following CA Virtual Assurance for Infrastructure Managers AIMs work with Virtual Host Manager:

vCenter Server AIM

Provides the capabilities for managing and monitoring systems that are under VMware vCenter Server control. The AIM communicates directly with vCenter Server software to get an entire view of all ESX servers that the associated VMware vCenter Server manages.

Solaris Zones AIM

Provides the capabilities for managing and monitoring Oracle Solaris systems that are configured to run containers and zones. The Solaris Zones AIM requires the CA SystemEDGE agent running on a Windows server. The Solaris Zones AIM

communicates with the managed Solaris Zones servers through SSH connections. Verify that SSH is enabled on the managed Solaris servers and on the server where the Solaris Zones AIM runs. Verify the supported platforms in the CA Virtual Assurance for Infrastructure Managers documentation set.

Hyper-V AIM

(13)

Chapter 1: Virtual Host Manager 13 IBM LPAR AIM

Provides the capabilities for monitoring IBM LPARs managed by the HMC (see definition on page 270). The IBM LPAR AIM requires the CA SystemEDGE agent running on a Windows server separate from the HMC. The IBM LPAR AIM uses SSH to communicate with the HMCs, gathering information from the HMC to monitor the IBM LPAR instances.

How Virtual Host Manager Works with VMware (see page 29) How Virtual Host Manager Works with Solaris Zones (see page 91) How Virtual Host Manager Works with Hyper-V (see page 141) How Virtual Host Manager Works with IBM LPARs (see page 181)

CA Mediation Manager

The following CA Mediation Manager Device Pack is used with Virtual Host Manager: Huawei SingleCLOUD

Provides the capabilities for monitoring the Huawei SingleCLOUD platform. CA Mediation Manager communicates directly with Huawei SingleCLOUD GalaX to obtain information about the Huawei HyperVisor Universal Virtualization Platform (UVP).

(14)

Overlapping Virtual Technologies

Your virtual environment has "overlapping" technologies when either of the following conditions exist:

■ When two or more virtual technologies are used together in your environment ■ _{When the same virtual technology is nested together}

Virtual Host Manager does not support overlapping technologies that are modeled within a single SpectroSERVER. The following configurations represent examples of overlapping virtual technologies:

■ Solaris Zones AIM and vCenter Server AIM are enabled on the same CA SystemEDGE host

■ _{vCenter Server AIM is enabled on a VMware virtual machine that a different} vCenter Server AIM manages

■ Solaris Zones AIM is installed on a VMware virtual machine ■ Solaris Zones Host is installed on a VMware virtual machine ■ _{Solaris Zones Manager is installed on a Hyper-V virtual machine}

■ _{IBM LPAR AIM running on a VMware virtual machine or Hyper-V virtual machine}

When CA Spectrum discovers an unsupported configuration between virtual technologies, the following behavior occurs:

■ _{During initial modeling of a virtual technology manager, CA Spectrum prevents the} creation of the technology folder. A minor alarm is generated, alerting you to the unsupported configuration.

■ _{When a virtual technology manager monitors the same device that another} manager is managing currently, CA Spectrum creates duplicate models for that device.

If you model the overlapping virtual technology manager on a separate SpectroSERVER, then Virtual Host Manager can support the overlapping technology managers.

For example, assume that you host a Solaris zone instance on a VMware virtual machine. You cannot manage both of these virtual environments on a single SpectroSERVER. Instead, each virtual environment must be managed on separate SpectroSERVERs.

(15)

Virtual Device Management and Multiple CA Spectrum AIM Solutions

Chapter 1: Virtual Host Manager 15

Virtual Device Management and Multiple CA Spectrum AIM

Solutions

When managing a device by multiple CA Spectrum AIM solutions, a defined ranked order of management applies, as follows:

1. Virtual Host Manager 2. Cluster Manager

3. Other technologies (such as Active Directory and Exchange Server Manager)

When a host with a CA SystemEDGE agent is already modeled in CA Spectrum, Virtual Host Manager recognizes the model. A duplicate model is not created. Instead, Virtual Host Manager pulls the existing model into its own management, applying the rules for each solution using the ranked order.

For example, when both Virtual Host Manager and Cluster Manager are managing a device, model parameters that Virtual Host Manager assigns are used. Examples of these parameters include the model name, IP address, and MAC address.

When a solution no longer manages a device, the rules of the remaining solutions are reapplied in the ranked order. Typically, any changes are made at the next polling cycle.

The defined order of management also affects how models appear in the Universe topology. Because Virtual Host Manager is the highest in the management ranking, all virtual devices appear in the appropriate virtual host containers automatically.

Note: For more information, see the Cluster Manager Solution Guide and the Active

Directory and Exchange Server Manager Solution Guide.

(16)

(17)

Chapter 2: Getting Started 17

Chapter 2: Getting Started

This section describes the basic information that is required to install and begin using Virtual Host Manager. The information in this section applies to all virtual technologies supported by Virtual Host Manager.

This section contains the following topics: How to Install Virtual Host Manager (see page 17)

How to Model Your Environment When Using Multiple AIM Solutions (see page 19) Viewing the Virtual Environment (see page 20)

Deleting Models When Using Multiple AIM Solutions (see page 27)

How to Install Virtual Host Manager

Virtual Host Manager is included in all CA Spectrum extraction keys. When you install CA Spectrum, the Virtual Host Manager components are automatically installed and available for use. However, Virtual Host Manager is operable only after you also install and configure the appropriate proxy manager for your solution. For Huawei

SingleCLOUD, use CA Mediation Manager. For all other supported technologies, use the CA Virtual Assurance for Infrastructure Managers AIM of the CA SystemEDGE agent.

(18)

How to Install Virtual Host Manager

To install Virtual Host Manager, complete these tasks: 1. Install the appropriate proxy manager:

■ For VMware, Solaris Zones, Hyper-V, and IBM LPAR solutions, install the CA SystemEDGE agent and load the appropriate CA Virtual Assurance for Infrastructure Managers AIM. Use the appropriate location for your virtual technology, as follows:

– VMware: Install on the same server where vCenter is installed or a separate server that can contact vCenter remotely.

– Solaris Zones: Install on a 32-bit Windows system with SSH access to each Solaris Zone Host.

– Hyper-V: Install on each Hyper-V Host.

– IBM LPAR: Install on a Windows server separate from the HMC (see definition on page 270) that manages the IBM LPARs.

Note: Monitor only one instance of the IBM LPAR Host with the IBM LPAR AIM. Do not manage a single IBM LPAR Host with multiple HMCs.

Monitoring more than one instance can result in duplicate models in CA Spectrum.

Note: For installation instructions and more information about the AIM for your virtual technology, see the CA Virtual Assurance for Infrastructure

Managers Implementation Guide.

■ For Huawei SingleCLOUD, install and configure CA Mediation Manager and the Huawei SingleCLOUD Device Pack. Do not install the CAMM components on the same server where CA Spectrum is installed.

Important! When configuring the Huawei SingleCLOUD Device Pack, you set

the virtual IP addresses. The primary IP address of the device or virtual machine where the CAMM Presenter is installed cannot be used as a virtual IP address.

Note: For more information, see the CA Mediation Manager documentation. 2. Install CA Spectrum with Virtual Host Manager included.

Important! Do not install the SpectroSERVER on a virtual machine that Virtual Host

Manager will manage.

(19)

How to Model Your Environment When Using Multiple AIM Solutions

Chapter 2: Getting Started 19 More information:

System Requirements (see page 10)

Discovering VMware Networks (see page 35) Getting Started with Solaris Zones (see page 94) Discovering Hyper-V Networks (see page 144) Discovering IBM LPAR Networks (see page 184)

Discovering Huawei SingleCLOUD Networks (see page 230)

How to Model Your Environment When Using Multiple AIM

Solutions

Depending on your environment, you can use Virtual Host Manager with other CA Spectrum AIM solutions to manage your infrastructure. Some configurations, such as the following examples, require multiple solutions for comprehensive management: ■ _{A cluster node is a virtual machine.}

■ An Active Directory or Exchange Server host is a virtual machine.

Each of the CA Spectrum AIM solutions provides information that is specific to the technology it supports. For example:

■ _{Virtual Host Manager provides data that is specific to virtual technologies.} ■ Cluster Manager provides data that is specific to cluster technologies.

■ _{Active Directory and Exchange Server (ADES) Manager data that is specific to the} supported Active Directory and Exchange Server roles.

Combined, these features provide a complete monitoring solution. To set up your implementation of multiple AIM solutions, take the following recommended approach.

Important! When using multiple AIMs, only a single AIM can be installed on a CA

SystemEDGE host.

Follow these steps:

1. Configure the AutoDiscovery settings on the VNM model.

2. Configure the Virtual Host Manager settings that are related to your virtual technology.

3. Set up Virtual Host Manager by modeling the virtual technology manager and all virtual technology components.

(20)

Viewing the Virtual Environment

5. Set up ADES Manager by modeling the ADES Host Manager and all Active Directory and Exchange Server hosts.

Note: For more information, see the Cluster Manager Solution Guide and the Active

Directory and Exchange Server Manager Solution Guide.

Virtual Device Management and Multiple CA Spectrum AIM Solutions (see page 15) Deleting Models When Using Multiple AIM Solutions (see page 27)

Viewing the Virtual Environment

The purpose of Virtual Host Manager is to provide visibility into your virtual

environment. This visibility lets you view the logical relationships between devices, view performance data for individual entities, and report on the data you discover. Your virtual environment inevitably connects with your physical environment. Virtual Host Manager can help you visualize where these connections are and how they are performing.

Virtual Host Manager provides several methods for viewing your virtual environment, as follows:

■ The Explorer tab hierarchy in the Navigation panel shows logical relationships. ■ _{Icons for individual models provide status and model type information at a glance.} ■ A graphical topology view helps you visualize connections between virtual and

physical entities.

■ _{Information views in the Contents and Component Detail panels provide detailed} information about individual entities in your virtual environment.

Understanding each of these methods can help you monitor your virtual environment, letting you troubleshoot issues and optimize performance.

(21)

Icons for Virtual Devices

Virtual Host Manager provides icons that are designed specifically to distinguish devices in your virtual environment. To distinguish physical and virtual entities, the virtual device icons have a halo-like appearance around the outer edge. For example, a virtual device model icon displays a halo around the perimeter, as follows:

(22)

Locating Virtual Models in CA Spectrum

The models that are created for your virtual environment are integrated into CA Spectrum in the following three places:

Universe group

Appears in the Navigation panel and provides a hierarchical tree structure that displays the logical relationships between devices, both physical and virtual. Virtual Host Manager group

Appears in the Navigation panel and provides a hierarchical tree structure. This structure helps you to visualize the relationships between your virtual devices, physical devices, and the logical entities that are configured in your virtual technology.

Topology tab

Appears in the Contents panel, providing a graphical view of your physical network, virtual network, and virtual machines. The topology provides a layer 2 view of the network, showing how your virtual and physical networks are connected. You can use this view to resolve alarms involving these virtual network models.

Note: This tab is available for only items in the Universe group. All these views are available from the Explorer tab in the Navigation panel.

Understanding how your virtual environment information appears in CA Spectrum is the key to deciding which view is best for viewing your virtual entities.

Note: For more information about using the OneClick interface, see the Operator Guide.

Locate Models on the Explorer tab

(23)

Chapter 2: Getting Started 23 View the same model in different Explorer tab groups to gain insight into its

relationships within your physical and virtual networks.

To locate models on the Explorer tab, use the following procedure.

1. Locate an item in the Contents panel or Component Detail panel that references a single model.

2. Right-click the item and select from the following options: Location

Changes the OneClick Console views to locate the selected model within the Explorer tab hierarchy in the Navigation panel. You can select from the following location options:

Universe

Locates the model in the Universe group hierarchy on the Explorer tab. Virtual Host Manager

Locates the model in the Virtual Host Manager group hierarchy on the Explorer tab.

The OneClick Console locates the related model in the Explorer tab. The Contents and Component Detail panels display details about the selected model.

Topology View

The CA Spectrum topology views provide a graphical depiction of your physical network, virtual network, and virtual machines. The topology views are available on the Topology tab in the Contents panel. Use the views on the Topology tab to resolve alarms involving these virtual network models. These views display the Layer 2 connectivity, showing how virtual and physical networks are connected.

CA Spectrum provides options for arranging the models in most topology views, such as the tree, radial, or manual layout. When selecting the tree layout, the Topology tab for the Universe group includes the following three unlabeled tiers of models:

Top tier

(24)

24 Virtual Host Manager Solution Guide Middle tier

Contains any manageable switches that are discovered in your environment. These switches provide connectivity to the virtual host devices within the data center. Bottom tier

Contains the virtual host device models and any unmanaged switches. The virtual host devices are the physical servers that run your virtualization technology.

When a server that hosts virtual machines is selected from the Explorer tab, only one layout option is available for the Topology tab. This automatic layout is organized into a tree structure and includes the following three labeled tiers:

Physical Network

Contains an off-page reference to any physical switches that detect traffic for a specific virtual machine. These entities are the components of your physical network that connect to your virtual network.

Virtual Network

Represents the internal or virtual switching that the virtual machine device

provides. When a virtual switch has been configured with multiple virtual machines, CA Spectrum creates a model in the Virtual Network tier named a "repeater segment" or a "fanout." This fanout model represents the presence of a virtual switch.

Virtual Machines

Includes the virtual machines that are configured on the virtual host device that you selected in the Navigation panel.

Information Tab and Subviews

The tabs in the Contents and Component Details panels provide information that helps you monitor your virtual environment. The Information tab provides details about a single entity in your environment.

(25)

Updating the Views

When you run the initial Discovery, Virtual Host Manager populates the Explorer tab with virtual device models. After Virtual Host Manager builds this initial hierarchy, your virtual network configuration can change frequently. Therefore, Virtual Host Manager continually updates this information. The information is useful for troubleshooting issues and optimizing performance only when it accurately reflects your virtual environment.

Understanding how and when the information is updated can help you evaluate the data and monitor your virtual environment.

How the VMware Data is Updated in Virtual Host Manager (see page 56) How the Solaris Zones Data is Updated in Virtual Host Manager (see page 119) How the Hyper-V Data is Updated in Virtual Host Manager (see page 160) How the IBM LPAR Data is Updated in Virtual Host Manager (see page 201)

How the Huawei SingleCLOUD Data is Updated in Virtual Host Manager (see page 248)

Searches

Searching your virtual environment with CA Spectrum is a fundamental network management task. Virtual Host Manager does not provide a virtual-only topology view. Instead, CA Spectrum provides a collection of searches on the Locater tab that are designed specifically for your virtual network. These searches identify specific models or groups of models on your virtual network. Using these searches can help you locate details that you can use to monitor the performance of your virtual environment.

Locater Tab for VMware Searches (see page 59) Locater Tab for Solaris Zones (see page 122) Locater Tab for Hyper-V Searches (see page 163) Locater Tab for IBM LPAR Searches (see page 204)

(26)

Alarms and Fault Isolation

To alert you to problems within your virtual network, CA Spectrum generates alarms and uses advanced fault management techniques to isolate the root cause. Virtual networks provide a unique management opportunity because they provide an alternate management perspective in addition to standard device monitoring. While gathering information directly from a device, CA Spectrum also simultaneously gathers

information from the proxy manager. With this extra monitoring capability, in addition to Contact Lost alarms, you can also incur Proxy Lost or Proxy Manager Unavailable alarms.

Alarms and fault isolation vary by virtual technology. The type of fault isolation that Virtual Host Manager uses depends on the devices that generate alarms and the type of events. CA Spectrum uses all available information to correlate the alarms to the appropriate root cause, avoiding multiple or false alarms.

Alarms on Initial Models

Until CA Spectrum contacts a model, the model remains in the Initial (blue) condition. Alarms are typically not visible on a model in the Initial condition; however, an

exception applies when using Virtual Host Manager. If a virtual machine is brought into Virtual Host Manager management in the powered-down or suspended state, the critical Powered-Down or Suspended alarm overrides the Initial condition.

Alarms and Fault Isolation for VMWare (see page 77) Alarms and Fault Isolation for Solaris Zones (see page 126) Alarms and Fault Isolation for Hyper-V (see page 170) Alarms and Fault Isolation for IBM LPAR (see page 213)

Alarms and Fault Isolation for Huawei SingleCLOUD (see page 253)

Creating Event Reports

Use event filters to create event reports in Report Manager. You can base these reports on any of the traps and events that are generated for your virtual entities in CA

Spectrum.

To report on Virtual Host Manager events, the following event filter files are included with Report Manager:

(27)

Deleting Models When Using Multiple AIM Solutions

Chapter 2: Getting Started 27 Note: For more information about using Report Manager to generate event reports from these codes, see the Report Manager User Guide. For information about using the predefined event filter files to generate reports, see the Report Manager Installation

and Administration Guide.

Deleting Models When Using Multiple AIM Solutions

If you use Virtual Host Manager with other CA Spectrum AIM solutions, consider the following points when deleting models in your environment:

■ _{If you plan to stop managing the device models using Virtual Host Manager,} configure Virtual Host Manager delete settings to retain models. Otherwise, Virtual Host Manager deletes the model initially, losing any history or customization. Another AIM solution then recreates the model.

Note: The Virtual Host Manager setting to retain models when the technology manager is deleted applies to SNMP-enabled device models only. For ICMP (Pingable) models, Virtual Host Manager deletes the model, and then another AIM solution recreates the model.

■ When Virtual Host Manager unmanages a device and the model is retained, another AIM solution automatically pulls the model into its management. ■ _{If a solution no longer manages a device, the rules of the remaining solutions are}

reapplied in the ranked order. Typically, any changes are made at the next polling cycle.

■ _{The Explorer view hierarchy synchronizes after the Lost and Found (LostFound) is} emptied.

(28)

(29)

Chapter 3: VMware 29

Chapter 3: VMware

This section is for VMware users and describes how to use Virtual Host Manager to manage your virtual entities that are created with VMware vCenter.

This section contains the following topics:

How Virtual Host Manager Works with VMware (see page 29) Models Created for VMware (see page 32)

Discovering VMware Networks (see page 35)

Viewing Your VMware Virtual Environment (see page 52) How to Configure Management Options (see page 64) Controlling vCenter Server AIM Polling (see page 69) Deleting Virtual Host Manager Models (see page 71) Distributed and Selective Management (see page 72) Alarms and Fault Isolation for VMWare (see page 77)

How Virtual Host Manager Works with VMware

(30)

How Virtual Host Manager Works with VMware

(31)

How Virtual Host Manager Works with VMware

Chapter 3: VMware 31 As shown in the diagram, the process to gather information about your VMware virtual environment is as follows:

1. The VMware vCenter application manages the ESX hosts in your virtual network. The VMware vCenter application stores detailed data about each ESX host and their virtual machines.

2. The CA SystemEDGE agent communicates with vCenter to gather the details about your virtual network. The CA SystemEDGE agent must have the vCenter Server AIM loaded. CA SystemEDGE can be deployed in either of the following two locations: ■ The same server as vCenter

■ A different server from vCenter

Note: For more information about locally or remotely deploying CA SystemEDGE and the vCenter Server AIM, see the CA Virtual Assurance for Infrastructure

Managers Implementation Guide.

3. Periodically, CA Spectrum retrieves information from CA SystemEDGE and uses it to model and monitor your virtual entities in OneClick.

Because Virtual Host Manager communicates with vCenter, CA Spectrum is aware of spontaneous network configuration changes. Examples are those changes that are due to VMware VMotion, HA technology, or a DRS scenario. Changes that are associated with these events are quickly reflected in OneClick and factored into the root cause analysis.

How Virtual Host Manager Works (see page 11)

(32)

Models Created for VMware

Virtual Host Manager provides several models to represent the components of your VMware virtual technology network. Understanding the following basic models can help you better understand Discovery and how the virtual environment interfaces with your physical environment.

Note: Deployment of the CA SystemEDGE agent and vCenter Server AIM in your environment (see page 29) impacts the models that Virtual Host Manager displays. Virtual Host Manager includes the following models and icons for VMware devices in a

remote deployment scenario:

VMware Manager

Represents a physical or virtual host that contains the CA SystemEDGE agent with vCenter Server AIM loaded. This CA SystemEDGE agent remotely monitors the vCenter application running on a separate host (represented by the VMware vCenter Server model).

Icon: or

VMware vCenter Server

Represents a physical or virtual host that contains the vCenter application to manage your VMware virtual environment. The CA SystemEDGE agent with vCenter Server AIM monitors the vCenter application remotely. The CA SystemEDGE agent with vCenter Server AIM is on a separate host (represented by the VMware Manager model).

(33)

Chapter 3: VMware 33 Virtual Host Manager includes the following models and icons for VMware devices in a

local deployment scenario:

VMware Manager and vCenter Server

Represents a physical or virtual host that contains both the vCenter application and the CA SystemEDGE agent with vCenter Server AIM loaded. Because these items are both installed on the same host, Virtual Host Manager uses a single model to represent them in OneClick.

Icon: or

Both the local and remote deployment Virtual Host Manager scenarios include the following models and icons for VMware devices:

ESX Host

Represents an ESX host, as configured in your VMware virtualization technology. An

ESX host is a physical computer that uses ESX Server virtualization software to run

virtual machines. Hosts provide the CPU and memory resources that virtual

machines use and give virtual machines access to storage and network connectivity. In the Universe topology, these models group your virtual entities into a separate view while showing how the virtual environment interacts with the physical network. The ESX host cannot be contacted directly for status information. Instead, the status of these models is inferred from the status of the items that it contains.

Icon:

ESX Service Console

Represents the ESX service console component of your virtual environment. The

ESX service console is a Linux kernel running on the ESX host that provides a

management interface to the hosted virtual machines.

(34)

34 Virtual Host Manager Solution Guide Virtual Machines

Represents a virtual machine, as configured in your VMware virtualization technology. A virtual machine (VM) is a software computer that, like a physical computer, runs an operating system and applications. A virtual machine

dynamically consumes resources on its physical host, depending on its workload. Because virtual machines are flexible computing units, their deployment comprises a wide range of environments. Examples include environments such as data centers, cloud computing, test environments, or desktops and laptops. In data center implementations, they are used for server consolidation, workload optimization, or higher energy efficiency.

Icon:

Virtual Host Manager also creates models these additional VMware entities that organize the ESX hosts and their virtual machines:

Data Centers

Represents a data center, as configured in your VMware virtualization technology. A data center serves as a container for your hosts, virtual machines, resource pools, or clusters. Depending on their virtual configuration, data centers can represent organizational structures, such as geographical regions or separate business functions. You can also use data centers to create isolated virtual environments for testing or to organize your infrastructure. Components can interact within data centers, but interaction across data centers is limited. A data center can contain clusters or hosts.

Icon: Clusters

Represents a cluster, as configured in your VMware virtualization technology. A

cluster is a group of ESX hosts and their associated virtual machines. When a host is

added to a cluster, the host resources become part of the cluster resources. The cluster manages the resources of all hosts within it. A cluster can contain hosts, resource pools, or virtual machines.

(35)

Discovering VMware Networks

Chapter 3: VMware 35 Resource Pools

Represents a resource pool, as configured in your VMware virtualization

technology. A resource pool defines partitions of physical computing and memory resources of a single host or a cluster. You can partition any resource pool into smaller resource pools to divide and assign resources to specific groups or for specific purposes. You can also hierarchically organize and nest resource pools. A resource pool can contain virtual machines or more resource pools.

Icon:

Important! Resource pools that are named "Resources" are skipped during

Discovery and modeling. This name is designated for internal use only. Therefore, Virtual Host Manager filters these resource pools out of the Discovery results. You can avoid missing models for resource pools and the devices that they contain by specifying a different name for VMware resource pools.

Viewing Your VMware Virtual Network (see page 52)

Discovering VMware Networks

This section describes the Discovery and modeling process for Virtual Host Manager. The Virtual Host Manager administrator typically performs these tasks.

How to Configure Discovery Options

After installation, configure Virtual Host Manager for vCenter Discovery. Selecting preferences helps Virtual Host Manager to model virtual devices correctly.

Select preferences for the following options:

Automatically Model New Data Centers (see page 36)

Determines whether new data centers that are discovered during vCenter Discovery are modeled automatically.

Maintenance Mode for New Virtual Machines (see page 37)

(36)

Allow Device Model Deletes During vCenter Discovery (see page 38)

Controls how CA Spectrum handles ESX host, ESX service console, and virtual machine models when vCenter no longer manages them. Controls how these models are handled when you configure CA Spectrum to disable management of their parent data center.

Search for Existing Models (see page 40)

Determines the secure domains that Virtual Host Manager searches during a vCenter Discovery.

Discover SNMP-Capable Devices (see page 41)

Controls how SNMP-capable devices are modeled during vCenter Discovery. By default, new models are initially created as VHM models only. But, this option lets you override the default and immediately create SNMP models for devices that meet the necessary criteria.

Retain SNMP-enabled Virtual Machines During VMware Manager Deletion (see

page 42)

Controls how CA Spectrum handles SNMP-enabled virtual machine models when a VMware Manager model is deleted.

Configure Automatic Modeling for New Data Centers

For each SpectroSERVER in your networking environment, you can control whether CA Spectrum automatically models new data centers that are found during vCenter Discovery. Modeling data centers automatically means that CA Spectrum manages all data centers in your vCenter environment.

1. Open Virtual Host Manager in the Navigation panel (see page 52).

The main details page opens in the Contents panel for the selected Virtual Host Manager.

(37)

Chapter 3: VMware 37 3. Expand the Configuration, VMware, vCenter Discovery subview.

4. Click Set in the 'Automatically Model New Datacenters' field, and select one of the following options:

Yes

(Default) Models all data centers that are found during vCenter Discovery. Includes all of the contained clusters, resource pools, ESX hosts, ESX service consoles, and virtual machines.

No

Prevents the modeling of new data centers that are found during vCenter Discovery. CA Spectrum does not model the components that are contained within the data center.

Use this option if your networking environment includes data centers that do not require monitoring. Then model your data centers manually.

Your setting is saved, and new data centers are modeled in Virtual Host Manager according to your selection.

How to Configure Discovery Options (see page 35)

Manage Device Models for Devices Deleted from vCenter (see page 38) Select the Data Centers to Model on a vCenter Server (see page 73)

Configure Maintenance Mode for New Virtual Machines

Virtual Host Manager automatically models the virtual machines that vCenter manages. CA Spectrum attempts to manage all discovered models. However, some virtual machines are not ready for CA Spectrum management when they are initially modeled. For example, CA Spectrum generates a Virtual Machine Powered Down alarm when it detects virtual machines that are powered down. To prevent undesired alarms on new models, you can select virtual machine models to be immediately placed into

maintenance mode. Later, you can manually disable maintenance mode when you are ready to manage these devices.

Configure the maintenance mode for new virtual machines in OneClick.

(38)

3. Expand the Configuration, VMware, vCenter Discovery subview.

4. Click Set in the "Maintenance Mode for New Virtual Machines" field, and select one of the following options:

Place only Powered down VMs in Maintenance Mode

(Default) Applies maintenance mode only to powered-down or suspended virtual machine models at initial vCenter Discovery.

Place all VMs in Maintenance Mode

Applies maintenance mode to all new virtual machine models upon initial vCenter Discovery.

Your setting is saved, and new virtual machines that are modeled in Virtual Host Manager are placed into maintenance mode according to your selection.

How to Configure Discovery Options (see page 35) Status Monitoring Options (see page 61)

Manage Device Models for Devices Deleted from vCenter

The devices and the relationships between them change frequently in virtual networks. CA Spectrum attempts to reflect these changes accurately. When an ESX host is removed or a virtual machine is deleted in vCenter, CA Spectrum removes the corresponding device model from the Virtual Host Manager hierarchy. The option to "Allow Device Model Deletes During vCenter Discovery" controls whether CA Spectrum deletes the model. This option also controls the handling of device models that are contained in a data center when you disable management of the data center in Virtual Host Manager.

Important! When models are deleted, all notes or other customizations on those

models are lost. You can disable this option if your models are likely to be recreated in vCenter later.

You can manage device models for devices that are deleted from vCenter.

2. Click the Information tab.

(39)

Chapter 3: VMware 39 4. Click Set in the "Allow Device Model Deletes During vCenter Discovery" field and

select one of the following options: Yes

(Default) Deletes the Virtual Host Manager models that correspond to entities that are no longer managed in vCenter. Also deletes data center models for which you disable modeling in Virtual Host Manager.

No

Places Virtual Host Manager models in the LostFound container if their corresponding entity is no longer managed in vCenter. Also places data center models in the LostFound container when you disable modeling for the data center in Virtual Host Manager.

Note: Models with more associations, such as a model that is included in a Global Collection, are handled differently. These models are removed from the Universe, but they are not moved to the LostFound container.

Your setting is saved, and device models are handled as such after the device is deleted from vCenter.

Configure Automatic Modeling for New Data Centers (see page 36) Deleting Virtual Host Manager Models (see page 71)

Manage SNMP-Enabled Virtual Machine Models After VMware Manager Deletion (see page 42)

Select the Data Centers to Model on a vCenter Server (see page 73) Virtual Host Manager Alarms for VMware (see page 77)

(40)

Configure Model Searches Across Secure Domains

Rather than creating new models, vCenter Discovery attempts to locate models that exist in the SpectroSERVER. In an environment with Secure Domain Manager deployed, vCenter Discovery searches for models within the same secure domain as your VMware Manager. This domain is the "local" domain. However, some of your virtual

environment devices can exist within a different secure domain. In this case, you can configure vCenter Discovery to search all secure domains for existing models.

You configure model searches across secure domains.

4. Click Set in the "Search for Existing Models" field and select from the following options:

In vCenter's Secure Domain

(Default) Searches for existing models within the same secure domain as the vCenter server.

In All Secure Domains

Searches for existing models within all secure domains managed by the SpectroSERVER. Select this option only in the following situations: ■ All devices have unique IP addresses.

■ When secure domains are used for security purposes or to isolate network traffic.

Note: Do not select this option for a NAT environment.

Your setting is saved. vCenter Discovery searches for the specified models in CA Spectrum. When duplicate models (models with the same IP address) exist in multiple secure domains, Virtual Host Manager handles the situation as follows: ■ Virtual Host Manager selects the model in the local secure domain, if available. ■ If a duplicate model does not exist in the local domain, Virtual Host Manager

randomly selects a model from another secure domain.

(41)

Chapter 3: VMware 41 More information:

Configure SNMP Modeling Preferences

SNMP-capable virtual machines support enriched device monitoring, such as process and file system monitoring capabilities. However, SNMP agents can be costly and time-consuming to deploy. By default, vCenter Discovery creates ESX service consoles and virtual machines as VHM models (see definition on page 272). You can later upgrade them to SNMP models. However, you can also configure vCenter Discovery to model all new SNMP-capable devices as SNMP models. Although vCenter Discovery can take longer to complete, initially modeling as SNMP models avoids manually upgrading these models later.

Important! Enable SNMP modeling before you model your vCenter servers. If you model

the vCenter servers first, all child models are created as VHM models, which must be manually upgraded to SNMP models.

3. Expand the Configuration, VMware, vCenter Discovery, SNMP Discovery subview. Important! To prepare your devices and CA Spectrum for SNMP Discovery, follow

the steps in the subview. If devices are not properly prepared before vCenter Discovery, Virtual Host Manager cannot create SNMP models.

4. Click Set in the 'Discover SNMP-Capable Devices' field and select from the following options:

Yes

Enables SNMP modeling during vCenter Discovery. Only those devices that meet the specified criteria in the SNMP Discovery subview text are modeled as SNMP devices. Applies to new models only.

No

(42)

42 Virtual Host Manager Solution Guide More information:

How vCenter Discovery Works (see page 46)

Adding SNMP Capabilities to VHM Models (see page 48)

Manage SNMP-Enabled Virtual Machine Models After VMware Manager Deletion (see page 42)

How to Discover and Model Your Virtual Environment (see page 43)

Manage SNMP-Enabled Virtual Machine Models After VMware Manager Deletion

By default, SNMP-enabled devices are deleted from CA Spectrum when the following items are deleted:

■ _{VMware Manager model for the device} ■ VMware folder in the Navigation panel

SNMP-enabled device models can include significant customizations that you want to retain. You can adjust your settings to avoid deleting these models. They are placed into the LostFound container for later use.

You can retain SNMP-enabled device models after VMware Manager or VMware folder deletion.

4. Click Set in the "Retain SNMP-enabled Virtual Machines During VMware Manager Deletion" field and select one of the following options:

Yes

Retains SNMP-enabled virtual machine models in the LostFound container when their VMware Manager or the VMware folder is deleted.

Note: Models with more associations, such as a model that is included in a Global Collection, are handled differently. These models are removed from the Universe, but they are not moved to the LostFound container.

No

(Default) Deletes all virtual machine models when their VMware Manager or the VMware folder is deleted.

(43)

Chapter 3: VMware 43 More information:

Manage Device Models for Devices Deleted from vCenter (see page 38) Deleting Virtual Host Manager Models (see page 71)

How to Discover and Model Your Virtual Environment

To monitor your virtual environment, discover and model your virtual entities—data centers, resource pools, clusters, ESX hosts, ESX service consoles, and virtual machines. Modeling these entities in Virtual Host Manager lets you view your complete network topology in one tool. You can see the relationships between your physical and virtual components.

The main steps for modeling your virtual environment are as follows: 1. Run a standard CA Spectrum Discovery (see page 44).

This Discovery ensures that the upstream routers and switches are modeled before vCenter Discovery runs. Or, if the SNMP Modeling option is disabled, this step can also model the SNMP-capable ESX service consoles and virtual machines. When modeling these entities, be sure that your modeling options are set correctly to support Virtual Host Manager.

2. Upgrade the CA SystemEDGE model (see page 45).

This step is required only when your CA SystemEDGE agent on the vCenter server was modeled in a release earlier than CA Spectrum r9.1.

3. Let vCenter Discovery run (see page 46).

When you model the CA SystemEDGE agent (with the vCenter Server AIM), vCenter Discovery begins automatically. Each of these vCenter Server models has its own vCenter Discovery process. vCenter Discovery finds the virtual entities that vCenter manages and models the ones that do not exist. vCenter Discovery then places the models in the Virtual Host Manager view of the Navigation panel.

(44)

Run CA Spectrum Discovery

To discover your VMware environment, run the standard CA Spectrum Discovery. This Discovery ensures that the upstream routers and switches are modeled so that later connections from the virtual entities can be established. You can also model the

SNMP-capable ESX service consoles and virtual machines during CA Spectrum Discovery.

Note: Modeling SNMP-capable ESX service consoles and virtual machines is necessary during CA Spectrum Discovery only when the SNMP Modeling option is disabled during vCenter Discovery.

Note: Only an administrator performs this task. Follow these steps:

1. Open the Discovery console.

Note: Prepare by knowing the correct community strings, IP addresses, and port numbers for any SNMP agents that run on a nonstandard port.

2. Click (Creates a new configuration) in the Navigation panel. 3. Configure your options for supporting virtual network modeling:

a. Click the Modeling Options button in the Modeling Options group. The Modeling Configuration dialog opens.

b. Click the Protocol Options button. The Protocol Options dialog opens.

c. Select the "ARP Tables for Pingables" option, and click OK. The Modeling Configuration dialog opens.

d. (Optional) Click the Advanced Options button in the Advanced Options group. Add your nonstandard SNMP ports (such as the CA SystemEDGE agent port), and click OK.

4. Enter individual IP addresses or the beginning and ending IP addresses in the IP Boundary List fields and click Add.

(45)

Chapter 3: VMware 45 5. Enter any additional values in the Discovery console, and click Discover.

The following models are created and are added to your network topology in CA Spectrum:

■ vCenter servers and the switches and routers that connect them to your network—Information about your virtual environment comes from the vCenter server. When these vCenter Server models exist in CA Spectrum, vCenter Discovery can begin.

■ ESX service consoles and virtual machines—If you decide not to model these entities with CA Spectrum Discovery, vCenter Discovery creates them as VHM models (see definition on page 272).

Note: You can also manually model your virtual network by IP address. In this case, we recommend modeling the upstream devices first. Modeling in the correct order ensures that the relationships between these entities are built correctly in the topology. For more information about Discovery, see the Modeling and Managing

Your IT Infrastructure Administrator Guide.

Move an ESX Host to a Different vCenter (see page 51) Adding SNMP Capabilities to VHM Models (see page 48) How to Configure Management Options (see page 64) Configure SNMP Modeling Preferences (see page 41)

Upgrade the CA SystemEDGE Model

The CA SystemEDGE agent could have been modeled in CA Spectrum before installing Virtual Host Manager or before the vCenter Server AIM was loaded on the agent. In this case, the existing CA SystemEDGE model is not compatible with Virtual Host Manager. Upgrade the model so that Virtual Host Manager can access the vCenter Server AIM capabilities in CA SystemEDGE. This procedure is not required if the CA SystemEDGE

agent with vCenter Server AIM is modeled after installing CA Spectrum.

To upgrade the CA SystemEDGE model, right-click the model and select Reconfiguration, Reconfigure Model.

The CA SystemEDGE model is upgraded to support the vCenter Server AIM.

Note: You can also send a reconfigure model action to CA SystemEDGE using the CLI. For more information, see the Modeling and Managing Your IT Infrastructure Administrator

(46)

46 Virtual Host Manager Solution Guide More information:

Move an ESX Host to a Different vCenter (see page 51) Adding SNMP Capabilities to VHM Models (see page 48) How to Configure Management Options (see page 64)

How vCenter Discovery Works

vCenter Discovery is a specialized discovery process that gathers detailed information about your virtual environment entities. vCenter Discovery finds the virtual entities that vCenter manages and models the ones that do not exist. vCenter Discovery then places the models in the Virtual Host Manager view of the Navigation panel.

A key benefit of vCenter Discovery is that it runs automatically in the background, continually keeping your virtual environment data updated in CA Spectrum. Understanding how vCenter Discovery works reinforces the importance of properly installing and modeling the various components of Virtual Host Manager.

The vCenter Discovery process works as follows:

1. When the CA SystemEDGE agent and vCenter Server AIM are operational, the AIM communicates with vCenter to gather information about the virtual entities it manages. The vCenter Server AIM stores this information.

Important! The CA SystemEDGE agent and vCenter Server AIM must be installed

and configured so that CA SystemEDGE, vCenter, and CA Spectrum can communicate. If they cannot, vCenter Discovery cannot run.

2. During CA Spectrum Discovery, CA Spectrum creates a vCenter Server model for each server that is referenced in step 1. CA Spectrum intelligence is enabled to handle communication between CA Spectrum and the CA SystemEDGE agent. 3. CA Spectrum polls the vCenter Server AIM to gather the vCenter information that