.. _initial-bonding-configuration:

==============================
Initial Bonding configuration
==============================

When SD-WAN in installed on a host, it can be configured in one
of two ways:

#. By assigning it to a specific bond or aggregator record defined in
   the management server—useful for sending pre-configured devices to
   customers or for building aggregators
#. With a default, generic bonder configuration—the device can be
   assigned to a bond at a later time via a web application on the
   device

Configuration modes
--------------------

Configuration as a specific bond or aggregator
+++++++++++++++++++++++++++++++++++++++++++++++

In this configuration mode, a host is given a node key at the same time
SD-WAN is installed. This will assign the host to a specific
bond or aggregator record in the management server. It can be used to
configure a bonder for a certain customer, then ship the bonder to the
customer ready to connect to the legs and connected IP networks.

To use this mode, provide a node key at the SD-WAN installer
prompt. The appropriate configuration file will be downloaded and saved
on the host.

Default bonder configuration
+++++++++++++++++++++++++++++

In this mode, the device is not assigned to a bond or aggregator when
SD-WAN is installed. Instead, it uses a default configuration
and can be assigned to a bond at a later time using a `simple web
application hosted on the
device <configuring-default-bonder-via-web-service.html>`__.

To use this mode, leave the node key field empty when prompted by the
SD-WAN installer.

Installation steps
-------------------

SD-WAN requires certain information before it can complete its
installation.

Management server address
++++++++++++++++++++++++++

The URL of the management server. For example, bondingadmin.example.com.

The management server address is not requested when using the `custom
ISO <../nodes/provisioning-nodes/creating-bootable-usb-disks-from-iso-images.html>`__
or `PXE boot <node-installation-methods/installing-via-a-pxe-server.html>`__ methods,
because the address is specified in the custom ISO or PXE options.

|image0|

.. _node-key:

Node key
+++++++++

The key the node uses to identify itself to the management server. If
left blank, the host will use a default bonder configuration, described
above.

|image1|

If the host is to be configured as a bonder, the key is available on the
bond details page:

|image2|

To configure a host as a bonder, the bond must have at least one leg.

If the host is an aggregator, the key is available on the aggregator
details page:

|image3|

Type the key at the prompt and press enter. The installer will download
the host's configuration file and set up a number of services and
resources on the device. The installer will exit when it finishes
configuring the host.

.. note::

    If the management server's SSL certificate cannot be verified, a warning
    is shown. You can choose to ignore the error, retry the request, or quit
    the installation. If you quit the installation, SD-WAN will be
    left in a partially-configured state.

    The most common reason a SSL certificate cannot be verified is because
    it is not signed by a trusted authority. This is known as a self-signed
    certificate. To avoid seeing this error, `technical
    support <../../spaces/technical-support.html>`__ can help you get a properly
    signed certificate.


.. |image0| image:: /attachments/1179681/2392092.png
.. |image1| image:: /attachments/1179681/2392097.png
.. |image2| image:: /attachments/1179681/2392095.png
.. |image3| image:: /attachments/1179681/2392098.png
