WLSE 2.13, WDS, SNMP Unreachable

I just reconfigured one AP to be the WDS infrastructure device, now WLSE tells me it's SNMP unreachable. I copied the config from the backup WDS which is fine SNMP wise. I can get the SNMP table with the WLSE, discovery works fine, but WLSE still reports it as down. It is working fine as WDS, with 58 devices registered to it and Security Keys Set. I went from IOS 12.3(7)JA to 12.3(8) to 12.3(7)JA3. Also, I noticed I can't import images from Cisco.com any more with 2.13?

This may help with the import:
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Security%20and%20Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddaf642

Similar Messages

WLSE Express 2.13 SNMP unreachable

Hi,
Has anyone had trouble with SNMP querying Aironet access points with WLSE Express 2.13? Everything was fine with version 2.12 - I could SNMP query and SNMP discover all my access points. After upgrading the WLSE Express to 2.13, I have a few access points that are now SNMP unreachable. I can reach some APs and other APs are SNMP unreachable. The configurations of all the APs are standardized - all lines pertaining to SNMP are the same.
Any clues or tips? Is this a bug with version 2.13?

What do the SNMP Reachable Test in WLSE come back with for the APs in question?.

WLSE & SNMP unreachable fault

Hello,
I configured my WLSE to check if my AP (AP1231 and AP1131) are SNMP reachable once every ten minutes. I want to have an fault only when SNMP reachability is down for 3 consecutive polling cycles = if an AP is down for 20min
Actually, I get a fault as of the first time wlse polls the access point.
Anyone knows why wlse reacts like that ?
Thank you
Regards

Actually, I checked my configuration and I saw that during the upgrade from 2.12 to 2.13 the fault profiles I configured was not upgrade :
For example we don't have the same name for the SNMP reachable fault :
MO Names | Policy Names
wlse2.12 : AccessPoint | SNMPReachable
WLSE2.13 : IOSAccessPoint | SNMPReachable
It seems that I have to create a new profile...
Anyone has the same trouble when upgrading 2.12 to 2.13 ?
Thx

WLSE manage AP using SNMP through xDSL line with an NAT router

Hi,
This is the deployment architecture that I had :
WLSE (Internet public add)--->xDSL----->NAT router---->BBSM--->APs
I had a problem in managing the APs which the ip address will be translated to a public ip addresses. When I use discovery options from my WLSE, it does not find any AP. I enable the CDP on my router and APs. There is only 1 ssid on all my APs.
Is it possible to manage the APs using snmp using this model?
regards,
Sam

Since you have NAT in between the WLSE and the APs, this will not work. SNMP does not work over NAT. To test this, try using the SNMP Reachable Tool under Administration->Connectivity Tools. enter the ip address and click on SNMP Reachable, you'll see that it will time out.

WLSE Configuration archive download SNMP timeout

HI, I´m new to WLSE. My AP´s are already discovered and managed, but when I try to download the configuration archive from them, the Job Always fail with a SNMP timeout error message. This problem occur in the upgrade firmware job too.
Whe I go to reports, device center, I can see the AP configuration, but in the configuration>archives>view archive I have nothing.
I appreciate your help

You can configure the timeout value by selecting Firmware > Advanced Parameters. From this option you can change the "Per device job operation timeout value" to a higher value

WLSE doesn't seem to notice it when an Aironet device goes down

WLSE type: 1105, version 2.7
Aironet 1100 devices (267 pieces), IOS 12.2(13)JA4
After the upgrade from version 2.6 to 2.7 we have a problem with the WLSE. Device discoveries and inventories run without a problem, but whenever a device goes down the WLSE doesn't seem to notice.
With a sniffer we found the WLSE's polling the device, but there's no follow-up when there's no reply. As a result the device stays green.
All configurations are the same with the exeption of one location. Here we've configured the WDS and this is the only location on which the WLSE reacts in the correct way.
On several other locations there might be one or two devices on which the WLSE reacts correctly, but these are exeptions. We have compared configuration files, but can't find any differences between the devices.
Whenever the WLSE does discover a failing device (with no WDS configured) it generates a P1 severity fault (default was P2).
In case these devices have become reachable again the P1 severity fault is automatically acknowledged and remains this way. So far I haven't been able to clear these faults and therefor the device will keep it's alert status in the reportview.
I do hope somebody has some idea about what's going on.
After I encountered these problems after the upgrade I've started from scratch and used a clean installation of version 2.7. and a new discovery of our network.
I really don't know what went wrong. Anybody with any suggestions is very welcome to vent them.
Thanks for your help,
Corine

I'm having a similar issue. 500+ AP1200 units, IOS 15JA, newest WLSE version. Most of the time when a unit goes down, it will generate a SNMP unreachable fault message, and we are set to have the WLSE send an email in the event of a SNMP unreachable. That's great. Except once in awhile, it won't generate the fault. The device could be powered completely down for three or four days, and I'd never get a fault message. It's driving me nuts. All these AP's are configured the same using the exact same template, with only the IP info changed.

Unable to discover AP350 using WLSE

Hi,
I am using WLSE 1.3 and using AP350 12.01T. It always give me snmp unreachable. unable to read cdp cache. What can be the problem. I put the seed device as the switch that is connected to the AP and the device credential is the AP that I am going to discovered. Any other settings?
Thanks.

Have you got SNMP correctly configured on the AP ?? you using the correct snmp community names

I can't get my wlse to discover anything...

originally i had wlse 1.3.1 and 1220s, 340s, and 350s. i got the wlse to discover all of the ap's and i was a happy man.
now i have upgraded my 1220s to IOS. the 340s and 350s haven't changed. and i upgraded the wlse to 2.0. now i can't discover anything. i get snmp unreachable to everything i try as a seed device. i have set the snmp strings correctly.
what is going on?
thanks
--ryan

It's in the on-line help. Misconfigured Devices group contains IOS APs that do not have an ISO view configured on them. You can create this from the device CLI or using WLSE. Doing this via CLI need the commands in the order listed:
snmp-server view iso iso included
snmp-server community view iso RO
snmp-server community RW
Devices that do not have an ISO view will be placed in the Misconfigured Devices system group after discovery and fault will be generated. The fault refers to a dot11mib problem.

Scanning not working b/c ICMP or SNMP is blocked?

I'm having a terrible time getting scanning over the network functioning on 10.6.1 with my Brother printer/scanner. (Printing works fine.)
Because scanning works over USB, I suspected something was being blocked by the Mac. I turned of the firewall and still no luck. So I ran TCPDUMP and it looks like ICMP and/or SNMP is being blocked. This is what I get when initiating a request to the scanner:
18:00:40.845716 IP macbook.suthoff.com.64048 > brother.suthoff.com.snmp: C=internal GetRequest(45) system.sysName.0 E:2435.2.3.9.1.1.7.0
18:00:40.848540 IP brother.suthoff.com > macbook.suthoff.com: ICMP brother.suthoff.com udp port snmp unreachable, length 36
18:00:42.846122 IP macbook.suthoff.com.57266 > brother.suthoff.com.snmp: C=internal GetRequest(45) system.sysName.0 E:2435.2.3.9.1.1.7.0
18:00:42.848749 IP brother.suthoff.com > macbook.suthoff.com: ICMP brother.suthoff.com udp port snmp unreachable, length 36
Anyone else experiencing this? Tips? Suggestions?

Then I would contact Brother tech support. I would also check for any updated drivers for your model. I went through this with a non-network model that bugged me badly until I traded emails with Brother tech support. It can take some research to find out what Brother models will and will not play nice with OS X. Contact their tech support. It sometimes took a couple of days to get a reply, but they did reply. Check their support web site for drivers in case new ones have been posted. Most printer manufacturers are playing catchup with SL. If you do have the most current drivers, then try uninstalling what you have, delete the printer in Print & Fax. reinstall the software an re-add the printer as well as configuring the Brother software to use the appropriate network connection - USB or Ethernet as I recall. Since the Brother model I have isn't a network model I don't know how the network configuration goes. Sorry.

WLSE states no measurement report received on AP scan

I have a netwok with 1240's with fw 123-8ja2 WLSE:2.13
30 AP's
All AP's are registred to the WDS. The WLSE properly authenticated to the WDS (setting registry keys). All AP's are managed by the WLSE. Radio management is switched on on all AP's.
When I do a AP radio scan (or walkabout) i get "no measurement report received". from every AP in that scan on almost every power step. Sometimes, a Power step completes OK.
Has anyone seen this before, and what is causing this?
I've added a screenshot of the WLSE

News :)
Cisco released IOS 12.3-8JEA1 which has the following in the release notes:
CSCsg91315?WDS do return reportS to WLSE without problems
And this bug is:
Symptom:During a WLSE radio scan, Infrastructure APs will fail internittently; sometimes not sending appropriate reports to the WLSE from the WDS. When the reports are missing, the WLSE is unable to complete the task and WLSE fails the job.
Conditions:AP 1100 series, 12.3(8)JEA code, WLSE 2.13
Workaround:Deleting the device from WLSE inventory and rediscovering makes the job run successfully, but only temporarily; after a period of time (less than a day) the jobs will begin failing again.
Further Problem Description:When the AP addresses are hashed in memory, some addresses hash to the same value. When two APs have the same hash vallue, one of them is dropped. This also affects the ability to run Assisted Config jobs.
I'm not shure if this really fixes it, but it sounds good at least :)
Anybody going to try out?
Sadly the current WSLE doesn't show this image as supported :(
Patrick

ACS Authentication Errors

Friday I upgraded my CiscoSecure ACS from version 3.3 to 4.1. Upgrade seemed to go fine. Today I come in to find out that no one is getting authenticated. I have APs in WLSE configed with WDS that are not authenticating. I also have AP's not in WLSE that are not authenticating. All these worked before the upgrade.
Any ideas??
Thanks,
Becky

Yes. I was getting Radius Server not responding. BUT, I just got it fixed!!! During the upgrade ACS wiped out the IP address of the AAA server. Once I re-entered it, things starting coming back up.
Thanks to everyone who thought about this!!
Becky

Airport WLAN implementation for the BRS system.

I am setting up a wireless network for an airport an the implementation is like this: The airport HQ is 2km from the airport. The two enterprise networks are connected via a 2mbs E1 link backed up by an 11mbs wireless link. The data centre is in the airport HQ where there are 2 6509 switches. The wireless network to be impplemented is for a BRS on the airport side. I am planning to use the cisco SWAN solution where i put two WLSMs in the 6509 switches, wlse and cisco acs in the datacenter.In this case the wlsm will be running the WDS. The problem is incase the primary link and the backup link fails. Now can i implement another AP based WDS on one of the APs at the airport side in failover mode such that if the link fails the AP can take over; run WDS and authenticate users. Is this possible and how can it be done?

Make sure you have configured the WLSE to authenticate with WDS devices.
In the WLSE User Interface (WLSE UI), you can give the credentials under Devices > Discover > Device Credentials > Wireless LAN Context Control Protocol (WLCCP) Credentials.
The security key can be set up only after the WLSE authenticates to WDS. Therefore, if there are no problems, the final status should be security key setup.

WLSE 2.11, snmp and wds errors

Hello,
I try to use WLSE to manage our AP1131,1231 with different IOS version.. Some AP are in WDS domain with a WLSM, others in WDS with an AP configured to be wds master, and other are standalone without wds configured.
I have a lot of AP with error on WLSE, the most recurring ones are "Device was not reachable via SNMP" and "Inconsistent state found for query "interface.radio.basic"".
WLSE says that some device were not reachable by SNMP but snmp community is configured with a good access-list. Moreover, when I test snmp reachability from WLSE (admin>appliance>connectivity tools>SNMP Query Tool) it works fine. So I do not understand why I have this fault.
I do not understand the fault "Inconsistent state found for query "interface.radio.basic"", someone could help me perhaps ?
And the last question, some AP without wds configured have "Parent WDS for the Access Point" = 0.0.0.0.. I do not understand why..
If someone could help me for one of these troubles, it would be great
Thank You,
regards

All these faults are explained in detail at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/ts_gd/faults.htm
including the "Inconsistent state found for query...

WDS not authenticated with WLSE / Freeradius

I create a AP WDS (12.2(15))with Freeradius working well -> AP Information : authenticated
I give the Wireless Network Manager Ip Adresse on my WDS and my WDS Status is allways NOT AUTH. I never a request of my WLSE on my Radius. How can I configure my WLSE / WDS or Radius to have authenticated status ?

I configure SNMP on both with the same public and private community but how can I be sure that my WLSE is able to manage the WDS AP ?
I have entered in DEVICES->DISCOVER->WLCPP Credentials a USER/PASSWD I olso have entered this USER/PASSWD on my radius and in the Admin Access of my WDS AP is it good ? (I don't understand when you say "you have entered the LEAP credental on the WLSE")

WDS and SNMP

I have an AP1131 setup to act as a WDS Master and I have the radio interfaces disabled. I am also using WLSE. I am getting traps on the WLSE referring to the radio interfaces on the AP being administratively down.
I have inserted a 'no snmp trap link-status' into the config for each radio interface and have also removed any reference to 'link-up' and 'link-down' for global SNMP-Server Enable Trap commands.
I still get the same traps on the WLSE.
Is there a way to mask this trap?

This is the only setting for The snmp-server enable traps snmp [ linkup] [linkdown] form of this command globally enables or disables SNMP linkUp and linkDown traps. After enabling either of these traps globally, you can disable these traps on specific interfaces using the no snmp trap link-status command in interface configuration mode. Note that on the interface level, linkUp and linkDown traps are enabled by default. This means that you do not have to enable these notifications on a per-interface basis. However, linkUp and linkDown notifications will not be sent unless you enable them globally using the snmp-server enable traps snmp command.
And also recheck the configuration. It may help you. For the further description following command guide help you :
http://www.cisco.com/en/US/docs/ios/12_3/configfun/command/reference/cfr_1g11.html

WLSE 2.13, WDS, SNMP Unreachable

Similar Messages

Maybe you are looking for