CA Nimsoft Monitor Snap

Transcription

1 CA Nimsoft Monitor Snap Configuration Guide for SNMP data monitoring snmpcollector v1.1 series

2 Legal Notices Copyright 2013, CA. All rights reserved. Warranty The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control. Technology Licenses The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws. Restricted Rights Legend If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC s standard commercial license terms, and non-dod Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR (c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR (June 1987) or DFAR (b)(2) (November 1995), as applicable in any technical data. Trademarks Nimsoft is a trademark of CA. Adobe, Acrobat, Acrobat Reader, and Acrobat Exchange are registered trademarks of Adobe Systems Incorporated. Intel and Pentium are U.S. registered trademarks of Intel Corporation. Java(TM) is a U.S. trademark of Sun Microsystems, Inc. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Netscape(TM) is a U.S. trademark of Netscape Communications Corporation. Oracle is a U.S. registered trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of the Open Group. ITIL is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries. All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies. For information on licensed and public domain software, see the Nimsoft Monitor Third-Party Licenses and Terms of Use document at:

3 Contents Chapter 1: Overview 7 About This Guide... 7 Related Documentation... 7 Release Summary... 8 New Features... 8 Requirements... 8 Chapter 2: Configure the snmpcollector Probe 9 Verify Prerequisites... 9 Discover Your Devices Set Up SNMP Authentication Set the Path to the Discovery Server Discover Devices Apply Monitoring Advanced Configuration Customize Monitoring Turn Monitoring Off for Some Metrics or Components Chapter 3: Probe GUI Reference 23 SNMP Collector Probe Node Custom Monitors Node Metric Families Node Monitoring Configurations Node <Configuration Name> Node <Metric Family> Node (Configurations) <Rule Name> Node Profiles Node <Profile Name> Node <Device Name> Node <Metric Family> Node (Profiles) <Component Name> Nodes Thresholds Node Contents 3

4 Chapter 4: QoS Metrics 35 Chapter 5: Known Issues 41 Discovery Does Not Return Appropriate Data Device is Not Listed No QoS Data is Available Metric or Component is Not Monitored A Rule Has Disappeared Thresholds Node is Not Listed Configuration Guide for SNMP data monitoring

5 Documentation Changes This table describes the version history for this document. Version Date What's New? November 2013 Added chapter on QoS metrics. 1.1 September 2013 Changes to reflect additional default rules, changes to metric families, and other GUI changes. 1.0 June 2013 Initial release of web-based GUI probe configuration. Documentation Changes 5

6

7 Chapter 1: Overview Simple Network Management Protocol (SNMP) is an internet-standard protocol for managing devices on IP networks and consists of a set of standards for network management, including an application layer protocol, database schema, and set of data objects. Typical devices that support SNMP are routers, switches, servers, workstations, and printers. SNMP agents expose management data in the form of variables that describe the system configuration. This protocol allows you to modify and apply a new configuration through remote modification of these variables. The variables are organized in tree-structures which are described by Management Information Bases (MIBs). A MIB is a virtual database used for managing the entities in a communications network. Each entry in the database is addressed through an object identifier (OID). Each OID identifies a variable that can be read or set using SNMP. The Simple Network Management Protocol Collector probe allows you to monitor network-attached devices for conditions that require administrative attention. This section contains the following topics: About This Guide (see page 7) Related Documentation (see page 7) Release Summary (see page 8) Requirements (see page 8) About This Guide This guide is for the CA Nimsoft Monitor Snap Administrator to help understand the configuration of the SNMP data monitoring probe. Related Documentation For related information that may be of interest, see the following material: Related Documentation The Release Notes for the snmpcollector probe (SNMP data monitoring) Chapter 1: Overview 7

8 Release Summary Release Summary Please refer to the Nimsoft Compatibility Support Matrix for the latest information on supported platforms. See also the Support Matrix for Nimsoft Probes for additional specific information on the SNMP data monitoring probe. New Features Additional metric families Automatic subcomponent discovery Additional rules added to the default monitoring configuration Improved discovery performance Requirements The SNMP data monitoring probe requires: CA Nimsoft Monitor Snap version 7.0 or later CA Unified Management Portal (UMP) version 7.0 or later CA Nimsoft Monitor Snap discovery_server probe version 7.0 or later on the primary hub CA Nimsoft Monitor Snap ppm probe version 2.10 or later on the primary hub.net version 3.5 on the robot where the probe is installed for Windows systems 8 Configuration Guide for SNMP data monitoring

9 Chapter 2: Configure the snmpcollector Probe This section contains configuration details specific to the SNMP data monitoring probe. Important! For Admin Console users, you must know the path to your primary hub. See the topic Set the Path to the Discovery Server (see page 15). The primary hub must have the discovery_server 7.0 and ppm 2.10 probes installed and running. Important! An SNMP authentication profile must be created using the Discovery Wizard before the SNMP data monitoring is configured. If the SNMP authentication profile is not configured appropriately the SNMP data monitoring probe discovery query will not return an accurate list of devices. This section contains the following topics: Verify Prerequisites (see page 9) Discover Your Devices (see page 10) Apply Monitoring (see page 16) Advanced Configuration (see page 16) Verify Prerequisites Before configuring the SNMP data monitoring probe, verify that required software and information is available. Follow these steps: 1. Verify in the Admin Console that the following probes are installed and running on the primary hub: discovery_server version 7.0 or later ppm version 2.10 or later Note: Users of CA Nimsoft Monitor Snap Snap can skip this step. Snap comes packaged with the necessary probes. 2. Have the following information: IP address for the CA Unified Management Portal (UMP) version 6.6 or later Login credentials for UMP SNMP credentials Path to your CA Nimsoft Monitor Snap primary hub Chapter 2: Configure the snmpcollector Probe 9

10 Discover Your Devices Discover Your Devices The CA Nimsoft Monitor Snap Discovery Server discovers the SNMP devices in your environment. However, before running the Discovery Server you must create SNMP authentication credentials in the CA Unified Management Portal (UMP) Discovery Wizard and enter the path to the discovery_server probe in the SNMP data monitoring configuration GUI. The following sections provide detailed instructions for completing discovery. Set Up SNMP Authentication Authentication credentials for your SNMP devices are entered in the Discovery Wizard, accessed from the CA Unified Management Portal (UMP). Credentials are stored in authentication profiles, which are used by the discovery_agent probe to access and gather information about computer systems and devices in your network. You can create multiple SNMP authentication profiles. Important! Be cautious about modifying existing SNMP authentication profiles in the Discovery Wizard. If you change an authentication profile that is in use, monitoring on devices using this profile may fail. Follow these steps: 1. Enter the IP address for UMP in your browser. The login screen for UMP is displayed. 2. Log into UMP. If this is the first time you have logged into UMP, the Discovery Wizard may be displayed. If so, skip the following step. If the Discovery Wizard is not displayed, you see the Unified Service Manager (USM) portlet. 10 Configuration Guide for SNMP data monitoring

11 Discover Your Devices 3. Under the Discovery node in the tree, hover over the name of your primary hub and click the Discovery Wizard icon ( ). The Discovery Wizard is launched. 4. Click the SNMP tab. 5. Click New credentials. 6. Enter information in all required fields (outlined in red). If you are using SNMP v3, set the following values: Method = MD5 or SHA Privacy protocol = DES For a description of each field, see SNMP Credential Settings (see page 12). 7. Click the Ranges tab. 8. Specify a mask, range, or single IP address, then assign your SNMP authentication profile to the specified ranges. Note: To avoid unnecessary authentications traps/alerts, assign only one SNMP authentication credential per discovery range. If you have a device that accepts only a unique SNMP community string, create a Single type range and specify the device's IP address. Assign the corresponding authentication profile to the range. For more information, see Define a Discovery Range (see page 14). Chapter 2: Configure the snmpcollector Probe 11

12 Discover Your Devices SNMP Credential Settings 9. Save your changes and exit the Discovery Wizard. SNMP credentials are now configured for your CA Nimsoft Monitor Snap system, including the SNMP data monitoring probe. SNMP (Simple Network Management Protocol) is a widely-used standard protocol for managing devices on IP networks. CA Nimsoft Discovery supports SNMP versions 1, 2c, and 3. SNMP v3 adds security features which v1 and v2c lack. As a result, authentication profile configuration fields in the Discovery Wizard that deal with security and privacy (encryption) are only active when 3 is selected in the Version pull-down menu. We recommend the following best practices: Create a minimal set of SNMP Authentication Profiles that will, in aggregate, provide SNMP access to all your network devices and hosts that support SNMP. Set up as many of your network devices as possible to use "universal" read-only credentials. For example, you could define a read-only (get-only) credential to be nms_get_only. Create an authentication profile that uses that. Then set up every device possible to allow read-only SNMP access via this universal credential. This minimizes the number of SNMP authentication credentials that must be attempted on network nodes, and simplifies your discovery configuration. If there are devices that accept unique SNMP credentials, create one authentication profile for each of those. Field (SNMP v1 or v2) Required Description Description Yes Name for the authentication profile ID This read-only field is the Nimsoft system ID for this authentication profile, assigned when the profile is saved. It identifies the profile uniquely for re-use in other areas of USM that reference authentication profiles. Version Yes The SNMP version supported by the monitored device. When version 1 or 2 is selected, only the Community field is active. Community Yes The SNMP community string. Check Show new passwords to verify the text as you enter it. Be aware that this string is sent across the network in clear text as part of SNMP v1 or v2c requests, which may pose a security risk. 12 Configuration Guide for SNMP data monitoring

13 Discover Your Devices Field (SNMP v3) Required Description Description Yes Name for the authentication profile ID This read-only field is the Nimsoft system ID for this authentication profile, assigned when the profile is saved. It identifies the profile uniquely for re-use in other areas of USM that reference authentication profiles. Version Yes SNMP version supported by the monitored device. Versions 1, 2c, and 3 are supported. When v3 is selected, other fields for security and privacy are enabled. Password See note The password associated with the SNMP v1/v2c device or SNMP v3 user. Check Show new passwords to verify the text as you enter it. Note: This field is enabled and required if either AuthNoPriv or AuthPriv security is selected. See the description for the Security field below. User Yes SNMP v3 user name used to access the monitored device. Required for all SNMP v3 security levels. See the description for the Security field below. Method Yes SNMP v3 method of encryption, when AuthPriv security is selected (see the description for the Security field below): None MD5 - MD5 Message-Digest Algorithm (HMAC-MD5-96) SHA - Secure Hash Algorithm (HMAC-SHA-96) Security Yes SNMP v3 security level of the user. Depending on what level of security is selected, other security fields are enabled or disabled. NoAuthNoPriv - messages sent unauthenticated and unencrypted AuthNoPriv - messages sent authenticated but unencrypted AuthPriv - messages sent authenticated and encrypted Chapter 2: Configure the snmpcollector Probe 13

14 Discover Your Devices Priv.Password See note SNMP v3 privacy password to use if AuthPriv security level is selected. Must be at least eight characters. Do not confuse with the user password (authentication). Note: This field is enabled and required if AuthPriv security is selected Priv.Protocol See note SNMP v3 privacy (encryption) protocol to use. DES - Data Encryption Standard AES - Advanced Encryption Standard Note: Enabled and required if AuthPriv is selected. Define a Discovery Range Note: AES is not supported by the SNMP data monitoring probe. Choose DES for the Privacy Protocol. 1. Click New range in the left pane of the Ranges tab. 2. Enter a name for the range. 3. In the Range definition section, enter one of the following to specify the area(s) of your network where you want to perform discovery: Mask - Bitmask for a subnet using Classless Inter-Domain Routing (CIDR) notation with a base IP address and a routing prefix. For example, /24. The value /24 refers to a Class C subnet of 256 addresses. Other values for reference: /30 (4 addresses) and /16 (65,536 addresses, or a Class B subnet). Range - Range of IP addresses. Single - Single IP address. An additional field is automatically added if you type the hyphen (-) or slash character (/) to enter a range or mask. The pull-down menu also dynamically updates if you enter a range or mask. 4. To add another IP range, address, or mask, click New IP range or single IP address and repeat the previous step. 5. In the Credentials section, you can assign authentication profiles to the selected range. By default, all of the authentication profiles are selected. If you have a large number of authentication profiles in the list, you can enter the name of a profile to filter the list. To view only the profiles that are selected, click the Hide unused credentials check box. When you have finished defining ranges, click Next. 14 Configuration Guide for SNMP data monitoring

15 Discover Your Devices Set the Path to the Discovery Server Set the path to the discovery_server probe, which must be installed and running on your CA Nimsoft Monitor Snap primary hub. The discovery_server discovers the subcomponents (such as router interfaces) of your SNMP devices. Note: Users of CA Nimsoft Monitor Snap Snap can skip this step. The correct path to the discovery_server is already set in Snap. Follow these steps: 1. In the SNMP data monitoring probe configuration GUI, click the top node in the tree, SNMP Collector Probe. 2. Enter the path to the discovery_server probe in the Address of discovery_server Probe field in the Probe Configuration section. The path must be the complete path, in the following pattern: /<domain>/<hub>/<robot>/discovery_server 3. Click Save. Discover Devices Use the Discovery Server to obtain the list of devices available on your CA Nimsoft Monitor Snap system. Follow these steps: 1. Click the Options icon ( ) next to the Profiles node. 2. Click Query Discovery Server. Device discovery is launched. When discovery is complete, a Success dialog is displayed. 3. Click Reload to refresh your screen. A profile for each device is listed under the Profiles node. When the profile is first added, discovery for the device's subcomponents runs and the profile icon ( ) indicates that subcomponent discovery is pending. This may take some time when your devices are first discovered. When subcomponent discovery completes the profile icon indicates its status is OK ( ). You can also check the status of subcomponent discovery by going to SNMP Collector Probe > Profiles > profile name > device name and viewing the Component Discovery field. Chapter 2: Configure the snmpcollector Probe 15

16 Apply Monitoring Apply Monitoring Once discovery is complete, you are ready to apply monitoring for your devices. Note: Users of CA Nimsoft Monitor Snap Snap can skip this step. The Default configuration is automatically applied to your SNMP devices when you activate the SNMP data monitoring probe in Snap. To apply monitoring, we recommend you start by applying the default monitoring configuration. You can also customize monitoring; see the advanced configuration topic Customize Monitoring (see page 17). Follow these steps: 1. Go to SNMP Collector Probe > Profiles > profile name and click on the device name. 2. Choose Default in the Monitoring Configuration field. 3. Click Save at the top of the screen. When the new configuration is loaded, a Success dialog appears. 4. Click OK. The tree is updated with the new configuration. 5. Expand the node for the device you applied the default configuration to. You now see the Thresholds node listed under each component. If you wish, you can override the default alarm thresholds for each component; see Thresholds Node (see page 32). More information: Customize Monitoring (see page 17) Advanced Configuration This section describes advanced configuration tasks for the SNMP data monitoring probe. 16 Configuration Guide for SNMP data monitoring

17 Advanced Configuration Customize Monitoring After running discovery, you are ready to configure monitoring. Monitoring is applied to a device by applying a monitoring configuration. For Snap users, the Default configuration is automatically applied to your SNMP devices and the appropriate data is collected from each device. For Admin Console users, you must apply a monitoring configuration to your devices. To apply a monitoring configuration, click the name of a device in the tree and select a configuration in the Monitoring Configuration field. All users (Snap and Admin Console) may want to refine monitoring so that different devices or components have different thresholds. The following table describes the ways you can customize monitoring by the SNMP data monitoring probe. Use Case Action More Information You always want default thresholds that are different than the preconfigured defaults. These custom thresholds are applied to all devices that have the default configuration applied to them. Modify the thresholds in the default configuration. <Rule Name> Node (see page 28) You want to tailor the default thresholds for specific components of a device. For example, you have a device with ethernet, vlan, gigabit, fiber channel, and control plane interfaces, and you want different thresholds for each type of interface. Or, perhaps you want different thresholds for devices in your testing environment and your production environment. Add rules to the monitoring configuration that is applied to the device. (This could be the default configuration or a monitoring configuration you created and applied to the device.) Define a Monitoring Rule (see page 19) You want custom thresholds to apply to some, but not all, devices. These thresholds are not part of the default configuration. Create a new monitoring configuration. Create a Monitoring Configuration (see page 18) Chapter 2: Configure the snmpcollector Probe 17

18 Advanced Configuration Use Case Action More Information You want to apply custom thresholds to a specific device. These thresholds will override thresholds in the monitoring configuration applied to the device. Create a custom monitor. Custom Monitors (see page 24) More information: Apply Monitoring (see page 16) Create a Monitoring Configuration If the thresholds in the default configuration do not meet your needs, you can create a monitoring configuration with different thresholds. First create a new monitoring configuration, then modify it to set the thresholds. Important! It is strongly recommended that you create a new monitoring configuration instead of modifying a monitoring configuration that is applied to devices. If you modify a monitoring configuration that is already applied to devices, the changes are immediately applied to all monitored devices. Follow these steps: 1. Select Monitoring Configurations > > Create New Monitoring Configuration. 2. Enter the name for the configuration and click Submit. The configuration is empty. You must modify the configuration. 3. Select new configuration name > > Modify Configuration. 4. In the Available column, click the metric families you want to collect data for. 5. Click Submit. 6. Click Reload to reload the SNMP data monitoring probe configuration. 7. Select new configuration name > metric family > Default Rule. The metrics and default thresholds for the component are displayed in the right pane. 8. In the table, select a metric. The threshold information appears below the table. 18 Configuration Guide for SNMP data monitoring

19 Advanced Configuration 9. Update the threshold information as needed, then click Save. Note: To return to the default thresholds for a metric, click Actions > Reset Thresholds to Defaults. More information: Monitoring Configurations Node (see page 25) <Configuration Name> Node (see page 27) Define a Monitoring Rule You can add rules to a monitoring configuration (either the default configuration or a monitoring configuration you created). Use the default rule to apply to most devices, and use rules for certain devices or components that you want to set different thresholds for. Rules are applied in priority order. If no other rule applies to a device, the default rule is used. Follow these steps: 1. Go to SNMP Collector Probe > Monitoring Configurations > configuration name and click on a metric family name (such as CPU, Fan, Interface, and so on). Rules for the configuration are displayed in the pane to the right. 2. Click New at the top of the table under Rules. 3. Enter information in the fields for the rule. For a description of each field, see <Metric Family> Node (Configurations) (see page 27). 4. Click Save. 5. Click the name of the new rule. The metrics and thresholds for the rule are displayed in the pane to the right. 6. Click the name of a QoS metric in the table. 7. Enter information in the threshold fields below the table. For a description of each field, see <Rule Name> Node (see page 28). 8. Click Save. Chapter 2: Configure the snmpcollector Probe 19

20 Advanced Configuration Turn Monitoring Off for Some Metrics or Components You can turn monitoring off for specific QoS metrics or for specific devices or components. Use Case Action More Information You want to turn off monitoring completely on multiple devices. For example, you have devices with multiple types of interfaces, and you want to turn off monitoring for fiber channel interfaces. You want to turn off monitoring for specific QoS metrics on multiple devices. For example, for the CPU metric family, you do not want to monitor the system CPU load for the last 15 minutes on certain servers. You want to turn off monitoring, for all or some QoS metrics, on a specific device component. Create a rule with conditions that identify the devices where you want to turn off monitoring (for example, fiber channel interfaces). In the rule, select Disable All Metrics from the Actions menu. Create a rule with conditions that identify the servers. In the rule, disable the SysCPULoadLast15Minutes metric. Turn monitoring off at the device component level. Turn Monitoring Off Using a Rule (see page 21) Turn Monitoring Off Using a Rule (see page 21) Turn Monitoring Off at the Component Level (see page 22) 20 Configuration Guide for SNMP data monitoring

21 Advanced Configuration Turn Monitoring Off Using a Rule You can create a rule to turn off monitoring for certain QoS metrics or device components. Note: Settings in rules are overridden by settings at the component level. For example, if you disable monitoring in a rule but enable it at the component level, the compoment is monitored. Follow these steps: 1. Go to SNMP Collector Probe > Monitoring Configurations > configuration name and click on a metric family name (such as CPU, Fan, Interface, and so on). Rules for the configuration are displayed in the pane to the right. 2. Click New at the top of the table under Rules. 3. Enter information in the Rule Name and Rule Priority fields. For a description of these fields, see <Metric Family> Node (Configurations) (see page 27). 4. Enter conditions that identify the devices or components you want to apply the rule to. 5. Click Save. 6. Click the name of the new rule in the tree. The metrics and thresholds for the rule are displayed in the pane to the right. 7. Do one of the following: To turn monitoring off for a QoS metric, click the name the metric in the table, then uncheck the Enabled box. To turn off all monitoring for the component, choose Disable All Metrics from the Actions menu. 8. Click Save. Chapter 2: Configure the snmpcollector Probe 21

22 Advanced Configuration Turn Monitoring Off at the Component Level You can turn off monitoring for some or all QoS metrics at the component level. Note: Settings defined here override settings in any rules applied to the component. For example, if you disable monitoring in a rule but enable it at the component level, the compoment is monitored. Follow these steps: 1. Go to SNMP Collector Probe > Profiles > profile name > device name > metric family name > component name > Thresholds. Information about metrics and thresholds for the component are displayed in the pane to the right. 2. Do one of the following: To turn monitoring off for a QoS metric, click the name the metric in the table, then uncheck the Enabled box. To turn off all monitoring for the component, choose Disable All Metrics from the Actions menu. 3. Click Save. 22 Configuration Guide for SNMP data monitoring

23 Chapter 3: Probe GUI Reference This section describes the fields and features of the SNMP data monitoring probe. This section contains the following topics: SNMP Collector Probe Node (see page 23) Custom Monitors Node (see page 24) Metric Families Node (see page 25) Monitoring Configurations Node (see page 25) Profiles Node (see page 29) SNMP Collector Probe Node Navigation: SNMP Collector Probe Set or modify the following values based on your requirements: SNMP Collector Probe > Probe Configuration Fields to know: Log Level: Select the amount of log information you would like to collect for this probe. Default: 3 (Recommended) Address of discovery_server Probe: Enter the path to the discovery_server probe within this domain. Important! This is the complete path to the discovery_server probe on your primary hub, in the pattern of /<domain>/<hub>/<robot>/discovery_server. Hours Between Rediscovery: Enter the number of hours between component discovery updates. Note: To turn off automatic discovery set this value to 0. Number of Discovery Threads: Enter the number of discovery threads to display in the Discovery Status field. Important! Changing this value requires a probe restart. SNMP Collector Probe > Probe Information This section displays read-only information about the SNMP data monitoring probe. Chapter 3: Probe GUI Reference 23

24 Custom Monitors Node Custom Monitors Node Navigation: SNMP Collector Probe > Custom Monitors Custom Monitors allow you to define monitors for specific SNMP object IDs (OIDs) directly. For Custom Monitors, SNMP data monitoring probe supports rate calculations on SNMP counters. The full OID must be specified for each Custom Monitor. Custom Monitors are applied directly to a device. They cannot be applied as part of a monitoring configuration. Use a monitoring configuration to apply to monitoring to most devices, and use a Custom Monitor when you want a different monitor for a specific device. Custom Monitors override monitoring configurations applied to the device. Custom Monitors > > Create New Monitor Select this option to create a new monitor. Fields to know: Monitor Name: Enter a name for the monitor. OID: Enter the OID for the specific SNMP object you want to monitor. Units: Enter the type of units for the SNMP object. Use Delta Values: Select to use the delta values for the monitor. This allows you to monitor SNMP counters. This value is the difference between the current and previous values of the OID. Rearm Count: Select the rearm count value. This value determines how many successive samples must not violate the threshold values before an alarm is cleared. Condition: Select the appropriate condition. Warning, Minor, Major and Critical Threshold: Select the appropriate threshold value for each. Message: Enter the message to send when a threshold is reached. Clear Message: Enter the message to send when the alarm is cleared. Generic Clear Message: Enter the message to send when an alarm is cleared. This message is used when a clear message has not been defined. 24 Configuration Guide for SNMP data monitoring

25 Metric Families Node Metric Families Node Navigation: SNMP Collector Probe > Metric Families A metric family defines the set of values to collect and report on for a given technology. A router metric family, for example, specifies the values (or metrics) collected to monitor the performance of a router. These values are normalized so that reporting is uniform regardless of the data source. When you create or modify a monitoring configuration, you choose one or more metric families to apply to the configuration. Click the node of a metric family to view read-only data about the metrics collected for that metric family. Monitoring Configurations Node Navigation: SNMP Collector Probe > Monitoring Configurations A monitoring configuration is applied to a device to enable monitoring of the device. The configuration defines the metrics to be collected for a device and the thresholds applied to the metrics. A monitoring configuration contains: A set of metric families Thresholds for each of the metrics Support for four levels of thresholds (warning, minor, major, and critical) Alarm messages for each level of threshold violation The SNMP data monitoring probe comes with two monitoring configurations, the Default and the All Metrics Configuration. The Default configuration enables a basic set of metrics to monitor interfaces, CPU utilization, power supply, fan, physical memory, voltage, and temperature. This is the configuration that is automatically applied when you activate SNMP data monitoring in Snap. To view the metrics enabled in the Default configuration, go to snmpcollector > Monitoring Configurations > Default Configuration > metric family name > Default Rule and view the Enabled column in the table. The All Metrics Configuration enables all metrics in all metric families. You can also create your own monitoring configurations. Chapter 3: Probe GUI Reference 25

26 Monitoring Configurations Node Important! It is strongly recommended that you create a new monitoring configuration instead of modifying a monitoring configuration that is applied to devices. If you modify a monitoring configuration that is already applied to devices, the changes are immediately applied to all monitored devices. A monitoring configuration can be applied to multiple devices. A monitoring configuration cannot be used to apply a Custom Monitor to a device or set of devices. A Custom Monitor must be applied directly to a device. Monitoring Configurations > > Create New Monitoring Configuration Select this option to create a new monitoring configuration. You will be prompted to reload after creating a new configuration. These procedures only create the monitoring configuration. You must select a metric family to apply to this configuration by modifying the configuration. See Create a Monitoring Configuration (see page 18). Monitoring Configurations > configuration name > > Modify Configuration The Metric Family Selection dialog box appears. Click the name of a metric family in the Available list to add the metric family to the configuration. Monitoring Configurations > configuration name > Select this option to delete the configuration. > Delete Configuration More information: Create a Monitoring Configuration (see page 18) 26 Configuration Guide for SNMP data monitoring

27 Monitoring Configurations Node <Configuration Name> Node Navigation: SNMP Collector Probe > Monitoring Configurations > configuration name The configuration name node allows you to delete or modify configurations. Set or modify the following values based on your requirements: configuration name > > Delete Configuration Select this option to delete the configuration. Note: This option is not available for the default configuration. You cannot delete the default configuration. configuration name > > Modify Configuration Select this option to modify the configuration. Click a metric family name to move it between the Available and Selected lists. Metric families in the Selected list are included in the monitoring configuration. More information: Create a Monitoring Configuration (see page 18) <Metric Family> Node (Configurations) Navigation: SNMP Collector Probe > Monitoring Configurations > configuration name > metric family The metric family node lists the rules available for the component. Rules identify a device or group of devices and contain thresholds that are applied to those devices. At the metric family node you can modify the default rule for a component type, create a new rule, or delete a rule. To set the thresholds for the rule, click the rule name node. Note: You can modify but not delete the default rule for a metric family. If none of the other rules apply to a device, the default rule is used. Chapter 3: Probe GUI Reference 27

28 Monitoring Configurations Node Set or modify the following values based on your requirements: metric family > Rules Fields to know: Rule Name: Enter a name for the rule. Rule Priority: Set a priority for the rule. If multiple rules are applied to a device the rule with the first priority is used. For example, a rule with priority 1 is applied before a rule with priority 2. You can enter a priority from 1 to 99. The default rule is always the last priority, 100. This way the default rule is applied to any devices not covered by other rules. Important! Do not assign the same priority to more than one rule. If you do so, the existing rule with that priority is overwritten (deleted). Condition 1 through 4: Conditions identify the devices that the rule will be applied to. Choose the criterion to use to identify the devices (such as Device IP Address or Component Type), then fill out the appropriate fields. You can set up to four conditions. <Rule Name> Node Navigation: SNMP Collector Probe > Monitoring Configurations > configuration name > metric family > rule name The rule name node allows you to set thresholds for the rule. This can be the default rule or a rule you created. Click the name of a QoS metric to view or modify its threshold settings in the fields below the table. Set or modify the following values based on your requirements: rule name > Polled Metrics Fields to know: Metric Name: Click the name of a QoS metric in the table to display the information for the metric here. Enabled: When checked, enables monitoring for the selected metric. This setting can be overridden at the component level. See Thresholds Node (see page 32). Units: Unit for the QoS metric measurement. Rearm Count: Number of successive samples that must not violate the threshold values before an alarm is cleared. Condition: Select the appropriate condition. 28 Configuration Guide for SNMP data monitoring

29 Profiles Node Warning, Minor, Major and Critical Threshold: Select the appropriate threshold value for each. Message: Enter the message to send when a threshold is reached. Clear Message: Enter the message to send when the alarm is cleared. Generic Clear Message: Enter the message to send when an alarm is cleared. This message is used when a clear message has not been defined. rule name > Actions menu Note: Save any changes (such as changes to threshold values) before executing an option on the Actions menu. Unsaved changes will be lost. Disable All Metrics: Disables monitoring for all metrics in the rule. Enable All Metrics: Enables monitoring for all metrics in the rule. Reset Thresholds to Defaults: Resets thresholds to the default values, including whether monitoring for the component is Enabled. Profiles Node Navigation: SNMP Collector Probe > Profiles Profiles > > Create New Profile You can manually add a device profile. You may want to do this if you want to quickly add a specific device without running discovery for all devices. Fields to know: Hostname or IP Address: Host name or IP address of the device you want to create a profile for Description: Text description of the profile SNMP Credentials: For v1 or v2c enter the community string to access the device. For v3, also enter information for these fields: Username: User name to use to access the device Type: SNMP v3 security level. Depending on what level of security is selected, other security fields are enabled or disabled. NoAuthNoPriv: messages sent unauthenticated and unencrypted AuthNoPriv:messages sent authenticated but unencrypted AuthPriv:messages sent authenticated and encrypted Auth Protocol: Method of encryption. Choose either MD5 or SHA. Chapter 3: Probe GUI Reference 29

30 Profiles Node authenticationkey: The user password for authentication privacyprotocol: SNMP v3 privacy (encryption) protocol to use. Must be DES. privatekey: SNMP v3 privacy password. Must be at least eight characters. Do not confuse with the user password (authentication key). Profiles > > Query Discovery Server Discovers SNMP devices in your environment. When device discovery is completed, a Success dialog is displayed. Click Reload to refresh your screen. The tree displays a profile for each device. Once the device is discovered, discovery of the subcomponents of the device is run. The profile icon indicates the status of subcomponent discovery: OK. Discovery of subcomponents is completed. Pending. Discovery of subcomponents is in progress. Unknown. Failed. Discovery of subcomponents failed. <Profile Name> Node This section describes how to manage your SNMP device configuration. You can delete a device profile, rediscover subcomponents, modify custom monitors, and validate the credentials for each device. Navigation: SNMP Collector Probe > Profiles > profile name profile name > > Delete Profile Select this option to delete the profile. profile name > > Force Component Rediscovery Select this option to rediscover the subcomponents for the selected device. A Scheduled dialog appears indicating the discovery job has been scheduled. Click Close to return to the probe configuration. profile name > > Modify Custom Monitors Select this option to apply or deactivate custom monitors for this device. Click a montior name to move it to the Available or Selected list. Monitors in the Selected list are active for this device. See Custom Monitors (see page 24) for information on creating custom monitors. profile name > > Validate Credentials Select this option to validate your SNMP credentials for this device. 30 Configuration Guide for SNMP data monitoring

31 Profiles Node <Device Name> Node Navigation: SNMP Collector Probe > Profiles > profile name > device name Set or modify the following values based on your requirements: device name > Device Configuration Fields to know: IP Address: IP Address of device. Monitoring Configuration: Monitoring configuration to apply to the device. The SNMP data monitoring probe comes with two monitoring configurations, the Default and the All Metrics Configuration. The Default configuration enables a basic set of metrics to monitor interfaces, CPU utilization, power supply, fan, physical memory, voltage, and temperature. This is the configuration that is automatically applied when you activate SNMP data monitoring in Snap. To view the metrics enabled in the Default configuration, go to snmpcollector > Monitoring Configurations > Default Configuration > metric family name > Default Rule and view the Enabled column in the table. The All Metrics Configuration enables all metrics in all metric families. You can also create custom monitoring configurations. See Create a Monitoring Configuration (see page 18). Component Discovery: Status of discovery of components of the device. Custom Monitors: User defined monitors applied to the device. device name > metric family A table displays read-only information for the metric families applied to the device. <Metric Family> Node (Profiles) Navigation: SNMP Collector Probe > Profiles > profile name > device name > metric family Click to view read-only information about the metrics in the metric family. <Component Name> Nodes Navigation: SNMP Collector Probe > Profiles > profile name > device name > metric family > component name An organizational node in the tree. This node contains the thresholds for the device component. Chapter 3: Probe GUI Reference 31

32 Profiles Node Thresholds Node Navigation: SNMP Collector Probe > Profiles > profile name > device name > metric family > component name > Thresholds Under the Thresholds node you can view information and change thresholds for each device component. Click a Thresholds node to see a table with information about QoS metrics and thresholds. Note: Threshold settings defined here, at the component level, override threshold settings in rules applied to the component. For example, you may have a rule for the Interface metric family where monitoring for all metrics is Enabled. If you disable monitoring (choose Disable All Metrics from the Actions menu) for a specific interface, the interface is not monitored despite the settings in the rule. Thresholds > Polled Metrics You can change threshold settings in the fields below the table. Click New to add a metric to the table, and enter information for the metric in the fields below the table. Fields to know: Metric Name: Click the name of a QoS metric in the table to display the information for the metric here. Enabled: When checked, enables monitoring for the selected metric. This setting overrides the Enabled setting in any rules applied to the component. Units: Unit for the QoS metric measurement. Rearm Count: Number of successive samples that must not violate the threshold values before an alarm is cleared. Condition: Select the appropriate condition. Warning, Minor, Major and Critical Threshold: Select the appropriate threshold value for each. 32 Configuration Guide for SNMP data monitoring

33 Profiles Node Message: Enter the message to send when a threshold is reached. Clear Message: Enter the message to send when the alarm is cleared. Generic Clear Message: Enter the message to send when an alarm is cleared. This message is used when a clear message has not been defined, and is also sent when the probe restarts. Thresholds > Actions menu Note: Save any changes (such as changes to threshold values) before executing an option on the Actions menu. Unsaved changes will be lost. Disable All Metrics: Disables monitoring for all metrics for the component. Enable All Metrics: Enables monitoring for all metrics for the component. Reset Thresholds to Defaults: Resets thresholds to the default values, including whether monitoring for the component is Enabled. You may want to use this feature, for example, if you create or modify a rule and you want the settings in the rule to apply to all components (and not be overridden by settings defined at the component level). If all thresholds are set to default values, the settings in the rule are applied to the component. Chapter 3: Probe GUI Reference 33

34

35 Chapter 4: QoS Metrics The snmpcollector probe ships with the following metric families available: CPU Fan Interface Physical Memory Power Supply Temperature Voltage Within each, certain metrics are enabled and certain QoS threshold values set in the Default Configuration folder. The default threshold values provide an idea of the type of values to be entered in the fields. These default values are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section lists all QoS metrics, showing which are enabled, and provides the default QoS thresholds. CPU Normalized Name cpuidleutilization Enabled by Default Unit Rearm Count Condition Warning Minor Major Critical cpusystemutilization percent 2 Increasing cpuuserutilization percent 2 Increasing cpuwaitutilization CurrentCPSession CurrentFlowSession MemoryUtilization percent 2 Increasing PctCPUSpentRunning IOProc PctCPUSpentRunning IRQProc PctCPUUtilizationper Process percent 2 Increasing percent 2 Increasing Chapter 4: QoS Metrics 35

36 Profiles Node Normalized Name Enabled by Default Unit Rearm Count Condition Warning Minor Major Critical Reachability percent 2 Decreasing 95 SnmpService ResponseTime SysCPULoad Last15Minutes SysCPULoadLast5Minutes SysCPULoadLastMinute TtlMemoryConsumedby MemoryCacheonCPU TtlMemoryConsumedCPU TtlMemoryDedicatedCPU TtlNumProcessesCPU percent 2 Increasing Utilization TRUE percent 2 Increasing Fan Normalized Name Enabled by Default Unit Rearm Count FanSpeed Units Increasing PctTimeInBadState TRUE Percent Increasing PctTimeInGoodState Percent Increasing Condition Warning Minor Major Critical Reachability percent 2 Decreasing 95 SnmpService ResponseTime percent 2 Increasing TimeInBadState Seconds Increasing TimeInGoodState Seconds Increasing Interface Normalized Name Bits Enabled by Default Unit BitsIn TRUE Bits Rearm Count Condition Warning Minor Major Critical 36 Configuration Guide for SNMP data monitoring

37 Profiles Node Normalized Name Enabled by Default Unit BitsOut TRUE Bits Bytes BytesIn BytesOut Discards DiscardsIn DiscardsOut Errors ErrorsIn ErrorsOut Frames FramesIn FrameSize FrameSizeIn FrameSizeOut FramesOut Nonunicast NonunicastIn NonunicastOut Rearm Count Condition Warning Minor Major Critical PctDiscards percent 2 Increasing PctDiscardsIn TRUE percent 2 Increasing PctDiscardsOut TRUE percent 2 Increasing PctErrors percent 2 Increasing PctErrorsIn TRUE percent 2 Increasing PctErrorsOut TRUE percent 2 Increasing QueueDropsIn QueueDropsOut Reachability percent 2 Decreasing 95 SnmpService ResponseTime percent 2 Increasing Chapter 4: QoS Metrics 37

38 Profiles Node Normalized Name SpeedIn SpeedOut Unicast UnicastIn UnicastOut Enabled by Default Unit Rearm Count Condition Warning Minor Major Critical Utilization percent 2 Increasing UtilizationIn TRUE percent 2 Increasing UtilizationOut TRUE percent 2 Increasing Physical Memory Normalized Name Free Enabled by Default Unit Rearm Count Condition Warning Minor Major Critical Reachability percent 2 Decreasing 95 SnmpService ResponseTime Total Used percent 2 Increasing Utilization TRUE percent 2 Increasing Power Supply Normalized Name Enabled by Default Unit Rearm Count Condition Warning Minor Major Critical TimeInBadState TRUE percent 2 Increasing 1 TimeInGoodState PctTimeInGood State Reachability percent 2 Decreasing 95 SnmpService ResponseTime percent 2 Increasing Configuration Guide for SNMP data monitoring