Event Log

This page lists the most recent events generated by this access point (see Events Log).

This page also gives you the option of enabling a remote "log relay host" to capture all system events and errors in a Kernel Log. (This requires setting up a remote relay host first. See Log Relay Host for Kernel Messages).

Log Relay Host for Kernel Messages

Note	The U.S. Robotics Professional Access Point acquires its date and time information using the network time protocol (NTP). This data is reported in UTC format (also known as Greenwich Mean Time). You need to convert the reported time to your local time. For information on setting the network time protocol, see Enabling the Network Time Protocol Server.

Understanding Remote Logging

Setting Up the Log Relay Host

Enabling or Disabling the Log Relay Host on the Status > Events Page

Understanding Remote Logging

The Kernel Log is a comprehensive list of system events (shown in the System Log) and kernel messages such as error conditions like dropping frames.

You cannot view Kernel Log messages directly from the Administration Web UI for an access point. You must first set up a remote server running a syslog process and acting as a syslog "log relay host" on your network. Then, you can configure the U.S. Robotics Professional Access Point to send its syslog messages to the remote server.

Using a remote server to collect access point syslog messages affords you several benefits. You can:

Aggregate syslog messages from multiple access points

Store a longer history of messages than kept on a single access point

Trigger scripted management operations and alerts

Setting Up the Log Relay Host

To use Kernel Log relaying, you must configure a remote server to receive the syslog messages. This procedure will vary depending on the type of machine you use as the remote log host. Following is an example of how to configure a remote Linux server using the syslog daemon.

The following steps activate the syslog daemon on a Linux server. Make sure you have root user identity for these tasks.

Log on as root to the machine you want to use as your syslog relay host.

The following operations require root user permissions. If you are not already logged on as root, type su at the command line prompt to become root ("super user").

Edit /etc/init.d/sysklogd and add "-r" to the variable SYSLOGD near the top of the file. The line you edit will look like this:

SYSLOGD="-r"

Consult the man pages to get more information on syslogd command options. (Type man syslogd at the command line.)

If you want to send all the messages to a file, edit /etc/syslog.conf.

For example you can add this line to send all messages to a log file called "AP_syslog":

*.* -/tmp/AP_syslog

Consult the man pages to get more information on syslog.conf command options. (Type man syslog.conf at the command line.)

Restart the syslog server by typing the following at the command line prompt:

/etc/init.d/sysklogd restart


Note	The syslog process will default to use port 514. We recommend keeping this default port. However; If you choose to reconfigure the log port, make sure that the port number you assign to syslog is not being used by another process.

Enabling or Disabling the Log Relay Host on the Status > Events Page

To enable and configure Log Relaying on the Status > Events page, set the Log Relay options as described below and then click Update.

If you enabled the Log Relay Host, clicking Update will activate remote logging. The access point will send its kernel messages real-time for display to the remote log server monitor, a specified kernel log file, or other storage, depending on how you configured the Log Relay Host.

If you disabled the Log Relay Host, clicking Update will disable remote logging.

Events Log

The Events Log shows system events on the access point such as stations associating, being authenticated, and other occurrences. The real-time Events Log is always shown on the Status > Events Administration Web UI page for the access point you are monitoring.

Field	Description
Log Relay Host Enabled	Choose to either enable or disable use of the Log Relay Host: Enabled Disabled If you select "Enabled", the Relay Host and Relay Port fields are editable.
Relay Host	Specify the IP Address or DNS name of the Relay Host. Note: If you are using Devicescape Conductor, the Repository Server should receive the syslog messages from all access points. In this case, use the IP address of the Conductor Repository Server as the Relay Host.
Relay Port	Specify the Port number for the syslog process on the Relay Host. The default port is 514.