[xcat-user] bmc setup with fixed IP addresses

[Nicolas Roosen]

Hello,

I'm in the process of installing a cluster of Supermicro x86_64 nodes
with xCAT (CentOS 7.3).

I created a single node (manually with mkdef and nodeset), can install
it successfully.

But one thing doesn't work for me: the setup of the BMC ip address.

In our setup the BMC is shared over the first Ethernet interface. So
I've declared a DHCP dynamic range, all BMC's get an IP address.

Then I need to change this dynamically obtained BMC IP address in a
static one (which is in a different subnet).

So I though that simply adding into the node definition the BMC ip
address and setting a [chain="runcmd=bmcsetup"] was enough.
But it seems that this is not the case.

How can I automatically change the BMC ip address while provisioning a node?

Thanks.
Nicolas

P.S: the mkdef command:

mkdef -t node -o n039-clu "groups=all,ipmi" arch="x86_64" mgt="ipmi"
bmc="10.33.192.53" mac="0c:c4:7a:70:f3:6e" ip="10.33.240.53"
installnic=mac primarynic=mac provmethod="centos7.3-node-giga"
chain="runcmd=bmcsetup"

P.S. 2: the node definition.

lsdef n039-clu
Object name: n039-clu
arch=x86_64
bmc=10.33.192.53
bmcpassword=admin
bmcport=0
bmcusername=admin
chain=runcmd=bmcsetup
groups=all,ipmi
installnic=mac
ip=10.33.240.53
mac=0c:c4:7a:70:f3:6e
mgt=ipmi
netboot=xnba
nfsserver=10.33.240.1
os=centos7.3
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
primarynic=mac
profile=node-giga
provmethod=centos7.3-x86_64-node-giga
tftpdir=/tftpboot
tftpserver=10.33.240.1
xcatmaster=10.33.240.1

[Jarrod Johnson]

If you nodeset <node> shell
Then boot it, ssh in and run bmcsetup by hand, the output may be informative as to why the BMC didn't get set up correctly.

-----Original Message-----
From: Nicolas Roosen [mailto:***@hpe.com]
Sent: Wednesday, June 21, 2017 11:50 AM
To: xcat-***@lists.sourceforge.net
Subject: [xcat-user] bmc setup with fixed IP addresses

Hello,

I'm in the process of installing a cluster of Supermicro x86_64 nodes with xCAT (CentOS 7.3).

I created a single node (manually with mkdef and nodeset), can install it successfully.

But one thing doesn't work for me: the setup of the BMC ip address.

In our setup the BMC is shared over the first Ethernet interface. So I've declared a DHCP dynamic range, all BMC's get an IP address.

Then I need to change this dynamically obtained BMC IP address in a static one (which is in a different subnet).

So I though that simply adding into the node definition the BMC ip address and setting a [chain="runcmd=bmcsetup"] was enough.
But it seems that this is not the case.

How can I automatically change the BMC ip address while provisioning a node?

Thanks.
Nicolas

P.S: the mkdef command:

mkdef -t node -o n039-clu "groups=all,ipmi" arch="x86_64" mgt="ipmi"
bmc="10.33.192.53" mac="0c:c4:7a:70:f3:6e" ip="10.33.240.53"
installnic=mac primarynic=mac provmethod="centos7.3-node-giga"
chain="runcmd=bmcsetup"

P.S. 2: the node definition.

lsdef n039-clu
Object name: n039-clu
arch=x86_64
bmc=10.33.192.53
bmcpassword=admin
bmcport=0
bmcusername=admin
chain=runcmd=bmcsetup
groups=all,ipmi
installnic=mac
ip=10.33.240.53
mac=0c:c4:7a:70:f3:6e
mgt=ipmi
netboot=xnba
nfsserver=10.33.240.1
os=centos7.3
postbootscripts=otherpkgs
postscripts=syslog,remoteshell,syncfiles
primarynic=mac
profile=node-giga
provmethod=centos7.3-x86_64-node-giga
tftpdir=/tftpboot
tftpserver=10.33.240.1
xcatmaster=10.33.240.1

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
xCAT-user mailing list
xCAT-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

[Nicolas Roosen]

Hi,

Post by Jarrod Johnson
If you nodeset <node> shell
Then boot it, ssh in and run bmcsetup by hand, the output may be informative as to why the BMC didn't get set up correctly.

Practical. So the bmcsetup while run into the shell did successfully set
the correct IP address.

My guess is that the bmcsetup command is not run during the provisioning?
How can I check that?

Thanks.
Nicolas

Post by Jarrod Johnson
-----Original Message-----
Sent: Wednesday, June 21, 2017 11:50 AM
Subject: [xcat-user] bmc setup with fixed IP addresses
Hello,
I'm in the process of installing a cluster of Supermicro x86_64 nodes with xCAT (CentOS 7.3).
I created a single node (manually with mkdef and nodeset), can install it successfully.
But one thing doesn't work for me: the setup of the BMC ip address.
In our setup the BMC is shared over the first Ethernet interface. So I've declared a DHCP dynamic range, all BMC's get an IP address.
Then I need to change this dynamically obtained BMC IP address in a static one (which is in a different subnet).
So I though that simply adding into the node definition the BMC ip address and setting a [chain="runcmd=bmcsetup"] was enough.
But it seems that this is not the case.
How can I automatically change the BMC ip address while provisioning a node?
Thanks.
Nicolas

[Nicolas Roosen]

Post by Nicolas Roosen
Hi,

Post by Jarrod Johnson
If you nodeset <node> shell
Then boot it, ssh in and run bmcsetup by hand, the output may be
informative as to why the BMC didn't get set up correctly.

Practical. So the bmcsetup while run into the shell did successfully set
the correct IP address.
My guess is that the bmcsetup command is not run during the provisioning?
How can I check that?

We found out that bmcsetup didn't run because our node wasn't affected
to a discovered UUID (since we are adding the nodes manually I guess):

# nodediscoverls
UUID NODE METHOD
MTM SERIAL
00000000-0000-0000-0000-0CC47A70F36E undef undef
Supermicro:NONEA00AD6FA

As soon as we affected the node to the correct UUID, bmcsetup worked:

# nodediscoverdef -u 00000000-0000-0000-0000-0CC47A71F39E -n n040-clu
Defined [00000000-0000-0000-0000-0CC47A71F39E] to node n040-clu.

[Er Tao Zhao]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot