[an error occurred while processing this directive][an error occurred while processing this directive]

Events and Alarms

View Alarms

On J Series routers only, you can monitor active alarms on the J-Web interface. To view the alarms page click Monitor > Events and Alarms > Alarms. The View Alarms page alerts you about conditions that might prevent the routing platform from operating normally. The page displays information about active alarms, the severity of the alarms, the time at which the alarm began and a brief description for each active alarm. Alternatively you can use the CLI to view alarms on all routers. An alarm indicates that you are running the routing platform in a manner that is not recommended. When you see an alarm, you must check its cause and remedy it.

Alternatively, you can display alarm information by entering the following commands at the J-Web CLI terminal:

  • show chassis alarms
  • show system alarms

All active alarms are displayed on the View Alarms page with detailed description of the alarm. This description provides more information about the probable cause or solution for the condition that caused the alarm (see Sample Task¿Viewing and Filtering Alarms). The description also provides the date and time when the failure was detected.

For more information see Unresolved xref

View Events

To view system log messages that record events occurring on your routing platform, click Monitor>Events and Alarms>View Events. The View Events page is displayed. This page provides an easy method to view the events recorded in the system log (also known as system log messages). By default, the View Events page displays a summary of the most recent 25 events, with severity levels highlighted in different colors.

The View Events page displays system log messages that record events occurring on the routing platform. Events recorded include those of the following types:

  • Routine operations, such as creation of an Open Shortest Path First (OSPF) protocol adjacency or a user login into the configuration database
  • Failure and error conditions, such as failure to access a configuration file or unexpected closure of a connection to a child or peer process
  • Emergency or critical conditions, such as routing platform power-off due to excessive temperature

On the View Events page, you can also use filters to display relevant events. Unresolved xref lists the different filters, their functions, and the associated actions. You can apply any or a combination of the described filters to view the messages that you want to view. After specifying the filter or filters you want, click Search to display the filtered events.

For more information see Unresolved xref.

Published: 2010-04-29

[an error occurred while processing this directive]