Nimsoft Monitor. cluster Guide. v2.6 series

Transcription

1 Nimsoft Monitor cluster Guide v2.6 series

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

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: cluster Cluster Probe installation... 9 Configuring the standard Nimsoft probes on the Cluster Nodes Cluster Probe Configuration The Cluster Properties General tab Alarm Settings tab QoS Settings tab The Node Properties General Configuration The Resource Group Properties Add new Monitoring Profiles Add new shared section Restart a Node Open the Log Viewer Configuration File versions Glossary 31 Contents 5

6

7 Chapter 1: cluster 2.6 This description applies to version 2.6x. A cluster consists of two or more nodes (computers), which allows for automatic fail-over. NOTE: The Nimsoft cluster probe supports all Microsoft Cluster configurations. A cluster contains one or more resource groups that are shared between the nodes (only one node has the control of a resource group at any given time). A resource group is a collection of shared resources, such as disk drives, IP-addresses, host names, applications, etc. Upon a failure of one of the nodes, the control of all resources is automatically transferred to the functioning node. The Nimsoft Cluster probe enables fail-over support for the standard Nimsoft probes. Probe profiles of standard Nimsoft probes can be associated with different resource groups, and will then follow that group if it is transferred to another cluster node. Note that Nimsoft probes also may expose one or more so-called shared sections, see Add new shared section for further information. The cluster probe will also send alarms if a cluster node or resource group changes state. Each of the nodes in the cluster must have the same set of Nimsoft probes installed. The cluster probe will automatically update changes to profile setup. These changes must be implemented on the probe running on the node currently in control of the associated resource group. General probe parameters must be updated manually on the different nodes. The collected data must contain the name and state of the nodes, the name and state of each resource group and on what node they are running. This information is used to manage where the different probe configurations should run and not run. NOTE: When the cdm probe runs in a clustered environment in co-operation with the cluster probe: If the flag /disk/fixed_default/active=yes; then cdm will issue alarms about disks which no longer is available at the current node (because it has been failed over to another node in the cluster). The cluster probe has removed the configuration, but cdm will the use the default settings and issue an alarm about the disk size being 0MB. Chapter 1: cluster 2.6 7

8 Cluster Probe installation The solution is to set the flag /disk/fixed_default/active=no. This section contains the following topics: Documentation Changes (see page 9) Cluster Probe installation (see page 9) Configuring the standard Nimsoft probes on the Cluster Nodes (see page 10) Cluster Probe Configuration (see page 11) The Cluster Properties (see page 12) General tab (see page 14) Alarm Settings tab (see page 15) QoS Settings tab (see page 19) The Node Properties (see page 20) General (see page 20) Configuration (see page 21) The Resource Group Properties (see page 21) Add new Monitoring Profiles (see page 22) Add new shared section (see page 24) Restart a Node (see page 25) Open the Log Viewer (see page 26) Configuration File versions (see page 28) 8 cluster Guide

9 Cluster Probe installation Documentation Changes This table describes the version history for this document. Version Date What's New? 2.6x October 2011 Initial Release Cluster Probe installation A wizard will guide you through the probe installation process. First, you must select type of cluster and click the Next button to continue. Chapter 1: cluster 2.6 9

10 Configuring the standard Nimsoft probes on the Cluster Nodes The next dialog appears with the cluster name filled in (the name is fetched from the node computer). Click the Finish button to finish the wizard. Configuring the standard Nimsoft probes on the Cluster Nodes As mentioned previously, each of the nodes in the cluster must have the same set of Nimsoft probes installed. These Nimsoft probes must be configured with setup parameters and monitoring parameters according the description of the different probes involved. If configuring Nimsoft probes to monitor shared resources, you must configure the monitoring profile on the probe residing on the Cluster Node currently in control of these resources. When these monitoring profiles are defined as resources in the cluster probe (see Add new ), then the profiles will be saved in the cluster probe and will be automatically uploaded to the other nodes when they gain control of the resource group. 10 cluster Guide

11 Cluster Probe Configuration Cluster Probe Configuration The cluster probe is configured by double-clicking the line representing the probe in the Infrastructure Manager. This brings up the configuration tool for the cluster probe. The configuration tool consists of a tree-structure on the left-hand side and a list on the right-hand side. The tree detects and displays the cluster structure (Nodes > Resource groups > Resources/Shared sections). The list on the right-hand side will change its contents according to the selected item on the left-hand side. When a Resource group is selected on the left-hand side, then resources/shared sections defined for that resource group will be listed on the right-hand side. Note the following symbols: Chapter 1: cluster

12 The Cluster Properties NOTE: While naming resources or resource groups, ensure that there are no preceding or trailing white spaces in the resource name. For example, "Test<space> Group" is a valid resource name; however names such as "<space>testgroup" or "TestGroup<space><space>" are not permissible. In case you have resource names with preceding or trailing white spaces in the existing cluster probe configuration, the upgrade from cluster probe version 2.3x to any higher version will require a clean install. The Cluster Properties You open the cluster properties dialog by clicking the icon in the upper left corner or by right-clicking the cluster icon in the tree-structure and selecting Properties. Note that you may also add and delete nodes from this right-click menu. 12 cluster Guide

13 The Cluster Properties The dialog has three tabs: The parameters: Chapter 1: cluster

14 General tab General tab Name: The name of the cluster. Use Cluster Name as Alarm Source: The cluster name will be used as the source of alarms generated by probes on Nodes in the Cluster when this option is checked. If not checked, the node name will be used. Log Level: Sets the level of details written to the log file. See also the section Open the Log Viewer. 14 cluster Guide

15 Alarm Settings tab Alarm Settings tab Here you can set the alarm message properties for both Node alarms and Resource Group alarms. Chapter 1: cluster

16 Alarm Settings tab Node Alarm Properties These alarm messages are sent when a Node changes its state (for example the node is shut down). Active: Alarms from the cluster nodes are activated when this option is checked. Message: Here you can define the message text for alarms coming from nodes in the cluster. The following variables can be used in the text string: name state state_text Clear: Here you can define the text for clear messages coming from nodes in the cluster. The following variables can be used in the text string: name state state_text Severity: Defines the severity level for alarms from the nodes. You can select different severity levels for state down, state up and other state than up or down. Subs ID: This is the NimBUS subsystem ID. The mapping is listed in the NAS (Nimsoft Alarm Server). Resource Group Alarm Properties (Active) These alarm messages are sent when a resource group changes its state. Note that the alarm is sent as soon as the state of the resource group changes (for example when a resource Group goes from "Online" to "Pending" or from "Offline" to "Pending"). IMPORTANT: If this flag is turned ON: Monitoring Profiles associated with a Resource Group that is NOT "Online" will be deactivated. Upon state change from "Online" to "Pending": - You will get an alarm from the cluster probe indicating the state of the resource group. 16 cluster Guide

17 Alarm Settings tab - NO alarms from other Nimsoft probes monitoring profiles associated with this resource group (these profiles will be deactivated/removed when state changes to "Pending", and inserted/activated again when state changes back to "Online"). If this flag is turned OFF: Monitoring profiles associated with a resource group will be kept active independently of resource group state. Upon state change from "Online" to "Pending": - NO alarm from cluster probe about the state of the resource group. - Other Nimsoft probes monitoring profiles associated with this resource group will send alarms if applicable (Not considering the state of the resource group). Active: Alarms from the resource groups are activated when this option is checked. Message: Here you can define the message text for alarms coming from the resource groups. The following variables can be used in the text string: name node state state_text Clear: Here you can define the text for clear messages coming from resource groups in the cluster. The following variables can be used in the text string: name node state state_text Severity: Defines the severity level for alarms from the resource groups. You can select different severity levels for state down, state up and other state than up or down. Subs ID This is the NimBUS subsystem ID. The mapping is listed in the NAS (Nimsoft Alarm Server). Resource Group Failover Alarm Properties (Active) Chapter 1: cluster

18 Alarm Settings tab These alarm messages are sent when a Resource group is moved to another node (due to a failover situation). Active: Alarms from the resource groups are activated when this option is checked. Message: Here you can define the message text for alarms coming from the resource group if the group has been moved to another node (either manually or due to an error situation). The following variables can be used in the text string: name node state state_text Clear: Resource groups can moved to another node either manually or due to an error situation. A clear message will be issued when the resource group is moved back to the original node again. Here you can define the message text. The following variables can be used in the text string: name node state state_text Severity: Defines the severity level for failover alarms from the resource groups. Subs ID: This is the NimBUS subsystem ID. The mapping is listed in the NAS (Nimsoft Alarm Server). 18 cluster Guide

19 QoS Settings tab QoS Settings tab This tab lets you select QoS messages to be sent on Resource Group state (where 1 = online, 2= offline and 3 other state), and/or Node state (where 1 = up, 2= down and 3 other state). Chapter 1: cluster

20 The Node Properties The Node Properties You open the node properties dialog by right-clicking a node icon in the tree-structure and selecting Properties. Note that you may also open the Log viewer window or restart the Cluster probe on the selected Node from this right-click menu. The Node properties dialog appears. The dialog has two tabs: General This tab contains the following four fields: Name field - the name of the Node Description - a short optional description of the Node IP address - the IP address of the Node computer. Probe Probe address, full path: /Domain/Hub/Node/Probe 20 cluster Guide

21 Configuration Configuration This tab contains options for setting check intervals for the Node. Select the Configuration tab. Specify the time interval (in seconds) for Check Group Interval (sets the check interval of the Resource groups on the Node) and Check Node Interval (sets the check interval of the Node). Click OK button. The Resource Group Properties You open the Resource Group properties dialog by right-clicking a Resource Group icon in the tree-structure and selecting Properties. Chapter 1: cluster

22 Add new Monitoring Profiles The Resource Group properties dialog appears: The following parameters can be modified in this dialog. The name of the Resource Group A description of the Resource Group Allow Partially Online : You can make the cluster probe interpret "Partially Online" resource groups as "Online". This is achieved by ticking off the checkbox "Allow Partially Online". Add new Monitoring Profiles You can add new monitoring profiles for a Resource group by right-clicking a group and selecting New. Note that this should be done on the Cluster currently in control of the Resource group. 22 cluster Guide

23 Add new Monitoring Profiles The New Monitor Resource properties dialog appears. Select a probe from the drop-down list. The configured profiles will be listed in the profile window. Select a profile from the list and then click OK. The monitoring profiles saved in the cluster probe will be automatically uploaded to the other nodes. Chapter 1: cluster

24 Add new shared section Add new shared section Nimsoft probes may expose one or more so-called shared sections for the cluster probe. These sections can be set up in the cluster probe to follow a Resource Group upon failover (almost like a profile section). All shared sections that the cluster probe has been configured for, will automatically be synchronized between the probes running on the different nodes in the cluster. The shared section will not be removed from the probe running on the Node losing control of the resource group, but any changes made to that section will be reflected in probe configurations on the node taking over control of the associated resource group. A typical shared section can be "/connections" or "/messages". Note: Any changes to a shared section must be implemented on the probe running on the Node currently in control of the associated Resource Group. You can add new shared section for a resource group by right-clicking a group and selecting New Shared Section. 24 cluster Guide

25 Restart a Node The New Shared Section properties dialog appears. Select a probe from the drop-down list. The configured sections will be listed in the profile window. Select a section from the list and then click OK. The sections saved in the cluster probe will be automatically uploaded to the other nodes. You can select all the checkpoints by clicking the option under the Section column. Alternatively, you can also select individual checkpoints by clicking them. Restart a Node You can restart the cluster probes on the different nodes in the cluster by right-clicking the node in the tree-structure and selecting Restart Probe. Chapter 1: cluster

26 Open the Log Viewer Open the Log Viewer You can open the Log viewer window to study the log file for the cluster probe on the different nodes by right-clicking a node in the tree-structure and selecting View log. The Log Viewer window appears, displaying log information for the selected Cluster. 26 cluster Guide

27 Open the Log Viewer NOTE: There are two different log files in the cluster probe directory. Cluster.log is default log file, but the user may change to view the log file plugin.log by right-clicking the cluster probe in the Infrastructure Manager, selecting Edit. Change from cluster.log to plugin.log in the Log File field of the dialog and click the OK button. Cluster.log logs the cluster probe activity, such as the communication between the cluster probes, and also other tasks performed by the cluster probe (sending alarms, activating/deactivating profiles for other probes etc.). Plugin.log logs information from the cluster software (via the different plugins). This is mainly status from Nodes and Resource Groups). There is one plugin fetching information from Microsoft Clusters, and another plugin for VERITAS clusters. Chapter 1: cluster

28 Configuration File versions Configuration File versions The cluster.cfg file displays version numbers and md5 values for the Cluster, Group and Shared Disks. You can open the cluster probe configuration file by selecting the cluster probe and pressing CTRL + N keys. 28 cluster Guide

29 Configuration File versions When a checkpoint selected under Shared Sections is modified, the version number as well as md5 value of the relevant Cluster Group or Shared Disks is updated on the node where the change has occurred. As per the check intervals specified in the Configuration tab of Cluster Node Properties dialog, the version numbers and md5 values are compared between the groups and nodes. In the case where the version numbers differ, the change is affected across the nodes. Chapter 1: cluster

30

31 Glossary Glossary 31