Help with adding mibs to simple v3 config

2010-03-22 Thread Joseph L. Casale
Hi, For some time I have been using a simple v3 config such as: # snmpd.conf rwuser myuser priv in a fairly locked down environment. I now have to add functionality to monitor RHCS using the following from their KB entry: dlmod RedHatCluster/usr/lib64/cluster-snmp/libClusterMonitorSnmp.so vi

RE: Help with adding mibs to simple v3 config

2010-03-22 Thread Joseph L. Casale
>Concentrate on the dlmod entry, and check for any errors logged >by the agent when it starts up. Also try walking the dlmod table. Dave, Here's some new info that has me puzzled: # snmpwalk -v 3 ... hostname UCD-DLMOD-MIB::dlmodTable UCD-DLMOD-MIB::dlmodName.1 = STRING: RedHatCluster UCD-DLMOD-M

RE: Help with adding mibs to simple v3 config

2010-03-23 Thread Joseph L. Casale
>> http://www.linuxdynasty.org/howto-monitor-redhat-cluster-using-snmp-and-python.html > >The walk above should show this. >Note that you probably need to have snmpwalk explicitly load the >REDHAT-CLUSTER-MIB in order to see the names correctly: > >snmpwalk -m +REDHAT-CLUSTER-MIB -v 3 ... hostn

Processing traps

2010-07-10 Thread Joseph L. Casale
I am using a custom traphandler that pushes all traps through a Perl script and then filters so far for two conditions, SNMPv2-MIB::coldStart for reboots and SNMPv2-MIB::snmpTraps.6 for custom alerts used by locally run scripts that push text for the various events I am interested in knowing about

RE: Processing traps

2010-07-12 Thread Joseph L. Casale
>Shouldn't that be >snmptrap . 6 23 >rather than 5 23 . >? Whoops, yes, I did mean 6/23. So does it make sense to use .1.3.6.1.6.3.1.1.5.6 for both the enterprise-oid and the OID like this: snmptrap -v 1 -c public nms.domain.com .1.3.6.1.6.3.1.1.5.6 "" 6 23 "" \

RE: Processing traps

2010-07-12 Thread Joseph L. Casale
>The whole point about enterprise-specific traps is that they are >specific to a particular organisation ('enterprise'). Hence the name. >My idea of what trap #23 represents will be different to your idea >of what trap #23 represents. > >So the enterprise OID is used to identify whose set of enter

Windows binaries and v3

2011-02-14 Thread Joseph L. Casale
I am trying to install the windows binaries and enable v3 so I installed openssl as directed, then setup snmpd.conf to proxy through to the existing ms snmp server moved to a different port (as I have done several times) but this time the service won't start and the logfile is empty. Any ideas how

RE: Windows binaries and v3

2011-02-14 Thread Joseph L. Casale
>You could start by opening a command prompt and by running this command >(assuming C:\usr\bin is in PATH): > >snmpd -f -Lo Bart, It just crashes and exits w/o any error. I should have tested other binaries, none of them run w/o simply exiting. I have the runtime files installed afaik (I don't e

RE: Windows binaries and v3

2011-02-14 Thread Joseph L. Casale
>It just crashes and exits w/o any error. I should have tested other binaries, >none of them >run w/o simply exiting. I have the runtime files installed afaik (I don't even >recall ever >needing to before anyway). Turned out to be ssl related, the windows 1.0.0c binaries aren't compatible with

RE: Windows binaries and v3

2011-02-14 Thread Joseph L. Casale
>Yes, these have been built against openssl 0.9.x. Unfortunately I don't know a > public location where these binaries can be downloaded from. The wiki points to a source: http://www.slproweb.com/products/Win32OpenSSL.html Thanks, jlc -

iSCSI mounts not appearing in storage table

2011-08-25 Thread Joseph L. Casale
I have several new RHEL 6 based machines that unlike RHEL 5 do not enumerate storage info for iscsi based mounts. Anyone know what/why this has changed and a way around this? Thanks! jlc -- EMC VNX: the world's simplest

Interpreting trap data sent to a handler

2013-12-28 Thread Joseph L. Casale
I am working on a handler and a little unclear on how to extend it. Looking at rfc2089 section 3.3 to understand the v1 trap fields passed to a handler, the case I am needing to account for now are generic type 6 traps and the associated specific id. The packet nicely breaks out the generic and