Skip to ContentSun and Oracle Channel Sun How to Buy Log In

Site/SunNet/Domain Manager Administration Guide

包含在

Site/SunNet/Domain Manager 2.3 AnswerBook

尋找其他文件

Viewing Reports

6

This chapter discusses:

Viewing alarm reports
Viewing error messages and error reports
Viewing traps
Viewing event reports

SunNet Manager returns four types of reports:

Data report
Event report
Error report
Trap report

The Console groups the last three under the heading of "alarms." You can view a summary of alarm reports for all elements within a given view. To do this, follow these steps:

Make sure there are no glyphs selected in the Console window.
Press MENU on the View button in the Console window and release MENU over Alarms.
You receive a window such as the one shown in Figure 6-1.

Figure 6-1

Note - If both the Console Alarm Report Summary window and a device-specific Alarm Summary window are displayed simultaneously and reports continue to arrive for the device, the "number-of-reports-received" totals for the two windows will differ until the Console Alarm Reports Summary window is next updated (every 30 seconds).

The following subsections describe how to use functions of the Alarm Reports feature, including (but restricted to) functions available through the buttons--Alarm Reports, Show View, and Find--at the bottom of the Alarm Reports Summary window.

6.0.1 Finding a Device

To find a device that is not visible in the window's scrolling list, you can scroll through the list or, more conveniently:

Click SELECT on the Find button.
You receive the window shown in Figure 6-2.

Figure 6-2

In the Device Name field, enter the name of the network element of the report for which you are looking.

Click SELECT on Find.

If a line for a device is present, that line is displayed and highlighted in the Alarm Reports window's scrolling list. If a line for a device is not present, you receive the message "Device name not found" in a popup window.

6.0.2 Switching Views

Through the Alarm Reports Summary window, you can switch views for a specific device. (This function is also available through the View >> Find option in the Console window.) To show the current view for a device and to be able to switch views, do the following:

Select the specific device in the Alarm Reports Summary window's scrolling list.
Click SELECT on the Show View button.
You receive a window such as the one shown below.

Figure 6-3

If a device is in only one view, the Next button in the window above is greyed-out.

If a device is in multiple views, click SELECT on Next to switch from the current view (as displayed in the Console window) to the next view in which the specified device appears.
In this context, "next" means the next view on the list of views as displayed by the Console's Goto menu.

6.0.3 Obtaining Device-specific Alarm Reports

You can view further detail for a specific device. To obtain a device-specific report, use any of the following methods:

Double click on the line for a device in the scrolling list in the Alarm Reports Summary window.
Click SELECT on the line for a device in the scrolling list in the Alarm Reports window, then click SELECT on the Alarm Reports button at the bottom of the window.
Click SELECT on the glyph for a device and invoke View >> Alarm Reports in the Console menu
Invoke Alarm Reports from an element's glyph menu.

Using any of the preceding methods, you then receive an Alarm Reports window for the specified device, as shown in Figure 6-4.

Figure 6-4

6.0.4 Device-specific Alarm Reports Window

A device-specific Alarm Reports window allows you to:

Sort alarm reports
Filter reports
Find reports associated with a specific agent
Save reports to a file
Print reports

These functions are available through the View, Save, and Print buttons at the bottom of the Alarm Reports window. The functions are described in detail in "Part 2: Reference."

6.0.4.1 Filtering Alarm Reports

Press MENU in the View button, to receive the following menu;

Figure 6-5

Release MENU over Filter to receive the following window:

Figure 6-6

Your selections in the Filter window determine which types of reports are displayed in the device-specific Alarm Reports window. The default is that all alarm reports are displayed. Priority choices apply only to Event Reports.

Click on Apply, your choices take effect immediately.
Click on Reset to restore the choices to the way they were when you opened the Filter window.

Note - If you plan to both sort (described below) and filter your device-specific alarm reports, you must sort before filtering. If you want to sort again, after filtering, you must click SELECT on Reset, then Apply, in the Filter window, sort again, as described below, then reinvoke Filter.

6.0.4.2 Sorting Alarm Reports

In a device-specific Alarm Reports window, press MENU on View >> Sort By. You receive the following menu:

Figure 6-7

Release MENU over the sorting method you want. Your selection takes effect immediately. The choices are mutually exclusive.

The sorting choices are:

Time Stamp: The default. Reports are sorted in chronological order with the most recent appearing last on the list.

Priority: high priority reports are listed first. Use this option if you are filtering out trap and error reports. If you are not filtering out reports and you specify sorting by priority, event reports are listed first, followed by error reports, then trap reports.

Type: Reports are sorted by type, in the order: event, error, trap. Note that alarm reports received after you specify sorting by type, are appended to the appropriate list of reports, depending on the type of the new reports.

Note - When sorting alarm reports, only the reports currently displayed in the Alarm Reports window are sorted. All new reports received during the sorting operation are appended to the end of the sorted list.

6.0.4.3 Finding Agent-specific Alarm Reports

You can search on an agent name to find instance(s) of event reports originating with that agent. To do this, in the device-specific Alarm Reports window, press MENU on View >> Find and release MENU to receive the window shown in the Figure below.

Figure 6-8

In the Agent Name field, enter the agent and group name--not just the agent name. For example, specify hostperf.data, not just hostperf. When you click SELECT on Find, the window displays the contents of the first (oldest) report originating with the agent you specified. If there is no report originating with the agent you specify, you receive the message, "Agent name not found."

6.0.4.4 Saving Device-specific Alarm Reports

SunNet Manager allows you to save device-specific alarm reports to a file. To do this, in the device-specific Alarm Reports window, click SELECT on Save. You receive a window such as the one in Figure 6-9.

Figure 6-9

If the directory first displayed is not the directory you want, change directories by clicking SELECT on folder icons or the. (level above) symbol. Alternatively, you can enter a pathname in the Name field and click SELECT on Save. If the path you enter ends in a valid directory, you are switched to that directory.

When you reach the directory you want, enter the name of the file to which the report will be written.

6.0.4.5 Printing Device-specific Alarm Reports

SunNet Manager allows you to print device-specific alarm reports. Click SELECT on the Print button on the bottom of the device-specific Alarm Reports window, or press MENU on Print >> Report and release MENU. SunNet Manager sends the currently displayed alarm report to your default printer.

6.1 Viewing Error Messages and Error Reports

The Console displays error messages in several locations:

Footer of the Console window. These are generally brief messages about the status of an operation and are temporary. They are overwritten by subsequent status messages. Because of the brevity of these messages, you are usually directed to the Error Reports window for more information.

Figure 6-10

Footer of the Console pop-up windows or a tool (Results Browser, Grapher, Set Tool) window.
These messages are described in the Site/SunNet/Domain Manager Troubleshooting Guide.

Figure 6-11

Error Reports window. Errors detected by the Console and errors returned by agents are displayed in this window. These messages are described in Site/SunNet/Domain Manager Troubleshooting Guide and in the man page for the agent.
To view the Error Reports window:

Move the mouse pointer over the View button and press MENU to open the View menu.
Drag the mouse pointer down to Error Reports and release MENU.
You receive a sample error reports window similar to the one below:

Figure 6-12

To examine error reports for a particular system, type in the device name after the Device prompt and press Return.
To see entries for all elements again, press Ctrl-U to clear the Device line and press Return.
To save the error reports to a file, press MENU in the output portion of the Error Reports window and release MENU over File >> Save or File >> Store as New File. In the window you then receive, select or enter a directory and enter a file name. Click SELECT on the Save button.
To browse through entries in the log:

Press SELECT on the slider and drag the slider to the left or right.
Click SELECT to the left or right of the slider.
Click SELECT on either end of the slider bar.
Enter the number of a report on the Report line and press Return.

6.1.1 Useful Notes about Types of Errors

Two types of agent errors are returned to the Console. Agent-specific errors are errors defined in the agent schema file--these error messages are described in the man pages for each agent. There are also "generic" errors, such as "unknown host" or "no threshold value"--these errors are described in the Site/SunNet/Domain Manager Troubleshooting Guide.

Agent errors can also be classified as "fatal" or "warning." All generic errors are fatal errors. Agent-specific errors can be either fatal or warning. Fatal errors cause the agent to stop servicing the request. Warnings are for your information only; the agent will continue to return reports.

The Errors category of the Console Properties window allows you to specify signal options and any operations to be started when the Console receives an error from an agent. The default Errors category settings cause the glyph for the target element to be dimmed only if a fatal error is reported for the element. The glyph effect is not propagated. You can change the Errors category settings--for more information, refer to "Part 2: Reference."

Fatal errors reported by agents, whether agent-specific or generic, are considered in the Console as high-priority errors. The Console treats warnings as low-priority errors. Thus, if you specify Color by Priority in the Glyph Effect setting for the Errors category in the Console Properties window, fatal errors will change an element glyph to red, and warnings will change an element glyph to yellow, or to colors you have customized.

By default, a maximum of 100 error reports are displayed in the Error Reports window. You can change the maximum number in the Console Properties window. See the description of the Maximum Error Reports setting in "Part 2: Reference."

6.2 Viewing Traps

A trap is an unsolicited report sent from an agent that usually signifies some unexpected error condition. Trap reports are displayed in the Event/Trap Reports window.

When a trap is generated, a trap report stating the cause of the trap is returned to the Console. The report is stored in the event.log file and may be viewed using the following steps.

In the Console window, press MENU in View >> Event/Trap Reports and release MENU.
You receive an Event/Traps Reports window similar to the one below.

Figure 6-13

To examine trap reports for a particular system, type in the device name after the Device prompt and press Return.
To see entries for all elements again, press Ctrl-U to clear the Device line and press Return.
An alternative way to obtain an element-specific trap reports is to click SELECT on the glyph in the Console window, then invoke View >> Event/Trap Reports.

To save the Event/Trap Reports to a file, click SELECT on the Save button.
A pop-up Save window appears, where you can enter the path and file name where the event/trap reports are to be stored.
To browse through entries in the log:

Press SELECT on the slider and drag the slider to the left or right.
Click SELECT to the left or right of the slider.
Click SELECT on either end of the slider bar.
Enter the number of a report on the Report line and press Return.

6.2.1 Useful Notes about Report Settings and Display

The Trap Information settings in the Events and Traps category of the Console Properties window allow you to specify signal options and any operations to be started when the Console receives a trap. The default Events and Traps category settings cause the glyph for the target element to blink only if a trap is reported for the element. By default, the glyph effect is propagated. If the Console window is closed to an icon, you can specify that it be opened automatically if an event or trap is received. To view or change event- and trap-related settings, click SELECT on Props in the Console's control area, then select Events and Traps in the Category pulldown menu. For more information on changing Trap Information settings, refer on the Console's Properties window in "Part 2: Reference."

Trap reports are generated when elements are added, changed, or deleted in the runtime database. By default, these traps are ignored by the Console. If you want to have these traps displayed, toggle the check mark off in the Ignore Database Traps setting for the Events and Traps category. If a glyph effect is specified for traps, the glyph representing the system on which the runtime database is located is affected.

Note - When you create an element with the Ignore-Database-Traps option turned off in the Console's Props >> Events and Traps window, the trap report for that element says that the element was "created." An analogous operation using the database API returns the word "added" rather than "created."

6.2.2 Priority Settings for Traps

Traps can be high, medium, or low priority. Starting with version 2.3 of SunNet Manager, you can determine priority level for any SNMP trap (low, medium or high). Enter your choice into the trap configuration file, snmp.traps after the trap description field. See Chapter 8, "Managing SNMP Devices" for information on how to set SNMP trap priorities. Traps generated by changes to the runtime database are considered low-priority.

If you specify Color by Priority in the Glyph Effect setting for the Events and Traps category in the Console Properties window, SNMP traps will change an element glyph to the default color of red, or to the color you have customized. Database traps will change an element glyph to the default color of yellow or to the color you have customized. For more information about customizing Color by Priority, see "Part 2: Reference."

By default, a maximum of 1000 trap reports are displayed in the Event/Trap Reports window. You can change this maximum number in the Console Properties window. See the description of the Maximum Trap Reports setting in "Part 2: Reference."

包含在