Using SNMP traps

Hello,
We are trying to get our Ironports to send out SNMP traps.
At this moment we use a M1050 for testing. we have no test C series and I do not want to pull out a power supply or disk on one of our production systems, just for testing :wink:
At this moment the experiences with the M1050 are not very hopeful.
At first the cold-start trap was send out on the default interface (data1) instead of the management interface which we configured for SNMP, most of the other traps where not send out at all. This was confirmed by support and they promised a better behavior for next versions.
When we upgraded the M1050 to version 6 we expected to gain some traps but the result was disappointing. The cold start trap was now send out over the expected (configured) interface but all the other traps where not send out at all.
Does anyone have other experiences with the C series?
All input is appreciated.
Regards Steven

There is a known issue affecting SNMP traps in AsyncOS versions 5.5 and above. Look for a maintenance release next week and then try your tests again.
cheers,
Chris
Do you have a link to that case, as i have some issues in my own setup. We are using Cacti to monitor our 2 C350. From time to time, we get a timeout on SNMP, but the C350 i proccesesing mail.
/Thorsten

Similar Messages

  • Snmp Traps using in SSIS

    Hi All,
    I want to use Snmp Traps for SSIS packages.If any error in Package,
    I want to send notifications to main server.
    How can we implement in SSIS.Can we implement in SSIS?
    If anybody knows please tell me it is very urgent.
    Thanks in Advance.

    I've not used it
    But you may try code like below within script task in SSIS
    http://www.c-sharpcorner.com/forums/thread/59866/sending-snmp-traps.aspx
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Sending alerts as SNMP-Traps from Solman to Nagios

    Hi!
    we would like to set up the alerting structure for sending the alerts as SNMP-Traps from Solman to Nagios.
    The questions:
    1) Is such integration possible? If yes, how complexe?
    2) What are the technical steps to perform in order to realize these steps?
    3) What are the steps to perform on Nagios server?
    Thank you very much!
    regards
    H. Thomasson

    Hello Prasad,
    a search for SNMP in the Online Documentation returns [Sending and Receiving Alerts Using SNMP Traps|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ff/0620fbf6a404479d48b9e24552f770/frameset.htm].
    Regards, Michael

  • BPMon: Send BPMon alerts to third party tool through SNMP traps

    Hi All,
    In our environment the preferred ticketing tool for raising tickets is a CA tool. I have managed to integrate system monitoring on Solution Manager with this third party tool using SNMP traps. Essentially when a system monitoring alert is raised in the alert inbox of solution manager, ticket gets raised in the CA tool.
    I want the same integration with BPMon alerts. Whenever a BPMon alert is raised, I want to send an SNMP trap to the CA ticketing tool.
    Can someone please guide me to the correct configuration guide or how its done.
    Regards,
    Ash

    Hi Ash
    Pleasee see the help guides on raise auto alerts based on CCMS and MTE
    http://help.sap.com/saphelp_nw04s/helpdata/en/a9/ef1e109d1af946ae5ab624f972c6fa/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/43/ee6df92cf4eb41b11d15cc8e3a368a/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/66/f9a9b903a611d3b44f006094b910d9/content.htm
    As Keiji has said, the functionality that you are looking for is part of teh MAI infrastructure that is available is SP12
    Best Regards
    Mark

  • Sending as SNMP trap

    Hello expert,
    Currently my SolMan system serve as central ccms monitoring, some of the alerts are sending email alert as auto reaction method.
    But recently there is request to send the alert to 3rd party non SAP monitoring tool. I am thinking of SNMP traps. but question is each MTE can only have 1 auto reaction method, if i change it to use SNMP traps, so my exisitng email alert is not able to working parallel?
    please advise.
    thank you
    kelly

    Dear Kelly,
    You may find the following document useful when using CCMS and SNMP Traps.
    > https://websmp109.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001606922004E
    Regards,
    Paul

  • Send solman alerts as SNMP traps?

    We want to send solman alerts as SNMP traps to an external monitoring solution.
    Can someone please provide info on how to do it?
    Thanks

    Hello Prasad,
    a search for SNMP in the Online Documentation returns [Sending and Receiving Alerts Using SNMP Traps|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ff/0620fbf6a404479d48b9e24552f770/frameset.htm].
    Regards, Michael

  • SNMP Traps Monitoring problem.

    Hi,
    Hear is my problem. I am using SNMP Traps as Auto-Reaction Method to monitor some files system. I am already receiving Traps when the file exceeds the thresholds value (when change from Green to Yellow and when change from Yellow to Red). The problem that I’m having is that I am not receiving Traps to reset these values (Reset from Red to Yellow and Reset from Yellow to Green). What do I have to do to receive those traps?

    Hi Santiago,
    I am trying to send snmp alert from solution manager to Tivoli enterprise console. I did all configuration based on SAP document but Tivoli team keep saying that they did not receive anything. There is no way i can test on my side that what is the problem. When aler is generated, i see the MTE goes red and then alert status shows " Action required". However if I change the method to email, i receive emails. it is only SNMP which does not  work.
    Can you tell if i need to setup special parameter in SNMP method which i am missing. I did the following:
    HOST - Tivoli server
    Trapsort - UDP
    Port - 162
    MIB_DIR = /usr/sap//SID/SYS/exe/run/MIBS
    Also is there any settings which Tivoli team has to do for receiving traps? It is possible for you to share the setup document? you can send it to me on [email protected]
    Thanks for ur help.
    Pavan

  • BGP Peer down monitoring through SNMP Traps

    Hello,
    I'm trying to figure out how I can monitor with BGP peer went down using SNMP traps or any other methods that are out there. Basically I would like to get a trap that tells me the IP address of the peer that went down.
    Looking over the SNMP MIBs for BGP all i can find is snmp traps that tell me there was a change in states in BGP, but don't say which neighbor.
    Is there any way to get such information? Would I have to use EEM with some script? This seems like a very common thing that people would want to know.
    Thank you in advance,
    Tom

    SNMP notifications can be configured on the router and GET operations can be performed from an external management station only after BGP SNMP support is enabled.
    SUMMARY STEPS
    1. enable
    2. configure terminal
    3. snmp-server enable traps bgp [state-changes {[all] [backward-trans] [limited]}] | [threshold prefix]
    4. exit

  • Questions on Receiving SNMP Traps

    Hi:
    - I have more questions on receiving SNMP traps:
    1) the OEM plug-in can receive traps now, but when I click the metric, I see:
    Error getting data for target test20. Exception: ORA-20216: ORA-06512: at "SYSMAN.EMD_MNTR", line 817 ORA-01403: no data found ORA-06512: at line 1
    - the push descriptor looks like:
    <PushDescriptor RECVLET_ID="SNMPTrap">
    <Property NAME="MatchEnterprise" SCOPE="GLOBAL">...</Property>
    <Property NAME="MatchGenericTrap" SCOPE="GLOBAL">6</Property> <Property NAME="MatchSpecificTrap" SCOPE="GLOBAL">31</Property> <Property NAME="MatchAgentAddr" SCOPE="INSTANCE">target_ip</Property>
    <Property NAME="EventsnChasFanIndexOID" SCOPE="GLOBAL">...</Property>
    <Property NAME="ContextsnChasFanDescriptionOID" SCOPE="GLOBAL">...</Property>
    <Property NAME="SeverityCode" SCOPE="GLOBAL">WARNING</Property>
    </PushDescriptor>
    - is the Key Property needed ?
    2) The alerts for some reason do not filter back to the all targets home page.
    - When I click the Home tab and goto to the 'All Targets' pane, I do not see the alert generated by the OEM plug-in.
    - What I am doing wrong ?
    3) Is it okay to receive traps with the metric usage set to either: HIDDEN or HIDDEN_COLLECT ?
    - Does this cause the errors I see in Q 1) ?
    Thanks
    John
    Edited by: user8826739 on Feb 23, 2010 7:05 AM

    Hi John,
    Can you post the full definition of the metric? You would need to use the Key property for each key column in the metric description.
    With the SNMP receivelet you can set up definitons for data points or alerts. I would assume (as I've never tried this ;) that if you set up the definition to be a data point, you would see data from the All Metrics page. To me, it wouldn't make sense for a metric that used the PushDescriptor SNMPTrap to have data to be viewed as the result of the SNMP trap coming is would be an alert. I will have to look into that. My gut reaction is that a metric with PushDescriptor SNMPTrap shouldn't even appear on the All Metrics page ...
    To be clear are you saying that you don't see the Warning number under "All Targets Alerts" increase by 1 when you SNMP trap is caught and alert is generated? When this occurs do you see the alert on the target instance homepage?
    In regards to HIDDEN and HIDDEN_COLLECT, I don't know what effect they would have on a metric defined for an SNMP trap to raise an alert. You definitely wouldn't want to use HIDDEN as this setting is for temporary metrics that are used in the caclulation of other metrics. HIDDEN metrics are not collected (or hence uploaded to the OMS) and don't appear in the UI. HIDDEN_COLLECT are collected, but do not show up in the UI and are not uploaded. I've never used this settings with SNMP trap metrics that are for alerts. If your metrics for the SNMP trap alerts do show up on the All Metrics page (I'd have to get something set up to look at this), then it could make sense to use the HIDDEN_COLLECT as the alert would still be generated, but the metric itself wouldn't be shown in the UI.
    Let me find out the expected behavior from someone on the agent team.
    Dave

  • SNMP traps from Solaris 10

    Hi,
    I'm trying very hard to set up a Sun Fire V245 to send SNMP traps when certain hardware or software related events occur. I've been looking at sma_snmp (net-snmp) and the Fault Management Daemon (SUNWfmd) but they seem to be very limited in their capabilities. I have manged to get some traps sent for filesystem fill-ups and high load averages but that is about it.
    Most of all I would like the system to send traps when there is a HW failure such as a faulty FRU or if there are disk failures.
    If anyone can point me to some documentation about this, I would be most grateful.
    /Mikael

    Mikael,
    I struggled through the same thing with a Netra 240 recently. The Sun docs are garbage when it comes to this. I opened a ticket with Sun and after 3 days and 6 hours on the phone I finally got hold of someone who knew how to spell SNMP. Yes, it was that bad!
    Here's the scoop. In Solaris 10 you run Net-SNMP, a.k.a. SMA, snmpd. The old snmpdx is obsoleted and you shouldn't configure it at all.
    Now to get the hardware related traps for the Sunfire and Netra series servers... (what you are really looking for).
    You have to load and configure an additional SNMP daemon for the hardware specific traps.
    (The first doc is rather old, the last one 819-7978-12 is pretty new and is somewhat more relevant.)
    Sun� SNMP Management Agent for Sun Fire� and Netra� Systems: Sun Doc number 817-2559-13
    Sun� SNMP Management Agent Addendum for the Netra� 240 Server: Sun Doc Number 817-6238-10
    Sun� SNMP Management Agent Administration Guide for Sun Blade� /Sun Fire�/Sun SPARC� Enterprise/Netra� Servers: Sun Doc Number 819-7978-12
    And finally the SMA/net-snmp/snmpd guide for the standard Solaris related traps:
    Solaris System Management Agent Administration Guide: Sun Doc Number 817�3000�11
    There are problems with all of the above documents. None of the Netra/Sunfire docs specifically talk about Solaris 10 so read them with caution. They also talk about configuring and running snmpdx and never reference SMA/net-snmp. This is odd because the instructions I got from Sun (finally) were not to run snmpdx, only to run sma/snmpd and additionally run the sunfire/netra snmpd agent.
    The SMA document (817-3000-11) has an undocumented bug, which Sun knows about and is working on but will not reveal to the public. In the section titled "Migration From the Sun Fire Management Agent" it references using a script called masfcnv to convert the sunfire/netra specific snmp config and daemon to work with and through SMA. Since they all use the same ports (161/162) there is some conflict and the masfcnv is script is meant to resolve this by making sma/snmpd a proxy agent to requests toward the sunfire/netra specific hardware daemon.
    The problem is the masfcnv script doesn't work properly. In fact, if you run the script you will destroy your other snmp configurations and may have to uninstall and reinstall the packages to clean everything up. This script hasn't ever worked and Sun is working on a fix but they neglect to mention this in the document which is IMO gross negligence and is a reflection of Sun's overall state of affairs (but that's another ranting thread).
    So what you must do is configure SMA/net-snmp (or whatever you want to call it), and also configure the sunfire/netra specific snmp (after downloading and installing that package).
    Since traps are sent to the remote trapsink using destination port 162, both net-snmp and the netra specific snmp daemons can co-exist here (port 162 is not an open listening port on the machine).
    Port 161 is used for receiving SNMP Get requests and can only be bound to one daemon at a time. So either it is used by net-snmp or the netra snmp daemon, but not both. Since my boxes have not been fully integrated still I can't figure out which daemon 161 is bound to. At any rate, in my application the customer is only interested in receiving traps so the outcome here isn't that important.
    I realize this isn't complete but I'm no expert here and haven't worked through all the test scenarios on a fully configured system. Hopefully though this will help clear some of the confusion propogated through Sun's stupid documents. Good luck!
    /Frank

  • SCOM 2012 SNMP Trap - Does anyone have it working?

    I am wondering if anyone out there has had any luck with getting SNMP Traps to be captured by SCOM 2012?  Probes work fine.
    We have been unable to get SCOM 2012 to receive a SNMP Trap from network devices.  We currently have a case open with Microsoft, but they dont have any answers as of yet.
    Here are the cliff notes version of what we have done so far.
    Discovery - OK
    The nodes discover without issue.  I made sure they were set to SNMP only.  I did this to verify we were talking SNMP and not just ICMP.
    Open Ports/Firewall Issues
    No firewalls are in place on the SCOM server and none exist between devices we are trying to get traps from.  Using a port tool, I can see that UDP 162 is listening as expected and its the System Center Management Host Process that is running the
    process.  We have tried having SNMP installed, but disabled, installed and running, and uninstalled.  Currently we have the SNMP service installed and running.  The SNMP Trap Service is NOT installed.
    Data Validation
    Using Wireshark running on the SCOM box I have been able to validate the OIDs we are searching for are hitting the SCOM server.  I installed an SNMP Trap generator and Receiver on my local machine as well as Jalasoft SNMP Simulator.  I was able
    to discover my local machine as a network device and if I send a TRAP from the TRAP generator on my local machine to the receiver on my local machine I can validate the data is coming through ok.
    What has been done on SCOM side
    The simplest place to look for data is with an Event Collection Rule and then an Event View Monitor.  We have set up an Event Based Monitor to search for an OID that I know to be accurate and then I set up an Event monitor to look for
    anything hitting that Collection Rule.  The Event monitor showed nothing so we changed the EVent Monitor to look for anything that hit Node which should show any SNMP traps that have hit from network devices.  No results.
    We tried to run WFAnalyzer from the 2007R2 Authoring Console, but it wont run against 2012 and from what I have found the 2012 edition doesnt exist anywhere yet.
    So has anyone succesfully received a SNMP TRAP into SCOM 2012?

    Hi,
    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.
    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
    Thanks,
    Yog Li
    TechNet Community Support
    How could you possibly mark this as answered? No answer was given, it was quiet for a couple of days including one of which was a holiday in the US. The previous steps are NOT helpful.  The question remains, Does anyone have it working?
    People have given troubleshooting advice, but nobody has actually answered the simple question.  Do they have it actually WORKING?

  • SNMP Trap Translation Wrong For Hebrew Language

    SR 3-4956842281
    sev 2
    Cus ISRAEL CREDIT CARDS LTD
    =====================
    Customer is using OMS 10.2.0.5 on linux server.
    They have created an user defined metric on DB cluster instance with alert message written in hebrew.
    The OMS console showed the alert in hebrew as expected.
    However when they send this alert with snmp trap notification to a second system (HP openview for windows) then the message appeared not cleared (with question marks). This second system get messages in hebrew from other systems without any problems.
    +Does setting LANG variable at OMS level will impact this
    +Any tracing which can help to find the cause of the issue                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Closing as issue found at HP openview parameter settings

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

  • SNMP trap on OutOfMemory Error Log record

    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

    Andriy,
    I dont think you could do much here, since Outofmemory is not part of
    log record SNMP agent cannot filter on this. I would be curious to hear
    if anyone got it to work using SNMP.
    sorry,
    -satya
    Andriy Potapov wrote:
    I would like to implement SNMP trap on OutOfMemory Error Log record.
    In theory SNMP LogFilter with Severity Level "Error" and Message Substring "OutOfMemory" should do the trick.
    In reality it does not work (doh)(see explanations below), I wonder if someone managed to make it work.
    Log entry has following format:
    ----------- entry begin ----------
    ####<Nov 12, 2003 3:09:23 PM EST> <Error> <HTTP> <ustrwd2021> <local> <ExecuteThread: '14' for queue: 'default'> <> <> <101020> <[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>
    java.lang.OutOfMemoryError
         <<no stack trace available>>
    ------------ entry end ------------
    Notice that java.lang.... is NOT part of the log record, yep it seems that exception stack trace is not part of log record! Thus filter could be applied only to "<[WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception>" string, which is really useless.
    Here is fragment of trap data (i had to remove Message Substring in order to get Error trap to work)
    1.3.6.1.4.1.140.625.100.50: trapLogMessage: [WebAppServletContext(747136,logs2,/logs2)] Servlet failed with Exception

Maybe you are looking for