White Papers - Open NerveCenter: Downstream Alarm Suppression - Testing the Model - Running Node Availability Reports -
Previous: Testing the Alarm Suppression Model     Next: Understanding the Technical Details

Running Node Availability Reports

If you turned on the alarms that log transition data, you can run node availability reports against that data.


Note    Currently, these reports are available for NerveCenter Servers running on Windows  NT only. Also, you must have imported the model and turned the correct alarms on: DwnStrmIcmpStatus_LogToDB and DwnStrmSnmpStatus_LogToDB.


MetaView no longer ships with Open NerveCenter because of Y2K issues. If you are running NerveCenter on UNIX, you can export your data to Windows  NT and run the reports there using Crystal Reports or another ODBC-compliant reporting tool, or use another third-party reporting utility on UNIX.

 
  To run the node availability reports:

1.      report.gifFrom the Admin menu in the NerveCenter Client, select Report List.

The Report List dialog box is displayed.

  1. Select New.

The Add Report dialog box is displayed.

Add Report Dialog Box

addreport.gif

Click the thumbnail above to view full-sized image.

 

  1. In the Report Select List, select one of the following reports:
  2. In the Report Name field, type a name for your report (optional).
  3. In the Report Author field, type your name (optional).
  4. In the Description field, type any information that will help you or others understand the report or why it was generated (optional).
  5. Select the Override Server Name in Report checkbox.
  6. Select OK.

The report is added to the report list.

  1. Select the report, and then select Run.

The report is generated and displayed. The following report is an example of the availstat.rpt report.

availstat.rpt Report

nc36_report_availstat_html.gif

Click the thumbnail above to view full-sized image.

 

See Monitoring Your Network for more details about running and viewing reports.


Previous: Testing the Alarm Suppression Model

Next: Understanding the Technical Details

Please send comments or corrections to Information Development
This file was last updated on 10 October © 2002