arti/irix-657m-src
1
0
Fork 0
Code Activity
Files
e7c7761dd1cf3929b3a32affcea843b768a23ec1
irix-657m-src/eoe/cmd/sss/console/plugins/plugin_datafiles/help_contents.html
calmsacibis995 8fc8fa8089 Source code upload
2022-09-29 17:59:04 +03:00

1522 lines
95 KiB
HTML
Raw Blame History

<HTML><HEAD><TITLE>SGI Embedded Support Partner - Help</TITLE></HEAD>
<BODY BGCOLOR="#ffffcc" link="#333300" vlink="#333300">
<font face="Arial,Helvetica">
<A NAME="archive_database"><p><b><font size=+1>Archive Database</font></b></a>
<P>Use the <TT>Archive Database</TT> command to delete a previously archived
database or to get instructions for archiving.</P>
<UL>
<LI>The <font face="Courier"><TT>Archive</TT></font> database option conserves disk space by compressing the
current database. The SGI Embedded Support Partner can continue to read the compressed data. To ensure data
integrity, you must execute the command <font face="Courier"><TT>esparchive</TT></font> from a command line.
All Embedded Support Partner daemons are shut down during this operation and will be automatically restarted
when archiving is completed. Archiving is possible only when the size of the current database is at least
10 megabytes; the compression mechanism will not work if you try to archive a smaller database.<p>
<LI>The <font face="Courier"><TT>Delete Database</TT></font> option deletes an archived database that you no
longer need.
</UL>
<A NAME="sysinfo"><HR NOSHADE SIZE="3"></a>
<b><font size=+1>SYSTEM INFORMATION</font></b>
<P>The <TT>SYSTEM INFORMATION</TT> category provides information about the
system on which the Single-system Manager is running.</P>
<P>Use the commands in this category to display the following types of
system information:</P>
<UL>
<LI>Hardware configuration for a specific date and time
<LI>Software configuration and version information for a specific date and time
<LI>System changes between a range of dates
<LI>Part changes for a specific hardware component
<LI>Events that have occurred on the system
<LI>Actions that the SGI Embedded Support Partner has performed
<LI>Availability information for a specified range of dates
</UL>
All reports in this category display general system information:
<UL>
<LI>System name
<LI>System identification number
<LI>System serial number
<LI>IP type
<LI>System IP address
</UL>
<A NAME="sysinfo_hardware"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Hardware</b>
<P>Use this command to display the hardware configuration of the system,
which existed at a specific time on a specific date.</P>
<p>Hardware configuration information is available for the following systems:</p>
<ul>
<li>IP19 - Challenge/Onyx
<li>IP21 - Power Challenge/Power Onyx
<Li>IP25 - Power Challenge 10000/Power Onyx 10000
<li>IP27 - Origin2000/Onyx2
<li>IP29 - Origin200
<li>IP30 - Octane
<li>IP32 - O2
</ul>
<P>If you are interested in hardware information for a specific date/time, enter the desired date/time in the
appropriate field. Otherwise, the information displayed is as of 23:59:59 for the current date or the latest available.</p>
<p>Note: The current date means the date that your system displays.</p>
<p>You must select a database that corresponds to the date that you specified.<p>
<p>For a <b>Group of Systems</b>, choose the system whose hardware information you want.</p>
<P>If you have changed the query date or time, this report displays a table of the
hardware components that form the selected configuration. The information is displayed in a hierarchical manner.
If information is not available or not applicable, &#034;N/A&#034; is displayed.</P>
<P>The first column of the report table can include one or more of the following symbols: a double arrow
(<img src="/images/double_arrow_right.gif" alt="double arrow">), a single arrow that points to the right
(<img src="/images/arrow_right.gif" alt="right arrow">), or a single arrow that points down (<img src="/images/arrow_down.gif" alt="down arrow">).
Clicking on a double arrow fully expands a particular entry and all of the components and subcomponents below it. For the Origin2000 and Onyx2
series double error expands only one module and its components. Clicking on a right arrow expands the
table to display the subcomponents that compose the selected component. Clicking on a down arrow collapses the subcomponent display.</P>
<P>The other columns of the table contain the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</font></B></TD>
<TD><B><font face="Arial,Helvetica">Description</font></B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>NAME</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The name of the component. For the top most component(s), numbers are used to
indicate module number(s) (Origin2000/Onyx2)</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>LOCATION</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The location of the component</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>PART_NUMBER</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The part number of the component</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>SERIAL_NUMBER</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The serial number of the component</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>REVISION</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The revision level of the component</TD>
</TR>
</TABLE>
<A NAME="sysinfo_software"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Software</b>
<P>Use this command to display the software configuration of the system and version information
that existed at a specific time on a specific date.</P>
<p>If you are interested in software information for a specific date/time, enter the desired date/time in
the appropriate field.
Otherwise, the displayed information defaults to 23:59:59 for the current date or the latest available.</p>
<p>Note: The current date means the date that your system displays.</p>
<p>You must select the database that corresponds to the date that you specified.</p>
<p>For a <b>Group of Systems</b>, choose the system whose hardware information you want.
<P>&nbsp;</p>
<p>This report lists the software that was installed on the system at the time you specify.
The installed software is listed 10 items per page. <img src="/images/arrow_right.gif"
alt="next 10 pages"> lists the next 10 pages, <img src="/images/double_arrow_right.gif"
alt="last page"> goes to the last page. <img src="/images/arrow_left.gif"
alt="previous 10 pages"> lists the previous 10 pages, and <img src="/images/double_arrow_left.gif"
alt="first page"> returns to the first page.
The report table provides the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>NAME</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The name of the software application</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>VERSION</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The version number of the software application</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>INSTALL_DATE</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date on which the software application was installed</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>DESCRIPTION</TT></TD>
<TD><font face="Arial,Helvetica">A description of the software</TD>
</TR>
</TABLE>
<A NAME="sysinfo_system_changes"><p><hr></A>
<b>SYSTEM INFORMATION &gt; System Changes</b>
<P>Use this command to view any system changes that occurred within the range of dates that you specify.</P>
<p>If you want to see information for a specific period of time, change the entries in the &#034;From&#034; and &#034;To&#034; fields.
By default, the dates are set to the current day.</p>
<p>Note: The current date means the date that your system displays.</p>
<p>You must select the database that corresponds to the dates that you specified.</p>
<p>System change information can be collected from only one database at a time.</p>
<p>For a <b>Group of Systems</b>, you must also choose the system whose hardware information you want.</p>
<P>The SGI Embedded Support Partner tracks the following types of system changes:</P>
<ul>
<li>Software changes
<li>Hardware changes
<li>System changes
</ul>
<P>The software table describes all software changes that occurred during the period
of time that you specified. The table provides the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The name of the software application</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Version</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The version number of the software
application</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Install Date</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date on which the software
application was installed</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Deinstall Date</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date on which the software
application was deinstalled</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Description</TT></TD>
<TD><font face="Arial,Helvetica">A description of the software</TD>
</TR>
</TABLE>
<P>The hardware table describes all hardware changes that occurred during the period of time
that you specified. The table provides the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The name of the part</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Location</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The location of the part</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Part Number</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The part number for the part</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Serial NUmber</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The serial number of the part</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Revision</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The revision level of the part</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Install Time</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date on which the component was
installed</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Deinstall Time</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date on which the component was
deinstalled.</TD>
</TR>
</TABLE>
<P>The system changes table describes all system changes (for example, hostname, IP address change, and so on)
that occurred during the period of time that you specified. The table provides the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>System Changes</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Current/Previous system</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>System ID</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Numeric System ID</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>System Type</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">System IP type</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>System Serial Number</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The serial number of a system</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Hostname</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The hostname of a system</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>IP Address</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">IP address of a system</TD>
</TR>
</TABLE>
<A NAME="sysinfo_part_changes"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Part Changes</b>
<P>Use this command to view the transaction history of a part.</p>
<P>You must enter the component serial number. (If
necessary, use the <a href="#sysinfo_hardware">SYSTEM Information &gt;
Hardware</a> to locate a serial number.)</P>
<p>You must choose a database to view the history of
the component whose serial number you entered above.</P>
<p>For a <b>Group of Systems</b>, you also must choose the system whose part transaction
history you want to view.</p>
<p>The report table lists
the name of the component,
the module number in which the component was installed,
the part number of the component,
the serial number of the module,
the revision number of the part,
and the slot number in which the component was installed.</P>
<A NAME="sysinfo_events"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Events Registered</b>
<P>Use this command to view information about events that SGI Embedded
Support Partner has registered.</P>
<P>Enter a range of dates for the events that you want to view. For <b>Group of
Systems</b> you must choose the system whose events registered information that you want to
see. Then, choose the type of event information that you want to view. The following
options are available:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>All System Events</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A view of all events that occurred
between a range of dates that you specify</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Specific System Event</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A view of a specific event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>System Events by Class</TT></TD>
<TD><font face="Arial,Helvetica">A view of a selected class of events</TD>
</TR>
</TABLE>
<A NAME="screens_all_sys_events1"><p><b>All System Events</b></a>
<P>The report table provides the following information about events that were registered
within the selected range of dates:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Number</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The chronological order of the
event within the event list</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Class</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The class in which the event belongs
(for example, Availability)</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A brief description of the event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event ID</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The unique identification number
assigned to this event. You can use this number to find this event via SYSLOG</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>First Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
first occurred</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Last Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
last occurred. If Number of Occurrences is 1, the time value of the First Occurrence and the
time value of the Last Occurrence will be identical</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Number of Occurrences</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The number of times that the event
occurred. This number corresponds to the number of events that must occur before registration
begins. By default, this number is 1.</TD>
</TR>
</TABLE>
<A NAME="screens_specific_sys_event1"><p><b>Specific System Event</b></a>
<P>Use this report to track a specific event that is associated with an actual or suspected
system problem. Choose an event class from the list that appears.</P>
<A NAME="screens_specific_sys_event2"><p></A>
Use this page to specify the event that you want to view. Choose the
event from the list of events in the class that you have already specified.</P>
<A NAME="screens_specific_sys_event3">&nbsp;<p></A>
The report table provides the following information about the event
registrations between the selected range of dates:<P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>First Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
first occurred</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Last Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
last occurred. If Number of Occurrences is 1, the time value of the First Occurrence and the
time value of the Last Occurrence will be identical.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Number of Events</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The number of times that the event
occurred. This number corresponds to the number of events that must occur before
registration begins. By default, this number is 1.</TD>
</TR>
</TABLE>
<A NAME="screens_sys_event_class"><P><b>System Events by Class</b></a>
<P>Use this report when you need information about events that are associated with a specific
class. For example, use Memory class to track various memory
events. Choose the appropriate class for the event that you want to view. </P>
<A NAME="screens_sys_event_class2">&nbsp;<p></A>
The report table provides the following information about events that were
registered between the selected range of dates:<P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Number</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The chronological order of the
event within the event list</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A brief description of the event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event ID</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The unique identification number
assigned to this event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>First Event Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
first occurred</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Last Event Occurrence</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the event
last occurred. If Number of Occurrences is 1, the time value of the First Occurrence and the
time value of the Last Occurrence will be identical</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Number of Events</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The number of times that the event
occurred. This number corresponds to the number of events that must occur before
registration begins. By default, this number is 1.</TD>
</TR>
</TABLE>
<A NAME="sysinfo_actions"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Actions Taken</b>
<P>Use this command to display information about actions that have been performed
by SGI Embedded Support Partner.</P>
<p>Specify the range of dates for which you want to report actions taken.
If you do not enter a date, this option defaults to the current date.</p>
<p>For a <b>Group of Systems</b>, you must specify the system for which you want to
generate a report. Note: the report shows actions taken by Systems Group Manager for
the system that you specify.</p>
<p>You must choose one of the two available types of reports:</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Report Type</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>All Actions Taken</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Displays all actions that were taken
on the system and the events that triggered those actions</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Actions Taken for a Specific Event</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Displays actions taken for a specific event only</TD>
</TR>
</TABLE>
<a name="all_actions_taken"><p><b>All Actions Taken</b></p></a>
<P>This option displays the actions that the SGI Embedded
Support Partner performed within the range of dates that you specified.
The report table provides the following information about actions that were taken for all events
between the selected range of dates:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Class</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The class in which the event belongs (for
example, Availability)</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event Description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A brief description of the event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Event ID</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The unique identification number
assigned to this event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action Description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A brief description of the action</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action Taken</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The action that SGI Embedded
Support Partner performed in response to the event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Time of Action</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that SGI
Embedded Support Partner performed the action</TD>
</TR>
</TABLE>
<a name="specific_action_taken"><p><b>Actions Taken for a Specific Event</b></p></a>
<p>Use this option when you want to view actions taken for specific events.
Choose an event class that contains the event that you want to select.</p>
<a name="specific_action_taken1">&nbsp;<p></a>
From the list of events, choose the event that you want to research.</p>
<P>The report table provides the following information about actions that were taken for the
specified event between the selected range of dates:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Column</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action Description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A brief description of the action</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action Taken</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The action that the SGI Embedded
Support Partner performed in response to the event</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Time of Action</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The date and time that the SGI
Embedded Support Partner performed the action</TD>
</TR>
</TABLE>
<a name="report_diags_result"><p><hr></a>
<b>Diagnostics Results</b>
<p>This command displays the results of the diagnostics that you run on the system.
<p>You must specify the range of dates for which you want to view diagnostics results.
For a <b>Group of Systems</b>, you must also specify a system for which you want to view diagnostics results.
<p>The top portion of the diagnostic report contains the information that pertains
to the system from which you requested the report.
<p>The diagnostics results table provides the following information for all diagnostics that were run
on the system during the period of time that you specified:
<table border=1 width=100% cellpadding=4 cellspacing=2>
<tr><td><b><font face="Arial,Helvetica">Column</b></td>
<td><b><font face="Arial,Helvetica">Description</b></td></tr>
<tr valign=top><td><tt>Diagnostic Name</tt></td>
<td><font face="Arial,Helvetica">Contains the name of diagnostic.
In cases where multiple tests run as a group under one program (for example, under SVP),
the total number of tests is indicated in parentheses next to the name of the diagnostic:
<dl><dd><font face="Courier"><tt>SVP (86)</tt></font>
means that 86 tests ran under the SVP program.</dd></dl></td></tr>
<tr valign=top><td><tt>Diagnostic Status</tt></td>
<td><font face="Arial,Helvetica">Diagnostic status can be PASS, FAIL or COMPLETE.
<dl><dd>PASS indicates that the diagnostic completed successfully<p>
<dd>FAIL indicates a failure occurred<p>
<dd>COMPLETE indicates that multiple tests ran, and one or more
of them failed and others completed successfully</dd></dl></td></tr>
<tr valign=top><td><tt>Diagnostic Result Time</tt></td>
<td><font face="Arial,Helvetica">The time when the diagnostic test
completed. When multiple tests run under one program, the
Diagnostic Result Time indicates the time when the entire program
completed.</td></tr>
</table><p>
</ul>
<A NAME="sysinfo_availability"><p><hr></A>
<b>SYSTEM INFORMATION &gt; Availability</b>
<P>This command displays system availability statistics. The upper portion of this page displays the total availability percentage
and the mean time between interrupts (MTBI) in minutes.</P>
<P>You must specify the range of dates and type of availability information that you want to view. For a
<b>Group of Systems</b>, you must also specify a system or a set of systems for which you want to view availability information.</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Overall Availability</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Summary of overall availability information for
the system</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Availability Events List</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Information about individual
availability events that the system has registered</TD>
</TR>
</TABLE>
<A NAME="screen_over_avail"><p><b>Overall Availability</b></a>
<p>The <font face="Courier"><TT>Overall Availability</TT></font> option covers the aggregation of events for the given
system. Events are grouped as either "Unscheduled" or "Service Action" (controlled shutdown) events. Events are
further classified by categories within these two groups. For each category, the overall availability report includes
the count of events in that category, the total downtime (in minutes), the MTBI (mean time between interrupts, in
minutes) and the availability as a percentage. MTBI and availability per category are computed for events within the
category as applied to the entire time period of the report. Count, total downtime, MTBI, and availability are also
displayed for the two groups, as well as the final total of all the events.</p>
<p>The average, least, and most uptimes and downtimes are also included in the report in addition to logging start time
and the duration of system uptime since the last boot.</p>
<p>On a <b>Group of Systems</b>, the above statistics are calculated for all systems in the group.</p>
<P>The <font face="Courier"><TT>Overall Availability</TT></font> table summarizes the overall availability
of the system:</P>
<UL>
<LI>Information about service actions (number, downtime, MTBI, and availability percentage)
<LI>Average uptime
<LI>Least uptime
<LI>Most uptime
<LI>Average downtime
<LI>Least downtime
<LI>Most downtime
<LI>The time at which availability monitoring was started
<LI>The time the last boot occurred
<LI>The amount of time that the system has been up
</UL>
<P>For a <b>Single System</b>, use the <font face="Courier"><TT>Event Availability Information</TT></font> link at the
bottom of the page to access information about the individual availability events that the system has registered.</P>
<P>For a <b>Group of Systems</b>, use the <font face="Courier"><TT>Availability Summary For All Hosts</TT></font> link
at the bottom of the page to access information about the summary of all availability events that the system(s) has registered.</P>
<a name="av_summary_all_hosts"><p><b>Availability Summary For All Hosts</b></p></a>
<p>This report is applicable only for a <b>Group of Systems</b>. It displays the summary of events and availability of
each individual system that has been subscribed to. Clicking on <font face="Courier"><TT>Host Overall Availability</TT></font>
will display the <font face="Courier"><TT>Overall Availability</TT></font> for that particular system. Please refer to the
<a href="#screen_over_avail">Overall Availability</a> for more information.</p> <a name="event_availability_info"><p><b>Event Availability Information</b></p></a>
<p>In the events list display, the fields shown are Start time (when the system was previously booted), the Incident Time,
when the event occurred, the uptime and downtime in minutes, and a very brief description of the event type or cause of the
event. The <font face="Courier"><TT>Event Summary</tt></font> displays the event information with more details, including
a complete event type description.</p>
<a name="event_summary">&nbsp;<p></a>
The report provides a summary of an event that includes the following information:</P>
<UL>
<LI>The hostname of the system
<LI>The reason for the shutdown
<LI>The time that the system was initially started
<LI>The time that the incident occurred
<LI>The time that the system was restarted after the incident occurred
<LI>The amount of time that the system was up before the incident occurred
<LI>The amount of time that the system was down because of the incident
</UL>
<p>If a system panic occurs, this report also includes a brief summary of why the system panicked.</p>
<HR NOSHADE SIZE="3">
<b><font size=+1><A NAME="setup">SETUP</A></font></b>
<P>Use the <font face="Courier"><TT>SETUP</TT></font> menu to set or change the following parameters that
control the operation of SGI Embedded Support Partner:</P>
<UL>
<LI>Web server access parameters
<LI>Global event parameters
<LI>Event parameters
<LI>Action parameters
<LI>Notification parameters
<LI>Availability monitoring parameters
</UL>
<HR>
<b><A NAME="setup_global_web_access_cfg">SETUP &gt; Global &gt; Server</A></b>
<P>This command configures the Web server that SGI Embedded Support Partner uses. Use this command to perform the following functions:</P>
<UL>
<LI>Display the current server port, version number, and identification information
<LI>Specify access privileges to the system via IP addresses
<LI>Change the username of the current Web server user
<LI>Change the password of the current Web server user
</UL>
<P>The upper portion of this page displays the following information:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Name</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Server Identification</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The name of the Web server software in use</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Server Version</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The version level of the Web server
software and its installation date</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Server Port</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The Web server connection port in use</TD>
</TR>
</TABLE>
<P>The lower portion of this page displays the following selectable options:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Server Access Permissions</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Enables or restricts access by external systems</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>User Name &amp; Password Change</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Enables you to change the current username and password</TD>
</TR>
</TABLE>
<A NAME="server_access_option"><p><b>Server Access Permissions Option</b></a>
<P>Use this page to specify which systems can access the SGI Embedded
Support Partner Web server. Any change that you make to the server access
list takes effect immediately.</P>
<p>You can specify the exact IP address or IP address mask using a wildcard. For example,
197.23.14.5, or 135.*.*.5, or *.*.*.*, and so on.</p>
<p>IMPORTANT: If <font face="Courier"><tt>Restrict access to the systems with the following IP addresses</tt></font>
list is empty, all systems are allowed to connect to the SGI Embedded Support Partner server. To restrict access,
add &#034;*.*.*.*&#034; to the restriction list. All IP addresses are allowed to connect to the server by default.
Only the presence of the &#034;*.*.*.*&#034; in the restriction list enables the filtering mechanism of the server.
Combinations of different IP addresses in &#034;restricted&#034; and &#034;allowed&#034; lists can create complex and
flexible filtering mechanism for incoming IP addresses. Be very cautious in updating the &#034;restricted&#034; and
&#034;allowed&#034; lists to avoid locking yourself out of the Embedded Support Partner facilities.</p>
<b><A NAME="user_name_change_option">User Name and Password Change Option</A></b>
<P>Use this page to change a current username or password that enables access to
SGI Embedded Support Partner. Any change that you make to a username or
password takes effect immediately.</P>
<p>The username and password must each contain between 1 and 128 characters.
Characters like &#034;*&#034;, &#034;&amp;&#034;, and &#034;:&#034; are not allowed in the username
and password strings.</p>
<p>The default username <font face="Courier"><tt>administrator</tt></font> and the default password
<font face="Courier"><tt>partner</tt></font> must be changed immediately after installation.</p>
<A NAME="setup_global_event_cfg"><p><hr></A>
<b>SETUP &gt; Global &gt; Global Configuration</b>
<P>An <I>event</I> is a happening or an occurrence that takes place on the
system that SGI Embedded Support Partner is monitoring. A few examples of
events follow: parity errors, disk full, nonmaskable interrupts (NMI), and
even activities of the SGI Embedded Support Partner itself.</P>
<P>Use this page if you want to reset the following parameters for all events on the system.
In the case of a <b>Group of Systems</b>, use this option to reset parameters for all systems.</p>
<UL>
<LI>The <font face="Courier"><TT>Log events</TT></font> parameter enables or disables global
event logging. Select <font face="Courier"><TT>Yes</TT></font> to log events in the SGI
Embedded Support Partner database. Select <font face="Courier"><TT>No</TT></font> if you
do not want to log events in the SGI Embedded Support Partner database. You can disable event
logging if you are not interested in the history of events on the system.<p>
<LI>The <font face="Courier"><TT>Throttle events</TT></font> parameter enables or disables event
throttling requirements for all events. Select <font face="Courier"><TT>Yes</TT></font> to require that a
specific number of events (a threshold) must occur before the event is registered in the SGI Embedded Support Partner database. Select
<font face="Courier"><TT>No</TT></font> to register every event in the SGI Embedded System Partner database. Enable event throttling,
if you are not interested in every event of a particular type, but you are interested only
when this event occurs a specified number of times.<p>
<LI>The <font face="Courier"><TT>Act on event</TT></font> parameter enables or disables the capability of SGI Embedded Support
Partner to react (respond) to events. Select <font face="Courier"><TT>Yes</TT></font> to specify that the SGI Embedded Support
Partner should respond (react) to all events. Select <font face="Courier"><TT>No</TT></font> to specify that the SGI
Embedded Support Partner should not respond (react) to any events.<p>
Note: Refer to the SETUP &gt; Events and the SETUP &gt; Actions menus for
additional information about events and actions.
</UL>
<p>Note: The Global Configuration setting will override individual event setting.</p>
<A NAME="setup_events_viewcurr"><p><hr></A>
<b>SETUP &gt; Events &gt; View Current Setup</b>
<P>Because the number of events can be extensive, events are divided into sets called <I>classes</I>. This scheme simplifies
the management of events, enables more efficient use of displays, and facilitates navigation within
the program.</P>
<p>The following options are available:</p>
<ul>
<li>View Event
<li>View Event List
<li>View Classes
</ul>
<a name="setup_view_event"><p><b>View Event</b></p></a>
<p>This option is available only for a <b>Single System</b>. Use this option to determine the
current setting of an individual event. This option allows you to view:
<ul>
<li>Event class ID and class name
<li>Event ID and event description
<li>Event registration
<Li>Number of events that must occur per registration
<li>Actions for the specified event
</ul>
<a name="setup_view_event_list"><p><b>View Event List</b></p></a>
<p>This option is available for a <b>Single System</b> and for a <b>Group of Systems</b>. Use this option when you want to obtain
a list of all events compatible with the SGI Embedded Support Partner. The report allows you to view:</p>
<ul>
<li>Class Name
<li>Event Description
<li>Member Systems (<b>Group of Systems</b> only) *
</ul>
<a name="setup_view_classes"><p><b>View Classes</b></p></a>
<p>This option is available for a <b>Single System</b> and for a <b>Group of Systems</b>. Use this option when you want to view
all classes available on the system. The report allows you to view:</p>
<ul>
<li>Class ID
<Li>Class Name
<li>Member Systems (<b>Group of Systems</b> only) *
</ul>
<p>* A Member system is a system that is subscribed to the Systems Group Manager.</p>
<A NAME="screens_setup_events_update"><p><hr></A>
<b>SETUP &gt; Events &gt; Update</b>
<p>Use this command to update existing events. For a <b>Group of Systems</b>, you must choose the system whose event you
want to update.</p>
<p>You must select the class that contains the event(s) that you want to update.</p>
<A NAME="setup_events_update_type">&nbsp;<p></a>
Specify the event(s) that you want to update by one of the following methods:</p>
<ol>
<Li>You can choose one event and proceed with Single Event Update<p>or<p>
<li>You can choose multiple events and proceed with Multiple Events Update (<b>Single System</b> only)
</ol>
<dl><dd><a name="screens_setup_events_update1"><b>1. Single Event Update</b></a>
<p>Single Event Update displays the current parameters for a chosen event:</p>
<ul>
<li>You can set whether or not SGI Embedded Support Partner registers the selected event. This parameter is applicable
for a <b>Single System</b> only. You do not need to set this parameter for a <b>Group of Systems</b>. Subscribing an
event automatically registers the event.
<li>You can change the number of events that must occur per registration (default = 1)
<li>You can change the action(s) that will be taken upon the occurrence of the specified event<p>
Note: You can select more than one action. If you cannot locate an action that you need, use the SETUP > Actions > Add command to add it.
</ul>
<a name="screens_setup_events_update2"><p><b>2. Multiple Event Update</b></p></a>
<p>This option is available for a <b>Single System</b> only. When you update multiple events, you must remember
that any changes you specify on this page will affect all of the selected events:</p>
<ul>
<li>You can set whether or not the SGI Embedded Support Partner registers the selected event (default <font face="Courier"><tt>Register</tt></font>)
<li>You can change the number of events that must occur per registration (default = 1)
</ul>
<p>To replace, add, or delete actions for multiple events, use <a href="#setup_events_update_event_actions">SETUP > Events > Update Event Actions</a>.
</dd></dl>
<A NAME="setup_events_update_event_actions"><p><b>SETUP &gt; Events &gt; Update Event Actions</b></p></a>
<P>An <I>event/action assignment</I> defines the action that the SGI Embedded
Support Partner performs when it registers a specific event. An <I>event/action</I>
is a cause-and-effect relationship between an event and an ensuing action.
Use this command to modify an event/action assignment; that is, to replace,
add, or delete event/action assignments.</P>
<P>You can select the event/action relationship that you want to update by two methods:</P>
<UL>
<LI>Method 1: Choose an action for which you want to modify the <I>event</I>
assignment.
<LI>Method 2: Choose an event for which you want to modify the <I>action</I>
assignment.
</UL>
<A NAME="setup_events_update_event_actions_method1"><b>Updating Event Action Assignments (Method 1)</b></a>
<P>1. Choose the action that you want to update.</P>
<P>2. Select the events for which you want to update the action assignment.</P>
<P>3. Click on <font face="Courier"><TT>Replace</TT>, <TT>Add</TT></font>, or <font face="Courier"><TT>Delete</TT></font>.</P>
<b><A NAME="screens_update_event_actions_update1">Replace Option:</A></b>
<P>The <font face="Courier"><TT>Replace</TT></font> option deletes the current action from the event
and assigns a new action to the event. Choose the action with which you
want to replace the current action.</P>
<b><A NAME="screens_update_event_actions_add1">Add Option:</A></b>
<P>The <font face="Courier"><TT>Add</TT></font> option assigns the selected action to one or more
events. Select one or more actions that you want to assign to the selected event(s) in addition to the existing ones.</P>
<b><A NAME="screens_update_event_actions_delete1">Delete Option:</A></b>
<P>The <font face="Courier"><TT>Delete</TT></font> option deletes the action from the events that you selected.</P>
<A NAME="setup_events_update_event_actions_method2"><b>Updating Event Action Assignments (Method 2)</b></a>
<P>1. Choose the class that you want to search.</P>
<P>2. Choose the event(s) in the class.</P>
<P>3. Choose the action that you want to add. (This method does not provide
<font face="Courier"><TT>Replace</TT></font> or <font face="Courier"><TT>Delete</TT></font> options.)</P>
<p><HR>
<b><A NAME="setup_events_add">SETUP &gt; Events &gt; Add</A></b>
<P>Use this command to add new events for the SGI Embedded Support
Partner to monitor. This option is available for a <b>Single System</b> only. To add an event to a <b>Group of Systems</b>,
refer to <a href="#subscribe">SETUP &gt; Event &gt; Subscribe</a>. The following options are available:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Either select a class name for the new event</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the existing class to which you want to add the event</P>
If you want to add a new class, leave this option unselected and enter
a new class description.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Or create a new class name for the new event</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies a new class of events</P>
Use this option if you want to add an event to a new class of events.
If you want to add an event to an existing class of events, select the
class from the existing classes and leave this option blank.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Enter a name for the new event</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies a description of the event that is
shown in the interface</TD>
</TR>
</TABLE>
<a name="setup_events_add1"><p>You may set the following parameters:</a>
<ul>
<li>Whether or not SGI Embedded Support Partner registers the selected event (default Register)
<li>The number of events that must occur per registration (default = 1)
<li>The action(s) that will be taken upon the occurrence of the specified event
</ul>
<a name="setup_events_delete"><p><b>SETUP &gt; Events &gt; Delete</b></p></a>
<p>Use this command to delete custom event or custom class from the SGI Embedded Support Partner.
All records and information associated with these classes/events will also be deleted.
This option is available for a <b>Single System</b> only. To delete an event from a <b>Group of Systems</b>,
refer to <a href="#subscribe">SETUP &gt; Event &gt; Subscribe</a>.</p>
<p>If you want to delete a custom class, choose the class that you want to delete. Click on
<font face="Courier"><tt>Delete Class</tt></font>. The class will be deleted with all associated
events and event data. You are not allowed to delete System classes .</p>
<p>If you want to delete a custom event, choose the class to which the event belongs. Click on
<font face="Courier"><tt>Delete Event</tt></font>.</p>
<a name="setup_events_delete1">&nbsp;<p></a>
From the list of the events for the selected class, choose the event that you want to delete.</p>
<p>Note: All event data associated with this event will be deleted.</p>
<A NAME="subscribe"><p><b>SETUP &gt; Events &gt; Subscribe</b></p></a>
<P>This option is available for <b>Group of Systems</b> only. Subscription is the process by which a Systems Group Manager
requests a remote system that is running SGI Embedded Support Partner to forward events that occur on the remote system. Subscription
is done based on Events that are recognized on the remote host. Events can be individually subscribed with some exceptions. For
example, all Availability class events are subscribed together. This is done to provide accurate availability statistics.
Once an event is subscribed, the remote host forwards any occurrences of the event to Group Manager, which enables the Systems Group
Manager to act as a central repository of information for different remote systems.</P>
<P>Unsubscription is the reverse of Subscription. It is the process by which Systems Group Manager informs a remote system
that it is no longer interested in the events that were subscribed earlier.</P>
<A NAME="setup_events_subscribe1">&nbsp;<p></A>
Once you enter a hostname and choose subscribe or unsubscribe, you must select a class that you want to operate upon.
For subscription, the list of classes is obtained from the remote host. For unsubscription, the list of classes is obtained from
the SGI Embedded Support Partner database, which runs as Systems Group Manager.</P>
<A NAME="setup_events_subscribe2">&nbsp;<p></A>
After a class is selected, all the events that are available for that class are presented.
You may subscribe or unsubscribe certain classes of events only in full. For these classes, the list of events will
not be presented. Instead, an entry that says 'All Events' is presented.</P>
<P>For subscription, the list of events is obtained from the remote host. If the same class was subscribed before,
events that were already subscribed before will not appear in the list.</P>
<P>For unsubscription, the list of events is obtained from the Systems Group Manager database. If the same class was
unsubscribed before, events that were already unsubscribed will not appear in the list.</P>
<A NAME="setup_actions_viewcurr"><p><hr></A>
<b>SETUP &gt; Actions &gt; View Current Setup</b>
<P>Use this command to view the current configuration of actions. The following options are available:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>View Action Setup</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Displays the configuration information for a
specific action</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>View Available Actions List</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Displays a table of all actions that are
currently available</TD>
</TR>
</TABLE>
<A NAME="screens_action_setup"><p><b>View Action Setup</b></p></a>
<p>You must choose an action whose information you want to view.</p>
<p>This option allows you to view the following action information:</p>
<ul>
<li>Action command string - an exact command that will execute
<li>Action description - simple description of the action
<Li>Execute this action as nobody, guest, etc. (default = nobody)
<li>Action timeout (default = 600 seconds)
<li>Number of times the event must be registered before an action will be taken (default = 1)
<li>Retry times (default = 0)
</ul>
<A NAME="screens_avail_action"><p><b>View Available Actions List</b></p></a>
<P>This report displays all actions that are currently available.
The table includes the following information:</P>
<ul>
<li>Action order number
<li>Action command string - an exact command that will execute
<li>Action description - simple description of the action
</ul>
<A NAME="setup_actions_update"><p><hr></A>
<b>SETUP &gt; Actions &gt; Update</b>
<P>Use this command to update an existing action.</p>
<p>Select an action that you want to update. You can modify all of the action parameters, except the action description:</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Actual action command string</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the command that action executes</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>A username to execute the action as</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the user account that the SGI
Embedded Support uses to execute the command.<p>Default = nobody<p>Note: username cannot
be set to "root" nor to any any other account that has root privileges.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action timeout</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the time period for which the action can run without being killed</p>
The value that you specify must be a multiple of 5. Default = 600 seconds</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>The number of times that the event must be registered before an action will be taken</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies how many times the event must be
registered before the SGI Embedded Support Partner performs this action</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>The number of retry times</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the number of times that the SGI Embedded Support Partner
attempts to execute the action before it stops</P>
<p>The value cannot exceed 23; however, it is not recommended that you set it greater than 4. Default = 0</TD>
</TR>
</TABLE>
<a name="setup_action_example"><p>For example: action is to run diagnostic</p></a>
<p><dl><dd>username to execute an action as - nobody
<br>action timeout - 3600 seconds
<br>the number of times that the event must be registered before an action will be taken - 5
<br>the number of retry times - 2
</dd></dl>
This diagnostic will run after the event is registered in the SGI Embedded Support Partner database 5 times.
It will be executed with nobody privileges. If the diagnostic is still running after an hour (3600 seconds),
it will be killed and restarted a second time (retry times = 2).
<A NAME="setup_actions_add"><p><hr></A>
<b>SETUP &gt; Actions &gt; Add</b>
<P>Use this command to add a new action. The following options are available:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Option</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action description</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Provides a description of the action.<p>
Example: page to John Dow</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action command string</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the exact action command to execute.<p>
Example: /usr/bin/espnotify -p 1234567</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Username to execute the action as (default = nobody)</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the user account that the SGI
Embedded Support uses to execute the command.<p>Default = nobody<p>Note: username cannot
be set to "root" nor to any any other account that has root privileges.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Action timeout</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the time period for which the action can run without being killed.</p>
The value that you specify must be a multiple of 5. Default = 600 seconds</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>The number of times an event must be registered before an action will be taken</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies how many times the event must be
registered before the SGI Embedded Support Partner performs this action.<p>
Default = 1</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>The number of retry times</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the number of times that the SGI Embedded Support Partner
attempts to execute the action before it stops</P>
<p>The value cannot exceed 23; however, it is not recommended that you set it greater than 4. Default = 0</p></td>
</TR>
</TABLE>
<p>For example: action is to run diagnostic
<p><dl><dd>username to execute an action as - nobody
<br>action timeout - 3600 seconds
<br>the number of times that the event must be registered before an action will be taken - 5
<br>the number of retry times - 2
</dd></dl>
This diagnostic will run after the event is registered in the SGI Embedded Support Partner database 5 times.
It will be executed with nobody privileges. If the diagnostic is still running after an hour (3600 seconds),
it will be killed and restarted a second time (retry times = 2).
<P>Examples of notification options:</p>
<ul>
<li>/usr/bin/espnotify -E your_email@sgi.com,your_email2@sgi.com -e email_subject (email notification)
<Li>/usr/bin/espnotify -p pager_id (pager notification)
<li>/usr/bin/espnotify -A message_string (display message on the console)
<li>/usr/bin/espnotify -D your_system_name:0.0 -c %D (graphical pop-up window with an event data in it)
</ul>
<p>For more information regarding notification options, refer to the <font face="Courier"><tt>espnotify</tt></font> man page.</p>
<p>The following list includes the accepted user format strings and any action-specific options:</p>
<ul>
<li>%C = event class
<li>%T = event type
<li>%D = event data (this is the data received along with the event.)
<li>%H = host name from which event originated
<li>%S = Event time stamp, time event occured (in seconds since Jan 1 1970)
<li>%F = forwarder hostname (in case of DSM.)
<li>%I = sys id
<li>%t = time string (current)
<li>%s = seconds since Jan 1 1970 (current)
<li>%m = current minute of the hour 0-59 (current)
<li>%M = current month of the year 0-11 (current)
<li>%h = current hour of the day 0-23 (current)
<li>%y = current year (current)
<li>%d = day of the month (current)
</ul>
<p>For example: /usr/bin/espnotify -D system_name.sgi.com:0.0 -c %D</p>
<dl><dd>This displays a window on the machine system_name.sgi.com. The window contains data that is significant to the event.</dd></dl>
<A NAME="setup_actions_delete"><p><hr></A>
<b>SETUP &gt; Actions &gt; Delete</b>
<P>Use this command to delete an action. Choose an action that you want to delete.</p>
<p>Note: The action will be deleted from the SGI Embedded Support Partner database. If this action is
assigned to some events, the list of all affected events is displayed. You have a choice to cancel or proceed with deletion.
Use the <font face="Courier"><TT>Proceed with deletion</TT></font> button to delete the
action and remove the selected action from all events to which it is assigned. Use the <font face="Courier"><TT>Stop
deletion</TT></font> button to abort the deletion and leave the action in the SGI Embedded Support Partner.</p>
<p>If you need to assign a different action to an event, use <a href="#screens_setup_events_update">SETUP &gt; Events &gt; Update</a>
or <a href="#setup_events_update_event_actions">SETUP &gt; Events &gt; Update Event Actions</a>.</p>
<A NAME="setup_notification"><p><hr></a>
<b>SETUP &gt; Paging</b>
<p>Use <font face="Courier"><TT>espnotify</tt></font> action to deliver a text/numeric message to a pager by specifying appropriate
command line options. You may obtain more information on espnotify by using the <font face="Courier"><tt>man espnotify</tt></font>
command.</p>
<p>To work properly, paging has to be configured. The SGI Embedded Support Partner provides the required User Interface to set required
configuration parameters. All the parameters are written to <font face="Courier"><TT>/etc/qpage.cf</tt></font> file.</p>
<p><font face="Courier"><TT>Paging</tt></font> requires that a modem be connected to the system to dial the paging service provider
to deliver a page. The Modem/Admin section enables modem configuration. The Service section enables configuration of the parameters
of the Paging Service Provider(s). Because the service provider normally identifies each individual pager by means of a pager ID
(which does not have to be the pager Touch-tone number), a pager ID must be provided in order to deliver the page. The Pager section
enables you to configure different pagers that are associated with the Service.</p>
<A NAME="setup_notification_viewcurr"><p><hr></A>
<b>SETUP &gt; Paging &gt; View Current Setup</b>
<P>Use this command to display the current values of the paging parameters
and the following types of information:</P>
<UL>
<LI><font face="Courier"><TT>espnotify</TT></font>Administration Variables
<LI>Modem Setup Parameters
<LI>Services Setup Parameters
<LI>Pager Setup Parameters
</UL>
<HR>
<b><A NAME="setup_notification_modem">SETUP &gt; Paging &gt; Modem/admin</A></b>
<P>You can configure the following <font face="Courier"><TT>Modem setup</TT></font> parameters:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Modem name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies a unique name that the SGI Embedded
Support Partner uses to identify a modem. Entering an existing modem name will update the modem name.
No spaces are allowed.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Modem device</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the device to which the modem is
connected (for example, <font face="Courier"><TT>/dev/ttya</TT></font>)</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Modem initialization command</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the command that the SGI Embedded
Support Partner should use to initialize the modem before dialing the Service Provider.
These initialization commands are modem specific and are available in your modem manual.
For example, many paging services require that error correction be turned off on your modem.
For some modems, this can be done by including &amp;A0&amp;K0&amp;M0 in the modem initialization command</TD>
</TR>
</TABLE>
<P>You can configure the following <font face="Courier"><TT>Administration Setup</TT></font> parameters:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Administrator's e-mail address</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the e-mail address of the person to
contact if <font face="Courier"><TT>Paging</TT></font> fails to deliver a pager</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>The time interval for retrying</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the amount of time that the <font face="Courier"><TT>espnotify</TT></font>
should wait between retries</TD>
</TR>
</TABLE>
<A NAME="setup_notification_service"><p><hr></A>
<b>SETUP &gt; Paging &gt; Service</b>
<P>Use this command to set up information about a paging service.</P>
<P>You can configure the following parameters:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Service name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the unique name that the SGI
Embedded Support Partner uses to identify paging service provider. Entering an existing
service name will result update the service name. No spaces are allowed.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Device</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the device (modem name) that the SGI Embedded
Support Partner should use to dial the service provider. Use <a href="#setup_notification_modem">SETUP &gt;
Paging &gt; Modem/Admin</a> to set up any modems.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Maximum number of retries</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the maximum number of times the SGI
Embedded Support Partner should attempt to access this service before it quits trying.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Maximum length of the message</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the maximum number of characters
that can be sent using this service. This depends on your service provider.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Phone number of the paging service</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the IXO/TAP telephone number of the Service Provider.
Do not confuse your pager's Touch-tone telephone number with the service provider's IXO/TAP telephone number. They
are never the same.<p>The telephone number should contain at least 7 numbers and should not include any spaces,
&#034;-&#034;, or other symbols.</td>
</TR>
</TABLE>
<A NAME="setup_notification_pager"><p><hr></A>
<b>SETUP &gt; Paging &gt; Pager</b>
<P>Use this command to set up a specific pager.</P>
<P>You can configure the following parameters:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Pager Name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies a unique name to identify this pager</td>
</TR>
<TR><TD VALIGN="TOP"><TT>Pager ID</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies a unique number (ID) that is used by
paging service provider to identify the pager. The ID can or cannot be the touch-tone phone
number that you dial to access the pager. PLease contact your service provider to get this
information</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Service Name</TT></TD>
<TD VALIGN="TOP"><P><font face="Arial,Helvetica">Specifies the paging service (service name) to which
<font face="Courier"><tt>espnotify</tt></font> should deliver the page for this pager<p> Use the
<a href="#setup_notification_service">SETUP &gt; Paging &gt; Service</a> to set up any paging services
that you want to use</a></td>
</TR>
</TABLE>
<A NAME="setup_availmon"><p><hr></a>
<b>SETUP &gt; Availability Monitoring</b>
<p>The Availability Monitoring is a set of tools that collectivly monitor and report the availability of
system(s) and diagnosis of system crashes. Availability monitoring tools gather information from diagnostic
programs like ICRASH, FRU Analyzer, SYSLOG and identify the cause of system shutdowns. The system configuration
information comes from configmon, hinv and versions. Availability monitoring tools can report data to various locations
based on the Availability MailList setting.
<A NAME="setup_availmon_viewcurr"><p><hr></a>
<b>SETUP &gt; Availability Monitoring &gt; View Current Setup</b>
<P>Use this command to view the current values of the availability monitor parameters. It displays the
following information:</P>
<UL>
<LI>General availability monitoring parameters
<LI>Availability monitoring e-mail list parameters
</UL>
<A NAME="setup_availmon_configuration"><p><hr></a>
<b>SETUP &gt; Availability Monitoring &gt; Configuration</b>
<P>Use this command to set up the <font face="Courier"><TT>availability monitor</TT></font> component of
the SGI Embedded Support Partner.</P>
<P>You can configure the following parameters:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Possible Values</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Automatic e-mail distribution</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Enable or Disable</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies whether <font face="Courier"><TT>availability monitor</TT></font>
should automatically distribute reports by e-mail</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Display of shutdown reason</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Enable or Disable</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies whether <font face="Courier"><TT>availability monitor</TT></font>
should display the reason for a shutdown</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Include HINV information into e-mail</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Yes or No</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies whether <font face="Courier"><TT>availability monitor</TT></font>
should include HINV information in the diagnostic e-mail messages that it generates</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Start uptime daemon</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Yes or No</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies whether <font face="Courier"><TT>availability monitor</TT></font>
should start the uptime daemon</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Number of days between status updates (default = 60)</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">0 - 300</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">This value specifies the number of days after which
a status report should be sent. (<font face="Courier"><TT>Availability monitor</tt></font> with the help of
<font face="Courier"><TT>eventmond</tt></font> sends a status report
periodically if the system is up for an extended period of time.)</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Interval in seconds between uptime check (default = 300 seconds)</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">User specified</TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the number of seconds that <font face="Courier"><TT>event monitor</TT></font>
should wait before it performs an uptime check on the system</TD>
</TR>
</TABLE>
<A NAME="setup_availmon_email"><p><hr></a>
<b>SETUP &gt; Availability Monitor &gt; Availability MailList</b>
<P>Use this command to set up the e-mail lists for availability information reports.</P>
<P>You can set up e-mail lists for the following reports:</P>
<UL>
<LI>Availability report in text format
<LI>Availability report in compressed format
<LI>Availability report in compressed format (encrypted)
<LI>Diagnostic report in text format
<LI>Diagnostic report in compressed format
<LI>Diagnostic report in compressed format (encrypted)
<li>Pager report in concise text form
</UL>
<P>The availability report contains computed system availability metrics.</P>
<P>The diagnostic report includes all of the availability report data and
diagnostic data for troubleshooting.</P>
<a name="setup_system_monitor"><p><hr></a>
<b>SETUP &gt; System Monitoring</b>
<p>System Monitoring is available only for a <b>Group of Systems</b>. It is a facility that is packaged with SGI
Performance Co-Pilot software tools (pcp_eoe). It enables monitoring of selected services on a remote machine from Embedded
Support Partner. In order to monitor a service, a hostname and a command must be provided. This command,
when it is executed on the machine that is running Embedded Support Partner, obtains information about the selected
service on the remote machine.</p>
<p>The System Monitoring facility of Performance Co-Pilot can be configured via the SGI Embedded Support Partner User
Interface. This option is available only if SGI Embedded Support Partner is running as a Group Manager.</p>
<p>Embedded Support Partner User Interface provides 2 different screens for configuring System Monitoring. The Service
section of System Monitoring allows you to add a new service or update an existing service, or delete an existing service. The
Service section provides more details on how these operations can be performed. After a service has been added, you can add
this service to a host by using the Hosts screen of System Monitoring. This action enables monitoring of that particular service
for the host. The Hosts section provides more information on how services can be associated with hosts.</P>
<a name="setup_system_monitor_viewcurr"><P><b>SETUP &gt; System Monitoring &gt; View Current Setup</b></p></a>
<p>Use this command to display the current values of System Monitoring parameters and the following types of
information :
<ul>
<li>Service Setup Parameters
<li>Hosts Setup Parameters
</ul>
<a name="setup_system_monitor_service"><p><hr></a>
<b>SETUP &gt; System Monitoring &gt; Service</b>
<p>Use this command to set up services that need to be monitored by System Monitor.</p>
<p>You can add a Service by using the top section of the screen. You can configure the following Service setup
parameters:</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>New Service Name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies a unique name that System Monitor uses to identify the service</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Command to Execute</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the command to be executed for monitoring this service on the remote
machine. Please note that the command must contain HOST keyword, which is replaced by the actual hostname during execution.<p>
For example, if you want to find out whether a machine is responding to ICMP
requests, you can enter the following command:<dl><dd>/usr/etc/ping -c 3 -f -i 4 HOST</dd></dl>
This service can now be used to monitor any number of hosts that you select from the Hosts screen.</td>
</TR>
</TABLE>
<p>You can update or delete a Service by using the bottom section of the screen.</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Service name</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">You can choose an existing service to update or delete from the list of services provided.</TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Command to Execute</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Specifies the command to be executed for monitoring this service on the remote
machine (see add Service above). This option is applicable only while updating existing service. No
command is required to execute when a service is being deleted.</td>
</TR>
</TABLE>
<p>The default setup comes with the following services:</P>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica">Service Name</B></TD>
<TD><B><font face="Arial,Helvetica">Service Command</B></TD>
<TD><B><font face="Arial,Helvetica">Service Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">icmp</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">/usr/etc/ping -c 3 -f -i 4 HOST</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">ICMP Echo Request</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">dns</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">nslookup - HOST</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">DNS Server</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">x-server</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">DISPLAY=HOST:0 /usr/bin/X11/xhost</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">X Server</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">rpcbind</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">/usr/etc/rpcinfo -p HOST</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">RPC Services</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">smtp</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">( echo "expn root" ; echo quit ) | telnet HOST 25 | cat</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Mail Server</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">nntp</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">( echo "listgroup comp.sys.sgi"; echo quit ) | telnet HOST 119 | cat</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">News Server</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">autofsd</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">/usr/pcp/bin/autofsd-probe -h HOST</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Autofs functionality</TD>
</TR>
<TR><TD VALIGN="TOP"><font face="Arial,Helvetica">pmcd</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">/usr/pcp/bin/pmcd_wait -h HOST</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Performance metrics collector deamon</TD>
</TR>
</table>
<a name="setup_system_monitor_hosts"><p><hr></a>
<b>SETUP &gt; System Monitoring &gt; Hosts</b>
<p>Use this command to set up hosts that need service monitoring by System Monitor.</p>
<p>You can add/update/delete Services for any host by choosing the appropriate options:</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica"><b>Parameter</B></TD>
<TD><B><font face="Arial,Helvetica">Description</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>Host</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">You can choose an existing host from the list of hosts provided. Please note that in order for a
host to appear in this box, it must be Subscribed first. (see Subscribe in Events section).</td>
</tr>
<TR><TD VALIGN="TOP"><TT>Service(s)</TT></TD>
<TD VALIGN="TOP"><font face="Arial,Helvetica">You can choose any number of existing Services provided.
<ul><li>If you select Add after choosing Services, those services will be added to the existing list if not already available
<li>If you select Update after choosing Services, all existing services will be replaced by the selected ones
<Li>If you select Delete after choosing Services, only the selected services will be deleted from the existing list of services
</ul></td>
</tr>
</table>
<a name="setup_performance_viewcurr"><p><hr></a>
<b>SETUP &gt; Performance Monitoring &gt; View Current Setup</b>
<p>All performance rules can be enabled or disabled via user interface.Use this command to display performance rules status.</p>
<p>The report table displays the following information:</p>
<ul>
<li>PMIE Rule Description
<li>PMIE Rule
<li>Status (enabled/disabled)
</ul>
<a name="setup_performance_config"><p><hr></a>
<b>SETUP &gt; Performance Monitoring &gt; Configuration</b>
<p>There is a set of rules available to set up for performance monitoring.</p>
<p>The table below provides a short description for each rule:</p>
<TABLE BORDER="1" WIDTH="100%" cellpadding=4 cellspacing=2>
<TR><TD><B><font face="Arial,Helvetica"><b>PMIE Rule Name</B></TD>
<TD><B><font face="Arial,Helvetica">PMIE Rule Description</B></TD>
<TD><B><font face="Arial,Helvetica">PMIE Rule's Action</B></TD>
</TR>
<TR><TD VALIGN="TOP"><TT>cpu.context_switch</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High aggregate context switch rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Average number of context switches per CPU
per second exceeded threshold over the past sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.excess_fpe</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Possible high floating point exception rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">This predicate attempts to detect processes generating very large
numbers of floating point exceptions (FPEs). Characteristic of
this situation is heavy system time coupled with low system call
rates (exceptions are delivered through the kernel to the process,
taking some system time, but no system call is serviced on the
application's behalf).</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.load_average</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High 1-minute load average</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The current 1-minute load average is higher than the larger of
min_load and ( per_cpu_load times the number of CPUs ).
The load average measures the number of processes that are running,
runnable or soon to be runnable (i.e. in short term sleep).</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.low_util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Low average processor utilization</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The average processor utilization over all CPUs was below threshold
percent during the last sample interval.
This rule is effectively the opposite of cpu.util and is disabled by
default - it is only useful in specialized environments where, for
example, processing is batch oriented and low processor utilization
is indicative of poor use of system resources. In such a situation
the cpu.low_util rule should be enabled, and cpu.util disabled.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.syscall</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High aggregate system call rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Average number of system calls per CPU per second exceeded
threshold over the past sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.system</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Busy executing in system mode</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Over the last sample interval, the average utilization per CPU was
busy percent or more, and the ratio of system time to busy time
exceeded threshold percent.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>cpu.util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High average processor utilization</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The average processor utilization over all CPUs exceeded threshold
percent during the last sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>craylink.node_cb_errs</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">CrayLink checkbit errors on Origin node</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For some Origin 2000 node, at least one checkbit error was
observed on the node (CrayLink) interface and/or the I/O interface in the last sample interval. Use the command
<br><center>$ pminfo -f hinv.map.node</center>
to discover the abbreviated PCP names of the installed nodes and
their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>craylink.router_cb_errs</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">CrayLink checkbit errors on Origin route</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For some CrayLink router port, at least one checkbit error was
observed in the last sample interval. Use the command<br><center>$ pminfo -f hinv.map.routerport</center>
to discover the abbreviated PCP names of the installed router ports
and their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>filesys.buffer_cache</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Low buffer cache read hit ratio</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Some filesystem read activity (at least min_lread Kbytes per
second of logical reads), and the read hit ratio in the buffer
cache is below threshold percent.Note: It is possible for the read hit ratio to be negative
(more phsical reads than logical reads) - this can be as a result of:
<ul><li>XLV striped volumes, where blocks span stripe boundaries
<li>very large files, where the disk controller has to read
blocks indirectly (multiple block reads to find a single
data block result)
<li>file system read-ahead pre-fetching blocks which are not
subsequently read
</ul></td>
</tr>
<TR><TD VALIGN="TOP"><TT>filesys.dnlc_miss</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High directory name cache miss rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">With at least min_lookup directory name cache (DNLC) lookups per
second being performed, threshold percent of lookups result in
cache misses.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>filesys.filling</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">File system is filling up</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Filesystem is at least threshold percent full and the used space
is growing at a rate that would see the file system full within
lead_time.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>memory.exhausted</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Severe demand for real memory</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The system is swapping modified pages out of main memory to the
swap partitions, and has been doing this at the rate of at least
threshold pages swapped out per second for at least pct of the last
10 samples, ie. sustained page out activity.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>memory.swap_low</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Low free swap space</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">There is only threshold percent swap space remaining - the system
may soon run out of virtual memory. Reduce the number and size of
the running programs or add more swap(1) space before it completely
runs out.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>network.buffers</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Serious demand for network buffers</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">During the last sample interval the rate at which processes tried to
acquire network buffers (mbufs) and either failed or were stalled
waiting for a buffer to be freed is greater than threshold times per
second.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>network.tcp_drop_connects</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High ratio of TCP connections dropped</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">There is some TCP connection activity (at least min_close
connections closed per minute) and the ratio of TCP dropped
connections to all closed connections exceeds threshold percent
during the last sample interval. High drop rates indicate either
network congestion (check the packet retransmission rate) or an
application like a Web browser that is prone to terminating TCP
connections prematurely, perhaps due to sluggish response or user
impatience.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>network.tcp_retransmit</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High number of TCP packet retransmissions</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">There is some network output activity (at least 100 TCP packets per
second) and the average ratio of retransmitted TCP packets to output
TCP packets exceeds threshold percent during the last sample
interval.<p> High retransmission rates are suggestive of network congestion, or
long latency between the end-points of the TCP connections.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_cpu.context_switch</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High per CPU context switch rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The number of context switches per second for at least one CPU
exceeded threshold over the past sample interval. This rule only applies to multi-processor systems, for
single-processor systems refer to the cpu.context_switch rule. For Origin 200 and Origin 2000 systems, use the command
<br><center>$ pminfo -f hinv.map.cpu</center> to discover the abbreviated PCP names of the installed CPUs and
their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_cpu.many_util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High number of saturated processors</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The processor utilization for at least pct percent of the CPUs
exceeded threshold percent during the last sample interval. Only applies to multi-processor systems having more than min_cpu_count
processors - for single-processor systems refer to the cpu.util rule, for multi-processor systems with less than min_cpu_count
processors refer to the per_cpu.some_util rule.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_cpu.some_util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High per CPU processor utilization</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The processor utilization for at least one CPU exceeded threshold
percent during the last sample interval. Only applies to multi-processor systems with less than max_cpu_count processors -
for single-processor systems refer to the cpu.util rule, and for multi-processor systems with more than max_cpu_count processors
refer to the cpu.many_util rule. For Origin 200 and Origin 2000 systems, use the command
<br><center>$ pminfo -f hinv.map.cpu</center>to discover the abbreviated PCP names of the installed CPUs and
their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_cpu.syscall</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High per CPU system call rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">The number of system calls per second for at least one CPU
exceeded threshold over the past sample interval. This rule only applies to multi-processor systems, for
single-processor systems refer to the cpu.syscall rule. For Origin 200 and Origin 2000 systems, use the command
<br><center>$ pminfo -f hinv.map.cpu</center>to discover the abbreviated PCP names of the installed CPUs and
their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_cpu.system</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Some CPU busy executing in system mode</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">Over the last sample interval, at least one CPU was active for
busy percent or more, and the ratio of system time to busy time exceeded threshold percent. Only applies to multi-processor
systems, for single-processor systems refer to the cpu.system rule. For Origin 200 and Origin 2000 systems, use the command
<br><center>$ pminfo -f hinv.map.cpu</center>to discover the abbreviated PCP names of the installed CPUs and
their corresponding full names in the <font face="Courier"><tt>/hw</tt></font> file system.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_disk.util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High per spindle disk utilization</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For at least one spindle, disk utilization exceeded threshold
percent during the last sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_netif.collisions</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High collision rate in packet sends</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">More than threshold percent of the packets being sent across an
interface are causing a collision, and packets are being sent across the interface at packet_rate packets per second.
Ethernet interfaces expect a certain number of packet collisions, but a high ratio of collisions to packet sends is indicitive of a
saturated network.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_netif.errors</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High network interface error rate</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For at least one network interface, the error rate exceeded
threshold errors per second during the last sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_netif.packets</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High network interface packet transfers</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For at least one network interface, the average rate of packet
transfers (in and/or out) exceeded the threshold during the last sample interval.<p>
This rule is disabled by default because the per_netif.util rule is more generally useful as it takes into consideration each
network interfaces' reported bandwidth. However, there are some situations in which this value is zero, in which case an absolute
threshold-based rule like this one will make more sense (for this reason it should typically be applied to some network interfaces,
but not others - use the "interfaces" variable to filter this).</td>
</tr>
<TR><TD VALIGN="TOP"><TT>per_netif.util</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">High network interface utilization</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">For at least one network interface, the average transfer rate (in
and/or out) exceeded threshold percent of the peak bandwidth of the
interface during the last sample interval.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>rpc.bad_network</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">RPC network transmission failure</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">More than threshold percent of sent client remote procedure call
(RPC) packets are timing out before the server responds and the
number of timeouts is significantly more than the number of duplicate
packets being received (indicating lost packets).
The networked file system (NFS) utilizes the RPC protocol for its
client-server communication needs. This high failure rate when sending
RPC packets may be due to faulty network hardware or inappropriately
sized NFS packets (packets possibly too large).</td>
</tr>
<TR><TD VALIGN="TOP"><TT>rpc.slow_response</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">RPC server response is slow</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">More than threshold percent of sent client remote procedure call
(RPC) packets are timing out before the server responds and the
number of timeouts is roughly equivalent to the number of duplicate
packets being received.
The network file system (NFS) utilizes the RPC protocol for its
client-server communication needs. This high timeout rate when
sending RPC packets may be because the NFS server is processing
duplicate requests from the clients which were sent after the
original requests timed out.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>espping.response</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">System Group Manager slow service response</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A service being monitored by the SGI Embedded Support Partner Group
Manager has taken more than threshold milliseconds to complete, during the last sample interval. The hosts parameter specifies
hosts running the espping PMDA, not hosts being monitored by this PMDA. The latter are encoded in the "instances" for each
espping PMDA metric - run<br><center>$ pminfo -f espping.cmd</center>to list the instances and values for the espping.cmd metric.</td>
</tr>
<TR><TD VALIGN="TOP"><TT>espping.status</tt></td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">System Group Manager service probe failure</td>
<TD VALIGN="TOP"><font face="Arial,Helvetica">A service being monitored by the SGI Embedded Support Partner Group
Manager has either failed, or not responded within a timeout period (as defined by espping.control.timeout) during the last sample
interval. The hosts parameter specifies hosts running the espping PMDA, not hosts being monitored by this PMDA. The latter are
encoded in the "instances" for each espping PMDA metric - run<br><center>$ pminfo -f espping.cmd</center>to list the instances
and values for the espping.cmd metric.</td>
</tr>
</table>
<p><HR NOSHADE SIZE="3">
</BODY>
</HTML>
View Git Blame Copy Permalink