nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Config Change Report - WLan Controller

rcahill

Having tried various methods to reduce the amount of data in my daily config change report I have been unsuccessful in eliminating the normal noise from our Cisco WLan Controllers. I can not seem to elimate the Channel data.

Unfortuantely the web interface does not display the information properly.

Channel 1.. -98 dBm Channel 1.. -97 dBm

There are a number of (.) between the Channel (n) and dBm data as the graphic indicates. Having a number of LWAP this results in a very long report. How may I eliminate the Channel (n) .... data?

WLan.jpg

Find more posts tagged with

Accepted answers

All comments

chris.lapoint

Have you tried adding an exclusion regex in the comparison criteria (File > Settings > Comparison Criteria)?

rcahill

I've used the Exclusion comparison criteria options for other configurations. This one does not want to exclude.

chris.lapoint

Can you post the regex you are using for the exclusions?

ecornwell

Are you getting the information you're looking for? It looks like the info you're getting is from a "show run-config" not from a "show running-config"

We back up our WLC's using the "show running-config" because that's what we'd be able to paste back into the devices if they ever failed. The run-config command just shows you a nice version of how it's configured.

I did some looking and the "show running-config" command doesn't seem to have any information about the AP's in it though.

ecornwell

After doing some more research, it doesn't seem like that option is a good option either. The run-config command seems to show all the config in a nice fashion and the running-config shows some basic settings but neither provides a way to restore the device. Here's something I found on the netpro forums when someone asked about doing a cli backup.

1)log on to controller cli.
2)enter transfer upload datatype config
3)if u want to encrypt do following
a)enter transfer encrypt enable
b)enter transfer encrypt set-key<key>
4)enter transfer upload serverip <tftp server ip address>
5)enter transfer upload path<path>
6)enter transfer upload filename<filename>
7)enter transfer upload start
8)To confirm give "y".

That still does a tftp to do the backup and isn't any good from a RTCD standpoint...

rcahill

I tried this as a manual process a while ago and couldn't figure out the file format. After your noe I did try again and reviewed Cisco's website to see if there were any leads and nothing.

I never thought to try this through Cirrus, soley because the application can not seem to automate a series of command lines and the issue above. I tried doing a series of commands for another switch type and it was a no go.

The run-config is the closest thing I can figure out to approximate the existing configuration. But as you noted it is not a replacement config. The replacement config file should be in our wcs_tftp directory. I need or I guess want something I can read and know that I can recover from. Even if manually.

Also since there may be "many hands in the pot" I want a change report, because some admins will not admit to an oops.

ecornwell

We have a similar situation here and I'd like to get good reports. Are you happy with the change reports that you are getting minus what you mentioned above? We use WCS as well and I'm guessing we'll just have to use that for backups and NCM for change reports.