Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

On-Site Bootstrap Process for SD-WAN Devices

The on-site bootstrap process involves generating a bootstrap configuration file that loads from a bootable USB drive or from internal boot flash to a device that supports SD-WAN. When the device boots, it uses the information in the configuration file to come up on the network.

Overview

The on-site bootstrap process consists of this general workflow:

  • Use Cisco vManage NMS to generate a configuration file
  • Copy the configuration file to a bootable USB drive and plug the drive into a device, or copy the configuration to the bootflash of a device
  • Boot the device

If the configuration file is on both an inserted USB drive and on the bootflash, a device gives priority to the configuration file on the bootflash.

Device Requirements

Make sure that an SD-WAN image with version 16.10.1 or higher is loaded into the bootflash on the device.

Perform the On-Site Bootstrap Process

To perform the on-site bootstrap process for a device, follow these steps:

  1. Upload the Chassis ID and the serial number of the device to Cisco vManage.

For instructions, see Upload the vEdge Serial Number File.

  1. In Cisco vManage NMS, select AdministrationSettings and make sure that the Organization Name and the vBond IP address are configured properly.

These options display at the top of the Settings page.

  1. If you are using your own enterprise root certificate authority (CA) for device certification in your network, take these actions in Cisco vManage NMS:
  1. Select AdministrationSettings.
  2. Click Edit in the WAN Edge Cloud Certificate Authorization row.
  3. Click the Manual radio button.
  4. Click Save.
  1. In Cisco vManage NMS, select ConfigurationTemplatesFeature and create a template for the device.

For information about creating a template, see the “Create a Device Template” section in Templates.

  1. In Cisco vManage NMS, take these actions:
  1. Select Configuration ► Templates.
  2. Click the More Actions icon to the right of the row for the template that you created and select Attach Devices.
  3. Select the device for which you will generate the bootstrap configuration and attach the device. vManage NMS indicates that the device is offline but the template is attached.
  1. In Cisco vManage NMS, take these actions:
  1. Select ConfigurationDevices.
  2. Click the More Actions icon to the right of the row for the applicable device and select Generate Bootstrap Configuration.
  3. In the dialog box that opens, make sure that the Cloud-init radio button is selected, and then click OK.

The system generates a Multipurpose Internet Mail Extensions (MIME) file and displays its contents in a pop-up window. This file contains system properties for the device, the root CA if you are using an enterprise root CA, and configuration settings from the template that you created.

  1. In the MIME file pop-up window, click Download.

The system downloads the file to your local system and saves it in your directory for downloads. The file name is chassis.cfg, where chassis is the device chassis ID that you uploaded in Step 1.

Note: as an alternative to this step, you can copy the contents of the MIME file from the pop-up window to a text file, save the text file with the name ciscosdwan.cfg (case sensitive), and then skip to Step 8. The ciscosdwan.cfg file is the configuration file for the on-site bootstrap process.

  1. If you downloaded the MIME file, rename it to ciscosdwan.cfg (case sensitive).

This file is the configuration file for the on-site bootstrap process.

  1. Copy the ciscosdwan.cfg file to a bootable USB drive or to the bootflash of the device.

The file must be named exactly as shown or the device will not read it.

  1. If you are using a USB drive, plug the USB drive into the device.
  2. From the router, enter this command to create a backup of the current configuration that can be saved in the router bootflash:

ISR4K# copy run bootflash:original-xe-config

  1. Enter these commands to remove all existing boot statements and save the configuration:

ISR4K# (config)# no boot system ...
ISR4K# wr mem

  1. Enter this command and verify that the BOOT variable is blank as shown in in the sample output:

ISR4K# show bootvar

BOOT variable =CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
Standby not ready to show bootvar
  1. Enter these commands to add a boot variable that points to the XE SD-WAN image:

ISR4K# (config)# boot system flash bootflash:SDWAN-image

ISR4K# wr mem

  1. Enter this command and verify that the BOOT variable points to the XE SD-WAN image as shown in the sample output:

ISR4K# show bootvar

BOOT variable =  bootflash:isr4300-ucmk9.16.10.1.SPA.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exists
Configuration register is 0x2102

Standby not ready to show bootvar
  1. Enter this command to remove all existing configuration from the router:

ISR4K# write erase

  1. Enter the following commands to set the config-register to 0x2102:

ISR4K# config t

ISR4K(config)# config-register 0x2102

ISR4K(config)# end

  1. Enter the following commands to verify that the config-register is set to 0x2102 or that it will be set to 0x2102 at the next reboot:

ISR4K# show bootvar

  1. Enter these commands to reboot the router:

ISR4K# reload

Proceed with reload? [confirm] Yes

If prompted to save the configuration, enter No. The device reads the configuration file from the USB drive or the bootflash and uses the configuration information to come up on the network. The device give priority to a configuration file that is on its bootflash.

  • Was this article helpful?