powerpath management pack for microsoft … management pack for microsoft operations manager ... 4...

EMC® PowerPath® Management Pack for MicrosoftOperations Manager

Version 5.5

USER GUIDEP/N 300-011-450

REV A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

2

Copyright © 2006 - 2010 EMC Corporation. All rights reserved.

Published September 2010

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THISPUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC PowerPath Management Pack for Microsoft Operations Manager

Preface

As part of an effort to improve and enhance the performance and capabilitiesof its product line, EMC from time to time releases revisions of its hardwareand software. Therefore, some functions described in this guide may not besupported by all revisions of the software or hardware currently in use. Forthe most up-to-date information on product features, refer to your productrelease notes.

If a product does not function properly or does not function as described inthis guide, please contact your EMC representative.

Audience andprerequisites

This document is intended for use by storage administrators andother information system professionals responsible for using,installing, and maintaining PowerPath. Readers of this document areexpected to be familiar with storage systems management, theapplications used with PowerPath, and Microsoft products.

Readers of this guide are expected to be familiar with the operatingsystem on which you are running PowerPath Migration Enabler andwith EMC storage systems.

Relateddocumentation

Other related EMC PowerPath publications include:

◆ PowerPath Migration Enabler User Guide

◆ PowerPath Encryption with RSA User Guide

◆ PowerPath CLI and System Messages Reference Guide

◆ PowerPath Product Guide

◆ PowerPath Management Pack for Windows User Guide

◆ PowerPath Management Pack for Microsoft Operations Manager UserGuide

Preface 3

4

Preface

These PowerPath manuals are updated periodically. Electronicversions of the updated manuals are available on the EMC Powerlinkwebsite.

Revision history Beginning with PowerPath 5.5, this document includes a revisionhistory.

The following table presents the revision history of this document.

Conventions used inthis guide

EMC uses the following conventions for notes, cautions, warnings,and danger notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss ordamage to the system or equipment. The caution may apply tohardware or software.

Typographical conventionsEMC uses the following type style conventions in this document:

Revision Date Description

A01 September 3, 2010 First release of the EMC PowerPath ManagementPack for Microsoft Operations Manager Version 5.5User Guide.

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean expressions,

buttons, DQL statements, keywords, clauses, environmentvariables, filenames, functions, utilities

• URLs, pathnames, filenames, directory names, computernames, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels,notifications, system call, man pages

Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types


Preface

Where to get help EMC support, product, and licensing information can be obtained asfollows.

Product information — For documentation, release notes, softwareupdates, or for information about EMC products, licensing, andservice, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC WebSupporton Powerlink. To open a case on EMC WebSupport, you must be aWebSupport customer. Information about your site configuration andthe circumstances under which the problem occurred is required.

Your comments Your suggestions will help us continue to improve the accuracy,organization, and overall quality of the user publications. Please sendyour opinion of this guide to:

[email protected]

Italic: Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis (for example a new term)• Variables

Courier: Used for:• System output, such as an error message or script• URLs, complete paths, filenames, prompts, and syntax when

shown outside of running text

Courier bold: Used for:• Specific user input (such as commands)

Courier italic: Used in procedures for:• Variables on command line• User input variables

< > Angle brackets enclose parameter or variable values supplied bythe user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from theexample

Preface 5

http://powerlink.emc.com

6

Preface


Contents

Preface ............................................................................................................................. 3

Chapter 1 OverviewAbout this Guide............................................................................... 10PowerPath management pack overview....................................... 11

Chapter 2 Installation and DeploymentInstalling the PowerPath management pack ................................ 14Deploying the PowerPath management pack .............................. 16

Chapter 3 Configuring for the SNMP trapsPowerPath SNMP traps ................................................................... 22PowerPath SNMP configuration tool ............................................ 22Monitoring the PowerPath states ................................................... 24

Chapter 4 Components and OperationsPowerPath management pack components for SCOM 2007...... 28PowerPath management pack operations for SCOM 2007......... 31PowerPath management pack components for MOM 2005 ....... 35PowerPath management pack operations for MOM 2005.......... 37

Index ................................................................................................................................ 43

7

EMC PowerPath Management Pack for Microsoft Operations Manager8

1Invisible Body Tag

This chapter provides information about EMC PowerPathManagement Pack for Microsoft Operations Manager (MOM) 2005and Systems Center Operations Manager (SCOM) 2007. Topicsinclude:

◆ About this Guide................................................................................ 10◆ PowerPath management pack overview........................................ 11

Overview

Overview 9

10

Overview

About this GuideThis guide is designed for system administrators who use PowerPathmanagement packs for Microsoft Operations Manager 2005 andMicrosoft System Center Operations Manager 2007 to monitorPowerPath operations.

Users should be familiar with the configuration and operation ofMicrosoft Windows, Microsoft Operations Manager 2005 andMicrosoft System Center Operations Manager 2007. This guide is forindividuals who are experienced with using this software and it isassumed that this level of expertise is available to customers usingthis guide. EMC recommends further review of the productdocumentation of the above mentioned products.


Overview

PowerPath management pack overviewPowerPath management pack has features to remotely monitor theinstallation and operation of PowerPath, and also its paths andvolumes on data networks. Using the management pack, the networkmonitoring solutions can effectively monitor PowerPath by using thetriggers, alerts, and SNMP traps.

The management pack for System Center Operations Manager(SCOM) 2007 help monitor PowerPath on the SCOM 2007 servers,and the management pack for Microsoft Operations Manager (MOM)2005 help monitor PowerPath on the MOM 2005 servers.

The management pack defines the services and components of theSCOM or MOM to be monitored, and also consists of rules toremotely monitor the PowerPath events.

Apart from monitoring the PowerPath and the SCOM or MOM alerts,the management pack also monitors the connectivity. When a path orvolume is unavailable for a specified period, the management packreceives SNMP traps informing about the disconnection.

The MOM alerts are viewed from the console and the SNMP traps areviewed from an SNMP manager.

IMPORTANT!There are some known interoperability issues between differentversions of MOM. For further details, refer to Microsoft productdocumentation on MOM.

EMC PowerPath supportThe PowerPath management pack supports all third-party arrays,including CLARiiON AX systems that use PowerPath versions 5.xand above.

Overview 11

12

Overview

Microsoft Operations Manager supportThe PowerPath management pack is fully qualified to install andoperate with System Center Operations Manager (SCOM) 2007 SP1and Microsoft Operations Manager (MOM) 2005 SP1.

CAUTION!EMC recommends that you do not combine MOM 2005 and SCOM2007 agents on the same client host, as this could result in a conflictof cross talk between the two agents.

Operating systems supportedPowerPath management packs for MOM 2005 and SCOM 2007support the discovery and monitoring of PowerPath running on thefollowing operating systems:

◆ MOM 2005 Management Pack

• Windows 2003 SP1 or SP2 (32-bit)

• Windows 2003 SP1 or SP2 (64-bit for IA-64)

• Windows 2008 R2

◆ SCOM 2007 Management Pack

• Windows 2003 SP1 or SP2 (32-bit)

• Windows 2003 SP1 or SP2 (64-bit for IA-64)

• Windows 2003 with or without SP2 (64-bit)

• Windows 2008 (32-bit and 64-bit)

• Windows 2008 R2


2Invisible Body Tag

This chapter describes the installation and deployment processes ofthe PowerPath management pack, and the process requirements.

◆ Installing the PowerPath management pack ................................. 14◆ Deploying the PowerPath management pack ............................... 16

Installation andDeployment

Installation and Deployment 13

14

Installation and Deployment

Installing the PowerPath management packThe PowerPath management pack is a collection of all the monitoringfunctionalities required to monitor a SCOM 2007 or a MOM 2005setup. Once the management pack is imported, you can view all thecomponents of the management pack, including the rule groups andcomputer groups, which help monitor the Microsoft OperationsManager.

In turn, the Microsoft Operations Manager monitors the PowerPathinstallation and operations.

PrerequisitesBefore installing the PowerPath management pack, meet thefollowing requirements:

1. Ensure that SCOM 2007 or MOM 2005 is already installed andrunning on the server dedicated for monitoring.

2. Ensure that the required agents are already installed and running.

3. Ensure that the configuration tool for PowerPath and thePowerPath SNMP is installed on the client host.

The “PowerPath SNMP configuration tool” on page 22 providesadditional information about installing PowerPath and thePowerPath SNMP configuration tool.

4. Ensure that any previous PowerPath management pack isuninstalled.

A previous installation of PowerPath management pack couldresult in duplicate event and group entries leading tomalfunctioning of the current PowerPath management pack.

5. Ensure that the correct management pack is selected based on theMOM 2005 or SCOM 2007 management server.

EMC provides different management packs for MOM 2005 andSCOM 2007.

Installing the PowerPath management packInstall the PowerPath management pack on a SCOM 2007 or MOM2005 server as follows:



1. Select the appropriate management pack to install.

2. Download the PowerPath management pack from Powerlink andsave it locally.

3. Import the PowerPath management pack into the MicrosoftOperations Manager environment as shown in Figure 1 onpage 15.

Figure 1 Importing the PowerPath management pack

4. Complete the post-installation procedures that discover anddisplay PowerPath servers in the Operations Managerenvironment.


16


Deploying the PowerPath management packAfter the management pack is installed, you can deploy themanagement pack containing all the rules framed for monitoringPowerPath events.

Tasks for deploying the management pack are as follows:

◆ Selecting the Discovery Criteria

◆ Selecting the Discovery Method

◆ Selecting an Administrator Account

◆ Selecting the Computer to be managed

◆ Selecting an Agent Installation Directory

◆ Importing the Management Pack

SCOM 2007 deploymentFollow the steps below to deploy the management pack for SCOM2007:

1. In the Administration pane, right-click Device Management, andselect Discovery Wizard to view the managed computers.

The Device Management screen describes the process ofdiscovering your network and installing agents on the managedcomputers.

2. Click Next.

3. From the Discovery Method screen, select Automatic computerdiscovery or Advanced discovery. If Advanced discovery isselected, specify the discovery criteria.

4. Select the Discovery Method by selecting either the Scan ActiveDirectory or Browse for, or type in computer names options.

5. Click Next.

6. From the Select Objects to Manage screen, select the computeryou want to manage, and click Next.

7. In the Summary screen, you can change the installation directoryof the agent on the managed computer. You can also specify theaction account to be used by the agent.



8. Click Finish.

9. Select Agent Managed in the navigation pane to view themanaged computers.

10. Locate and select the management pack to import in the ImportManagement Pack dialog box.

11. Click Open.

12. Click Import.

The Import Management Packs dialog box shows the importedmanagement pack along with all other imported managementpacks.

13. Open the Monitoring pane and select Discovered Inventory inthe Scope pane.

14. Right-click and select Change target type...

The list of targets is displayed.

15. Select EMC PowerPath Host and click OK.

This step adds members of the target EMC PowerPath Host tothe Discovered Inventory, and is the first step in discovering yourtargets for monitoring.

Note: It may take some time for the members to show up as targets,depending on the query interval set for that target type.

MOM 2005 deploymentFollow the steps below to deploy the management pack for MOM2005.

1. In the Administrator Console, right-click Computer DiscoveryRules and select Create Computer Discovery Rule.

The Computer Discovery Rule dialog box appears.

2. Provide the managed computer information on the ComputerDiscovery Rule screen as follows:

a. In the Management Server field, select the appropriate hostname from the drop-down menu.

b. From the Rule type list, select Include.


18


c. From the Computer name list, select equals.

d. From the Computer type list, select Servers and Clients.

e. From the Initial Management Mode list, selectAgent-managed.

f. Select the Apply query criteria to domain controllers option.

3. Click OK.

The Administrator Console screen appears.

4. Right-click Computer Discovery Rules.

5. Select Run Computer Discovery Now to run the recently createdcomputer discovery rule.

On completion of the running task, the computer is visible in thelist of unmanaged computers.

6. In the Administrator Console's left pane, select UnmanagedComputers and right-click the selected computer.

7. Select Install Agent to install the MOM agent.

8. Follow the instructions on the Install Agent wizard for the agentinstallation on the monitored computers.

9. Click Next to display the Agent Installation Permissions dialogbox.

10. Provide administrator account details and the Agent InstallationDirectory.

11. Click Next.

12. Return to the Administrator console to verify agent installation,listed under Agent-managed computers.

13. In the Administrator Console, right-click Management Packs andselect Import/Export Management Pack to import themanagement pack to setup.

The Welcome to the Management Pack Import/Export Wizardscreen appears.

14. Click Next.

The Import or Export Management Packs screen appears.

15. Select Import Management Packs and /or reports and click Next.

The Management Pack Import/Export Wizard appears.



16. Browse for the folder containing the PowerPath managementpack, select it, and click Next.

17. In the Select Management Packs screen, select the managementpack as the import option.

18. Click Next.

19. Click Finish in the Completing the Management PackImport/Export Wizard to complete the import process.

20. Right-click the PowerPath server or servers to be managed, andclick Run Attribute Discovery Now.

Note: The default Attribute Discovery setting for automateddiscovery is every 60 minutes.

Fine-tuning the PowerPath environmentAn enterprise PowerPath environment should allow the agent to runmultiple responses and enable the host to store higher internalevents.

Fine-tuning the agent hostSometimes the default setting may be too low for an enterprisePowerPath environment to store all the internal events generatedwithin the MOM agent. Increasing temporary storage on the Agenthost achieves a more optimal performance.

To change the agent temporary storage size:

1. In the MOM 2005 Administrator Console, expand these folders:

Administration > Computers > Agent-managed Computers

2. On the Result pane, double click the agent where PowerPath isinstalled.

3. In the Properties dialog box, on the Temporary Storage tab,increase the Maximum disk space setting from the default of 3,000KB (3 MB). EMC recommends a setting of 100,000 KB (100 MB).

4. Clear the Use global settings option to effect this change.

5. Click OK to return to the MOM Administrator Console.


20


6. Commit the configuration change in MOM by right-clicking thetop-level Management Packs folder, and then selecting CommitConfiguration Change.

Fine-tuning the MOM agentThe MOM agent simultaneously runs multiple responses. Increasingthe number of responses lets the MOM agent to cover all the MOMand PowerPath events.

To change agent simultaneous responses allowed:

1. In the MOM 2005 Administrator Console, expand these folders:

Administration > Computers > Agent-managed Computers

2. On the Result pane, double click the agent host that containsPowerPath.

3. In the Properties dialog box, on the Responses tab, increase theSimultaneous responses allowed setting from the default valueof 5. EMC recommends the setting of 100.

4. Clear the Use global settings option to effect this change.

5. Click OK to return to the MOM Administrator Console.

6. Commit the configuration change in MOM by right-clicking thetop-level Management Packs folder, and then selecting CommitConfiguration Change.

Note: Restart the MOM service on the managed host after it receives the newconfiguration file from the server.


3Invisible Body Tag

This chapter provides an overview of the PowerPath SNMP traps andtheir generation by using the SNMP configuration tool.

◆ PowerPath SNMP traps .................................................................... 22◆ PowerPath SNMP configuration tool.............................................. 22◆ Monitoring the PowerPath states .................................................... 24

Configuring for theSNMP traps

Configuring for the SNMP traps 21

22

Configuring for the SNMP traps

PowerPath SNMP trapsA PowerPath SNMP trap is generated when a path or a volumeremains dead for more than the pre-defined time period. ThePowerPath SNMP traps are generated on the managed PowerPathhost. You can forward them to another server (MOM server or anyother server) by making the changes to the SNMP service settings.

The PowerPath SNMP traps can be captured and are viewable from aSNMP manager or any SNMP tool, for example the SNMPUTIL tool.

The following example shows a PowerPath SNMP trap informingabout a dead path:

C:\SNMP>SNMPUTIL.EXE trapsnmputil: listening for traps...snmputil: trap eneric=6 specific=1

from -> 10.31.18.25Variable =.iso.org.dod.internet.private.enterprises.1139.12.1.1.1Value = String EMCP_PATH_DEADVariable =.iso.org.dod.internet.private.enterprises.1139.12.1.1.22Value = String PowerPath: Patch Bus 4 Tgt 1 Lun 3 toAPM00064502060

PowerPath SNMP configuration toolThe SNMP configuration tool help configure the SNMP trapgeneration for the dead path and volume events of the MOM andPowerPath applications.

The PowerPath SNMP configuration tool deploys the followingSNMP binaries on the PowerPath host:

1. SNMP Extension Agent–PPSNMPExtension.dll

2. SNMP Management Application–PPSNMPTrap.exe

The configuration file, pp_delay.config, helps you set the interval themanagement pack waits for the path to MOM becomes active.



Installing the SNMP configuration toolInstall the PowerPath SNMP configuration tool on the agent machinewhere PowerPath is installed.

Note: Installing the Windows SNMP service is a pre-requisite to installing thePowerPath SNMP configuration tool.

To install the PowerPath SNMP configuration tool:

1. Double-click the PowerPath SNMP Configuration Tool thatcomes with the management pack.

2. Click Next to proceed.

3. Click Install to proceed with the installation.

4. Click Finish to exit the installation.

Note: If PowerPath and the SNMP configuration tool are installed in thesame windows session, reboot the machine after the installation.

Uninstalling the SNMP configuration toolFollow the steps below to uninstall the PowerPath SNMPconfiguration tool:

1. Open the Control Panel and double-click Add/RemovePrograms.

2. Select EMC PowerPath SNMP Configuration Tool.

3. Click Remove.

4. When prompted to remove the PowerPath SNMP ConfigurationTool, click Yes.


24


Monitoring the PowerPath statesThe PowerPath management pack monitors PowerPath paths andvolumes, and triggers alerts and SNMP traps based on pre-definedcriterion. You can modify this criterion.

The PowerPath management pack addresses the followingPowerPath states:

◆ PowerPath path is dead—If the path does not come back alivewithin one minute (default interval), then an alert and an SNMPtrap is generated with the path information.

◆ PowerPath volume is dead—If the paths to the volume remaindead for more than five minutes (default interval), then an alertand an SNMP trap is generated with the volume information.

Table 1 on page 24 provides a snapshot of the events monitored byPowerPath management pack 1.0 and the actions taken on theseevents.

Table 1 Events and actions

Index Event nameEventID

Responsecriterion Alert type

SNMPtrap

1 EMCP_EVENT_MP_PATH_IS_DEAD 100 Path is deadfor morethan aconfigurabletime period

Warning Yes

2 EMCP_EVENT_MP_PATH_IS_ALIVE 101 Notapplicable

Notapplicable

No

3 EMCP_EVENT_MP_ALL_PATHS_DEAD 104 All paths toa volumeare dead formore than aconfigurabletime period

CriticalError

Yes

4 EMCP_EVENT_MP_NOT_ALL_PATHS_DEAD

105 Notapplicable

Notapplicable

No



To change the default time periodThe configurable time period is obtained from the configuration filenamed pp_delay.config, which is deployed as part of the SNMPconfiguration tool installation.

A set of registered OIDs (object identifiers) are used for the SNMPtraps that are generated for dead paths and volumes. They are:

1.3.6.1.4.1.1139.12.1.1.1 - for the Path/Volume label

1.3.6.1.4.1.1139.12.1.1.22 - for the Path/Volumeinformation


26



4Invisible Body Tag

This chapter describes the components of the PowerPathmanagement pack and its events.

◆ PowerPath management pack components for SCOM 2007 ....... 28◆ PowerPath management pack operations for SCOM 2007 .......... 31◆ PowerPath management pack components for MOM 2005 ........ 35◆ PowerPath management pack operations for MOM 2005 ........... 37

Components andOperations

Components and Operations 27

28

Components and Operations

PowerPath management pack components for SCOM 2007You can view the various components in the System ConsoleOperations Manager (SCOM) 2007 on the Monitoring and Authoringtabs.

Authoring tab The Authoring tab contains the following PowerPath managementpack components:

◆ Attributes

◆ Rules

◆ Tasks

◆ Views

Attributes In the left-hand pane in Figure 2 on page 29, Attributes is selectedunder Management Pack Objects. In the right-hand pane, the selectedattribute named EMC PowerPath is under the target EMCPowerPath Host, as shown at the bottom of the screen.



Figure 2 SCOM 2007 Authoring tab: Attributes selected

Rules You can view the PowerPath rules designed to monitor PowerPathevents. In Figure 3 on page 30, Rules is selected under ManagementPack Objects. In the right-hand pane, all the rules displayed aredesigned to monitor and track PowerPath dead paths/volumes onPowerPath server (s) that the SCOM server manages.

PowerPath management pack components for SCOM 2007 29

30


Figure 3 SCOM 2007 Authoring tab: Rules selected

Tasks The PowerPath tasks are also viewable in SCOM 2007 underManagement Pack Objects in the left-hand pane. Under EMCPowerPath Hosts in the right-hand pane, you can retrieve versionand license capabilities of the managed PowerPath server.

Views The PowerPath views are also viewable in SCOM 2007 underManagement Pack Objects in the left-hand pane. The PowerPathviews are designed to show the following:

◆ PowerPath servers that are managed by the SCOM server.

◆ Generated PowerPath alerts.

◆ Status of PowerPath tasks run by the administrator.



PowerPath management pack operations for SCOM 2007You can monitor the operations of the pack in the System ConsoleOperations Manager (SCOM) 2007 on the Monitoring tab.

Monitoring tabIn the Monitoring tab, a folder named EMC contains the followingPowerPath management pack components:

◆ EMC PowerPath Alerts

◆ EMC PowerPath Computers

◆ EMC PowerPath Task Status

Alerts In the left-hand pane under EMC, select EMC PowerPath Alerts toview the generated alerts in the right-hand pane. When you selectone of the alerts, you can view the alert details at the bottom of thescreen.

In Figure 4 on page 32, the alert details for the selected alert shows apath that remains dead for more than the pre-defined time period.The Alert Description section shows information on the dead path.

The pre-defined time period refers to the value in the pp_delay.configfile. The first field in this file specifies the interval that is allowed for adead path to become alive. The second field specifies the interval thatis allowed for a dead volume to make at least one path alive.

You can also view alerts that are generated when a volume remainsdead for more than the pre-defined time period. The AlertDescription section shows information about the dead volume.

PowerPath management pack operations for SCOM 2007 31

32


Figure 4 SCOM 2007 Monitoring tab: EMC PowerPath Alerts selected

Computers In the left-hand pane under EMC, select EMC PowerPath Computersto view the PowerPath servers that the SCOM server manages, asshown in Figure 5 on page 32.

Figure 5 SCOM 2007 Monitoring tab: EMC PowerPath Computers selected



Task Status In the left-hand pane under EMC, select EMC PowerPath TaskStatus. The screen displays the status of the PowerPath tasks thathave been run in the past.

License taskYou can retrieve licensing information for the PowerPath licensesinstalled on the managed host.

1. At the Operator console select the Computers view from thenavigation pane as shown in Figure 6 on page 33.

2. Select PowerPath host.

3. Click PowerPath License task in the task pane.

4. Click Run.

5. View the contents of the EMC PowerPath Task Status.

Figure 6 PowerPath License Task for SCOM 2007

PowerPath management pack operations for SCOM 2007 33

34


Version taskYou can retrieve versioning information of PowerPath that isinstalled on the managed host.

1. At the Operator console, select the Computers view from thenavigation pane.

2. Select PowerPath host.

3. Click PowerPath Version task in the task pane.

4. Click Run on the next screen.

5. View the contents of the EMC PowerPath Task Status as shown inFigure 7 on page 34.

Figure 7 PowerPath Version Task for SCOM 2007



PowerPath management pack components for MOM 2005You can view the following components in Microsoft OperationsManager (MOM) 2005 on the MOM 2005 Administrator Console:

◆ Computer Groups

◆ Rule Groups

◆ Computer Attributes

Computer Groups In the Administrator Console’s left-hand pane, select ComputerGroups, under Management Packs. Then select a new computergroup named EMC PowerPath as shown in Figure 8 on page 35.

Figure 8 MOM 2005 Administrator Console: Computer Groups

Rule Groups In the Administrator Console left-hand pane, select Rule Groups,under Management Packs. Then select the new rule group calledEMC PowerPath. The following information is displayed as shown inFigure 9 on page 36.

PowerPath management pack components for MOM 2005 35

36


Figure 9 MOM 2005 Administrator Console: Rule Groups

Computer Attributes In the Administrator Console’s left-hand pane under ManagementPacks, select Computer Attributes. Then select a computer attributecalled EMC PowerPath. This computer attribute is used by the EMCPowerPath computer group to identify which servers havePowerPath installed on them. The list of these servers is located in theAdministrator Console’s right-hand pane as shown in Figure 10 onpage 36.

Figure 10 MOM 2005 Administrator Console: Computer Attributes



PowerPath management pack operations for MOM 2005Invoke the PowerPath MOM 2005 operator console on your desktopas follows:

Start > Programs > Microsoft Operations Manager 2005 >Operator Console

Under Public Views, locate a folder named EMC that contains threePowerPath views as follows:

◆ EMC PowerPath Alerts

◆ EMC PowerPath Computers

◆ EMC PowerPath Task Status

Alerts A PowerPath alert is generated when a path remains dead for morethan the pre-defined time period. The Alert Details section showsinformation on the dead path.

A PowerPath alert is also generated when a volume remains dead formore than the pre-defined time period, and is shown on the AlertDetails section.

PowerPath management pack operations for MOM 2005 37

38


Figure 11 MOM 2005 Operator Console: PowerPath Alerts

Computers In the MOM 2005 Operator Console, select EMC PowerPathComputers under EMC to view the PowerPath servers that the MOMserver manages.

Tasks In the MOM 2005 Operator Console, select EMC PowerPath TaskStatus under EMC to view the PowerPath tasks that have been run,as shown in Figure 12 on page 39.



Figure 12 MOM 2005 Operator Console: PowerPath Task Status

License taskYou can retrieve licensing information for the PowerPath licensesinstalled on the managed host.

1. Select one of the computer instances in the result pane, and clickthe PowerPath License task in the task pane.

The PowerPath License MOM 2005 Launch Task wizard appears.

2. Click Next.

The Command Line Task Parameters screen appears.

3. Click Next.

This step shows the selected agent host on which the task is run.

4. Click Next.

The Completing the Launch Task Wizard screen appears.

5. Click Finish.

6. At the Operator Console, select EMC PowerPath Task Statusunder EMC.


40


Figure 13 PowerPath License Task for MOM 2005



Version taskYou can retrieve versioning information of PowerPath that isinstalled on the managed host.

1. Select one of the computer instances in the result pane and clickthe PowerPath Version task in the task pane.

The Launch Task Wizard screen appears.

2. Click Next.

The command line task parameters screen appears.

3. Click Next to view the selected agent host on which the task isrunning.

4. Click Next again.

The Completion Task Wizard screen appears.

5. Click Finish.

6. In the navigation pane, select Public Views and then select TaskStatus.

Figure 14 PowerPath Version Task for MOM 2005


42



Index

AAdvanced discovery 16alerts 24Automatic computer discovery 16

CCLARiiON AX 11components

management pack 24

Ddeploy the management pack 16deploying

MOM 2005 17SCOM 2007 16

Device Management 16

Ffine-tuning

agent host 19MOM agent 20

IImport

PowerPath management pack 15install

SNMP configuration tool 23

Mmanagement pack 31

deploying 16

installing 14overview 11prerequisites 14

MOM 11

OObject Identifiers 25operating systems 12operations 24

PPowerPath states

Dead Paths 24Path is Alive 24Path is Dead 24

SSCOM 11SNMP trap

binaries 22configuration file 22, 25configuration tool 22overview 22

SNMP traps 24events and states 24

supportfor SCOM 2007 and MOM 2005 12Operating Systems 12third-party array 11

Index 43

44

Index

Uuninstall

SNMP configuration tool 23


powerpath management pack for microsoft … management pack for microsoft operations manager ... 4...

Documents