Tag Info

Hot answers tagged

4

It depends a lot. Different hardware devices, operating systems, and even applications, have differing levels of support. There are a couple of variants of SNMP out there as well, which just makes it even more fun. When it comes to operating systems, Windows, Linux, and Solaris all have native SNMP agents. You have to turn them on, but they're there. They ...


4

You'll need to have the snmp package installed. "sudo apt-get install snmp" should install it for you if you don't have it installed already. The package contains the command line tools for snmp from the Net-SNMP project. After the package is installed use either snmptrap or snmpinfor depending on what you are trying to learn. Look at the manpages and ...


3

Looks like you can use snmptrap: http://manpages.ubuntu.com/manpages/intrepid/man1/snmptrap.1.html Cheers


3

As far as i can read only ALOM CMT supports snmp traps directly. Anyway you could do it passing through sunmc agent, as stated here: http://wikis.sun.com/display/ASRSO/Sun+T1+T2 (read Advanced Lights Out Manager (ALOM) Requirements) Hope this helps.


2

At a minimum, you need to define trapsink, trap2sink or informsink in /etc/snmp/snmpd.conf to specify the host to send SNMP traps to. You can also specify the community string and an alternate port number (if not using 162). You can also set a trapcommunity for a default community string to be used when sending traps. For sending v3 traps, use trapsess. ...


2

I posted this in the chat window awhile back, but it looks like you may have left it. Your snmptt.ini file has the following translation options set : translate_log_trap_oid = 1 translate_value_oids = 1 translate_enterprise_oid_format = 1 translate_trap_oid_format = 0 translate_varname_oid_format = 0 translate_integers = 1 The interesting one is the ...


2

Restart the snmpd service, service snmpd restart. That should send agent shutdown/start traps.


2

You can use snmptrap - see http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap.html for more details.


2

Traps trade consuming memory and processing resources on the switch for reduced network usage. Counters, status registers etc on network gear Polling and tracking the above Taking actions Doing (2) and part of (3) on the switch means less network traffic querying SNMP MIBs. This would be a win if you have one piece of network gear at a remote ...


2

Put to your snmptt.ini file line mibs_environment = ALL And restart snmptt. See if that helps.


2

Net-snmp can be configured to make internal SNMP query and send traps from DISMAN-EVENT-MIB when disk usage exceeds defined threshold. In order to send traps for the disk usage, add the following lines to snmpd.conf and restart the agent: # trap target and community trap2sink localhost public # authorization for self monitoring createUser ...


1

The snmpttconvertmib script relies on the the Net-SNMP snmptranslate utility to process the MIB files behind-the-scenes. The snmptranslate tool looks for dependent MIB files in the directories specified in the MIBDIRS environment variable. Are you certain that snmptranslate is looking in the right place in your scenario?


1

There's not much special to SNMP configuration on linux. Net-SNMP is probably one of the more popular options. The process is basically the same on linux as windows. Just make sure SNMP is installed, configured, and allowed through the firewall. Check out http://wiki.zenoss.org/Configure_SNMPv3 http://www.net-snmp.org/docs/man/snmpd.conf.html As far as ...


1

For mine I use: snmp-server enable traps entity config-change This captures any running or startup config changes. The fru-insert and fru-remove should capture hardware changes (not problems with existing but actual inserts or removals of modules). I know you specified the community in the snmp-server host line but do you also have a line for snmp-server ...


1

Turns out the issue was DNS look ups timing out so I just pushed the -n flag to the options lines in /etc/defaults/snmpd. This was on Debian 6.0. # snmpd options (use syslog, close stdin/out/err). SNMPDOPTS='-Lsd -Lf /var/log/snmpd.log -n -u snmp -g snmp -I -smux -p /var/run/snmpd.pid' # snmptrapd options (use syslog). TRAPDOPTS='-Lsd ...


1

I would try snmp-server enable traps config and then go in and out of configure mode. That is manually, but you can do it as often as you want. Or, you can do snmp-server enable traps event-manager and write your own EEM script to do things, but that's not my area of expertise unfortunately.


1

Seems like some confusion on your part. All you need to do on the AP is set it to send traps to the IP of your listener. Then, you need to build a listener - seems like you need to write a TCP server in Perl, so of course you couldn't use any existing SNMPD daemons. You shouldn't be using Perl and Expect to login to the AP, unless you're also supposed to be ...


1

php://stderr is not a stream that can be read from. It is a pipe to the STDERR for the PHP process itself, which is write-only. You need to access the data via STDIN. Rather than using the php:// wrapper to access the STDIO streams, which is known to be buggy (see the manual) you should use the special constants STDOUT, STDERR and STDIN. So for example, I ...


1

The RFC Alarm MIB is used to describe the alarms/notifications that you will be implementing in your own MIB for your own agent. The RFC Alarm MIB is related to your MIB in that the RFC Alarm MIB will create and list of your alarms and describe information about the alarms/notifications that are common with all alarms. Your MIB will be different in that ...


1

Comments are for humans - by definition they pretty much need to be inserted into the file by hand by (more knowledgeable) humans. If you need to have comments in your files I suggest a template file (with comments and $variable blocks to substitute in appropriate values for things that might change, like subnets and community strings) -- When you make a ...


1

Try the following: snmptrap.exe -v 2c -c xxxxxxx 192.168.100.65 '' .1.3.6.1.4.1.5089.1.0.1 .1.3.6.1.4.1.5089.2.0.999 s "123456" '' <- the first parameter for v2c trap is the agent uptime, it is mandatory and empty parameter will be replaced with current value .1.3.6.1.4.1.5089.1.0.1 <- trap OID .1.3.6.1.4.1.5089.2.0.999 <- varbind (this needs ...


1

OMSA is needed, unless you have a more conclusive management system in place, which would support PERC/CERCs



Only top voted, non community-wiki answers of a minimum length are eligible