SUMMARY: RM6.22 Raid Event mail messages

From: Nicole Skyrca <nskyrca_at_appliedtheory.com>
Date: Fri Mar 01 2002 - 10:00:43 EST
I got a few responses to this. It seems that I'm not alone with
this situation. People did not recommend that I disable the
parity checking, especially for mission critical systems.  It
was recommended that I change the /usr/lib/osa/bin/rmscript
so that the email that I will recieve will show the result
of the parity check. This is what I ended up doing.

The line to change is from: 

# Mail the superuser that an event has occurred
(awk -F\~ 'NF > 0 { printf "An array event has been detected on Controller %s \n Device %s at Host %s - Time %s %s\n", $2, $3, $1, $4, $5 }' < $1;
echo "\nGo to the Message Log in the Status Application for details" ) | mailx - s "raid Event" root
 
to:
 
# Mail the superuser that an event has occurred
(awk -F\~ 'NF > 0 { printf "An array event has been detected on Controller %s \n Device %s at Host %s - Time %s %s\n %s", $2, $3, $1, $4, $5, $7 }' < $1;
echo "\nGo to the Message Log in the Status Application for details" ) | mailx - s "raid Event" root




This changes the email from:
 
  An array event has been detected on Controller 1T83601869 
  Device c0t5d0 at Host sun-s21.ajb.org - Time 02/24/2002 02:27:35
  Go to the Message Log in the Status Application for details

to:
  An array event has been detected on Controller 1T83620382 
  Device c1t5d0 at Host sun-s20.ajb.org - Time 02/26/2002 10:49:19
  No parity errors detected on db046_002.
  Go to the Message Log in the Status Application for details
 
 

I tested it work and it seemed to work, I'll find out for sure
this weekend when the normal parity check takes place.

 
Thanks to the following people:
Mark Butscher,  Lee Lazon , Ric Anderson,  Scott Howard , Bruce Perttunen

 




Nicole Skyrca
AppliedTheory Communications Inc.        Phone: 315-453-2912 x5861
125 Elwood Davis Road                    Fax: 315-453-4594 
Syracuse, New York 13212



--- Original Post -----

Hello,

I have several E4500's with A1000 arrays with Raid Manager 6.22
software.  Some of the E4500's have Solaris 2.6 installed and
some have Solaris 8 installed.

Each week, I get an email that has the following in it:

An array event has been detected on Controller 1T83601869 
  Device c0t5d0 at Host {hostname} - Time 02/24/2002 02:27:35

Go to the Message Log in the Status Application for details



When I go to the status window, I see messages such as:
2/24/2002  2:29:18    db046_002   General   -  c1t5d0


When I go to the show details section, I see that the 
Description says "No parity errors detected on db046_002".




I know that these are just informational messages, but
are these normal?  Is there a way to get rid of getting
this email when there is not a problem? I opened a ticket with
Sun and they told me to either disable paritiy checking (but
the manual recommends having automated parity checking), or
to comment out the mailx entries in the script /usr/lib/osa/bin/rmscript,
which would make me not get any messages, even if there is an error.

Can I get rid of just these, or should I just live with
getting the emails?

Thanks!


Nicole Skyrca
AppliedTheory Communications Inc.        Phone: 315-453-2912 x5861
125 Elwood Davis Road                    Fax: 315-453-4594 
Syracuse, New York 13212
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Fri Mar 1 09:01:10 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:35 EST