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

Similar Messages

  • 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

  • Error messages during BC Activation.

    Hi Friends,
    I have the following warning messages during activation of BC. All the below mentioned DS are active and replicated to BI.
    Any help is appreciated.
    Installation (simulation mode) of: Transfer Rules (ISMP)                              
    Transfer rules 0ART_PLANT_ATTR RD2CLNT030                              
    Filtering fields                              
    Field AUSDT not delivered by source system -> Deleted from rule                              
    Field BEARZ not delivered by source system -> Deleted from rule                              
    Field BWSCL not delivered by source system -> Deleted from rule                              
    Field DISMM not delivered by source system -> Deleted from rule                              
    Field DISPO not delivered by source system -> Deleted from rule                              
    Field DZEIT not delivered by source system -> Deleted from rule                              
    Field EKGRP not delivered by source system -> Deleted from rule                              
    Field FEVOR not delivered by source system -> Deleted from rule                              
    Field KOKRS not delivered by source system -> Deleted from rule                         
    Field LVORM not delivered by source system -> Deleted from rule                         
    Field LZEIH not delivered by source system -> Deleted from rule                         
    Field MAABC not delivered by source system -> Deleted from rule                         
    Field MATNR not delivered by source system -> Deleted from rule                         
    Field MAXLZ not delivered by source system -> Deleted from rule                         
    Field PERIV not delivered by source system -> Deleted from rule                         
    Field PLIFZ not delivered by source system -> Deleted from rule                         
    Field PLNNR not delivered by source system -> Deleted from rule                         
    Field PLNTY not delivered by source system -> Deleted from rule                         
    Field PLVAR not delivered by source system -> Deleted from rule                         
    Field PRCTR not delivered by source system -> Deleted from rule                         
    Field RUEZT not delivered by source system -> Deleted from rule                         
    Field SERVG not delivered by source system -> Deleted from rule                         
    Field TRANZ not delivered by source system -> Deleted from rule                         
    Field VBEAZ not delivered by source system -> Deleted from rule                         
    Field WEBAZ not delivered by source system -> Deleted from rule                         
    Field WERKS not delivered by source system -> Deleted from rule                         
    Field WZEIT not delivered by source system -> Deleted from rule                         
    Transfer rules 0DISMM_ATTR RD2CLNT030                         
    Filtering fields                         
    Field DISMM not delivered by source system -> Deleted from rule                         
    Field DISVF not delivered by source system -> Deleted from rule                         
    Transfer rules 0DISMM_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Transfer rules 0MAT_PLANT_ATTR RD2CLNT030                         
    Filtering fields                         
    Field AUSDT not delivered by source system -> Deleted from rule                         
    Field BEARZ not delivered by source system -> Deleted from rule                         
    Field BWSCL not delivered by source system -> Deleted from rule                         
    Field DISMM not delivered by source system -> Deleted from rule                         
    Field DISPO not delivered by source system -> Deleted from rule                         
    Field DZEIT not delivered by source system -> Deleted from rule                         
    Field EKGRP not delivered by source system -> Deleted from rule                         
    Field FEVOR not delivered by source system -> Deleted from rule                         
    Field KOKRS not delivered by source system -> Deleted from rule                         
    Field LVORM not delivered by source system -> Deleted from rule                         
    Field LZEIH not delivered by source system -> Deleted from rule                         
    Field MAABC not delivered by source system -> Deleted from rule                         
    Field MATNR not delivered by source system -> Deleted from rule                         
    Field MAXLZ not delivered by source system -> Deleted from rule                         
    Field PERIV not delivered by source system -> Deleted from rule                         
    Field PLIFZ not delivered by source system -> Deleted from rule                         
    Field PLNNR not delivered by source system -> Deleted from rule                         
    Field PLNTY not delivered by source system -> Deleted from rule                         
    Field PRCTR not delivered by source system -> Deleted from rule                         
    Field RUEZT not delivered by source system -> Deleted from rule                         
    Field SERVG not delivered by source system -> Deleted from rule                         
    Field TRANZ not delivered by source system -> Deleted from rule                         
    Field VBEAZ not delivered by source system -> Deleted from rule                         
    Field WEBAZ not delivered by source system -> Deleted from rule                         
    Field WERKS not delivered by source system -> Deleted from rule                         
    Field WZEIT not delivered by source system -> Deleted from rule                         
    Transfer rules 0MAT_PLANT_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field KEY2 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Transfer rules 0MRP_CONTRL_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field KEY2 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTLG not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Field TXTSH not delivered by source system -> Deleted from rule                         
    Transfer rules 0PRODSCHED_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field KEY2 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTLG not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Field TXTSH not delivered by source system -> Deleted from rule                         
    Transfer rules 0PUR_GROUP_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field TXTSH not delivered by source system -> Deleted from rule                         
    Transfer rules 0RT_DEPARTM_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Transfer rules 0RT_PURCHAR_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Transfer rules 0RT_SERVLEV_TEXT RD2CLNT030                         
    Filtering fields                         
    Field KEY1 not delivered by source system -> Deleted from rule                         
    Field LANGU not delivered by source system -> Deleted from rule                         
    Field TXTMD not delivered by source system -> Deleted from rule                         
    Transfer rules 2LIS_04_P_MATNR RD2CLNT030                         
    Filtering fields                         
    Field AUFNR not delivered by source system -> Deleted from rule                         
    Field BUDAT not delivered by source system -> Deleted from rule                         
    Field BUKRS not delivered by source system -> Deleted from rule                         
    Field DFZEH not delivered by source system -> Deleted from rule                         
    Field DFZEXEH not delivered by source system -> Deleted from rule                         
    Field ERDAT not delivered by source system -> Deleted from rule                         
    Field ETRMP not delivered by source system -> Deleted from rule                         
    Field FA_GLFT not delivered by source system -> Deleted from rule                         
    Field FTRMI not delivered by source system -> Deleted from rule                         
    Field FTRMP not delivered by source system -> Deleted from rule                         
    Field FTRMS not delivered by source system -> Deleted from rule                         
    Field GETRI not delivered by source system -> Deleted from rule                         
    Field GLTRP not delivered by source system -> Deleted from rule                         
    Field GLTRS not delivered by source system -> Deleted from rule                         
    Field GSTRI not delivered by source system -> Deleted from rule                         
    Field GSTRP not delivered by source system -> Deleted from rule                         
    Field GSTRS not delivered by source system -> Deleted from rule                         
    Field IAMNG not delivered by source system -> Deleted from rule                         
    Field I_DFZ not delivered by source system -> Deleted from rule                         
    Field I_DFZ_EX not delivered by source system -> Deleted from rule                         
    Field I_DLZ not delivered by source system -> Deleted from rule                         
    Field I_DLZ_EX not delivered by source system -> Deleted from rule                         
    Field KDAUF not delivered by source system -> Deleted from rule                         
    Field KEINH not delivered by source system -> Deleted from rule                         
    Field KSUMS not delivered by source system -> Deleted from rule                         
    Field LEAD_AUFNR not delivered by source system -> Deleted from rule                         
    Field LEAD_MATNR not delivered by source system -> Deleted from rule                         
    Field LTRMI not delivered by source system -> Deleted from rule                         
    Field LTRMP not delivered by source system -> Deleted from rule                         
    Field MATNR not delivered by source system -> Deleted from rule                         
    Field MAUFNR not delivered by source system -> Deleted from rule                         
    Field MEINS not delivered by source system -> Deleted from rule                         
    Field PAMNG not delivered by source system -> Deleted from rule                         
    Field PGMNG not delivered by source system -> Deleted from rule                         
    Field PI_FREI not delivered by source system -> Deleted from rule                         
    Field PI_LIEF not delivered by source system -> Deleted from rule                         
    Field PI_STAR not delivered by source system -> Deleted from rule                         
    Field POSNR not delivered by source system -> Deleted from rule                         
    Field PSAMG not delivered by source system -> Deleted from rule                         
    Field PSMNG not delivered by source system -> Deleted from rule                         
    Field PS_FREI not delivered by source system -> Deleted from rule                         
    Field PS_LIEF not delivered by source system -> Deleted from rule                         
    Field PS_STAR not delivered by source system -> Deleted from rule                         
    Field PWERK not delivered by source system -> Deleted from rule                         
    Field P_DLZ not delivered by source system -> Deleted from rule                         
    Field ROCANCEL not delivered by source system -> Deleted from rule                         
    Field SI_FREI not delivered by source system -> Deleted from rule                         
    Field SI_LIEF not delivered by source system -> Deleted from rule                         
    Field SI_STAR not delivered by source system -> Deleted from rule                         
    Field STRMP not delivered by source system -> Deleted from rule                         
    Field S_DFZ not delivered by source system -> Deleted from rule                         
    Field S_DFZ_EX not delivered by source system -> Deleted from rule                         
    Field S_DLZ not delivered by source system -> Deleted from rule                         
    Field S_DLZ_EX not delivered by source system -> Deleted from rule                         
    Field WEMNG not delivered by source system -> Deleted from rule                         
    Field WERKS not delivered by source system -> Deleted from rule                         
    Field ZEITP not delivered by source system -> Deleted from rule                         
    Transferring the 12 objects from type ISMP took 0.0 seconds                         
    Thanks,
    VBR

    Hi,
    I do not know exactly why it happened but do the following things
    Rsa5-install the bc datasource and transfer
    and do u wat to customise customise at LBWE
    then replicate at bw here it asks thorough either transformations or infosource may be ur selected through transformations there u should map the field and object may this thing u r not done pls check as above.
    thanks
    sathish

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

  • 3750 sw is not sending SSH login failure SNMP trap

    Hi experts,
    I want to make my switch send trap when failed SSH login is detected. I found the "login Enhancement" feature and enabled the trap and logging for the failed attempt.
    3750# sh run | in login
    aaa authentication login default local
    login delay 1
    login on-failure
    3750# sh login
         A login delay of 1 seconds is applied.
         No Quiet-Mode access list has been configured.
         All failed login is logged and generate SNMP traps.
         Router NOT enabled to watch for login Attacks
    Then I enabled all the traps except the one for the syslog (because I don't want all the log messages are sent as SNMP traps...)
    (config)# snmp-server enable traps
    (config)# no snmp-server enable traps syslog
    (config)# snmp-server host 10.1.1.1 mysnmpkey
    Now when I try to login with incorrect password I do see the log but I don't receive the trap...
    Nov 23 12:39:27: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: admin] [Source: 10.1.1.1] [localport: 22] [Reason: Login Authentication Failed] at 12:39:27 EST Wed Nov 23 2011
    Of course when I enable the "syslog" trap I see something but that's more just for this log message
    Any idea why??
    My 3750-24TS-E is running
    Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE3, RELEASE SOFTWARE (fc1)
    Thanks!
    Difan

    Hey Smitesh thanks for the reply. However my switch doesn't support the aaa_server trap...
    #snmp-server enable traps ?
      auth-framework    Enable SNMP CISCO-AUTH-FRAMEWORK-MIB traps
      bgp               Enable BGP traps
    Mine is a 3750 switch. Is this command for routers?
    Thanks,
    Difan

  • LMS 3.2 snmp trap forwardig to HP-open view

    Hi,
    I want to forward snmp traps from cisco LMS to HP-open view. Both applications are installed on different servers.
    From previous post in this forum, I found a similar post that recommand using snmp forwording in DFM.
    What I want to know is do I need any integration or packages to install on both platforms to do this? Also, will DFM forward all traps that it receives from installed devices or it will forward some of them.
    Thank you
    BR,
    ZS

    Chris;
       current version of Java is 1.6.0 Update 20
    Additional information to the issue:  a WS-C3750 has been discovered (connected to another 6509 that is running hybrid) and added to the topology map as it one would expect.
    craig

  • 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

  • Error during activation a message mapping

    Hi,
    I get this error during activation a message mapping:
    source code has an syntax error:
    D:/usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapf1f9db20a78a11dac004000f1ff80130/source/com/sap/xi/tf/_Source2Target_.java:2: package com.sap.aii.mappingtool.tfapi does not exist import com.sap.aii.mapping.api.; import com.sap.aii.mappingtool.tfapi.; ^ 1 error
    Can anybody help me please??
    Thanks.
    Regards
    Stefan

    Hi Michal,
    I do not have deleted some libraries in the XI-Installation.
    I have some customer functions in other mappings but no message mapping without or with customer function can I activate, now.
    The mappings are in serveral software components but it is no chance to activate a message mapping.
    Regards,
    Stefan

  • HT4623 Cannot sign in on my iPad with Apple ID and password.  Everything is correct, but I keep getting a message that an error occurred during activation.  Try again.

    Any help?  I am unable to change my settings because my iPad is not recognizing my Apple ID and password.  Everything is correct,but I keep getting the message that an error occurred during activation.  Try Again.
    Thank you!

    Try this. Go to Settings>General>Date & Time>Set Automatically>On. Make sure that the time zone setting is also correct.

  • Can't sign in to messages on iPad mini says an error occurred during activation try again

    An error occurred during activation try again comes up when I try to sign in to messages on my iPad

    Hi krissi182,
    If you are having difficulties with activation when using Messages on your iPad mini, you may want to follow the steps in this article -
    iOS: Troubleshooting FaceTime and iMessage activation
    http://support.apple.com/kb/TS4268
    Thanks for using Apple Support Communities.
    Best,
    Brett L

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

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

  • Regarding my facetime and imessage i cant get it acctivated its giving me a message "An error occurred during activation. Try Again" .. i already done reset on network settings i've already tried to turn on and off my setting.

    Pls help me on how i can activate my imessage and facetime. Ive already tried to reset my iphone, done turning my iphone on and off, done turning on and off my settings and also tried time zone as suggested by others also tried to change my DNS settings but still it doesnt activate it only gives me an error "An error occurred during activation. Try again".......Pls help me.. Thank you

    Its possible that the server can be down now. Have you ever used it before?  If you want, try resseting the phone by just holding the sleep/wake key and the home button together for 10 seconds.  Then wait 5 seconds when it turns off and press the sleep/wake button to turn it back on.  Then try it again.  Let me know what the results are.

  • 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

  • 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