Cisco Crosswork Network Controller 7.2 Administration Guide

PDF

Device onboarding methods

Want to summarize with AI?

Log in

Explains the different methods for onboarding devices into Cisco Crosswork Network Controller, detailing their prerequisites, workflows, and recommendations to ensure successful device registration and configuration.


A device addition is an onboarding mechanism that

  • enables registration of network devices into Cisco Crosswork Network Controller,

  • offers multiple supported methods tailored for different workflows, and

  • requires specific prerequisites for each method to ensure successful onboarding.

Cisco Crosswork Network Controller supports dual-stack deployment. Devices can be onboarded with both IPv4 and IPv6 addresses. To prevent duplicate entries, onboard each device only once using either the IPv4 or IPv6 address.

There are different ways to add devices to Crosswork Network Controller:

  1. Importing devices using the Crosswork APIs is the fastest and most efficient method, but it requires programming skills and API knowledge.

    For more information, see the CNC 7.2 API documentation.

  2. Importing devices from a Devices CSV file is time-consuming. To use this method, you must first:

    • Create corresponding credential profiles for all of the devices and providers listed in the CSV file.

      For more information, see Manage credential profiles.

    • Create the provider(s) that will be associated with the devices.

      For more information, see Providers.

    • Create tags for use in grouping the new devices.

      For more information, see Import tags.

    • Download the CSV template file from Crosswork Network Controller and populate it with the devices you plan to add.

    For information about adding devices using a CSV file, see CSV device imports.

  3. Adding devices via the UI is the least error-prone method because all data is validated during entry. However, this approach is time-consuming and is best for adding only a small number of devices at a time. Make sure device and provider credential profiles, as well as tags to be applied to them, are created before onboarding. For more information, see Add devices individually through the UI.

  4. Auto-onboarding from a Cisco SR-PCE provider is a highly automated and relatively simple method. Create device and provider credential profiles and any required tags before applying them to these devices. The auto-onboarding method does not create or assign device information automatically. Devices are initially discovered and added with partial information. To complete the onboarding process, you must supplement the missing details. You can provide the additional information by uploading a CSV file or manually adding it using the API or UI.

    For more information, see the provider properties in Provider families.

  5. Auto-onboarding using Zero Touch Provisioning is an automated process. First, create device entries and modify your installation's DHCP server. Make sure provider credential profiles and tags are created before use. After onboarding and provisioning, edit each device to supply any information not automatically added.

    For more information, see the Zero Touch Provisioningchapter in the Cisco Crosswork Network Controller 7.2 Device Lifecycle Management.

Note

If a device onboarded in Crosswork Network Controller shares a subnet with a Crosswork Data Gateway interface, ensure the device is on the data gateway's southbound network. Reverse Path Forwarding (RPF) checks in Crosswork Data Gateway require source addresses to be on the southbound network. Devices cannot use management or northbound networks if multiple NICs (2 or 3 NIC) are deployed.