headers
J. Epperson | 1 Oct 2009 01:23

Re: PERC 320/DC in Precision 650 with RHEL5; Pitiful Disk Performance

On Wed, September 30, 2009 18:55, Charles Knox wrote:
> Hi all, For reasons of application compatibility I have recently upgraded
> a Precision 650 from RedHat 9 (which it shipped with) to RHEL5.  The disk
>  system in this machine is four 143GB SCSI drives as a RAID5 set on the
> PERC320/DC Adaptec built controller.  Before the update, the performance
> of the RAID was sort-of OK, no great shakes but I suspect it would do
> Read/Write operation at about 40MB/sec.  Since the update performance has
>  taken a BIG hit.  At first I could get only about 3 MB/sec on the RAID
> with the load on the system going up into the over 12 regime.  A web
> search on the aacraid driver plus performance yielded a hit at the SuSE
> site having to do with telling the driver to not do write caching with a
> modification to /etc/modprobe.conf; adding the line
>
> options aacraid cache=2
>
> I did this, and performance screamed up to 5-6MB/sec, but the load still
> skyrocketed when large writes were done.  Does anyone have any ideas
> about how to speed this up, aside from launching the PERC out the window
> and attaching the disks to the LSI controller in the system and trying
> software RAID?
>

Have not touched a  320 in a long time, but IIRC there's a background
consistency check option somewhere that if turned on will really bog down
a RAID 5.  Look for that.

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge <at> lists.us.dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen Vaughan | 1 Oct 2009 02:17
Picon

Re: OMSA won't install w/ yum - centos 4.8

It was a PE750, I ended up having to install 5.4, that was the only one that worked. The firmware rpms weren't installing on the newer version of OMSA, and the srvadmin packages weren't even recognised. I have an R410 which is only supported by 6.1, except 6.1 doesn't want to install on CentOS 4.8.. go figure

On Wed, Sep 30, 2009 at 9:51 PM, Matthew Willis <lilmatt <at> flock.com> wrote:
What PowerEdge is this on?  I had a similar experience (yum install
srvadmin-all failing with "Nothing to do") when attempting to install
6.1 on some older gear (1650, 1750).

I eventually looked through the hardware repositories ( http://linux.dell.com/repo/hardware/OMSA_6.0.2/
 vs. http://linux.dell.com/repo/hardware/OMSA_6.1/ ) and noticed a
lack of a "1650" or "1750" folder in 6.1.  When I switched to
installing 6.0.2 (which has those folders) things began working for me.

-lilmatt

On Sep 29, 2009, at 11:53 PM, Stephen Vaughan wrote:

> Hi,
>
> I've tried everything and I just cannot get it to work. I've
> followed the instructions on this page: http://linux.dell.com/repo/hardware/OMSA_6.1/
>
> Each time I try yum install srvadmin-all it can't locate the
> package. I've also tried yum search srvadmin and nothing shows up.
> Note this box was previously running RHEL4 w/ OMSA 5.4, the box was
> upgraded to centos 4.8 and then we removed the srvadmin rpm's.
> Plugins are enabled in yum.conf.
>
> This is the log:
>
> [root <at> box yum.repos.d]# wget -q -O - http://linux.dell.com/repo/hardware/OMSA_6.1/bootstrap.cgi
>  | bash
> Downloading GPG key: http://linux.dell.com/repo/hardware/OMSA_6.1/RPM-GPG-KEY-dell
>     Key already exists in RPM, skipping
> Downloading GPG key: http://linux.dell.com/repo/hardware/OMSA_6.1/RPM-GPG-KEY-libsmbios
>     Key already exists in RPM, skipping
> Downloading repository RPM
> Installing repository rpm: http://linux.dell.com/repo/hardware/OMSA_6.1/platform_independent/rh40/prereq/dell-omsa-repository-2-5.noarch.rpm
> Installing yum plugins for system id
> Setting up Install Process
> Setting up repositories
> Reading repository metadata in from local files
> Parsing package install arguments
> Resolving Dependencies
> --> Populating transaction set with selected packages. Please wait.
> ---> Package yum-dellsysid.i386 0:2.2.17-3.1.el4 set to be updated
> --> Running transaction check
>
> Dependencies Resolved
>
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
>  Package                 Arch       Version
> Repository        Size
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> Installing:
>  yum-dellsysid           i386       2.2.17-3.1.el4   dell-omsa-
> indep    15 k
>
> Transaction Summary
> =
> =
> =
> =
> =
> =
> =
> ======================================================================
> Install      1 Package(s)
> Update       0 Package(s)
> Remove       0 Package(s)
> Total download size: 15 k
> Downloading Packages:
> Running Transaction Test
> Finished Transaction Test
> Transaction Test Succeeded
> Running Transaction
>   Installing: yum-dellsysid                #########################
> [1/1]
>
> Installed: yum-dellsysid.i386 0:2.2.17-3.1.el4
> Complete!
> No handlers could be found for logger "trace.libsmbios_c.smbios"
> Done!
>
> [root <at> control2 yum.repos.d]# yum install srvadmin-all
> Loading "dellsysid" plugin
> Setting up Install Process
> Setting up repositories
> Reading repository metadata in from local files
> Parsing package install arguments
> No Match for argument: srvadmin-all
> Nothing to do
>
>
> --
> Best Regards,
> Stephen
> _______________________________________________
> 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

_______________________________________________
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



--
Best Regards,
Stephen
_______________________________________________
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
Permalink | Reply | 2 comments |
headers
ingard mevåg | 1 Oct 2009 14:43
Picon

Debian, dellomsa and omreport errors

Hi

I recently started using the following nagios plugins for all our dell 
systems:
http://folk.uio.no/trondham/software/check_openmanage-3.4.9/check_openmanage
.. and it reports something like the following for all our servers:

serv1:~# /usr/lib/nagios/plugins/check_openmanage
Controller 0 (PERC 5/i Integrated): Firmware is out of date (5.0.2-0003)
Controller 0 (PERC 5/i Integrated): Driver is out of date (00.00.03.01)
Controller 1 (SAS 5/E): Firmware is out of date (00.10.49.00.06.12.02.00)
Controller 2 (SAS 5/E): Firmware is out of date (00.10.49.00.06.12.02.00)

Is it possible to upgrade the firmware a) without booting the box? or b) 
without taking the controller offline?

We're running mostly debian etch and lenny 64bit

Regards

--

-- 
Ingard Mevåg
System Administrator
+47 450 22 834
ingard <at> startsiden.no

ABC Startsiden AS
Sagveien 21A, 0459 Oslo 

_______________________________________________
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
Permalink | Reply | 1 comment |
headers
Raul Metsma | 1 Oct 2009 15:04
Picon

Re: PowerEdge 1950 with EMC AX4-5Dell

I had similar problems with AX4.
Is it failover configuration ?
I think i solved it using multipath and added hd* devices to ingore list

Raul

Łukasz Jagiełło wrote:
> Hi,
> 
> Everytime at boot got such errors:
> 
> #v+
> QLogic Fibre Channel HBA Driver
> ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 16 (level, low) -> IRQ 169
> qla2xxx 0000:0c:00.0: Found an ISP2432, irq 169, iobase 0xffffc2000001a000
> qla2xxx 0000:0c:00.0: Configuring PCI space...
> PCI: Setting latency timer of device 0000:0c:00.0 to 64
> qla2xxx 0000:0c:00.0: Configure NVRAM parameters...
> qla2xxx 0000:0c:00.0: Verifying loaded RISC code...
> usb 1-5: new high speed USB device using ehci_hcd and address 4
> qla2xxx 0000:0c:00.0: Allocated (64 KB) for EFT...
> qla2xxx 0000:0c:00.0: Allocated (1413 KB) for firmware dump...
> scsi1 : qla2xxx
> qla2xxx 0000:0c:00.0:
>  QLogic Fibre Channel HBA Driver: 8.02.00.06.05.03-k
>   QLogic QLE2462 - PCI-Express to 4Gb FC, Dual Channel
>   ISP2432: PCIe (2.5Gb/s x4)  <at>  0000:0c:00.0 hdma+, host#=1, fw=4.04.05
> [IP] [Multi-ID] [84XX]
> GSI 20 sharing vector 0xC9 and IRQ 20
> ACPI: PCI Interrupt 0000:0c:00.1[B] -> GSI 17 (level, low) -> IRQ 201
> qla2xxx 0000:0c:00.1: Found an ISP2432, irq 201, iobase 0xffffc2000001c000
> qla2xxx 0000:0c:00.1: Configuring PCI space...
> PCI: Setting latency timer of device 0000:0c:00.1 to 64
> qla2xxx 0000:0c:00.1: Configure NVRAM parameters...
> qla2xxx 0000:0c:00.1: Verifying loaded RISC code...
> usb 1-5: configuration #1 chosen from 1 choice
> hub 1-5:1.0: USB hub found
> hub 1-5:1.0: 4 ports detected
> qla2xxx 0000:0c:00.1: Allocated (64 KB) for EFT...
> qla2xxx 0000:0c:00.1: Allocated (1413 KB) for firmware dump...
> scsi2 : qla2xxx
> qla2xxx 0000:0c:00.1:
>  QLogic Fibre Channel HBA Driver: 8.02.00.06.05.03-k
>   QLogic QLE2462 - PCI-Express to 4Gb FC, Dual Channel
>   ISP2432: PCIe (2.5Gb/s x4)  <at>  0000:0c:00.1 hdma+, host#=2, fw=4.04.05
> [IP] [Multi-ID] [84XX]
> Initializing USB Mass Storage driver...
> qla2xxx 0000:0c:00.0: LIP reset occured (f7f7).
> qla2xxx 0000:0c:00.0: LIP occured (f7f7).
> qla2xxx 0000:0c:00.0: LOOP UP detected (4 Gbps).
> usb 3-2: new low speed USB device using uhci_hcd and address 2
> qla2xxx 0000:0c:00.1: LIP reset occured (f7f7).
> qla2xxx 0000:0c:00.1: LIP occured (f7f7).
> qla2xxx 0000:0c:00.1: LOOP UP detected (4 Gbps).
> usb 3-2: configuration #1 chosen from 1 choice
> input:   USB Keyboard as /class/input/input0
> input: USB HID v1.10 Keyboard [  USB Keyboard] on usb-0000:00:1d.1-2
> input:   USB Keyboard as /class/input/input1
> input: USB HID v1.10 Device [  USB Keyboard] on usb-0000:00:1d.1-2
>   Vendor: DGC       Model: RAID 5            Rev: 0223
>   Type:   Direct-Access                      ANSI SCSI revision: 04
> SCSI device sdb: 2097152000 512-byte hdwr sectors (1073742 MB)
> sdb: test WP failed, assume Write Enabled
> sdb: asking for cache data failed
> sdb: assuming drive cache: write through
> SCSI device sdb: 2097152000 512-byte hdwr sectors (1073742 MB)
> sdb: test WP failed, assume Write Enabled
> sdb: asking for cache data failed
> sdb: assuming drive cache: write through
>  sdb:<6>sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> 
> end_request: I/O error, dev sdb, sector 0
> Buffer I/O error on device sdb, logical block 0
> Dev sdb: unable to read RDB block 0
> sd 1:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Add. Sense: Logical unit not ready, manual intervention required
> #v-
> 
> Any idea how turn off that ? OS is CentoOS 5.3. Kernel from CentOSplus.
> 
> Regards

_______________________________________________
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
Permalink | Reply | 0 comments |
headers
ingard mevåg | 1 Oct 2009 15:11
Picon

Re: Debian, dellomsa and omreport errors

Harald Jensås wrote:
> On Thu, 01 Oct 2009 14:43:59 +0200
> ingard mevåg <ingard <at> startsiden.no> wrote:
>
>   
>> Hi
>>
>> I recently started using the following nagios plugins for all our
>> dell systems:
>> http://folk.uio.no/trondham/software/check_openmanage-3.4.9/check_openmanage
>> .. and it reports something like the following for all our servers:
>>
>> serv1:~# /usr/lib/nagios/plugins/check_openmanage
>> Controller 0 (PERC 5/i Integrated): Firmware is out of date
>> (5.0.2-0003) Controller 0 (PERC 5/i Integrated): Driver is out of
>> date (00.00.03.01) Controller 1 (SAS 5/E): Firmware is out of date
>> (00.10.49.00.06.12.02.00) Controller 2 (SAS 5/E): Firmware is out of
>> date (00.10.49.00.06.12.02.00)
>>
>> Is it possible to upgrade the firmware a) without booting the box? or
>> b) without taking the controller offline?
>>
>> We're running mostly debian etch and lenny 64bit
>>
>>     
>
> You will have to reboot the box for the firmware update to take effect.
>
> If the OS is not running of drives connected too the PERC/SAS it might
> be possible to install the latest driver by doing modprobe -r on the
> currently loaded module and then use modprobe to load the new/updated
> module. You would still have to unmount all volumes that resides on the
> PARC/SAS drives... 
>
>
>   
Ok, so at least i can pxeboot to rescue/busybox shell and do it from 
there (without going to the server centre). But are there tools to do 
the actual upgrade for debian? I've seen rpm packages, but nothing for 
debian.

--

-- 
Ingard Mevåg
System Administrator
+47 450 22 834
ingard <at> startsiden.no

ABC Startsiden AS
Sagveien 21A, 0459 Oslo 

_______________________________________________
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
Permalink | Reply | 1 comment |
headers
Alessandro FAGLIA | 1 Oct 2009 15:18
Picon

Re: Debian, dellomsa and omreport errors

-------- Original Message  --------
Subject: Re: Debian, dellomsa and omreport errors
From: ingard mevåg <ingard <at> startsiden.no>
To: Harald Jensås <harald.jensas <at> dell.com>
Cc: linux-poweredge <at> lists.us.dell.com
Date: Thu Oct 01 2009 15:11:15 GMT+0200 (ora Legale Europa Occidentale)

> Harald Jensås wrote:
  Ok, so at least i can pxeboot to rescue/busybox shell and do it from
> there (without going to the server centre). But are there tools to do 
> the actual upgrade for debian? I've seen rpm packages, but nothing for 
> debian.
> 

Have a look at my previous post "System Updates and local repository".

Currently there is no native tool for Debian ASAIK, you should do it by 
means of a bootable CD/usb key.

HTH.

--

-- 
Alessandro

_______________________________________________
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
Permalink | Reply | 0 comments |
headers
Trond Hasle Amundsen | 1 Oct 2009 17:03
Picon
Picon
Favicon

Re: Debian, dellomsa and omreport errors

ingard mevåg <ingard <at> startsiden.no> writes:

> I recently started using the following nagios plugins for all our dell 
> systems:
> http://folk.uio.no/trondham/software/check_openmanage-3.4.9/check_openmanage
> .. and it reports something like the following for all our servers:
>
> serv1:~# /usr/lib/nagios/plugins/check_openmanage
> Controller 0 (PERC 5/i Integrated): Firmware is out of date (5.0.2-0003)
> Controller 0 (PERC 5/i Integrated): Driver is out of date (00.00.03.01)
> Controller 1 (SAS 5/E): Firmware is out of date (00.10.49.00.06.12.02.00)
> Controller 2 (SAS 5/E): Firmware is out of date (00.10.49.00.06.12.02.00)
>
> Is it possible to upgrade the firmware a) without booting the box? or b) 
> without taking the controller offline?
>
> We're running mostly debian etch and lenny 64bit

Hi Ingard,

I'm the author of that plugin. As far as I know, OpenManage sets the
controller in a degraded state simply because it knows that a newer
firmware and/or driver exists. It does not mean that it is dangerous not
to upgrade the firmware and driver. It can be an annoyance, and
check_openmanage has a blacklisting feature that can be used to suppress
these alarms:

  check_openmanage -b ctrl_fw=0,1,2/ctrl_driver=0,1,2

In the above example, messages about out-of-date controller firmware and
driver on controllers 0,1 and 2 are suppressed by check_openmanage.

As others have explained, upgrading the controller firmware requires a
reboot. Unfortunately, Debian is not supported by Dell and therefore no
firmware update scripts are available for Debian. You could try the
scripts for Red Hat and SuSE, they may work on Debian as well.

As for how critical a certain firmware or driver upgrade is, you'll have
to read the changelog for the firmware/driver available from the Dell
support site (support.dell.com).

Our policy is to upgrade firmware whenever we have scheduled downtime,
and ignore the driver completely (using blacklisting), thinking that the
Red Hat official driver is good enough.

Cheers,
--

-- 
Trond H. Amundsen <t.h.amundsen <at> usit.uio.no>
Center for Information Technology Services, University of Oslo

_______________________________________________
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
Permalink | Reply | 0 comments |
headers
Jeffrey_L_Mendoza | 1 Oct 2009 17:52
Picon
Favicon

RE: OMSA won't install w/ yum - centos 4.8

Stephen,

Yes the 750 will not be supported in the latest OMSA. I believe 5.5
works, in addition to 5.4.

Can you post the output of the problem you are having installing 6.1 on
your R410?

Thanks.
Jeff 

________________________________

	From: linux-poweredge-bounces <at> lists.us.dell.com
[mailto:linux-poweredge-bounces <at> lists.us.dell.com] On Behalf Of Stephen
Vaughan
	Sent: Wednesday, September 30, 2009 7:18 PM
	To: linux-poweredge-Lists
	Subject: Re: OMSA won't install w/ yum - centos 4.8
	
	
	It was a PE750, I ended up having to install 5.4, that was the
only one that worked. The firmware rpms weren't installing on the newer
version of OMSA, and the srvadmin packages weren't even recognised. I
have an R410 which is only supported by 6.1, except 6.1 doesn't want to
install on CentOS 4.8.. go figure
	
	
	On Wed, Sep 30, 2009 at 9:51 PM, Matthew Willis
<lilmatt <at> flock.com> wrote:
	

		What PowerEdge is this on?  I had a similar experience
(yum install
		srvadmin-all failing with "Nothing to do") when
attempting to install
		6.1 on some older gear (1650, 1750).
		
		I eventually looked through the hardware repositories (
http://linux.dell.com/repo/hardware/OMSA_6.0.2/
		 vs. http://linux.dell.com/repo/hardware/OMSA_6.1/ ) and
noticed a
		lack of a "1650" or "1750" folder in 6.1.  When I
switched to
		installing 6.0.2 (which has those folders) things began
working for me.
		
		-lilmatt
		

		On Sep 29, 2009, at 11:53 PM, Stephen Vaughan wrote:
		
		> Hi,
		>
		> I've tried everything and I just cannot get it to
work. I've
		> followed the instructions on this page:
http://linux.dell.com/repo/hardware/OMSA_6.1/
		>
		> Each time I try yum install srvadmin-all it can't
locate the
		> package. I've also tried yum search srvadmin and
nothing shows up.
		> Note this box was previously running RHEL4 w/ OMSA
5.4, the box was
		> upgraded to centos 4.8 and then we removed the
srvadmin rpm's.
		> Plugins are enabled in yum.conf.
		>
		> This is the log:
		>
		> [root <at> box yum.repos.d]# wget -q -O -
http://linux.dell.com/repo/hardware/OMSA_6.1/bootstrap.cgi
		>  | bash
		> Downloading GPG key:
http://linux.dell.com/repo/hardware/OMSA_6.1/RPM-GPG-KEY-dell
		>     Key already exists in RPM, skipping
		> Downloading GPG key:
http://linux.dell.com/repo/hardware/OMSA_6.1/RPM-GPG-KEY-libsmbios
		>     Key already exists in RPM, skipping
		> Downloading repository RPM
		> Installing repository rpm:
http://linux.dell.com/repo/hardware/OMSA_6.1/platform_independent/rh40/p
rereq/dell-omsa-repository-2-5.noarch.rpm
		> Installing yum plugins for system id
		> Setting up Install Process
		> Setting up repositories
		> Reading repository metadata in from local files
		> Parsing package install arguments
		> Resolving Dependencies
		> --> Populating transaction set with selected packages.
Please wait.
		> ---> Package yum-dellsysid.i386 0:2.2.17-3.1.el4 set
to be updated
		> --> Running transaction check
		>
		> Dependencies Resolved
		>
		> =
		> =
		> =
		> =
		> =
		> =
		> =
		>
======================================================================
		>  Package                 Arch       Version
		> Repository        Size
		> =
		> =
		> =
		> =
		> =
		> =
		> =
		>
======================================================================
		> Installing:
		>  yum-dellsysid           i386       2.2.17-3.1.el4
dell-omsa-
		> indep    15 k
		>
		> Transaction Summary
		> =
		> =
		> =
		> =
		> =
		> =
		> =
		>
======================================================================
		> Install      1 Package(s)
		> Update       0 Package(s)
		> Remove       0 Package(s)
		> Total download size: 15 k
		> Downloading Packages:
		> Running Transaction Test
		> Finished Transaction Test
		> Transaction Test Succeeded
		> Running Transaction
		>   Installing: yum-dellsysid
#########################
		> [1/1]
		>
		> Installed: yum-dellsysid.i386 0:2.2.17-3.1.el4
		> Complete!
		> No handlers could be found for logger
"trace.libsmbios_c.smbios"
		> Done!
		>
		> [root <at> control2 yum.repos.d]# yum install srvadmin-all
		> Loading "dellsysid" plugin
		> Setting up Install Process
		> Setting up repositories
		> Reading repository metadata in from local files
		> Parsing package install arguments
		> No Match for argument: srvadmin-all
		> Nothing to do
		>
		>
		> --
		> Best Regards,
		> Stephen
		
		> _______________________________________________
		> 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
		
		_______________________________________________
		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
		

	-- 
	Best Regards,
	Stephen
	

_______________________________________________
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
Permalink | Reply | 1 comment |
headers
Matthew Willis | 1 Oct 2009 21:33
Favicon

DRAC3 ERA/O login failures using OSX Snow Leopard (10.6.1)

Just as a heads up to anyone using Macs to control DRAC3s:

After upgrading to Mac OS X Snow Leopard (10.6.1), we can no longer  
login to our DRAC3 ERA/O cards.  We still can using Leopard (10.5.8).

After entering your credentials, you never make it past the login  
screen.  Java Console shows infinite repeated connection attempts to  
the DRAC.

It appears Snow Leopard no longer includes JDKs for Java 5 or Java 4  
-- just Java 6.  However, setting Leopard to use JDK 6 for applets  
still works.

Just FYI in case you're thinking of upgrading.

-lilmatt

_______________________________________________
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
Permalink | Reply | 0 comments |
headers
Ryan Dooley | 2 Oct 2009 20:51
Picon

Re: iDRAC 6 Express - vlan issues?

Turns out that Red Hat has an bug open on this for the e1000 driver
which was opened up earlier this year:

  https://bugzilla.redhat.com/show_bug.cgi?id=496248

On Tue, Sep 29, 2009 at 5:26 PM, Ryan Dooley <ryan.dooley <at> gmail.com> wrote:
> Hi,
> I've a bunch of shiny new R710's complete with the IDRAC 6 Express and
> I'm having what look like vlan issues.  Serial Over Lan consoles seem
> to work fine until the network driver for the bnx2 configures the
> interface and then it just up and stops responding.
>
> The host is on say vlan2 and the DRAC has been set to share eth0 on vlan102.
>
> I'm using the broadcom netxtreme driver on two different hosts:
> * 1.9.20b with a custom kernel 2.6.25.10 on one host
> * 1.9.3 with kernel 2.6.18-164.el5 on another
>
> Both hosts are essentially Centos 5.
>
> If the vlan is changed from 102 to another, say 106, things work fine.
>  It is as if there is a bit mask issue in handling vlan tagging.
>
> The exact same configuration on the 2950 III platform doesn't have
> this issue (but it doesn't have the DRAC either, just a bare BMC).
>
> Any suggestions would be great.
>
> Cheers,
> Ryan
>

_______________________________________________
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
Permalink | Reply | 3 comments |

Gmane