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

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

  • Can not Authenticate WLSE Express with Active Directory

    Hi ,All
    I can not authenticate WLSE Express using external database with AD. I have downloaded the agent to the Domain Controller and install it on AD.
    At WLSE Express I found log
    "Error Server 0 RemoteDomainAuth server domain-auth: Agent API encountered error (1)"
    "Error Server 0 Service domain-auth has no active remote servers available"
    "Warning Protocol 0 Request from AP101 (10.224.20.143): User insee-wds rejected (ServiceUnavailable)"
    "Warning Protocol 0 Request from AP101 (10.224.20.143): User insee-wds rejected (InternalError)"
    maybe something wrong on AD ,
    If anyone has an idea , please help me.
    Thankss.

    I got the problem like you.
    Do you have any solution to solve this issue?
    If you have, please e-mail or post to me and everybody who be like this.
    Thank you so much.

  • Authenticating 1300 Bridges to WLSE Express

    I'm curious how I can authenticate my 1300 bridges as a client to a WLSE Express.. The WLSE Express does have a built in AAA server and i've created the usernames, but, i'm not sure where in the 1300 I can assign it to authenticate to the WLSE..
    My question I guess is, do I need to point these bridges to authenticate to the Root Bridge, and configure a RADIUS association between the Root Bridge and the WLSE Express? Also, where abouts on the Non-Root bridge (or Workgroup) do I configure this?
    Any help would be appreaciated.
    Thanks,
    Jamie

    Administratively Standalone - Active defines that this is the active WDS in WDS domain.
    Active, backup, or candidate. If the state is backup, the command (show wlccp wds) also displays the current WDS access point's IP address, MAC address, and priority.
    You can configure the WLSE 1030 internal AAA server to authenticate infrastructure APs.
    http://www.cisco.com/en/US/customer/products/sw/cscowork/ps3915/products_user_guide_chapter09186a008052dbfd.html

  • WLSE Express with PEAP

    Hi All,
    We are playing with an WLSE 1030 in combination with PEAP. We think we have a certificate mismatch somewhere. Users are getting a pop-up for there username and password, but get not authenticated.
    We imported a CA cert, Server cert and an pvk file with the private key which seems to be correct.
    Is someone having a procedure to configure the WLSE Express with PEAP?
    Thanks in advance.

    I am having a problem importing the certificate to the WLSE Express. Here is teh error that i am getting:
    An error has occurred. Please try again or contact an administrator. The error message is:
    A validation error has occurred /Radius/Services/cisco-peap/ServerRSAKeyFile: The Server RSA private key cannot be loaded from PEM:/cisco-ar/certs/cisco-peap/server-key.pem. Verify that it contains a valid PEM encoded Server RSA key and that the private key password is correct
    Any help would be greatly appreciated.

  • Win XP PEAP - AP - WLSE express - AD

    Hello
    I'm trying to set up the following configuration:
    - Windows XP client connects to 1130 AP using PEAP with EAP-MSCHAP using the computer account
    - AP use WLSE express RADIUS server for authentication
    - WLSE express use Windows AD to verify computer account
    Is there an example for this configuration?
    thanks in advance
    Thomas

    The procedure for enabling EAP based authentication on the AP is the same for all EAP variants. This document has all the information to enable EAP authentication with a RADIUS server.
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801bd035.shtml

  • WLSE Express - OpenSSL certificate translating issue

    Does anyone have suggestions for converting a .PFX file to .PEM? I can't unzip / am getting an error when trying to install the latest version off of www.openssl.com. I need to perform this conversion for WLSE to accept the certificates. (This is needed for WLSE Express to become a AAA Radius server.) Thanks. Russ

    When you install an SSL certificate on a BBSM server, it enables visitors to verify the site's authenticity and communicate with it securely through SSL encryption, which protects confidential information, such as credit card numbers, online forms, and financial data from interception and hacking.
    This protection is accomplished by using "HTTPS" when coding the page sets. SSL comes in two strengths, 40 bit and 128 bit, which refer to the length of the "session key" that every encrypted transaction generates. The longer the key, the more difficult it is to break the encryption code.
    If you are using RADIUS or credit card page sets, you must install an SSL certificate for end users to gain access to the Internet.

  • 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

  • Diffrence between WLSE and WLSE express

    Hi all,
    We have 110 AP cisco and we look to bye a solution to helps us to manage ans troubleshoot our networks, we are looking for soltion ciscoworks.
    what is difference between Wireless LAN Solution Express and Wireless LAN Solution .
    Best regard

    The main differences are device scalability, hardware differences like CPU, RAM, HD etc. See the docs for more details on this.

  • WLSE Express

    Hello,
    have 8 point to point links with bridges 1310, my question is whether the WLSE can manage and monitor the bridges 1310. (1310 in bridge mode)?
    regards,

    According to this Cisco doc it can:  http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6380/ps6563/ps6379/prod_qas0900aecd80336a51.html

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

Maybe you are looking for