BGP Peer down monitoring through SNMP Traps

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

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

Similar Messages

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

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

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

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

SNMP trapping PRI channels up/down

Hi guys.
I am re-configuring some routers to generate traps for our new monitoring tool.
I have noticed that after I applied the snmp trap configs that we are getting traps for PRI channels (30 voice channels), which I wouldn´t like to. This happens when users are using the voice channels on demand. When they hang up, the used channel goes down and I get a trap.
Basically, regargint the controller, the only interface that I must monitor is the signaling one (my case is the channel 0/3/0:15) or if the entire controller goes down.
Below, the snmp trap config:
snmp-server ifindex persist
snmp-server trap-source Loopback0
snmp-server enable traps snmp linkdown linkup coldstart warmstart
snmp-server enable traps envmon
snmp-server enable traps isdn layer2
snmp-server enable traps isdn chan-not-avail
snmp-server enable traps isdn ietf
snmp-server enable traps bgp
snmp-server enable traps hsrp
snmp-server enable traps ipsla
snmp-server enable traps voice poor-qov
Could you please help me to figure out how I can solve this?
Also, if you guys have any other advises and more ways to monitor the voice environment.
Thanks in advance

Duplicate post.
Go HERE.

Monitoring PRi's with snmp traps

I am looking to monitor when my pri's go down and generate a trap.
Is this the best way:
snmp-server enable traps isdn layer2
or are there some other traps that I can enable?
Thanks,

Once I got my SNMP host to accept the correct attribute and configure the event trap all I had to do was add the trap command to the router. I then bounced one of my low usage PRI's (which had 0 calls on it ) and got the following event traps on the SNMP host:
Minor
May 19, 2010 2:21:00 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has layer 1 active but layer 2 not established. Interface Index = 83 Link Status = ISDNLinkInTransition
System
May 19, 2010 2:21:01 PM EDT
System
Major
May 19, 2010 2:20:59 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has both layers 1 and 2 inactive. Interface Index = 83 Link Status = ISDNLinkDown
System
May 19, 2010 2:21:00 PM EDT
System
It doesn't tell you specifically which interface is down but at least it narrows it down to the gateway/router. Most of our gateways have only one PRI anyway.
We use Spectrum One Click for network monitoring.
Here is L2 back on line:
May 19, 2010 2:21:01 PM EDT
A demandNbrLayer2Change notification has been received indicating that a D-channel on Rtr_Cisco device, named has layer 1 active and layer 2 established. Interface Index = 83 Link Status = ISDNLinkUp
System

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

Can custom standard MBean's properties be monitored to generate SNMP traps

I am trying to setup a trap monitor (Counter) to detect the
change in a property of my custom MBean, which gathers
runtime statistics for our application.
Here is the MBean interface:
public interface BOStatusSummaryRuntimeMBean {
public int getTotalClientRequestsCount();
I've registered the implementation MBean, through the startup class, with the
following code:
MBeanHome wlmbsh = (MBeanHome) ctx.lookup("weblogic.management.adminhome");
MBeanServer mbs = wlmbsh.getMBeanServer();
ObjectName myName = new ObjectName("businessobjects:Location=bo_server,Name=BOStatusSummary,
Type=BOStatusSummaryRuntime");
BOStatusSummaryRuntime mbean = new BOStatusSummaryRuntime();
mbs.registerMBean(mbean, myName);
This is the setup for the Counter trap:
MBean Type: BOStatusSummaryRuntime
MBean Name: BOStatusSummary
Attribute Name: TotalClientRequestsCount
PollingInterval: 1
Treshold: 1
Offset: 1
Modulus: 0
The MBean is available and I can see the property changing, as I execute client
applications, but SNMP traps are not generated.
Applying the same monitor on a Weblogic's MBean (Type=EJBComponent, Attribute=DeploymentOrder)
for one of the deployed EJBs, works fine and traps get generated.
I would appreciate if someone can point me in the right direction ...
Regards,
Darko Bohinc
Consultant

I was hoping Adobe had something that could be used, or am I stuck using php or Javascript and just doing this with custom scripting?
I think you will have to do the latter. While you are thinking about writing the PDF file, don't overlook fpdf (google it)....

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>

Monitoring servlets through SNMP Servlet Runtime Table

Is it possible to check or monitor a servlet/jsp using SNMP traps (counter, attribute change, etc). If so can you provide a sample set up for values such as the MBean Name, MBean Type, MBean Attribute.
Thanks,
Juan

Yes there is, monitor the gateway, not the CCM:
http://cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801abe59.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

CCMS agents, alert monitoring, SNMP traps

Hi Guys,
I have a question. There is a requirement about monitoring. Any documenation or links will be really appreciated.
My client needs me to use CCMS agents, alert monitoring for both ABAP and JAVA stacks, SNMP traps, sending SNMP traps, interface CCMS with third party monitoring tools. Mostly, the ,monitoring is done thru RZ20.
Anybody can point me in right direction or material.
Thanks
Venky

Hi,
Check these CCMS Weblogs. Really good ones...
/people/federico.babelis2/blog/2006/04/26/ccms-rule-based-monitors-configuration-guide-for-dummies
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
Feel free to revert back.
--Ragu

Link down and Link Up Snmp trap C#

Hi i've configure my cisco router to receive the SNMP traps if the link goes up or down. However i found out that when i plugged out the cable i'm not receiving any link down on the network management system. Until i plugged in again the link will then show up or down state. May i know whats the reason why i can't receive the link down when i plugged out my cable?

If your router has only fa0/0 as active interface, then this would be the interface that the router would use to communicate with the network management system. However when you unplug that interface now the router has no interface that it can use to send the link down trap to the network management system.
HTH
Rick

SNMP Traps Monitoring problem.

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

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

SNMP traps to monitor the signal strength on wireless AP

What snmp notification type should I enable on wireless AP to monitor the signal strength of the connected devices to the AP. What is the associated MIB for this SNMP trap.

Hi karthikeya,
Here is the link which gives us the info regarding the available MIB for the respective Model..
http://tools.cisco.com/ITDIT/MIBS/MainServlet?ReleaseSel=3469&PlatformSel=9&fsSel=1292
Please select the Device part number and then chose the MIB that you require.
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

ASA /Router -SNMP Trap when IP SLA monitored (ICMP timeout)

Hi,
I am looking for some solution for my below requirment
Requirment is :
How do I configure ASA or Router to send SNMP Trap when IP SLA monitored features enabled (ICMP request or 900 millisecond delay from destination IP)
Thanks in advance..

Hi,
Maybe this thread might help you?
https://supportforums.cisco.com/thread/2039293
I have not personally configured these type of SLA configurations on an ASA other than for testing purposes. We handle Dual ISP setups outside the ASA firewalls.
- Jouni

BGP Peer down monitoring through SNMP Traps

Similar Messages

Maybe you are looking for