xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-13 09:50:19 +00:00
Code Issues Releases Wiki Activity

Add some text describing the noboot option to disable the genesis kernel

Browse Source 
from being sent over a interface
This commit is contained in:
Victor Hu
2016-10-31 22:23:28 -04:00
parent 9dc963578c
commit 5abb24af16
1 changed files with 20 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/source/guides/admin-guides/manage_clusters/ppc64le/configure/networks.rst
View File

@ -12,15 +12,19 @@ Set attributes in the ``networks`` table
#. To define additional networks, use one of the following options:
* Use ``mkdef`` to create/update an entry into ``networks`` table. (**Recommended**)
* (**Recommended**) Use ``mkdef`` to create/update an entry into ``networks`` table.
To create a network entry for 192.168.X.X/16 with a gateway of 192.168.1.254: ::
mkdef -t network -o net1 net=192.168.0.0 mask=255.255.0.0 gateway=192.168.1.254
* Use the ``tabedit`` command to modify the networks table directly in an editor: ``tabedit networks``
* Use the ``tabedit`` command to modify the networks table directly in an editor: ::
* Use the ``makenetworks`` command to automatically generate a entry in the ``networks`` table
tabedit networks
* Use the ``makenetworks`` command to automatically generate a entry in the ``networks`` table: ::
makenetworks
#. Verify the network statements
@ -33,13 +37,23 @@ Initialize DHCP services
#. Configure DHCP to listen on different network interfaces (**Optional**)
xCAT allows specifying different network intercaces thateDHCP can listen on for different nodes or node groups. If this is not needed, go to the next step. To set dhcpinterfaces ::
The ``dhcpinterfaces`` keyword allows users to specify or limit the DHCP to listen over certain network interfaces.
chdef -t site dhcpinterfaces='xcatmn|eth1,eth2;service|bond0'
If the management node has 4 interfaces, (eth0, eth1, eth2, and eth3), and you want DHCP to listen only on "eth1" and "eth3", set ``dhcpinterfaces`` with: ::
chdef -t site dhcpinterfaces="eth1,eth3"
To set "eth1" and "eth3" on the management node, and "bond0" on all the nodes in the "service" nodegroup, set ``dhcpinterfaces`` with: ::
chdef -t site dhcpinterfaces="xcatmn|eth1,eth3;service|bond0"
[**noboot**]: For the IBM OpenPower S822LC for HPC ("Minsky") nodes, the BMC and "eth0" on the compute side shares the same physical ethernet port. However, it is recommended to allow the BMC to be dedicated and to use "eth1" for the compute node. When an open range is configured on the two networks, the xCAT Genesis Kernel will be sent to the BMC interface and will cause problems with discovery. In this scenario, if "eth1" is the BMC network and "eth3" is the compute network, disabled genesis by setting ``:noboot`` in ``dhcpinterfaces`` with: ::
chdef -t site dhcpinterfaces="eth1:noboot,eth3"
For more information, see ``dhcpinterfaces`` keyword in the :doc:`site </guides/admin-guides/references/man5/site.5>` table.
#. Create a new DHCP configuration file with the networks defined using the ``makedhcp`` command. ::
makedhcp -n