Guest

Cisco 4100 Series Wireless LAN Controllers

Syslog Server Configuration on Wireless LAN Controllers (WLCs)

Document ID: 107252

Updated: May 28, 2008

   Print

Introduction

This document explains how to configure the Wireless LAN Controller for syslog servers.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • Knowledge of how to configure the Wireless LAN Controller (WLC) and Lightweight Access Point (LAP) for basic operation

  • Basic knowledge of Lightweight Access Point Protocol (LWAPP)

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco 2000 / 2100 / 4400 Series WLC that runs firmware 5.0

  • LWAPP-based access points, Series 1230, 1240, 1130, 10x0, and 1500

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Syslog Server Support on Wireless LAN Controllers (WLCs)

In all WLC versions prior to Version 5.0, only one syslog server can be configured. In order to configure the syslog server with the CLI, enter this command from the WLC CLI:

config syslog {ip-address}

Send Syslog Events to Multiple Servers

In controller software release 5.0.148.0, you can enable the controller to log system events to up to three remote syslog servers. The controller sends a copy of each syslog message as it is logged to each syslog server configured on the controller. Because it is able to send the syslog messages to multiple servers, it ensures that the messages are not lost due to the temporary unavailability of one syslog server.

This type of configuration helps in these situations:

  • One of the configured syslog servers is not available.

  • Multiple administrator groups can monitor different message types.

  • Large deployments can want syslog messages sent to servers across different time-zones for extended visibility.

    Note: Syslog messages are sent on UDP Port 514; additional server configuration can require a relaxation of firewall rules.

With Wireless LAN Controller Release 5.0, a new CLI has been introduced to configure syslog servers with the CLI. The old command has been deprecated.

config logging syslog host {host_IP_address} 

WLC-Syslog-Server-1.gif

In order to set the facility for outbound syslog messages to the remote host, use the config logging syslog facility command.

config logging syslog facility {facility_code} 

WLC-Syslog-Server-3.gif

In order to set the severity level to filter syslog messages to the remote host, use the config logging syslog level command.

config logging syslog level {severity_level} 

WLC-Syslog-Server-4.gif

In order to remove a remote host that was configured to send syslog messages, enter this command:

config logging syslog host host_IP_address delete

As mentioned earlier, a maximum of three servers can be configured. When multiple syslog servers are configured, a copy of each syslog message is sent to all configured syslog servers.

In order to configure the WLC for syslog servers with the GUI, complete these steps from the Wireless LAN Controller GUI.

  1. Choose MANAGEMENT > Logs > Config to navigate to this page.

  2. Enter the syslog server IP address and click Add.

  3. Under Syslog Level, set the severity level to filter syslog messages to the syslog servers.

  4. Under Syslog Facility, set the facility for outbound syslog messages to the syslog servers.

  5. Click Apply.

This is an example.

WLC-Syslog-Server-2.gif

Verify

In order to verify the syslog configuration, use the show logging command from the controller CLI. This is an example.

(Cisco Controller) > show logging 
- Number of remote syslog hosts.................. 3
  - Host 0....................................... 2.2.2.2
  - Host 1....................................... 3.3.3.3
  - Host 2....................................... 4.4.4.4

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Related Information

Updated: May 28, 2008
Document ID: 107252