Hardware Sentry KM for NetApp Filers - Sentry Software · PDF fileUser Guide 9 Version 1.6.00...

Hardware Sentry KM for NetApp FilersUser Guide

SupportingHardware Sentry KM for NetApp Filers

Version 1.6.00

April 2009

Contacting BMC Software

You can access the BMC Software Web s i te at http://www.bmc.com/. From this Web s i te, you can obta ininformation about the company, i ts products , corporate offices , specia l events , and career opportuni ties .

United States and Canada Outside United States and Canada

Address BMC Software, Inc.2101 CityWest Blvd. Houston TX 77042-2827

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

Copyright 2006 BMC Software, Inc. or l i censors , as an unpubl i shed work. Al l rights reserved.

BMC Software, the BMC Software logos , and a l l other BMC Software product or service names are regis teredtrademarks or trademarks of BMC Software, Inc.

IBM is a regis tered trademark of International Bus iness Machines Corporation.

DB2 i s a regis tered trademark of International Bus iness Machines Corporation.

Oracle i s a regis tered trademark, and the Oracle product names are regis tered trademarks or trademarks ofOracle Corporation.

Al l other trademarks belong to thei r respective companies .

BMC Software cons iders information included in this documentation to be proprietary and confidentia l . Youruse of this information i s subject to the terms and conditions of the appl icable End User License Agreementfor the product and the proprietary and restricted rights notices included in this documentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THECOPYRIGHT LAWS OF THE UNITED STATES. Use, dupl ication, or disclosure of any data and computer software bythe U.S. Government i s subject to restrictions , as appl icable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time.Contractor/Manufacturer i s BMC Software, Inc., 2101 Ci tyWest Blvd., Houston, TX 77042-2827, USA. Any contractnotices should be sent to this address .

2

Hardware Sentry KM for NetApp FilersVers ion 1.6.00

Customer supportYou can obtain technical support by using the Support page on the BMC Software Web site or by contactingCustomer Support by telephone or e-mail. To expedite your inquiry, please see "Before Contacting BMCSoftware."

Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can

· Read overviews about support services and programs that BMC Software offers:

§ Find the most current information about BMC Software products

§ Search a database for problems similar to yours and possible solutions

§ Order or download product documentation

§ Report a problem or ask a question

§ Subscribe to receive e-mail notices when new product versions are released

§ Find worldwide BMC Software support center locations and contact information, including e-mailaddresses, fax numbers, and telephone numbers

Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call800 537 1813. Outside the United States and Canada, please contact your local support center for assistance.To find telephone and email contact information for the BMC Software support center that services yourlocation, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support canbegin working on your problem immediately:

3

Vers ion 1.6.00Hardware Sentry KM for NetApp Filers

http://www.bmc.com/support_home



4Table of Contents


Table of Contents

.........................................................................................................................................6Foreword

.........................................................................................................................................7User Guide

..........................................................................................................................................7Monitoring with NetApp Filers KM for PATROL

..............................................................................................................................8Adding a NetApp Filer

..............................................................................................................................9NetApp Filers KM Menu Commands

..............................................................................................................................9Monitoring NetApp Filers

.............................................................................................................................9Monitoring NFS Cache

.............................................................................................................................11Monitoring System Statistics

.............................................................................................................................12Monitoring Backups

.............................................................................................................................12Monitoring vFilers

.............................................................................................................................13Monitoring SnapVault

.............................................................................................................................13Monitoring SnapMirror

.............................................................................................................................14Monitoring Quota

.............................................................................................................................14Monitoring File System

.............................................................................................................................15Monitoring LUNs

..............................................................................................................................16Missing Component Detection

..............................................................................................................................17Administrative Tasks

.............................................................................................................................18Edit NetApp Server Configuration

.............................................................................................................................19Pause/Resume Monitoring

.............................................................................................................................20Terminate the Monitoring of a Component

.............................................................................................................................20Restore Component Monitoring

.............................................................................................................................22Reinitialize the KM

.............................................................................................................................24Java Settings

.............................................................................................................................27Generate Usage Reports

.............................................................................................................................29Enabling the Debug Mode

..............................................................................................................................30Thresholds, Alerts and Notifications

.............................................................................................................................30Customize the Polling Interval

.............................................................................................................................31Threshold Mechanism Selection

.............................................................................................................................32Modify Alert Thresholds

5Table of Contents


.............................................................................................................................36Alert after N Times

.............................................................................................................................36Alert Actions

.............................................................................................................................38Edit Alert Actions

..........................................................................................................39Trigger a PATROL Event

..........................................................................................................39Annotate the Parameter’s Graph

..........................................................................................................40Execute an OS Command

..........................................................................................................41Execute a PSL Command

..........................................................................................................42Send a Pop-up to the PATROL Consoles

..........................................................................................................43Write a Line to a LOG File

..........................................................................................................43Send a Basic SNMP Trap

..........................................................................................................44Send a custom SNMP trap (advanced)

..........................................................................................................45Send an E-mail

.............................................................................................................................45Alert Actions Macros

6Foreword


ForewordMeeting expected service levels in heterogeneous storage environments that include both SAN and NASimplementations is becoming increasingly difficult. Varying management products increase the burden onIT staff to adequately administer these differing technologies. NetApp Filers KM for PATROL offers monitoringand reporting capabilities integrated to the PATROL console for creating a common management platform foradministering all networked storage in your environment. This enables you to easily meet all your storageservice-level requirements while improving operational efficiency.

By monitoring all storage assets within a centralized management console, you can respond quickly toperformance problems, easily determine capacity requirements, and effectively plan for network expansions.

NetApp Filers KM for PATROL has been designed to monitor NetApp Filers performance metrics and usagestatistics. The software actually completes the range of hardware components monitoring features providedby BMC Hardware Sentry.

7User Guide


User Guide

Monitoring with NetApp Filers KM for PATROL

Monitoring NetApp Filers with NetApp Filers KM for PATROL is very simple. Once the KM is properly installed,as per the instructions given in the Installation Guide, NetApp Filers KM for PATROL automatically detectsall the various NetApp features and components and displays them in the PATROL interface. There is noconfiguration or “set–up” to be done in order to monitor NetApp Filers. All you have to do is set/modifythresholds (if required) and set alert actions as per your specific requirements in order to be notified aboutan error or failure. This section gives details about all the features and the components monitored by NetAppFilers KM for PATROL.

For details on which performance metrics and usage statistics are detected on each system, please see the Classesand Parameters section in the Reference Guide.

8User Guide


Adding a NetApp FilerAll NetApp Filers that you need to monitor must be added in the PATROL Console.

To add a NetApp Filer to the PATROL console, right-click the NetApp Filer main icon > KM Commands > Add aNetApp Filer:

1. Enter the Host name or IP address. Press Next to continue.

9User Guide


2. Enter the name of the SNMP community you wish to use. Press Finish to validate.

A new icon representing the NetApp Filer is automatically added to the PATROL console underneath theNetApp Filers KM for PATROL main icon. The component is then ready to be monitored.

NetApp Filers KM Menu CommandsNetApp Filers is the main NetApp Filers KM for PATROL icon for each managed system. The menu commandsavailable from this icon apply to the entire managed system.

· Right-click the NetApp Filers KM icon > KM Commands

· Add a NetApp Filer: Enables you to add a NetApp Filer to the console

· KM Settings: Displays all the menu command options for different monitoring settings

· Pause Monitoring: Enables you to pause the monitoring of the system

· Resume Monitoring: Enables you to resume the monitoring that’s been paused

· Reinitialize KM: Enables you to triggers a complete re-initialization of NetApp Filers KM for PATROL

· About: States basic product information and BMC Software support contact information

Monitoring NetApp FilersExponential growth in data storage has not only significantly increased the challenge for enterprises toensure data availabil ity, but also to ensure that the storage infrastructure is used efficiently for business-critical applications. NetApp Filers KM for PATROL automatically discovers components and enables themanagement of resources at various logical levels, ensuring that business needs are always met.

Monitoring NFS Cache

Network File System (NFS) is the protocol used by UNIX systems to access a fi lesystem from a remotemachine over the network.

NetApp Filers KM for PATROL provides administrators with valuable information to help them supervise NFSCache parameters. Any parameter can be viewed as graph by simply double-clicking on the parameter.

10User Guide


The system also provides NFS usage statistics on an hourly/daily basis for a defined period of time. Toaccess this feature, right-click the NFS Cache icon > KM Commands > Generate Usage Report.

Use the “Client – Received Bytes Rate” parameter to view the instantaneous per second rate value.

11User Guide


Monitoring System Statistics

System statistics provide useful information related to performance and usage of NetApp Filers; NetAppFilers KM for PATROL automatically detects the information sources available on the monitored componentand displays the storage information provided by those sources in the PATROL interface.

Most of the monitored parameters data, including auto support, cluster status, CPU usage, etc can be viewedas a graph. Double-click the a parameter to display a graph in the right pane of console.

12User Guide


Monitoring Backups

NetApp Filers KM for PATROL enables administrator to monitor backups of NetApp Filers. Successfulcompletion of your backups is critical to prevent recovery problems.

NetApp Filers KM for PATROL provides the number of active, attempted, failed and successful dumps andrestores. All dumps and restores history can be viewed as a graph by simply double-clicking the appropriateparameter.

Monitoring vFilers

A vFiler unit results of the partitioning of a "storage system". A vFiler unit, using the resources assigned,delivers fi le services to its cl ients as a storage system does. The storage resource assigned to a vFiler unitcan be one or more qtrees or volumes. The network resource assigned can be one or more base IP addressesor IP aliases associated with network interfaces.

NetApp Filers KM for PATROL monitors vFilers and displays their status directly in the component label.vFilers status history can be displayed as a graph by clicking on the Status parameter located directlyunderneath the vFiler icon of the PATROL console.

13User Guide


You can easily set alert conditions for vFilers by right-clicking the vFiler icon > KM Commands > Modify AlertThresholds...

After modifying any settings, refresh the data display of the console by right-clicking the vFiler icon > KM Commands> Refresh Parameters...

Monitoring SnapVault

SnapVault is a disk-based storage backup feature of Data ONTAP that enables data stored on multiplestorage system and Open Systems (non-fi ler) storage systems to be backed up to a central, secondary storagesystem quickly and efficiently as read-only snapshots. In event of data loss or corruption on a storagesystem or open storage system, backed up data can be restored from the SnapVault secondary storagesystem to the primary or open storage system with l ittle of the downtime and uncertainty associated withconventional tape backup and restore operations.

NetApp Filers KM for PATROL simplifies tracking the status of backup operations and provides valuableinformation to help administrator manage data transfers.

SnapVault parameters and status history can be displayed as a graph by clicking on the Status parameterlocated directly underneath the SnapVault icon of the PATROL console.

You can easily set alert conditions for SnapVault by right-clicking the SnapVault icon > KM Commands >Modify Alert Thresholds...

After modifying any settings, refresh the data display of the console by right-clicking the SnapVault icon > KMCommands > Refresh Parameters...

Monitoring SnapMirror

SnapMirror is an util ity in NetApp to do data transfer across fi lers. SnapMirror works at Volume level orqtree level. It replicates data from one volume or qtree (the source) to another volume or qtree (the mirror)and periodically updates the mirror to reflect incremental changes on the source. The result of this processis an online, read-only volume (the mirror) that contains the same data as the source volume at the time ofthe most recent update.

NetApp Filers KM for PATROL monitors SnapMirror jobs to confirm that data is being mirrored properly,provide alerts when data replication policies are not being met, and produce key reports for trackingSnapMirror relationships and util ization to ensure data protection.

14User Guide


For convenience, the component status is directly displayed in the element label.

Monitoring Quota

A disk quota is a set of rules that restrict disk space and the number of fi les used by a user or a group. Aquota can also restrict the total space and fi les used in a qtree or the usage of users and groups within aqtree. For example, you could create a user quota that specifies that a particular user can use up to 225MBof disk space in a given qtree in a given volume before a warning is issued (soft l imit) and up to 250MBmaximum (hard l imit).

NetApp Filers KM for PATROL monitors NetApp Quota and provides a Status (running/suspended/missing) foreach volume monitored. The status history can be displayed as a graph by simply double-clicking the Statusparameter of the appropriate volume.

Monitoring File System

NetApp Filers KM for PATROL enables system administrators to easily monitor File System space usage, inorder to efficiently manage storage resources.

In the PATROL Console, Aggregate/Volume labels show the component's state, type, capacity usage andstatus. Each parameter may be viewed as graph by simply double-clicking it.

15User Guide


After modifying any settings, refresh the data displayed by the console by right-clicking the vFiler icon > KMCommands > Refresh Parameters...

Monitoring LUNs

NetApp Filers KM for PATROL monitors Logical Unit (LUN) and provides written and read bytes count for eachmonitored component. The Error Count parameter indicates the total number of errors seen on this LUN sincethe stats were last reset. In a normal situation, this parameter’s value is always zero. Its value changes toone when an error occurs and goes back to zero (no alert) at the next poll ing.

All LUN usage history can be displayed as a graph by simply double-clicking the appropriate parameter.

16User Guide


You can easily set alert conditions for SnapVault by right-clicking the SnapVault icon > KM Commands >Modify Alert Thresholds...

After modifying any settings, refresh the data display of the console by right-clicking the SnapVault icon > KMCommands > Refresh Parameters...

Missing Component DetectionThe missing component detection mechanism of NetApp Filers KM for PATROL alerts operators when anelement that was previously detected in the system is no longer found.

This mechanism is very useful when, for example, the configuration of a LUN is accidentally altered andtherefore is no longer seen by the operating system and the monitoring software.

When a component is no longer discovered, its Status parameter goes into alarm and its label directlyshows that it is missing. The missing component detection feature is enabled by default. You can howeverdeactivate the feature by right-clicking on the Hardware icon > KM Commands > KM Settings > MissingComponent Detection.

17User Guide


Disabling this option when some missing components have already been detected will trigger a removal of thesecomponents from the monitoring environment.

Administrative Tasks

This section deals with information on basic configuration and administrative tasks such as:

· Editing NetApp Server Configuration

· Pause the monitoring of a component

· Resume the monitoring of a component

· Terminate the monitoring of a component

· Configure Java settings

18User Guide


Edit NetApp Server Configuration

NetApp Filers KM for PATROL provides a wizard to help administrators configuring NetApp Servers.

1. Right-click on the monitored element > KM Commands > Edit2. Enter the name of the system you wish to monitor or its IP address and click Next to continue.

Enter the appropriate SNMP Community and click Finish to validate your changes.

19User Guide


Pause/Resume Monitoring

In order to perform certain tasks - maintenance for example, it is often useful to pause the monitoring of anobject or even of the whole system by NetApp Filers KM for PATROL.

Right-click the component icon > KM Commands > Pause Monitoring.

When in paused state, the object/system is sti l l displayed in the PATROL Console but in an OFFLINE statusand no collect for that particular object is executed.

To restart the monitoring of the object/system click Resume Monitoring in the menu.

20User Guide


Terminate the Monitoring of a Component

Whenever the supervision of a component becomes irrelevant, administrators can terminate its monitoringby right-clicking the component icon > KM Commands > Remove.

The component icon is then removed from the Console and the data collection for this particular componentwill no longer be performed.

Restore Component Monitoring

It is possible to restore component monitoring with NetApp Filers KM for PATROL after it has been removedfrom monitoring through the Remove option.

To see the l ist of the removed objects or to restore a component monitoring:

1. Right-click the NetApp Filers icon > KM commands > KM Settings > Restore Component.

The first step of the procedure consists in selecting all or a specific component to restore. Click Next tocontinue.

21User Guide


If All is selected, the l ist of all components that had been removed and that will be restored is displayed.Click Next to continue.

However, if a component is selected, a l ist is displayed to enable to selection of a specific component.Click Next to continue.

2. Select one or several specific components or select the option Restore all components and sensors inthe l ist above, and click Finish.

22User Guide


Had you have chosen to restore All components and sensors monitoring in the first window; this second windowwould just display the list of components that would be restored.

Reinitialize the KM

If ever NetApp Filers KM for PATROL does not function properly: displays components as missing that youknow are present, or does not detect several components as it should etc., it is possible to reinitialize theconfiguration and let NetApp Filers KM for PATROL re-start monitoring from scratch.

The above cases of malfunction could occur after a configuration change or especially after a software/hardware upgrade etc.

In such a case, you can reinitialize the KM, and the KM will then run a full discovery and re-start themonitoring of existing and new components. Thresholds will be set to default so all previously manually setthresholds will be lost, unless specified otherwise in the Reinitialize KM wizard shown below.

23User Guide


1. To reinitialize NetApp Filers KM for PATROL: Right-click the NetApp Filers KM icon > KM Commands >Reinitialize KM:

Select the options as per your specific needs:

Alert thresholds and actions

§ Remove manually customized alert thresholds: Selection removes all customized thresholds.

§ Reset the threshold mechanism mode to default: Selection makes the KM revert to the default mode i.e. NetApp Filers KM for PATROL selects the mechanism is best suited to the system.

§ Reset Alert Actions: Selection removes all manually set Alert Actions and reverts to basic defaultactions i.e. Trigger a PATROL event and Annotate a parameter graph.

§ Reset other alert and threshold settings: Selection reverts any manually done configuration changesto default NetApp Filers KM for PATROL values.

Misc. options

§ Deactivate the debug mode: Selection deactivates the debug mode if manually enabled.

§ Restore and resume paused/removed objects: Selection restores all paused or removed objects.

Save reinitialize settings

24User Guide


§ Save reinitialize setting: Selection saves the defined settings that will then be considered as default.

In cases where configurations have been manually set in the PATROL Agent, there will be an additional sectioncalled Internal KM engine options displaying the used configuration variables and the option whether or not toremove them.

3. Click Reinitialize.

Java Settings

The Java Settings wizard enables you to define which Java instance is to be used by NetApp Filers KM forPATROL for managing the E-mail alert action only when using the version 3.6.0.11 (or older) of PATROL agent.

You can either use the automatic detection, select a pre-detected java path or enter manually the pathleading to the Java executable directory to be used.

To access the Java Settings wizard, right-click the main NetApp Filers KM icon > KM commands > KM Settings> Java Settings.

Select the Java executable detection method: Select one of the three following options:

· Let NetApp Filers KM automatically detect the Java path: Select this option if you wish NetApp Filers KMfor PATROL to detect the Java executable directory by itself upon each discovery.

· Select a Java path detected by NetApp Filers KM: Select this option if you wish to select a Javaexecutable directory within a l ist of pre-detected executables.

· Enter manually the Java path to be used by NetApp Filers KM: Select this option if you wish to manuallyenter the Java executable directory path.

Click Next to continue.

Automatic Detection

If you have selected the automatic detection at the previous step of the wizard, NetApp Filers KM for PATROLdisplays the path of the Java executable directory that will be used when performing commands requiringJava features.

25User Guide


Click Finish to save your settings.

User Selection

If you have selected the user selection option at the previous step of the wizard, NetApp Filers KM for PATROLdisplays a l ist of all the Java executable directory found on your machine.

Select the Java executable directory you wish NetApp Filers KM for PATROL to use when performingcommands requiring Java features and click Finish to save your settings.

26User Guide


Manual

If you have selected the Manual option at the previous step of the wizard, NetApp Filers KM for PATROL letyou enter the path to the Java executable directory you wish the application to use when performingcommands requiring Java features. Click Finish to save your settings.

27User Guide


Generate Usage Reports

To facil itate the monitoring of LUN, Backups and NFS Cache, NetApp Filers KM for PATROL providescustomizable usage reports.

28User Guide


1. Right-click the monitored component > KM Commands > Generate Usage Report:

Set the parameters you wish to apply to the usage report:

· Build a report for the pas x hours/days: Use the up and down arrows to set the number of hours/daysfor which you need to generate the report and select the time/day range.

· Using a hourly/daily interval: select the interval on which you wish to base the usage report

3. Click Show Reports to generate the usage report:

29User Guide


Enabling the Debug Mode

By default, NetApp Filers KM for PATROL sends only the most critical information, warning and errormessages to the System Output Window of the PATROL Consoles. Most often, this information is accurateenough to ensure that NetApp Filers KM for PATROL is working properly.

If you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the DebugMode and provide the debug output to the Sentry Software support team.

To enable the debug mode:

1. Right-click the main NetApp Filers KM icon > KM Commands > KM Settings > Debug...

2. Select Enable debug.

There could be some loss of debug information by the PATROL console, if debug is enabled just as the PATROLAgent is starting as it is not yet connected to the PATROL Agent. In other cases, or when you want to trace theactivity of NetApp Filers KM for PATROL during a few minutes, some debug information may be lost by thePATROL Console owing to a full buffer.

In such cases, it may help to send the debug output of NetApp Filers KM for PATROL to a specified fi le.

The debug file is stored on the computer where the Agent is running.

Pay attention to the file size. The debug output of NetApp Filers KM for PATROL may be very large if running forseveral days.

30User Guide


Thresholds, Alerts and NotificationsThis section deals with thresholds, alerts and notification. Alert thresholds are dynamically set by NetAppFilers KM for PATROL. However, it is possible to change the thresholds, the alert settings as well as thethreshold mechanism itself. the KM also offers you the possibil ity of selecting the type of notification (Alertactions) to be performed once an alert is raised. The section has the following sub-sections:

· Threshold Mechanism Selection

· Modifying alert thresholds on parameters

· Alert after N times – advanced alert settings

· Alert Actions

Customize the Polling Interval

A poll ing interval defines how often new data is collected. A new collect can be performed from once everysecond, to once in a day. NetApp Filers KM for PATROL polls the managed systems to collect performance andstatistics data. By default, the poll ing interval for this "data-collect" is set to every 2 minutes.

To change the poll ing interval for the managed system, right-click the NetApp Filers KM icon > KM Commands> KM Settings > Polling Interval…

In addition to the polling interval that is a global setting, i.e. it is applicable to the whole managed system, you canalso manually trigger a poll at any time on individual instances to refresh parameter values. Right-click the instanceicon > Refresh Parameters.

31User Guide


Threshold Mechanism Selection

Managing thresholds means selecting/modifying the mechanism by which NetApp Filers KM for PATROL setsthresholds for all parameters of the monitored components. This is done through the menu command: KMSettings > Threshold Mechanism Selection.

By default, NetApp Filers KM for PATROL automatically sets alert thresholds on the monitored parameters.

The different threshold mechanisms

To set the thresholds, NetApp Filers KM for PATROL uses one of the following two mechanisms, best suited tothe managed system:

Tuning: A standard internal PATROL mechanism, known as the Override parameters in PATROL but calledTuning in NetApp Filers KM for PATROL. With this mechanism, NetApp Filers KM for PATROL sets thethresholds of each parameter of each monitored object by setting a specially formatted variable under the /___tuning___ tree in the PATROL Agent configuration.

Or

PCM/Event Management: PATROL for Event Management (formerly known as EventSpring) or PATROLConfiguration Manager or PCM, formerly known as AgentSpring

By default, NetApp Filers KM for PATROL determines which of the above two mechanisms is best suited to themanaged system and uses that. This is the Automatic setting in the Threshold Mechanism Selection wizard.

To see which mode is currently used for the system, or to modify the Automatic mechanism, right-click: themain NetApp Filers KM > KM Commands > KM Settings > Threshold Mechanism Selection...

Select one of the following options:

32User Guide


· Automatic (default): NetApp Filers KM for PATROL determines and uses the threshold mechanism bestsuited to the managed system

· Tuning: If selected, NetApp Filers KM for PATROL will manage its thresholds through the standard theinternal PATROL mechanism (Override parameters). Thresholds are stored in the PATROL Agentconfiguration under the /___tuning___ tree.

· PCM/Event Management: if this option is selected, NetApp Filers KM for PATROL will manage itsthresholds through the PCM or Event Management mechanism. Thresholds are stored in the PATROLAgent configuration under the /AS tree. This option requires that you set up the PATROL for EventManagement KM on your PATROL Agent. PATROL for Event Management has to be enabled andpreloaded.

If you use PATROL for Event Management to manage thresholds in PATROL, it is strongly recommended that youuse this option in NetApp Filers KM for PATROL too.

In order to avoid side effects and unpredictable behavior, if you select the "PCM/Event Management" thresholdsmanagement option, NetApp Filers KM for PATROL will automatically remove the thresholds set through the othermethod. That is: if you select the "PCM/Event Management" option, NetApp Filers KM for PATROL willautomatically remove all the thresholds stored in the /___tuning___ tree in the PATROL Agent configuration.

· No Thresholds: NetApp Filers KM for PATROL will not set any thresholds on the monitored objects. Youare required to set them manually.

For details on how to manually set thresholds on the parameters, please see the topic: Modify AlertThresholds

Modify Alert Thresholds

Whenever possible, NetApp Filers KM for PATROL automatically sets thresholds for parameters. Thesethresholds are retrieved from the information available from the hardware agents and they are generallyaccurate.

Generally, there is no need to modify these thresholds but in case NetApp Filers KM for PATROL cannotobtain them, or if you prefer a more fault-tolerant monitoring, you can modify the thresholds of eachparameter through the command menu.

33User Guide


1. Right-click on the monitored element > KM Commands > Modify Alert Thresholds.

2. The first panel displays the l ist of parameters for the selected object. Select the parameter whosethresholds you wish to modify and click Next to continue.

3. The second panel enables you to select the alert threshold mode. Click Next to continue.

34User Guide


If you have selected the option Let NetApp Filers set appropriate alert thresholds, NetApp Filers KM forPATROL automatically determines and sets the alert thresholds best suited to the parameter/component/system. Click Next to view the threshold values and then Finish to validate the operation.

If you have selected the option Manually customize alert thresholds, a panel is displayed allowing youto define new threshold values for the parameter/component/system. Click Finish to validate theoperation.

35User Guide


If you select the Automatic thresholds mechanism option (see Managing the Threshold Mechanism), yourcustomized thresholds are stored under the /___tuning___ tree in the PATROL Agent configuration and then can bemodified through the "Override parameter" feature of the PATROL Console.

If you select the PCM/Event Management thresholds management option, your customized thresholds are storedunder the /AS tree in the PATROL Agent configuration and then can be modified through the PATROL for EventManagement (EventSpring) interface or through the PATROL Configuration Manager graphical user interface.

36User Guide


Alert after N TimesNetApp Filers KM for PATROL offers a global advanced alert setting in order to prevent false alerts. You cannow set/modify the number of times thresholds can be breached before triggering an alert.

This advanced alert setting, commonly known as "Alert after n times" is accessible by right-clicking the main NetApp Filers KM icon > KM Commands > KM Settings > Alert after N Times…

NetApp Filers KM for PATROL parameters can be categorized in three main groups:

· Numeric parameters: Parameters that have numeric values.

· Discrete parameters: Parameters that have values such as 0=OK, 1=Degraded/Predicted Failure, 2 =Failed etc. These parameters display the status of the component.

By setting or changing the number of times a threshold can be breached before it triggers an alert – you canavoid unnecessary false alerts.

This is a "global" setting, and applies to the parameters of all the monitored components of the system.

Alert Actions

Alert Actions enables the PATROL administrator to choose specific actions to be executed when a hardwarefailure is detected. With Alert Actions, it is possible to either:

· Customize the way a hardware problem notification is performed, or

· Specify a recovery action to be run when a problem occurs.

NetApp Filers KM for PATROL can be configured to run one, several, or all types of Alert Actions when an alertis triggered regarding the monitored hardware.

37User Guide


By default, upon NetApp failure, the KM triggers a PATROL event and annotates the parameter’s graph with acomprehensive report of the problem, giving details about the failure, the possible consequences and therecommended action to solve the problem.

The Alert Actions that can be performed by NetApp Filers KM for PATROL are:

· Trigger a PATROL event

· Annotate the parameter's graph

· Execute an OS command

· Execute a PSL command

· Send a pop-up to the PATROL consoles

· Write a l ine to a LOG fi le

· Send a basic SNMP trap (using the PATROL MIB)

· Send a custom SNMP trap

· Send an E-mail

Alert Actions are highly customizable. One can customize the string that is sent through SNMP, set theusername/password that is used to execute the OS Command, define the content of the PATROL event sent byNetApp Filers KM for PATROL, etc.

Additional information regarding the alert, such as the parameter name or its value, is available throughthe Alert Actions macros. This information can be used to further customize the Alert Action triggered byNetApp Filers KM for PATROL and provide more details about the problem that occurs.

38User Guide


Edit Alert Actions

To modify the Alert Actions executed by NetApp Filers KM for PATROL upon a hardware failure, right-click onthe main NetApp Filers KM icon > KM Commands > KM Settings > Edit Alert Actions…

Select the Alert Actions to be executed

Check the boxes corresponding to the actions you would l ike executed upon a hardware failure.

By default, NetApp Filers KM for PATROL triggers a PATROL event and annotates the parameter that raises thealert, but there are all the actions that can be triggered:

After selecting and defining Alert Actions, you need to validate your changes by clicking the Finish button.

39User Guide


If you select Trigger a PATROL Event, you need to enter the string that will be displayed with the event.

A PATROL Event can be viewed from:

· Standard PATROL Consoles (Classic Console, PATROL Central)

· PATROL Enterprise Manager

· BMC Impact Manager

· Other third-party products that interface with PATROL.

The PATROL event that is triggered is the ‘41’ event from the standard PATROL catalog. You can use macros thatwill be replaced at runtime. The Alert Actions Macro Variables states the list of available macros.

If you select the Annotate the parameter’s graph action, you need to enter the string that will be displayedwithin the annotation point.

40User Guide


You can use macros that will be replaced at runtime. The Alert Actions Macro Variables states the list of availablemacros.

If you select the Execute an OS command action:

Enter a command line to be executed

· Enter the username and password used to run the command.

The command can be a program util ity or a script shell, and can have arguments.

The command must be non-interactive (no window, no user input)


41User Guide


If you select the Execute a PSL command action, you need to enter the PSL statement to be executed by thePATROL Agent. Although only a single l ine is permitted, it can have several PSL instructions.

The PSL command is recommended for advanced user of PATROL.

You can use macros that will be replaced at runtime. The Alert Actions Macro Variables section states the list of allthe available macros.

42User Guide


If you select the Send a pop-up to the PATROL Consoles action, you need to enter the message that will bedisplayed in the pop-up as well as the in title of the pop-up window.

Too many pop-ups could annoy the operators.


43User Guide


If you select the Write a line to a LOG file action:

Enter the LOG fi le path and the content of the l ine.


If you select the Send a basic SNMP trap action:

Enter the following:

44User Guide


· IP address or hostname of the SNMP trap destination

· SNMP port and community string

· Text that will be sent in the SNMP trap

Upon a hardware failure, NetApp Filers KM for PATROL will send the trap that is defined in the PATROL MIB (Trapnumber 11, Enterprise ID: 1.3.6.1.4.1.1031.1.1.2, the text is stored in the 1.3.6.1.4.1.1031.1.1.2.1 OID). You can usemacros that will be replaced at runtime. The Alert Actions Macro Variables section states the list of availablemacros.

If you select the Send a custom SNMP trap action, you need to enter the following:

Enter the following:

· IP address or hostname of the SNMP trap destination

· SNMP port and community string

· All the characteristics of the trap: Enterprise ID, trap number and up to 4 varbinds.

45User Guide


If you select the Send an E-mail action, you need to complete the following panel:

Enter the sender and the recipient email addresses in respectively the From and To fields, and type the SMTPserver name. Finally, enter the email Subject and type the Body of the message you wish to send.

Alert Actions Macros

A macro is a variable whose value is replaced when an Alert Action is triggered. Macros can be used tocustomize the content of each Alert Action.

For example: %{VALUE} is replaced by the actual current value of the parameter that triggered the alert. Whenused in the text field for a PATROL event Alert Action, the percentage value is replaced by the actual currentvalue of the parameter that triggered the alert.

Each macro l isted in the tables below contains information about what triggered the PATROL alert.

Macros Description

%{PARAMETER_NAME} Name of the parameter that triggered the alertExample: PredictedFailure

%{VALUE} Formatted value (with unit) of the parameter that triggered the alertExample: 67.3 °C

%{OBJECT_ID} PATROL internal ID of the instance that triggered the alertExample: MS_HW_DellOpenManagehdf_11

46User Guide


Macros Description

%{OBJECT_LABEL} Display name of the instance that triggered the alertExample: Fan: 1.1 (CPU 1)

%{OBJECT_CLASS} Class of the instance that triggered the alertExample: MS_HW_FAN

%{FILER_LABEL} Filer displayed name

%{FILER_ID} Filer object ID

%{PARENT_ID} PATROL internal ID of the object that the faulty instance is attached toExample: MS_HW_DellOpenManagehdf_1

%{PARENT_LABEL} Display name of the object that the faulty instance is attached toExample: Computer: Dell PowerEdge 1600SC

%{PARENT_CLASS} Class of the object that the faulty instance is attached toExample: MS_HW_ENCLOSURE

%{DATE} Current date in the YYYY-MM-dd formatExample: 2005-6-23

%{TIME} Current time in the HH:MM:SS formatExample: 11:14:53

%{ASCTIME:…} Current date and time formatted as specified in the macroExample: %{ASCTIME:%m %d %T %Y} will produce Jun 6 11:14:53 2005The available formats for the %{ASCTIME:…} macro are l isted in theasctime() description of the PSL Reference Guide (Book 2)

%{/…} Recommended for advanced users only

Provides an internal instance variable name to be inserted. The pathis relative to the object triggering the alert

Example: %{/worstParam} will be contain the name of the worstparameter on this instance, which is an application instance built-invariable (see the "PATROL Script Language Reference" document)

%{NEWLINE} Linefeed.This is useful to produce multi-l ine information

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 revenues of more than $1.4 billion. For more information about BMC

Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software,provides key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

information about Sentry Software, please visit www.sentrysoftware.net.

103088

Hardware Sentry KM for NetApp Filers - Sentry Software · PDF fileUser Guide 9 Version 1.6.00...

Documents

Transcript of Hardware Sentry KM for NetApp Filers - Sentry Software · PDF fileUser Guide 9 Version 1.6.00...