anchor.diff:  ---
   ## <a id='manual'></a> Manual Networks
   
  -Manual networking allows you to specify one or more subnets and let the Director choose available IP from one of the subnet ranges. A subnet definition specifies the CIDR range and optionally the gateway and DNS servers. In addition certain IPs can be blacklisted (the Director will not use these IPs) via `reserved` property.
  +Manual networking allows you to specify one or more subnets and let the Director choose available IPs from one of the subnet ranges. A subnet definition specifies the CIDR range and, optionally, the gateway and DNS servers. In addition, certain IPs can be blacklisted (the Director will not use these IPs) via the `reserved` property.
   
   Each manual network attached to a job instance is typically represented as its own NIC in the IaaS layer.
   
   Schema for manual network definition:
   
  -* **name** [String, required]: Name used to reference this network configuration.
  -* **type** [String, required]: Value should be `manual`.
  -* **subnets** [Array, required]: Lists subnets in this network.
  -  * **range** [String, required]: Subnet IP range that includes all IPs from this subnet.
  -  * **gateway** [String, optional]: Subnet gateway IP.
  -  * **dns** [Array, optional]: DNS IP addresses for this subnet.
  -  * **reserved** [Array, optional]: Array of reserved IPs and/or IP ranges. BOSH does not assign IPs from this range to any VM.
  -  * **static** [Array, optional]: Array of static IPs and/or IP ranges. BOSH assigns IPs from this range to jobs requesting static IPs.
  +* **name** [String, required]: Name used to reference this network configuration
  +* **type** [String, required]: Value should be `manual`
  +* **subnets** [Array, required]: Lists subnets in this network
  +  * **range** [String, required]: Subnet IP range that includes all IPs from this subnet
  +  * **gateway** [String, optional]: Subnet gateway IP
  +  * **dns** [Array, optional]: DNS IP addresses for this subnet
  +  * **reserved** [Array, optional]: Array of reserved IPs and/or IP ranges. BOSH does not assign IPs from this range to any VM
  +  * **static** [Array, optional]: Array of static IPs and/or IP ranges. BOSH assigns IPs from this range to jobs requesting static IPs
     * **cloud_properties** [Hash, required]: Describes any IaaS-specific properties for the subnet. May be empty.
   
   Example:
  
positive.code: 
  - Multiple manual networks for each job instance
  - No dynamic networks since vSphere does not manage IP assignments
  - No vip networks since vSphere does not have a elastic/floating IP concept
  
  AWS CPI supports:
  
  
negative.code:     static_ips: [10.10.1.11, 10.10.1.12]
  ```
  
  <p class="note"><strong>Note</strong>: If a deployment job uses static IP reservation, all instances must be given static IPs.</p>
  
  A common problem that you may run into is configuring multiple deployments to use overlapping IP ranges. The Director does not consider an IP to be "used" even if the Director used that IP in a different deployment. There are two possible solutions for this problem: reconfigure one of the deployments to use a different IP range, or use the same IP range but configure each deployment such that reserved IPs exclude the deployment from each other.
  
  <p class="note">Note: While the Director usually selects the next available IP address, this behavior is not guaranteed.</p>
  
  ---
  ## <a id='dynamic'></a> Dynamic Networks
  
  Dynamic networking defers IP selection to the IaaS. For example, AWS assigns a private IP to each instance in the VPC by default. By associating a deployment job to a dynamic network, BOSH will pick up AWS-assigned private IP addresses.
  
  Each dynamic network attached to a job instance is typically represented as its own NIC in the IaaS layer.
  
  