ap.cisco
- Former user (Deleted)
- Juan Tomás Alonso Nieto (Unlicensed)
Introduction
The tags beginning with ap.cisco identify events generated by access point devices belonging to Cisco.
Valid tags and data tables
The full tag must have 3 levels. The first two are fixed as ap.cisco. The third level identifies the type of events sent.
Technology | Brand | Type |
|---|---|---|
ap | cisco | wlc |
These are the valid tags and corresponding data tables that will receive the parsers' data:
Tag | Data table |
|---|---|
ap.cisco.wlc | ap.cisco.wlc |
How is the data sent to Devo?
Logs generated by Cisco must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rules below:
Relay rule 1 - ap.cisco.wlc
Source Port → Any available port.
Target Tag → ap.cisco.wlc
Select the Sent without syslog tag checkbox.
No 3rd-party mechanism is used. No collector is needed.
Log samples
The following are sample logs sent to each of the ap.cisco data tables. Also, find how the information will be parsed in your data table under each sample log.
ap.cisco.wlc
2015-09-21 14:29:30.334 xxx=172.16.180.1 user.info ap.cisco.wlc: SE130-MM3-WC-KRO002: *spamApTask1: Sep 05 03:17:55.450: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6694 Did not receive heartbeat reply; AP: 00:08:2f:4a:29:90 2015-09-21 14:29:30.334 xxx=172.16.180.1 user.info ap.cisco.wlc: SE130-MM3-WC-KRO002: *spamApTask1: Sep 05 03:17:55.450: #CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:6694 Did not receive heartbeat reply; AP: 00:08:2f:4a:29:90
The parser can handle any letter or symbol before the facility field.
And this is how the log would be parsed:
Field | Value | Type |
|---|---|---|
eventdate |
|
|
hostchain |
|
|
embFacility |
|
|
embLevel |
|
|
tag |
|
|
apName |
|
|
task |
|
|
serverdate |
|
|
facility |
|
|
priority |
|
|
mnemonic |
|
|
message |
|
|
rawSource |
|
|