Disable default snmp traps

Hello,
I am trying to disable the default snmp trap for x25. I tried to use the "no" form of the command (no snmp-server enable traps x25), but after typing:
no snmp-server enable traps ?
x25 is not even listed.
The other workaround was to specify exactly what type of traps I wanted to be sent to my snmp-server using the commands:
snmp-server host ip_address community flash tty snmp
(x25 was not included), but that didn't solve the problem.
Any assistance would be highly appreciated.
Regards,
Katerina

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.

Similar Messages

  • Disable snmp trap link-status only on access ports?

    Hello,
    I am searching for a way to disable the snmp trap link-status only on access ports.
    The problem is that we have a lot of new devices which have no port scheme, so I can't say that everytime the router uplink on a switch is on port X or Y.
    So I have to figure out where my uplinks to routers, accesspoints or other switches are and set all other ports to
    no snmp trap link-status
    no logging event link-status
    spanning-tree portfast
    Campus Manager knows the uplinks between the devices, but there is no way to perform such a change, right?
    The next problem is, that there is nothing configured on the ports, so I can't search for a string by using compliance check in RME.
    Is there any posibility to get the topology informations from CM together with the configuration feature from RME?
    Thanks a lot!
    Sven

    Hello,
    thanks for your reply.
    I thought of something like you wrote...
    There is a best practice report for disabling cdp on access ports.
    Creating this report for a switch and click on "fix" the CM will configure the command "no cdp enable" on every access port.
    So I will have a difference between uplinks and access ports.
    The problem with that solution is, that I can't fix all my switches with one job.
    And with >1000 switches it is not really possible to click every device.
    Any further advice?
    Thanks!
    Sven

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

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

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

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

  • Re-routing of SNMP traps from port 162 to port greater than 1024

    Hello,
    I have to re-route SNMP traps received at port 162 to some other port greater that 1024 (say 2041). There is an application which sends SNMP traps to port 162 and our application running on Windows listens for SNMP traps on port 2041, so we want
    to route/forward the traps internally from port 162 to 2041.
    I have been looking at the rules defined in 'Windows Firewall with advanced security' but not able to succeed. I noticed that there is a predefined rule for SNMP traps but it does not give me an option to forward the trap to another port. I tried
    creating a new rule but that also does not give me an option to change the port.
    Please help.

    Hi,
    According to Technet Library:
    SNMP uses the default UDP port 161 for general SNMP messages and UDP port 162 for SNMP trap messages. If these ports are being used by another protocol or service, you can change the settings by modifying the local Services file on the agent. The Services
    file is located in \ % SystemRoot %\System32\Drivers\Etc
    There is no file name extension. You can use any text - based editor to modify the file. The management system must also be configured to listen and send on the new ports.
    Caution:
    If you have previously configured IP security to encrypt SNMP messages on the default ports, you must also update the IP security policy with the new port settings. Otherwise, communication can be erroneously blocked or SNMP communications might not be secured.
    You can access to the link below for this article:
    http://technet.microsoft.com/en-us/library/cc959643.aspx
    Roger Lu
    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

  • 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

  • Configure SNMP Traps

    Hello,
    I am running SCOM 2012 R2 and I am trying to set up the server to receive SNMP traps from my HP Procurve switches.  I setup 1 switch to send all traps to my SCOM server.  The SNMP Feature is installed and the SNMP Trap service is disabled. 
    The SNMP Service is configured to the correct community and is setup to accept from all hosts.  I setup a rule that targets Nodes and I setup an Event View that uses this rule.  I trigger an alert on my switch and I see nothing in the Event
    View.  What am I doing wrong? 

    Hi,
    Im glad you got the SNMP working.
    You can either right-click an event, press Notification subscription and Create...
    You can also go to Administration and create it from there. The setup is pretty straight forward, but there are some guides here:
    http://blogs.technet.com/b/kevinholman/archive/2012/04/28/opsmgr-2012-configure-notifications.aspx
    http://technet.microsoft.com/en-us/library/hh212805.aspx
    www.coretech.dk - blog.coretech.dk

  • BGP snmp trap on XR OS

    We are trying to test the snmp trap on IOS-XR for BGP up down, but ASR didn't send out any traps when we brought down the BGP neighbour. When we tested the OSPF, it worked fine. I also tried to use command 'snmp test' to generate the test trap and I got following message, The version is 4.2. Any suggestions? Thanks.
    RP/0/RSP0/CPU0:Feb 22 13:58:20.691 : test_trap[65889]: Debug init Done
    RP/0/RSP0/CPU0:Feb 22 13:58:21.083 : test_trap[446]: Trap ID: 28
    RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: make_test_traps: input args 0x0 0x0 (null) (null)
    Failed to format BGP Trap
    RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: get_first_bgp_peer_index: Getting first BGP Peer
    RP/0/RSP0/CPU0:Feb 22 13:58:21.104 : test_trap[446]: get_first_bgp_peer_index: Failed to get BGP indices
    Current config:
    snmp-server host x.x.x.x traps version 2c xxxxxx
    snmp-server community encrypted xxxx RO
    snmp-server community encrypted yyyy RW
    snmp-server traps rf
    snmp-server traps bgp cbgp2
    snmp-server traps bgp
    snmp-server traps ospf state-change neighbor-state-change
    snmp-server packetsize 1024
    snmp-server trap-source MgmtEth0/RSP0/CPU0/0
    snmp-server ifindex persist
    Regards. Leo

    Hi,
    I am running 4.2.3 and seems like trap generated.  also see the snm-server traps bgp commands in running config.
    RP/0/RSP0/CPU0:PE2#show vrf mse_1001 detail
    Mon Feb 25 14:58:29.027 PST
    VRF mse_1001; RD 65002:1001; VPN ID not set
    VRF mode: Regular
    Description not set
    Interfaces:
      GigabitEthernet0/3/0/0.1001
    Address family IPV4 Unicast
      Import VPN route-target communities:
        RT:65001:1001
      Export VPN route-target communities:
        RT:65001:1001
      No import route policy
      No export route policy
    Address family IPV6 Unicast
      Import VPN route-target communities:
        RT:65001:1001
      Export VPN route-target communities:
        RT:65001:1001
      No import route policy
      No export route policy
    RP/0/RSP0/CPU0:PE2#show ipv4 vrf mse_1001 interface brief
    Mon Feb 25 14:59:16.154 PST
    Interface                      IP-Address      Status                Protocol
    GigabitEthernet0/3/0/0.1001    101.1.1.1       Up                    Up     
    RP/0/RSP0/CPU0:PE2#term mon
    Mon Feb 25 14:59:33.803 PST
    RP/0/RSP0/CPU0:PE2#conf t
    Mon Feb 25 14:59:34.894 PST
    RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001
    RP/0/RSP0/CPU0:PE2(config-subif)#shut
    RP/0/RSP0/CPU0:PE2(config-subif)#commit
    Mon Feb 25 14:59:46.480 PST
    LC/0/3/CPU0:Feb  25 14:59:46.617 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE :  Adjacency to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001  was deleted
    RP/0/RSP0/CPU0:Feb 25 14:59:46.621 : bgp[1048]:  %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Down - Admin. shutdown  (VRF: mse_1001)
    RP/0/RSP1/CPU0:Feb 25 14:59:46.620 : bgp[1048]:  %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor  101.1.1.2 on standby due to Admin. shutdown (VRF: mse_1001)
    RP/0/RSP0/CPU0:Feb  25 14:59:46.626 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor  1011:1:1::2 Down - Admin. shutdown (VRF: mse_1001)
    RP/0/RSP1/CPU0:Feb 25 14:59:46.622 : bgp[1048]:  %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor  1011:1:1::2 on standby due to Admin. shutdown (VRF: mse_1001)
    LC/0/3/CPU0:Feb 25 14:59:46.719 : bfd_agent[124]:  %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor 1011:1:1::2 on  interface GigabitEthernet0/3/0/0.1001 was deleted
    LC/0/3/CPU0:Feb 25 14:59:47.294 : bfd_agent[124]:  %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 1011:1:1::2 on  interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Control  timer expired
    LC/0/3/CPU0:Feb 25 14:59:47.401 : bfd_agent[124]:  %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 101.1.1.2 on  interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Nbor  signalled down
    RP/0/RSP0/CPU0:Feb 25 14:59:47.513 : config[65903]:  %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use  'show configuration commit changes 1000000208' to view the changes.
    RP/0/RSP0/CPU0:PE2(config-subif)#RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.2 qlen:0
    RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:bgp.0.2 qlen:1
    RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:2
    RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:3
    RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4
    RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5
    RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:6
    RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:7
    RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:8
    RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.2
    RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap bgp.0.2
    RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8
    RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6
    RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.1
    RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8
    RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6
    RP/0/RSP0/CPU0:Feb 25 14:59:47.640 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:PE2(config-subif)#
    RP/0/RSP0/CPU0:PE2(config-subif)#end
    RP/0/RSP0/CPU0:Feb 25 14:59:55.901 : config[65903]:  %MGBL-SYS-5-CONFIG_I : Configured from console by lab on vty0  (223.255.254.249)
    RP/0/RSP0/CPU0:PE2#show snmp trap
    Mon Feb 25 14:59:59.901 PST
    TrapOID                                  Number of Times
    bgp.0.2                                  1                       
    ciscoBgp4MIB.0.1                         1                       
    ciscoBgp4MIB.0.2                         1                       
    ciscoBgp4MIB.0.6                         2                       
    ciscoBgp4MIB.0.7                         2                       
    ciscoBgp4MIB.0.8                         2                       
    RP/0/RSP0/CPU0:PE2#show running-config snmp-server
    Mon Feb 25 15:00:20.221 PST
    snmp-server vrf mse_1001
    context public
    snmp-server community public RW
    snmp-server traps bgp cbgp2
    snmp-server traps bgp
    snmp-server traps vrrp events
    snmp-server ifindex persist
    RP/0/RSP0/CPU0:PE2#conf t
    Mon Feb 25 15:02:35.935 PST
    RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001
    RP/0/RSP0/CPU0:PE2(config-subif)#no shut
    RP/0/RSP0/CPU0:PE2(config-subif)#commit
    Mon Feb 25 15:02:42.609 PST
    RP/0/RSP0/CPU0:Feb 25 15:02:43.369 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Up (VRF: mse_1001)
    RP/0/RSP0/CPU0:Feb  25 15:02:43.606 : config[65903]: %MGBL-CONFIG-6-DB_COMMIT :  Configuration committed by user 'lab'. Use 'show configuration commit  changes 1000000209' to view the changes.
    RP/0/RSP0/CPU0:PE2(config-subif)#LC/0/3/CPU0:Feb  25 15:02:44.223 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD  session to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001  is up
    RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:0
    RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:2
    RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:3
    RP/0/RSP0/CPU0:Feb 25 15:02:44.288 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4
    RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5
    RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:bgp.0.1 qlen:6
    RP/0/RSP0/CPU0:Feb 25 15:02:44.290 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:7
    RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:8
    RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:9
    RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap bgp.0.1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5
    RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
    RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:PE2(config-subif)#
    RP/0/RSP0/CPU0:PE2(config-subif)#end  
    RP/0/RSP0/CPU0:Feb  25 15:02:48.825 : config[65903]: %MGBL-SYS-5-CONFIG_I : Configured from  console by lab on vty0 (223.255.254.249)
    RP/0/RSP0/CPU0:PE2#conf tRP/0/RSP0/CPU0:Feb 25 15:02:49.418 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0
    RP/0/RSP0/CPU0:Feb 25 15:02:49.419 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1
    RP/0/RSP0/CPU0:Feb 25 15:02:49.420 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 15:02:49.421 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    show  running-config snmp-server RP/0/RSP0/CPU0:Feb 25 15:02:50.510 :  bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 1011:1:1::2 Up (VRF:  mse_1001)
    show snmp trapLC/0/3/CPU0:Feb 25 15:02:51.046 :  bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor  1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 is up
    RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0
    RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:1
    RP/0/RSP0/CPU0:Feb 25 15:02:51.517 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:2
    RP/0/RSP0/CPU0:Feb 25 15:02:51.519 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5
    RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
    Mon Feb 25 15:02:54.118 PST
    TrapOID                                  Number of Times
    bgp.0.1                                  1                       
    bgp.0.2                                  1                       
    ciscoBgp4MIB.0.1                         5                       
    ciscoBgp4MIB.0.2                         1                       
    ciscoBgp4MIB.0.5                         2                       
    ciscoBgp4MIB.0.6                         2                       
    ciscoBgp4MIB.0.7                         10                      
    ciscoBgp4MIB.0.8                         2                       
    RP/0/RSP0/CPU0:PE2#
    Thanks
    Parthiv

  • Generate SNMP TRAP when config changes

    Hello,
    Is there any way to generate a SNMP trap when new config is saved in ASA 5510?
    We are running ASA 8.3
    Thanks.

    I have a clue about how to do it.
    I use in the asa the fallowing command:
    snmp-server host DMZ 10.153.50.5 community *****snmp-server enable traps entity config-change fru-insert fru-remove
    And I setup a snmptrapd on a lin
    /etc/snmp/snmptrapd.conf# Example configuration file for snmptrapd## No traps are handled by default, you must edit this file!# authCommunity   log,execute,net public# traphandle SNMPv2-MIB::coldStart    /usr/bin/bin/my_great_script coldux box.
    But it doesn´t works when I do a config change, it doesn´t generate anything on the linux box log.
    Any idea?
    Thanks.

  • 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

  • How to set the DCM snmp trapping to a customized port

    Hi There,
    Anyone know how to set the DCM SNMP trapping to a customized port?
    The default port for SNMP should be 162 while my OSS team requies it be set as a customized port number for load balancing. Can't find a clue in the manual, any idea?
    Thanks,

    Hi Kim,
    The DCM only support the standard SNMP port.
    Regards,
    Ray

Maybe you are looking for