md3000 sas w/ md1000 sata

Hello...

Is there a md3000 firmware that will allow the md3000 with SAS drives to
also control a md1000 (A04 firmware) with SATA drives?

Right now I am getting "unsupported config". 

thanks

--

-- 
Christopher McCrory
 "The guy that keeps the servers running"

chrismcc <at> pricegrabber.com
 http://www.pricegrabber.com

Let's face it, there's no Hollow Earth, no robots, and
no 'mute rays.' And even if there were, waxed paper is
no defense.  I tried it.  Only tinfoil works.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Multipath , iSCSI and the MD3000i

  I'm having terrible trouble actually getting multipath failover to 
work with an MD3000i on RHEL 5.2.

  I can talk to the array fine, but I have no path redundancy - if I 
reboot a controller or pull one of the LAN cables, the machine hangs on 
access to the filesystem that was being accessed via the now missing 
path, it doesn't swap to the alternate controller.

  I've got multipathd running, multpath -l shows multiple paths, but 
fail-over never actually happens.

  If any one else has some ideas i'll post the multipath config and the 
path output.

  I'm assuming there is something wrong with the path selection.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

RE: Multipath , iSCSI and the MD3000i

The MD3000i is typically configured with two RAID controller modules. At
any given time, a virtual disk is owned by one of the two RAID
controller modules. Ownership of the virtual disk does not automatically
transition in response to network failures, and multipathd has no means
by which to tell the MD3000i to change virtual disk ownership. The
solution is to abandon multipathd for this application and use the
multipathing software that is provided with the MD3000i.

Thomas

-----Original Message-----
From: linux-poweredge-bounces <at> lists.us.dell.com
[mailto:linux-poweredge-bounces <at> lists.us.dell.com] On Behalf Of Matthew
Geier
Sent: Monday, June 01, 2009 4:09 PM
To: linux-poweredge-Lists
Subject: Multipath , iSCSI and the MD3000i

  I'm having terrible trouble actually getting multipath failover to 
work with an MD3000i on RHEL 5.2.

  I can talk to the array fine, but I have no path redundancy - if I 
reboot a controller or pull one of the LAN cables, the machine hangs on 
access to the filesystem that was being accessed via the now missing 
path, it doesn't swap to the alternate controller.

  I've got multipathd running, multpath -l shows multiple paths, but 
fail-over never actually happens.

  If any one else has some ideas i'll post the multipath config and the 

PE Hardware monitoring best practices for Linux

Can anyone give me advise, hopefully based on experience, for best proactive 
hardware monitoring practices for PowerEdge servers under Linux

What tools have you found reliable?

Thanks,

	JW

--

-- 

----------------------
System Administrator - Cedar Creek Software
http://www.cedarcreeksoftware.com

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

RE: PE Hardware monitoring best practices for Linux

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: PE Hardware monitoring best practices for Linux

On Mon, Jun 01, 2009 at 09:13:41PM -0500, SA wrote:
> Can anyone give me advise, hopefully based on experience, for best proactive 
> hardware monitoring practices for PowerEdge servers under Linux
> 
> What tools have you found reliable?

Bit of a hacky 'tool' but one of the things we do is to:
* run 'ipmitool sel list' saving the output to a temp file;
* diff the file with the previous and mail the differences.

Quick and hacky but so far has been reliable and told us when things have
died/been unhappy.

Andrew

--

-- 
Systems Developer

e: andrew.nicols <at> luns.net.uk
im: a.nicols <at> jabber.lancs.ac.uk
t: +44 (0)1524 5 10147

Lancaster University Network Services is a limited company registered in
England and Wales. Registered number: 4311892. Registered office:
University House, Lancaster University, Lancaster, LA1 4YW

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: PE Hardware monitoring best practices for Linux

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

APIC error on CPU0: 00(60),APIC error on CPU0: 60(60) on PE2850

Hi,

has anybody seen this kernel messages with EL4 U8 - 2.6.9-89.ELsmp X86_64?

Sys: PE2850 8GB RAM

APIC error on CPU0: 00(60)
APIC error on CPU0: 60(60)
APIC error on CPU0: 60(60)
APIC error on CPU0: 60(60)
APIC error on CPU1: 00(60)
APIC error on CPU0: 60(60)
APIC error on CPU1: 60(60)
APIC error on CPU1: 60(60)

Something to be concerned?
Other than that, server runs fine and OpenManage log is clear.

Thx
Rainer

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Open_Source

Dear Experts,

I want to know out of your experience people the following,
1- How open source served your businesses  requirements?
2- What kind of application that running on Open Source?
3- General experience with Open Source technology?

Your input would be really appreciated.

Thanks
madunix

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: PE Hardware monitoring best practices for Linux

SA wrote:
> Can anyone give me advise, hopefully based on experience, for best
> proactive hardware monitoring practices for PowerEdge servers under
> Linux

"Best practice" is a strange concept.

But I find it easy to install OpenManage and then monitor at least the 
following SNMP parameter:

  MIB-Dell-10892::systemStateGlobalSystemStatus.1
also known as:
  .1.3.6.1.4.1.674.10892.1.200.10.1.2.1

We use Nagios' check_snmp to watch it, using the following command:

define command{
    command_name    check_snmp_dell_systemStateGlobalSystemStatus
    command_line    $USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o
.1.3.6.1.4.1.674.10892.1.200.10.1.2.1 -w 3 -c 6:5
}

Then, if we get an alarm, we log into the openmanage web interface
at https://servername:1311 and investigate further.

Sometimes, we get a warning due to a battery performing a self 
test. Other than that we don't get false alarm from monitoring
systemStateGlobalSystemStatus

--

-- 
Regards,
Troels Arvin <troels <at> arvin.dk>
http://troels.arvin.dk/

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq