Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Provision 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.

An All-in-One (AIO) Contrail cluster is a single Contrail Networking server with multiple VMs that supply controller, orchestrator, and, compute nodes.AIO cluster node responds to DHCP requests to zeroize devices. Hence, AIO cluster node must be in the same subnet as of the management subnet.

Note:

The minimum required version of Junos OS for QFX5000 and QFX10000 Series devices is 18.1R3-S5 or higher. The minimum required version of Junos OS for the MX devices is 18.4R2-S3. Also, all MX Series Routers must be zereoized for ZTP to work.

The following example illustrates the process for provisioning fabric devices using end-to-end ZTP.

Sample Topology

Network topology diagram showing connections between switches and servers in a data center. Includes QFX10008 and QFX5110 switches with console IPs, CC and AIO servers with management and fabric ports, and labeled MGMT connections.

Prerequisites

  • Contrail Command server:

    • Install CentOS 7.6.

  • AIO Contrail cluster node:

    • 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.

command_servers.yml example file:

To provision fabric devices using ZTP via Contrail Command UI:

  1. Log in to Contrail Command UI as a super user using root user credentials.
    Contrail Command login page with fields for cluster selection, username root, password entry, and a blue Log in button.
  2. Install bootstrap server.

    Click Servers.

    1. Click Create.
    2. Enter the required details.
    3. Click Create.
    Configuration form for server setup with fields for mode selection, workload type, hostname, management IP, interface, credentials, MAC address, disk partitions, and network interfaces.

    • Port eno1 is connected to management VLAN.

    • Port ens2f1 is connected to QFX ToR.

  3. Create cluster by entering the required details.
    1. Click Cluster.
    2. Click Add Cluster.
    3. Enter the required details including Inventory, Cloud Manager, Infrastructure Networks, Overcloud, etc.

      Check Enable ZTP checkbox.

      • Default Vrouter Gateway is the QFX ToR IRB IP. The IP is used for provisioning the network.

      CONTROLLER_NODES and CONTROL_NODES are a part of Contrail Networking Configuration.

      • CONTROLLER_NODES IP is a static IP configured on port eno1.

      • CONTROL_NODES IP is a static IP configured on port ens2f1.

      Step 2 Cloud Manager configuration interface showing fields for cluster name, container registry, provisioner type, domain suffix, encapsulation priority, and options for enabling ZTP. User interface for server configuration showing available servers section empty and assigned control nodes section listing 5a12s1-node1 with multiple roles. High availability mode is unchecked. Options include search, add, and remove assigned nodes.
      Note:

      Set enable_swift to yes if the cluster will be used for any image management tasks on the fabric devices. Otherwise, set enable_swift to no.

      • enable_ironic is used for life cycle management of Bare Metal Servers (BMS).

      • enable_swift is used to provision Swift containers (object storage). All the images used during different fabric related tasks are stored in these containers.

      • enable_haproxy is used when OpenStack controllers are set up in high availability (HA) mode.

      OpenStack deployment interface with orchestrator type OpenStack, container registry default, release version queens, network configuration fields, custom configurations section, Kolla Globals with services disabled, empty Kolla Passwords and Available Servers, assigned node 5a12s1-node1 with control and network roles, navigation buttons Previous and Next. User interface for managing servers with sections for available servers and assigned service nodes. Includes hostname, IP address, disk partition columns, search bar, and buttons for adding or removing nodes. Cluster management interface displaying configuration details for an OpenStack and Contrail setup. Shows cluster name AIO, Contrail version master-550, provisioning type ansible, domain suffix local, NTP server ntp.juniper.net, encapsulation protocols VXLAN MPLSoUDP MPLSoGRE, Zero Touch Provisioning enabled, and OpenStack release queens. Nodes section lists a physical or virtual control and compute node named 5c1057-node4. Includes buttons for navigation and provisioning.
    4. Click Create.
  4. After creating the cluster, log in to the cluster using root user credentials.
    Login page for Contrail Command with fields for cluster selection, username entry, password entry, and a Log in button for access.
  5. 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.

       User interface screenshot for Step 1: Create Fabric in a network automation tool. Includes fields for fabric name, device credentials, overlay ASN, management subnets, options for YAML templates, selectable node profiles, and navigation buttons for Cancel and Next.
    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.

      Network configuration interface showing step 3 of 4, Assign the roles, in fabric setup. Table lists devices DK588 as spine with CRB-GatewayRoute-Reflector and WS3 as leaf with CRB-Access. Autoconfigure set to False for both. Options to search, refresh, and assign roles are on the right.

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.

    Form for configuring network settings with fields for Name set to provisioning, VLAN set to 222, empty IPAM Network fields for CIDR and Gateway, empty DHCP Relay Server field with add option, and Create and Cancel buttons.

  2. Import server topology.

    1. Click Servers.

    2. Click Import.

    3. Upload the server topology file.

      User interface for importing server configurations with options to upload JSON or YAML files. Selected file is server_01.yaml. Includes Cancel and Import buttons. 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.

      User interface showing a server management platform with tabs, server list including name, type, node profile, cluster name, cluster roles, action buttons for import, discovery, create, and icons for search, refresh, delete, and assign node profile.

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

Related Documentation

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
2003
The minimum required version of Junos OS for the MX devices is 18.4R2-S3. Also, all MX Series Routers must be zereoized for ZTP to work.
1907
Contrail Networking Release 1907 introduces the ability to configure hostnames to the devices being onboarded