|
Very useful tool. I use it to
set agents in maintenance mode or clear the queue of the agents if something
seems to be wrong.
Attempts to put the MOM agent
into maintenance mode. Because this tool initiates the communication from the
agent, if the agent cannot contact the MOM server, the agent will not appear to
be in maintenance mode in the console.
If you have servers with
regular reboots set the Agent in maintenancemode through a schedule on the MOM
Server as described in the example. The timeout option is set in seconds. Let
the server be in maintenance mode for 10 Minutes (600), this makes sure, that
most of the alerts during boot-up (If you have any) are not recognized.
You can use the MOM SDK
Example (MaintenanceModeUtility)
as well, to call maintenance mode on the MOM server to ensure the agent can be
put into maintenance mode.
Example:
mominfo.exe /server:server1
/maintenancemode:600
Usage:
MOMInfo.exe <Action Flag> [<Location>] [<Options>]
<Action Flag> - flag specifying the action to perform, can be any one of
the following:
/rules - dumps the rules as xml (optional)
/responses - dumps the responses as xml (optional)
/varset - dumps the varset as xml (optional)
/clearqueue - clears all MOM queues (optional)
/maintenancemode:<timeout> - sets maintenance mode (optional)
<timeout> is the max amount of time to remain in maintenance mode,
defaults to '-1' (INFINITE), set to 'exit' to exit maintenance mode (optional)
/scriptdebugging:<script> - sets script debugging (optional),
<script> is the name of the script to debug defaults to '*', set to 'off'
to turn script debugging off (optional)
/errorhandling:<mode> - sets error handling (optional),
<mode> is the either off (default), queue, or auto (optional)
[<Location>] - location to run the action on (optional, defaults to
agent), can be any one of the following:
/momagent - returns info from the agent-side(optional)
/momserver - returns info from the server-side(optional)
[<Options>] - can be any one of the following (optional): /s - suppresses
all prompts (optional)
/out:<file> - file to contain the output of the action (required for
rules, responses, and varset actions)
/config:<Config Group> - the config group to run the action against
(optional)
/server:<server name> - the server to run the action on (optional)
|
