anchor.diff:  
   image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png[Installer-provisioned networking]
   
  -[discrete]
  +[id='network-requirements-config-nics_{context}']
   == Configuring NICs
   
   {product-title} deploys with two networks:
  
positive.code: You can use the `dig` command to verify DNS resolution.
  ====
  
  [discrete]
  == Dynamic Host Configuration Protocol (DHCP) requirements
  
  By default, installer-provisioned installation deploys `ironic-dnsmasq` with DHCP enabled for the `provisioning` network. No other DHCP servers should be running on the `provisioning` network when the `provisioningNetwork` configuration setting is set to `managed`, which is the default value. If you have a DHCP server running on the `provisioning` network, you must set the `provisioningNetwork` configuration setting to `unmanaged` in the `install-config.yaml` file.
  
  Network administrators must reserve IP addresses for each node in the {product-title} cluster for the `baremetal` network on an external DHCP server.
  
  [discrete]
  == Reserving IP addresses for nodes with the DHCP server
  
  For the `baremetal` network, a network administrator must reserve a number of IP addresses, including:
  
negative.code: 
  State-driven network configuration requires installing `kubernetes-nmstate`, and also requires Network Manager running on the cluster nodes. See *OpenShift Virtualization > Kubernetes NMState (Tech Preview)* for additional details.
  
  [id='network-requirements-out-of-band_{context}']
  == Port access for the out-of-band management IP address
  
  The out-of-band management IP address is on a separate network from the node. To ensure that the out-of-band management can communicate with the `baremetal` node during installation, the out-of-band management IP address address must be granted access to the TCP 6180 port.
  