76
Admin Event Log Tab
The BBG-1090-TRX-MPEG includes an Event Log in non-volatile storage. This event log can
be used for fault-finding, and to check for error conditions. The following information is
included in each BBG-1090-TRX-MPEG event in the log:
•
Date: The calendar date in which the event occurred.
•
Time: The time at which the event occurred.
•
Severity: The severity of the event. The BBG-1090-TRX-MPEG defines three severity
levels:
o
Error: These are events that affect the operation of the device. For example, an
ASI Input losing lock or an IP Input no longer receiving packets. An error will
impact service until addressed.
o
Warning: These are events that may produce visible glitches, but they do not
have a continuous service impact. Examples of warnings are automatic
redundancy switches and ARP renewal failures.
o
Info: These are informational events. All configuration actions are logged with
this severity. When an error is cleared (for example, an ASI Input regains lock),
the event is logged with this severity as well.
•
Subsystem: The subsystem affected by the event. This may be a port, a stream, or the
card itself.
•
Event: This is a textual description of the event.
The BBG-1090-TRX-MPEG does not have a battery-backed real-time clock. It depends on the
frame controller to obtain the current date and time, and the frame controller depends on an
external Network Time Protocol (NTP) server to obtain current date and time. By default, the
BBG-1090-TRX-MPEG will initialize its internal time-of-day clock to January 1, 2010, GMT.
If the frame controller is NTP-synchronized, the BBG-1090-TRX-MPEG will then accept time
from it and set its time-of-day clock accordingly.
In order to configure the frame controller for NTP, open its configuration screen on
Dashboard™, select the Network Tab, and enter the IP address of an available NTP server:
Summary of Contents for BBG-1090-TRX-MPEG
Page 18: ...18...