{"id":1117,"date":"2019-06-19T18:15:14","date_gmt":"2019-06-19T18:15:14","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=1117"},"modified":"2020-05-06T10:26:58","modified_gmt":"2020-05-06T17:26:58","slug":"bare-metal-provisioning","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/community\/bare-metal-provisioning\/","title":{"rendered":"Bare Metal Provisioning"},"content":{"rendered":"

This document describes a possible method for implementing bare metal provisioning utilizing Infoblox\u2019s NetMRI and IPAM products.<\/p>\n

The aim of the process described here is to allow the customer to deliver network devices to their site and then have installers rack and connect the servers to power and network and have the devices come up onto the network with the correct configuration with no input from the installers.<\/p>\n

Sequence of events<\/strong><\/p>\n

The following diagram shows the steps involved and the sequence of events, between the device to be provisioned, the Infoblox DHCP server and IPAM servers along with the NetMRI Network Automation server.<\/p>\n

\"Bare<\/p>\n

Steps<\/strong><\/p>\n

    \n
  1. Engineer installs the device in the correct location, connects the device to the network and powers it up.<\/li>\n
  2. The Device starts up and sends out DHCP request for IP and location of a server to pick up a configuration from.<\/li>\n
  3. The DHCP server identifies the correct range to issue an IP address from, based on the gateway address in the initial DHCP Discover message.<\/li>\n
  4. The DHCP server returns the IP address for the device, along with the location of the server to pull the default configuration from (In this case, the NetMRI server).<\/li>\n
  5. The DHCP server informs NetMRI via syslog that it has issued a new lease, providing the IP address.<\/li>\n
  6. The Device contacts NetMRI to request a configuration file.<\/li>\n
  7. NetMRI returns the default config file to the device \u2013 this contains three items of information that are important for NetMRI in this process:\n
      \n
    1. A node name that identifies it as a device that is to be provisioned \u2013 for example \u2013 autoconfig.<\/li>\n
    2. A SNMP v1\/v2c community string or V3 details that is known to NetMRI, so it can discover the device.<\/li>\n
    3. A local Telnet\/SSH user that NetMRI knows of, so that it can discover and pull configurations from the device, and more importantly, also to push configuration to the device once it has been discovered.<\/li>\n<\/ol>\n<\/li>\n
    4. The Device Reloads using the default configuration file.<\/li>\n
    5. NetMRI attempts to discover the device, using the known credentials.<\/li>\n
    6. The device responds with the request information to NetMRI.<\/li>\n
    7. NetMRI identifies that this is a device that BMP is applicable for.<\/li>\n
    8. NetMRI builds up the correct configuration for the device, based on a template configuration, using the following information to pick out the configuration template to use:\n
        \n
      1. Device Type<\/li>\n
      2. Device Vendor<\/li>\n
      3. Device OS<\/li>\n
      4. Device Model<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

        As well as identifying the correct template to use, NetMRI will look up the IP address within IPAM, identify the range it was issued from and pull the extensible attributes to create the permanent node name for this device.<\/p>\n

        NetMRI could also look up other extensible attributes from IPAM, if for example other attributes were utilized to hold details for the following types of data:<\/p>\n