Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Provisioning Fabric Devices Using End-to-End ZTP

From Contrail Networking Release 5.1, you can provision fabric devices using Zero Touch Provisioning (ZTP).

ZTP allows you to provision new Juniper Networks devices in your network automatically, with minimal manual intervention.

This topic provides steps to provision fabric devices using ZTP and configure underlay network via Contrail Command UI.

Note:

You must complete Installing Contrail Command before proceeding.

Note:

The minimum required version of Junos OS for QFX5000 and QFX10000 Series devices is 18.1R3-S5 or higher.

Sample Topology

Prerequisites

These are example parameters. The interface name can be different based on your deployment.

  • 5a12s3-node1:

    • Install CentOS 7.6.

    • Configure eno1 port with the static IP 10.87.x.2/27.

  • 5a12s1-node1:

    • Install CentOS 7.6.

    • Configure eno1 port with the static IP 10.87.x.1/27.

    • Configure ens2f1 port with the static IP 10.1.x.2/24.

To provision fabric devices using ZTP via Contrail Command UI:

  1. Install Contrail Command. For details, see Installing Contrail Command.
  2. Install a Contrail cluster using Contrail Command. For details, see Installing a Contrail Cluster Using Contrail Command.
  3. After creating the cluster, log in to the cluster using root user credentials.
  4. Run fabric ZTP workflow to onboard the fabric devices
    1. Click Fabrics.
    2. Click Create .
    3. Click New Fabric.
    4. Click Provision.
    5. Enter the required details.
      Table 1: Required Fields for creating Fabric

      Field

      Details

      Overlay ASN (iBGP)

      IBGP ASN pool for Contrail Networking overlay network. List of the ASN pools that can be used to configure the IBGP peers for the IP fabric

      Underlay ASNs (eBGP)

      EBGP ASN pool for fabric underlay network. List of the ASN pools that can be used to configure the EBGP peers for the IP fabric

      Management subnet

      List of the management network subnets for the fabric

      Fabric subnet

      List of subnet prefixes that can be used for the P2P networks between fabric devices

      Loopback subnet

      List of the subnet prefixes that can be allocated to fabric device loopback IPs

      Sample device_info.yml file
      Note:

      The YAML file lists the devices used for ZTP during a greenfield onboarding of devices. Contrail Networking Release 1907 introduces the ability to configure hostnames to the devices being onboarded. If the hostnames attribute is not specified, the device serial number is used as the hostname by default.

    6. Assign the roles to the fabric devices.

      • DK588 as Spine with CRB-Gateway and Route-Reflector roles.

      • WS3XXXX0049 as Leaf with CRB-Access role.

To configure underlay network via Contrail Command UI:

  1. Create provisioning infrastructure network.

    1. Click Networks.

    2. Create a network by entering the required details.

  2. Import server topology.

    1. Click Servers.

    2. Click Import.

    3. Upload the server topology file.

      Sample server topology yaml file:
      Table 2: Required Fields for server topology yaml file

      Field

      Details

      name

      Name of the infrastructure BMS node

      type

      Type of the infrastructure BMS node. It must be "baremetal"

      ports

      List of the ports of BMS node connected to the TOR switch

      name

      Name of the BMS port

      switch_name

      TOR switch name

      port_name

      TOR port name

  3. Import server node profile.

    You must create server node profile for the Contrail Networking Controller server.

    1. Click Servers.

    2. Click Node Profiles.

    3. Click Import.

    4. Upload the server node profile file.

      Table 3: Required fields for Server Node Profile

      Field

      Details

      kind

      Resource type

      name

      Name of a resource

      fq_name

      Fully Qualified name of a resource

      parent_type

      Node profile parent resource type. It must be "global-system-config"

      node_profile_vendor

      Node Profile vendor name

      node_profile_type

      Node profile type. It must be "end-system" for servers

      hardware_refs

      List of references to the hardware models supported by the node profile

      card_refs

      List of references to the interface cards
      Sample server node profile json file:

  4. Assign node profile to the server.

    1. Click Servers.

    2. Select the required server from the list.

    3. Click Assign Node Profile.

Once the above procedure is completed, change the default route from management port to the access port.

Related Documentation

Release History Table
Release
Description
1907
Contrail Networking Release 1907 introduces the ability to configure hostnames to the devices being onboarded