Forwarding of traps

The SMC FAQ for SNMP lists steps to take to forward traps to a 3rd party management application. The steps listed here: http://wwws.sun.com/software/solaris/sunmanagementcenter/faq/snmp.html#0q10 do not seem to be valid. Has anyone gotten this to work? After reading the Appendix of the DE manual it says that you need to set OID .1.3.6.1.4.1.42.2.12.2.1.4.1.0 with the forwarding information. When I attempt this I'm told that there is no such variable in this MIB. Was this functionality removed from 3.5? Is the manual wrong? Any help would be appreciated.
Thanks,
Brian T. O'Neill

I just tested it on my 3.5 server without problems, but I did it a little differently:
- I created the topology object on port 162 as described
- used the attribute editor on the topology object to set the administrator community string to public
Then I ran the SNMP command (using the SunMC SNMP utilities):
bash-2.05$ /opt/SUNWsymon/util/bin/snmpset -h localhost -p 162 -c public 1.3.6.1.4.1.42.2.12.2.1.4.1.0 "OctetString" "10.0.0.201"
Request Id: 0
Error: noError
Index: 0
Count: 1
Name: 1.3.6.1.4.1.42.2.12.2.1.4.1.0
Kind: OctetString
Value: "10.0.0.201"
One thing that comes occassionally with SNMP utilities/libraries is the use or lack or a starting "." on the OID. In this case, using .1.3.6.1.4... did not work for me.
Hope this helps,
Jeff Grabell
http://www.cirba.com

Similar Messages

LMS 3.2 not forwarding SNMP Traps

I am using LMS 3.2 and under DFM... Notification Services... SNMP Trap Notification, I have a Subscription set up to forward Traps to Unicenter 11.1. I have tried a combination of sending Alerts and Events, Critical and Informational, Active and Cleared messages.
At this time I have it set to send:
Alerts Informational and Cleared
Events Critical and Informational, Active and Cleared.
Every Trap that is forwarded from LMS I get in the Unicenter console Twice. Also, I occasionally get a clear in Unicenter, but normally clears are not being forwaded.
Any ideas on this issue?
Thanks
-Scott

You should first install the consolidated DFM 3.2 patch from http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=3.2.0&mdfid=282640771&sftType=CiscoWorks+Device+Fault+Manager+Patches&optPlat=Windows&nodecount=2&edesignator=null&modelName=CiscoWorks+Device+Fault+Manager+3.2&treeMdfId=268439477&treeName=Network+Management&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y (patch for CSCta56151). If the problem persists after that, post the NMSROOT/log/dfmLogs/NOS/nos.log after reproducing the problem with a new event/alert.

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

Forwarding traps to another port

The Master Agent listens to Port 162 for SNMP traps. Is there a way to forward raw Enterprise traps from the Master Agent to another port on the local host? I have a trap listener application on Port 8162 and need traps forwarded to it.
I was able to use Domain Manager's /etc/opt/SUNWconn/snm.conf file, setting the na.snmp-trap.forward.snmp-traps variable to localhost,8162 but the Domain Manager package will not be installed anymore on my systems.
Thanks,
Warren Lim
[email protected]

The iPhone does not support MMS which is a software issue.
Apple could provide MMS if they wanted to via a software update.

LMS 4.2 forward traps to Netcool

We want to forward LMS 4.2 traps to a remote NMS (Netcool).
In order to translate the traps into an event, we need the MIB's which LMS 4.2.3 is using.
Does anyone know the location of the directory on the LMS server of these MIB's?

Hi,
you can forward the traps directly from here : Monitor > Fault Settings > SNMP Traps > Notification
check this location on the server:
NMSROOT\CSCOpx\hum\mibmanager\mibcompiler\mibs
If you want to add a new MIB to LMS , you can LOAD the MIB to the server from here :
Admin > Network > Monitor / Troubleshoot > Load MIB
Thanks-
Afroz
[Do rate the useful post]

LMS 4.0 SNMP Traps Forwarding

Hello,
I have installed a new version of CiscoWorks LMS 4.0.
I would like to forward certain SNMP traps to another server. Not all traps but only the traps of devices which are down.
Is it possible to filter the traps and then forward the traps who match the filter to a server?
Thanks,
Best Regards,
Joris

If you enable trap forwarding in LMS, all traps received by LMS will be forwarded to the external NMS.
You can, however, look at NMSROOT/objects/smarts/conf/trapd/trapd.conf. You can modify this file to specify exactly what traps to forward. The comments in the file should help you figure out the syntax. However, direct modification of this file is not supported by TAC, so be sure to save a backup just in case.

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

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

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

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

Added a Northbound SNMP Trap Receiver in Cisco PI 1.3, but not getting traps

Hi;
I tried going into the Administration, System Settings, Notification Receivers menu and adding a receiver. The receiver was our Zenoss 4.2.3 Resource Manager system. Zenoss has no problems receiving traps from IOS devices such as switches; that is routine for us. For example, we see snmpTrap_Linkdown events from 2960s,etc.
However, even with all the possible events and severities checked in the PI GUI for the receiver, we did not get anything.
As a quick test I added my desktop computer as a receiver and ran Wireshark. Nothing comes through from Cisco PI.
This is supposed to be UDP 162 stuff, so there ought not be a need for a handshake or need to permit anything on the receiver side. I would expect to see a total fire-hose of traps after the receiver is added. But that reasoning conflicts with the need to set the SNMP Community string for the Notification Receiver...
I downloaded the logs from Cisco PI and grepped through all of them for the IPs & names of the test receivers, but found no messages.
Any idea what might be wrong? Do I need to restart something after adding the receiver?
I did notice that even if I supply a ficticious IP and name for the receiver, after it is added the "Operational Status" still says "Up" ...
I sure wish NCS came with a better help system - I can't find anything in the Cisco config guides that explains what a "Northbound" receiver is.
So confused,
Steve

Hi Matt, thanks for taking the time to reply.
>> Not sure why you are trying to do this with PI, this is really more of an ISE function
We don't have ISE and won't be getting it ... still trying to afford the > $100K for PI licenses. Our Content Filter vendor suggested using PI.
>>Is PI set to forward traps for client authentication?
I have all traps and severities checked. Not sure last week nothing showed up in Wireshark. Today I am seeing some UDP info from PI hitting my test workstation. However, when I associate and dissassociate my laptop, nothing comes through. Most of what I see are rogue notifications.
>> Are the controllers that PI is managing also set to forward the same traps?
In Configure,Controllers, , Management, TrapControl, all possible boxes are checked.
>> Is PI configured correctly to forward the traps you want?
Please see answer above.
>> Does your content filter have the right MIBs to decipher the traps correctly?
The content filter vendor says they will customize their software as needed, but the first step is to see traps getting forwarded, and right now, it appeards that PI is not forwarding what I would expect from the GUI settings. Let's worry about MIB stuff after we are getting the raw trap data.
Thanks,
Steve
Message was edited by: Stephen Crye, elaborated & provided latest info.

Ciscoworks LMS 4.0 DFM Custom Traps

Hello,
We want to use Ciscoworks LMS 4.0 for Access Control List Monitoring. i.e. if we end the ACLs with "log" entry, we may send the ACL deny logs to the Ciscoworks as Syslog or Snmp Trap format.
With "debug snmp packets" command we may observe the packets are sent to the LMS, but the traps don't show up as alarms. Is it possible to observe any trap entry with LMS DFM Fault Manager by customizing the module, because we think the engine of the DFM analyzes the traps and shows some of the traps, not all of the traps are observable.
The command output is as below:
Thanks in Advance,
Best Regards,
Mar 2 10:28:30.028: SNMP: Queuing packet to 10.10.10.1
.Mar 2 10:28:30.028: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.20.1, gen trap 6, spectrap 1
clogHistoryEntry.2.742 = SEC
clogHistoryEntry.3.742 = 7
clogHistoryEntry.4.742 = IPACCESSLOGDP
clogHistoryEntry.5.742 = list 191 denied icmp 10.10.10.1 -> 10.10.20.1 (0/0), 10 packets
clogHistoryEntry.6.742 = 69082382

DFM consumes the traps and decides based on its built-in code-book what to do - rise one of the predefined Events or just silently ignore it. The best DFM can do is forward the trap as-is to another trap receiver.
Perhaps the LMS Syslog-Server can do what you want and lauch automated actions (like scripts or e-mail) based on certain criteria.
But you should take care of the underlying syslog file and keep its size under control with logrot.pl utility.
The online help of LMS should give you more details on the syslog capabilities or this link to the LMS 4.0 Administration Guide:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/admin/useNotif.html#wp1075603

LMS 3.2 snmp trap forwardig to HP-open view

Hi,
I want to forward snmp traps from cisco LMS to HP-open view. Both applications are installed on different servers.
From previous post in this forum, I found a similar post that recommand using snmp forwording in DFM.
What I want to know is do I need any integration or packages to install on both platforms to do this? Also, will DFM forward all traps that it receives from installed devices or it will forward some of them.
Thank you
BR,
ZS

Chris;
current version of Java is 1.6.0 Update 20
Additional information to the issue: a WS-C3750 has been discovered (connected to another 6509 that is running hybrid) and added to the topology map as it one would expect.
craig

Phantom SNMP Traps

Hi,
I've got most of my devices spouting SNMP traps for various different things, and Ciscoworks forwards these traps on via email, as you do.
For most things it works great, however since we've created a script to pull on the configs off the devices (Simply don't trust Ciscoworks), we're always spammed with SNMP traps like the one below:
ALERT ID                = 000071P
TIME                    = Mon 10-Jan-2011 16:19:07 GMT
STATUS                  = Active
SEVERITY                = Critical
MANAGED OBJECT          = lrouter-loo-0.mwam.local
MANAGED OBJECT TYPE     = Switches and Hubs
EVENT DESCRIPTION       = router1-loo-0.mwam.local: Cisco Configuration Management Trap:InformAlarm; PORT-lon-cr1-loo-0.mwam.local/10113 [Gi1/0/13] [Trunk to router2-gig-1-0-24]:OperationallyDown;
CUSTOMER IDENTIFICATION = networks-info
I know one port is down, and that's expected, I just haven't cleared the alert and turned off the monitoring in DFM.
We're using:
snmp-server enable traps config-copy
snmp-server enable traps config
on all of our devices, but only 4 out of 80+ devices throw this trap out when their config is copied by the script.
I've googled extensively, but I haven't come across any real help.
Has anyone got any idea what the situation is with this? I'm getting bored of deleting a bunch of emails every time our script runs, and I don't want to create a rule for fear of filtering real alerts.
Any ideas would be appreciated
Cheers

This isn't a trap. This is a DFM alert, which consists of multiple atomic events. In this case, it looks like the alert consists of two events. The first is a CISCO-CONFIG-MAN-MIB trap (i.e. ciscoConfigManEvent). If you look at the associated event in the DFM Alerts and Acitivities Display, I'll bet it will indicate the configuration was copied (per your script). The other event indicates that port Gi1/0/13 is operationally down on this switch. The two events are unrelated, but apply to the same device.

Configuring SNMP Trap receiver on AIP-SSM sensor

I receive the following error message from my ASA5520 firewall when attempting to forward SNMP traps from my AIP-SSM20 sensor to a server on my Inside interface that is configured to receive SNMP traps:
ASA-4-418001: Through-the-device packet to/from management-only network is denied: udp src management: 10.3.21.2/32768 dst Inside: PPC0ES/162
Can I reconfigure the management IP address of the AIP-SSM sensor to connect to the Inside interface instead of the management vlan or does my SNMP server have to reside on the management vlan with the sensor?

Hi Subodh,
Yes, the AIP-SSM can operate in either inline (IPS) or promiscuous (IDS) mode. I would recommend you start by reviewing the following config guide, which shows you how to configure the ASA to pass traffic to the SSM for inspection:
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807335ca.shtml
If you have any other specific questions, feel free to post back.
Hope that helps.
-Mike

SEA 1.0.3 snmpdx - no traps possible???

Hi list,
I'm struggling hard to implement an SNMP subagent using Solaris 8 SPARC and the SEA 1.0.3 SDK. I've applied patch 108869-18 to avoid difficulties.
Querying the mib subtree controlled by my subagent works fine. Unfortunately, I can not make the master agent (snmpdx) to forward the traps generated by my subagent.
The SEA 1.0.3 documentation on SNMP is very terse. It lacks examples, especially how to configure the /etc/snmp/conf files. It has some (buggy) grammar rules but the sample files contain commented out parameters that generate parsing errors when the parameters are actually used, e.g. the parameter trap-recipients in the acl-files. I'd also like to know what the parameters in the trap-block mean, especially trap-num. There's nothing in the docs... :-(
When I run master and subagent with -d 4 I can see that the subagent generate traps and the master agent receives them, but in the master agent I get
---------- cut here ----------
<< received 503 bytes from ichh2s101.faxdev.ic.47432
PACKET:
30 82 01 F3 02 01 00 04 06 70 75 62 6C 69 63 A4
82 01 E4 06 09 2B 06 01 04 01 93 0F 01 02 40 04
C0 A8 15 65 02 01 06 02 01 05 43 04 03 88 24 24
30 82 01 C3 30 17 06 0C 2B 06 01 04 01 93 0F 01
02 12 01 00 04 07 47 61 74 65 77 61 79 30 11 06
0C 2B 06 01 04 01 93 0F 01 02 12 02 00 02 01 65
30 16 06 0C 2B 06 01 04 01 93 0F 01 02 12 03 00
04 06 30 30 36 35 44 33 30 24 06 0C 2B 06 01 04
01 93 0F 01 02 12 04 00 04 14 50 72 6F 63 65 73
73 20 63 6F 6E 74 72 6F 6C 20 74 61 73 6B 30 1E
06 0C 2B 06 01 04 01 93 0F 01 02 12 05 00 04 0E
53 79 73 74 65 6D 20 77 61 72 6E 69 6E 67 30 12
06 0C 2B 06 01 04 01 93 0F 01 02 12 06 00 02 02
01 91 30 23 06 0C 2B 06 01 04 01 93 0F 01 02 12
07 00 04 13 32 30 30 32 2D 30 38 2D 31 33 2D 31
30 2E 35 32 2E 31 33 30 1E 06 0C 2B 06 01 04 01
93 0F 01 02 12 08 00 04 0E 4D 6F 64 75 6C 65 20
73 74 6F 70 70 65 64 30 46 06 0C 2B 06 01 04 01
93 0F 01 02 12 09 00 04 36 4D 6F 64 75 6C 65 20
68 61 73 20 62 65 65 6E 20 73 74 6F 70 70 65 64
20 62 79 20 6F 70 65 72 61 74 6F 72 20 28 6C 6F
63 61 6C 20 6F 72 20 72 65 6D 6F 74 65 29 2E 30
12 06 0C 2B 06 01 04 01 93 0F 01 02 12 0A 00 02
02 01 F5 30 81 81 06 0C 2B 06 01 04 01 93 0F 01
02 12 0B 00 04 71 44 6F 6D 61 69 6E 20 63 6F 6E
74 72 6F 6C 20 74 61 73 6B 20 69 6E 20 4D 6F 6E
69 74 6F 72 20 31 30 31 28 41 33 29 20 69 6E 69
74 69 61 74 65 64 20 73 68 75 74 64 6F 77 6E 20
28 4E 61 6D 65 3A 20 53 79 73 74 65 6D 20 4D 6F
6E 69 74 6F 72 2C 20 52 65 61 73 6F 6E 63 6F 64
65 3A 20 4E 6F 20 65 72 72 6F 72 20 6F 63 63 75
72 72 65 64 2E 29 2E
PDU:
version: 0
community: public
type: TRP_MSG (0xa4)
enterprise: 1.3.6.1.4.1.2447.1.2
IP agent addr: ichh2s101.faxdev.ic
generic: enterpriseSpecific(6)
specific: 5
time stamp: 59253796
name: 1.3.6.1.4.1.2447.1.2.18.1.0
type: OCTET STRING (0x4)
length: 7
value: Gateway ( 47 61 74 65 77 61 79 )
name: 1.3.6.1.4.1.2447.1.2.18.2.0
type: INTEGER (0x2)
length: 4
value: 101
name: 1.3.6.1.4.1.2447.1.2.18.3.0
type: OCTET STRING (0x4)
length: 6
value: 0065D3 ( 30 30 36 35 44 33 )
name: 1.3.6.1.4.1.2447.1.2.18.4.0
type: OCTET STRING (0x4)
length: 20
value: Process control task ( 50 72 6f 63 65 73 73 20 63 6f 6e 74 72 6f 6c 20 74 61 73 6b )
name: 1.3.6.1.4.1.2447.1.2.18.5.0
type: OCTET STRING (0x4)
length: 14
value: System warning ( 53 79 73 74 65 6d 20 77 61 72 6e 69 6e 67 )
name: 1.3.6.1.4.1.2447.1.2.18.6.0
type: INTEGER (0x2)
length: 4
value: 401
name: 1.3.6.1.4.1.2447.1.2.18.7.0
type: OCTET STRING (0x4)
length: 19
value: 2002-08-13-10.52.13 ( 32 30 30 32 2d 30 38 2d 31 33 2d 31 30 2e 35 32 2e 31 33 )
name: 1.3.6.1.4.1.2447.1.2.18.8.0
type: OCTET STRING (0x4)
length: 14
value: Module stopped ( 4d 6f 64 75 6c 65 20 73 74 6f 70 70 65 64 )
name: 1.3.6.1.4.1.2447.1.2.18.9.0
type: OCTET STRING (0x4)
length: 54
value: Module has been stopped by operator (local or remote). ( 4d 6f 64 75 6c 65 20 68 61 73 20 62 65 65 6e 20 73 74 6f 70 70 65 64 20 62 79 20 6f 70 65 72 61 74 6f 72 20 28 6c 6f 63 61 6c 20 6f 72 20 72 65 6d 6f 74 65 29 2e )
name: 1.3.6.1.4.1.2447.1.2.18.10.0
type: INTEGER (0x2)
length: 4
value: 501
name: 1.3.6.1.4.1.2447.1.2.18.11.0
type: OCTET STRING (0x4)
length: 113
value: Domain control task in Monitor 101(A3) initiated shutdown (Name: System Monitor, Reasoncode: No error occurred.). ( 44 6f 6d 61 69 6e 20 63 6f 6e 74 72 6f 6c 20 74 61 73 6b 20 69 6e 20 4d 6f 6e 69 74 6f 72 20 31 30 31 28 41 33 29 20 69 6e 69 74 69 61 74 65 64 20 73 68 75 74 64 6f 77 6e 20 28 4e 61 6d 65 3a 20 53 79 73 74 65 6d 20 4d 6f 6e 69 74 6f 72 2c 20 52 65 61 73 6f 6e 63 6f 64 65 3a 20 4e 6f 20 65 72 72 6f 72 20 6f 63 63 75 72 72 65 64 2e 29 2e )
BUG: SSAOidCmp(): oid1 is NULLSESSIONS:
NUMBER OF SESSIONS: 0
---------- cut here ----------
Is that a bug in snmpdx or is there a configuration problem?
This is what I get when I start snmpdx in debug mode, and since I don't know how to attach files to this posting (any tips?) I added this to this (now quite log) posting. So sorry for this...
---------- cut here ----------
root@ICHH2S101 /etc/snmp/conf >01 /etc/snmp/conf >/usr/lib/snmp/snmpdx -y -c /etc/snmp/conf -d 4
Local IP Addresss : 192.168.21.101
SUBTREES:
1.3.6.1.4.1.42.2.15 1 1 relay-agent 161 1
AGENTS:
444C8 relay-agent localhost.161 900000000 1 3 0 0
MANAGERS:
* 0
COMMUNITIES(READ_WRITE): private public
#EFILTER:
enterprise="1.3.6.1.4.1.2447.1.2"
trap-num=403 community-string: public
ichh2s15 192.168.21.15
trap-num=401 community-string: public
ichh2s15 192.168.21.15
trap-num=805 community-string: public
ichh2s15 192.168.21.15
trap-num=301 community-string: public
ichh2s15 192.168.21.15
trap-num=205 community-string: public
ichh2s15 192.168.21.15
trap-num=32 community-string: public
ichh2s15 192.168.21.15
trap-num=31 community-string: public
ichh2s15 192.168.21.15
trap-num=30 community-string: public
ichh2s15 192.168.21.15
trap-num=29 community-string: public
ichh2s15 192.168.21.15
trap-num=28 community-string: public
ichh2s15 192.168.21.15
trap-num=27 community-string: public
ichh2s15 192.168.21.15
trap-num=26 community-string: public
ichh2s15 192.168.21.15
trap-num=25 community-string: public
ichh2s15 192.168.21.15
trap-num=24 community-string: public
ichh2s15 192.168.21.15
trap-num=23 community-string: public
ichh2s15 192.168.21.15
trap-num=22 community-string: public
ichh2s15 192.168.21.15
trap-num=21 community-string: public
ichh2s15 192.168.21.15
trap-num=20 community-string: public
ichh2s15 192.168.21.15
trap-num=19 community-string: public
ichh2s15 192.168.21.15
trap-num=18 community-string: public
ichh2s15 192.168.21.15
trap-num=17 community-string: public
ichh2s15 192.168.21.15
trap-num=16 community-string: public
ichh2s15 192.168.21.15
trap-num=15 community-string: public
ichh2s15 192.168.21.15
trap-num=14 community-string: public
ichh2s15 192.168.21.15
trap-num=13 community-string: public
ichh2s15 192.168.21.15
trap-num=12 community-string: public
ichh2s15 192.168.21.15
trap-num=11 community-string: public
ichh2s15 192.168.21.15
trap-num=10 community-string: public
ichh2s15 192.168.21.15
trap-num=9 community-string: public
ichh2s15 192.168.21.15
trap-num=8 community-string: public
ichh2s15 192.168.21.15
trap-num=7 community-string: public
ichh2s15 192.168.21.15
trap-num=6 community-string: public
ichh2s15 192.168.21.15
trap-num=5 community-string: public
ichh2s15 192.168.21.15
trap-num=4 community-string: public
ichh2s15 192.168.21.15
trap-num=3 community-string: public
ichh2s15 192.168.21.15
trap-num=2 community-string: public
ichh2s15 192.168.21.15
trap-num=1 community-string: public
ichh2s15 192.168.21.15
TRAP RECIPIENTS:
PDU:
version: 0
community: public
type: GET_REQ_MSG (0xa0)
request id: 0
error status: noError(0)
error index: 0
name: 1.3.6.1.2.1.7
type: NULL (0x5)
length: 0
value: ( )
PACKET:
30 24 02 01 00 04 06 70 75 62 6C 69 63 A0 17 02
01 00 02 01 00 02 01 00 30 0C 30 0A 06 06 2B 06
01 02 01 07 05 00
sent 38 bytes to ichh2s101.faxdev.ic.47228Waiting for incoming SNMP requests on UDP port 161
SESSIONS:
NUMBER OF SESSIONS: 0
---------- cut here ----------
ichh2s15 (192.168.21.15) is the SNMP management station running HP OpenView listening for SNMP traps. From there, I can also query my mib subtree.
Please let me know if you need more information.
Many thanks in advance.
Michael Kwasigroch,
FaxPlus/Open Development
Intercope Hamburg Germany

Ok,
:: shame on me ::
adding the enterprise oid used in our traps to /etc/snmp/conf/enterprises.oid did the trick, now it works.
However, does anybody have any clarification about the parameters in the *.acl files?
Thanks in advance,
- Michael

Launching application from consoleone alarm disposition.

Hi!
I can't get this to work. I enable launching application for a certain
alarm but nothing happens. For example i've tried starting notepad when a
system: nlm loaded alarm arrives. But nothing. And i can't find a way to
debug this either....
Forwarding snmp traps and sending smtp works btw.
I run ConsoleOne locally on my machine and i enter the path to the
application as: c:\progran\applicationdir\application.exe
Thanks
/Tobias

[email protected] schrieb:
> Hi!
>
> I can't get this to work. I enable launching application for a certain
> alarm but nothing happens. For example i've tried starting notepad when a
> system: nlm loaded alarm arrives. But nothing. And i can't find a way to
> debug this either....
> Forwarding snmp traps and sending smtp works btw.
> I run ConsoleOne locally on my machine and i enter the path to the
> application as: c:\progran\applicationdir\application.exe
>
> Thanks
>
> /Tobias
Hi Tobias,
The alarm action is done on the management server- so you have to
configure Netware Server Actions.
Please check the
docu:http://www.novell.com/documentation/...a/acqbya8.html
will give you:
Launching an External Program
As part of editing the disposition of an alarm, you can set options to
automatically launch any program on the Novell ZENworks Server
Management server when an alarm is received. For example, you might want
an alarm to launch a program that sends a message to the system
administrator's pager.
Although ZENworks Server Management provides the capability to launch
applications, the product does not provide any predefined programs.
However, you can launch an NLM and run scripting routines or use
third-party programs.

Forwarding of traps

Similar Messages

Maybe you are looking for