Hi Chandrasekhar, I've attached the results from messages, nothing out of order here.
On this example server the version is 6.2.0, though on all other server it's updated to latest version... I'm trying to work out if what the problem is with this process so that I can decide if it's worth going through and configuring the alerts on the other servers which have the new version. All other servers are installed using http://linux.dell.com/repo/hardware/latest/ Name Server Administrator Version 6.2.0 Contains Adaptec FSA Adaptec FSA Data Engine 5.9.2 Hardware Abstraction Programming Interface 5.9.2 Instrumentation Services 5.9.2 Integrated Tunnel Provider 1.2.0 Regards Steve Tempest -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, 30 September 2010 3:55 PM To: [email protected]; Steve Tempest Subject: RE: OpenManage + Alerts Hi Steve, Please check the /var/log/messages for any Server Administrator events or error messages. What is the OMSA version you are using? Thanks, Chandrasekhar R Dell | OpenManage office +91 80 41178649 -----Original Message----- From: linux-poweredge-bounces-Lists On Behalf Of linux-poweredge-request-Lists Sent: Thursday, September 30, 2010 10:56 AM To: linux-poweredge-Lists Subject: Linux-PowerEdge Digest, Vol 75, Issue 51 Send Linux-PowerEdge mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.us.dell.com/mailman/listinfo/linux-poweredge or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..." Today's Topics: 1. Re: Identify disk on a SAS6iR controller (Tim Small) 2. Re: Identify disk on a SAS6iR controller (Barnaby Gray) 3. RE: Issues with OpenManage + CentOs 5.4 (Chris Szilagyi) 4. RE: Issues with OpenManage + CentOs 5.4 (Steve Tempest) 5. OpenManage + Alerts (Steve Tempest) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Sep 2010 18:40:27 +0100 From: Tim Small <[email protected]> Subject: Re: Identify disk on a SAS6iR controller To: Barnaby Gray <[email protected]> Cc: Dell Poweredge list server <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 29/09/10 17:35, Barnaby Gray wrote: > Is there a way to show the serial numbers of disks through the lsiutil > command line utility or otherwise? > Dunno about CentOS, but on Debian 5: # modprobe sg # lsscsi -g [0:0:0:0] disk SEAGATE ST3500620SS MS04 - /dev/sg0 [0:0:1:0] disk SEAGATE ST3500620SS MS04 - /dev/sg1 [0:1:0:0] disk Dell VIRTUAL DISK 1028 /dev/sda /dev/sg2 [1:0:0:0] cd/dvd TSSTcorp DVD+-RW TS-L633A D200 /dev/sr0 /dev/sg3 # sg_inq /dev/sg0 [.....] Unit serial number: 9QM9A34F # Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 ------------------------------ Message: 2 Date: Wed, 29 Sep 2010 18:50:33 +0100 From: Barnaby Gray <[email protected]> Subject: Re: Identify disk on a SAS6iR controller To: Dell Poweredge list server <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 29/09/2010 18:40, Tim Small wrote: > # modprobe sg > # lsscsi -g > [0:0:0:0] disk SEAGATE ST3500620SS MS04 - /dev/sg0 > [0:0:1:0] disk SEAGATE ST3500620SS MS04 - /dev/sg1 > [0:1:0:0] disk Dell VIRTUAL DISK 1028 /dev/sda /dev/sg2 > [1:0:0:0] cd/dvd TSSTcorp DVD+-RW TS-L633A D200 /dev/sr0 /dev/sg3 > # sg_inq /dev/sg0 > [.....] > Unit serial number: 9QM9A34F > # Cheers, worked a treat - for the archives on CentOS the packages are: yum install lsscsi sg3_utils In the meantime I'd given up and installed omsa - slight overkill for a SN! Very useful for future reference. Interestingly OMSA reports: Serial No. : WD-WCAS2208118581185 whereas sg_inq: Unit serial number: WD-WCAS22081185 So the OMSA output is a slightly garbled. Barnaby ------------------------------ Message: 3 Date: Wed, 29 Sep 2010 23:00:40 -0400 (EDT) From: "Chris Szilagyi" <[email protected]> Subject: RE: Issues with OpenManage + CentOs 5.4 To: [email protected] Cc: [email protected] Message-ID: <[email protected]> Content-Type: text/plain;charset=iso-8859-1 Wayne, I tried installing the RPMs for OMSA 5.5 as you suggested. It seems that they too are doing some sort of system check. "srvadmin-omilcore" installs fine. But, the remaining packages fail to install with the error: srvadmin-syscheck: This RPM is not supported on this system (sysid=009B) error: %pre(srvadmin-syscheck-5.5.0-364.i386) scriptlet failed, exit status 1 error: install: %pre scriptlet failed (2), skipping srvadmin-syscheck-5.5.0-364 I've tried adding "Tikanga" to /etc/redhat-release , however it does not help. Does anybody know of a way to get this to install? Thanks again in advance! -- Chris > In OM 6.1 we removed many of the install blockages. In the past, the > installation scripts would prevent installation on any unsupported > distribution or version. In 6.1, these checks have been replaced with > standard RPM dependency checks. At run time, there are a few checks within > our processes to ensure that we are running on Dell hardware that is not too > old. Note that the ability to install on a version/distribution does not > imply that it is officially supported or that it will work. > > The net of this is that you should be able to install OMSA on SELinlux if > the RPMs we are dependent on are installed. I believe there is a good > chance OMSA will work, but no guarantees. Try it and see. > > Wayne Weilnau > Systems Management Technologist > Dell | OpenManage Software Development > > Please consider the environment before printing this email. > > Confidentiality Notice | This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > or proprietary information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, > immediately contact the sender by reply e-mail and destroy all copies of the > original message. > > -----Original Message----- > From: linux-poweredge-bounces-Lists On Behalf Of Liberty Young > Sent: Wednesday, September 22, 2010 11:59 AM > To: Chris Szilagyi > Cc: linux-poweredge-Lists > Subject: Re: Issues with OpenManage + CentOs 5.4 > > what about SELinux? Is it enabled? > > On Thu, Sep 16, 2010 at 8:29 PM, Chris Szilagyi <[email protected]> > wrote: >> Hello: >> >> I recently set up a PowerEdge 2400 server running CentOS 5.4. ??I'm trying >> to >> get OpenManage 4.5 installed (last version that I could find, that >> supports >> the PowerEdge 2400). ??I installed everything using the supplied scripts, >> however when I try to start the services with "srvadmin-services.sh >> start", >> I get the following: >> >> Starting Systems Management Device Drivers: >> Starting dcdbas device driver: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? [ >> ??OK ??] >> Starting Systems Management Data Engine: >> Starting dcstor32d: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> ?? ??[ ??OK ??] >> Starting dcevt32d: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> ?? ?? [ ??OK ??] >> Starting OM Common Services: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> [ ??OK ??] >> invcol Error: extract(): Unable to create temporary files. Please ensure >> that there is enough space in the >> tmp folder. >> Starting Secure Port Server: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> [ ??OK ??] >> >> The disk has over 7 GB of free space, and permissions look OK on /tmp. >> ??Has >> anybody seen this problem or know of a solution? ??So far I'm stumped. >> >> Thank you !! >> -- >> Chris >> ------------------------------ Message: 4 Date: Thu, 30 Sep 2010 13:17:36 +1000 From: "Steve Tempest" <[email protected]> Subject: RE: Issues with OpenManage + CentOs 5.4 To: "Chris Szilagyi" <[email protected]>, <[email protected]> Cc: [email protected] Message-ID: <18941_1285816689_4CA40171_18941_16348_1_A6C7D453C45E694F843CB9E72847201 [email protected]> Content-Type: text/plain; charset="iso-8859-1" Here are the scripts that rpm runs.... preinstall scriptlet (using /bin/sh): [ ! -f "/etc/omreg.cfg" ] && "/etc/omreg.cfg file is not found" && exit 1 REG_KEY="openmanage.omilcore.installpath" INSTALL_DIR=`grep -i "^[[:space:]]*${REG_KEY}[[:space:]]*=" /etc/omreg.cfg | sed 's#^[^=]*=##; s#^[[:space:]]*##; s#[[:space:]]*$##'` FUNCS="${INSTALL_DIR}/omil/prereqcheck/Funcs.sh" . ${FUNCS} # check for proper system id SYSIDFILEPATH=`GetTemp` cat <<EOF >${SYSIDFILEPATH} [OPTIONS] VENDOR=DELL ProductVersion=5.5.0 BuildNumber=364 [SystemsSupported] 0106=PE4600 0109=PE6600 010A=PE6650 0121=PE2650 011B=PE1650 0123=PE2600 0124=PE1655MC 0141=PE650 014A=PE1750 0134=PE600SC 0135=PE1600SC 0165=PE750 0167=PE700SC 016C=PE1850 016D=PE2850 016E=PE2800 016F=PE6800 0170=PE6850 0183=PE1800 0185=PE800 018A=PE1855MC 01B6=PE850 01B7=PE830 01B8=PE1900 01B3=PE1950 01BB=PE1955 01B1=PE2900 01B2=PE2950 01E6=PE860 01E7=PE840 02C7=NX100 01EA=PE6950 0205=PE2970 01F0=PER900 0208=PEM600 020C=PEM605 020F=PER300 023C=PER200 023E=PVNF100 0210=PET300 025C=PEM805 027B=PEM905 0221=PER805 0223=PER905 020B=PET605 0295=DL2000 [HardwareSupported] 8086:1000=INTEL 8086:1001=INTEL 8086:1002=INTEL 8086:1004=INTEL 8086:1008=INTEL 8086:1009=INTEL 8086:100c=INTEL 8086:100d=INTEL 8086:100e=INTEL 8086:100f=INTEL 8086:1010=INTEL 8086:1011=INTEL 8086:1012=INTEL 8086:1026=INTEL 8086:1027=INTEL 8086:105e=INTEL 8086:1075=INTEL 8086:1076=INTEL 8086:107b=INTEL 8086:107d=INTEL 8086:107e=INTEL 8086:108a=INTEL 8086:10c7=INTEL 8086:10d6=INTEL 8086:10f0=INTEL 8086:10f1=INTEL 8086:1229=INTEL 14e4:163a=BROADCOM 14e4:1644=BROADCOM 14e4:1645=BROADCOM 14e4:1647=BROADCOM 14e4:1648=BROADCOM 14e4:164c=BROADCOM 14e4:164d=BROADCOM 14e4:164e=BROADCOM 14e4:1659=BROADCOM 14e4:165a=BROADCOM 14e4:1677=BROADCOM 14e4:167a=BROADCOM 14e4:16a7=BROADCOM 14e4:16ac=BROADCOM 14e4:16ae=BROADCOM 14e4:16c7=BROADCOM 101e:9063=DRAC2 1028:0007=DRAC3 1028:0008=DRAC3 1028:0009=DRAC3 1028:000c=DRAC3 1028:000d=DRAC3 1028:0010=DRAC4 1028:0011=DRAC4 [BladeSystems] 0124=PE1655MC 018A=PE1855MC 01BB=PE1955 0208=PEM600 020C=PEM605 025C=PEM805 027B=PEM905 EOF KEY="openmanage.sysidchkutlpath" FILE="/etc/omreg.cfg" # if SYSID is to be ignored, do not check for systemid! if [ -z "${OMIIGNORESYSID}" ]; then # if SYSID is NOT to be ignored [ ! -f "${FILE}" ] && ErrorMsg "srvadmin-syscheck: ${FILE} file is not found" && exit 1 SYSIDCHECKPATH=`grep -i "^[[:space:]]*${KEY}[[:space:]]*=" ${FILE} | sed 's#^[^=]*=##; s#^[[:space:]]*##; s#[[:space:]]*$##'` [ ! -f "${SYSIDCHECKPATH}" ] && ErrorMsg "srvadmin-syscheck: ${SYSIDCHECKPATH} file is not found" && exit 1 # look the sysid up in the syslist variable SYSID=`${SYSIDCHECKPATH} | grep "System ID" | sed 's#^.*0x##; s#[[:space:]].*$##'` VAL=`grep -i "^[[:space:]]*${SYSID}[[:space:]]*=" ${SYSIDFILEPATH} | sed 's#^[^=]*=##; s#^[[:space:]]*##; s#[[:space:]]*$##'` [ -z "${VAL}" ] && ErrorMsg "srvadmin-syscheck: This RPM is not supported on this system (sysid=${SYSID})" && exit 1 fi rm -f ${SYSIDFILEPATH} true #----------------------------------------------------------------------- ------- # post script #----------------------------------------------------------------------- ------- postinstall scriptlet (using /bin/sh): true #----------------------------------------------------------------------- ------- # preun script #----------------------------------------------------------------------- ------- preuninstall scriptlet (using /bin/sh): true #----------------------------------------------------------------------- ------- # postun script #----------------------------------------------------------------------- ------- postuninstall scriptlet (using /bin/sh): # Erase, not ugrade if [ $1 == 0 ]; then [ -d "${RPM_INSTALL_PREFIX}" ] && rmdir --ignore-fail-on-non-empty "${RPM_INSTALL_PREFIX}" [ -d /opt/dell ] && rmdir --ignore-fail-on-non-empty /opt/dell >/dev/null 2>&1 fi true ######################################################################## ####### # # Files List - indicates to RPM which files are to be packaged from the # build system and installed on the target system at install time # ######################################################################## ####### Regards Steve Tempest -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chris Szilagyi Sent: Thursday, 30 September 2010 1:01 PM To: [email protected] Cc: [email protected] Subject: RE: Issues with OpenManage + CentOs 5.4 Wayne, I tried installing the RPMs for OMSA 5.5 as you suggested. It seems that they too are doing some sort of system check. "srvadmin-omilcore" installs fine. But, the remaining packages fail to install with the error: srvadmin-syscheck: This RPM is not supported on this system (sysid=009B) error: %pre(srvadmin-syscheck-5.5.0-364.i386) scriptlet failed, exit status 1 error: install: %pre scriptlet failed (2), skipping srvadmin-syscheck-5.5.0-364 I've tried adding "Tikanga" to /etc/redhat-release , however it does not help. Does anybody know of a way to get this to install? Thanks again in advance! -- Chris > In OM 6.1 we removed many of the install blockages. In the past, the > installation scripts would prevent installation on any unsupported > distribution or version. In 6.1, these checks have been replaced with > standard RPM dependency checks. At run time, there are a few checks within > our processes to ensure that we are running on Dell hardware that is not too > old. Note that the ability to install on a version/distribution does not > imply that it is officially supported or that it will work. > > The net of this is that you should be able to install OMSA on SELinlux if > the RPMs we are dependent on are installed. I believe there is a good > chance OMSA will work, but no guarantees. Try it and see. > > Wayne Weilnau > Systems Management Technologist > Dell | OpenManage Software Development > > Please consider the environment before printing this email. > > Confidentiality Notice | This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > or proprietary information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, > immediately contact the sender by reply e-mail and destroy all copies of the > original message. > > -----Original Message----- > From: linux-poweredge-bounces-Lists On Behalf Of Liberty Young > Sent: Wednesday, September 22, 2010 11:59 AM > To: Chris Szilagyi > Cc: linux-poweredge-Lists > Subject: Re: Issues with OpenManage + CentOs 5.4 > > what about SELinux? Is it enabled? > > On Thu, Sep 16, 2010 at 8:29 PM, Chris Szilagyi <[email protected]> > wrote: >> Hello: >> >> I recently set up a PowerEdge 2400 server running CentOS 5.4. ??I'm trying >> to >> get OpenManage 4.5 installed (last version that I could find, that >> supports >> the PowerEdge 2400). ??I installed everything using the supplied scripts, >> however when I try to start the services with "srvadmin-services.sh >> start", >> I get the following: >> >> Starting Systems Management Device Drivers: >> Starting dcdbas device driver: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? [ >> ??OK ??] >> Starting Systems Management Data Engine: >> Starting dcstor32d: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> ?? ??[ ??OK ??] >> Starting dcevt32d: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> ?? ?? [ ??OK ??] >> Starting OM Common Services: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> [ ??OK ??] >> invcol Error: extract(): Unable to create temporary files. Please ensure >> that there is enough space in the >> tmp folder. >> Starting Secure Port Server: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? >> [ ??OK ??] >> >> The disk has over 7 GB of free space, and permissions look OK on /tmp. >> ??Has >> anybody seen this problem or know of a solution? ??So far I'm stumped. >> >> Thank you !! >> -- >> Chris >> _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq Notice This email and any attachments are strictly confidential and subject to copyright. They may contain privileged information. If you are not the intended recipient please delete the message and notify the sender. You should not read, copy, use, change, alter or disclose this email or its attachments without authorisation. The company and any related or associated companies do not accept any liability in connection with this email and any attachments including in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company or the views of any of our related or associated companies. ------------------------------ Message: 5 Date: Thu, 30 Sep 2010 15:25:35 +1000 From: "Steve Tempest" <[email protected]> Subject: OpenManage + Alerts To: <[email protected]> Message-ID: <18941_1285824351_4CA41F5F_18941_17788_1_A6C7D453C45E694F843CB9E72847201 [email protected]> Content-Type: text/plain; charset="us-ascii" Hi, I've setup the alerts on my server to execute an application when an error occurs but it's not working. Basically I've done the following: Configured the Alert.... omconfig system alertaction event=powersupply execappath=" /opt/asx_scripts/send_alert.pl" omconfig system alertaction event=powersupplywarn execappath=" /opt/asx_scripts/send_alert.pl" omconfig system alertaction event=tempwarn execappath=" /opt/asx_scripts/send_alert.pl" omconfig system alertaction event=tempfail execappath=" /opt/asx_scripts/send_alert.pl" omconfig system alertaction event=fanwarn execappath=" /opt/asx_scripts/send_alert.pl" I added the space in front of the script name as I found that the system would not accept it without and read on a forum thread that it's required. I can run the script from console as root and it sends the alert as I expect it to. As this is not working I'm wondering if some environment path is missing. Does anyone know how the alert is executed and which account executes it? If i go into the OM webpage after running above config I can see a tick next to all of the items in the "Execute Application" column. Here is the contents of the script that is executed #!/usr/bin/perl $desc=`omreport system alertlog 2>/dev/null | grep "Description" | head -1 | cut -f2-9 -d: | sed 's/ //'`; chomp($desc); $date=`omreport system alertlog 2>/dev/null | grep "Date and Time" | head -1 | cut -f2-9 -d: | sed 's/ //g' | sed 's/://g'`; chomp($date); $host=`omreport system summary 2>/dev/null | grep "Host Name" | head -1 | cut -f2-9 -d: | sed 's/ //'`; chomp($host); $tag=`omreport system summary 2>/dev/null | grep "Chassis Service Tag" | head -1 | cut -f2-9 -d: | sed 's/ //'`; chomp($tag); $attach="/tmp/$date.log"; `omreport system alertlog > "$attach"`; $send=`/opt/asx_scripts/sendEmail -f "[email protected]" -t "[email protected]" -u "System Error: $host SvcTag: $tag Time: $date" -m "$host SvcTag: $tag Error: $desc Time: $date" -a "$attach" -s "mailgateway.domain.com"`; exit; Any suggestions on how to debug this would be appreciated. I'm running the latest version of OMSA on Centos 5.5 x64 (fully patched). Regards Steve Tempest Notice This email and any attachments are strictly confidential and subject to copyright. They may contain privileged information. If you are not the intended recipient please delete the message and notify the sender. You should not read, copy, use, change, alter or disclose this email or its attachments without authorisation. The company and any related or associated companies do not accept any liability in connection with this email and any attachments including in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company or the views of any of our related or associated companies. ------------------------------ _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq End of Linux-PowerEdge Digest, Vol 75, Issue 51 *********************************************** Notice This email and any attachments are strictly confidential and subject to copyright. They may contain privileged information. If you are not the intended recipient please delete the message and notify the sender. You should not read, copy, use, change, alter or disclose this email or its attachments without authorisation. The company and any related or associated companies do not accept any liability in connection with this email and any attachments including in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company or the views of any of our related or associated companies.
[r...@process1 log]# cat messages* | egrep 'Server Administrator' Sep 29 21:00:17 process1 Server Administrator: Storage Service EventID: 2242 The Patrol Read has started.: Controller 0 (PERC 6/i Integrated) Sep 29 21:50:38 process1 Server Administrator: Storage Service EventID: 2243 The Patrol Read has stopped.: Controller 0 (PERC 6/i Integrated) Sep 22 21:00:15 process1 Server Administrator: Storage Service EventID: 2242 The Patrol Read has started.: Controller 0 (PERC 6/i Integrated) Sep 22 22:00:54 process1 Server Administrator: Storage Service EventID: 2243 The Patrol Read has stopped.: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:00 process1 Server Administrator: Instrumentation Service EventID: 1000 Server Administrator starting Sep 15 06:40:00 process1 Server Administrator: Instrumentation Service EventID: 1012 IPMI status Interface: OS Sep 15 06:40:00 process1 Server Administrator: Instrumentation Service EventID: 1001 Server Administrator startup complete Sep 15 06:40:05 process1 Server Administrator: Storage Service EventID: 2131 The current firmware version 6.0.2-0002 is older than the required firmware version 6.2.0-0012 for a controller of mode l 0x1F0C: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:05 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Shutdown command received from host: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:05 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Firmware initialization started (PCI ID 0060/1000/1f0c/1028): Controller 0 (PERC 6/i Integrated) Sep 15 06:40:05 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery Present: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:06 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Package version 6.0.2-0002: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:06 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Enclosure (SES) discovered on PD 20(c None/p0): Controller 0 (PERC 6/i Integrated) Sep 15 06:40:06 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Unexpected sense: Encl PD 20, CDB: 12 00 00 00 00 00, Sense: 70 00 06 00 00 00 00 0a 00 00 00 00 2 9 00 00 00 00 00: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:06 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: Encl PD 20: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:07 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: PD 00(e0x20/s0): Controller 0 (PERC 6/i Integrated) Sep 15 06:40:07 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: PD 01(e0x20/s1): Controller 0 (PERC 6/i Integrated) Sep 15 06:40:07 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Time established as 09/14/10 20:38:00; (58 seconds since power on): Controller 0 (PERC 6/i Integr ated) Sep 15 06:40:07 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery temperature is normal: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:08 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery started charging: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:08 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Current capacity of the battery is above threshold: Controller 0 (PERC 6/i Integrated) Sep 15 06:40:08 process1 Server Administrator: Storage Service EventID: 2095 SCSI sense data Sense key: 5 Sense code: 24 Sense qualifier: 0: Enclosure 0:0 Controller 0, Connector 0 Sep 15 07:29:04 process1 Server Administrator: Storage Service EventID: 2358 The battery charge cycle is complete.: Battery 0 Controller 0 Sep 15 21:00:13 process1 Server Administrator: Storage Service EventID: 2242 The Patrol Read has started.: Controller 0 (PERC 6/i Integrated) Sep 15 21:46:27 process1 Server Administrator: Storage Service EventID: 2243 The Patrol Read has stopped.: Controller 0 (PERC 6/i Integrated) Sep 5 15:02:02 process1 Server Administrator: Storage Service EventID: 2181 The controller battery Learn cycle will start in 24 hours.: Battery 0 Controller 0 Sep 6 10:02:48 process1 Server Administrator: Storage Service EventID: 2181 The controller battery Learn cycle will start in 5 hours.: Battery 0 Controller 0 Sep 6 15:22:23 process1 Server Administrator: Storage Service EventID: 2176 The controller battery Learn cycle has started.: Battery 0 Controller 0 Sep 6 15:23:28 process1 Server Administrator: Storage Service EventID: 2266 Controller log file entry: Battery is discharging: Battery 0 Controller 0 Sep 6 15:23:28 process1 Server Administrator: Storage Service EventID: 2248 The controller battery is executing a Learn cycle.: Battery 0 Controller 0 Sep 6 17:05:28 process1 Server Administrator: Storage Service EventID: 2278 The controller battery charge level is below a normal threshold.: Battery 0 Controller 0 Sep 6 17:05:28 process1 Server Administrator: Storage Service EventID: 2188 The controller write policy has been changed to Write Through.: Battery 0 Controller 0 Sep 6 17:05:29 process1 Server Administrator: Storage Service EventID: 2199 The virtual disk cache policy has changed.: Virtual Disk 0 (Virtual Disk 0) Controller 0 (PERC 6/i Integrated) Sep 6 17:34:13 process1 Server Administrator: Storage Service EventID: 2177 The controller battery Learn cycle has completed.: Battery 0 Controller 0 Sep 6 17:34:28 process1 Server Administrator: Storage Service EventID: 2247 The controller battery is charging.: Battery 0 Controller 0 Sep 6 17:34:28 process1 Server Administrator: Storage Service EventID: 2278 The controller battery charge level is below a normal threshold.: Battery 0 Controller 0 Sep 6 17:59:23 process1 Server Administrator: Storage Service EventID: 2279 The controller battery charge level is operating within normal limits: Battery 0 Controller 0 Sep 6 17:59:23 process1 Server Administrator: Storage Service EventID: 2189 The controller write policy has been changed to Write Back.: Battery 0 Controller 0 Sep 6 17:59:23 process1 Server Administrator: Storage Service EventID: 2199 The virtual disk cache policy has changed.: Virtual Disk 0 (Virtual Disk 0) Controller 0 (PERC 6/i Integrated) Sep 6 21:11:08 process1 Server Administrator: Storage Service EventID: 2358 The battery charge cycle is complete.: Battery 0 Controller 0 Sep 8 11:00:13 process1 Server Administrator: Storage Service EventID: 2242 The Patrol Read has started.: Controller 0 (PERC 6/i Integrated) Sep 8 11:42:20 process1 Server Administrator: Storage Service EventID: 2243 The Patrol Read has stopped.: Controller 0 (PERC 6/i Integrated) Sep 1 01:00:14 process1 Server Administrator: Storage Service EventID: 2242 The Patrol Read has started.: Controller 0 (PERC 6/i Integrated) Sep 1 02:32:18 process1 Server Administrator: Storage Service EventID: 2243 The Patrol Read has stopped.: Controller 0 (PERC 6/i Integrated) Sep 1 08:13:47 process1 Server Administrator: Storage Service EventID: 2247 The controller battery is charging.: Battery 0 Controller 0 Sep 1 09:31:47 process1 Server Administrator: Storage Service EventID: 2358 The battery charge cycle is complete.: Battery 0 Controller 0 Sep 2 15:01:58 process1 Server Administrator: Storage Service EventID: 2180 The controller battery Learn cycle will start in 4 days.: Battery 0 Controller 0 Sep 4 11:25:16 process1 Server Administrator: Instrumentation Service EventID: 1000 Server Administrator starting Sep 4 11:25:16 process1 Server Administrator: Instrumentation Service EventID: 1012 IPMI status Interface: OS Sep 4 11:25:16 process1 Server Administrator: Instrumentation Service EventID: 1001 Server Administrator startup complete Sep 4 11:25:21 process1 Server Administrator: Storage Service EventID: 2131 The current firmware version 6.0.2-0002 is older than the required firmware version 6.2.0-0012 for a controller of mode l 0x1F0C: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:21 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Shutdown command received from host: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:21 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Firmware initialization started (PCI ID 0060/1000/1f0c/1028): Controller 0 (PERC 6/i Integrated) Sep 4 11:25:22 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery Present: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:22 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Package version 6.0.2-0002: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:22 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Enclosure (SES) discovered on PD 20(c None/p0): Controller 0 (PERC 6/i Integrated) Sep 4 11:25:22 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Unexpected sense: Encl PD 20, CDB: 12 00 00 00 00 00, Sense: 70 00 06 00 00 00 00 0a 00 00 00 00 2 9 00 00 00 00 00: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:23 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: Encl PD 20: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:23 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: PD 00(e0x20/s0): Controller 0 (PERC 6/i Integrated) Sep 4 11:25:23 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Inserted: PD 01(e0x20/s1): Controller 0 (PERC 6/i Integrated) Sep 4 11:25:23 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Time established as 09/04/10 1:23:17; (57 seconds since power on): Controller 0 (PERC 6/i Integr ated) Sep 4 11:25:24 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery temperature is normal: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:24 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery started charging: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:24 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Current capacity of the battery is above threshold: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:24 process1 Server Administrator: Storage Service EventID: 2334 Controller event log: Battery relearn will start in 4 days: Controller 0 (PERC 6/i Integrated) Sep 4 11:25:25 process1 Server Administrator: Storage Service EventID: 2095 SCSI sense data Sense key: 5 Sense code: 24 Sense qualifier: 0: Enclosure 0:0 Controller 0, Connector 0 Sep 4 11:47:18 process1 Server Administrator: Storage Service EventID: 2358 The battery charge cycle is complete.: Battery 0 Controller 0 Sep 4 15:02:17 process1 Server Administrator: Storage Service EventID: 2180 The controller battery Learn cycle will start in 2 days.: Battery 0 Controller 0
_______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
