LOCKEDUSERS is set on BMC models known to have a limitation where user slots can't have name changed except for '4'. I can't recall exactly who the common firmware provider is that has this limitation, but it is one particular company that does this with at least one particular stack, but that stack is common across a few companies (e.g. dx320 was an iDataplex system that made use of it, no IMM systems have this limitation.
IPMIMFG=`ipmitool mc info|grep "^Manufacturer ID"|awk '{print $4}'`
PROD=`ipmitool mc info|grep "^Product ID"|awk '{print $4}'`
Adding that to the 'LOCKEDUSERS' detection mechanism should help it work.
I've long been frustrated by this behavior which is more restrictive than
IPMI spec would suggest. user slots 2 and up *should* be fair game, but oh
well.
From: Russell Jones <russell-l...@jonesmail.me>
To: xcat-user@lists.sourceforge.net
Date: 11/05/2013 05:35 PM
Subject: Re: [xcat-user] bmcsetup and Supermicro X9DRT
I've poked at this box some more, and it seems like this is the main reason
for the issues. It doesn't want to let the ADMIN user be overwritten.
Thoughts?
[xCAT Genesis running on node /]# bmcsetup
/bin/bmcsetup: line 45: 2237 Terminated allowcred.awk
Auto detecting LAN channel...Detected LAN channel 1
Setting LAN IP Address to 172.31.99.151
Setting LAN Subnet Mask to 255.255.255.0
Setting LAN Default Gateway IP to 172.31.99.254
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
Set User Name command failed (user 2, name foo1): Command not supported in
present state
^C[xCAT Genesis running on perth1 /]# ipmitool user set 2
User Commands: summary [<channel number>]
list [<channel number>]
set name <user id> <username>
set password <user id> [<password>]
disable <user id>
enable <user id>
priv <user id> <privilege level> [<channel
number>]
test <user id> <16|20> [<password]>
[xCAT Genesis running on perth1 /]# ipmitool user set name 2 foo1
Set User Name command failed (user 2, name foo1): Command not supported in
present state
On 11/4/2013 9:30 AM, Russell Jones wrote:
Thanks Jarrod,
That might be the issue, looks like the BMC user is getting added in
as user slot 3:
[xCAT Genesis running on node /]# ipmitool user list
ID Name Callin Link Auth IPMI Msg Channel Priv Limit
2 ADMIN true false false Unknown (0x00)
3 IPMIUSER true false true ADMINISTRATOR
Curious, why the specific lock down to slot 2 or 4 in the if
statement?
On 11/2/2013 6:41 AM, Jarrod B Johnson wrote:
the bmcsetup contains:
ipmitool -d $idev user enable $USERSLOT
The one user xCAT is supposed to be using should already be
having that done. USERSLOT:
f [ ! -z "$LOCKEDUSERS" ]; then
USERSLOT=`ipmitool -d $idev user list $LANCHAN |grep -v
^ID|awk '{print $1 " " $2}'|grep " $BMCUS"|awk '{print $1}'`
if [ -z "$USERSLOT" ]; then
USERSLOT=4
fi
else
USERSLOT=2
fi
It looks at the user list, sees if the requested user is one of
the first 4, if it is, it uses that. If it isn't, it takes
over slot 4.
There were some IPMI implementations that mandated we use slot
2. If supermicro has another limitation, we can probably adapt
bmcsetup easily enough.
Inactive hide details for Russell Jones ---11/01/2013
04:41:11 PM---Hi all, We have a Supermicro X9DRT-based node
that we are aRussell Jones ---11/01/2013 04:41:11 PM---Hi all,
We have a Supermicro X9DRT-based node that we are attempting to
use
From: Russell Jones <russell-l...@jonesmail.me>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Date: 11/01/2013 04:41 PM
Subject: [xcat-user] bmcsetup and Supermicro X9DRT
Hi all,
We have a Supermicro X9DRT-based node that we are attempting to
use
bmcsetup on. We are running into an issue where bmcsetup on
this
Supermicro seems to be adding users with a default to
"disabled" state.
I have to specifically run "ipmitool user enable <id>" on the
node to
enable the user.
Other nodes we run bmcsetup on, such as Dell's, this is not the
case and
the user is added and enabled by default.
Would it be possible to perhaps change the bmcsetup code to
purposefully
enable the user after it has been added? Would this be the
right path to
take for this?
Thanks for your input!
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development
platform that
developers love is also attractive to malware creators.
Download this white
paper to learn more about secure code signing practices that
can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development
platform that
developers love is also attractive to malware creators.
Download this white
paper to learn more about secure code signing practices that
can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development
platform that
developers love is also attractive to malware creators. Download this
white
paper to learn more about secure code signing practices that can help
keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models.
Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and
register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
