<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EVA alarms in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136668#M26032</link>
    <description>&lt;!--!*#--&gt;Excuse do not speak English very well.&lt;BR /&gt;I'm trying to configure a linux server for the storage of a Trap&lt;BR /&gt;I have HP EVA 4400 and I have to configure so that we can receive TRAP abnormalities found in powertrain.&lt;BR /&gt;I might indicate a TOOL for LINUX affinchÃ¨ TRAP can filter that I need and identify anomalies?&lt;BR /&gt;I use nagios to monitor servers and thr take information on their status&lt;BR /&gt;But for the TRAP I read many articles but I can not make the decisive step for my work.&lt;BR /&gt;I can show or give inidicazioni to configure Nagios to receive TRAP and decrypt the message arrives&lt;BR /&gt;&lt;BR /&gt;THANKS</description>
    <pubDate>Fri, 26 Jun 2009 11:23:13 GMT</pubDate>
    <dc:creator>MAX72</dc:creator>
    <dc:date>2009-06-26T11:23:13Z</dc:date>
    <item>
      <title>EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136661#M26025</link>
      <description>Hi all:&lt;BR /&gt;&lt;BR /&gt;Had an EVA 8000 lose a drive yesterday. Did it routine and called home via ISEE. Problem was HP only calls the primary contact, and being a Sunday the primary contact was not in the office. The result was 15+ hrs to find out a disk was bad and to get a replacement. &lt;BR /&gt;&lt;BR /&gt;My question - I am running Nagios 2.9 in our environment. I would like some insight on how to query the EVAs (8000 &amp;amp; 5000) so we can be alerted ASAP.</description>
      <pubDate>Mon, 28 Jan 2008 15:59:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136661#M26025</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2008-01-28T15:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136662#M26026</link>
      <description>ISEE also sends a copy of the report to a customer configurable e-mail. And you can put 3 contact persons and phone numbers on the ISEE configuration. Specify one cellullar for out of hours cases. Specify hours of availability as 24x7, if you put monday-friday 9 am to 5 pm, the case will be skipped and passed directly to bussiness hours support.</description>
      <pubDate>Mon, 28 Jan 2008 16:38:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136662#M26026</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2008-01-28T16:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136663#M26027</link>
      <description>We have been trying that and enlisting the ASE to help do that. This approach has not met with much success.&lt;BR /&gt;&lt;BR /&gt;Also, in an effort to automate our internal tracking process (an internal ticket # gets generated) we are looking to capture this info as well. &lt;BR /&gt;&lt;BR /&gt;Typical of the powers that be - generate more paper work. I want to automate the process to avoid the paper work.&lt;BR /&gt;&lt;BR /&gt;We are running HPUX 11.11 &amp;amp; 11.23. Our Nagios server is CentOS5. No WIN.</description>
      <pubDate>Mon, 28 Jan 2008 16:50:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136663#M26027</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2008-01-28T16:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136664#M26028</link>
      <description>My ISEE sends me email's when we have an issue with our EVA. Can you have an email address for Nagios that it will check?&lt;BR /&gt;&lt;BR /&gt;You could also have this email to ALL your IT staff (if you've got blackberries or similar). Someone will get it.&lt;BR /&gt;&lt;BR /&gt;We also still use a pager and we can send email's to our pager supplier which come through to the pager. Not sure if you can do this in the US.</description>
      <pubDate>Tue, 29 Jan 2008 05:37:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136664#M26028</guid>
      <dc:creator>Chris Rosan2</dc:creator>
      <dc:date>2008-01-29T05:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136665#M26029</link>
      <description>&lt;!--!*#--&gt;We use a "simple" check with SSSU, the only thing we check is the operational state. This is good for us, as at any alarm, operators connect to command view (read only) and check the status. The bad thing is that operations like cloning/snapshot changes the operational state of the eva, so every time you get an alarm, most won't be a problem.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;eva_check.sssu&lt;BR /&gt;==============&lt;BR /&gt;&lt;BR /&gt;set option on_error=continue&lt;BR /&gt;&lt;BR /&gt;select manager &lt;IP&gt; USERNAME=administrator PASSWORD=&lt;PASSWORD&gt;&lt;BR /&gt;ls system full&lt;BR /&gt;&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;eva_check&lt;BR /&gt;=========&lt;BR /&gt;&lt;BR /&gt;#!/bin/ksh&lt;BR /&gt;BODYFILE=/tmp/check_eva.body&lt;BR /&gt;LASTCHECK=`ls -la /etc/sssu.out | awk ' { print $6,$7,$8 }'`&lt;BR /&gt;&lt;BR /&gt;/usr/local/sbin/sssu "file /usr/local/sbin/eva_check.sssu" |grep -v PASSWORD  &amp;gt; /etc/sssu.out&lt;BR /&gt;&lt;BR /&gt;PROBLEM=`grep -w operationalstate /etc/sssu.out |grep -v good |wc -l`&lt;BR /&gt;&lt;BR /&gt;if  [ "$PROBLEM" -gt 0 ]; then&lt;BR /&gt;  echo "ATENCION: One storage EVA requires attention." &amp;gt; $BODYFILE&lt;BR /&gt;  echo "Verify the status using Command View" &amp;gt;&amp;gt; $BODYFILE&lt;BR /&gt;  echo &amp;gt;&amp;gt; $BODYFILE&lt;BR /&gt;  echo "EVA state detected at: $LASTCHECK;" &amp;gt;&amp;gt; $BODYFILE&lt;BR /&gt;  awk ' $1 == "objectname"  { STORAGE=$3 } \&lt;BR /&gt;  $1 == "operationalstate"  { STATE=$3 } \&lt;BR /&gt;  $1 == "connectionstatus" { print STORAGE, STATE } ' /etc/sssu.out  &amp;gt;&amp;gt; $BODYFILE&lt;BR /&gt;  mailx -s "Storage EVA requires attention!" user@domain.com &amp;lt; $BODYFILE&lt;BR /&gt;fi&lt;BR /&gt;&lt;/PASSWORD&gt;&lt;/IP&gt;</description>
      <pubDate>Tue, 29 Jan 2008 13:08:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136665#M26029</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-01-29T13:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136666#M26030</link>
      <description>Hi,&lt;BR /&gt;it can be done via WEBES in 2 ways - you can:&lt;BR /&gt;a) configure the notification to your preferred email adresses, this is only informative&lt;BR /&gt;b) configure the WEBES SNMP to send the traps into the system which can collect the SNMP traps and process them into the incident tickets&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Mar 2008 19:55:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136666#M26030</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-03-17T19:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136667#M26031</link>
      <description>Very interesting!&lt;BR /&gt;I am now trying to make the same test in combination with Nagios.&lt;BR /&gt;But obviously I need to have sssu installed on this Linux machine (/usr/sbin/sssu program). &lt;BR /&gt;&lt;BR /&gt;On the HP website I only found it for RedHat and Suse Linux and unfortunately without file type (neither rpm nor tar.gz). I want to compile it on Debian but no package exists for it.&lt;BR /&gt;Could anyone help?&lt;BR /&gt;thanks</description>
      <pubDate>Fri, 20 Mar 2009 13:19:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136667#M26031</guid>
      <dc:creator>ckuenzler</dc:creator>
      <dc:date>2009-03-20T13:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: EVA alarms</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136668#M26032</link>
      <description>&lt;!--!*#--&gt;Excuse do not speak English very well.&lt;BR /&gt;I'm trying to configure a linux server for the storage of a Trap&lt;BR /&gt;I have HP EVA 4400 and I have to configure so that we can receive TRAP abnormalities found in powertrain.&lt;BR /&gt;I might indicate a TOOL for LINUX affinchÃ¨ TRAP can filter that I need and identify anomalies?&lt;BR /&gt;I use nagios to monitor servers and thr take information on their status&lt;BR /&gt;But for the TRAP I read many articles but I can not make the decisive step for my work.&lt;BR /&gt;I can show or give inidicazioni to configure Nagios to receive TRAP and decrypt the message arrives&lt;BR /&gt;&lt;BR /&gt;THANKS</description>
      <pubDate>Fri, 26 Jun 2009 11:23:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-alarms/m-p/4136668#M26032</guid>
      <dc:creator>MAX72</dc:creator>
      <dc:date>2009-06-26T11:23:13Z</dc:date>
    </item>
  </channel>
</rss>

