 |
What is an AdminUX alarm? |
| AdminUX carries out many tasks without supervision. An alarm is set when an operating system or application error condition that requires the attention of an administrator is discovered. |
|
|
|
Where are AdminUX alarm conditions defined? |
| Alarm test conditions are defined in the Alarms Matrix. Matrixes are text files that contain AdminUX's system administration policies. Refer to the matrix documentation for a complete list of variables and their function. |
|
|
|
How is an AdminUX event alarm created? |
| The Alarms Matrix is a template from which Bourne shell scripts to test for alarm conditions are created. AdminUX reads the matrix, creates script programs to test for alarm conditions, and runs the scripts. The results of the tests determine if an alarm condition exists. |
|
|
|
May I define custom alarms for my environment? |
| Yes. Users may customize alarms based on application events using standard AdminUX variables in reserved Sections 300 - 399. Users may also customize other non-application related alarms in Sections 400 - 699. |
|
|
|
How am I notified of alarms? |
Once an alarm has been created, the system administrator must be notified of the condition. There are 4 methods of notification:
1. Local Notification - audible beep of defined logins and/or console
2. Pager Notification - digital page is issued through the "cu" command
3. Custom Notification - executes commands/scripts written by the system administrator to send alarms by email, text page, or other methods.
4. Enterprise Management Console (EMC) notification - An unsolicited Simple Network Management Protocol (SNMP) "trap" of an event sent by AdminUX to an EMC like Computer Associates (CA) Unicenter, Tivoli, or HP OpenView.
Any or all of these methods can be configured and enabled. The default method is Custom Notification. AdminUX event alarms will be emailed to root unless otherwise specified on the appropriate line of the Alarms Matrix.
|
|
|
|
How do I respond to alarms? |
To check the alarms, issue one of the following commands:
AdminUXsh: Display alarms
ACP: Run==>Alarms and Notifications==>Alarms==>Display
Once you have seen the alarms, you can cancel them using:
AdminUXsh: Cancel alarms
ACP: Run==>Alarms and Notifications==>Alarms==>Cancel
Canceling an alarm notification only stops AdminUX from notifying you. It does not fix the condition that triggered the alarm. If the alarm condition persists, you will continue to receive notifications up to the maximum number defined in the alarm Section for that alarm and notification method.
|
|
|
|
What is an AdminUX log? |
| AdminUX generates around 80 logs. Each one gathers data on a specific area of the system. Keep in mind that these are data files and not reports. The main log is the Master Log that contains an entry for every major activity that AdminUX has run. The other logs are each for a specific purpose. |
|
|
|
How do I view a log? |
To display a current log or historical log use, issue one of the following commands:
AdminUXsh: Display logs "LOGNAME"(i.e. Display logs ALARMS)
ACP: Run==>Files==>Logs==>Display (displays ALL logs)
|
|
|
|
Why is the data in all these logs important? |
UNIX and LINUX are primarily data-less operating systems. If there is a problem with the system, the system administrator will need to know about resources such as processes, space, etc., over the past few hours, days, or months.
Even if there have been no problems with a server, the system administrator will still need data for periodic management inquiries and cleanup operations, such as what logins have not been used this past year. In addition, data can be extracted from AdminUX's logs and plotted to forecast when a resource such as disk space will be expended assuming the current rate.
|
|
|
|
How do I respond to alarms? |
| To check the alarms, issue one of the following commands:
AdminUXsh: Display alarms
ACP: Run==>Alarms and Notifications==>Alarms==>Display
Once you have seen the alarms, you can cancel them using:
AdminUXsh: Cancel alarms
ACP: Run==>Alarms and Notifications==>Alarms==>Cancel
Canceling an alarm notification only stops AdminUX from notifying you. It does not fix the condition that triggered the alarm. If the alarm condition persists, you will continue to receive notifications up to the maximum number defined in the alarm Section for that alarm and notification method. |
|
|
