======================
Changing a bonder key
======================

It may be convenient to update a bonder so that it hosts a different
bond, without re-imaging the device. This may happen when a device is
retrieved from one customer's site and is then put into service at a
different customer's site.

.. note::

    To change the bond associated with a particular bonder, consider
    re-imaging the device instead of following the instructions on this
    page. This has some advantages over changing the node key:

    -  it is less prone to error,
    -  it ensures the bonding software and operating system packages are up
       to date, and
    -  it removes old log files and any customizations made to the device.


To change a bonder's key so that it hosts a different bond, follow these
instructions:

#. Start a command shell, either via SSH, serial, or a virtual console.
#. Ensure the node has network access.
#. Open the file ``/etc/bonding/bonding.conf`` with your favourite text
   editor.
   For example:
   ``nano /etc/bonding/bonding.conf``
#. Update the key and/or server field. Save the file.
   For example, in nano type Ctrl-X, then type Y, then hit <enter>.
#. Download a new cached config file by running ``nodeconfig``.
#. Restart bonding.
   ``service bonding restart``
