Configuring and Monitoring Hitachi SAN Servers Implementer's... · · 2014-02-01table of contents...

Configuring and Monitoring Hitachi SAN Servers

eG Enterprise v5.6

Restricted Rights Legend

The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eG Innovations, Inc. eG Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

Trademarks

Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Copyright

© 2012 eG Innovations, Inc. All rights reserved.

Table of Contents CONFIGURING AND MONITORING THE HITACHI AMS SAN ...................................................................................................1

1.1 COFIGURING THE EG AGENT TO MONITOR THE HITACHI AMS SAN ............................................................................................1 1.2 ADMINISTERING THE EG MANAGER TO WORK WITH THE HITACHI AMS SAN.............................................................................3 1.3 MONITORING THE HITACHI AMS SAN SERVER.............................................................................................................................8

CONFIGURING AND MONITORING THE HITACHI USP SAN.....................................................................................................9 2.1 CONFIGURING THE EG AGENT TO MONITOR THE HITACHI USP SAN ...........................................................................................9 2.2 ADMINISTERING THE EG MANAGER TO MONITOR THE HITACHI USP SAN SERVER...................................................................10 2.3 MONITORING THE HITACHI USP SAN ..........................................................................................................................................14

CONCLUSION..........................................................................................................................................................................................15

Table of Figures

Figure 1.1: Adding a Hitachi AMS SAN server...........................................................................................................................................3 Figure 1.2: List of Unconfigured tests to be configured for the Hitachi AMS SAN server .......................................................................4 Figure 1.3: Configuring the Cache Memory Usage test ..............................................................................................................................4 Figure 1.4: Configuring the Cache Load test................................................................................................................................................5 Figure 1.5: Configuring the Trap Status test ................................................................................................................................................6 Figure 2.1: Adding a Hitachi USP SAN server ..........................................................................................................................................10 Figure 2.2: List of Unconfigured tests to be configured for the Hitachi USP SAN server.......................................................................11 Figure 2.3: Configuring the Battery Status test ........................................................................................................................................11 Figure 2.4: Configuring the Nsc Traps test.................................................................................................................................................12

C o n f i g u r i n g a n d M o n i t o r i n g t h e H i t a c h i A M S S A N

1

Configuring and Monitoring the Hitachi AMS SAN

1.1 Cofiguring the eG Agent to Monitor the Hitachi AMS SAN

For collecting these performance statistics, the eG agent uses both the following information sources:

The Performance Monitor software that is installed with the storage device;

The SNMP MIB of the device;

The Performance Monitor is a controller-based software application that acquires information on the performance of RAID groups, logical units, and other elements of the disk subsystem while tracking the utilization rates of resources such as hard disk drives and processors. To periodically run the Performance Monitor application and to extract the metrics of interest from the storage device, a client utility named the Storage Navigator Modular (AMS) must be available on the eG agent host.

The tests that need to access the Performance Monitor should then be configured with the path to the Storage Navigator. This way, whenever that test is run, the eG agent executing the test automatically invokes the storage navigator client via CLI, which then connects to the storage device, accesses the Performance Monitor on the device, and extracts the desired metrics.

A few other tests executed by the eG agent collect the statistics of interest using SNMP-based access to the MIB statistics of the storage device. For these tests to work, you first need to SNMP-enable the storage device.

While you need to configure a remote agent for accessing the Performance Monitor software and collecting metrics, an external agent is necessary for performing the SNMP-based monitoring.

Chapter

1

Note: If need be, you can configure a ‘single agent’ to function both as a remote agent and as an external agent for monitoring the Hitachi AMS.


2

To ensure that the eG agent is able to use both the Performance Monitor and the SNMP MIB (of the device) effectively for collecting metrics from the Hitachi AMS, the following pre-requisites should be fulfilled:

The SNMP service should be enabled on the device;

The eG SNMP trap receiver service should be installed on the external agent host;

SNMP traps should be enabled on the device and configured to send traps to the external agent host;

The Hitachi Performance Monitor software should be available;

The Storage Navigator Modular (AMS) Version 7.0 or later should be available on the remote agent host;

The Storage Navigator Modular (AMS) Version 7.0 or later should be able to connect to the storage unit being monitored, without requiring any user permissions.

The eG agent can monitor only those storage units that are registered with the Storage Navigator Modular (AMS) Version 7.0 or later; if a target unit is neither discovered nor registered with the SNClient, do the following:

i. Login to the host on which the Storage Navigator Modular operates.

ii. Go to the command prompt and switch to the directory: C:\Program Files\Storage Navigator Modular CLI

iii. From this directory, run the following command to discover unregistered storage units:

auunitaddauto -ip 192.168.40.1 192.168.40.255

iv. All discovered storage units will then be listed as follows:

Searching... 192.168.40.255 Detected Count : 1

The subsystem of the following was discovered.

No. Name Controller0

Controller1 Type Construction

Serial No

1 DF700M_75010626 192.168.40.41

192.168.40.42 DF700M Dual

75010626

v. The command will now prompt you confirm whether you want to register the discovered subsystem with the Storage Navigator Modular. Type y here to register one/more of the discovered storage units.

Are you sure you want to register the discovered subsystem? (y/n

[y]) : y

vi. Next, specify the No. of the discovered subsystem to register it.


3

Please specify the number of the subsystem to register: 1

vii. If registration is successful, the following message will appear:

DF700M_75010626 has been registered.

The subsystems have been registered successfully

viii. Micro program 0710/A or later is required;

1.2 Administering the eG Manager to Work with the Hitachi AMS SAN

1. Log into the eG administrative interface.

2. eG Enterprise cannot automatically discover Hitachi AMS SAN server. You need to manually add the server using the add/modify components page (see Figure 1.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically.

Figure 1.1: Adding a Hitachi AMS SAN server

3. Specify the Host IP and the Nick name of the Hitachi AMS SAN server. Also select Other as the OS and SNMP as the MODE. Then, click the ADD button to register the changes.

Note: Though the Mode is set to SNMP while adding a new component, the eG agent will be ableto collect metrics from the target environment through the SNCLlENTLOCATION path thatwill be specified by you during parameter configuration for the tests pertaining to theHitachi AMS SAN server.


4

When you attempt to sign out, a list of unconfigured tests appears as shown in

4. Figure 1.2.

Figure 1.2: List of Unconfigured tests to be configured for the Hitachi AMS SAN server

5. Click on the Cache Memory Usage test to configure it. This test reports how well the objects in the cache have been utilized.

Figure 1.3: Configuring the Cache Memory Usage test

6. To configure the test, specify the following in Figure 1.3.

TEST PERIOD - How often should the test be executed

HOST - The host for which the test is to be configured

PORT - The port at which the HOST listens.

UNITNAME - Specify the name of the storage unit to be monitored. To determine the unit name registered with the Storage Navigator Client for the AMS SAN device, run the following commands, one after another, from the C:\Program Files\Storage Navigator Modular CLI directory on the Storage Navigator Client:

startnsmen

auunitref

The output of the command includes the Name of the storage unit. DF700M_75011118 is a sample unit name.


5

MCTYPE – Indicate the machine type. The value can be AMS or WMS. By default, this parameter is set to AMS.

SNCLIENTLOCATION – Specify the full path to the install directory of the storage navigator.

TIMEOUT – Indicate the duration (in minutes) for which this test should wait for a response from the storage device. By default, this is set to 3 minutes.

USER – Specify the name of the user who is authorized to access the target server.

PASSWORD – Specify the password corresponding to the specified USER.

CONFIRM PASSWORD – Confirm the password by retyping it here

7. Next, try to signout of the administrative interface again. When the LIST OF UNCONFIGURED tests comes, choose to configure the Cache Load test. Doing so will invoke Figure 1.4.

Figure 1.4: Configuring the Cache Load test

8. This test reports the rate at which data is written to the cache memory. To configure this test, specify the following:



SNMPPORT – Here specify the port number through which the server exposes its SNMP MIB. The default value is 161.

SNMPVERSION – By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPVERSION list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.

SNMPCOMMUNITY – Here, specify the SNMP community name that the test uses to communicate with the mail server. The default is public. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVERSION chosen is v3, then this parameter will not appear.

USERNAME – This parameter appears only when v3 is selected as the SNMPVERSION. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB


6

using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against the USERNAME parameter.

AUTHPASS – Specify the password that corresponds to the above-mentioned USERNAME. This parameter once again appears only if the SNMPVERSION selected is v3.

CONFIRM PASSWORD – Confirm the AUTHPASS by retyping it here.

AUTHTYPE – This parameter too appears only if v3 is selected as the SNMPVERSION. From the AUTHTYPE list box, choose the authentication algorithm using which SNMP v3 converts the specified USERNAME and PASSWORD into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

o MD5 – Message Digest Algorithm

o SHA – Secure Hash Algorithm

ENCRYPTFLAG – This flag appears only when v3 is selected as the SNMPVERSION. By

default, the eG agent does not encrypt SNMP requests. Accordingly, the ENCRYPTFLAG is set to NO by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the YES option.

ENCRYPTTYPE – If the ENCRYPTFLAG is set to YES, then you will have to mention the encryption type by selecting an option from the ENCRYPTTYPE list. SNMP v3 supports the following encryption types:

o DES – Data Encryption Standard

o AES – Advanced Encryption Standard

ENCRYPTPASSWORD – Specify the encryption password here.

CONFIRM PASSWORD – Confirm the encryption password by retyping it here.

TIMEOUT - Here, specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 seconds.

9. Then, click the Update button in Figure 1.4 and try signing out again. This time you will be prompted to configure the Traps Status test. Doing so will invoke Figure 1.5.

Figure 1.5: Configuring the Trap Status test


7

10. This test captures the SNMP trap messages sent out by the hardware components (such as battery, cache memory, drive, enclosure controller, fan, host controller, other enclosures, and power supply units) on the storage device, and thus enables administrators to promptly detect potential hardware failures. To configure this test, do the following:



PORT – Specify the port number at which the specified host listens. By default, this is NULL.

SOURCEADDRESS - Specify a comma-separated list of IP addresses or address patterns of the hosts from which traps are considered in this test. For example, 10.0.0.1,192.168.10.*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters.

OIDVALUE - Provide a comma-separated list of OID and value pairs returned by the traps. The values are to be expressed in the form, DisplayName:OID-OIDValue. For example, assume that the following OIDs are to be considered by this test: .1.3.6.1.4.1.9156.1.1.2 and .1.3.6.1.4.1.9156.1.1.3. The values of these OIDs are as given hereunder:

OID Value

.1.3.6.1.4.1.9156.1.1.2 Host_system

.1.3.6.1.4.1.9156.1.1.3 NETWORK

In this case the OIDVALUE parameter can be configured as Trap1:.1.3.6.1.4.1.9156.1.1.2-Host_system,Trap2:.1.3.6.1.4.1.9156.1.1.3-Network, where Trap1 and Trap2 are the display names that appear as descriptors of this test in the monitor interface.

An * can be used in the OID/value patterns to denote any number of leading or trailing characters (as the case may be). For example, to monitor all the OIDs that return values which begin with the letter 'F', set this parameter to Failed:*-F*.

Typically, if a valid value is specified for an OID in the OID-value pair configured, then the test considers the configured OID for monitoring only when the actual value of the OID matches with its configured value. For instance, in the example above, if the value of OID .1.3.6.1.4.1.9156.1.1.2 is found to be HOST and not Host_system, then the test ignores OID .1.3.6.1.4.1.9156.1.1.2 while monitoring. In some cases however, an OID might not be associated with a separate value – instead, the OID itself might represent a value. While configuring such OIDs for monitoring, your OIDVALUE specification should be: DisplayName:OID-any. For instance, to ensure that the test monitors the OID .1.3.6.1.4.1.9156.1.1.5, which in itself, say represents a failure condition, then your specification would be:

Trap5: .1.3.6.1.4.1.9156.1.1.5-any.


8

SHOWOID – Specifying true against SHOWOID will ensure that the detailed diagnosis of this test shows the OID strings along with their corresponding values. If you enter false, then the values alone will appear in the detailed diagnosis page, and not the OIDs.

11. Finally, click the Update button and exit the eG administrative interface.

1.3 Monitoring the Hitachi AMS SAN Server To monitor the Hitachi AMS SAN server, do the following:

1. Login as a monitor / supermonitor user.

2. Click on the components option in the menu bar, and select the Servers option from the components menu.

3. From the component list page, click on the Hitachi AMS SAN component for which you wish to view measurements.

C o n f i g u r i n g a n d M o n i t o r i n g t h e H i t a c h i U P S S A N

9

Configuring and Monitoring the Hitachi USP SAN

2.1 Configuring the eG Agent to Monitor the Hitachi USP SAN

Each layer of the Hitachi USP SAN model is mapped to a variety of tests which report useful performance statistics related to the storage device. These tests use both the following approaches to collecting metrics from the Hitachi USP device:

By accessing the Performance Monitor application available with the storage device;

Using SNMP-based access to the SNMP MIB of the device;

The Performance Monitor is a controller-based software application that acquires information on the performance of RAID groups, logical units, and other elements of the disk subsystem while tracking the utilization rates of resources such as hard disk drives and processors. To periodically run the Performance Monitor application and to extract the metrics of interest from the storage device, a Java export utility must be available on the eG agent host.

The tests that need to access the Performance Monitor for metrics should then be configured with the path to the Java export utility. This way, whenever that test is run, the eG agent executing the test automatically invokes the Java export utility via CLI, which then connects to the storage device, accesses the Performance Monitor on the device, and extracts the desired metrics.

A few other tests executed by the eG agent collects the statistics of interest using SNMP-based access to the MIB statistics of the storage device. For these tests to work, you first need to SNMP-enable the storage device.

While you need to configure a remote agent for accessing the Performance Monitor software and collecting metrics, an external agent is necessary for performing the SNMP-based monitoring.

Chapter

2

Note:

If need be, you can configure a ‘single agent’ to function both as a remote agent and as an external agent for monitoring the Hitachi USP.


10

To ensure that the eG agent is able to use both the Performance Monitor and the SNMP MIB (of the device) effectively for collecting metrics from the Hitachi USP, the following pre-requisites should be fulfilled:

The SNMP service should be enabled on the device;

The eG SNMP trap receiver service should be installed on the external agent host;

The storage device should be configured to send SNMP traps to the external agent host;

The Hitachi Performance Monitor software should be available;

The Java export utility should be available on the remote agent host;

The eG agent should be configured with the credentials of a special user account, which is specifically created for use with the export utility; this account should fulfill the following conditions:

i. Should not possess the ‘write’ permission;

ii. Can be of any user type; however, to ensure that the eG agent collects statistics pertaining to all storage partitions, it is recommended that this user is of type storage administrator;

2.2 Administering the eG Manager to monitor the Hitachi USP SAN Server

1. Log into the eG administrative interface.

2. eG Enterprise cannot automatically discover a Hitachi USP SAN. You need to manually add the server using the ADD/MODIFY COMPONENTS page (see Figure 2.1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically.

Figure 2.1: Adding a Hitachi USP SAN server

3. After specifying the Host IP, Nick name of the Hitachi USP SAN server, select Other as the OS and SNMP as the MODE. Then, click the ADD botton to register the changes.


11

4. When you attempt to sign out, a list of unconfigured tests appears as shown in Figure 2.2.

Figure 2.2: List of Unconfigured tests to be configured for the Hitachi USP SAN server

5. Click on the Battery Status test to configure it.

Figure 2.3: Configuring the Battery Status test

6. To configure the test, specify the following in Figure 2.3.



SNMPPORT – Here specify the port number through which the server exposes its SNMP MIB. The default value is 161.

SNMPVERSION – By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPVERSION list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.

SNMPCOMMUNITY – Here, specify the SNMP community name that the test uses to communicate with the mail server. The default is public. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVERSION chosen is v3, then this parameter will not appear.

USERNAME – This parameter appears only when v3 is selected as the SNMPVERSION. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the

Note: Though the Mode is set to SNMP while adding a new component, the eG agent will be ableto collect metrics from the target environment through the specified CLI path.


12

required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against the USERNAME parameter.

AUTHPASS – Specify the password that corresponds to the above-mentioned USERNAME. This parameter once again appears only if the SNMPVERSION selected is v3.

CONFIRM PASSWORD – Confirm the AUTHPASS by retyping it here.

AUTHTYPE – This parameter too appears only if v3 is selected as the SNMPVERSION. From the AUTHTYPE list box, choose the authentication algorithm using which SNMP v3 converts the specified USERNAME and PASSWORD into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

o MD5 – Message Digest Algorithm

o SHA – Secure Hash Algorithm

ENCRYPTFLAG – This flag appears only when v3 is selected as the SNMPVERSION. By

default, the eG agent does not encrypt SNMP requests. Accordingly, the ENCRYPTFLAG is set to NO by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the YES option.

ENCRYPTTYPE – If the ENCRYPTFLAG is set to YES, then you will have to mention the encryption type by selecting an option from the ENCRYPTTYPE list. SNMP v3 supports the following encryption types:

o DES – Data Encryption Standard

o AES – Advanced Encryption Standard

ENCRYPTPASSWORD – Specify the encryption password here.

CONFIRM PASSWORD – Confirm the encryption password by retyping it here.

TIMEOUT - Here, specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 seconds.

7. Next, when you try to signout of the administrative interface, you will be prompted to configure the Nsc traps test.

Figure 2.4: Configuring the Nsc Traps test

8. To configure the test, specify the following in Figure 2.4:


13



PORT – Specify the port number at which the specified host listens. By default, this is NULL.

SOURCEADDRESS - Specify a comma-separated list of IP addresses or address patterns of the hosts from which traps are considered in this test. For example, 10.0.0.1,192.168.10.*. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters.

OIDVALUE - Provide a comma-separated list of OID and value pairs returned by the traps. The values are to be expressed in the form, DisplayName:OID-OIDValue. For example, assume that the following OIDs are to be considered by this test: .1.3.6.1.4.1.9156.1.1.2 and .1.3.6.1.4.1.9156.1.1.3. The values of these OIDs are as given hereunder:

OID Value

.1.3.6.1.4.1.9156.1.1.2 Host_system

.1.3.6.1.4.1.9156.1.1.3 NETWORK

In this case the OIDVALUE parameter can be configured as Trap1:.1.3.6.1.4.1.9156.1.1.2-Host_system,Trap2:.1.3.6.1.4.1.9156.1.1.3-Network, where Trap1 and Trap2 are the display names that appear as descriptors of this test in the monitor interface.

An * can be used in the OID/value patterns to denote any number of leading or trailing characters (as the case may be). For example, to monitor all the OIDs that return values which begin with the letter 'F', set this parameter to Failed:*-F*.

Typically, if a valid value is specified for an OID in the OID-value pair configured, then the test considers the configured OID for monitoring only when the actual value of the OID matches with its configured value. For instance, in the example above, if the value of OID .1.3.6.1.4.1.9156.1.1.2 is found to be HOST and not Host_system, then the test ignores OID .1.3.6.1.4.1.9156.1.1.2 while monitoring. In some cases however, an OID might not be associated with a separate value – instead, the OID itself might represent a value. While configuring such OIDs for monitoring, your OIDVALUE specification should be: DisplayName:OID-any. For instance, to ensure that the test monitors the OID .1.3.6.1.4.1.9156.1.1.5, which in itself, say represents a failure condition, then your specification would be:

Trap5: .1.3.6.1.4.1.9156.1.1.5-any.

SHOWOID – Specifying true against SHOWOID will ensure that the detailed diagnosis of this test shows the OID strings along with their corresponding values. If you enter false, then the values alone will appear in the detailed diagnosis page, and not the OIDs.


14

9. Finally, signout of the administrative interface.

2.3 Monitoring the Hitachi USP SAN To monitor the Hitachi USP SAN, do the following:

1. Login as a monitor / supermonitor user.

2. Click on the components option in the menu bar, and select the Servers option from the components menu.

3. From the component list page, click on the Hitachi USP SAN server for which you wish to view measurements.

C o n c l u s i o n

15

Conclusion This document has described in detail the steps for configuring and monitoring the Hitachi SAN Servers. For details of how to administer and use the eG Enterprise suite of products, refer to the user manuals.

We will be adding new measurement capabilities into the future versions of the eG Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eG Enterprise suite of products, please contact [email protected]. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eG Enterprise suite can be forwarded to [email protected].

Chapter

3

mailto:[email protected]

Configuring and Monitoring Hitachi SAN Servers Implementer's... · · 2014-02-01table of contents...

Documents

Transcript of Configuring and Monitoring Hitachi SAN Servers Implementer's... · · 2014-02-01table of contents...