HP LeftHand SAN Solutions

Transcription

1 HP LeftHand SAN Solutions Support Document Application Notes Best Practices for Using PRTG Traffic Grapher to Monitor SANiQ Performance

2 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notices Copyright 2009 Hewlett-Packard Development Company, L.P. 2

3 Documentation Updates The title page of this document contains the following identifying information: Software Version number, which indicates the software version. Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software. To check for recent updates or to verify that you are using the most recent edition of a document, go to: This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. The following table indicates changes made to this document since the last released edition. Document Changes Chapter Version Changes 3

4 Support Visit the HP Software Support web site at: This web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: To find more information about access levels, go to: 4

5 Contents 1 Chapter: Configuring NSMS for SNMP Chapter: Configuring a Windows Server for SNMP Chapter: Installing PRTG Traffic Grapher Chapter: Adding Custom Polling Statistics Chapter: Modifying Custom Sensors Chapter: Setting Threshold Alerts Chapter: Frequently Asked Questions A Appendix: How to Find OIDs in SAN/IQ B Appendix: Commonly Used Lefthand OIDs

6 6 This page is intentionally left blank

7 1 Chapter: Configuring NSMS for SNMP Overview SAN/iQ 8.0 from LeftHand Networks introduces new performance monitoring tools that allow administrators to monitor SAN workload. The LeftHand Networks Centralized Management Console is used for monitoring real time performance statistics. For long term data collection, SAN/iQ 8.0 offers SNMP counters for performance metrics which allow long term data collection and analysis. This document details the procedures for monitoring a SAN/iQ environment by using Orion from SolarWinds ( products/orion/index.aspx). Orion uses a SQL Server database to store the data it collects, and can install a database into a new environment upon Orion installation. For more information about Orion system requirements, go to system_requirements.aspx Configuring NSMS for SNMP LeftHand Networks NSMs running SAN/iQ version 8.0 or later come with SNMP performance monitoring capabilities built in to the core software. It is disabled by default, so it must be configured and enabled before monitoring can begin. To configure and enable SNMP on an NSM, perform the following steps: Open the CMC, and browse down the left hand side of the CMC to the NSM you wish to monitor. Expand the tree further and select SNMP under the NSM. 7

8 Click on SNMP General Tasks, and choose Edit Settings. From this pop up window, choose to enable the SNMP agent, enter the Community String and System Location and System Contact if desired. Also enter the hostname or IP address of the Orion server that will be monitoring this NSM. If more than one server will need access, a subnet can be substituted for a single IP address. For example, the host would be and the subnet mast would be this would allow all hosts on the 10.x.x.x subnet to access this NSM via SNMP. Click OK. 8 Chapter 1

9 2 Chapter: Configuring a Windows Server for SNMP The Windows SNMP service must be installed on the server running Orion before installing Orion. If SNMP is not installed, go to Start -> Control Panel -> Add/Remove Programs, then Add/Remove Windows Components. Highlight Management and Monitoring Tools, then click the Details button. Select Simple Network Management Protocol, then OK. Click Next to complete the installation. With SNMP installed on the Orion server, perform the following steps to configure SNMP for use with Orion: Go to the Services section of the Computer Management plugin by right clicking on My Computer and selecting Manage. Edit the properties of the SNMP Service by either double clicking on the SNMP Service item or right clicking and choosing Properties. 9

10 Go to the Security tab. Click Add under the Accepted Community Names section, and enter the SNMP community name as read only. Then either choose to accept SNMP packets from any host or from a list of hosts. If you choose to accept SNMP packets from select hosts, make sure the IP addresses of all NSMs to be monitored are listed. Restart the service for the changes to take effect. 10 Chapter 2

11 3 Chapter: Installing PRTG Traffic Grapher PRTG is available from the Paessler website at prtg/. A trial version is available for download, however, the functionality is crippled in comparison to the commercial edition. Before installing the commercial version, make sure the license key is handy. To install PRTG Traffic Grapher, perform the following steps: Double click the installation file and select the proper language and click OK Click Next Accept the license terms and click Next 13

12 Choose an installation directory and click Next Choose which components to install. Make sure all components are selected (Full installation) and click Next 14 Chapter 3

13 Depending on requirements, choose to either allow or disallow network access to the PRTG server s web interface. Additionally, install the PRTG Watchdog service. Click Next The PRTG installation wizard begins the installation Chapter: Installing PRTG Traffic Grapher 15

14 Finish the installation by clicking Finish. 16 Chapter 3

15 4 Chapter: Adding Custom Polling Statistics To access the SAN/iQ SNMP counters, you must add customer polling statistics to the PRTG interface. To do so: Start PRTG Click on Click here to create your first sensor. The Add Sensor Wizard appears. Click Next. 17

16 Choose SNMP (Simple Networks Management Protocol) from the list of Data Acquisition Types. Choose Custom SNMP Sensor from the SNMP Sensor Type Selection page. Enter the device name, IP address, and SNMP Community String. The SNMP port usually does not change. SNMP V2c MUST be selected as SAN/iQ uses 64-bit SNMPcounters which are not supported in SNMP V1. Click Next. 18 Chapter 4

17 Enter the OID for the value you wish to monitor, and click Test. (For help on finding OIDs for specific counters, see Appendix A, How to Find OIDs in SAN/iQ 8.0 ) If the OID is valid, a value will be returned by PRTG. At this point you can choose to customize the scale, Indicator name and Unit name. In this case, the OID is for write I/Os per second, so the Unit type will be IOPS. Click Next. The final step is to choose which list this item will be categorized under, whether a new subgroup will be created, the scanning interval, and what tags are being used. You can then define the type of measuring you want to do. Your options are: Gauge (absolute value) Chapter: Adding Custom Polling Statistics 19

18 Delta (difference per period) Check the Float value box if the returned value is a float (with a decima point). The Scale function is a floating point value through which the value delivered from the SNMP sensor is either divided or multiplied. You can select which one of the two to perform by clicking on the appropriate radio button to the right. The Indicator field can be used to enter information that will be shown in the legend, as the name for the information of the sensor. In the Unit field you can enter any string that shall be used as units when displaying the graphs. The user should select the options that work best for their environment. Click Finish. The new counter now shows up in PRTG. 20 Chapter 4

19 5 Chapter: Modifying Custom Sensors At any time, a user can modify their customer sensors to change such settings as Sensor Name, SNMP settings, etc. To modify a custom sensor, simply right click on the sensor and select Edit. A common item that might be edited is Sensor Name. In this example, the Custom Sensor is for I/O Writes per Second, but the Sensor Name shows up as Custom () on #host. The Sensor Name can be changed to something more meaningful via this pop-up box: 23

20 One group of settings that might be useful to change is the Sensor Settings. The scanning interval for the poller can be set here, as well as the schedule at which the poller will run. When monitoring objects like volume utilization, there may be no benefit to polling every 10 seconds as volume use typically takes a fair amount of time to go from a good state to a critical or near critical state. Additionally, there may be no benefit to monitoring the SAN over the weekends, such as cases where known heavy report generation may produce expected polling results that exceed certain thresholds. 24 Chapter 5

21 The data that is collected and displayed can be scaled on the Advanced tab. You can define what units to use for the volume, as well as for the speed. In the Values settings you can define the scale the raw result of the sensor is either divided or multiplied by this value, depending on which radio button is checked. If you want to filter spikes, check the Spike Filter checkbox and enter a maximal value (per second) in the right field. This will avoid the graphs spiking when erroneous values are reached. Chapter: Modifying Custom Sensors 25

22 The Notifications & Limits options are covered in more detail in Section 6: Setting Threshold Alerts. 26 Chapter 5

23 Finally, if you ever need to change the SNMP settings, such as the IP of the NSM you are monitoring, they can be changed in the SNMP section. Chapter: Modifying Custom Sensors 27

24 6 Chapter: Setting Threshold Alerts Users can set Alerts to notify them or perform an action should a monitored threshold be met or exceeded. To set alerts for thresholds, perform the following steps: Right lick on the custom sensor that you wish to monitor, and choose Edit. Select the Notifications and Limits option from the left hand pane. A box pops up with that sensor and a default threshold setting. These settings will vary depending on the quantity and type of LeftHand platform you are monitoring, as well as the type of counter you are monitoring. Change these values to fit your requirements. The thresholds you set will be dependant on many factors, such as type and quantity of NSMs and your own preferences, for example. 27

25 There are several options available for when the threshold is exceeded. Sending an when a threshold is exceeded can allow administrators to take proactive actions when a SAN is busy or reaching capacity. Additionally, having a visual cue in the form of a background color change can help administrators identify problem areas. Choose the proper options and OK to exit the notifications options box, and OK again to exit the sensor editing dialog box. Now with these options configured, an is sent and the background of the charts turns red when the threshold limit is exceeded. 28 Chapter 6

26 7 Chapter: Frequently Asked Questions The following FAQ covers questions commonly asked about using SolarWinds Orion to monitor SAN/iQ 8.0. Doesn t your performance dashboard do some of this stuff already? Many of the same counters available through SNMP are also available through the CMC. Throughput, IOPS (Inputs/Outputs per second), and disk utilization are examples of some counters that are obtainable through either the Performance Dashboard or through SNMP. The Performance Dashboard however was designed to be a real time monitoring tool, where monitoring performance through SNMP allows for long term data collection, enabling historical analysis and trending. The tools complement each other, and it is not unusual to use both tools to analyze SAN performance and utilization. How do I know what Community String to use? The Community String is determined in advance by the system administrator. Any text string can be used, however many system administrators use the string public as their default string. This document uses SNMP-Demo as the community string, mainly for clarity throughout the document. How do I tell if SNMP is installed on the host server? From the command line, enter the command SC Interrogate SNMP. If SNMP is installed, information similar to the following screen shot will be displayed. If SNMP is not installed, a Windows will return a message indicating that the service does not exist or is not installed. 29

27 How do I restart the SNMP service? The SC command allows administrators to stop and start any service. To stop the service, enter the command SC stop SNMP. To start the service back up, enter the command SC start SNMP. The status of the service can be checked with the command SC interrogate SNMP. 30 Chapter 7

28 A Appendix: How to Find OIDs in SAN/ IQ 8.0 Each object in the MIB has an object identifier (OID), which the management station uses to request the object's value from the agent. An OID is a sequence of integers that uniquely identifies a managed object by defining a path to that object through a tree-like structure called the OID tree or registration tree. When an SNMP agent needs to access a specific managed object, it traverses the OID tree to find the object. Many SNMP monitoring tools require the user to know the specific OID for the object that is being monitored. A MIB browser can be an invaluable tool for finding specific OIDs for your management needs. There are several free and commercial MIB browsers available; this section will discuss how to use the ireasoning MIB browser to find the OIDs for specific object. A free personal edition of the ireasoning MIB browser is available at a commercial version is also available from the ireasoning web site. To use the ireasoning MIB browser: Download and install the ireasoning MIB browser. Using the default installation options is fine. Open the ireasoning MIB browser by clicking on Start -> Programs -> ireasoning -> MIB Browser -> MIB Browser. In the Address field, enter the IP address of the NSM you wish to monitor. Be sure that the NSM is running SAN/iQ version 8.0 or higher. Click on the Advanced button, and enter the correct community strings. Make sure that the SNMP version is set to 2. Because SAN/iQ uses 64-bit SNMP counters, any other SNMP version will not function properly. Click Ok 31

29 From the File menu, choose Load MIBs Browse to C:\Program Files\LeftHand Networks\UI\mibs. Select LEFTHAND-NETWORKS-NSMCLUSTERING-MIB.mib Click Open 32 Appendix A

30 In the MIB tree on the left side, select the folder that begins with LEFTHAND-NETWORKS-NSMCLUSTERING-MIB Right click on the folder and click Walk. Or, select Walk from the Operations dropdown on the top right of the application. The result table will be populated with Name/OID, Value, and Type. Scroll down the right side until you find the desired name and value. Select the counter you wish to find the OID of, and the OID will appear in the OID: box. Notice that clusvolumestatsioswrite has three entries. These represent the three volumes that have been created in the SAN. The numbers correspond to the volumes that were created in the order they were created. The volume Appendix: How to Find OIDs in SAN/IQ

31 that was created first is represented by.1, etc. This mapping can also be done by going to cluvolumename and seeing which volume names correspond to which numerical suffix. You can then use this correlation to monitor other volume counters. 34 Appendix A

32 B Appendix: Commonly Used Lefthand OIDs Name Description OID Clusters: clusclusterstatscachehits counter of read ahead hits clusclusterstatsiolatencywrite counter of cache hits clusclusterstatsiolatencyread time spent waiting for write operations to complete for this cluster clusclusterstatsqdepthwrite time spent waiting for read operations to complete for this cluster clusclusterstatsqdepthread number of pending write operations clusclusterstatskbyteswrite counter of Kbytes written clusclusterstatskbytesread counter of Kbytes read clusclusterstatsioswrite counter of IO write operations clusclusterstatsiosread counter of IO read operations Space available to create new volume(s) (assuming one replica). clusclusterspaceavailable Divide by the replication level to obtain the true number clusclusterdescription description of cluster clusclustername name of cluster Volumes: clusvolumestatsaheadhits counter of read ahead hits

33 Name Description OID clusvolumestatscachehits counter of cache hits clusvolumestatsiolatencywrite time spent waiting for write operations to complete for this volume clusvolumestatsiolatencyread time spent waiting for read operations to complete for this volume clusvolumestatsqdepthwrite number of pending write operations clusvolumestatsqdepthread number of pending read operations clusvolumestatskbyteswrite counter of Kbytes written clusvolumestatskbytesread counter of Kbytes read clusvolumestatsioswrite counter of IO write operations clusvolumestatsiosread counter of IO read operations clusvolumeusedspace maximum space used by volume (high watermark) clusvolumeclusterusedpercent maximum space used by volume (high watermark) as a percent of the cluster clusvolumesize number of kbytes comprising the volume clusvolumename name of volume Modules: clusmodulestatsserveriolatencytota l time spent waiting for read and write operations to complete for this server clusmodulestatsiolatencywrite time spent waiting for write operations to complete for this module clusmodulestatsiolatencyread time spent waiting for read operations to complete for this module clusmodulestatsqdepthtotal number of pending read and write operations clusmodulestatskbyteswrite counter of Kbytes written Appendix B

34 Name Description OID clusmodulestatskbytesread counter of Kbytes read clusmodulestatsioswrite counter of IO write operations clusmodulestatsiosread counter of IO read operations clusmodulestoragestatus storage status of a module clusmoduleraidstatus RAID status of a module clusmoduleavailsize available storage size of module clusmoduleserialno serial number of module clusmodulename hostname of module Snapshots: clusvolumesnapshotstatsaheadhits counter of read ahead hits clusvolumesnapshotstatscachehits counter of cache hits clusvolumesnapshotstatsiolatency Write time spent waiting for write operations to complete for this snapshot clusvolumesnapshotstatsiolatencyr ead time spent waiting for read operations to complete for this snapshot clusvolumesnapshotstatsqdepthwri te number of pending write operations clusvolumesnapshotstatsqdepthrea d number of pending read operations clusvolumesnapshotstatskbyteswrit e counter of Kbytes written clusvolumesnapshotstatskbytesrea d counter of Kbytes read clusvolumesnapshotstatsioswrite counter of IO write operations clusvolumesnapshotstatsiosread counter of IO read operations Appendix: Commonly Used Lefthand OIDs 37

35 Name Description OID clusvolumesnapshotprovisionedspac e maximum space used by snapshot (high watermark) clusvolumesnapshotclusterusedperc ent maximum space used by snapshot and writable space (high watermark) as a percent of cluster space clusvolumesnapshotusedspace maximum space used by snapshot (high watermark) clusvolumesnapshotcopyprogress percentage progress of a remote IP copy (if a remote copy is in progress) clusvolumesnapshotsize size of the snapshot in Kbytes clusvolumesnapshotname snapshot name Appendix B