SNMP traps config

G Control 11.1
My scenario is ( 3 components):
Node A (managed, monitored) ---- GC box------ SNMP box (final destination).
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 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,

Solved

Similar Messages

SNMP trapping PRI channels up/down

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

Duplicate post.
Go HERE.

Generate SNMP TRAP when config changes

Hello,
Is there any way to generate a SNMP trap when new config is saved in ASA 5510?
We are running ASA 8.3
Thanks.

I have a clue about how to do it.
I use in the asa the fallowing command:
snmp-server host DMZ 10.153.50.5 community *****snmp-server enable traps entity config-change fru-insert fru-remove
And I setup a snmptrapd on a lin
/etc/snmp/snmptrapd.conf# Example configuration file for snmptrapd## No traps are handled by default, you must edit this file!# authCommunity log,execute,net public# traphandle SNMPv2-MIB::coldStart /usr/bin/bin/my_great_script coldux box.
But it doesn´t works when I do a config change, it doesn´t generate anything on the linux box log.
Any idea?
Thanks.

Migrating IOS to NX-OS equivalent command snmp-server enable traps config

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Hello,
I am trying to figure out what is the equivalent command to configure the IOS "snmp-server enable traps config" on a Nexus 5020 running NX-OS version 4.2.1.N2.1 ,can someone please help me with this problem.
Also I would like to know if there is a cisco howto document or tool to migrate from IOS to NX-OS ?
Any help is greatly appreciated
Thanks
Frank

Hello,
both Nexus 5k are not generating a trap after a config change, because on both Nexus running same NX-OS version show up the snmp-server enable traps config command. This is really strange behavior, because we are using the same software version for the Nexus 5k devices it doesn't make sense to me. In the meantime I checked the command line guide for this software version but the command wasnt showing up.
nx5k-mt-2# show snmp trap | grep config
nx5k-mt-2#
nx5k-mt-2# show snmp trap
Trap type                                                              Enabled
entity               : entity_mib_change                            Yes
entity               : entity_module_status_change                  Yes
entity               : entity_power_status_change                   Yes
entity               : entity_module_inserted                       Yes
entity               : entity_module_removed                        Yes
entity               : entity_unrecognised_module                   Yes
entity               : entity_fan_status_change                     Yes
link                 : linkDown                                     Yes
link                 : linkUp                                       Yes
link                 : extended-linkDown                            Yes
link                 : extended-linkUp                              Yes
link                 : cieLinkDown                                  Yes
link                 : cieLinkUp                                    Yes
link                 : connUnitPortStatusChange                     Yes
link                 : fcTrunkIfUpNotify                            Yes
link                 : fcTrunkIfDownNotify                          Yes
link                 : delayed-link-state-change                    Yes
link                 : fcot-inserted                                Yes
link                 : fcot-removed                                 Yes
callhome             : event-notify                                 Yes
callhome             : smtp-send-fail                               Yes
cfs                  : state-change-notif                           Yes
cfs                  : merge-failure                                Yes
fcdomain             : dmNewPrincipalSwitchNotify                   Yes
fcdomain             : dmDomainIdNotAssignedNotify                  Yes
fcdomain             : dmFabricChangeNotify                         Yes
rf                   : redundancy_framework                         Yes
aaa                  : server-state-change                          Yes
license              : notify-license-expiry                        Yes
license              : notify-no-license-for-feature                Yes
license              : notify-licensefile-missing                   Yes
license              : notify-license-expiry-warning                Yes
scsi                 : scsi-disc-complete                           Yes
fcns                 : reject-reg-req                               Yes
fcns                 : local-entry-change                           Yes
fcns                 : db-full                                      Yes
fcns                 : remote-entry-change                          Yes
rscn                 : rscnElsRejectReqNotify                       Yes
rscn                 : rscnIlsRejectReqNotify                       Yes
rscn                 : rscnElsRxRejectReqNotify                     Yes
rscn                 : rscnIlsRxRejectReqNotify                     Yes
fcs                  : request-reject                               Yes
fcs                  : discovery-complete                           Yes
fctrace              : route                                        Yes
zone                 : request-reject1                              Yes
zone                 : merge-success                                Yes
zone                 : merge-failure                                Yes
zone                 : default-zone-behavior-change                 Yes
zone                 : unsupp-mem                                   Yes
vsan                 : vsanStatusChange                             Yes
vsan                 : vsanPortMembershipChange                     Yes
fspf                 : fspfNbrStateChangeNotify                     Yes
upgrade              : UpgradeOpNotifyOnCompletion                  Yes
upgrade              : UpgradeJobStatusNotify                       Yes
feature-control      : FeatureOpStatusChange                        Yes
snmp                 : authentication                               Yes
nx5k-mt-2#
nx5k-mt-2#

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

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

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

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

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

SNMP Traps - Mangled packet issue

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

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

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

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.

CAM Event Log: SNMP trap is received from switch [ ip address ] which is NOT in our database.

We keep getting thousands of entries in the CAM event log like this:
SNMP trap is received from switch [<ip address>] which is NOT in our database.
apparently, these aren't NAC'd switches. Why does the CAM see these and how can they be eliminated from the Event Log?
Thanks,

Matt,
Do you switches have the CAM as a host where they are sending traps? Check the running-config of the servers and see if you spot the CAM IP address as one of the snmp-servers.
HTH,
Faisal

Veritas SNMP Traps

Hello to all,
I do not know if this is a right forum to ask this but anyway ...
I know that Solstice Disk suite (native Solaris Volume Manager) is capable of sending SNMP traps towards a SNMP receiver (Sun Net Manager, HP Network Node Manaher ...) upon any problems detected on volume management level.
Can Veritas Volume Manager do the same?

No probs, I have the answer.
It's "config"
int fc2/36
no link-state-trap
Cheers.

Generating RMON SNMP Traps

I am trying to generate SNMP traps from RMON events but they won't work. I have the following test configuration:
snmp-server host 10.1.1.1 version 2c TEST
snmp-server enable traps
rmon event 1 log trap PUBLIC description "TEST TEST TEST" owner config
rmon alarm 1 ifOutUcastPkts.6 5 delta rising-threshold 100 1 falling-threshold 50 1 owner config
When I enable 'debug snmp packet' I see don't see any packets being generated. I do see %RMON-5 syslog messages but I don't see any "TEST TEST TEST" messages in the console, although I do see them here:
show rmon events
Event 1 is active, owned by config
Description is TEST TEST TEST
Event firing causes log and trap to community PUBLIC,
last event fired at 0y0w0d,01:03:09,
Current uptime       0y0w0d,01:05:58
Current log entries:
index uptime              description
1      0y0w0d,01:02:59     TEST TEST TEST
2      0y0w0d,01:03:04     TEST TEST TEST
3      0y0w0d,01:03:09     TEST TEST TEST
Am I missing something? Thanks

Your RMON event community is PUBLIC, but your trap host is using community TEST. Set these two so that they agree. You will not see
the description on the console. You will only see that a rising or falling condition has occurred.
If you want more flexibility on these syslogs or traps, consider using EEM instead of RMON.

Cisco Prime SNMP Traps Best Pratice

The Cisco Prime documentation recommends configuring switches to send SNMP traps. However it does not give any more details.
I was wondering what sorts of SNMP traps people in the community are using with Cisco Prime 2.1. I'm looking for some sort of best practice or for an idea of what traps would be the most useful to configure on the switches, to send to Prime.

Hi ,
Snmp traps need to be configured only on device end , there is no config need to be done on PI.
you can enable all the traps that you want. for e.g
snmp-server enable traps syslog
snmp-server enable traps ipsec start stop
snmp-server enable traps memory-threshold
snmp-server enable traps interface-threshold
snmp-server enable traps connection-limit-reached
snmp-server enable traps cpu threshold rising
etc......
and you can monitor then in PI (Administration > System Settings > Severity Configuration, Link down)
check the below link as well:
https://supportforums.cisco.com/discussion/11919481/prime-infrastructure-20-link-status-alarms
Thanks-
Afroz
***Ratings Encourages Contributors ***

Curious message during activation of snmp traps in cisco router 2800

I activated snmp traps in cisco router 2800 (I didn't specify a set of them, so all of them were activated). The thing is, when i configure "snmp-server enable traps", appears a message in the next line :
" %Cannot enable both sham-link state-change interface traps.
%New sham link interface trap not enabled "
Anyway, traps are activated and are completely functional.
I would like to know, why this message appears... and also what is the difference between informs and traps, because I can activate both of the in a router to be sent to the network admin pc.
Thanks in advance.

Hi Marcelo,
the snmp-server enable traps command enables just all types of traps that the IOS version supports.
The message apperes because of this two, which are mutually exclusive:
R1(config)#snmp-server enable traps ospf cisco-specific state-change shamlink interfaceR1(config)#snmp-server enable traps ospf cisco-specific state-change shamlink interface-old% Cannot enable both sham-link state-change interface traps.% Deprecated sham link interface trap not enabled.
It's recommended to only enable the traps you really need.
Informs were introduced with SNMPv2, and they have the same format and purpose as traps.
The main difference is that traps are send in a hit-or-miss fashion whereas informs expect an acknowledge and will be re-send if unacknowledged.
Hope that helps
Rolf

SNMP traps config

Similar Messages

Maybe you are looking for