HP LeftHand SAN Solutions Support Document Applications Notes Best Practices for Using SolarWinds' ORION to Monitor SANiQ Performance
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 12.211 and 12.212, 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
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: http://h20230.www2.hp.com/selfsolve/manuals This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html 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
Support Visit the HP Software Support web site at: www.hp.com/go/hpsoftwaresupport 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: http:// h20229.www2.hp.com/passport-registration.html To find more information about access levels, go to: http://h20230.www2.hp.com/ new_access_levels.jsp 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 (http://www.solarwinds.com/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 http://www.solarwinds.com/products/orion/ system_requirements.aspx 4
Contents 1 Chapter: Configuring NSMs for SNMP...................................... 7 2 Chapter: Configuring a Windows Server for SNMP.......................... 9 3 Chapter: Installing SolarWinds Orion..................................... 13 4 Chapter: Adding custom polling statistics................................... 29 5 Chapter: Modifying custom sensors........................................ 49 6 Chapter: Setting theshold alerts........................................... 51 7 Chapter: Frequently Asked Questions...................................... 57 A Appendix: How to find OIDs in SAN/IQ 8.0............................... 59 B Appendix: Commonly used Lefthand OIDs................................. 63 5
6 This page is intentionally left blank
1 Chapter: 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. 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 10.0.0.0 and the subnet mast would be 255.0.0.0 this would allow all hosts on the 10.x.x.x subnet to access this NSM via SNMP. Click OK. 7
8 Chapter 1
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. 9
Edit the properties of the SNMP Service by either double clicking on the SNMP Service item or right clicking and choosing Properties. 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. 10 Chapter 2
Chapter: Configuring a Windows Server for SNMP 11
Restart the service for the changes to take effect. 12 Chapter 2
3 Chapter: Installing SolarWinds Orion This section contains basic installation instructions for installing SolarWinds Orion as it pertains to use with SAN/iQ 8.0. For more detailed instructions, please visit the Orion web page at http://www.solarwinds.com/products/orion/index.aspx. To begin the installation, double click on the setup executable. 13
Click Next Accept the license agreement and click Next 14 Chapter 3
Click Next to use the default Orion installation directory, or click Browse to install Orion to a different directory, then click Next Chapter: Installing SolarWinds Orion 15
If Orion will be using an existing SQL Server installation, choose the bottom option. If no other SQL Server is to be used, choose to install SQL Server by choosing the first option and selecting Next. These instructions assume no existing SQL Server implementation and will therefore use the version of SQL Server that comes with Orion. 16 Chapter 3
Choose to either use the default SQL Server installation directory or change it to a custom location. Click Next Choose to use the default location for SQL Server data files, or change it to a custom location. Click Next Chapter: Installing SolarWinds Orion 17
The SQL Server instance requires an administrative password. This password Is used for the administration of the SQL Server instance, and not for the Orion database itself. Choose a secure password, enter it twice to verify it, and click Next 18 Chapter 3
Review the installation options, and click Next Orion completes its installation of the software and of the SQL Server instance. Chapter: Installing SolarWinds Orion 19
The installation completes. 20 Chapter 3
When Orion and SQL Server are done being installed, the Orion configuration wizard appears. Click Next Chapter: Installing SolarWinds Orion 21
Begin the installation by setting the database that Orion will use to store its data, and enter the username sa and password entered in step 8. 22 Chapter 3
If not using an existing database, you will be prompted to create a new database. Choose a name that makes sense, and click Next Chapter: Installing SolarWinds Orion 23
Create a user account for Orion to use for the SQL Server instance. This is a different account than the SQL Server administrator s account created in step 8. Orion has a web interface which must also be configured. If Orion server has no other web sites associated with it, the default settings will usually be ok. Otherwise, see the Orion web site for more details on installation options. Click Next. If the Orion website is the first website on the server, you will be prompted with the following questions: Directory c:\inetpub\solarwinds does not exist. Create directory? A website exists with the same TCP port binding. Do you want to use the existing web site? Choose Yes for both questions. 24 Chapter 3
Select all services to install, unless otherwise directed by LeftHand Networks or SolarWinds. Click Next Chapter: Installing SolarWinds Orion 25
Review the configuration options and click Next to begin the Orion configuration. 26 Chapter 3
Orion begins the configuration process. Chapter: Installing SolarWinds Orion 27
The configuration summary appears. Click Finish 28 Chapter 3
4 Chapter: Adding custom polling statistics To access the SAN/iQ SNMP counters, you must add customer polling statistics to the Orion interface. To do so: Start Orion by clicking on Start, Programs, SolarWinds Orion, then System Manager. Click on Add Node. From the Add Node dialog box, enter the IP of the NSM you wish to monitor, the community string, and choose SNMPv2c. SAN/iQ SNMP MIBs are 64-bit, and require SNMPv2c to function properly. Leave the default SNMP port of 161 unchanged. 29
Orion makes connection to the NSM and retrieves basic system information. Click OK. 30 Chapter 4
Right click on the NSM you wish to monitor and click Assign Custom MIB Poller Chapter: Adding custom polling statistics 31
Click Custom MIB Pollers 32 Chapter 4
Click New Chapter: Adding custom polling statistics 33
Click Browse to select the NSM to monitor. 34 Chapter 4
Select the NSM you wish to monitor, the click OK Chapter: Adding custom polling statistics 35
Select OID by clicking the Browse button. 36 Chapter 4
Enter proper OID or browse to find the right OID. Click Test to test the OID. You must test the OID successfully to continue the process. If the test fails, Orion will not allow you to proceed. (For help on finding OIDs for specific counters, see Appendix A, How to Find OIDs in SAN/iQ 8.0 ) Chapter: Adding custom polling statistics 37
Enter an optional name for the Custom MIB Poller, a description, and choose to add it to a group for easier management if so desired. 38 Chapter 4
Choose the MIB value type and whether to monitor real-time activity only or keep historical and real-time data. These options will vary depending on the type of data being collected. Click Finish Chapter: Adding custom polling statistics 39
Close the Custom MIB Poller dialog box by clicking the X on the top right corner. 40 Chapter 4
The Custom MIB Poller has been set up, but Orion must be configured to show that information in the console. To configure Orion, start the Orion web console. Chapter: Adding custom polling statistics 41
Click on Admin, then Manage Views 42 Chapter 4
Click on Node Details, then Edit Chapter: Adding custom polling statistics 43
Click on the Add Resources button 44 Chapter 4
Expand Node Details Report, then select Custom Poller Status, then click Submit Chapter: Adding custom polling statistics 45
Go to Home, expand All Nodes, click on the node name 46 Chapter 4
The custom poller that was added is available now on the right side. It appears on the bottom by default, but can be moved to the top by customizing the node details from the screen shown in step 16. Chapter: Adding custom polling statistics 47
Click on Poller Name (Volume1WriteIOPS in this example) to see the chart and polling data. In the screenshot below, you see the first data point appear on the chart. This chart will fill in over time. 48 Chapter 4
5 Chapter: Modifying custom sensors 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: 49
You will need to repeat this process for all Custom Sensors that you add. 50 Chapter 5
6 Chapter: Setting theshold 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: In Orion System Manager, click Alerts From the Alerts window, choose to configure advanced basic alerts. Click on Configure Advanced Alerts. Click on New 51
Enter a name for the alert, and a description. Make sure that the Enable this Alert box is checked. You can use the default Alert Evaluation Frequency, or change it to something more suitable for your needs. Go to the Trigger Condition tab. From the Type of Property to Monitor dropdown, choose Custom Node Poller. Then click Add to add a threshold to monitor. In this example, when the IO per second is greater than 100 and exists for more than 10 seconds, the threshold is triggered. The recommended thresholds for performance counters will vary based on a number of factors, including type and quantity of NSMs, RAID level, etc. The 10 seconds is in place to trigger an alert for a sustained condition, rather than a random occurrence. 52 Chapter 6
The Reset Condition and Alert Suppression tabs are optional, and automate the resetting of the condition or the suppression of the condition. In many cases, you would want manual intervention to suppress or reset the alerts. The Time of Day tab allows the user to select when the monitoring will occur. Many thresholds will be continuously monitored, in which case no changes are necessary. Some thresholds may not need to be monitored at all times. For example, if you know that heavy reporting leads to heavy SAN usage on the weekends, you might not want to monitor IO to the SAN on those days. The following screenshot shows an example of a threshold that is not being monitored on weekends. Simply uncheck the days you do not wish to monitor the system. Chapter: Setting theshold alerts 53
The Trigger Actions tab is key to an effective monitoring system. This tab determines what action will occur if a threshold is met. To define the action(s), select the Trigger Actions tab, and click Add New Action. ***While this document covers only one type of Trigger Action, the options for each action are very similar to sending an email. For further information, read the user documentation available at http://www.solarwinds.com/support/ documentation.aspx 54 Chapter 6
For this example, we will configure the system to send an email alert to the IT department. To do so, select Send an E-Mail/Page and click OK. Enter an email address in the To: field, and then fill in the other email addresses as deemed appropriate. Chapter: Setting theshold alerts 55
You can customize the message of the email by clicking on the Message tab. Enter a meaningful subject line (in this example, something like Warning - Max IOPS exceeded would be appropriate) and a description in the message body. In the example below, the actual rate is in the message body with the variable ${CustomPollerStatus.Rate}. To add this variable, click on Insert Variable, then select CustomPollerStatus and Rate. Click Build Selected Variable to add it to the message body. You can then build text around the variable. On the SMTP Server tab, enter the name or IP of the SMTP server that will be sending the email alerts. If the server requires authentication, check the This SMTP Server requires Authentication box and enter the proper login credentials. The Time of Day tab allows users to configure when the email alerts can be sent. To allow emails to be sent at any time, leave the default values. Alert escalation defines the behavior of the alert over time. For critical thresholds that are exceeded (such as temperature, node down, etc), it is suggested that the action be repeated. The user should evaluate their IT policies to determine an Alert Escalation policy that meets their needs. Click ok to exit the action setup options, then ok again to exit the setup for the Advanced Alert options. At the Manage Alerts box the user can click Done to finish, or first test the alert to make sure the options are configured properly. Testing alerts is highly recommended 56 Chapter 6
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. 57
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. 58 Chapter 7
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 http:// www.ireasoning.com/downloadmibbrowserfree.php, 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 59
From the File menu, choose Load MIBs 60 Appendix A
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. Appendix: How to find OIDs in SAN/IQ 8.0 61
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 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. 62 Appendix A
B Appendix: Commonly used Lefthand OIDs Name Description OID Clusters: clusclusterstatscachehits counter of read ahead hits.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.29 clusclusterstatsiolatencywrite counter of cache hits.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.28 clusclusterstatsiolatencyread time spent waiting for write operations to.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.27 complete for this cluster clusclusterstatsqdepthwrite time spent waiting for read operations to.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.26 complete for this cluster clusclusterstatsqdepthread number of pending write operations.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.25 clusclusterstatskbyteswrite counter of Kbytes written.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.23 clusclusterstatskbytesread counter of Kbytes read.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.22 clusclusterstatsioswrite counter of IO write operations.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.21 clusclusterstatsiosread counter of IO read operations.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.20 Space available to create new volume(s) (assuming one replica). clusclusterspaceavailable Divide by the replication level to obtain the true.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.17 number. clusclusterdescription description of cluster.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.5 clusclustername name of cluster.1.3.6.1.4.1.9804.3.1.1.2.12.48.1.2 Volumes: clusvolumestatsaheadhits counter of read ahead hits.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.45 clusvolumestatscachehits counter of cache hits.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.44 clusvolumestatsiolatencywrite time spent waiting for write operations to.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.43 complete for this volume clusvolumestatsiolatencyread time spent waiting for read operations to.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.42 complete for this volume clusvolumestatsqdepthwrite number of pending write operations.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.41 clusvolumestatsqdepthread number of pending read operations.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.40 clusvolumestatskbyteswrite counter of Kbytes written.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.39 clusvolumestatskbytesread counter of Kbytes read.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.38 clusvolumestatsioswrite counter of IO write operations.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.37 clusvolumestatsiosread counter of IO read operations.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.36 clusvolumeusedspace maximum space used by volume (high.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.31 watermark) clusvolumeclusterusedpercent maximum space used by volume (high.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.32 watermark) as a percent of the cluster clusvolumesize number of kbytes comprising the volume.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.5 clusvolumename name of volume.1.3.6.1.4.1.9804.3.1.1.2.12.97.1.2 Modules: clusmodulestatsserveriolatencytotal time spent waiting for read and write operations to complete for this server.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.18 63
Name Description OID clusmodulestatsiolatencywrite clusmodulestatsiolatencyread time spent waiting for write operations to complete for this module time spent waiting for read operations to complete for this module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.27.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.26 clusmodulestatsqdepthtotal number of pending read and write operations.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.25 clusmodulestatskbyteswrite counter of Kbytes written.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.24 clusmodulestatskbytesread counter of Kbytes read.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.23 clusmodulestatsioswrite counter of IO write operations.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.22 clusmodulestatsiosread counter of IO read operations.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.21 clusmodulestoragestatus storage status of a module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.19 clusmoduleraidstatus RAID status of a module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.10 clusmoduleavailsize available storage size of module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.9 clusmoduleserialno serial number of module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.6 clusmodulename hostname of module.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.4.1.3.6.1.4.1.9804.3.1.1.2.12.46.1.2 Snapshots: clusvolumesnapshotstatsaheadhits counter of read ahead hits.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.45 clusvolumesnapshotstatscachehits counter of cache hits.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.44 clusvolumesnapshotstatsiolatencywrite time spent waiting for write operations to complete for this snapshot.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.43 clusvolumesnapshotstatsiolatencyread time spent waiting for read operations to complete for this snapshot.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.42 clusvolumesnapshotstatsqdepthwrite number of pending write operations.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.41 clusvolumesnapshotstatsqdepthread number of pending read operations.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.40 clusvolumesnapshotstatskbyteswrite counter of Kbytes written.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.39 clusvolumesnapshotstatskbytesread counter of Kbytes read.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.38 clusvolumesnapshotstatsioswrite counter of IO write operations.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.37 clusvolumesnapshotstatsiosread counter of IO read operations.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.36 clusvolumesnapshotprovisionedspace maximum space used by snapshot (high watermark).1.3.6.1.4.1.9804.3.1.1.2.12.101.1.32 clusvolumesnapshotclusterusedpercent clusvolumesnapshotusedspace clusvolumesnapshotcopyprogress maximum space used by snapshot and writable space (high watermark) as a percent of cluster space maximum space used by snapshot (high watermark) percentage progress of a remote IP copy (if a remote copy is in progress).1.3.6.1.4.1.9804.3.1.1.2.12.101.1.31.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.28.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.16 clusvolumesnapshotsize size of the snapshot in Kbytes.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.5 clusvolumesnapshotname snapshot name.1.3.6.1.4.1.9804.3.1.1.2.12.101.1.2 64 Appendix B