ISR 3945 - SNMP trap set up to recieve option pings from ASR1006

I am working on a set up : ISR 3945 - Receiving option pings from another device (ASR) and sending a snmp trap (say ex: if a link down on a dial-peer ) to snmp server if those option ping fails.
- Need inputs on SNMP config
Thanks in advance.

Hi.
the easiest way is to get the snmp-server trap source command to work.
when you say it's not working, do you mean the branches still use the external interface as the source? or that it's sourced properly from vlan1 but somehow doesn't get encrypted?
what ios version are you running on the branches? maybe this is a bug and newer versions get it to work?
if you want to through another way than snmp-server trap source, then an ipsec redesign might be needed. As you noticed dmvpn would be the easiest. another solution would be dynamic lan-to-lan from branch to headend with gre tunnels (similar to dmvpn), and then force the route to the management network via GRE, this way the snmp trap source would default to use the tunnel ip address.
Regards,
Fadi.

Similar Messages

NX-OS snmp-trap strdata does not return string sent from device to object server

NX-OS snmp-trap strdata does not return string sent from device to object server
Applet was created:
   event manage applet TEST_VPC
   description "%ETHPORT-5-IF_DOWN_ADMIN_DOWN"
   event syslog occurs 1 priority 4 pattern "%ETHPORT-5-IF_DOWN_ADMIN_DOWN"
   action 1.0 snmp-trap strdata "Loopback0 is admin down"
after event is generated (link admin down), trap is sent to snmp server, but string does not appear in received messages:
2014-03-17T04:29:26: Debug: D-P_M-105-000: 1 trap in queue
2014-03-17T04:29:26: Debug: D-P_M-105-000: V2/V3 trap/inform received
2014-03-17T04:29:26: Information: I-P_M-104-000: Number of items in the trap queue is 0
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReqId: 1427018637
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] community: xxxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] IPaddress: x.x.x.x
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] PeerIPaddress: x.x.x.x
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReceivedPort: 162
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] ReceivedTime: 1395044966
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Protocol: UDP
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] SNMP_Version: 2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] UpTime: 1166940388
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Uptime: 1:30:03.88
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.2.1.1.3.0: (1166940388) 135 days, 1:30:03.88
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] notify: .1.3.6.1.4.1.9.9.43.2.0.2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.6.3.1.1.4.1.0: .1.3.6.1.4.1.9.9.43.2.0.2
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] OID1: .1.3.6.1.4.1.9.9.43.1.1.1.0
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_raw: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_text: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 1_hex: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.4.1.9.9.43.1.1.1.0: (1166939868) 135 days, 1:29:58.68
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] OID2: .1.3.6.1.4.1.9.9.43.1.1.6.1.6.36
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_raw: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_text: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] 2_hex: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] .1.3.6.1.4.1.9.9.43.1.1.6.1.6.36: 4
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Node: xxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] PeerAddress: xxxx
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] EventCount: 360
2014-03-17T04:29:26: Debug: D-UNK-000-000: [Event Processor] Processing alert {0 remaining}
please help figure this out

This is a CISCO-CONFIG-MAN-MIB trap, not an EEM trap. I don't think your EEM applet is being triggered since you have that priority argument in there. Try removing that and leave the syslog pattern alone. You will see the string as a varbind in the trap.

"Set up Family Sharing option" missing from iCloud settings

I'm trying to set up a child (under 13) via. my Apple ID/iPod touch.
There is no "Set up Family Sharing" option when we go to Settings > iCloud.
What do I do?

Hi Elliot,
Happy Holidays! To set up Family Sharing, you need to have iOS 8 on your iPod touch. Check to see if you have updated to the latest version, which is 8.1.2 on your device.
Update the iOS software on your iPhone, iPad, and iPod touch - Apple Support
http://support.apple.com/en-is/ht4623
iOS software updates introduce new features that let you do even more with your iPhone, iPad, or iPod touch. Be sure to keep your devices up to date so that you don't miss out on the latest features.
Before you update
Back up your device to iCloud or iTunes.
If you use your device's Personal Hotspot for your computer's Internet connection, update your device wirelessly or connect your computer to another network.
Update your device wirelessly
The easiest way to update your device is wirelessly, also called “over the air.” Here’s how:
Plug in your device to a power source.
Tap Settings > General > Software Update.
Tap Download and Install. Updates might download automatically while your device is connected to Wi-Fi and a power source.
Tap Install, or tap Later to install the update later. If you use a passcode, you'll need to enter it before installing the update.
If you have some free space, but not enough to update over the air, you can either update using iTunes or delete content manually from your device. Whether you use iTunes or update over the air, you'll have the same amount of free space on your device after you update.
The resource below explains how to set up Family Sharing and how to create an Apple ID for your child.
Start or join a family group using Family Sharing - Apple Support
http://support.apple.com/en-is/HT201088
Start or join a family group using Family Sharing
Family Sharing makes it easy for up to six people in your family to share each other’s iTunes, iBooks, and App Store purchases without sharing accounts. Pay for family purchases with the same credit card and approve kids’ spending right from a parent’s device. And share photos, a family calendar, and more to help keep everyone connected.
Use the steps below to start a new family group or join an existing family group. You can be a part of only one family at a time.Get started
Here's what you'll need to use Family Sharing:
An Apple ID signed in to iCloud and iTunes
iOS 8 on your iPhone, iPad, or iPod touch or OS X Yosemite on your Mac
Start a family group
One adult in the family—the family organizer—can set up Family Sharing for the group. When you set up Family Sharing, you'll be asked to confirm that you agree to pay for purchases initiated by the family members you invite and that you have a valid payment method on file. Valid payment methods for setting up Family Sharing include credit cards and debit cards.
Set up Family Sharing
Use these steps in iOS 8:
Go to Settings > iCloud.
Tap Set Up Family Sharing, then tap Get Started.
Confirm that you want to be the family organizer and that you're signed in with your personal Apple ID.
Follow the onscreen instructions.
Use these steps in OS X Yosemite:
Choose Apple menu > System Preferences, then click iCloud.
Click Set Up Family.
Follow the onscreen instructions.
After you set up Family Sharing, you can invite your family members to join.Invite people to join your family
Use these steps in iOS 8:
Go to Settings > iCloud > Family > Add Family Member.
Enter your family member's name or email address.
Follow the onscreen instructions. After you send the invitation, you can check its status under the person's name in Settings > iCloud > Family.
Use these steps in OS X Yosemite:
Choose Apple menu > System Preferences, then click iCloud.
Click Manage Family.
Click +, then follow the onscreen instructions.
You can also use these steps to create an Apple ID for a child and add them to your family group. When you create an account for a child, you must use a credit card as the payment method as part of providing your parental consent. After you create the child's Apple ID, you can change your payment method back to a debit card if you choose.Join a family group
You can accept or decline an invitation to join a family from you iPhone, iPad, iPod touch, or Mac. If the invitation is sent to your email address, you can also respond right from your email. To accept an invitation in iOS 8, go to Settings > iCloud > Invitations. In OS X Yosemite, choose Apple menu > System Preferences > iCloud > Manage Family. Then follow the onscreen instructions.
Here's what you'll be asked to do when you join:
Confirm your Apple ID and password.
Choose if you want to share your content and which iTunes Store account you want to share from.
Choose if you want to share your location. If you agree, your location can be displayed on family members’ devices in Find My Friends and Messages, and the location of your shared devices will also appear on family members’ devices in Find My iPhone.
What's next
You can share eligible iTunes Store, iBooks Store, and App Store content, family photos, a family calendar, your location, and more.
Get help using Family Sharing.
See what you can share and how to download content from your family members. You need to use the iTunes Store in the same country as your family members to use Family Sharing.
Choose when to share your location with your family members.
Learn about family purchases and payments.
Manage your child's account and use Ask to Buy.
Learn more
Family Sharing requires a personal Apple ID signed in to iCloud and iTunes. Music, movies, TV shows, and books can be downloaded on up to 10 devices per account, five of which can be computers. iOS 8 and OS X Yosemite are required to set up or join a Family Sharing group and are recommended for full functionality. Not all content is eligible for Family Sharing. Content can be hidden by family members; hidden content is not available for download. Content downloaded from family members or acquired via redemption codes is not subject to Ask to Buy.
Last Modified: Oct 16, 2014
Cheers!
- Judy

WLC 5508 - Set SNMP traps differently per AP

Hey All,
We have a controller with multiple remote AP's connected to it. A couple of the AP's are at branch offices connected to very low quality DSL connections (which is all that is available) and because of this those AP's cut SNMP traps constantly. For example last month one AP cut about 50 traps because the DSL connection kept cutting out...usually for only a few seconds/minutes.
I looked though and couldnt find a way to set the traps per AP...only globally. Is there a way to change the threshold per AP so for example it will only cut a trap if the AP is seen down for a 24 hour period as opposed to everytime it only goes down for a few minutes?
Thanks!

Hey All,
We have a controller with multiple remote AP's connected to it. A couple of the AP's are at branch offices connected to very low quality DSL connections (which is all that is available) and because of this those AP's cut SNMP traps constantly. For example last month one AP cut about 50 traps because the DSL connection kept cutting out...usually for only a few seconds/minutes.
I looked though and couldnt find a way to set the traps per AP...only globally. Is there a way to change the threshold per AP so for example it will only cut a trap if the AP is seen down for a 24 hour period as opposed to everytime it only goes down for a few minutes?
Thanks!

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

Questions on Receiving SNMP Traps

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

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

SNMP traps from Solaris 10

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

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

SCOM 2012 SNMP Trap - Does anyone have it working?

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

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

SNMP Trap Translation Wrong For Hebrew Language

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

Closing as issue found at HP openview parameter settings

Sending alerts as SNMP-Traps from Solman to Nagios

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

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

No SNMP traps from sun x4150 ILOM server

Hi all,
I have set up the ILOM alerts with SNMP traps (v2c,public) according to the ILOM user guide and pressed the "send test alerts". Nothing shows up in the SNMP trap monitor (using MG-SOFT software). When I add another alert of IPMI pet type (same destination ip as of SNMP trap alert) I see events in the trap monitor. It looks like the ILOM does not generate SNMP traps but only IPMI traps.
In the ILOM user guide there is an explicit example of traps sent from the ILOM (in addition to the fact that the ILOM features include SNMP traps AS WELL as IPMI) so it seems this is possible...
my ILOM version is
SP Firmware Version 2.0.2.6
Does anyone have any idea of any step I have missed ?
Thanks in advance.
Lior

Once the Network Device (Linux server in this case) is discovered you will still need a rule that targets that class and accepts incoming SNMP Traps for that OID, or All OIDs if you prefer. I found 2 links that may be of help, the first is just a basic
overview of the SNMP listener in SCOM 2012 as it has changed from the OS Listener in 2007 to a dedicated one.
http://systemcentertech.com/2012/05/17/scom-2012-built-in-snmp-trap-listener/
The second link covers SNMP setup, but starting at Step 7 there is a great how-to on creating your own SNMP rule which will be needed to collect your traps.
http://scom-2012.blogspot.com/2012/07/setting-up-snmp-monitoring-in-scom-2012.html
www.Practice2Perfect.com

SNMP traps from Cisco 4404

I have a Cisco 4404 WLC that sends its system logs to a syslog server (kiwicat), but I'm interested in getting the snmp traps sent over there as well. I've configured the syslog server to accept the snmp on the right ports and I've confirmed that the syslog server can receive then by sending traps manually from other devices.
I cannot seem to actually get the WLC to send the traps to the server. the syslog stuff gets through ok, but not the snmp. I've added the syslog server as an SNMP trap reciever and configured it as much as it needs to be and the only difference it seems to have made is to add more things to the main trap log on the 'monitor' tab on the WLC. Am i missing something really basic?
p.s. the WLC and the syslog server are separated by a firewall, but the syslog rules have been altered to also allow the snmp, should it attempt to go through.
Any help would be gratefully received.

Yes, I think the Network Devices need to be discovered first in order to receive traps and generate alerts.
Juke Chou
TechNet Community Support

SNMP traps from EMC SRM to SCOM 2012 R2

Hi,
I'm trying to configure SCOM 2012 R2 as an SNMP trap listner. I've seen many articles on setting this up but all are based around SNMP traps from network devices which must first be discovered and identified in the network device list.
However in my scenario I am trying to monitor/listen for traps send by a Linux box hosting EMC SRM - this management software can be configured to send SNMP traps out so it is these that I need to try and listen for/capture.
So can anyone explain how I can configure SCOM 2012 R2 to do this. I have tried to just used the IP of the Linux box and discover it as a network device but it fails - in Network Devices Pending Mgmt it says No response Ping, even though I can
ping the box from the Server OK - so I am guessing you cant cheat scom in discovering the Linux box as a network device in ths way?
Can anyone offer any advice for setting this up. Just to add I've ensured the RunAs Community String (public) and SNMP version is correct on both side...
Cheers...

Once the Network Device (Linux server in this case) is discovered you will still need a rule that targets that class and accepts incoming SNMP Traps for that OID, or All OIDs if you prefer. I found 2 links that may be of help, the first is just a basic
overview of the SNMP listener in SCOM 2012 as it has changed from the OS Listener in 2007 to a dedicated one.
http://systemcentertech.com/2012/05/17/scom-2012-built-in-snmp-trap-listener/
The second link covers SNMP setup, but starting at Step 7 there is a great how-to on creating your own SNMP rule which will be needed to collect your traps.
http://scom-2012.blogspot.com/2012/07/setting-up-snmp-monitoring-in-scom-2012.html
www.Practice2Perfect.com

SNMP traps from HP NNMi - SCOM

Hi,
We wan't to forward snmp traps from hp nnmi to scom.
I have found a description of a solution for this here: http://social.technet.microsoft.com/Forums/systemcenter/en-US/19c29988-dfe8-4918-b0d5-f3124bcfea95/operations-manager-and-hewlett-packard-nnmi?forum=operationsmanagergeneral
I have added a server as snmp device. By using snmptrapgen I have also confirmed that the traps are received from scom.
In NNM I have specified that all traps are to be forwarded to the server which is discovered as a network device. I have also activated the snmp services and set the correct settings. These traps have not been received in scom.
Have I understood this correctly? If NNMi just forwards the traps, will not the traps have source IPs which is not registered as network devices in SCOM, and therefor be discarded?
I would very much like to hear from people how have done a simular type of integration :)
Thanks in advance, Best Regards

Yes, I think the Network Devices need to be discovered first in order to receive traps and generate alerts.
Juke Chou
TechNet Community Support

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.

ISR 3945 - SNMP trap set up to recieve option pings from ASR1006

Similar Messages

Maybe you are looking for