Bug 698636

Summary:	delloem commands: how to recognize supported hw
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Sklenar <psklenar>
Component:	ipmitool	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	ctatman, jfeeney, martinez, narayanan_d, ovasik, shiyer, srinivas_g_gowda, syeghiay, wwlinuxengineering
Target Milestone:	rc
Target Release:	6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-04 08:03:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	695900

Description Petr Sklenar 2011-04-21 12:54:13 UTC

Description of problem:
delloem command relies on specific hw and there is no way how to find if I am using such a hw. Then its possible to use 50% commands successfully from delloem and the rest of commands return error like 'Unknown (0x80)'

I would like to see something like:
'ipmitool delloem checkhw' which returns true or false

Version-Release number of selected component (if applicable):
ipmitool-1.8.11-7.el6.x86_64
OpenIPMI-2.0.16-12.el6.x86_64

How reproducible:
find a hw which don't fully support delloem, like dell-per805

Steps to Reproduce:
[root@dell-per805-01 ~]# /etc/init.d/ipmi restart
Stopping all ipmi drivers: may be in use[FAILED]
Starting ipmi drivers: [  OK  ]
[root@dell-per805-01 ~]# /etc/init.d/ipmievd restart
Shutting down ipmievd:[  OK  ]
Starting ipmievd:[  OK  ]

# try delloem commands

some of them works:
# ipmitool delloem powermonitor
Power Tracking Statistics
Statistic      : Cumulative Energy Consumption
Start Time     : Thu Apr 21 08:17:11 2011
Finish Time    : Thu Apr 21 08:35:28 2011
Reading        : 184.1 kWh

Statistic      : System Peak Power
Start Time     : Thu Apr 21 08:16:59 2011
Peak Time      : Thu Apr 21 08:21:29 2011
Peak Reading   : 121 W

Statistic      : System Peak Amperage
Start Time     : Thu Apr 21 08:16:59 2011
Peak Time      : Thu Apr 21 08:16:59 2011
Peak Reading   : 0.6 A

and some of them not:
[root@dell-per805-01 ~]# ipmitool delloem powermonitor getpowerbudget
  Error getting power cap: Unknown (0x80)
[root@dell-per805-01 ~]# ipmitool delloem powermonitor disablepowercap
 Error getting powercap statusr: Invalid command
 Can not set powercap on this system

Actual results:
some of the delloem does not work

Expected results:
how to be sure that hw is fully supported
add support for another hw, like dell-per805
I would like to see something like:
'ipmitool delloem checkhw' which returns true or false

Additional info:

Comment 1 Marizol Martinez 2011-04-21 18:40:47 UTC

Adding Dell.

Comment 2 srinivas gowda 2011-04-27 06:16:24 UTC

I am afraid we don`t have a command that can give this information.

The commands such as "ipmitool delloem powermonitor getpowerbudget" are relatively alien for 10G Rack servers. The BMC on 11G server will support all the commands.

Comment 3 RHEL Program Management 2011-07-06 01:12:41 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Chris Tatman 2011-11-03 19:32:15 UTC

Petr,

Based on the answer Ddell gave us in comment# 2, can we close this bug?

--Chris

Comment 5 Petr Sklenar 2011-11-04 08:03:25 UTC

(In reply to comment #4)
> Petr,
> 
> Based on the answer Ddell gave us in comment# 2, can we close this bug?
> 
> --Chris

yes, we can
closing