Operation Manual

106
Admin Event Log Tab
The B264 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 B264
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 B264 defines three severity levels:
o Error: These are events that affect the operation of the device. For example, an
encoder losing video input. 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. One example is the ARP renewal failure.
o Info: These are informational events. All configuration actions are logged with
this severity. When an error is cleared (for example, a Video 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. Some events are self-explanatory, and
some are intended for Niagara Video support staff. Please contact Niagara Video if you
need clarification on any event logged by this unit.
None of the B264 models have a battery-backed real-time clock, so they depend on external time
servers to synchronize to the current time. By default, the B264 will initialize its internal time-
of-day clock to January 1, 2010, GMT and synchronize with a time server if available.
The B264 openGear card 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. 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:
Select This
Configure