SNMP Trap on AP Max associations reached

Hi all,
I want to be able to send snmp traps to my NMS alerting our NOC to when we reach our configured max-associations on an ap.  We currently use both 1130 AG and 1140-2N in autonomous mode, no controller.  I have found a debug command "debug dot11 station connection failure" and the output of a test AP shows us the fact that the maximum number was reached.  I need to find if it is possible to trap on such information. 
Any information on this would be greatly appreciated.  Also please ask me for more information if you need...
Thanks,
Daniel

Daniel,
This is a shot in the dark, but try this configuration:
ap# snmp-server enable traps dot11-mibs
I'm curious about this one, too, so please let me know if this produces the information you're looking for.
Justin

Similar Messages

  • SNMP trap on IP sla

    Hi all,
    Does anyone know that, how can SNMP trap the information(such as jitter, number of packet loss, process number of RTR) from a router enabled IP SLA/RTR?

    SNMPv1 (Simple Network Management Protocol) and SNMPv2c, along with the associated Management Information Base (MIB), encourage trap-directed notification.
    The idea behind trap-directed notification is as follows: if a manager is responsible for a large number of devices, and each device has a large number of objects, it is impractical for him to poll or request information from every object on every device. The solution is for each agent on the managed device to notify the manager without solicitation. It does this by sending a message known as a trap of the event.
    After receiving the event, the manager displays it and may choose to take an action based on the event. For instance, the manager can poll the agent directly, or poll other associated device agents to get a better understanding of the event.
    Trap-directed notification can result in substantial savings of network and agent resources by eliminating the need for frivolous SNMP requests. However, it is not possible to totally eliminate SNMP polling. SNMP requests are required for discovery and topology changes. In addition, a managed device agent can not send a trap, if the device has had a catastrophic outage.
    http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094aa5.shtml

  • IP SLA SNMP trap: ¿any way to include a meaningful message in it?

    Hello team:
    I managed my router to generate a SNMP trap when one IP SLA object detects a trigger condition.
    I would like this SNMP trap (or the associated SYSLOG message) to have a meaningful, easy to identify message (ex: SERVER NOT REACHABLE).
    ¿is there any way to accomplish this?
    Hints will be greatly appreciated
    Best regards
    Rogelio Alvez
    Argentina

    Try changing
    ip sla reaction-configuration 500 react timeout action-type trapOnly
    to
    ip sla reaction-configuration 500 react timeout threshold-type immediate action-type trapOnly
    and post "show ip sla reaction configuration".

  • Enterprise Manager Grid Control can send SNMP Traps to third-party?

    GC 11.1
    It looks like a simple config, but I've got into a confusion about it.
    I'm trying to figure out the configuration to send SNMP traps to a third party server.
    My scenario is:
    Node A (managed, monitored) ---- GC box------ SNMP box (final destination).
    My understanding is that the traps (notification methods) configured on GC box are generated by the Agent on Node A, then received by the GC and distributed as e-mails.
    What is the config to set the traps from A to reach SNMP box?
    There is the help page from the GC page (confused about interpretation):
    "Add SNMP Trap pageThe Add SNMP Trap page enables you to provide the name of the host (machine) on which the SNMP Master Agent is running and other details so that SNMP traps can be sent through Notification Rules.
    An example is shown below.
    Name HP OpenView Console
    Description Notification method to send trap to HP openview console
    SNMP Trap Host Name litleguy.us.oracle.com
    SNMP Host Port 162
    SNMP Community public
    This SNMP host will receive your SNMP traps.
    Note: A Test Trap button exists for you to test your setup."
    Any suggestions are highly appreciated.
    Thx,

    Please reply with the specific questions around this.
    11.1
    EM can send SNMP traps to specific designated receivers. You create an advanced notification method (of type SNMP Trap) with the appropriate details about the receiver.
    (See Setup->Notification Methods)
    In the notification rules UI, you specify the alerts you are interested in forwarding and select the SNMP trap advanced notification method you created earlier.
    The SNMP receiver should be provided the correct MIB that defines the SNMP trap. There were some bugs with the MIB definition in one of the releases (don't recall which one off hand), so if the traps you are receiving don't match what the receiver expects - please let us know and we can point to the right one.
    regards

  • Phantom SNMP Traps

    Hi,
    I've got most of my devices spouting SNMP traps for various different things, and Ciscoworks forwards these traps on via email, as you do.
    For most things it works great, however since we've created a script to pull on the configs off the devices (Simply don't trust Ciscoworks), we're always spammed with SNMP traps like the one below:
    ALERT ID                = 000071P
    TIME                    = Mon 10-Jan-2011 16:19:07 GMT
    STATUS                  = Active
    SEVERITY                = Critical
    MANAGED OBJECT          = lrouter-loo-0.mwam.local
    MANAGED OBJECT TYPE     = Switches and Hubs
    EVENT DESCRIPTION       = router1-loo-0.mwam.local: Cisco Configuration Management Trap:InformAlarm; PORT-lon-cr1-loo-0.mwam.local/10113 [Gi1/0/13] [Trunk to router2-gig-1-0-24]:OperationallyDown;
    CUSTOMER IDENTIFICATION = networks-info
    I know one port is down, and that's expected, I just haven't cleared the alert and turned off the monitoring in DFM.
    We're using:
    snmp-server enable traps config-copy
    snmp-server enable traps config
    on all of our devices, but only 4 out of 80+ devices throw this trap out when their config is copied by the script.
    I've googled extensively, but I haven't come across any real help.
    Has anyone got any idea what the situation is with this? I'm getting bored of deleting a bunch of emails every time our script runs, and I don't want to create a rule for fear of filtering real alerts.
    Any ideas would be appreciated
    Cheers

    This isn't a trap.  This is a DFM alert, which consists of multiple atomic events.  In this case, it looks like the alert consists of two events.  The first is a CISCO-CONFIG-MAN-MIB trap (i.e. ciscoConfigManEvent).  If you look at the associated event in the DFM Alerts and Acitivities Display, I'll bet it will indicate the configuration was copied (per your script).  The other event indicates that port Gi1/0/13 is operationally down on this switch.  The two events are unrelated, but apply to the same device.

  • Cisco Prime SNMP Traps Best Pratice

    The Cisco Prime documentation recommends configuring switches to send SNMP traps. However it does not give any more details.
    I was wondering what sorts of SNMP traps people in the community are using with Cisco Prime 2.1. I'm looking for some sort of best practice or for an idea of what traps would be the most useful to configure on the switches, to send to Prime.

    Hi ,
    Snmp traps need to be configured only on device end , there is no config need to be done on PI.
    you can enable all the traps that you want.  for e.g
    snmp-server enable traps syslog
    snmp-server enable traps ipsec start stop
    snmp-server enable traps memory-threshold
    snmp-server enable traps interface-threshold
    snmp-server enable traps connection-limit-reached
    snmp-server enable traps cpu threshold rising
    etc......
    and you can monitor then in PI (Administration > System Settings > Severity Configuration, Link down)
    check the below link as well:
    https://supportforums.cisco.com/discussion/11919481/prime-infrastructure-20-link-status-alarms
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ***

  • SNMP traps config

    G Control 11.1
    My scenario is ( 3 components):
    Node A (managed, monitored) ---- GC box------ SNMP box (final destination).
    It looks like a simple config, but I've got into a confusion about it.
    I'm trying to figure out the configuration to send SNMP traps to a third party server.
    My understanding is that the traps (notification methods) configured on GC box are generated by the Agent on Node A, then received by the GC and distributed as e-mails.
    What is the config to set the traps from A to reach SNMP box?
    There is the help page from the GC page (confused about interpretation):
    "Add SNMP Trap pageThe Add SNMP Trap page enables you to provide the name of the host (machine) on which the SNMP Master Agent is running and other details so that SNMP traps can be sent through Notification Rules.
    An example is shown below.
    Name HP OpenView Console
    Description Notification method to send trap to HP openview console
    SNMP Trap Host Name litleguy.us.oracle.com
    SNMP Host Port 162
    SNMP Community public
    This SNMP host will receive your SNMP traps.
    Note: A Test Trap button exists for you to test your setup."
    Any suggestions are highly appreciated.
    Thx,

    Solved

  • SNMP traps not capture in SCOM

    we required to capture traps sent from the proofpoint(linux base) device - snmp v2 and display on SCOM but it does not work. we can saw the traps reach SCOM by using network trace. 

    Hi
    Check this
    http://stefanroth.net/2014/04/07/scom-2012-snmp-traps-how-the-heck-do-i-get-it-working/ and thishttp://blogs.technet.com/b/kevinholman/archive/2015/02/03/snmp-trap-monitoring-with-scom-2012-r2.aspx
    and this
    http://blogs.msdn.com/b/wei_out_there_with_system_center/archive/2014/02/15/opsmgr-customizing-the-snmp-trap-collection-rule-for-all-snmp-version-traps.aspx .
    I think this should solve your Problems.
    Cheers,
    Stefan
    Blog: http://stefanroth.net If my post helped you, please take a moment to vote as helpful and\or mark as an answer

  • WLC 5508 - SNMP traps

    OK, so I'm at wit's end with this one now.
    I configured my SNMP items on the controller and let it roll.
    I started to watch my SNMP monitor (SNMPc Management Console by CastleRock) and saw some life from my controller.  Yay, woot and dance.
    I then started narrowing down the SNMP trap controls because I was getting more than what I want/need currently.  I really just want to know if an AP falls off the network or if the controller's link drops.
    I continued to get alerts that were just not desireable at this point.
    The traps were similar to this:
    ciscoLwappDot11ClientAssocNacAlert [1] cldcClientMacAddress.0.36.214.60.32.32 (DisplayString): 00:24:d6:3c:20:20 [2] cldcClientWlanProfileName.0.36.214.60.32.32 (DisplayString): Wireless [3] cldcClientIPAddress.0.36.214.60.32.32 (IpAddress): 172.31.19.101 [4] cldcApMacAddress.0.36.214.60.32.32 (DisplayString): 00:08:30:39:6c:80 [5] cldcClientQuarantineVLAN.0.36.214.60.32.32 (Integer): 0 [6] cldcClientAccessVLAN.0.36.214.60.32.32 (Integer): 119
    I couldn't find the culprit, so I turned off (unchecked) all trap controls in the web interface and then verified in the CLI with "show trapflags".
    I continue to get these same messages.
    Any ideas?
    Model: AIR-CT5508-K9
    Version: 7.2.103.0

    I went through the entire log (about 2000 lines) and almost all are this same type:
    (Cisco Controller) >show traplog
    Number of Traps Since Last Reset ............ 323738
    Number of Traps Since Log Last Displayed .... 0
    Log System Time              Trap
      0 Mon Mar 11 08:21:49 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
                                 ned profile SC Wireless                        
      1 Mon Mar 11 08:20:16 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
                                 ned profile SC Wireless                        
      2 Mon Mar 11 08:19:09 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
                                 ned profile SC Wireless                        
      3 Mon Mar 11 08:10:21 2013 Client with MAC address cc:af:78:44:7d:2b has joi
                                 ned profile SC Wireless                        
      4 Mon Mar 11 08:10:18 2013 Client with MAC address cc:af:78:44:7d:2b has joi
                                 ned profile SC Wireless                        
    Keep in mind that I have all trap controls disabled.
    (Cisco Controller) >show trapflags
    Authentication Flag.............................. Disable
    Link Up/Down Flag................................ Disable
    Multiple Users Flag.............................. Disable
    configsave....................................... Disabled
    strong-pwd check................................. Disabled
    Client Related Traps
            802.11 Disassociation........................... Disabled
            802.11 Association.............................. Disabled
            802.11 Deauthenticate........................... Disabled
            802.11 Authenticate Failure..................... Disabled
            802.11 Association Failure...................... Disabled
            Excluded........................................ Disabled
            Authentication.................................. Disabled
    Cisco AP
            AuthFailure..................................... Disabled
            Register........................................ Disabled
            InterfaceUp..................................... Disabled
    802.11 Security related traps
            WEP/WPA Decrypt Error........................... Disabled
            IDS Signature Attack............................ Disable
    AAA
            auth............................................ Disabled
            servers......................................... Disabled
    rogueap......................................... Disabled
    Auto-RF Profiles
            Load............................................ Disabled
            Noise........................................... Disabled
            Interference.................................... Disabled
            Coverage........................................ Disabled
    Auto-RF Thresholds
            tx-power........................................ Disabled
            channel......................................... Disabled
    Mesh
            auth failure.................................... Disabled
            child excluded parent........................... Disabled
            parent change................................... Disabled
            child moved..................................... Disabled
            excessive parent change......................... Disabled
            onset SNR....................................... Disabled
            abate SNR....................................... Disabled
            console login................................... Disabled
            excessive association........................... Disabled
            default bridge group name....................... Disabled
            excessive hop count............................. Disabled
            excessive children.............................. Disabled
            sec backhaul change............................. Disabled
    Hopefully I'm just missing something stupid, but it appears all flags are off.
    Message was edited by: Casey Hearn
    Added "Show TrapFlags" details.

  • SNMP traps to monitor the signal strength on wireless AP

    What snmp notification type should I enable on wireless AP to monitor the signal strength of the connected  devices  to the AP. What is the associated MIB for this SNMP trap.

    Hi karthikeya,
    Here is the link which gives us the info regarding the available MIB for the respective Model..
    http://tools.cisco.com/ITDIT/MIBS/MainServlet?ReleaseSel=3469&PlatformSel=9&fsSel=1292
    Please select the Device part number and then chose the MIB that you require.
    lemme know if this answered your question..
    Regards
    Surendra
    ====
    Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

  • SNMP traps with WLC 4402

    Currently using WLC 4402 with about a dozen WAPs. I would like to start logging some messages to troubleshoot some association issues. The syslog does not seem adequate for this the issues I am having. I noticed the default SNMP traps but is only holds 255 traps. I have tried to setup an SNMP server to get the traps but I get no data, only OID values. I was successful in getting the MIBs for the OIDs but still not all the data that I see on the brief traps screen.

    Hi,
    I have tried it with solarwinds and works fine for me. Talking about the traps. But they are too many.
    The OID is : 1.3.6.1.4.1.14179.1.1.2.4.1.22
    snmp info for polling:
    MIB Value Type: Raw Value
    Format: None
    SNMP Get Type: Get Table
    Polling Type: node
    On WLC go to Managemnet (top TAB)
    Right hand select > SNMP > Traps Control.
    In this menu select what traps to need to be logged.
    These traps will be shows on the oid polled.

  • CiscoWorks LMS: not receveing certain SNMP traps

    CiscoWorks LMS 4.0.1 (I know it's old and unsupported).
    Problem: not receiving certain SNMP traps.
    For example: I receive trap like "STP new root" but not like "port put to err-disabled" or my custom traps (produced by EEM scripts).
    I've investigated my situation and found out that switch sends traps and they reach* LMS but somehow LMS ignores them (there's no trace of them in GUI). I've read that some traps just pass through LMS but my traps are very important and I need to know about them.
    * I did Wireshark capture on LMS machine.
    I'd like to know how to debug receiving of SNMP traps in LMS:
    which specific debugs need to be enabled,
    which specific log files need to be examined.

    LMS uses DFM to process certain traps.
    All traps it deems unimportant are dropped.
    If you want to use the LMS GUI you can have you device send a SYSLOG message rather than a trap.
    use logging source command to make the management interface send the message.
    Then there is a GUI that allows you to launch an action on a message
    Cheers,
    Michel

  • Snmp trap versus syslog message

    Hi,
    Most network devices will send snmp traps and syslog messages to a central server.
    For analyzing purpose this server runs software to display the messages or traps.
    My question is, what is the difference between syslog messages and snmp traps?
    What is best practise?
    Thank you very much.
    Hansruedi

    From the very basic level, traps and syslog differ in the encoding.  Syslog messages are typically text messages sent within a UDP packet.  There is a bit of binary encoding to indicate the syslog facility and severity.  SNMP traps have encoded ASN.1 fields (called variable bindings).  These varbinds are not ASCII text like syslog messages.  Instead they are encoded object identifiers that can be translated into object names using MIB definitions.
    More syslog messages exist than SNMP traps because syslog messages do not have as much governance associated with them.  However, we typically recommend that customers enable both as there are some details available in traps that you may not get in syslog messages.  Traps can also be processed in a more programmatic fashion because of the documentation that goes into the MIBs that define them.

  • Re:SNMP Trap in 10.3

    Hello
    We are migrating Applications for 8.1 to 10.3
    So we wanted to set SNMP Traps in the 10.3 at the domain Level
    We had setup the traps in 10.3 and restarted but we are not able to recevie any traps
    Please let me know if you have any suggestions
    Regards
    -nar-

    When you start the managed server, you should see a message such as the following:
    <Feb 18, 2010 12:39:04 AM EST> <Notice> <SNMP> <BEA-320931> <The SNMP trap version is 2>
    Are you using a port > 1000 on your Server agent? 161 is probably just your port on the Domain agent. There are 2 ports to be careful of, SNMP UDP Port and Master AgentX Port; both on the General tab for the server agent.
    Here's an extract of the SNMP config, showing the "Server SNMP Agents" and a single String Monitor for the server status
    <snmp-agent-deployment>
    <name>Name_of_server_SNMPAgent</name>
    <enabled>true</enabled>
    <send-automatic-traps-enabled>true</send-automatic-traps-enabled>
    <snmp-port>1161</snmp-port>
    <snmp-trap-version>2</snmp-trap-version>
    <community-prefix>public</community-prefix>
    <snmp-trap-destination>
    <name>some name</name>
    <host>xxx.xxx.xxx.xxx</host>
    <port>162</port>
    <community>public</community>
    <security-level>noAuthNoPriv</security-level>
    </snmp-trap-destination>
    <snmp-string-monitor>
    <name>ServerStatus</name>
    <enabled-server>Server1,Server2</enabled-server>
    <monitored-m-bean-type>ServerRuntime</monitored-m-bean-type>
    <monitored-m-bean-name></monitored-m-bean-name>
    <monitored-attribute-name>HealthState</monitored-attribute-name>
    <polling-interval>10</polling-interval>
    <string-to-compare>OK</string-to-compare>
    <notify-differ>true</notify-differ>
    <notify-match>false</notify-match>
    </snmp-string-monitor>
    <community-based-access-enabled>true</community-based-access-enabled>
    <snmp-engine-id>Name_of_server_SNMPAgent</snmp-engine-id>
    <authentication-protocol>noAuth</authentication-protocol>
    <privacy-protocol>noPriv</privacy-protocol>
    <inform-retry-interval>10000</inform-retry-interval>
    <max-inform-retry-count>1</max-inform-retry-count>
    <localized-key-cache-invalidation-interval>3600000</localized-key-cache-invalidation-interval>
    <snmp-access-for-user-m-beans-enabled>false</snmp-access-for-user-m-beans-enabled>
    <inform-enabled>false</inform-enabled>
    <master-agent-x-port>1705</master-agent-x-port>
    <target>AdminServer,Cluster1,Cluster2</target>
    </snmp-agent-deployment>

  • EBGP PEER FLAP SNMP TRAP

    Hi
    Whenever there is a bgp neighbour flap, we are not getting snmp traps on the HP NNMI Server.. I believe during the neighbour flap, the device is unable to communicate with NNMI and drop the trap..
    So I would like to write a custom EEM SCRIPT that can match a syslog pattern and generate a customised SNMP trap and send it to NNMI. May be I can delay the trap generation or sending so that the device restores the connectivity and then send an alert
    Here are my questions:
    Is this a good idea?
    Can you give me a sample configuration with the MIB Values to be generated?
    What MIB Should be loaded on the server?
    I am curious how others are monitoring this kind of bgp flaps...
    Sent from Cisco Technical Support iPad App

    After i enabled snmp inform using following command
    snmp-server host 100.190.19.33 informs version 2c XXXX
    I see it is contineously incrementing snmp inform sent messages on the router..I am not sure what it is sending..I would like to be specific like sending only BGP snmp informs to the NMS..is it possible ?
    DR1#show snmp
    Chassis: FHK0850F0HL
    4338622 SNMP packets input
        0 Bad SNMP version errors
        746076 Unknown community name
        0 Illegal operation for community name supplied
        0 Encoding errors
        35020739 Number of requested variables
        0 Number of altered variables
        3303916 Get-request PDUs
        97632 Get-next PDUs
        0 Set-request PDUs
        0 Input queue packet drops (Maximum queue size 1000)
    6639622 SNMP packets output
        0 Too big errors (Maximum packet size 1500)
        546341 No such name errors
        0 Bad values errors
        0 General errors
        3592535 Response PDUs
        3047076 Trap PDUs
    SNMP Dispatcher:
       queue 0/75 (current/max), 0 dropped
    SNMP Engine:
       queue 0/1000 (current/max), 0 dropped
    SNMP logging: enabled
        Logging to 10.45.224.19.162, 0/10, 761350 sent, 347 dropped.
        Logging to 10.48.176.1.162, 0/10, 759955 sent, 1886 dropped.
        Logging to 100.190.19.25.162, 0/10, 761329 sent, 368 dropped.
        Logging to 100.190.19.33.162, 0/10, 761367 sent, 474 dropped.
    SNMP Manager-role output packets
        0 Get-request PDUs
        0 Get-next PDUs
        0 Get-bulk PDUs
        0 Set-request PDUs
        11 Inform-request PDUs
        0 Timeouts
        0 Drops
    SNMP Manager-role input packets
        0 Inform request PDUs
        0 Trap PDUs
        11 Response PDUs
        0 Responses with errors
    SNMP informs: enabled
        Informs in flight 0/25 (current/max)
        Logging to 100.190.19.33.162
            11 sent, 0 in-flight, 0 retries, 0 failed, 0 dropped

Maybe you are looking for