AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090415122336.53f9917d@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<patrick.haverty@onstor.com>,<rendell.fong@onstor.com>,<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31284F9B4D7@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 15 Apr 2009 12:24:11 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Patrick Haverty <patrick.haverty@onstor.com>
Cc: Rendell Fong <rendell.fong@onstor.com>, Brian Stark
 <brian.stark@onstor.com>
Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
Message-ID: <20090415122411.503e52c0@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB31284F9B4D7@exch1.onstor.net>
References: <20090415121422.72951c22@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB31284F9B4D7@exch1.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

On Wed, 15 Apr 2009 12:20:06 -0700 Patrick Haverty
<patrick.haverty@onstor.com> wrote:

> While not ideal to have the Leopard be a SNMP trap client, it could save us the cost of an optional RAC (Remote Access Controller) by allowing us to use the Nexenta SNMP to emailer route. 
> 

Hm, OK.  You must know something I don't. ~:^)  BTW, could you please
configure your email client (Outlick?) to autowrap at some reasonable
right margin, like 72 or whatever the default is?  Thankyouverymuch.


> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, April 15, 2009 12:14 PM
> To: Rendell Fong
> Cc: Patrick Haverty; Brian Stark
> Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
> 
> Well, there are two programs, snmptrapd and snmpd on nexenta/solaris.
> I assume that if you configure/run snmptrapd, that it will listen for traps.  Not exactly sure what that would accomplish for us.  Normally in a production environment I would not want a leopard also configured to be a SNMP trap host client.  Would I?  Yes, I'm very proud of myself for using the proper SNMP terminology.  One day when I'm older I'll actually know what it means.  Oops, I'm already older.  Sigh.
> 
> 
> On Wed, 15 Apr 2009 12:02:50 -0700 Rendell Fong <rendell.fong@onstor.com> wrote:
> 
> > If OpenSolaris has a command like netstat you can check to see if any process is listening on udp port 162.  This port is normally used for receiving SNMP trap msgs.
> > 
> > ________________________________
> > From: Patrick Haverty
> > Sent: Wednesday, April 15, 2009 11:41 AM
> > To: Andy Sharp; Rendell Fong
> > Cc: Brian Stark
> > Subject: Dell Openmanage IT Assistant and SNMP Messages
> > 
> > I disabled the IPMI over LAN function of the system (which would not
> work in "teamed" or aggregated port configuration) and then verified that hardware event messages were still being sent from the PowerEdge server and received by IT assistant running on a remote computer.
> SNMP_Message1.JPG shows the alert as it is received (bold highlighting) and SNMP_Message2.JPG just shows the complete set of messages (upper
> six) that come through when an AC cord is unplugged and then re-plugged.
> Note that the IP address 10.11.1.220 is the one setup in the BMC BIOS settings (mostly for IPMI use), so there is not any response to an SNMP query.  I think that means that if there is not any active monitoring when the event messages are sent, then they are lost.  I was unable to figure out how to get the BMC to send the alert to a destination that the Nexenta/OpenSolaris system noticed.  There may be an OpenSolaris service which could receive an SNMP alert, but when I tried setting up the appliances IP address as the destination address for alerts, I could not see any reflection in the /var/adm/messages file or NMS log file that would indicate the system saw the SNMP alert.
> > 
> > Pat
