--- title: "Deployment for Bare Metal Provisioning, Pt. 1" canonical: "https://docs.infoblox.com/space/NetMRI753/42010324/Deployment%20for%20Bare%20Metal%20Provisioning%2C%20Pt.%201" format: markdown --- The **Provision** **Bare** **Metal** **Device** automated task enables automated installation of new switches and routers into the network. **Provision** **Bare** **Metal** **Device** (which we will refer to as BMP, for Bare Metal Provisioning) is used in initial deployments of many instances of the exact same device model, that will all use very similar configurations. For example, a company named Genuine Parts has 5500 storefront locations that will each use a new Cisco 2812 router as their gateway. Each device uses the exact same configuration, excepting the IP address, interface description and VLAN ID. Bare Metal Provisioning is defined for specific cases of this type. BMP jobs cannot be executed across multiple types of devices in the same Job (e.g. a few 2812 routers, several 3750 switches, a dozen 2960 switches in the same job) because the Lists for BMP are written for a single device type for each job execution, to account for different numbers, interface types and other parameters. The job script must be modified to support the changes to the List for each job execution. The BMP process is quite different from simply plugging a new Cisco appliance, giving it an IP address through a terminal program, allowing NetMRI to discover it and then pushing a configuration to it. BMP automates the process for deployments of the same device across many individual locations. The Automation task enables cost and convenience savings by detecting the default behavior of new devices on the network, pointing them to TFTP servers from which the new devices download and install standardized bare-metal configuration files. Configuration for the **Provision** **Bare** **Metal** **Device** automated task is primarily done in the NetMRI user interface. The automated task is automatically triggered by detection of a network device requiring configuration. > Macro (legacy-content) d. Click **Register** to commit settings. After registration, the ACM Registration menu item changes to read ACM Deregistration to support disconnection from the Automation Change Manager appliance. 8. To set NetMRI to receive Syslog from the NIOS appliances running DHCP, do the following on the NIOS system: > Macro (legacy-content) Individual NIOS appliances may need to be restarted for the changes to take effect. 9. Set up the DHCP protocol in the NIOS appliances. On each NIOS system running DHCP that you expect to participate in auto-configuring network devices, set the DHCP ranges as follows. For the NIOS Grid, do the following: > Macro (legacy-content) Example: for Cisco devices, choose option 66 and enter the FQDN, or the IP address of the TFTP server (which could be the NetMRI system, a NIOS appliance or another system). e. Click **Save** **and** **Close**. f. Follow the same steps for any other DHCP range as necessary. 10. In the NetMRI appliance, choose **Settings** icon > **General**** Settings** > **Advanced**** Settings** and make sure the following two settings are turned **On**: > Macro (legacy-content) 11. Choose **Settings** icon > **Setup** > **Credentials** **>** **CLI** and add a new USER credential of *admin*/*infoblox*, with an ENABLE password of *infoblox*. These credentials are pushed to the bare metal device after it boots with its TFTP configuration. 12. Choose Settings icon > **Setup**>** Credentials** >** SNMPv1/2c** and click the *autoconfig* community string (it defaults to Priority 16). Click Edit and change its Priority value to 1. 13. Also in the **SNMPv1/2c** page, click **New** and create a new community string *infoblox*. Assign it a Priority value of 2 and click **Add**. 14. Continue to the following topic, [ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[Deployment](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[for](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[Bare](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[Metal](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[Provisioning,](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[Pt.](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*[2](https://infoblox-docs.atlassian.net/wiki/spaces/NetMRI753/pages/41912558)*