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

Similar Messages

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

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 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.

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...

Wlse unknown fault

does anyone familiar with this message on the wlse faults -
"Inconsistent state found for query "interface.radio.config"
thanks

All WLSE Faults details are listed at: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_11/ts_gd/faults.htm
Not seen this before. What WLSE version is this?

WLSE Fault Settings

I'm looking for a good explanation regarding the following:
XXXXX Aironet AP 1210 Radio-B Port Dot11Radio0 Packet Error is in Degraded state (29%) P4 Degraded 15:26:59 06/07/2004
I've set up the faults, but haven't came across and good explanation how will this affect my wireless network performance. Any help would be greatly appreciated.

See "Table 2-2 Radio Interface Faults" for the details on this Fault: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_7/ts_gd/faults.htm#wp1035591

Windows 2012 - SNMP Fault

I have a Batch file to configure SNMP by modifying registry. I, the past, i had used successfully to configure WIn2008/R2 Servers with no problem.
Now, í´m trying to configure WIn2012/R2 Servers and i got an error. And the error appears, even configuring manually, without the batch file.
The error:
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Description:
Faulting application name: snmp.exe, version: 6.2.9200.16384, time stamp: 0x5010a8da
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x766c
Faulting application start time: 0x01cf6fb104bdf438
Faulting application path: C:\Windows\syswow64\snmp.exe
Faulting module path: unknown
Report Id: 426ce085-dba4-11e3-93fb-001018f79f53
Faulting package full name:
Faulting package-relative application ID:
Always followed by 2 times Event ID #1001
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: snmp.exe
P2: 6.2.9200.16384
P3: 5010a8da
P4: StackHash_c916
P5: 0.0.0.0
P6: 00000000
P7: PCH_E5_FROM_ntdll+0x0002DC34
P8: c0000005
P9: 00000008
The batch file ist´s simply a REG ADD command:
========= Cutted ===============================================
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters" /v EnableAuthenticationTraps /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 1 /t REG_SZ /d %SOURCESERVER1% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 2 /t REG_SZ /d %SOURCESERVER2% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 3 /t REG_SZ /d %SOURCESERVER3% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 4 /t REG_SZ /d %SOURCESERVER4% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\ValidCommunities" /v %COMMUNITYNAME% /t REG_DWORD /d 4 /f
========= Cutted ===============================================

In most of the occurrences, the unistall/reboot/reinstall of SNMP solved the issue. Maybe because the reinstall was doing the check you mentioned.
Now i´m facing another problem, because in another machine i did the exact same procedure but event doing that, the SNMP service is up, no firewall, and network monitor showing the snmp traffic coming and no response from snmp service, like "ignoring"
the traffic
Te config in the GUI and registry are OK, to make sure the source IP address is known
The machines are workgroup, so, i created a batch file and this batch file worked with no problem in several machines
In my Win2008R2 and WIn2012/R2 the service is on: C:\Windows\System32\snmp.exe
The machine have 2 NIC Teams and UDP is listening in port 161 on on all interfaces
The network monitor shows a message, with a proof of SNMP traffic coming
SNMP:Version2, Community = <COM_NAME>, Get request, RequestID = 56355 {UDP:24, IPv4:23}
The SNMP.EXE versionas are diferente
C:\Windows>dir SysWOW64\snmp.exe
Volume in drive C is DISCO
Volume Serial Number is 004D-74E8
Directory of C:\Windows\SysWOW64
26/07/2012 12:20            45.056 snmp.exe
               1 File(s)         45.056 bytes
               0 Dir(s) 272.665.096.192 bytes free
C:\Windows>dir SysWOW64\snmp.exe
C:\Windows>dir system32\snmp.exe
Volume in drive C is DISCO
Volume Serial Number is 004D-74E8
Directory of C:\Windows\system32
26/07/2012 12:08            50.688 snmp.exe
               1 File(s)         50.688 bytes
======================================
@echo off
cls
echo.
echo.
echo versao 2.3fb
set COMMUNITYNAME=NonPublic
set SOURCESERVER1=10.11.12.13
set SOURCESERVER2=mon.contoso.com
set SOURCESERVER3=mon.proseware.net
set SOURCESERVER4=mon.litware.local
echo.
echo.
echo Lendo dados SNMP atuais
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers"
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\ValidCommunities"
echo.
echo.
echo Parando SNMP...
echo.
echo Se der erro... Nao tem SNMP instalado!
echo.
echo.
net stop SNMP
echo.
echo.
echo Alterando valores
echo.
echo.
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters" /v EnableAuthenticationTraps /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 1 /t REG_SZ /d %SOURCESERVER1% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 2 /t REG_SZ /d %SOURCESERVER2% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 3 /t REG_SZ /d %SOURCESERVER3% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers" /v 4 /t REG_SZ /d %SOURCESERVER4% /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\ValidCommunities" /v %COMMUNITYNAME% /t REG_DWORD /d 4 /f
echo.
echo.
echo Iniciando SNMP...
echo.
echo.
net start SNMP
echo.
echo.
echo Lendo dados SNMP atuais
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\PermittedManagers"
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SNMP\Parameters\ValidCommunities"
PAUSE
========================================

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.

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

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 error with new firmware 12.4-3g

when i update my 1131 APs, WLSE send this message ;
Inconsistent device state found:
CISCO-DOT11-IF-MIB cd11IfStationConfigTable.cd11IfStationRole must be in the range [1..11] (was 0)"

Hi,
Check this out,
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi58022
CSCsi58022 : IOD : Inconsistent Error messages in WLSE for 1130 and 1240
IOD : Inconsistent Error messages in WLSE for 1130 and 1240
Alternate Headline: IOD : Inconsistent Error messages in WLSE for 1130 and 1240
Symptom:
====================
WLSE reports a fault as follows.
Inconsistent device state found: Device "APXXXX": ifIndex=1, MAC=XX-XX-XX-XX-XX-XX: "CISCO-DOT11-IF-MIB cd11IfStationConfigTable.cd11IfStationRole must be in the range [1..11] (was 0)"
Condition:
===========
Reproducibility : unknown
Frequency : unknown
Components:
==================
WLSE Ver2.15
Aironet Ver12.4(3g)JA
Workaround:
==========
This phenomenon doesn't impact function.
Regards,
Prem

AP1230 and 123-8.JEA1 and WLSE 2.13.1

Hi all
Cisco recently released the IOS 12.3-8.JEA1 which seem to fix some issues with the communication between the WDS and the WLSE (SNMP Timeout). But the current version of the WLSE only "supports" images up to release 12.3-8.JEA.
Can I savely install the newer release on our WDS or could they loose the communication with the WLSE?
Thanks,
Patrick

Hi Patrick,
you are right. The WLSE shows the devices as not supported. But on the other ahnd i have some installations running with these image at different costumers without any loss of service.
Radio Management, Archiving, Location Manager and some more services are running fine.
My experiences are leading to the conclusion that you can install the IOS Image.
Best regards,
Frank

WLSE2.13 event log

I have upgraded WLSE to version 2.13.
After upgrading, "Unable to verify MFP configuration","MFP Timebase Invalid (bad SNTP), Device was not reachable via SNMP" these messages are logging so many on WLSE fault status. What are these mean and How to solve this problems.
and "Client MAC Spoofing Detected on 004096ae4f8f , and on AP" this message also show up too many.What is this mean and what should i do clear this fault event log?

For both faults, refer to Table 2-3 in Fault FAQ: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_13/ts_gd/faults.htm for details on Fault Description, Explanation, Related Setting and Recommended Action

C370 - 7.6.3-019 An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370'

I got the following CRITICAL error at C370:
The Critical message is:
An application fault occurred: ('snmp/ipmi_handlers.py _handle_fan_result|370', "<type 'exceptions.ValueError'>", "invalid literal for int() with base 10: 'no reading'", '[_coro.pyx coro._coro._wrap1 (coro/_coro.c:8477)|757] [egg/interface_controller.py poll_ipmi|1409] [snmp/hardware.py update_sensors|89] [snmp/ipmi_handlers.py update_sensors|609] [snmp/ipmi_handlers.py _parse_sensor_lines|583] [snmp/ipmi_handlers.py _handle_fan_result|370]')
Version: 7.6.3-019
Maybe this bug is related to WSA bug CSCzv78978...
Need a help to see if this bug is resolved at 8.0.1-023 release.

This is ESA defect on 7.6 family... see the following:
https://tools.cisco.com/bugsearch/bug/CSCzv22991
You'll need to upgrade to 8.0.1-023, or you can open support case, we can provision 8.5.6 FCS, or you can wait for our 8.5.6 GA release shortly...
I hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

WLSE & SNMP unreachable fault

Similar Messages

Maybe you are looking for