You saw the discovery message was because of the node configuration was not
finished yet. After running 'nodeset' and start the node deployment, the
discovery message won't show again.
Regarding the discovery, you can use 'sequential discovery' to discover
virtual node. Refer to:
https://sourcefor
What I can think of is the user/certificates/permission things are not
correct on your service node. Try to run 'rpower' or 'lsdef' on service
node directly and check the syslog to see the xCAT log like this 'xCAT:
Allowing lsdef for from xxx' to get the current user.
Thanks
Best Regards
xCAT assumes that using 'mgt=ipmi' for all bmc related management, that
means 'ipmi.pm' plugin will be used for bmc related management.
What's the problem in your case if setting 'mgt=ipmi'?
Thanks
Best Regards
--
Wang Xiaopeng
From my understanding the networks.dhcpserver is used with
networks.dynamicrange. Since the dynamicrange in a service node pool cannot
be configured in multiple dhcp servers, use networks.dhcpserver to specify
the dhcp server which is enabling the dynamicrange.
Thanks
Best Regards
To enable DHCP service on SN can be done by configuring the servicenode
table or setupdhcp attribute of SN node.
To enable DNS service which can be running without MN, you need to enable
DSN server on SN in slave mode. It will available in 2.8.4 realease. Refer
to Option #3.2 in
https://sourceforg
