Devices

The Devices settings view is the where you can register devices that you want to push configuration on.

This is different from the Infrastructure Device view which is displaying operational and configurational information about devices.

Register a Device

To register a Device in Prelude OneBoard, navigate to Application Settings > Devices.

Then click on the "+ New Device" button.

First, you need to give the device details:

• Hostname The device hostname, it has to match the hostname configured on the device
• Management IP The management IP address of the device. Keep it blank if you are using a ZTP extension that will allocate it
• Management VRF The management VRF of the device. Keep it blank if management doesn't use a VRF.
• Network OS The Network Operating System of the device
• Credentials The credentials to access the device
• Device Role The role you want to apply to the device (the list of protocols and the license of the Device role will be applied to the device)
• NSO Connection Select the NSO instance you want to use to manage the device configuration. Keep it blank if you don't want to configure this device via Prelude
• Prelude Gateway Select the Gateway instance you want to use to manage the device
• Enable ZTP See the Prepare a Device for ZTP Section

Then, you can customize the protocols that have been applied from the Device Role.

For each protocol, you can change the port, management IP or credentials.

Then, you can validate your device settings.

Prepare a Device for ZTP

If you selected the Enable ZTP option on the first step of the device registration wizard, after validating the device protocols settings, you will get to the ZTP settings view.

For more details about Zero Touch Provisioning, see our ZTP guide

See our vendor support page to identify what wee are supporting.

This view will allow you to specify the parameters to automatically onboard the device when it will be connected to the network.

• Serial Number The serial number of the target device
• ZTP Interface The interface that will start the ZTP process on the target device
• ZTP Subnet pool The Subnet pool to allocate a prefix from for the first phase of the ZTP process (see our ZTP guide)
• Device Target Template The configuration template that will be push to the device during the second phase of the ZTP process (see our ZTP guide)
• Software Version Optional software version to install on the device during the ZTP process

Then, select if you want to do Out-of-band ZTP or In-band ZTP

Out-of-band ZTP

For out-of-band ZTP, you need to specify additional parameters:

• ZTP Subnet Gateway The gateway to use during the first phase of the ZTP process (see our ZTP guide)
• ZTP Subnet Netmask The netmask of the prefix used during the first phase of the ZTP process (see our ZTP guide)

In-band ZTP

For in-band ZTP, you need to specify additional parameters:

• Attachment Device The device that will forward the ZTP requests
• Attachment Interface The Interface on the attachment device that will forward the ZTP requests
• Attachment ZTP VRF The VRF to use on the attachment device to forward the ZTP request
• Attachment AS Number The AS Number of the attachment device.

The VRF and ASN are used to announce the ZTP prefix in VRF BGP configuration on the attachment device.

ZTP Extension

ZTP Extension are Prelude plugins that can extend the default ZTP process with additional steps to integrate the newly onboarded device in your infrastructure.

As ZTP Extension are specific plugins, you need to refer to your extensions' documentation.

Template Variables

Finally, you will have to give values to the user defined variables in the ZTP template you selected.

The variables defined in the templates are automatically displayed here. If a variable is not shown, you should check your template syntax.

The "Preview template" button allow you to visualize the selected template with all the variables populated.

NSO Connector

If you selected a NSO connector for the device, you will see on the Device settings page the NSO sync state and the NSO Device ID.

NSO sync state

The NSO sync state should be to in-sync, if it is showing failed click on the state to get more details.

NSO Device ID

Before NSO 6.4, the device ID in NSO are difficult to change. So, we made the choice to use a UUID instead of the device hostname.

So, if you need to connect directly to NSO, you will need to use the UUID.