anchor.diff:  //
   // * installing/installing_bare_metal/installing-bare-metal.adoc
   // * installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc
  -// * installing_bare_metal/installing-bare-metal-network-customizations.adoc
  +// * installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc
   
   [id="installation-user-infra-machines-static-network_{context}"]
  -= Configure advanced networking
  -
  -If you install {op-system-first} from an ISO image, you can add kernel arguments
  -when you boot that image to configure the node's networking.
  -The following table describes and illustrates how to use those kernel arguments.
  -
  -.Configure advanced networking
  += Advanced {op-system} installation reference
  +
  +This section illustrates the networking configuration and other advanced options that allow you to modify the {op-system-first} bare metal install process. The following tables describe the kernel arguments and command-line options you can use with:
  +
  +* The {op-system} live installer boot prompt by using routing and bonding.
  +
  +* The {op-system} live installer by using `core.inst` for ISO or PXE installs.
  +
  +* The `coreos-installer` command for ISO installs.
  +
  +[discrete]
  +== Routing and bonding options at {op-system} boot prompt
  +
  +If you install {op-system} from an ISO image, you can add kernel arguments manually when you boot that image to configure the node's networking. If no networking arguments are used, the installation defaults to using DHCP.
  +
  +[IMPORTANT]
  +====
  +When adding networking arguments, you must also add the `rd.neednet=1` kernel argument.
  +====
  +
  +The following table describes how to use `ip=`, `nameserver=`, and `bond=` kernel arguments for live ISO installs.
  +
  +.Routing and bonding options for ISO
   [source,adoc]
   |===
   |Description |Examples
   
  -a|To configure an IP address, either use DHCP (`ip=dhcp`) or set an individual
  -static IP address (`ip=<host_ip>`). Then identify the DNS server IP address (`nameserver=<dns_ip>`) on each node. This example sets: +
  +a|To configure an IP address, either use DHCP (`ip=dhcp`) or set an individual static IP address (`ip=<host_ip>`). Then identify the DNS server IP address (`nameserver=<dns_ip>`) on each node. This example sets: +
   
   * The node's IP address to `10.10.10.2` +
   * The gateway address to `10.10.10.254` +
  
positive.code: bond=bond0:em1,em2:mode=active-backup
  ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:bond0:none
  ----
  |===
  
negative.code: nameserver=4.4.4.41
  ----
  
  a|Specify multiple network interfaces by specifying multiple `ip=` entries.
  
  a|
  ----
  ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp1s0:none
  ip=10.10.10.3::10.10.10.254:255.255.255.0:core0.example.com:enp2s0:none
  ----
  
  a|You can combine DHCP and static IP configurations on systems with multiple network interfaces.
  
  a|
  ----
  ip=enp1s0:dhcp
  ip=10.10.10.2::10.10.10.254:255.255.255.0:core0.example.com:enp2s0:none
  ----
  
  a|You can provide multiple DNS servers by adding a `nameserver=` entry for each server.
  
  a|
  ----
  nameserver=1.1.1.1
  nameserver=8.8.8.8
  ----
  
  a|Optional: Bonding multiple network interfaces to a single interface is supported using the `bond=` option. In these two examples:
  
  * The syntax for configuring a bonded interface is: `bond=name[:network_interfaces][:options]`
  * _name_ is the bonding device name (`bond0`), _network_interfaces_
  represents a comma-separated list of physical (ethernet) interfaces (`em1,em2`),
  and _options_ is a comma-separated list of bonding options. Enter `modinfo bonding` to see available options.
  * When you
  create a bonded interface using `bond=`, you must specify how the IP address
  is assigned and other
  information for the bonded interface.
  
  a|
  To configure the bonded interface to use DHCP, set the bond's IP address
  to `dhcp`. For example:
  