Fro most of the command, xCAT expect you run command from management node, as xcatd will decide if the request will be forwarded to service node.
So if your MN could handle dhcp lease entry successfully, there is okay.
Base on that I am not sure your exact problem? Do you hit provision error, or discovering error, or something else?
BTW: any possibility for you to upgrade your xCAT to latest release.
Bin Xu
HPC Software Development
Software Defined Infrastructure, IBM Systems
Software Defined Infrastructure, IBM Systems
Phone: 86-010-82454067
E-mail: bx...@cn.ibm.com
----- Original message -----
From: RUSSELL AULD <russa...@comcast.net>
To: xCAT-Users <xcat-user@lists.sourceforge.net>
Cc:
Subject: [xcat-user] Nodeset from SN not running DHCP
Date: Wed, Feb 20, 2019 8:16 PM
I have a hierarchical cluster setup running xCAT v2.12.2.
I do not wish to run the DHCP server on the service node (SN) - the master node (MN) will serve the DHCP leases.
When I run 'nodeset node01 osimage' on the SN I get the following message:
[root@c2-service]# nodeset node01 osimage
node01: install rhels7.5-x86_64-compute
Error: dhcp server is not running. please start the dhcp server.
If I run the nodeset operation on MN, it works, since it is running the dhcpd server and omshell can update the DHCP leases file.
Is this the expected behavior? Can the SN remotely manage the DHCP leases on the MN? It looks like 'omshell' is able to talk to remote servers, but that doesn't look like it's happening in my version of xCAT.
It looks like the other important things happen like generating the kickstart file and the tftpboot file.
I have the SN/CN network defined like this:
# lsdef -t network -o 10_20_116_0-255_255_252_0
Object name: 10_20_116_0-255_255_252_0
dhcpserver=10.20.11.129
tftpserver=10.20.119.0
gateway=10.20.116.1
mask=255.255.252.0
mgtifname=!remote!
net=10.20.116.0
usercomment=cluster2_prod_net
Notice that the dhcpserver is in a separate VLAN. Functionally this works because our layer three router forwards the DHCP broadcast traffic from the 10.20.116.0/22 VLAN to the dhcpserver listed in the output above.
The remote interface is listed as a dhcp interface:
# lsdef -t site -o clustersite -i dhcpinterfaces
Object name: clustersite
dhcpinterfaces=10.20.11.129|br0,!remote!,virbr1
The service node is not configured to serve DHCP:
tabch node=c2-service servicenode.nameserver=0 servicenode.dhcpserver=0 servicenode.tftpserver=1 servicenode.nfsserver=0
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
