Nimsoft Monitor. cisco_monitor Guide. v3.3 series

Transcription

1 Nimsoft Monitor cisco_monitor Guide v3.3 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 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation Send comments or questions about CA Technologies Nimsoft product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4

5 Contents Chapter 1: cisco_monitor cisco_monitor Overview... 7 Chapter 2: cisco_monitor Probe Deployment 9 Supported Platforms... 9 System Requirements... 9 Software Requirements... 9 Monitoring System Requirements Probe Deployment Information Chapter 3: cisco_monitor Configuration 11 Probe Defaults Probe Configuration Interface Installation Probe GUI The Left Pane The Right Pane The Tool Buttons Probe Configuration Set the General Properties Configure Agent Group Configure Agent Profiles Configure the Variable Properties Set Default Variable Parameters Bulk Configuration Get Oid Values Monitor a Variable Ping Sweep Chapter 4: QoS Threshold Metrics 37 cisco_monitor Metrics cisco_monitor Alert Metrics Default Settings Contents 5

6

7 Chapter 1: cisco_monitor 3.3 This description applies to cisco_monitor probe version 3.3. This section contains the following topics: cisco_monitor Overview (see page 7) Documentation Changes (see page 8) cisco_monitor Overview Monitor Cisco hardware. The Nimsoft Monitor Cisco probe performs SNMP GET queries to selected Cisco SNMP devices transforming the query result into alarms and/or quality of service (QoS) messages for SLA purposes. You may configure the profile to your requirements in order to integrate the device seamlessly into the Nimsoft Monitor solution. The Cisco Monitor probe includes a user interface for probe configuration. The probe supports SNMPv1, SNMPv2c and SNMPv3. The probe includes a set of predefined SNMP OID variables available on most Cisco devices, such as CPU and memory usage, state of temperatures, fans, power supply and voltages. Chapter 1: cisco_monitor 3.3 7

8 cisco_monitor Overview Documentation Changes This table describes the version history for this document. Version Date What's New? 3.3 October 2013 Added the SNMP V3 Support topic. 3.3 April 2013 Added a new field - Items in sample array in the General tab of the Setup dialog. Profile is not created, by drag-and-drop from ping sweep, if it is already exist in a group. Added a field - Calculate average based on samples on the Variable Properties dialog. Added a column - Average Value on the tabular representation of the Agent variables. Added Probe Defaults for cisco_monitor. 3.2 March 2012 Added information for authorization password and privacy phrase for SNMPv3 devices. Reorganized information for the Ping Sweep functionality. 3.1 December 2011 Implemented IPv6 Compatibility; SNMP query related bugs fixed; and updated libraries. 3.0 March 2011 Added support for high and low threshold alarms in checkpoints; added toolbar button to retrieve current values; and added new templates. Related Documentation Documentation for other versions of the cisco_monitor probe The Release Notes for the cisco_monitor probe Monitor Metrics Reference Information for CA Nimsoft Probes ( 8 cisco_monitor Guide

9 Chapter 2: cisco_monitor Probe Deployment This section contains the prerequisites, system requirements and deployment information for the cisco_monitor probe. This section contains the following topics: Supported Platforms (see page 9) System Requirements (see page 9) Software Requirements (see page 9) Monitoring System Requirements (see page 10) Probe Deployment Information (see page 10) Supported Platforms The cisco_monitor probe supports the same set of operating systems and databases as supported by the Nimsoft Server solution. 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 cisco_monitor probe. System Requirements The cisco_monitor probe should be installed on systems with the following minimum resources: Memory: 2-4GB of RAM. Probe's OOB configuration requires 256MB of RAM CPU: 3GHz dual-core processor, 32-bit or 64-bit Software Requirements The cisco_monitor probe requires the following software environment: Nimsoft Monitor Server or later Nimsoft Robot 5.23 or later Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and above) Chapter 2: cisco_monitor Probe Deployment 9

10 Monitoring System Requirements Note: For SOC functionality, NM Server 5.6 or later and UMP or later is required. Monitoring System Requirements The cisco_monitor probe monitors selected Cisco SNMP hardware devices through SNMP GET queries. The query results are then transformed to QoS messages and alarms. Probe Deployment Information There are three ways to distribute archive packages. You can distribute the package within the web-based Admin Console (for supported probes), from within Infrastructure Manager, or use the standalone Nimsoft Distribution application.see Probe Deployment for more information on deploying probes. 10 cisco_monitor Guide

11 Chapter 3: cisco_monitor Configuration This section describes the configuration concepts and procedures for setting up the cisco_monitor probe. This probe is configured to monitor environment variables for Cisco devices. This section contains the following topics: Probe Defaults (see page 11) Probe Configuration Interface Installation (see page 11) Probe GUI (see page 12) Probe Configuration (see page 16) Probe Defaults You can use the sample configuration file to configure a probe with default monitoring values. Follow these steps: 1. Navigate to the Program Files\Nimsoft\Probes\Network\<probe name> folder. 2. Rename the <probe name>.cfg file to <probe name>_bkp.cfg to take the backup of the existing configuration file. 3. Rename the sample_<probe name>.cfg file in this folder to <probe name>.cfg. 4. Run/restart the probe in Infrastructure Manager to initialize the configuration. You can now use the newly added default monitoring values (templates) from the left pane. Probe Configuration Interface Installation The probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot. Chapter 3: cisco_monitor Configuration 11

12 Probe GUI Probe GUI You can double-click the cisco_monitor probe in Infrastructure Manager to open the configuration GUI. You can configure the probe to map your Cisco devices and define variable settings for monitoring the performance of the device. The configuration GUI is divided in the following sections: Left pane (see page 13) Right pane (see page 14) Tool buttons (see page 15) Note: The term Host and Agent are also used to represent a Cisco device throughout this document. 12 cisco_monitor Guide

13 Probe GUI The Left Pane The left pane is used to create monitoring groups and add agents for monitoring. The list of groups and agents is displayed in the left-pane. Select an agent and view all variables that are listed in the right pane. You can right-click in the pane to open a pop-up menu with the following options: New Agent Opens the profile dialog for connecting with a new agent. New Group Edit Delete Adds a group to the probe. Opens the profile dialog for the selected agent, enabling you to modify the properties. This option is available only when an agent is selected. Lets you delete the selected group or agent. However, you are not allowed to delete the Default Group, but this group disappears on removing all agents from it. Deleting a group also delete the agents of the group. You are asked to confirm that you really want to delete the group with its agent definitions. Rename Ping Lets you rename the selected group or agent. Available only when an agent is selected. Pings the selected agent. If the agent responds, you are notified with the ping round-trip time. Chapter 3: cisco_monitor Configuration 13

14 Probe GUI Information Available only when an agent is selected. Opens a dialog containing system and configuration information for the selected agent. Note: You can drag and drop agents to move them between groups. Initially the probe comes with a Default Group. You are not allowed to delete this group, but if you delete all agents in the group, the group will disappear the next time you open the cisco_monitor GUI. Note that an agent that is unavailable will be assigned a symbol as shown on the figure below: The Right Pane The right-pane is a multifunctional pand displays the following: Agents when a group is selected in the left-pane. SNMP Variables when an agent is selected in the left-pane. You select the variables that you want to include by selecting the check box in front of the variable name. This will enable the probe to send alarm and QoS messages for the selected variable. The icons in front of the variable names have the following meaning: Green means OK. 14 cisco_monitor Guide

15 Probe GUI Black means the Enable Monitoring option and the QoS option is turned off in the properties dialog for the variable. Other colors indicate the severity level selected (in the properties dialog for the variable) when the current value breaches the alarm threshold. Indicates that this value cannot be measured on the monitored device. Indicates that the Enable Monitoring option is turned off, but the QoS option is selected in the properties dialog for the variable. Right-clicking in the pane gives you the following possibilities: When agents are listed: Same options as when right-clicking in the left window pane (see page 13). When variables are listed: Edit Opens the properties dialog for the selected variable, enabling you to modify the properties. Delete Deletes the selected variable. Refresh Refreshes the list to ensure that the most recent values are displayed. Monitor Opens the monitor window and starts monitoring the selected SNMP variable, where you can watch the graphs being filled. The Tool Buttons The configuration tool also contains a row of tool buttons: Chapter 3: cisco_monitor Configuration 15

16 The General Setup button The New Group Folder button The Add new Agent button The Set default variable properties button The Bulk Configuration button The Ping Sweep button The Get OID Values button Probe Configuration This section contains the specific configuration for the probe. Set the General Properties The General Tab This functionality is used to set the general properties for the probe. When clicked, the Setup dialog is displayed which contains two tabs - General and Advanced. The fields in the above dialog are explained below: 16 cisco_monitor Guide

17 Encrypt community string Encrypts the passwords, in the probe configuration file, specified for the different agent profiles. Items in sample array Indicates the default amount of samples stored in memory for each interface. This value can be overridden for each interface. SNMP request timeout Specifies the timeout value for the SNMP requests. Use the default value or select another value (in seconds) from the drop-down list. This value will be used for profiles that have not their own timeout defined. Default alarm message string Defines the default alarm message issued when alarm situations occur. Log-level Sets the level of details written to the log file. Log as little as possible during normal operation to minimize disk consumption and increase the amount of detail when debugging. The Advanced Tab This tab is used to add connection information, which will be used in the Ping Sweep feature for connecting to the device. Chapter 3: cisco_monitor Configuration 17

18 You can: Add Connection Information Delete Connection Information Follow these steps to add connection information: 1. Click the + button (Add) in the Setup dialog. The Add connection information dialog displays. The fields in the above dialog are explained below: Name Alphanumeric name for the configuration. SNMP Version Select the appropriate SNMP version for the configuration. Authentication Port Authentication for the configuration (valid only in case of SNMPv3). SNMP port number. Community/password Represents community, if SNMP version is selected as SNMPv1 or SNMPv2. Represents password, if SNMP version is selected as SNMPv3. Note: Password string must be at least 8 characters long. Username Security Specify the username that needs to be used (valid only in case of SNMPv3. Security descriptor to be used (valid only in case of SNMPv3). 18 cisco_monitor Guide

19 Privacy Protocol Privacy protocol to be used (valid only in case of SNMPv3). Privacy Passphrase Privacy Passphrase to be used (valid only in case of SNMPv3). Note: Privacy Passphrase must be at least 8 characters long. 2. Click OK. The connection information is now added. Follow these steps to delete connection information: 1. Select the item that you want to delete. 2. Click the Delete (X) button. The selected item gets deleted. Configure Agent Group If you want to create an agent group for the agents, you can do so by: Right-clicking in the left pane and selecting the New Group option, or Clicking the Create a New Agent Group button in the tool bar. The group will appear as a new node in the left pane, and will by default be named as New Group. Right-click the group and select the Rename option to give it a name of your own choice. Chapter 3: cisco_monitor Configuration 19

20 Configure Agent Profiles Click Create a New Agent Profile button on the tool bar to open the Profile dialog box. The fields in the above dialog are explained below: Agent hostname or IP address The name or IP address of the device. Active If checked, activate the profile to monitor the selected SNMP Agent. Check interval Indicates the time interval between each time the SNMP Agent is checked. Severity Indicates the severity for messages if the agent does not respond. Group Indicates the agent group to which the agent is to be placed. 20 cisco_monitor Guide

21 SNMP Settings QoS SNMP Version Select the appropriate SNMP version for the configuration. Authentication Port Timeout Retries Select the authentication for the configuration. (Valid only in case of SNMPv3). Specify the port to be used by the SNMP device. Default port is 161. Select the timeout value in seconds before a new SNMP GET request is sent to the SNMP agent. Default value is 1 second. Select the number of attempts to be done before giving up and reporting it as a failure. An alarm is issued. Default is 5 retries. Community/password Represents community, if SNMP version is selected as SNMPv1 or SNMPv2. Represents password, if SNMP version is selected as SNMPv3. Note: Password string must be at least 8 characters long. Username Specify the username that needs to be used. (Valid only in case of SNMPv3). Show password When checked, the entry in the Community/password field is shown as plain text. Security Security descriptor to be used (valid only in case of SNMPv3). Priv. Protocol Privacy protocol to be used (valid only in case of SNMPv3). Priv. Passphrase Privacy passphrase to be used (valid only in case of SNMPv3). QoS identification method Enables you to define a QoS target. Chapter 3: cisco_monitor Configuration 21

22 SNMP V3 Support The cisco_monitor probe is enabled to monitor hosts/agents based on the SNMP V3 protocol. Few guidelines that must be adhered to when monitoring the SNMP V3 hosts are given as follows: If the same probe instance is monitoring multiple SNMP V3 hosts/agent, the user must ensure that the EngineID of all the hosts/agents is unique. The absence of unique EngineID causes sporadic connection timeouts and failure alarms. The probe does not support creating multiple monitoring profiles for one V3 host/agent. Adding such duplicate profiles is disabled in the probe GUI at most of the places, except the Bulk Configure screen. Do not use the Raw Configure option or add directly in the configuration file for creating multiple profiles for the same V3 host/agent. Doing so, causes the probe for producing some unpredictable results. Configure the Variable Properties Double-clicking one of the variables (or right-clicking the variable and selecting Edit) opens the variable properties dialog. 22 cisco_monitor Guide

23 Now you can set the alarm and QoS definitions for the variable. The fields in the above dialog are explained below: Name Indicates the name of the variable. Object Identifier (OID) Indicates the variable name in the format of an Object Identifier. Description The description of the variable. Chapter 3: cisco_monitor Configuration 23

24 Value properties Active Calculate average based on samples Enter the number of samples for which the average value is to be calculated. This value is displayed under the Average Value column against each variable. The cisco_monitor probe will send alarms on the basis of this average value. See the second snapshot in Get Oid Values (see page 31). If checked, activates the selected variable. Enable Monitoring Enables monitoring of the variable issuing alarms if the defined threshold is breached. Rule Tab Operator Select an operator when defining a threshold value for alarms to be issued. Threshold Value The alarm threshold value. An alarm will be issued if this threshold is breached. Severity Level Unit Select the severity level of the alarms issued when the specified threshold value is breached. Indicates the unit to be combined with the threshold value (for example, MB, %, etc.). Message String Specify a text string describing the alarm situation. If nothing is specified here, the default message (defined under General Properties for the probe) will be used. Clear Message String Specify a text string, overruling the default clear message text. If nothing is specified here, the default clear message (hard coded) will be used. 24 cisco_monitor Guide

25 Extend Rule Tab This tab enables you to set critical thresholds for the variable. Notes: This tab is only enabled when the Operator field in the Rule tab is NOT set to "=" (equal to operator). This tab is only available for the variables in which user needs to manually specify the threshold value in the Rule tab. For the variables ( for example, Fan State) in which user can only choose a threshold from the drop-down, the Extend Rule tab is disabled. The probe first checks if the condition in the Rule tab is satisfied. If yes, then it checks if the condition in Extend Rule tab is satisfied. If Yes, then the message string in Extend Rule tab is displayed. If No, then the message string in Rule tab will be displayed. Publish Quality of Service If checked, sends the QoS data at the specified check interval for the profile. Set Default Variable Parameters Click the Set the default variable parameters button on the tool bar to open the Default variable settings dialog. This dialog enables you to configure default values for the selected variable. Chapter 3: cisco_monitor Configuration 25

26 Follow these steps: 1. Select one of the options from the drop-down and click OK. The Default variable configuration dialog opens. The fields in the above dialog are explained below: Active If checked, activates the profile. Enable Monitoring Enables monitoring of the variable. Rule/Extended Rule Tabs These tabs are activated when the option Enable Monitoring is selected. The fields on these tabs define the alarm and QoS conditions for the variable.you have the option to use one or two levels of alarm triggering rules. You define a set of alarm triggering rules on the Rule tab and alternatively also a set of additional alarm triggering rules on the Extended Rule tab. 26 cisco_monitor Guide

27 Important! Rule has to trigger before the Extended Rule is checked. Note also that the Extended Rule tab is disabled if selecting the operator = in the Rule tab. Example: Rule: Operator =>, Value 5, Severity Major Extended Rule: Operator =>, Value 10, Severity Critical This means: If the measured value is 6, the alarm message specified on the Rule tab (severity level Major) is issued. If the measured value is 13, the alarm message specified on the Extended Rule tab (severity level Critical) is issued. Operator Select an operator when defining a threshold value for alarms to be issued. Threshold Value Specify an alarm threshold value which when breached issues an alarm. Severity level Unit Select the severity level of the alarms, issued when the specified threshold value is breached. Indicates the unit to be combined with the threshold value (for example, MB, %, etc.). Message String Specify a text string describing the alarm situation. If nothing is specified here, the default message (defined under General Properties for the probe) will be used. Clear Message String Specify a text string, overruling the default clear message text. If nothing is specified here, the default clear message (hard coded) will be used. Publish Quality of Service (QoS) If checked, sends QoS data at the specified check interval for the profile. 2. Configure the properties and click OK. The default values get configured for the variable. Note: Next time when you select this variable (the one for which you have set the default properties), the properties will be configured with default values. Chapter 3: cisco_monitor Configuration 27

28 Bulk Configuration You can use the the bulk configuration option to configure variables for more than one agents at one go. This option is useful when threshold values of a variable is same for more than one agents. Click the Bulk Configuration option on the tool bar to open the Bulk Configuration dialog box. The fields in the above dialog are explained below: Select Agents All agents The configuration parameters are distributed to your monitored agents. Only active ones The configuration parameters are distributed to all active agents. 28 cisco_monitor Guide

29 All agents matching The configuration parameters are distributed to all agents matching your input in this field (pattern matching). All agents in the group The configuration parameters are distributed to all agents in the selected group. Selected agent(s) Select Variable The configuration parameters are distributed to all agents selected in the right pane. Choose the required variable. Modify Agent Values If checked, configures the agent parameters as discussed below. Enables the Interval field and some fields in the SNMP Properties section. Interval Version Auth. Port Specify the time interval between each time the SNMP agent is checked. Default value is 5min. Specify the SNMP software version number supported by the monitored device. Select the type of authentication strategy (none, HMAC-MD5-96 or HMAC-SHA-96). Only enabled when SNMPv3 option is selected in the Version field. Timeout Retries Specify the port to be used by the SNMP device. Default value is 161. Select the timeout value in seconds before a new SNMP Get request is sent to the SNMP agent. Select the number attempts to be done before giving up and reporting it as a failure. An alarm is issued. Default is 5 retries. Community/Password Represents community, if SNMP version is selected as SNMPv1 or SNMPv2. Represents password, if SNMP version is selected as SNMPv3. Chapter 3: cisco_monitor Configuration 29

30 Username Specify a username defined on the monitored device. Show Community/Password Select this check box to show the entry in the Community/Password field as plain text. Security Define the security level for the user. Valid levels are NoAuthNoPriv, AuthNoPriv, and AuthPriv. This field is available only when the SNMP version is SNMPv3. Priv. Protocol It is the privacy protocol for the SNMP. It is not required if the security level is NoAuthNoPriv or AuthNoPriv. This field is available only when the SNMP version is SNMPv3 and Security field is selected as AuthPriv. Priv. Passphrase It is the privacy pass phrase. It is not required if the security level is NoAuthNoPriv or AuthNoPriv. It must be at least 8 characters long. This field is available only when the SNMP version is SNMPv3 and Security field is selected as AuthPriv. Modify variable values You can either choose to Use the default variable settings option or you can choose to Configure variable settings option as per the requirement. By default, the Use the default variable settings option is selected. 30 cisco_monitor Guide

31 Get Oid Values When you select a node from the tree view, the values for respective variables are not populated automatically. Chapter 3: cisco_monitor Configuration 31

32 To get the latest values, click the Get Oid Values button from the tool bar. Latest values for all the variables are populated in the Value and Average Value columns. Notes: The Average Value is calculated on the basis of the value provided in the Calculate average based on samples field in the Variable Properties (see page 22) dialog. For state variables (Fan State, Temperature State, and so on), the cisco_monitor probe will not calculate the average value. Rather, it will publish the actual values of these state variables as average values under the Average Value column. The alarms and QoS for these variables will also come on actual values only. The cisco_monitor probe sends alarms on the basis of values displayed under the Average Value column, depending on the conditions specified in the Variable Properties (see page 22) dialog (through Operator and Threshold Value fields). QoS will always come on actual value. The Misses Oids (Big Buffer Misses, Huge Buffer Misses, Large Buffer Misses, and so on) will give alarms on change in average value and QoS on change in actual value. 32 cisco_monitor Guide

33 Monitor a Variable Right-clicking a variable and selecting Monitor opens the monitor window and starts monitoring the selected SNMP variable. This allows for a continuous monitoring of specific variables, and runs independent of the probe s general QoS/alarm monitoring of an agent. Note: Clicking in the Interval field (in the lower left corner) opens a drop-down list, allowing you to select the sample interval from the list. This sample interval is for the monitor window only and has nothing to do with the sample rate defined in the agent profile. Chapter 3: cisco_monitor Configuration 33

34 Available intervals are: 1 minute 30 seconds 2 minutes 5 minutes 10 minutes 1 hour Ping Sweep The Ping Sweep option allows you to discover Cisco devices within an IP address range and verify the connection to each device. You can then monitor those devices that are found connected. Follow these steps: 1. Click the Create New Agent Profile(s) Using Ping Sweep button on the tool bar. The Ping Sweep dialog appears. 34 cisco_monitor Guide

35 2. Enter the starting IP address of an IP address range and number of hosts in the range. 3. Click Generate. The specified range appears in the table. Note: The Duplicate IP addresses are ignored. You can generate multiple ranges before starting the ping sweep. 4. Select a connection information from the Connection information drop-down list that you want to use for the router detection. 5. Click Start. In case, the Auto option is selected in the Connection information dialog then each IP address connection is checked based on the connection information of the Connection information dialog. The Red icon indicates the failure and Green icon indicates the successful connection. Further, for the device discovery, the sysname OID is checked for Cisco strings. In case the sysname does not contain Cisco string then ping sweep will not detect the Cisco device. All the detected devices are marked in green. Chapter 3: cisco_monitor Configuration 35

36 6. You may now drag one or more (multi select) of the discovered agents and drop into one of the groups in the left pane or to the root level. Note: If the Agent already exist in any Group and you drag and drop it to the same group, then the profile will not get created. Even if you drag and drop it to any other group where it does not exist, then also the profile will not get created. 36 cisco_monitor Guide

37 Chapter 4: QoS Threshold Metrics Many Nimsoft Monitor probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds. This section contains the following topics: cisco_monitor Metrics (see page 37) cisco_monitor Alert Metrics Default Settings (see page 38) cisco_monitor Metrics The following table describes the checkpoint metrics that can be configured using the cisco_monitor probe. Monitor Name Units Description QOS_CISCO_BUFFER_MISSES Misses Cisco Buffer Misses QOS_CISCO_ENVIRONMENT State Cisco Environment QOS_CPU_USAGE Percent CPU Usage QOS_MEMORY_PERC_USAGE Percent Memory Usage in percent QOS_MEMORY_USAGE Megabytes Memory Usage QOS_MEMORY_USAGE_PERC Percent Memory Usage (%) Note: The QoS Definitions and QoS for Buffer Misses are delayed, as per the Check interval, for the first time. This is because the QoS for buffer misses are calculated based on the delta value hence they do not come for the first time. Chapter 4: QoS Threshold Metrics 37

38 cisco_monitor Alert Metrics Default Settings cisco_monitor Alert Metrics Default Settings This section contains the alert metric default settings for the cisco_monitor probe. QoS Metric Error Threshold Error Severity CPU Last 5 sec 90 Minor CPU Last 1 Min 90 Minor CPU Last 5 Min 90 Minor Small Buffer Misses Minor Medium Buffer Misses Minor Big Buffer Misses Minor Large Buffer Misses Minor Very Large Buffer Misses Minor Huge Buffer Misses Minor Memory Free 1 Minor Description The overall CPU busy percentage in the last 5 second period The overall CPU busy percentage in the last 1 minute period The overall CPU busy percentage in the last 5 minute period The average number of times that the router failed to queue a packet in a small buffer (64 to 104 bytes). The average number of times that the router failed to queue a packet in a medium buffer (105 to 600 bytes). The average number of times that the router failed to queue a packet in a big buffer (601 to 1524 bytes). The average number of times that the router failed to queue a packet in a large buffer (1525 to 5024 bytes). The average number of times that the router failed to queue a packet in a very large buffer. The average number of times that the router failed to queue a packet in a huge buffer (5025 to bytes). Indicates the number of megabytes from the memory pool that are currently unused on the managed device. 38 cisco_monitor Guide

39 cisco_monitor Alert Metrics Default Settings QoS Metric Error Threshold Error Severity Memory Used 10 Minor Memory Percent Free 10 Minor Description Indicates the number of megabytes from the memory pool that are currently in use by applications on the managed device. The overall available memory percentage in the memory pool. Power Supply State 1 Minor The current power supply state Temperature State 1 Minor The current temperature state Fan State 1 Minor The current fan state. Voltage State 1 Minor The current voltage state Operational Status - Critical Resource is not responding. Chapter 4: QoS Threshold Metrics 39