To achieve this, please follow document: Cisco WLC - Palo Alto Networks config guide. The SNMP Trap must be converted into a Syslog message. Cisco WLC generates SNMP Traps that do contain this information. snmp trapreceiver create WCS 192.168.100. Here is the CLI commands to achieve that. Community Name means SNMP trap receiver name & that does not have any significance like snmp community value. Cisco WLC native Syslog messages do not contain authentication information, so User-ID mappings cannot be derived from them. Also you can configure SNMP trap receiver where WLC can send its snmp trap messages.
Note: Make sure the Syslog listener is on the interface that is expected to reach the device. When pasting the text into the “Syslog Parse Profile” window, make sure to delete all spaces at the end of the string. Note that trailing spaces can cause problems in parsing the syslog message. Some versions of Cisco WLC might be sending a slightly different syslog message than the one mentioned above. A Field Identifier is being used instead of Regex
Cisco wlc delete snmp trap receiver cli how to#
The screenshot below explains how to parse this information and extract the needed details. Shown below is a typical example of a syslog from the wireless controller.
This document describes how to configure User-ID Agent to get User-IP mapping from the Cisco Wireless controller. 4 1 4 1 1 2 2 3 1 1 1 1 0tion+Airport icon 3 dBidBd+2.15 1 defined DSSS and FHSS as possible methods for modulation 4 wireless>AP>802.11 b/g/n > network incorectly configured 7 an information Roming-ESS field, which is added to every message that comes from the WLC 1 the ip address of the controller is used and the CiscoWCSacts as SNMP TRAP receiver 4 a single point of management for multiple.