Sie sind auf Seite 1von 40

White paper

HP Systems Insight Manager with HP Command View EVA

HP Systems Insight Manager

White paper HP Systems Insight Manager with HP Command View EVA HP Systems Insight Manager

White paper | HP Systems Insight Manager

Table of Contents

Terminology

HP Command View EVA overview

HP Systems Insight Manager overview

Installing HP SIM and HP CV EVA

HP CV EVA deployment options

Discovering EVAs in HP SIM

Centralizing event notifications SNMP

EVAs in HP SIM Centralizing event notifications SNMP WBEM Launching HP CV EVA from HP SIM

WBEMEVAs in HP SIM Centralizing event notifications SNMP Launching HP CV EVA from HP SIM Configuring

Launching HP CV EVA from HP SIM

Configuring a trust relationship for HP SIM in HP CV EVA

Viewing EVA LUNs and storage capacity information from HP SIM

Configuring HP CV EVA and HP SIM on a single server Port settings Configuring HP SIM Installing HP SIM for the first time Correcting an existing HP SIM installation Troubleshooting SIM connectivity to Command View SMI-S Using WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA

WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9
WBEMDISCO Restoring defaults to wbemportlist.xml HP CV EVA 2 | March 2013 5 7 8 9

2 | March 2013

5

7

8

9

10

11

13

13

15

23

24

26

27

27

27

27

29

31

31

34

35

White paper | HP Systems Insight Manager

Command View on the EVA 4400

Command View on the EVA 4400

37

Configuring HP CV EVA and HP SIM on different servers

39

Summary

40

White paper | HP Systems Insight Manager

Executive summary

Many businesses today face similar infrastructure challengesunder-utilized server and storage capacity, a great deal of time and money spent on managing the infrastructure, and a relentless demand to meet changing business needs. And with each passing year, the costs associated with the management of the server and storage infrastructure take a larger chunk out of the data center budget.

This white paper describes the integration of HP SIM with HP CV EVA. Key benefits of a unified server and storage management infrastructure follow:

Provides a central point of integration to simplify and consolidate management of the entire server and storage infrastructure. It also reduces deployment time and costs, and facilitates collaboration between traditional islands of server and storage management.unified server and storage management infrastructure follow: Provides centralized event notifications in HP SIM for

Provides centralized event notifications in HP SIM for servers and storage. This is especially beneficial when there are multiple CV EVA servers in the environment. You can simplify and improve response times when managing server-storage infrastructure alerts.traditional islands of server and storage management. Provides more detailed information about EVA events through

Provides more detailed information about EVA events through Insight Remote Support, ideal for both small and large environments that need to integrate remote support capabilities with a centralized management platform. It also provides faster notification and subsequent resolution of server and storage system events in your network.times when managing server-storage infrastructure alerts. Provides a high-level summary of storage utilization for

Provides a high-level summary of storage utilization for EVA.of server and storage system events in your network. The reader should be familiar with HP

The reader should be familiar with HP SIM and HP CV EVA, as well as the HP service tools, such as Insight Remote Support and WEBES.

White paper | HP Systems Insight Manager

Terminology

This document uses the following terms:

Term

Definition

ABM

Array-Based Management

CIMOM

Common Information Model Object Manager

CLI

Command-line interface

CMS

Central Management Station

CV EVA

Command View EVA

DESTA

Distributed Enterprise Service Tools Architecture

ELMC

Event Log Monitoring Collector

EVA

Enterprise Virtual Array

GUI

Graphical user interface

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol over Secure Socket Layer

IRSA

Insight Remote Support Advanced

IRSS

Insight Remote Support Standard

LUN

Logical unit number

MIB

Management Information Base

RSA

Remote Support Advanced

RSE

Remote Support Eligibility

RSS

Remote Support Standard

SAN

Storage area network

SBM

Server-Based Management

SIM

Systems Insight Manager

SMI-S

Storage Management Initiative Specification

SMS

Storage Management Server

5 | March 2013

White paper | HP Systems Insight Manager

SNIA

Storage Networking Industry Association

SNMP

Simple Network Management Protocol

SSL

Secure Sockets Layer

SSO

Single sign-on

SSSU

Storage System Scripting Utility

UI

User interface

UUID

Unique unit identifier

WBEM

Web-Based Enterprise Management

WCC

WEBES Common Components

WEBES

Web-Based Enterprise Services

WMI

Window Management Interface

WWN

World Wide Name

6 | March 2013

White paper | HP Systems Insight Manager

HP Command View EVA overview

The HP CV EVA software suite is used configure, manage, and monitor the EVAs, a family of advanced, enterprise storage arrays from HP. The software suite comprises the following:

HP Command View EVA: Use the GUI for initial configuration, storage provisioning, and ongoing storage system management and : Use the GUI for initial configuration, storage provisioning, and ongoing storage system management and monitoring.

HP Storage System Scripting Utility (SSSU): Use the CLI to script and run repetitive and complex configuration tasks. Go to : Use the CLI to script and run repetitive and complex configuration tasks. Go to www.hp.com/go/cveva and select Support and then the link HP Support & Documents. Then, click Manuals and search for the document HP Storage System Scripting Utility Reference.

HP StorageWorks Command View EVAPerf: Use this tool to monitor array performance. : Use this tool to monitor array performance.

Storage Management Initiative Specification for Enterprise Virtual Array (SMI-S EVA): Install SMI-S EVA on a management server to provide a common management interface in : Install SMI-S EVA on a management server to provide a common management interface in a server- based management environment. This is a standard management interface developed by SNIA to ease the management burden in multivendor SAN environments.

HP CV EVA enables you to do the following:

Manage storage security and passwords.SAN environments. HP CV EVA enables you to do the following: License storage systems. Provision storage

License storage systems.to do the following: Manage storage security and passwords. Provision storage to hosts. Replicate storage using

Provision storage to hosts.storage security and passwords. License storage systems. Replicate storage using HP Business Copy EVA and HP

Replicate storage using HP Business Copy EVA and HP Continuous Access EVA.License storage systems. Provision storage to hosts. Maintain and manage storage systems. 7 | March 2013

Maintain and manage storage systems.Replicate storage using HP Business Copy EVA and HP Continuous Access EVA. 7 | March 2013

7 | March 2013

Monitor storage system events.storage using HP Business Copy EVA and HP Continuous Access EVA. Maintain and manage storage systems.

White paper | HP Systems Insight Manager

HP Systems Insight Manager overview

HP SIM is the foundation for the HP unified server-storage management strategy. HP SIM is a hardware-level management product that supports multiple operating systems on HP ProLiant, Integrity, and HP 9000 servers; HP MSA, EVA, and XP arrays; and third-party arrays. Through a single management view of Microsoft Windows; HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3; and Red Hat and SUSE Linux, HP SIM provides the basic management features for the following:

System discovery and identificationprovides the basic management features for the following: Single-event view Inventory data collection Reporting HP SIM

Single-event viewfor the following: System discovery and identification Inventory data collection Reporting HP SIM uses the

Inventory data collectionSystem discovery and identification Single-event view Reporting HP SIM uses the following: WBEM to deliver the

Reportingidentification Single-event view Inventory data collection HP SIM uses the following: WBEM to deliver the capabilities

HP SIM uses the following:

WBEM to deliver the capabilities required to manage all HP server platformsdata collection Reporting HP SIM uses the following: SMI-S to discover and manage the storage systems

SMI-S to discover and manage the storage systems it supportsHP SIM uses the following: WBEM to deliver the capabilities required to manage all HP server

8 | March 2013

White paper | HP Systems Insight Manager

Installing HP SIM and HP CV EVA

For information about installing and setting up HP SIM and HP CV EVA, see the manuals available on the following webpages:

HP SIM:CV EVA, see the manuals available on the following webpages:

HP CV EVA:

9 | March 2013

White paper | HP Systems Insight Manager

HP CV EVA deployment options

HP CV EVA can be installed on a server called the SBM server. On certain models, it can also be installed on the EVA management module called the ABM module. The way that HP CV EVA is deployed affects the way it interacts with SIM.

Option 1: Command View EVA (SBM) and Systems Insight Manager on separate servers : Command View EVA (SBM) and Systems Insight Manager on separate servers

Option 2: Command View EVA (SBM) and Systems Insight Manager on the same server : Command View EVA (SBM) and Systems Insight Manager on the same server

Option 3: Command View EVA (SBM) and Command View EVA (ABM) and Systems Insight Manager : Command View EVA (SBM) and Command View EVA (ABM) and Systems Insight Manager

Option 4: Command View EVA (ABM) and Systems Insight Manager : Command View EVA (ABM) and Systems Insight Manager

For options 3 and 4, the IP address of HP CV EVA on the ABM module must be added to the SMI-S proxy list. For details, see Configuring HP SIM and HP CV EVA on a single server.

White paper | HP Systems Insight Manager

Discovering EVAs in HP SIM

To enable HP SIM to discover each Command View instance and the EVAs:

1. Launch HP SIM, and then select OptionsDiscovery. See Figure 1.

Figure 1: Add a new discovery taskStep 1

Figure 1 . Figure 1: Add a new discovery task — Step 1 2. To create

2. To create a new discovery task, click New, and then select the option that you want (Discover a group of systems or Discover a single system). To discover a group of systems, click Help with Syntax. By default, the Schedule option is selected. Clear this option if it is not needed; you can reschedule the task later. See Figure 2.

Figure 2: Add a new discovery taskStep 2

Figure 2 . Figure 2: Add a new discovery task — Step 2 3. Click Credentials

3. Click Credentials, and then enter the sign-in credentials for HP CV EVA. See Figure 3.

You can also configure global credentials by using Configure Global Credentials. See Figure 1.

White paper | HP Systems Insight Manager

Figure 3: Add a new discovery taskStep 3

Manager Figure 3: Add a new discovery task — Step 3 4. The newly created discovery

4. The newly created discovery task appears on the OptionsDiscovery page. Select the new discovery task, and then click Run Now to start the discovery and initial data collection. See Figure 1.

5. After the discovery and initial data collection is completed, click All Systems in the navigation pane to see all discovered systems. Select a system and browse through it for detailed information. See Figure 4.

Figure 4: View all discovered systems

See Figure 4 . Figure 4: View all discovered systems Note: For more information about a

Note: For more information about a particular state, point to the state, such as ?, i, or !.

White paper | HP Systems Insight Manager

Centralizing event notifications

HP SIM can receive events by using SNMP or WBEM.

SNMP

1. In HP CV EVA, configure the following under System Options:

SNMP event notification: Select all events or specified events to be notified, and save the changes. : Select all events or specified events to be notified, and save the changes.

SNMP host notification: Add the IP address of the HP SIM server, and save the changes. : Add the IP address of the HP SIM server, and save the changes.

2. Ensure that SNMP services are running on both the HP SIM and HP CV EVA servers. You can use Windows Service Manager to check for SNMP services that include SNMP Service and SNMP Trap Service. If you do not find these two components in Windows Service Manager, go to Windows Control PanelAdd or Remove Programs, and click Add/Remove Windows Components. In the Windows Component Wizard that appears, select Management and Monitoring Tools and install it. If HP SIM and HP CV EVA reside on a single server, check for SNMP services only on that server.

3. In Command View, go to System OptionsConfigure SNMP/event log notificationConfigure events for SNMP/event log notification. Click Get MIB to download and save the MIB files for the required EVA types. The MIB file is saved with a .mib.idi extension. Remove the .idi extension, and then save the file with only the .mib extension. See Figure 5.

Figure 5: Locating the MIB file in HP CV EVA

See Figure 5 . Figure 5: Locating the MIB file in HP CV EVA 4. Copy

4. Copy the saved MIB file to the following location on the HP SIM server:

C:\Program Files\HP\Systems Insight Manager\mibs\

White paper | HP Systems Insight Manager

5. Open a command window on the HP SIM server, and then enter the following path:

C:\Program Files\HP\Systems Insight Manager\mibs

6. Execute the mcompile <MIB file> command (for example, mcompile

eva6400.mib).

The system generates a .cfg file (eva6400.cfg in this example) and displays the following output in the command window (Figure 6):

Figure 6: Compiling the MIBs in HP SIM

window ( Figure 6 ): Figure 6: Compiling the MIBs in HP SIM 7. Execute the

7. Execute the command mxmib -a <cfg file> (for example, mxmib a evapamib.cfg). This registers the new CFG, <myfile.cfg>, or replaces the data of a previously registered MIB.

Figure 7 shows the output that appears in the command window.

Figure 7: Registering the MIBs in HP SIM

appears in the command window. Figure 7: Registering the MIBs in HP SIM 8. Restart the

8. Restart the HP SIM service.

White paper | HP Systems Insight Manager

Snapshot of events from HP SIM

To see all events from HP SIM, click All Events in the navigation pane. See Figure 8.

Figure 8: Snapshot of events from HP SIM

See Figure 8 . Figure 8: Snapshot of events from HP SIM Sample SNMP events On

Sample SNMP events

On the Event Details page, the SNMP event name is prefixed by (SNMP).See Figure 9.

Figure 9: SNMP events

by “ (SNMP). ” See Figure 9 . Figure 9: SNMP events WBEM WEBES and EVA

WBEM

WEBES and EVA 4400

Command View V9.1 and later for ABM includes ELMC (WCCProxy) running on the ABM. This provides WEBES with a connection point to the array event data.

WEBES retrieves Managed Entity information from HP SIM when operating on the RSA CMS. HP SIM communicates with the array through the WBEM protocol by using the SMI-S provider, and WEBES communicates with the array by using a network connection to ELMC (WCCProxy).

White paper | HP Systems Insight Manager

The following sections explain how to set up HP SIM and WEBES to monitor the array.

Remote Support Advanced (RSA)

First, you must set up the Command View Protocol credentials in the WEBES UI. This enables the correct ELMC protocol to be selected when WEBES discovers the array and ABM.

The ABM firmware does not include SNMP or WBEM agents to support HP SIM communication for retrieval of hardware information. Therefore, certain fields must be set manually. The HP SIM System and Entitlement information is tightly coupled with the WEBES Managed Entity information.

WEBES detects the presence of HP SIM. Then, it populates the Managed Entity information based on what is defined in HP SIM for newly added systems or changes made to existing systems. For more information about WEBES, IRSS, and IRSA, see the manuals available on the following webpages:

support/supportpack/index.html

The synchronization of this information causes the entity discovered by WEBES to be left in an incomplete and unrecoverable state if any of the required fields are missing. You may have to delete the Managed Entity from the WEBES UI and rediscover it after all required information is entered in HP SIM. To trigger rediscovery, stop and restart the DESTA service.

To set up the EVA 4400 and ABM in HP SIM:

1. Discover the EVA 4400 array (managed by ABM) in HP SIM by performing a discovery to the server running SMI-S that has been set up to connect to the ABM by using discoverer.bat, or an SMS running SMI-S and managing the array. (See Configure HP SIM and HP CV EVA on a single server for information about using discoverer.bat to set up SMI-S to connect to ABM.)

2. Edit the System Properties in HP SIM for the discovered EVA array, including the Contract and Warranty information, Site Name, and Primary Contact. These fields are required for HP SIM to present this entitlement data to the WEBES Managed Entity. The Customer-Entered Serial Number and Customer-Entered Product Number settings are not required for the EVA 4400 array because WEBES retrieves this information from the array for the EVA Managed Entity.

3. In HP SIM, discover the ABM by providing the IP address of the ABM module, and set the System Name to be the fully qualified domain name for the ABM. This is required for the WEBES Managed Entity to correctly detect and add the ABM as a connection for the EVA.

4. Edit the System Properties in HP SIM for the discovered ABM. This is a placeholder in the HP SIM System List, but there are fields required for WEBES to create a Managed Entity and pass the RSE list check. Complete the following fields:

o

System type = Storage Device

o

System subtype = Storage

o

Product model = EVA ABM

White paper | HP Systems Insight Manager

In Figure 10, EVA is required in the Product model and Hardware description fields for the RSE check. ABM is included in this example as a way to differentiate between the ABM and the array in the HP SIM UI.

Figure 10: ABM Module System PropertiesSection 1

UI. Figure 10: ABM Module System Properties — Section 1 In Figure 10 , the Hardware

In Figure 10, the Hardware description field has also been populated for the ABM. This is not required, but it is a convenient location to add information presented in the HP SIM UI.

Entitlement Information:location to add information presented in the HP SIM UI. o Customer-Entered Serial Number o

o

Customer-Entered Serial Number

o

Customer-Entered Product Number

To obtain this information, select Command View UIarray-nameHardwareController Enclosure.

The following fields are required for WEBES to set up the ABM Entity correctly:

Site nameare required for WEBES to set up the ABM Entity correctly: Primary customer contact Figure 11

Primary customer contactfor WEBES to set up the ABM Entity correctly: Site name Figure 11 shows the Entitlement

Figure 11 shows the Entitlement Information, Site name, and Primary customer contact settings.

White paper | HP Systems Insight Manager

Figure 11: ABM Module System PropertiesSection 2

Figure 11: ABM Module System Properties — Section 2 The WEBES Managed Entity UI should now

The WEBES Managed Entity UI should now display the EVA 4400 array and the ABM module.

Remote Support Standard (RSS)

WEBES cannot obtain the entitlement information from HP SIM because it is not installed on the RSS. The Managed Entity information is entered manually using the WEBES Managed Entity UI.

To add the EVA 4400 array:

1. Add the ABM module to the WEBES Managed Entity UI using the fully qualified domain name.

The orange-bar status indicates that the ABM entity requires information. See Figure 12.

Figure 12: WEBES Managed EntityStep 1

See Figure 12 . Figure 12: WEBES Managed Entity — Step 1 2. When you select

2. When you select the ABM entity name, the Entitlement Serial Number and Entitlement Product Number fields are displayed. See Figure 13.

Figure 13: WEBES Managed EntityStep 2

See Figure 13 . Figure 13: WEBES Managed Entity — Step 2 3. Add the information

3. Add the information required for the ABM entity in the Entitlement Serial Number and Entitlement Product Number fields.

White paper | HP Systems Insight Manager

These fields are required for WEBES to set up the ABM entity correctly. The information can be obtained through Command View UIarray-nameHardwareController Enclosure. See Figure 14.

Figure 14: Controller enclosure information

See Figure 14 . Figure 14: Controller enclosure information After the required information is added and

After the required information is added and saved, WEBES connects to the ABM module and discovers the EVA 4400.

The Managed Entity information for the EVA 4400 array, including the serial number and model number, has been completed by the WEBES discovery of the array, along with the WWN, UUID, and path to the array. See Figure 15.

Figure 15: WEBES Managed Entity Properties for EVA 4400 array

and path to the array. See Figure 15 . Figure 15: WEBES Managed Entity Properties for

White paper | HP Systems Insight Manager

To receive events through WBEM:

1. In HP SIM, subscribe to WBEM events by selecting all of the EVAs. Then, select OptionsEventsSubscribe to WBEM Events. See Figure 16.

To unsubscribe from WBEM events, select OptionsEventsUnsubscribe to WBEM Events.

Figure 16: Subscribing to WBEM events from HP SIMStep 1

Figure 16: Subscribing to WBEM events from HP SIM — Step 1 2. Follow the instructions

2. Follow the instructions in Step 1: Verify Target System and Step 2: Task Confirmation, and then click Run Now.

After the operation is complete, subscription to WBEM events is shown as being successful. See Figure 17.

Figure 17: Subscribing to WBEM events from HP SIMStep 1

shown as being successful. See Figure 17 . Figure 17: Subscribing to WBEM events from HP

White paper | HP Systems Insight Manager

Sample WBEM events

Each WBEM event name on the Event Details page is prefaced by WBEM. See Figure 18.

Figure 18: WBEM events

prefaced by WBEM . See Figure 18 . Figure 18: WBEM events Using WEBES instead of

Using WEBES instead of SNMP is advantageous because WEBES provides a higher-quality event as an alert indication. If WEBES is configured to send Type 3 traps, the SMI-S provider includes event severities in alert indications sent to HP SIM.

Actions that can be taken in HP SIM based on events

Send pageHP SIM. Actions that can be taken in HP SIM based on events Send email Run

Send emailthat can be taken in HP SIM based on events Send page Run custom CMS tool

Run custom CMS toolcan be taken in HP SIM based on events Send page Send email Assign Forward as

AssignSIM based on events Send page Send email Run custom CMS tool Forward as SNMP trap

Forward as SNMP trapHP SIM based on events Send page Send email Run custom CMS tool Assign Write to

Write to system logHP SIM based on events Send page Send email Run custom CMS tool Assign Forward as

Clear eventbased on events Send page Send email Run custom CMS tool Assign Forward as SNMP trap

White paper | HP Systems Insight Manager

To learn how to configure actions, select the following in HP SIM (Figure 19):

Options Events  Automatic Event Handling  New Task EventsAutomatic Event HandlingNew Task

Options Events  Automatic Event Handling  E-mail Settings EventsAutomatic Event HandlingE-mail Settings

For more information, see the HP Systems Insight Manager User Guide.

Figure 19: Define a new task to perform an action based on events

Systems Insight Manager User Guide . Figure 19: Define a new task to perform an action

White paper | HP Systems Insight Manager

Launching HP CV EVA from HP SIM

To launch HP CV EVA from HP SIM:

1. In the navigation pane, select SystemsSharedSystems by TypeStorage SystemsAll Storage Systems.

2. Select an EVA that has been discovered.

In the content pane, the following tabs appear:

Systemdiscovered. In the content pane, the following tabs appear: Tools & Links Events Essentials 3. Click

Tools & LinksIn the content pane, the following tabs appear: System Events Essentials 3. Click the Tools &

Eventspane, the following tabs appear: System Tools & Links Essentials 3. Click the Tools & Links

Essentialsthe following tabs appear: System Tools & Links Events 3. Click the Tools & Links tab.

3. Click the Tools & Links tab.

4. Click URL of the Command View EVA web-based element manager. See Figure 20.

5. On the HP CV EVA login page that is displayed, enter the HP CV EVA user name and password.

Figure 20: Launching HP CV EVA from HP SIM

is displayed, enter the HP CV EVA user name and password. Figure 20: Launching HP CV

White paper | HP Systems Insight Manager

Configuring a trust relationship for HP SIM in HP CV EVA

Currently, the SSO feature is disabled for HP CV EVA in HP SIM. However, the following procedure explains how to configure SSO in HP SIM for HP CV EVA. This feature is enabled in HP SIM 6.0 and HP CV EVA 9.2.

Adding a trust relationship enables you to automatically log in to HP CV EVA from HP SIM. This feature is sometimes called SSO. HP CV EVA imports a certificate from a trusted source, such as HP SIM. Users who are authenticated by HP SIM are then allowed to automatically authenticate by using HP CV EVA without logging in again.

If you prefer to have HP CV EVA users log in each time, do not create the trust relationship. Click Uninstall Certificates to remove the trust relationship and require each user to log in to HP CV EVA.

1. Launch HP CV EVA. Go to Server Options, and then click SIM/RSM trust relationships. See Figure 21.

Figure 21: Trust relationshipStep 1

and then click SIM/RSM trust relationships . See Figure 21 . Figure 21: Trust relationship —

White paper | HP Systems Insight Manager

2. Enter the HP SIM server IP address in the Server field, and then click Install Certificate. See Figure 22.

The trust relationship is established successfully. See Figure 23.

Figure 22: Trust relationshipStep 2

See Figure 23 . Figure 22: Trust relationship — Step 2 Figure 23: Trust relationship —

Figure 23: Trust relationshipStep 3

See Figure 23 . Figure 22: Trust relationship — Step 2 Figure 23: Trust relationship —

White paper | HP Systems Insight Manager

Viewing EVA LUNs and storage capacity information from HP SIM

To view the EVA LUNs:

1.

In the navigation pane, select SystemsSharedSystems by TypeStorage SystemsAll Storage Systems.

2.

Select an EVA that has been discovered.

3.

In the content pane, the following categories appear on the System tab:

Identification Product Description Firmware and Software revision Ports Storage Volumes Capacity Information

4.

Expand the Storage Volumes tree to see all LUNs for the EVA.

You can also view EVA storage capacity information by expanding the Capacity Information tree in HP SIM. See Figure 24.

To obtain information about the LUNs presented to a host, in HP SIM, discover the host to which the LUNs are presented.

Figure 24: Viewing LUN and storage capacity information

the host to which the LUNs are presented. Figure 24: Viewing LUN and storage capacity information

White paper | HP Systems Insight Manager

Configuring HP CV EVA and HP SIM on a single server

Port settings

The default port assignment of 5989 for WBEM/WMI and SMI-S has created an issue for several versions. The following sections describe the changes that address the port-assignment issue and provide a solution for setting up HP SIM with Command View SMI-S on the same server.

The installation sequence for HP SIM and Command View SMI-S on a CMS affects the default port settings. The current Best Practices suggestion is to install HP SIM first and allow the WMI Mapper to use the default port 5989. The subsequent Command View installation can detect if port 5989 is in use, and can redirect to a different port.

To obtain a snapshot of the customer environment for the currently assigned ports, in a command window, execute the following command:

C:\ netstat -anb >netstat.txt

Configuring HP SIM

This section describes how to install HP SIM for the first time. It also explains how to correct an existing HP SIM installation.

Installing HP SIM for the first time

When installing HP SIM for the first time, the First Time Wizard includes a step to configure WBEM/WMI Mapper Proxy. See Figure 25.

Figure 25: WBEM/WMI Mapper ProxyFirst Time Wizard

25 . Figure 25: WBEM/WMI Mapper Proxy — First Time Wizard Keep the default setting of

Keep the default setting of port 5989. After you complete the installation of HP SIM, add the port that Command View SMI-S will use to the .xml file shown in step 1 of the following procedure.

White paper | HP Systems Insight Manager

Follow these steps to identify the port that HP SIM will use to connect to SMI-S. In this example, port 60000 is used for the SMI-S HTTPS connection to the interop namespace.

1. Open the following file:

C:\Program Files\HP\Systems Insight Manager\config\identification\wbemportlist.xml

2. Add the following lines of text to the end of the file:

<port id=“60000” protocol=“https”>

<interopnamespacelist>

<interopnamespace name=“interop”/>

</interopnamespacelist>

</port>

The following example shows the complete file after you add the port for SMI-S:

<?xml version=“1.0” encoding=“UTF-8”?>

<wbemportlist>

<port id=“5989” protocol=“https”>

<cimnamespacelist>

<cimnamespace name=“root/cimv2”/>

<cimnamespace name=“vmware/esxv2”/>

<cimnamespace name=“root/hpq”/>

</cimnamespacelist>

<interopnamespacelist>

<interopnamespace name=“root/pg_interop”/>

<interopnamespace name=“root”/>

<interopnamespace name=“root/emulex”/>

<interopnamespace name=“root/qlogic”/>

<interopnamespace name=“root/ibm”/>

<interopnamespace name=“root/emc”/>

<interopnamespace name=“root/smis/current”/>

<interopnamespace name=“root/hitachi/dm51”/>

<interopnamespace name=“interop”/>

<interopnamespace name=“root/interop”/>

<interopnamespace name=“root/switch”/>

<interopnamespace name=“root/cimv2”/>

White paper | HP Systems Insight Manager

</interopnamespacelist>

</port>

<port id=“60000” protocol=“https”>

<interopnamespacelist>

<interopnamespace name=“interop”/>

</interopnamespacelist>

</port>

</wbemportlist>

3. Save the changes.

4. Restart the HP SIM service.

Correcting an existing HP SIM installation

Important: Do not use the following procedure if this is a first-time installation of HP SIM. Use this procedure only if HP SIM has already been installed and the WMI Mapper port has been changed to something (for example, 6989) other than the default (5989).

To restore the WMI Mapper port to the default port:

1. Stop the Pegasus WMI Mapper service.

2. Open the following file:

C:\Program Files\The Open Group\WMI Mapper\cimserver_planned.conf

3. In the line that includes httpsPort=6989, change the port number to 5989.

The port number may have already been set to something other than 6989; it is used here as an example only.

4. Save the file.

5. Restart the Pegasus WMI Mapper service.

6. Execute the netstat command, and verify that the change has been made.

Note: The changes made in the cimserver_planned.conf file will be applied to the cimserver_current.conf file after the service is restarted.

An example of a cimserver_planned.conf file follows:

enableRemotePrivilegedUserAccess=true

enableHttpsConnection=true

enableHttpConnection=false

sslCertificateFilePath=C:\hp\sslshare\cert.pem

sslKeyFilePath=C:\hp\sslshare\file.pem

httpsPort=5989

White paper | HP Systems Insight Manager

To change the WMI Mapper Proxy port in HP SIM:

1. Log in to HP SIM with Administrative privileges.

2. Verify that the credentials for the CMS are correct:

a. Open the All Systems list and select the HP SIM CMS from the list.

b. Click the Tools & Links tab.

c. Click System Credentials.

d. Select the check box for the CMS instance of WMI Mapper that is running on the local host.

e. Click Edit system credentials.

f. Verify that the sign-in credentials exist and are correct for the CMS (preferred), or that there are advanced WBEM settings. Also, verify that the port number is 5989, and that the credentials are correct for the WMI Mapper. See Figure 26.

Figure 26: CMS system credentials

Mapper. See Figure 26 . Figure 26: CMS system credentials g. Select Options  Protocol Settings

g. Select OptionsProtocol SettingsWMI Mapper Proxy.

h. Select the CMS instance of WMI Mapper that is running on the local host.

i. Click Edit.

j. Enter 5989 in the Port number field.

k. Click OK to save the settings. See Figure 27.

White paper | HP Systems Insight Manager

Figure 27: WBEM/WMI Mapper ProxyProtocol Settings

Figure 27: WBEM/WMI Mapper Proxy — Protocol Settings Troubleshooting SIM connectivity to Command View SMI-S If

Troubleshooting SIM connectivity to Command View SMI-S

If the discovery process fails to find the Command View server and gather information about the EVAs, you can use the WBEMDISCO tool to determine if the SMI-S provider is responding and that the credentials are correct. WBEMDISCO is installed automatically by SIM.

Using WBEMDISCO

WBEMDISCO is packaged with HP SIM. To use WBEMDISCO:

1. Open a command window.

2. Enter the following path:

C:\Program Files\HP\Systems Insight Manager

On a 64-bit version of Windows, the path is as follows:

C:\Program Files (x86)\HP\Systems Insight Manager

3. Execute WBEMDISCO.CMD from the command line.

White paper | HP Systems Insight Manager

The following dialog box appears:

HP Systems Insight Manager The following dialog box appears: 4. In the Profile Name field, enter

4. In the Profile Name field, enter a name for the profile (optional).

5. Specify the IP address of the server on which SMI-S is installed, and the port (either HTTP or HTTPS) on which SMI-S is running.

6. Specify the root namespace for CXWS CIMOM (interop) and the SMI-S user name and password credentials.

7. Click Run.

White paper | HP Systems Insight Manager

After WBEMDISCO has finished checking the SMI-S provider response and credentials, the following output is displayed, listing the discovered EVAs:

following output is displayed, listing the discovered EVAs: If the credentials are not correct, WBEMDISCO displays

If the credentials are not correct, WBEMDISCO displays a message similar to the following:

WBEMDISCO displays a message similar to the following: If this occurs, verify that the HP Storage

If this occurs, verify that the HP Storage Admins group on the CV EVA server contains the specified user name and password.

White paper | HP Systems Insight Manager

Restoring defaults to wbemportlist.xml

1. Open the following file:

C:\Program Files\HP\Systems Insight Manager\config\identification\wbemportlist.xml

2. Remove the following lines from the file:

<!-- WMI Mapper httpsPort=6989 -->

<port id=“6989” protocol=“https”>

<cimnamespacelist>

<cimnamespace name=“root/cimv2”/>

</cimnamespacelist>

</port>

3. Add the following lines to the end of the file. In this example, the port number 60000 is used as the HTTPS port for SMI-S.

</port>

<port id=“60000” protocol=“https”>

<interopnamespacelist>

<interopnamespace name=“interop”/>

</interopnamespacelist>

</port>

The following example shows the complete file, with port number 60000 used as the HTTPS port for SMI-S:

<?xml version=“1.0” encoding=“UTF-8”?>

<wbemportlist>

<port id=“5989” protocol=“https”>

<cimnamespacelist>

<cimnamespace name=“root/cimv2”/>

<cimnamespace name=“vmware/esxv2”/>

<cimnamespace name=“root/hpq”/>

</cimnamespacelist>

<interopnamespacelist>

<interopnamespace

name=“root/pg_interop”/>

<interopnamespace name=“root”/>

White paper | HP Systems Insight Manager

<interopnamespace name=“root/emulex”/>

<interopnamespace name=“root/qlogic”/>

<interopnamespace name=“root/ibm”/>

<interopnamespace name=“root/emc”/>

<interopnamespace

name=“root/smis/current”/>

<interopnamespace

name=“root/hitachi/dm51”/>

<interopnamespace name=“interop”/>

<interopnamespace name=“root/interop”/>

<interopnamespace name=“root/switch”/>

<interopnamespace name=“root/cimv2”/>

</interopnamespacelist>

</port>

<port id=“60000” protocol=“https”>

<interopnamespacelist>

<interopnamespace name=“interop”/>

</interopnamespacelist>

</port>

</wbemportlist>

4. Save the changes.

5. Restart the HP SIM service.

6. Select OptionsIdentify Systems. Re-identify all WBEM/WMI systems in HP SIM to correct the port reference.

HP CV EVA

The HP CV EVA installation kit includes SMI-S as a component. At installation time, SMI-S assigns the following as default ports if they are available:

HTTP port=5988the following as default ports if they are available: HTTPS port=5989 If one or both of

HTTPS port=5989as default ports if they are available: HTTP port=5988 If one or both of these ports

If one or both of these ports are in use, a screen appears on which you can change the port numbers. The SMI-S installer suggests port 60000 if that port is not in use. SMI-S retains port 5988 if it does not conflict with another port number. SMI-S uses these ports when the HP CIMOM process starts.

Note: This screen appears only if a port conflict is detected, which is why HP recommends installing HP SIM before installing Command View.

White paper | HP Systems Insight Manager

Figure 28 shows an example of SMI-S installation on an RSA host that already has HP SIM installed with WMI Mapper.

Figure 28: Installing SMI-S on an RSA with HP SIM

Mapper. Figure 28: Installing SMI-S on an RSA with HP SIM After the ports are set,

After the ports are set, you can verify them by executing the netstat command as described in Port settings. The following output is displayed:

TCP

0.0.0.0:5988 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]

TCP

0.0.0.0:5989 0.0.0.0:0 LISTENING 460 [WMIServer.exe]

TCP

0.0.0.0:60000 0.0.0.0:0 LISTENING 1712 [JavaWrapper.exe]

In this example (Figure 28), SMI-S is set up to use ports 5988 and 60000.

To reset the port numbers if Command View is already installed:

1. Open the following file:

C:\Program Files\Hewlett-Packard\SMI- S\CXWSCimom\config\cxws.properties

2. Locate the cxws.http.port and cxws.https.port entries and set them to the following values:

cxws.http.port=5988

cxws.https.port=60000

3. Restart the HP CIMOM service.

White paper | HP Systems Insight Manager

Command View on the EVA 4400

The SMI-S provider cannot be installed on the ABM. SMI-S must be installed elsewhere in the LAN to serve as a proxy connection to the array.

The Command View installation kit enables SMI-S to be installed on a server independently. SMI-S can be installed on the HP SIM CMS or any other server in the LAN.

SMI-S includes a utility named discoverer.bat for setting up the connection to the array ABM. This allows SMI-S to pass connection requests to the array by having the IP address and credentials for the target ABM. To invoke this procedure, double-click the following file:

C:\Program Files\Hewlett-Packard\SMI- S\EVAProvider\bin\discoverer.bat

A command window opens. See Figure 29.

The first line of text shows http://localhost:5988 defined as the default path to where SMI-S is running. This HTTP port may have been changed if it was operating on the CMS, as described in Port settings.

The second and third lines require the credentials of the account that was set up for HP Storage Group access. After you enter the credentials, the menu is displayed. See Figure 29.

Figure 29: Setting up SMI-S Proxy for ABMStep 1

29 . Figure 29: Setting up SMI-S Proxy for ABM — Step 1 1. Select 1

1. Select 1 to add a Command View IP address.

2. Enter the IP address and credentials for Command View on the ABM. The IP address of the HP CV EVA on ABM must be added successfully. See Figure 30.

White paper | HP Systems Insight Manager

Figure 30: Setting up SMI-S Proxy for ABMStep 2

Manager Figure 30: Setting up SMI-S Proxy for ABM — Step 2 3. Select 3 to

3. Select 3 to view a list of the Command View IPs. See Figure 31.

Figure 31: Setting up SMI-S Proxy for ABMStep 3

31 . Figure 31: Setting up SMI-S Proxy for ABM — Step 3 If Command View

If Command View is installed on the local host that is running discoverer.bat, you will also see the IP address of the local host in this list.

4. Enter 0 to exit the discoverer.bat utility.

5. Restart the HP CIMOM service.

Now that SMI-S has a connection to the ABM, HP SIM can discover the EVA 4400 array that is being managed on the ABM by doing a discovery of the server running SMI-S.

White paper | HP Systems Insight Manager

Configuring HP CV EVA and HP SIM on different servers

When HP SIM and HP CV EVA are installed on different servers, a port conflict on port 5989 does not occur. Follow the installation procedures for HP SIM and HP CV EVA described in the installation guide.

White paper | HP Systems Insight Manager

Summary

The benefits of a unified server and storage infrastructure are very compelling. HP SIM, together with HP CV EVA, provides a solid foundation for a unified server-storage management strategy.

Sign up for updates hp.com/go/getupdated

Share with colleagues
Share with colleagues
up for updates hp.com/go/getupdated Share with colleagues Rate this document © Copyright 2010, 2013 Hewlett-Packard

Rate this document