In case you need to physically locate and access point that is controlled by a WLC you can do so by making the LED status light blink on demand.

You will first need to enable debug mode on the AP to enable the controller to send commands to it from its CLI

debug ap enable your_access_point_name

NOTE:The output of these commands is sent only to the controller console, regardless of whether the commands were entered on the console or in a TELNET/SSH CLI session.

To make a specific access point to flash its LEDs for a specified number of seconds, enter this command:

debug ap command "led flash seconds" your_access_point_name

You can enter a value between 1 and 3600 seconds for the seconds parameter.

To disable LED flashing for a specific access point, enter this command:

debug ap command "led flash disable" your_access_point_name

You can disable debug mode once you’ve located you AP by using this command or simply close your ssh session

debug ap disable your_access_point_name

[source:CISCO WLC Config Guide]

 

You can log off a Cisco ASA VPN session from the command line as follows

Find the users session index

show vpn-sessiondb | include (username)

The index field is what you’re looking for. Once you have this you can log that particular session off by using the following command.

vpn-sessiondb logoff index XXXX

where XXXX is the index number.

 

Here’s how you can quickly list the currently active IPSec VPN sessions on your ASA.

show vpn-sessiondb remote

You can of course use modifiers to filter only the text you’re interested in. For example

show vpn-sessiondb remote | include (Username|Duration)

This will give you the username and duration of the session.

You can also get a summary of all the connections as follows

show vpn-sessiondb summary

 

Generally GBICs have been open so you can use any brand. Cisco equipment won’t accept “just any vendor’s” compatible SFPs. I found this out the hard way last year trying to save some money when I purchased a couple of OEM SFP transceivers from Dell to use in a Cisco switch. Plugging in the SFP module would disable the port. The switch’s firmware supposedly checks the identifying data in the SFP’s internal Flash memory, and if it isn’t built by Cisco, the switch refuses to enable that slot. It’s not only Cisco that does this. Other vendors like Extreme Networks and 3Com are also reported to do the same.

I had to to give in and purchase a $300+ Cisco branded SFP from CDW to use with this switch. Fortunately, there is a way to disable this check in the switch depending on the IOS version installed on the switch.

Issuing the following commands will allow for unsupported SFPs and wont disable the port.

switch(config)#service unsupported-transciever
switch(config)#no errdisable detect cause gbic-invalid

You will be presented with a warning after the first command with something to the effect that if you experience any problems with the switch, Cisco may deny support if the cause is determined to be the ‘unsupported’ SFP.

© 2012 !NSFW Suffusion theme by Sayontan Sinha