ion!
No... the BEST solution would be for Dell to release OMSA as proper Open
Source software, and leave packaging and repository management to
others. How about OMSA in EPEL? Wouldn't that be great? :)
Cheers,
--
Trond Hasle Amundsen
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Hat
package it could take some time before we have a fix. Red Hat usually
only release (non-important) bug fixes as part of a major upgrade,
meaning we may have to wait until RHEL 7.6.
But with the EPEL packages working for 11G and the official Red Hat
packages working for 12G and
g behind the new libsmbiosc++
package from Dell.
I've confirmed that it works with the (soon-to-be-retired) EPEL
packages, but it doesn't work with the new Red Hat libsmbios + Dell
libsmbiosc++ combo. Hopefully it's an easy fix for Dell :)
Regards,
--
Trond Hasle Amundsen
___
Support Matrix for a list of
supported systems.
Installed smbios packages:
# rpm -qa|grep smbios
libsmbios-2.3.3-6.el7.x86_64
libsmbiosc++-2.3.1-3013.13047.el7.x86_64
smbios-utils-bin-2.3.3-6.el7.x86_64
Regards,
--
Trond Hasle Amundsen
___
Hi,
OMSA has issues with the latest firmware for H700 controllers. There
seems to be a bug related to parsing the version numbers, which in turn
makes OMSA complain about the firmware being too old:
# omreport storage controller
Controller PERC H700 Integrated (Embedded)
Controllers
Karsten Suehring writes:
>> Ah.. stupid typo. Try again, please?
>
> Yes, it works. Great work. Thank you very much :-)
Good :) Thanks for reporting this. After running the beta in production
here for a few days, I'll make a new release if I don't discover any
more bugs or regressions.
Regards,
Karsten Suehring writes:
>> Please give it a try and let me know if this resolves the issue for
>> you.
>
> I tried 3.6.1-beta6. This still gives the same error message :-(
Ah.. stupid typo. Try again, please?
Regards,
--
Trond H. Amundsen
Center for Information Technology Services, Universit
Karsten Suehring writes:
>> snmpwalk -v2c -c 1.3.6.1.4.1.674.10892.1.600.30.1
>
> On the upgraded system I get the following:
>
> Cannot find module (LM-SENSORS-MIB): At line 0 in (none)
> SNMPv2-SMI::enterprises.674.10892.1.600.30.1.1.1.1 = INTEGER: 1
> SNMPv2-SMI::enterprises.674.10892.1.600.
Karsten Suehring writes:
> The systems are around one year old and only have one power supply. We
> recently purchased some more R410 with redundant power supply that
> have power monitoring capabilities. I'm not sure if this a restriction
> of the power supply itself or the systems management co
Karsten Suehring writes:
> thanks for the quick reply. The system does not have power monitoring
> capabilities.
Strange. We don't have any R410s, but I was under the impression that
most 10th gen servers has power monitoring capability, including the
R410.
>> Interesting problem.. what does 'o
Karsten Suehring writes:
> Hi,
>
> I recently installed on two of my Dell Poweredge R410 servers the BMC
> firmware version 1.54.
> Now the check_openmanage nagios plugin reports:
>
>> Amperage probe 0 [System Board System Level] is [N/A]
>
> Does anybody have similar problems? Is it a problem w
"dellpowere...@semantico.com" writes:
> Hi List,
>
> We have this omsa error after rebooting after a disk became unmountable:-
>
> Physical Disk 1:0:1 [Dell ST3750640NS, 750GB] on ctrl 1 needs attention:
> Foreign
>
> omreport storage pdisk controller=1 pdisk=1:0:1
> Hard Disk 1:1 on Controller P
Gianluca Cecchi writes:
> Thanks Trond and Bryan for the clarifications
>
> Probably I misunderstood the line for "-o" option at check_openmanage page:
>
> "
> Most would go for the default (value of 0), i.e. a single line.
> "
Yes, you are correct. I remembered it wrong. The option takes 0, 1,
Gianluca Cecchi writes:
> hello,
> a blade M910 with RH EL 5.5 x86_64 and 6.2 agents.
> Installed these:
> libsmbios-2.2.19-10.1.el5.i386.rpm
> libsmbios-2.2.19-10.1.el5.x86_64.rpm
> RPM-GPG-KEY-dell
> RPM-GPG-KEY-libsmbios
> smbios-utils-bin-2.2.19-10.1.el5.x86_64.rpm
> srvadmin-cm-6.2.0-677.i38
Nick Silkey writes:
> We have quite a few production RHEL3u5 WS hosts running OMSA
> 5.1.0-354. We find pointing Trond Amundsen's check_poweredge Nagios
> plugin at them eventually leads to semaphore resource exhaustion, but
> only when the machine is under high load (low load == semaphores come
Jamie Shaffer writes:
> I use logwatch to check on the status of my linux boxes, but I don?t have a
> script to check for the output of OpenManage. OpenManage appears to write only
> to /var/log/messages. Does anyone already have a filter script for use with
> logwatch? (Sorry if this is a repeat
Tino Schwarze writes:
> On Tue, Mar 02, 2010 at 03:37:44PM +0100, Trond Hasle Amundsen wrote:
>
>> > I found this:
>> > http://support.dell.com/support/downloads/format.aspx?c=us&cs=555&l=en&s
>> > =biz&deviceid=2331&libid=36&relea
"Donald Harper" writes:
> I found this:
> http://support.dell.com/support/downloads/format.aspx?c=us&cs=555&l=en&s
> =biz&deviceid=2331&libid=36&releaseid=R251021&vercnt=3&formatcnt=0&Syste
> mID=PWE_M610&servicetag=&os=RHEL5&osl=en&catid=-1&dateid=-1&typeid=-1&fo
> rmatid=-1&impid=-1&checkFormat
Hi,
As far as I can see, the newest version of MIBs for Poweredge available
for download from Dell is 6.0.1. From recent experience, there are some
OIDs and values reported by OM 6.1 and 6.2 that are not defined in this
version of the MIBs. Does a newer version exist somewhere?
Cheers,
--
Trond
Rahul Nabar writes:
> I was having trouble installing the Dell Toolkit. This error:
>
> rpm -ihv --force dell-toolkit.rpm
> Preparing...### [100%]
> You cannot install Dell deployment toolkit and Open manage on the same Server
> error: %pre(
Robin Bowes writes:
> I use OpenNMS for monitoring - it automatically detects Dell OMSA data
> and monitors/logs/graphs it. I'm using OMSA 6.2.0 on R410 machines.
>
> I am getting temperature and system fan speed data but am not getting
> any system power consumption information.
>
> Indeed, if I
"Steve Jenkins" writes:
> I used to use OMSA a couple versions ago, but didn't like how much
> processing and memory it used.
I find it hard to believe that this poses a problem for most people
these days. The following is taken from a 1950 with RHEL5 and OMSA
5.5.0, that has been up for 95 days
"Brian A. Seklecki" writes:
>> It is in a remote location, so command line tools would be great. I
>
> MegaCli from LSI is all that you need. OMSA if your nights are long.
I'm not running OMSA on Debian/Ubuntu myself (we're a Red Hat shop), but
the procedure looks quite straightforward. Del
23 matches
Mail list logo
