Nimsoft Monitor. ntp_response Guide. v1.2 series

Transcription

1 Nimsoft Monitor ntp_response Guide v1.2 series

2 Legal Notices Copyright 2012, 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.

3 Contact Nimsoft For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads Nimsoft Support policies and guidelines Other helpful resources appropriate for your product Provide Feedback If you have comments or questions about Nimsoft product documentation, you can send a message to support@nimsoft.com.

4

5 Contents Chapter 1: ntp_response ntp_response Overview... 7 Chapter 2: ntp_response Deployment 8 System Requirements... 8 Operating System Requirements... 8 Software Requirements... 9 Monitoring System Requirements... 9 Probe Deployment Information... 9 Chapter 3: ntp_response Configuration 9 Probe Configuration Interface... 9 Probe GUI Probe Configuration Setup tab Status tab Messages tab Chapter 4: QoS Threshold Metrics 19 ntp_response Metrics Alert Metrics Default Settings Contents 5

6

7 Chapter 1: ntp_response 1.2 This description applies to ntp_response version 1.2. This section contains the following topics: ntp_response Overview (see page 7) Documentation Changes (see page 8) ntp_response Overview The ntp_response probe checks the current time from NTP (Network Time Protocol) and SNTP (Simple Network Time Protocol) servers and measures the response time of the query. The probe can also request status information from NTP servers. Alarms can be generated on response time and, in the case of NTP servers, offset and jitter (in comparison with their time reference). Alarms can also be generated on error situations. The ntp_response probe is configured by double-clicking on the line representing the probe in Infrastructure Manager. This brings up the configuration tool for the probe. Chapter 1: ntp_response 1.2 7

8 System Requirements Documentation Changes This table describes the version history for this document. Version Date What's New? 1.2 April 2012 Added support for localized alarm messages. Added fix to properly deploy the probe on 64-bit Linux machines. Related Documentation Fixed SOC issues Added an Advanced tab in the Status tab. Allow source override field added. Documentation for other versions of the ntp_response probe Getting Started with Nimsoft Probes Nimsoft Probes Reference Chapter 2: ntp_response Deployment Successful distribution of the ntp_response probe package relies on the Java package installed with the Nimsoft Management Server. System Requirements This section contains the system requirements for the ntp_response probe. Operating System Requirements The ntp_response probe runs on the following operating systems: Windows: XP, 2003, 2008 Linux: Glibc >=2.3 8 ntp_response Guide

9 Probe Deployment Information Software Requirements The ntp_response 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). Note: For SOC functionality, NM server 5.6 or later and UMP or later is required. Monitoring System Requirements The monitoring system requirement for ntp_response probe is that NTP server must be running. Probe Deployment Information There are two ways to distribute the probe archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft distribution application. Chapter 3: ntp_response Configuration This section describes the configuration concepts and procedures for setting up the ntp_response probe. The configuration user interface is based on tabs. Probe Configuration Interface The ntp_response probe configuration interface is installed when the ntp_response probe is deployed. Chapter 3: ntp_response Configuration 9

10 Probe GUI Probe GUI This section contains the basic GUI information for the ntp_response probe. The user interface for this probe contains three tabs: Setup: Use to configure general elements of the ntp_response probe. Status: Displays a list of defined profiles where each profile monitors one NTP or SNTP server. You can add, modify, or delete a profile. Messages: Displays a list of configured alarm messages. You can add a message, modify message properties, or delete a message. Probe Configuration This section contains specific configuration information for the ntp_response probe. Setup tab 10 ntp_response Guide

11 Probe Configuration The controls on the setup tab configure the general elements of the ntp_response probe: Field Log-file Log-level Description The name of the log file is usually the same as the probe name with a.log extension. If the log file name is changed, the settings of the probe should be changed accordingly in Infrastructure Manager. The log level determines the detail level of messages written to the log file. A higher log level will generate more information. On log-level 0 (which is the default) only critical errors are logged. Status tab On the status tab you will see a list of defined profiles. Each profile defines the monitoring of one NTP or SNTP server. A check box indicates if a profile is active. The following fields are shown: Field Name Host Interval System Description A user defined name of the monitoring profile. The name or ip-address of the host being monitored by this profile. The time interval in seconds between each host check. For NTP servers, this field will contain a short system description found during the last check; otherwise this field will be empty. Chapter 3: ntp_response Configuration 11

12 Probe Configuration Refid Response time alarm limit Type For NTP servers, this field will contain the reference id for the NTP server found during the last check; otherwise this field will be empty. The configured maximum response time in milliseconds allowed before an alarm is issued. If this field is empty, any response time is deemed acceptable. The type of server monitored by this profile. This can be SNTP (in which case only a simple time-fetch is done) or NTP (in which case an attempt is made to get server status information). 12 ntp_response Guide

13 Probe Configuration The status line below the profile list indicates the probe version and when it was started. The following commands are available when you right click in the profile list: Add profile Creates a new profile and presents you with the Profile properties window described below. Edit profile Edit the selected Profile. Remove profile Delete the selected Profile. You will be asked to confirm the deletion. Profile properties dialog This dialog appears when double-clicking a profile, or by right-clicking in the list and selecting Add or Edit. Chapter 3: ntp_response Configuration 13

14 Probe Configuration General parameters Name The name of the profile. Active Check this box if you want checking of the selected profile to be done. NTP Server Host is the name of the NTP host you are configuring a profile for. Type is one of NTP or SNTP. The Test button is used to check that you can reach the host you are configuring a profile for. If you use profile type NTP on a host supporting only SNTP, the check will time out. Setup On the Setup tab you define the check interval in seconds. Alarm messages On the Alarm messages tab, the situations in which an alarm message should be generated is configured. In the case of an SNTP server, only Response Time exceeds and No contact with server is available. Field Response time exceeds. Offset exceeds. Jitter exceeds. No contact with server. Server in not updated by any peer. Server is not fully initialized. Description Specify the maximum allowed response time and select a message to be sent when this time is exceeded. Specify the maximum allowed server time offset and select a message to be sent when this value is exceeded. Specify the maximum allowed server time jitter, which indicates the server s time stability, and select a message to be sent when this value is exceeded. Select a message to be sent if the probe is not able to connect to the server. Select a message to be sent if the server is not updated. Select a message to be sent if the server is not fully initialized. 14 ntp_response Guide

15 Probe Configuration Quality of Service On the Quality of Service messages tab you can select which values to generate QoS messages for. Available options are: NTP response time Server offset Server jitter In the case of an SNTP server, only the NTP time is available. Advanced Tab The Advanced tab contains the Allow Source Override field. The text specified in this field will override the Source of Alarm and QoS. If you do not enter a value in this field, the QoS source will be hostname of system where probe is deployed and alarm source will be IP address of the system where probe is deployed. You can use the following variables in this field: Variable $host Description If $host is specified in Allow Source Override field, then the $host is replaced by host of NTP server in source field of Alarms and QoS. Chapter 3: ntp_response Configuration 15

16 Probe Configuration $profile If $profile is specified in Allow Source Override field, then $profile is replaced by profile of NTP server in source field of Alarms and QoS. Note: You can also override any text in Allow Source Override field with or without variables in both QoS and alarm variables. Messages tab On the Messages tab a complete list of configured alarm messages is shown. These messages can be individually used from the configured profiles. There are 6 situations in which an alarm can be generated. For each of these, one of the messages can be the default alarm. The following fields are shown for the alarm messages: Field Name Description User defined message name. 16 ntp_response Guide

17 Probe Configuration Text Level Subsystem Default for Alarm message text. The following variables are expanded from the message text on an alarm situation: Profile The name of the profile in which the situation occurred. Host The host name being queried. Jitter The server time jitter. This indicates the time stability of the server. Jitter_limit The limit for jitter set in the profile above which an alarm should be generated. Offset The server time offset. Offset_limit The limit for offset set in the profile above which an alarm should be generated. Refid The refid of the NTP server queried. Response_time The time in milliseconds used querying the server. Response_time_limit The limit for response time set in the profile above which an alarm should be generated. The alarm level (information, warning, minor, major or critical). The subsystem used in the alarm message. Refer to the nas documentation for more information. If this field is not empty, the message is the default message for this alarm situation. The following alarm situations are defined: jitter offset response_time no_contact no_peer no_refid Chapter 3: ntp_response Configuration 17

18 Probe Configuration The following commands are available when you right-click in the message list: Add message Creates a new message and presents you with the Message properties window described below. Message properties Edit the selected Message. Remove message Delete the selected Message. You will be asked to confirm the deletion. Message properties 18 ntp_response Guide

19 Probe Configuration Name Each message must be given a unique name. This name is used to refer to the message from the profiles. Default for alarm situation The message can be made the default message for a particular alarm situation. You must leave this field empty if another message is to be the default. Text The alarm message text. Variable expansion is supported, and the following variables are available: profile mail_to used threshold diff Level The severity level assigned to any the alarm messages. Subsystem The subsystem_id of alarms generated by this watcher. A string or an id managed by the nas. 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. Chapter 4: QoS Threshold Metrics 19

20 ntp_response Metrics ntp_response Metrics The following table describes the checkpoint metrics that can be configured using the ntp_response probe. Monitor Name Units Description QOS_N TP_JITT ER NTP Server Jitter QOS_N TP_OFF SET NTP Server Offset QOS_N TP_RES PONSE _TIME NTP Respon se Time 20 ntp_response Guide

21 Alert Metrics Default Settings Alert Metrics Default Settings This section contains the default settings for alert metrics for the ntp_response probe. QoS Metric Warning Threshold Warning Severity Error Threshold Error Severity Description Jitter None None None None Jitter exceeds NoContact None None None None No contact with server NoPeer None None None None Server is not updated from any peer NoRefid None None None None Server is not fully initialized Offset None None None None Offset exceeds Response Time None None None None Response time exceeds Chapter 4: QoS Threshold Metrics 21