Nimsoft Monitor. reboot Guide. v1.4 series

Transcription

1 Nimsoft Monitor reboot Guide v1.4 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: reboot reboot Configuration... 8 Editing a key Key features Examples Probe GUI Testing your Configuration Some useful Arguments Glossary 17 Contents 5

6

7 Chapter 1: reboot 1.4 This description applies to reboot probe version 1.4x The reboot probe is a "timed" probe that reboots the computer according to the probe configuration. When activated, the probe checks its configuration to determine if a reboot is needed, and performs the reboot at the specified point of time. On initial installation, the probe is not active. On activation, it is set to run five minutes past midnight each Monday morning. You can change these settings either using the probe GUI or using the Raw Configure tool. NOTE: You should modify the default configuration parameters according your requirements before activating the probe. This section contains the following topics: reboot Configuration (see page 8) Editing a key (see page 10) Key features (see page 10) Probe GUI (see page 13) Testing your Configuration (see page 15) Some useful Arguments (see page 16) Chapter 1: reboot 1.4 7

8 reboot Configuration reboot Configuration Open the Raw Configure tool to modify the configuration parameters for the probe. This is done by right-clicking the probe in Infrastructure Manager and selecting Configure. 8 reboot Guide

9 reboot Configuration The Raw Configure tool comes up, containing the following two sections: setup loglevel Sets the level of details written to the log file (where 0 gives the minimum level, 2 is the default level. A higher number gives more logging information). Logfile The name of the log file. The file is located in the../nimsoft/probes/system/reboot directory. send_alarm Send alarm when the reboot is executed. forced_shutdown Shut down immediately (without questions), even if applications have unsaved data. before_reboot_command A command to be executed before the reboot takes place. before_reboot_delay Time to wait for the specified before_reboot_command (if any) to finish before rebooting. alarm_level Set the alarm level, such as information, warning, or critical alarm_subsystem The alarm subsystem ID alarm_text timespec Specify the text to be displayed for the particular alarm level The timespec section in the configuration file is used to determine when the probe should reboot the computer. Using the timespec setup, it is possible to let the robot start the probe at regular intervals, and the probe itself will then determine if a reboot is needed. The two parameters in this section are: activate_when A time specification defining when to execute the reboot. last_reboot The probe saves the time of the last reboot it initiated (in seconds since EPOC). This value is used to determine whether a reboot should be initiated at the next probe activation. Chapter 1: reboot 1.4 9

10 Editing a key NOTE: EPOC is a system date used by computers, which starts on Thursday, January 01, :00:00 with the value 0. Editing a key Double-clicking a key opens the properties dialog for the key, enabling you to modify it. Click the OK button to exit the Edit Key dialog, and remember to click the Apply button in the Raw Configure dialog to activate configuration modifications. NOTE: It is recommended to test your parameters before activating the probe, see the section Testing your configuration. Key features A command can be executed before the reboot is initiated by specifying the before_reboot_command and before_reboot_delay in the setup section. 10 reboot Guide

11 Key features Examples Example.cfg: This example will execute the command net stop "TapeWare", wait for 50 seconds and then perform the reboot. <setup> loglevel = 2 logfile = reboot.log send_alarm = yes forced_shutdown = yes before_reboot_command = net stop "TapeWare" before_reboot_delay = 50 </setup> <timespec> activate_when = always last_reboot = </timespec> Example time specifications: Reboot when called: (default) activate_when = always Reboot every evening, but only once each day activate_when = after 22:00 and before 23:45 Reboot when at least 1 day has gone and it is Sunday evening after 10 pm: activate_when = sunday after 22:00 Reboot when at least 2 weeks and 1 day has gone and it is Sunday evening after 10 pm: activate_when = 3rd sunday after 22:00 Reboot every 1st Sunday of the month activate_when = 1st sunday of month after 22:00 activate_when syntax: activate_when -> [ always <day> <time interval> ] day -> [ <date> ( <enumeration> ) ( <weekday> ) ( ( of ) <month> ) ] weekday -> [ monday mon ] [ tuesday tue ] Chapter 1: reboot

12 Key features [ wednesday wed ] [ thursday thu ] [ friday fri ] [ saturday sat ] [ sunday sun ] enumeration -> [ 1st 1 1. ] [ 2nd 2 2. ] [ 3rd 3 3. ] [ 4th 4 4. ]... month -> month [ january jan ] [ february feb ] [ march mar ] [ april apr ]... date -> <monthday>.<monthno> monthday -> monthno -> time interval -> ( after <time> ) ( (and) before <time> ) time -> <hour>:<minute> hour -> minute -> reboot Guide

13 Probe GUI Probe GUI It is recommended to test the configuration parameters before activating the probe. Right-click the probe in the Infrastructure Manager and select Edit. The following dialog appears. Field Probe Type Command Arguments Working Directory Description The probe name. This field is non-editable. The type of execution. By default, timed option is selected. You can deactivate the setting by unselecting the Active checkbox. The process that will execute the rebbot. By default, it is nimreboot.exe Optional arguments that can be passed to the probe. For available arguments, please refer to the section "Some useful Arguments". The probe s working directory path. By default, the path is \probes\system\reboot Chapter 1: reboot

14 Probe GUI Field Configuration File Data File Time Specification Execution Group Description Log File Description The name of the probe configuration file. By default, the file is named reboot.cfg Specify the name if the probe data file, if required. Specify the time range within which the probe activity should be carried out Specify the time interval at which the reboot should be executed. You can specify the start time or frequency (in minutes). Choose Ignore option to nullify this field. Specified the probe grouping. By default, it is System group. A brief description of the probe activity. Be default, the description text is " Reboot computer". Name of the log file for the probe. By default, it is reboot.log 14 reboot Guide

15 Testing your Configuration Testing your Configuration It is recommended to test the configuration parameters before activating the probe. Right-click the probe in the Infrastructure Manager and select Edit. The following dialog appears. Type alarm -test in the Arguments field and click the OK button. Activate the probe by right-clicking it in the Infrastructure Manager and selecting Activate. The probe will now run with the configuration parameters defined and write to the log file as if it really performed the reboot, but without performing the reboot. Study the log file. When you have made sure that the configuration parameters work as intended, you remove the -test argument from the Edit dialog and activate the probe. Chapter 1: reboot

16 Some useful Arguments Some useful Arguments NOTE: The arguments -now, -alarm, -noalarm and -delay described below override settings in the configuration file. now Reboot now alarm Send alarm noalarm Do not send alarm delay Delay before reboot test Test only mode(no reboot, but writing to log file) -? and help Help. Note that these two help commands are available in reboot probe version 1.05 or newer 16 reboot Guide

17 Glossary Glossary 17