Provisioning Fabric Devices Using End-to-End ZTP

Sample Topology

Prerequisites

• 5a12s3-node1:

  • Install CentOS 7.6.

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

    HWADDR=ac:xx:xx:xx:xx:88

NM_CONTROLLED=no

BOOTPROTO=none

DEVICE=enp2s0f0

ONBOOT=yes

IPADDR=10.87.x.2

NETMASK=255.255.255.224

GATEWAY=10.87.6.30

• 5a12s1-node1:

  • Install CentOS 7.6.

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

    HWADDR=0c:xx:xx:xx:xx:4a

NM_CONTROLLED=no

BOOTPROTO=none

DEVICE=eno1

ONBOOT=yes

IPADDR=10.87.x.1

NETMASK=255.255.255.224

GATEWAY=10.87.6.30

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

    HWADDR=90:xx:xx:xx:xx:a1

NM_CONTROLLED=no

BOOTPROTO=none

DEVICE=ens2f1

ONBOOT=yes

IPADDR=10.1.x.2

NETMASK=255.255.255.0

GATEWAY=10.1.x.1

1. Login to Contrail Command UI as a super user using credentials root for username and contrail123 for password.
   
2. Install bootstrap server.

   Click Servers.

   1. Click Create.
      
   2. Enter the required details.
   3. Click Create.
   

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

      
      
      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.

      
      
      
   4. Click Create.
4. After creating the cluster, login to the cluster using credentials root for username and c0ntrail123 for password.
   
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.

      
   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.

      

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.