--- title: "Preparing the NetMRI VM Configuration File" canonical: "https://docs.infoblox.com/space/OCDeployGuide/143295611/Preparing%20the%20NetMRI%20VM%20Configuration%20File" format: markdown --- The cloud-init automatically configures NetMRI and Sandbox virtual appliances with user-defined parameters. Currently, automatic configuration is possible for deployments of OpenStack and AWS. YAML and XML formats are supported for cloud-init configurations, but only the most essential cloud-init configuration fields are supported. For details about the valid fields for each option, refer to the *[Configuring Network Interfaces](https://infoblox-docs.atlassian.net/wiki/spaces/OCDeployGuide/pages/143295408)* section. When setting up a NetMRI instance in OpenStack, you can pass the configuration file to the NetMRI VM in various methods. The file format is dependent on the method selected. These methods consist of the following: - Using direct text input or uploading the configuration file accessible via network - The text or file must use the YAML format. This method is enabled by default cluster-wide in an OpenStack environment, although there may be some distributions that disable it. - Using the Configuration Drive (i.e., virtual CD-ROM) - The configuration file is provided as mentioned above, along with an additional Configuration Drive option. The file is automatically placed in an ISO image that appears to the VM as a CDROM drive. - Using the OVF transport method - The configuration file must be an XML file of the OVF schema type, encoded in Base 64 encoding. For more information, see [U](https://infoblox-docs.atlassian.net/wiki/spaces/OCDeployGuide/pages/142967836)*[sing OVF Transport Method of Passing Configuration File to NetMRI VM Instance](https://infoblox-docs.atlassian.net/wiki/spaces/OCDeployGuide/pages/142967836)*. ## **YAML Format Examples** The following are examples of YAML-formatted configuration file content from the NetMRI and Sandbox configurations: ### Configuring NetMRI with a Static IP Address for the MGMT Interface `#infoblox-config` `default_admin_password:` `"admin_password"` `server_name:` `test-vm` `db_name:` `this_test_db` `mgmt_port:`     `v4_addr:` `192.168.1.10`     `v4_netmask:` `255.255.255.0`     `v4_gw:` `192.168.1.1`     `v6_addr:` `2002::10`     `v6_prefix:` `64`     `v6_gw:` `2002::1`     `primary_dns_server:` `192.168.1.1`     `secondary_dns_server:` `2002::1`     `search_domains:`         `-` `mgmt.domain`         `-` `mgmt.local` `scan_port:`     `v4_addr:` `192.168.2.10`     `v4_netmask:` `255.255.255.0`     `v4_gw:` `192.168.2.1`     `v6_addr:` `2003::10`     `v6_prefix:` `64`     `v6_gw:` `2003::1`     `primary_dns_server:` `192.168.2.1`     `secondary_dns_server:` `2003::1`     `search_domains:`         `-` `scan.domain`         `-` `scan.local` `time:`     `server_1:` `time.local`     `timezone:` `Etc/UTC` ### Configuring MGMT Interface IP for NetMRI using DHCP `#infoblox-config` `default_admin_password:` `"admin_password"` `server_name:` `test-vm` `db_name:` `this_test_db` `mgmt_port:`     `v4_use_dhcp:` `true`     `v6_use_dhcp:` `true`     `primary_dns_server:` `192.168.1.1`     `secondary_dns_server:` `2002::1`     `search_domains:`         `-` `mgmt.domain`         `-` `mgmt.local` `scan_port:`     `v4_addr:` `192.168.2.10`     `v4_netmask:` `255.255.255.0`     `v4_gw:` `192.168.2.1`     `v6_addr:` `2003::10`     `v6_prefix:` `64`     `v6_gw:` `2003::1`     `primary_dns_server:` `192.168.2.1`     `secondary_dns_server:` `2003::1`     `search_domains:`         `-` `scan.domain`         `-` `scan.local` `time:`     `server_1:` `time.local`     `timezone:Etc/UTC` ### Configuring Sandbox with a Static IP Address for the MGMT Interface `#infoblox-config` `default_admin_password:` `"admin_password"` `server_name:` `test-vm` `mgmt_port:`     `v4_addr:` `192.168.1.10`     `v4_netmask:` `255.255.255.0`     `v4_gw:` `192.168.1.1`     `v6_addr:` `2002::10`     `v6_prefix:` `64`     `v6_gw:` `2002::1`     `primary_dns_server:` `192.168.1.1`     `secondary_dns_server:` `2002::1`     `search_domains:`         `-` `mgmt.domain`         `-` `mgmt.local` `time:`     `server_1:` `time.local`     `timezone:` `Etc/UTC` ### Configuring DHCP IP for MGMT Interface in a Sandbox `#infoblox-config` `default_admin_password:` `"admin_password"` `server_name:` `test-vm` `mgmt_port:` `mgmt_port:`     `v4_use_dhcp:` `true`     `v6_use_dhcp:` `true`     `primary_dns_server:` `192.168.1.1`     `secondary_dns_server:` `2002::1`     `search_domains:`         `-` `mgmt.domain`         `-` `mgmt.local` `time:`     `server_1:` `time.local`     `timezone:Etc/UTC` ## **XML Format Example** The following is an example of XML-formatted configuration file content: `` `` `` `` `` `` > ⚠️ ### Note > ⚠️ > ⚠️ The value of the user-data key here is of the same format as the configuration above but encoded in Base64 encoding.