SNMP Trap with Solaris 9

Hello,
I am looking for information on SNMP traps that can be generated by the SNMP installed with the OS.
How can I configure them and what is available?
I read the doc Solstice Enterprise Agents 1.0 User Guide but did not find anything to configure SNMP Traps.
Or which MIB should I use to get an event log that will report problem?
Any help would be great!
Thanks

Hi,
Even im facing this issue, for latest solaris 10 patches also.
Thanks,
Srikanth.

Similar Messages

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

Snmp trap on solaris 10

Hi,
how can i make my Solaris 10 generate SNMP trap on specific event?
like high CPU,Load or lack of disk space ?
thanks
Ram

it should be possible to define the "index" in each /etc/hostname. file
I have never done this, but when the system boots it reads the content of these files and passes them to "ifconfig" to configure the NICs
search this page for "index":
http://docs.oracle.com/cd/E19253-01/816-5166/ifconfig-1m/index.html

SNMP traps with WLC 4402

Currently using WLC 4402 with about a dozen WAPs. I would like to start logging some messages to troubleshoot some association issues. The syslog does not seem adequate for this the issues I am having. I noticed the default SNMP traps but is only holds 255 traps. I have tried to setup an SNMP server to get the traps but I get no data, only OID values. I was successful in getting the MIBs for the OIDs but still not all the data that I see on the brief traps screen.

Hi,
I have tried it with solarwinds and works fine for me. Talking about the traps. But they are too many.
The OID is : 1.3.6.1.4.1.14179.1.1.2.4.1.22
snmp info for polling:
MIB Value Type: Raw Value
Format: None
SNMP Get Type: Get Table
Polling Type: node
On WLC go to Managemnet (top TAB)
Right hand select > SNMP > Traps Control.
In this menu select what traps to need to be logged.
These traps will be shows on the oid polled.

Snmp traps with Call Manager 4.13

Anyone being able to get snmp traps from Call Manager 4.13 to work. I can walk the MIB and get snmp cold start traps but no Call Manager specific traps

There is a possibility that the CCM service controls this trap and thus cannot send a trap until it is up. This is an issue seen in many devices not just CCM. CCM supports only certain traps.Refer the following URL for more information
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00803f52e1.html#wp1041935

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

Enterprise Manager Grid Control can send SNMP Traps to third-party?

GC 11.1
It looks like a simple config, but I've got into a confusion about it.
I'm trying to figure out the configuration to send SNMP traps to a third party server.
My scenario is:
Node A (managed, monitored) ---- GC box------ SNMP box (final destination).
My understanding is that the traps (notification methods) configured on GC box are generated by the Agent on Node A, then received by the GC and distributed as e-mails.
What is the config to set the traps from A to reach SNMP box?
There is the help page from the GC page (confused about interpretation):
"Add SNMP Trap pageThe Add SNMP Trap page enables you to provide the name of the host (machine) on which the SNMP Master Agent is running and other details so that SNMP traps can be sent through Notification Rules.
An example is shown below.
Name HP OpenView Console
Description Notification method to send trap to HP openview console
SNMP Trap Host Name litleguy.us.oracle.com
SNMP Host Port 162
SNMP Community public
This SNMP host will receive your SNMP traps.
Note: A Test Trap button exists for you to test your setup."
Any suggestions are highly appreciated.
Thx,

Please reply with the specific questions around this.
11.1
EM can send SNMP traps to specific designated receivers. You create an advanced notification method (of type SNMP Trap) with the appropriate details about the receiver.
(See Setup->Notification Methods)
In the notification rules UI, you specify the alerts you are interested in forwarding and select the SNMP trap advanced notification method you created earlier.
The SNMP receiver should be provided the correct MIB that defines the SNMP trap. There were some bugs with the MIB definition in one of the releases (don't recall which one off hand), so if the traps you are receiving don't match what the receiver expects - please let us know and we can point to the right one.
regards

Can a WLC have multiple SNMP Trap Receivers with the same cummunity string?

My Monitoring team want me to send traps to three different trap collectors with the same SNMP Community string.
I have 2106's, 2504, 4400's, 5500's, 7510 all running either version 6 or 7.
Is this possible on a Wireless controller? If so, how?

Read this from my friends blog ..
http://mrncciew.com/2013/02/14/configuring-snmp-on-wlc/
"Also you can configure SNMP trap receiver where WLC can send its snmp trap messages. Community Name means SNMP trap receiver name & that does not have any significance like snmp community value."
It doesnt appear to have the same significants .. But I havent tested it
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

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

Problem with Generating SNMP traps from Windows Events

Hi Supporter,
I configured some events to be translated to traps using evntwin for Service Control Manager and Local Session Manager events. But I just got traps from Service Control Manager event. There is no Local Session Manager events are generated. I checked
with Event Viewer that events are created. Do you have any idea to fix my problem?
Thank you!
Here is my config file from evntwin:
#pragma add "System" "Microsoft-Windows-TerminalServices-LocalSessionManager" 2952790037 1 0
#pragma add "System" "Microsoft-Windows-TerminalServices-LocalSessionManager" 2952790039 1 0
#pragma add "System" "Microsoft-Windows-TerminalServices-LocalSessionManager" 2952790040 1 0
#pragma add "System" "Microsoft-Windows-TerminalServices-LocalSessionManager" 2952790041 1 0
#pragma add "System" "Service Control Manager" 1073748864 1 0

#pragma ADD<EventLogFile> <EventSource> <EventID> [<Count> [<Period>]]
The parameter EventSource specifies the application that generates the event.
those maybe helpful...
http://www.questiondriven.com/2012/03/08/windows-server-20032008-event-log-snmp-traps/
http://www.networkcircus.com/articles/20050715.html
Best,
Howtodo

Experiences with sending SNMP-Traps to 3rd party (Nagios)

Hello Colleagues,
i'm working on a project where we would like to monitor our databases additionally sending SNMP-Traps to Nagios.
At the moment i'm using net-snmp-utils and snmptt. The snmptt-traphandler is running in daemon-mode and passes incoming SNMP-Traps to Nagtrap.
Now i want to create passive service checks. For example a passive service check for TBS_Usage for database 'exdb' which returns the values from the incoming SNMP-Trap.
Has anyone experiences by implementing the SNMP Notifications (to Nagios)? Is there an easier way to implement this than using snmptt?
Does anyone know, how the MIB (snmptt.conf) must be configured for the passive service check?
I'm looking forward hearing from you soon!
Best regards,
Sönke

Hi Nikhil!
Basically I am trying to set trap forwarding to a
a NNM on the network from sunMC 3.5 Update 1.
I have followed all the directions in sunMC snmp FAQ
and other threads on this forum but I am not able to
set the trap destinations.<snip>
Other thread having same question is
http://forum.sun.com/thread.jspa?threadID=15625&tstart
=0Have you reviewed the options in the other thread? (i.e. Halcyon SNMP integration or HP integration packages). Both are off-the-shelf and if you can understand SunMC SNMP infrastructure you certainly wouldn't have trouble configuring either. If you've looked at both packages, what parts made you decide not to use them? Note: I work for Halcyon.
Building your own custom integration with direct traps may be difficult: the generic snmp faq doens't have all the info you need to do so (i.e. how to get NNM to go backwards to an Agent to request the details of an event like "Warning /op is 95% full" or "Critical: Power Supply 2 is Offline"). I'm not even sure how I'd go about it, and I've been using SunMC for years :)
Regards,
Mike
([email protected])

SNMP Traps

Hi there, I'm trying to configure Oracle SNMP on a Solaris 5.9 box. I've followed the instructions on "Note:94313.1".
The start_peer script started successfully the following daemons:
(1) master_peer
(2) encap_peer
(3) snmpdx
I have also started the dbsnmp daemon manually using 'lsrnctl dbsnmo_start'.
I have snooped the machine on which Oracle is installed on port 162:
#snoop port 162
This snoop reported several traps sent to the SNMP manager (HP Openview). The problem is that HP openview is not displaying these traps, so I used ethereal to sniff packets from the Solaris machine (where there is Oracle) to HP Openview. I found that these packets were traps (Enterprise OID's) but had the following description - "Authentication Failed". Can someone explain me what does this mean??
Also, I have another question related to SNMP, considering I'm no SNMP guru - where is the Oracle MIB file so that I can load it on HP_Openview??

Hi
Thanks for answering my question , when i took the module out physically
it sent the trap/callhome .
how can i get callhome message with port discription insted of %port....when link goes up/down ?
Thanks ,
Ronen

Step by step guide to receiving SNMP traps in OEM:now available

Hi,
If you are interested in receiving SNMP traps (as a way of monitoring SNMP aware products) within OEM, we have published a white paper that walks you through the steps:
http://www.oracle.com/technology/products/oem/extensions/receivelet_plugin_wp.pdf
The white paper also walks you you through the steps involved in developing a plug-in. Happy reading and best of luck with developing new plug-ins.
Thanks
Anirban
Sr. Product Manager

ok here i am again...sorry for bugging u...but im helpless...please help me!
I've been getting the following message from the time I installed Solaris 10
"Last Shut Down is later than time ....... time of date chip
Next after the login appears...lthis is wat I see on the screen
" Mar 2007/03/07 blah....... My unqualified host name"
"sleeping for retry"
"Waiting for desktop Logic screen before Loggin in.."
I thought DEP might be interfering in this so I disabled DEP in wondows also :O
Should i format Solaris partition and re-install it again??

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

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>

SNMP Trap with Solaris 9

Similar Messages

Maybe you are looking for