+ <title>Common Scenarios</title>
+
+ <para>Below are common scenarios that the boot manager might encounter
+ that would exist outside of the documented procedures for handling nodes.
+ A full description of how they will be handled follows each.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>A configuration file from previously installed and functioning
+ node is copied or moved to another machine, and the networks settings
+ are updated on it (but the key is left the same).</para>
+
+ <para>Since the authentication for a node consists of matching not
+ only the node id, but the primary node ip, this step will fail, and
+ the node will not allow the boot manager to be run. Instead, the new
+ node must be created at PLC first, and a network configuration file
+ for it must be generated, with its own node key.</para>
+ </listitem>
+
+ <listitem>
+ <para>After a node is installed and running, the administrators
+ mistakenly remove the cd and disk.</para>
+
+ <para>The node installer clears all boot records from the disk, so the
+ node will not boot. Typically, the bios will report no operating
+ system.</para>
+ </listitem>
+ </itemizedlist>