Cisco ACS SNMP Traps

Is it possible to send an SNMP trap from Cisco ACE 4710  for any configuration changes that  occurs?
Regards,
Hesham                 

Hi Hesham,
these are the traps which are supported by ACE.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA5_1_0/configuration/administration/guide/snmp.html#wp1177230
read section "ACE SNMP Notifications (Traps)"
I do not see a trap which is useful for your requirement.
regards,
Ajay Kumar

Similar Messages

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

  • Cisco Prime SNMP trap logs

    Hi
    In Cisco Prime Infrastructure, where can we find the snmp trap logs and can we do the snmp polling through webconsole, please suggest how we can troubleshoot if the device is not reachable, do we need to login through ssh and check or is there any other options available.
    Can we find out the configuration details of the specific device, how we can do it.
    Please advice

    Hi abhishek ,
    First of al you have to check on your devices SNMP is enable or not , its all depending on SNMP configuration , if possible check the running config , and paste the running configration , to solve your issue
    rate it

  • Cisco ACS SNMP

    Hello,
    We're running two ACS boxes (Release 4.1(4) Build 13 Patch 3). On of our boxes doesn't have the SNMP option available under Appliance Configuration, but our other does. Anyone know how to enable this? Thank you.
    John

    Probably you have an appliance that was not re-imaged with 3.3.3 CD, where SNMP was introduced and to have SNMP option, it was necessary to re-image. And you made all the remote upgrades and reached from 3.x to version 4.1.4.13.3 on your ACS SE.
    To get this option,
    - Take a backup of the database
    - re-image ACS SE with 4.1.1.x recovery Cd for the appropriate platform, and then upgrade it to version 4.1.4, and then apply patch 3
    - Restore the backup
    Regards,
    Prem
    Please rate if it helps!

  • Cisco ISE 1.2 and Cisco ACS 5.4 patch 6 and support for snmp version 3

    does anyone know if cisco ISE version 1.2 patch 8 and Cisco ACS 5.4 patch 6 support snmp version 3?
    ciscoISE/admin(config)# snmp-server ?
      community  Set community string
      contact    Text for mib object sysContact
      host       Specify hosts to receive SNMP notifications
      location   Text for mib object sysLocation
    ciscoISE/admin(config)# snmp-server
    Ciscoacs/admin(config)# snmp-server ?
      community  Set community string
      contact    Text for mib object sysContact
      host       Specify hosts to receive SNMP notifications
      location   Text for mib object sysLocation
    Ciscoacs/admin(config)# snmp-server

    No support SNMP v3 on ISE v1.2 and 1.3 except for profilling
    http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/cli_ref_guide/ise_cli/ise_cli_app_a.html#12768
     http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/cli_ref_guide/b_ise_CLIReferenceGuide/b_ise_CLIReferenceGuide_chapter_0100.html#ID-1364-00000d30

  • SNMP traps from Cisco 4404

    I have a Cisco 4404 WLC that sends its system logs to a syslog server (kiwicat), but I'm interested in getting the snmp traps sent over there as well.  I've configured the syslog server to accept the snmp on the right ports and I've confirmed that the syslog server can receive then by sending traps manually from other devices.
    I cannot seem to actually get the WLC to send the traps to the server.  the syslog stuff gets through ok, but not the snmp.  I've added the syslog server as an SNMP trap reciever and configured it as much as it needs to be and the only difference it seems to have made is to add more things to the main trap log on the 'monitor' tab on the WLC.  Am i missing something really basic?
    p.s. the WLC and the syslog server are separated by a firewall, but the syslog rules have been altered to also allow the snmp, should it attempt to go through.
    Any help would be gratefully received.

    Yes, I think the Network Devices need to be discovered first in order to receive traps and generate alerts.
    Juke Chou
    TechNet Community Support

  • Cisco Prime Infrastructure 1.4 SNMP Traps are not converted into Alarms

    Hi everybody,
    I just configured SNMP Traps on a Cisco Catalyst 3750-x to send to our Cisco Prime Infrastructure 1.4 Appliance.
    Now I forced the Switch to send some traps (Power off a Power Supply, Interface errdisable). The only events I see in Alarms & Events on PI is the same information message everytime:
    Configuration management event has been recorded in ccmHistoryEventTable.
    I think the forced traps should be converted into alarms? Why can't I see them?
    Thanks,
    Marc

    Ok, I started debugging as you said. I get the following output:
    Mar 13 09:28:13.711: SNMP: V2 Trap, reqid 11689, errstat 0, erridx 0
     sysUpTime.0 = 198609846
     snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
     clogHistoryEntry.2.1688 = PM
     clogHistoryEntry.3.1688 = 5
     clogHistoryEntry.4.1688 = ERR_RECOVER
     clogHistoryEntry.5.1688 = Attempting to recover from bpduguard err-disable state on Gi1/0/13
     clogHistoryEntry.6.1688 = 198609844
    Mar 13 09:28:13.737: SNMP: Queuing packet to xx.xx.xx.xx
    Looks like the Switch is sending SNMP Traps from the ciscoSyslogMIB. Is this why PI can't show the Traps and convert it into a alarm?
    After this test I configured logging (syslog) to the PI. Now the errors are showed but still not converted into alarms. I just want to be notified by email when such errors occurs.
    Thanks,
    Marc

  • Cisco WLC 5508 not sending SNMP Traps

    Hello Everyone.
    I'm having a weird error on our WLC environment. We have an HA with two cisco WLC 5508 and i cannot get SNMP Traps working on a Windows PC running Kiwi Syslog server (free ed.).
    I can receive correctly Syslog messages, but not traps.
    I Tried also to send SNMP Traps from WLC to a different PC using Linux with snmptrapd and it works fine.
    I tried then to send from my Linux box a snmp trap to my Windows PC, and it works fine, but i still cannot receive anything from WLC.
    Using Wireshark to detect traffic, i cannot see any packet on udp port 162.
    I cannot figure out any problem with my scenario, but i can see the following errors on syslog:
    *rmgrTrasport: Mar 30 16:08:22.602: #RMGR-3-INVALID_PING_RESPONSE: rmgr_utils.c:270 Ping response from <my_windows_PC> is invalid. Ip address do not match.
    My WLC Version is 7.6.130.0
    Thank you for your support.

    I have gone through your query and found the following fruitful links ,please let me know if it helps and mark it correct answer if it is.
    https://www.manageengine.com/network-monitoring/help/userguide/processing_traps.html
    https://rscciew.wordpress.com/2014/10/12/snmp-configuration-on-wlc/
    Thanks :)

  • Curious message during activation of snmp traps in cisco router 2800

    I activated snmp traps in cisco router 2800 (I didn't specify a set of them, so all of them were activated). The thing is, when i configure "snmp-server enable traps", appears a message in the next line :
    " %Cannot enable both sham-link state-change interface traps.
       %New sham link interface trap not enabled "
    Anyway, traps are activated and are completely functional.
    I would like to know, why this message appears... and also what is the difference between  informs and traps, because I can activate both of the in a router to be sent to the network admin pc.
    Thanks in advance.

    Hi Marcelo,
    the snmp-server enable traps command enables just all types of traps that the IOS version supports.
    The message apperes because of this two, which are mutually exclusive:
    R1(config)#snmp-server enable traps ospf cisco-specific state-change shamlink interfaceR1(config)#snmp-server enable traps ospf cisco-specific state-change shamlink interface-old% Cannot enable both sham-link state-change interface traps.% Deprecated sham link interface trap not enabled.
    It's recommended to only enable the traps you really need.
    Informs were introduced with SNMPv2, and they have the same format and purpose as traps.
    The main difference is that traps are send in a hit-or-miss fashion whereas informs expect an acknowledge and will be re-send if unacknowledged.
    Hope that helps
    Rolf

  • Cisco ISE supported SNMP traps

    What's the supported SNMP traps on Cisco ISE.
    I am able to retrieve the supported MIBs, however not able to find any information on traps.
    I have reviewed these previous thread, but not clear to me which traps are supported by Cisco ISE ?
    https://supportforums.cisco.com/thread/2165257
    https://supportforums.cisco.com/message/4021560#4021560
    Testing the Cisco ISE in a lab, I notice that interface up/down and authentication traps are being sent to SNMP server. Any docummentation or full list of the traps would be appreciated.
    Regards,
    Ahmed Ramadan.

    Please see the attached file for SNMP and radius attribute.

  • How view snmp Traps CISCO PRIME 1.2

                       It is posible to view snmp Traps from WLC to CISCO Prime ?? How ?

    Hi Steve :
    I need to view the traps which are generated in the Controller, I need to view that in the Cisco Prime Infractructure. I´ve configured Communities in WLC with IP Address to Cisco Prime and Trap Receiver with IP address to Cisco Prime.
    Now, How can I view these Traps in the Cisco Prime ?.
    Another question , Is it posible to configure Switch from Cisco Prime ?
    Thanks,
    Claudio

  • LMS 3.2.1 integration with Clarity NMS for snmp trap forwarding

    Our client have integrated Clarity NMS to Ciscoworks LMS 3.2.1. So far they are receiving raw alarms/snmp traps but it lacks information/inventory of the originating device. Kindly see sample raw alarms below:
    2420: 2011-11-25 12:10:46 Received trap ==> Received SNMPv1 Trap
    Community=ciscoworks
    Enterprise=1.3.6.1.6.3.1.1.5
    Generip trap type=2
    Specific Trap Type=0
    Trap From=10.220.10.1
    Trap ID=1.3.6.1.6.3.1.1.5.2
    Trap Time=-1436283373
    1.3.6.1.2.1.2.2.1.1.83=83
    1.3.6.1.2.1.2.2.1.2.83=GigabitEthernet1/40
    1.3.6.1.2.1.2.2.1.3.83=6
    1.3.6.1.4.1.9.2.2.1.1.20.83=Lost Carrier
    EndTrap
    10933: 2011-11-24 11:57:53 Received trap ==> Received SNMPv1 Trap
    Community=ciscoworks
    Enterprise=1.3.6.1.4.1.9.1.291
    Generip trap type=2
    Specific Trap Type=0
    Trap From=10.220.10.1
    Trap ID=1.3.6.1.4.1.9.1.291.2
    Trap Time=1628056965
    1.3.6.1.2.1.2.2.1.1.8=8
    1.3.6.1.2.1.2.2.1.2.8=E1 0/0/0
    1.3.6.1.2.1.2.2.1.3.8=18
    EndTrap
    As you can see, those raw alarms doesn’t contain any information about the originating equipment or the physical card, port related information where those alarms were generated. Instead those alarms received are just NMS level alarms.
    How do we resolve this so that the inventory of the equipment would be part of the trap to be received by Clarity from Ciscoworks.

    Hi,
    Is the issue you have the source IP address of the forwarded trap?  Per RFC it is the IP of the actual device sending the trap.  The originating IP should be contained within the packet. I have included some additional information you may find helpful.
    Q. What is the difference between SNMP Raw Trap Forwarding and SNMP Trap alert/event Trap Forwarding? Does DFM support both?
    A. You can configure raw trap forwarding at DFM > Other configuration > SNMP Trap forwarding, and processed event/alert trap forwarding at DFM > Notification Services > SNMP Trap Forwarding. Processed trap is "when DFM receives certain SNMP traps, it analyzes the data found in fields (Enterprise/Generic trap identifier/Specific Trap identifier/variable−bindings) of each SNMP trap message, and changes the property value of the object property (if required)". Raw trap is the trap that the device forwards to DFM and DFM has yet to process it. For more information, refer to the DFM User Guide. Yes, DFM supports both ways of trap forwarding.
    http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_qanda_item09186a0080a9b35b.shtml
    DFM will only forward SNMP traps from devices in the DFM inventory. It will not change the trap format—it will forward the raw trap in the format in which the trap was received from the device. However, you must enable SNMP on your devices and you must do one of the following:
    Configure SNMP to send traps directly to DFM
    Integrate SNMP trap receiving with an NMS or a trap daemon
    The versions of SNMP traps supported by DFM are described in SNMP and ICMP Polling. For information on forwarding processed and pass-through traps, see Processed and Pass-Through Traps, and Unidentified Traps and Events.
    Pass-through traps are traps that DFM receives from devices that are not in the DFM inventory, and DFM has not processed. Forwarding these traps is controlled using Configuration > Other Configurations > SNMP Trap Forwarding. These traps are shown in the Alerts and Activities display because of their relevance to fault monitoring. Pass-through traps are displayed as follows:
    As one of the following events:
    > InformAlarm
    > MinorAlarm
    > MajorAlarm
    With the device type and the device name from which it was generated.
    If DFM does not know which device generated the trap, it ignores the trap. Pass-through traps will be cleared after a default interval of 10 minutes to one hour
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/dfm32ug_Book.html

  • 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

  • SNMP TRAP ON Secondary WLC 5508

    Hi I'm Louis,
    I work on 2 WLC 5508 with version 7.4 and Prime Infrastructure 1.3
    We have activate AP SSO to work with a primary and secondary controller.
    We have added the controller to Prime infrastructure and activated SNMP.
    We receive correctly the alarms on Prime.
    But when we work on Primary WLC, and the secondary crash we haven't got information about that. No SNMP received.
    That is normal ?
    Thx for your reply
    Regards

    I find this, in Monitoring and Troubleshooting the Redundancy States
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/chgdevconfig.html
    On my primary controller, in SNMP => Trap Log , I can see :
    RF failure notification ErrorType: 34 Reason :Lost Peer, Moving to Active-No-Peer State! => When I unplug RP link
    RF progress notification unitId: -1407319963 peerUnitId :14 unitState: -1407319863 peerUnitState :5
    RF progress notification unitId: -1407319963 peerUnitId :14 unitState: -1407319863 peerUnitState :9  => When I plug the RP link.
    So I can see the trap on my controller but there is nothing in Prime ...

  • SNMP Traps is not being sent clear event when DB is UP

    Test Traps everything else is also coming fine. Listener, Database Errors, down etc are all coming in fine thru' SNMP. SNMP traps and OEM all working ok. Question is for database up event there is no CLEAR event being sent. Is there anything else that needs to be configured?
    SQL> SELECT owner, name, enqueue_enabled, dequeue_enabled FROM dba_queues
    2 WHERE name like '%NOTIFY%';
    OWNER NAME ENQUEUE DEQUEUE
    SYS AQ_PROP_NOTIFY YES YES
    SYSMAN AQ$_MGMT_NOTIFY_QTABLE_E NO NO
    SYSMAN MGMT_NOTIFY_Q YES YES
    SYSMAN AQ$_MGMT_NOTIFY_INPUT_QTABLE_E NO NO
    SYSMAN MGMT_NOTIFY_INPUT_Q YES YES

    Hello,
    Under interface for specific interface: snmp trap link-status
    http://www.cisco.com/en/US/docs/ios/12_0/configfun/command/reference/frmonitr.html#wp1023375
    Also in newer IOS
    The snmp-server enable traps snmp [ linkup] [linkdown] form of this command replaces the snmp trap link-status interface configuration mode command.
    http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a05.shtml
    HTH
    Saju
    Pls rate helpful posts

Maybe you are looking for