Enable snmp traps on Nexus1000V

Hello community,
I have the following issue. I want to configure snmp-traps regarding stpx (root-inconsistency, loop-inconsistency) on a Cisco Nexus 1000V.
The command "show snmp traps" lists stpx as a trap that could be configured and which is not at the moment.
MKBE1NX1# sh snmp trap
Trap type                                           Enabled
entity               : entity_mib_change               Yes         
entity               : entity_module_status_change     Yes         
entity               : entity_power_status_change      Yes         
entity               : entity_module_inserted          Yes         
entity               : entity_module_removed           Yes         
entity               : entity_unrecognised_module      Yes         
entity               : entity_fan_status_change        Yes         
entity               : entity_power_out_change         Yes         
link                 : linkDown                        Yes         
link                 : linkUp                          Yes         
link                 : extended-linkDown               Yes         
link                 : extended-linkUp                 Yes         
link                 : cieLinkDown                     No          
link                 : cieLinkUp                       No          
link                 : connUnitPortStatusChange        Yes         
rf                   : redundancy_framework            Yes         
aaa                  : server-state-change             No          
license              : notify-license-expiry           Yes         
license              : notify-no-license-for-feature   Yes         
license              : notify-licensefile-missing      Yes         
license              : notify-license-expiry-warning   Yes         
zone                 : unsupp-mem                      No          
upgrade              : UpgradeOpNotifyOnCompletion     No          
upgrade              : UpgradeJobStatusNotify          No          
feature-control      : FeatureOpStatusChange           No          
rmon                 : risingAlarm                     No          
rmon                 : fallingAlarm                    No          
rmon                 : hcRisingAlarm                   No          
rmon                 : hcFallingAlarm                  No          
config               : ccmCLIRunningConfigChanged      No          
snmp                 : authentication                  No          
bridge               : topologychange                  No          
bridge               : newroot                         No          
stp                  : inconsistency                   No          
stpx                 : loop-inconsistency              No          
stpx                 : root-inconsistency              No   
The only snmp traps that can be configured on the system are:
aaa              Module notifications enable
  config           Module notifications enable
  entity           Module notifications enable
  feature-control  Module notifications enable
  license          Module notifications enable
  link             Module notifications enable
  rf               Module notifications enable
  rmon             Module notifications enable
  snmp             Module notifications enable
  upgrade          Module notifications enable
  zone             Module notifications enable
Nothing about stpx... Is there some other way to configure more traps?
Thanks in advance,
Katerina

Looks like you could be hitting CSCsz96130 "show snmp trap displays five unconfigurable types bridge / stpx" and it looks like support has been added starting 5.0(2)N1(1).

Similar Messages

  • Enabled SNMP trap

    Hi Experts,
    When i configure Snmp trap in switches it is showing a list of commands, What exacatly is these are?
    snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
    snmp-server enable traps tty
    snmp-server enable traps vtp
    snmp-server enable traps vlancreate
    snmp-server enable traps vlandelete
    snmp-server enable traps stpx
    snmp-server enable traps port-security
    snmp-server enable traps config
    snmp-server enable traps entity
    snmp-server enable traps copy-config
    snmp-server enable traps fru-ctrl
    snmp-server enable traps flash insertion removal
    snmp-server enable traps syslog
    snmp-server enable traps bridge
    snmp-server enable traps envmon fan shutdown supply temperature status
    snmp-server enable traps hsrp
    snmp-server enable traps bgp
    snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message
    snmp-server enable traps ipmulticast
    snmp-server enable traps msdp
    snmp-server enable traps rtr
    snmp-server enable traps vlan-membership
    Does it cause more CPU utilization? Do i need to enable snmp traps to monitor network using solarwinds NPM. I have configured community string and snmpserver host address.
    Thanks
    Vipin

    Hi Vipin,
    We usually configure SNMP traps to monitor our network reachability and availability. If anything goes on Device whether it is a link down situation or any issue with protocol running on the Device. So, whenever anything goes wrong on the device it generates an SNMP Trap and notify you if you have configure SNMP-Server host to receive the notifications/traps.
    To configure SNMP host command following is the command that you need to configure:
    (config)#snmp-server host
    E.g.:
    snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
    Above trap will send you send you following information :
    >Authentication : if any one tries to poll the device using wrong community string
    >linkdown/linkup : if any of the interface/ports/links goes down it will notify you
    snmp-server enable traps bgp
    Above trap will send you traps regarding problems with BGP running on your Device
    Now I come to CPU part, yes it may spike CPU sometime if regular polling is done from the Management Server or if any MIB has long output. You can use Solarwinds NPM for the same however if it causes high cpu then you have to openup a TAC Case with NMS team to have the issue resolved.
    To know more about MIB's on your device you can execute command on your Device 'show snmp mib' and can translate the MIB's using following link to know more about particular MIB :
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.15
    Kindly let me know in case you have any other doubts.
    Thanks & Regards,
    Nikhil Gakhar

  • Enabling SNMP traps in WebLogic6.1

    I work with a WebLogic server ver 6.1, trying to use its SNMP capabilities.
    - I succeed in GET requests (I see it both in the manager and in the log)
    - The traps mechanism doesn't work at all (no traps are sent, at least according
    to the log, which is on highest debug level).
    I noticed that in the log there was a debug message saying "Trap targets enabled
    =0". I defined one target, and I can't find a way to enable it.
    Can you help?

    Deer lovely Nurit T.
    As U're probably know we in Kabul are specialize in those TRAPS that U're trying
    to put.
    I just wanted to clearify the U won't succeed in your mission even if with WLS
    17.5 version.
    Insha'ala that your project will crush and you company will be closed.
    BiLsalam Alecum Vu Rahmat ALLA.
    "Nurit T" <[email protected]> wrote:
    >
    I work with a WebLogic server ver 6.1, trying to use its SNMP capabilities.
    - I succeed in GET requests (I see it both in the manager and in the
    log)
    - The traps mechanism doesn't work at all (no traps are sent, at least
    according
    to the log, which is on highest debug level).
    I noticed that in the log there was a debug message saying "Trap targets
    enabled
    =0". I defined one target, and I can't find a way to enable it.
    Can you help?

  • How to enable the "SNMP TRAP" Funcation in Prime Infrasructure 2.0 for receiveing the Third Party Device's SNMP TRAP

    I already uploaded the third party device's MIB to PI2.0,  but could not recive the third party device's SNMP TRAP properly .
    what do I need check for the PI ? or what do I need to setup for the PI?
    Thanks

    Duplicate post of :
    https://supportforums.cisco.com/discussion/12148626/how-enable-snmp-trap-funcation-prime-infrasructure-20-receiveing-third-party
    -Thanks
    Vinod

  • What is the minimum server layer OEM version supports SNMP trap reception ?

    Hi:
    - I have been trying to enable SNMP trap reception on an OEM plug-in.
    - I turned on debug channel for recvlets.snmp and saw:
    2009-10-16 16:07:42,808 Thread-3028552624 ERROR recvlets.snmp: Duplicate threshold : test900, oracle_guide, interfaces, status
    and
    2009-10-16 16:09:08,382 Thread-3021634480 INFO recvlets.snmp: Trap received is to convert Data Point
    2009-10-16 16:09:08,379 Thread-3021634480 INFO recvlets.snmp: Sending Data Point ...
    2009-10-16 16:09:08,379 Thread-3021634480 INFO recvlets.snmp: Listening for TRAP
    So, it looks like the OEM agent can receive traps but no data point or alert appears.
    And, the agent always issues an error about duplicate thresholds.
    - Does the agent have to be patched ?
    My agent is:
    Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.5.0
    OMS Version : 10.2.0.1.0
    Protocol Version : 10.2.0.0.0
    Agent is Running and Ready
    - on the server layer, the oms is:
    Oracle Enterprise Manager 10g Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    Oracle Management Server is Up.
    Is a patch needed for OMS ?
    Should OMS be version 10.2.0.5.0 ?
    Thanks
    John
    Edited by: user8826739 on Feb 23, 2010 7:17 AM

    10.2.0.5 should be fine ...
    Dave

  • SNMP Trap modules and env

    Hi,
    I would like to know what the equivalent command to enable snmp traps module and env in IOS XR.
    The IOS command is like below :
    snmp-server   enable traps module
    snmp-server enable traps envmon fan shutdown supply temperature status
    i could not find similar command in IOS XR. is it the same with "snmp-server traps system" in IOS XR ?

    Hey,
    You will need to configure "snmp-server traps sensor" to enable the traps under the CISCO-ENTITY-SENSOR-MIB. You can use the following docs to check whether these are supported on your XR platform.
    For ASR9k, (table 3-2 lists the supported Traps on the ASR9k),
    http://www.cisco.com/en/US/docs/routers/asr9000/mib/guide/asr9kmib3.html#wp1602338
    For the GSR XR,
    ftp://ftp.cisco.com/pub/mibs/supportlists/xr12000/xr12000-supportlist.html
    For the CRS-1,
    ftp://ftp.cisco.com/pub/mibs/supportlists/crs1/crs1-supportlist.html
    Thanks and regards,
    Rahul.

  • Creating SNMP Trap Monitors in 2012 R2

    Hello,
    For the past week or so  I have been attempting to create a MP for my company's UPSs to be monitored in SCOM 2012 R2. I have created a custom MP with custom datasources and objects. All seems to go according to the plan until I attempt to create a SNMP
    Trap monitor for those objects. I am able to verify that the device is discovered and is sending the traps successfully with a view. The problem seems to lie within the setup of the monitor. I have followed the steps as much as I can from this page http://technet.microsoft.com/en-us/library/hh563870.aspx
    to create a monitor that will be triggered by an incoming trap saying the UPS is on Battery Power.
    This is the initial or trigger event information received by SCOM:
    <EventData>
    <DataItem type="System.SnmpData" time="2014-07-03T08:48:07.6990732-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790">
    <Source>10.51.85.40</Source>
    <Destination>127.0.0.1</Destination>
    <ErrorCode>1</ErrorCode>
    <Version>1</Version>
    <SnmpVarBinds>
    <SnmpVarBind>
    <OID>.1.3.6.1.2.1.1.3.0</OID>
    <Syntax>67</Syntax>
    <Value VariantType="19">17567220</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
    <Syntax>6</Syntax>
    <Value VariantType="8">.1.3.6.1.4.1.318.0.5</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
    <Syntax>4</Syntax>
    <Value VariantType="8">UPS: On battery power in response to an input power problem.</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
    <Syntax>6</Syntax>
    <Value VariantType="8">.1.3.6.1.4.1.318</Value>
    </SnmpVarBind>
    </SnmpVarBinds>
    </DataItem>
    </EventData>
    This is the event should signal that everything is operating normally once again.
    <EventData>
    <DataItem type="System.SnmpData" time="2014-07-03T08:48:12.9133769-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790"><Source>10.51.85.40</Source>
    <Destination>127.0.0.1</Destination>
    <ErrorCode>1</ErrorCode>
    <Version>1</Version>
    <SnmpVarBinds>
    <SnmpVarBind>
    <OID>.1.3.6.1.2.1.1.3.0</OID>
    <Syntax>67</Syntax>
    <Value VariantType="19">17567730</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
    <Syntax>6</Syntax>
    <Value VariantType="8">.1.3.6.1.4.1.318.0.9</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
    <Syntax>4</Syntax>
    <Value VariantType="8">UPS: No longer on battery power.</Value>
    </SnmpVarBind>
    <SnmpVarBind>
    <OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
    <Syntax>6</Syntax>
    <Value VariantType="8">.1.3.6.1.4.1.318</Value>
    </SnmpVarBind>
    </SnmpVarBinds>
    </DataItem>
    </EventData>
    You may notice that these traps are being sent as SNMP v1. I am unable to change that on the UPS so i have modified the monitors to account for that. Here is the code for the monitor:
    <UnitMonitor ID="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae" Accessibility="Public" Enabled="true" Target="APC.MP.UPS" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="SNL!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
    <Category>Custom</Category>
    <AlertSettings AlertMessage="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae_AlertMessageResourceID">
    <AlertOnState>Warning</AlertOnState>
    <AutoResolve>true</AutoResolve>
    <AlertPriority>Normal</AlertPriority>
    <AlertSeverity>Error</AlertSeverity>
    </AlertSettings>
    <OperationalStates>
    <OperationalState ID="UIGeneratedOpStateId2750c1ab2cd14b4a8a8e9f4633eba0b0" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
    <OperationalState ID="UIGeneratedOpStateId5753748399984d08953c1a46895df99c" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
    </OperationalStates>
    <Configuration>
    <FirstIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
    <FirstVersion>1</FirstVersion>
    <FirstOIDProps>
    <OIDProp>.1.3.6.1.4.1.318</OIDProp>
    </FirstOIDProps>
    <FirstExpression>
    <SimpleExpression>
    <ValueExpression>
    <XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
    </ValueExpression>
    <Operator>Equal</Operator>
    <ValueExpression>
    <Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
    </ValueExpression>
    </SimpleExpression>
    </FirstExpression>
    <SecondIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
    <SecondVersion>1</SecondVersion>
    <SecondOIDProps>
    <OIDProp>.1.3.6.1.4.1.318</OIDProp>
    </SecondOIDProps>
    <SecondExpression>
    <SimpleExpression>
    <ValueExpression>
    <XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
    </ValueExpression>
    <Operator>Equal</Operator>
    <ValueExpression>
    <Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
    </ValueExpression>
    </SimpleExpression>
    </SecondExpression>
    </Configuration>
    </UnitMonitor>
    I tried the following things while attempting to troubleshoot this issue:
    Leaving  First
    SnmpTrapProvider and Second
    SnmpTrapProvider blank while creating the monitor.
    Adding "" and also '' around the value as it is a string and perhaps that was the cause.
    Changing the First and Second SNMPTrapProvider to .1.3.6.1.6.3.1.1.4.1.0 since that is the specific OID I am looking for the value of.
    Reading every page of the internet and bashing my head on the keyboard.
     I am guessing that the issue will reside in the the monitor creation and definition, but I have not found anything that clearly describes how to fill out the SNMP Trap Monitor wizard given the trap info. Especially since the trap I am receiving does
    not seem to contain the usual OID with a common Int or string value.  Hopefully someone can provide assistance as I am nearing my wits end with this problem.

    Firstly, thank you Michael Skov, knowing that the First and Second SnmpTrapProvider or <FirstOIDProps> in the xml, needed to be blank got me pointed in the right direction. I figured I would come back and share my final working code snippet in case
    others run across a similar issue. 
    <UnitMonitor ID="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d" Accessibility="Public" Enabled="true" Target="Disc!APC.Disc.UPS" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="NetworkManagement!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
    <Category>Custom</Category>
    <AlertSettings AlertMessage="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d_AlertMessageResourceID">
    <AlertOnState>Warning</AlertOnState>
    <AutoResolve>true</AutoResolve>
    <AlertPriority>Normal</AlertPriority>
    <AlertSeverity>Warning</AlertSeverity>
    </AlertSettings>
    <OperationalStates>
    <OperationalState ID="UIGeneratedOpStateId8700c95344254f87a60c92d30d4a3953" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
    <OperationalState ID="UIGeneratedOpStateId7bf68c6cfe3d4faabe83e630781c7327" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
    </OperationalStates>
    <Configuration>
    <FirstIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
    <FirstVersion>1</FirstVersion>
    <FirstOIDProps />
    <FirstExpression>
    <SimpleExpression>
    <ValueExpression>
    <XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
    </ValueExpression>
    <Operator>Equal</Operator>
    <ValueExpression>
    <Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
    </ValueExpression>
    </SimpleExpression>
    </FirstExpression>
    <SecondIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
    <SecondVersion>1</SecondVersion>
    <SecondOIDProps />
    <SecondExpression>
    <SimpleExpression>
    <ValueExpression>
    <XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
    </ValueExpression>
    <Operator>Equal</Operator>
    <ValueExpression>
    <Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
    </ValueExpression>
    </SimpleExpression>
    </SecondExpression>
    </Configuration>
    </UnitMonitor>

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

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

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

  • Monitoring SNMP Traps from Windows Server

    Hello All
    im looking for a way to monitor an application that runs with os windows server 2003 and windows 2008 r2 and send its alarms as a snmp traps with system center operations maanger 2012 R2.
    in the scom 2007 environment i could discover the servers as network device and recive traps and genrate alerts.
    is there a way to edit the existing management pack to enable the windows server discovery as a network device
    and enable traps with a microsoft oid to be resived  ?
    i understand that this is by desigin from
    http://technet.microsoft.com/en-us/library/hh212935.aspx
    or is there another option to create this monitor with scom 2012 R2?
    Thank you

    Hello Yan.
    thank you for the replay i understand that this is by design, 
    what im looking for is a way to edit the management pack that discard those OID
    or even a 3rd part solution to monitor windoes server snmp genrated alerts.
    thank you

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

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

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

  • Prime Infrastructure 2.1 - Fan-Failure SNMP-Trap Issue

    Hello,
    I am facing the following Prime Infrastructure (v2.1) issue:
    - A Fan-Failure SNMP-Trap from a Cisco 3650 switch doesn't appear on Prime, but a Link-Failure from the same switch does.
    - The both events appears on Prime with Syslog.
    - The command "snmp-server enable traps envmon fan shutdown supply temperature status" is set up.
    - The switch is in "Managed" state in PI, I have checked the ACL at the "snmp-server community" command, it is okay.
    - I have set up an SNMP-Trace for the switch on PI, but only "SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex" arrived. Please find the log below.
    07/02/14 12:39:53.211 TRACE [presence-9] [] Adding attributes for object Fan3KStats[151206060_,1012]
    07/02/14 12:39:53.211 TRACE [presence-9] [] Index name : fanIndex
    07/02/14 12:39:53.211 TRACE [presence-9] [] Index Value : 1012
    07/02/14 12:39:53.211 TRACE [presence-9] [] Device MIB table index: .1012
    07/02/14 12:39:53.211 TRACE [presence-9] [] MIB table row index: .1012
    07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanIndex = 1.3.6.1.2.1.47.1.1.1.1.1.1012
    07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanOperStatus = 1.3.6.1.4.1.9.9.13.1.4.1.3.1012
    07/02/14 12:39:53.211 TRACE [presence-9] [] Get fragment
    07/02/14 12:39:53.211 TRACE [presence-9] [] Creating PDU: Get
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1010
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1010
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1011
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1011
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1012
    07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1012
    07/02/14 12:39:53.218 TRACE [presence-9] [] Error Status: 0
    07/02/14 12:39:53.218 TRACE [presence-9] [] Error index:  0
    07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
    07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
    07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
    07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, assembling attributes
    07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyIndex = 1.3.6.1.2.1.47.1.1.1.1.1
    07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyIndex
    07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyOperStatus = 1.3.6.1.4.1.9.9.13.1.5.1.3
    07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyOperStatus
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes invoked
    07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes building OIDs for next PDU
    07/02/14 12:39:53.218 TRACE [presence-9] [] Adding attributes for object PowerSupply3kStats[151206060_,1009]
    - The switch sends the SNMP Trap, based on the followings:
    Jul  7 13:38:30 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:30 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 removed
    Jul  7 13:38:30 UTC: %PLATFORM_THERMAL-1-FRU_FAN_NOT_PRESENT: Switch 1: System fan 1 not present
    Jul  7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:30 UTC: SNMP: V2 Trap, reqid 33202, errstat 0, erridx 0
    sysUpTime.0 = 576753333
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
    ciscoEnvMonFanStatusEntry.3.1010 = 5
    Jul  7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:30 UTC: SNMP: V2 Trap, reqid 33203, errstat 0, erridx 0
    sysUpTime.0 = 576753333
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
    ciscoEnvMonFanStatusEntry.3.1010 = 5
    Jul  7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:30 UTC: SNMP: V2 Trap, reqid 33204, errstat 0, erridx 0
    sysUpTime.0 = 576753333
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
    ciscoEnvMonFanStatusEntry.3.1010 = 5
    Jul  7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:30 UTC: SNMP: V2 Trap, reqid 33205, errstat 0, erridx 0
    sysUpTime.0 = 576753333
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
    ciscoEnvMonFanStatusEntry.3.1010 = 5
    Jul  7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS 
    Jul  7 13:38:45 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:51 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 inserted
    Jul  7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:54 UTC: SNMP: V2 Trap, reqid 33206, errstat 0, erridx 0
    sysUpTime.0 = 576755733
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
    ciscoEnvMonFanStatusEntry.3.1010 = 1
    Jul  7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:54 UTC: SNMP: V2 Trap, reqid 33207, errstat 0, erridx 0
    sysUpTime.0 = 576755733
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
    ciscoEnvMonFanStatusEntry.3.1010 = 1
    Jul  7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:54 UTC: SNMP: V2 Trap, reqid 33208, errstat 0, erridx 0
    sysUpTime.0 = 576755733
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
    ciscoEnvMonFanStatusEntry.3.1010 = 1
    Jul  7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
    Jul  7 13:38:54 UTC: SNMP: V2 Trap, reqid 33209, errstat 0, erridx 0
    sysUpTime.0 = 576755733
    snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
    ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
    ciscoEnvMonFanStatusEntry.3.1010 = 1
    Jul  7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    Jul  7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
    It seems like PI and the switch doesn't understand each other concerning the fan...
    Thanks for any ideas, comments and feedbacks,
    Csaba

    I have the very same problem.
    The switch has a power supply error (one of the two is down). There is the syslog message in PI about it, but no event has created, so nor alarm is there as well.
    When I check the status of the switch in the Device Work Center, and choose the Environment in Device Details I can see that PI has not realized the power supply error.
    However when I click on the Sync for this very device the power supply status is updated, but still no event or alarm.
    This is the case with the FANs as well.

  • I can not make IP SLA to signal SNMP traps upon timeout

    Hello team.
    I want SNMP traps to be sent every time an IP SLA (ICMP) object times out. For that purpose, I carried out the following
    ip sla monitor logging traps
    ip sla monitor 1
    type echo protocol ipIcmpEcho 10.1.1.254
    timeout 1000
    frequency 15
    ip sla monitor schedule 1 life forever start-time now
    snmp-server enable traps rtr
    snmp-server host 10.1.1.10 mycommunity
    But no SNMP trap is sent when the IP SLA object times out. ¿ Am I missing something?
    Any help will be greatly appreciated.
    Rogelio Alvez
    Argentina

    SNMP traps for IP SLAs are handled through the system logging (syslog) process. This means that system logging messages for IP SLAs violations are generated when the specified conditions are met, then sent as SNMP traps using the CISCO-SYSLOG-MIB. The ip sla monitor logging traps command is used to enable the generation of these IP SLAs specific traps. The generation of IP SLAs specific logging messages is dependant on the configuration of the standard set of logging commands (for example, logging on). IP SLAs logging messages are generated at the "informational" system logging severity level.
    The command ip sla monitor logging traps is sometime hidden and may not show with ?, so just copy and paste in global config mode and have logging on and check if any traps are generated.
    -Thanks
    Vinod
    **Encourage Contributors. RATE them**

  • SNMP Traps - Mangled packet issue

    One of our client using EMC SMARTS trap Adapter  to collect SNMP traps from Resource Manager Essentials > Tools > Change Audit > Automated Action. recieves mangled packet every night around midnight from the LMS3.1 server as shown below. I could not find any scheduled process at midnight on the server. Attached is a file capture during that period
    Any idea what is causing this ?
    26-Nov-2010 12:01:29 AM+554ms E. Australia Standard Time] t@2712 SNMP_TrapsHandler [0.0.0.0:162] Processor
    SNM2-E-SNMP_AGENTERRORSTATS-Below message for SNMP agent at
        '10.200.4.57:9033', was suppressed 0 times since The Epoch
    SNMP-EPARSER-Mangled or incorrect packet; parsing aborted and data discarded;
        in file "h:/FOUNDATION-7.2.0.X/137/smarts/snmp/lib/SNMP_Parser.c" at line
        1312
    [26-Nov-2010 12:01:50 AM+272ms E. Australia Standard Time] t@2712 SNMP_TrapsHandler [0.0.0.0:162] Processor
    SNM2-E-SNMP_AGENTERRORSTATS-Below message for SNMP agent at
        '10.200.4.57:9060', was suppressed 0 times since The Epoch
    SNMP-EPARSER-Mangled or incorrect packet; parsing aborted and data discarded;
        in file "h:/FOUNDATION-7.2.0.X/137/smarts/snmp/lib/SNMP_Parser.c" at line

    I looked at the trap PDUs that correspond the timestamps in the log output, and I do not see any problems.  Is there additional debugging you can enable in the Smarts application that will indicate why it thinks these traps are mangled?
    The traps themselves come from RME because it looks like you have enabled Inventory and Config collection failure notification, and RME cannot fetch the config from certain devices.  It appears that perhaps RME is doing periodic config collection or polling around 11:30 pm when these traps start to get generated.

Maybe you are looking for

  • FLASH PLAYER 10.1 does not work on my 32bit browser

    the newest  version  of  FLASH PLAYER 10.1 would  not  work  on  my  32bit  FIREFOX browser.  so  I  installed  flash  player  on  a  32bit  VERSION of  internet  explorer. it worked fine for a few days till ADOBE asked me if i wanted to update  my 

  • Invalid URL The requesed URL "/?qs=20920211...", is invalid

    I received an email from Newegg with the following link; http://click.email.newegg.com/?qs=2092021128449e4cb0bd4d4a59cd9edac0a3605d20252e322f8f64d64f3af97ec5927e200f4e494c The response when I click on the link is that Firefox opens and displays the f

  • Webservices and CFNetwork

    Hi all ! I was wondering if someone has a good example of implementing Webservices with the CFNetwork ? The main idea is to have a rails application on a laptop that could communicate with an iphone/ipod touch for exchanging data. Thanks !

  • Permanently remove package from AUR/yaourt updates

    I've installed grub-git manually from the AUR, because I needed to patch it in order to get the intel graphics working on my MacBook. https://wiki.archlinux.org/index.php/Ma - _on_11.2C3 I usually use yaourt -Syua to keep my system up to date. Now ya

  • Updates/1.4.2 Download

    Hi, On the JRocket front page is a hyperlink to download JRockit 1.4.2. I followed the links and there isn't a download for this. Is this right? Will JRockit support RH 8/9/AES3 in the near future? i.e. in months... TIA, -Allen