AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090414120021.10973487@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<dmitry@nexenta.com>,<alex@nexenta.com>,<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 14 Apr 2009 12:00:57 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: 'Dmitry Yusupov' <dmitry@nexenta.com>
Cc: Alex Aizman <alex@nexenta.com>, Brian Stark <brian.stark@onstor.com>
Subject: storage JBOD fault reporting
Message-ID: <20090414120057.1c9dd707@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Dmitry,

I'm temporarily filling in for Larry as best I can, and I have a
question regarding snmp that I hope you can address.

I need to connect up log messages coming in from syslog that are caused
by non-disk fault events on the JBOD, like fan or power supply death
and so forth.

So I need to get those events into either the nexenta fault reporting
infrastructure, or simply comb that log data for the particular
messages we're looking for and use the snmptrap command to issue an
snmp trap.  The second option would be the easiest and quickest from my
point of view.  The problem is that it appears that only the snmpd and
snmptrapd are built and installed.  I assume that all the snmp commands
come from the same source package, so I'm hoping that you can just add
those other commands to the distro.

Let me know what you think.

Thanks,

a
