Logging; General Syslog Information - Proxim Orinoco AP-2500 User Manual

Public Space Parameters
e. Repeat the above procedure for the Secondary Server parameters if you have a back-up RADIUS
server.
5. Configure the Retransmission Options.
• Select a Retransmission Method. This option is only valid if you have configured settings for a
Secondary Server.
— Failover: The AP makes multiple attempts to reach the Primary Server. If the Primary Server fails to
respond (after the specified number of Retransmission Attempts), the AP falls over to the Secondary
Server.
— Round-Robin: The AP first attempts to reach the Primary Server. If the Primary Server fails to
respond, the AP tries the Secondary Server. If the Secondary Server fails to respond, the AP again
tries the Primary Server.
• Enter the number of retransmission attempts (per server) in the Retransmission Attempts field.
• Enter the number of seconds between retransmission attempts in the Retransmission Frequency field.

Logging

You can configure the AP-2500 to send system events and/or AAA events to network servers using the Syslog
protocol. You can specify a single server to receive both types of messages or you can specify a different server for
each message type.

General Syslog Information

• The Syslog message format is defined in RFC 3164 (see http://www.rfc-editor.org/).
• The AP transmits Syslog messages to the specified server(s) using the well-known UDP Syslog port (514).
• If Syslog is enabled, the AP sends a Syslog heartbeat every 60 seconds, and the Syslog heartbeat message
contains the AP's Ethernet MAC address.
• You need a Syslog server program running on a network computer to receive Syslog messages from the AP.
– Kiwi Enterprises has a freeware Syslog Daemon for Windows operating systems. You can download the
program at http://www.kiwisyslog.com/.
• Syslog Events are logged according to the level of detail specified by the administrator. Logging only urgent
system messages will create a far smaller, more easily read log then a log of every event the system encounters.
Determine which events to log by selecting a priority defined by the following scale:
Event Priority
LOG_EMERG
LOG_ALERT
LOG_CRIT
LOG_ERR
LOG_WARNING
LOG_NOTICE
LOG_INFO
LOG_DEBUG
Description
0 system is unusable
1 action must be taken immediately
2 critical conditions
3 error conditions
4 warning conditions
5 normal but significant condition
6 informational
7 debug-level messages
136