Skip to main content

Initialize Your Device - Advanced Workflows

While the Web Interface is the recommended method of initializing and onboarding your SSR device, there are alternative methods that can be used to complete the process. These methods are typically used when further customization of the conductor and router is required, and performed by advanced users.

In this document, you will find:

  • Information about the PCLI commands used to initialize a conductor and conductor-managed router.
  • Information about the PCLI commands used to initialize a Mist-managed router.
  • File structure needed for performing automated onboarding of conductors and routers.
  • Workflows for automating onboarding by supplying the necessary files using three different processes:
    • USB Initialization
    • File on Disk
    • API Initialization

Select the initialization workflow that suits the needs of your deployment.

Connection Setup​

For non console access you can connect your laptop or other device to any of the designated LAN port and SSH to 192.168.128.1 to login via SSR PCLI and/or shell.

note

The laptop or other client device must be assigned a static IP address within the range of 192.168.128.2 to 192.168.128.254 along with a subnet mask of /24 or 255.255.255.0

PCLI Workflow​

Use the following workflows to initialize and onboard your device. For a conductor-managed deployment use

To onboard a Mist-managed router to your Mist Org, use

Initialize a Conductor​

The initialize conductor command allows the user to overwrite the defaults provided in the Web workflow and allows for further customization of conductors.

initialize conductor [artifactory-user <artifactory-user>] [artifactory-password <artifactory-password>] [dns-servers <dns-servers>] [node-ip <node-ip>] [node-gateway <node-gateway>] [interface-name <interface-name>] [clustered] [ha-ip <ha-ip>] [ha-interface-name <ha-interface-name>] [ha-peer-ip <ha-peer-ip>] [ha-peer-name <ha-peer-name>] [learn-from-ha-peer] [ha-peer-username <ha-peer-username>] [unsafe-ha-peer-password <unsafe-ha-peer-password>] router-name <router-name> node-name <node-name>

Allowed Options:

namedescription
artifactory-passwordPassword portion of the artifactory credentials.
artifactory-userUser portion of the artifactory credentials.
dns-serversComma separated list of DNS servers.
interface-nameInterface name (matching a port in the device-map) to bind the node-ip and node-gateway.
learn-from-ha-peerIf true, the Initializer will use the HA peer to obtain setup information.
node-gatewayThe IP address of the gateway of the node being provisioned.
node-ip(Required) The IPv4 address of the node being provisioned (x.x.x.x/y)
node-name(Required) The name of the node being provisioned. For standalone, this is node0.
router-name(Required) Assign a name to the router/conductor.
clustered(Required for HA) Whether or not this conductor is to be configured as an HA pair; set to true .
ha-interface-nameInterface name (matching a port in the device-map) to bind the ha-ip.
ha-ipThe IPv4 address to assign to the HA interface on this node.
ha-peer-ipThe IPv4 address of the node to be used as an HA peer.
ha-peer-nameThe name of the Node to be used as an HA peer.
ha-peer-usernameThe user on the peer node to authenticate as. This user must have sudo privileges. Required if learn-from-ha-peer is true.
unsafe-ha-peer-passwordThe password for the user on the peer node to authenticate as. WARNING: If this field is used, the preferences file should not be world-readable to avoid leaking the peer node password. Required if learn-from-ha-peer is true.

When configuring High Availability, if any one of the following options is configured, then they all must be:

  • ha-ip
  • ha-interface-name
  • ha-peer-ip
  • ha-peer-name
  • learn-from-ha-peer
  • ha-peer-username
  • unsafe-ha-peer-password

For more information on the available options and parameters, refer to the initialize conductor command.

Initialize a Conductor-Managed Router​

The following PCLI command can be used to onboard a router to a conductor as conductor managed.

initialize conductor-managed router-name <rtr-name> conductor-ip <ip-address>

For additional information, refer to the initialize conductor-managed command.

Initialize a Mist-Managed Router​

The following PCLI command will onboard a router to the Mist inventory.

adopt router-name <router-name> registration-code <reg-code>

Automated Onboarding​

Automated onboarding can be used whenever the user wants to automatically set up a device during first boot, and does not require manual input. All the onboarding configurations must be known prior to starting the process. These methods should also be used If the user wants to provide a customized interface mapping scheme for whitebox platforms.

Onboarding Configuration File​

The brains behind the automated onboarding process is a json file named onboarding-config.json. This file contains all the configuration parameters and drives the entire onboarding process. The onboarding-config.json can be provided from a USB, as a file placed in /etc/128T-hardware-bootstrapper/onboarding-config.json on the SSR disk, or applied via API initialization. For virtual and cloud based deployments, the same mechanism is supported via cloud-init as well.

The following are examples of the onboarding-config.json files.

Conductor Onboarding Configuration Example File​

The following JSON is an example of a valid conductor onboarding-config.json that can be used to onboard a conductor using any of the following methods:

{
"name": "MyConductor",
"mode": "conductor",
"artifactory-user": "username",
"artifactory-password": "password",
"node-name": "node0",
"node-ip": "10.73.1.10/24",
"node-gateway": "10.73.1.11",
	"interface-name": "ge-0-0",
	"dns-servers": [
		"8.8.8.8",
		"1.1.1.1"
	]
}

Conductor-Managed Router Onboarding Configuration Example File​

The following is an example onboarding config that can be used to onboard a conductor-managed router using API Initialization or a file placed on disk.

{
“mode”: “conductor-managed”,
“conductor-hosts”: [“1.2.3.4”]
}

If no router name is supplied in the onboarding config, the default name is chosen in this order:

  1. Serial Number (via DMI table)
  2. Hostname
  3. UUID (via DMI table)

Mist-Managed Router Onboarding Configuration Example File​

The following is an example onboarding config that can be used to onboard a Mist-managed router using API Initialization or a file placed on disk.

{
“mode”: “mist-managed”,
“name”: “mist-router”,
“registration-code”: "<mist-reg-code>”
}

If no router name is supplied in the onboarding config, the default name is chosen in this order:

  1. Serial Number (via DMI table)
  2. Hostname
  3. UUID (via DMI table)
note

If no onboarding configuration file is provided, it is assumed that the device is an unmanaged router, and an onboarding configuration will be provided later.

USB Initialization​

When the device boots for the first time it looks for a connected USB device named BOOTSTRAP.

  1. Create a USB device named BOOTSTRAP.

  2. On the USB, create the following files in the root directory:

    • onboarding-config.json
    • devicemap.json
    • pre-bootstrap
    • post-bootstrap

  3. Insert the USB into the SSR device and power it on.

  4. The device will boot and automatically configure based on the provided files.

Scriptlets are passed in the device identifier, which is typically the device serial number. The order of operations is:

  1. Pre-bootstrap
  2. Normal bootstrapping operation
  3. Post-bootstrap
  4. Onboarding

File on Disk​

If no onboarding config was found on a USB device, the initialization process looks for a configuration file placed on the device; this is a common workflow for virtual devices. You can also provide a customized devicemap in the onboarding config at this time.

  1. Create the following files:

    • onboarding-config.json
    • devicemap.json
    • pre-bootstrap
    • post-bootstrap

  2. Copy the files onto the SSR device into the following locations:

    • /etc/128T-hardware-bootstrapper/onboarding-config.json
    • /etc/128T-hardware-bootstrapper/devicemap.json
    • /etc/128T-hardware-bootstrapper/pre-bootstrap
    • /etc/128T-hardware-bootstrapper/post-bootstrap

  3. Reboot the device.

If you wish to not onboard the device and only supply a devicemap, the device is onboarded as an unmanaged router.

API Initialization​

If an onboarding-config.json was not provided during the initial bootstrapping of the device, the you can choose to initialize the device by supplying an onboarding config path directly from the API. The POST endpoint is /api/bootstrap/onboarding with a json body containing the contents of the onboarding-config file. To apply an onboarding configuration, place the contents of the desired onboarding config file in onboarding-cfg.json and run the following command. Alternatively, you can include the JSON contents directly in the curl request.

curl -X POST -H "Content-Type: application/json" -d @onboard-cfg.json http://localhost:31517/api/bootstrap/onboarding