anchor.diff:  </code>
   </pre>
   
  +<% else %>
  +<%= vars.pcf_networking_is1 %>
  +<% end %>
  +
   ##<a id='config-instance-group'></a> Step 3: Configure Additional Routers
   
  +<% if vars.product_name == 'CF' %>
   You must edit the BOSH deployment manifest to include an instance group for each set of routers.
   
   The sample [BOSH v2 manifest](https://bosh.io/docs/manifest-v2.html) snippet below includes additional instance groups for the routers of each isolation segment, each associated with different BOSH AZs. As a result, a router instances will be configured with IP addresses from different subnets. 
  
positive.code:     vm_extensions:
      - cf-router-network-properties
    ```
    
  <% else %>
  <%= vars.config_networking_is %>
  <% end %>
  
  ## <a id='config-dns-lb'></a>Step 5: Configure DNS and Load Balancers
  
negative.code: </code>
  </pre>
  
  <% else %>
  <%= vars.pcf_networking_is2 %>
  <% end %>
  
  ## <a id='add-routers'></a>Step 4: Add Routers to Load Balancer
  
  <% if vars.product_name == 'CF' %>
  For some IaaS (e.g. AWS, GCP), the BOSH Cloud Config and deployment manifest can be used to instruct BOSH to add routers to the IaaS load balancers automatically. For others, operators must assign static IPs to the routers in the manifest and assign these IPs to the load balancers out of band.
  
  For deployments to GCP, associate the router instance groups with load balancers by first configuring a backend service which describes the load balancer rules. Next, define the backend service in the Cloud Config with a `vm_extension`. Finally, associate the router instance groups with the `vm_extention`. In the following example, the `vm_extension` called `cf-router-network-properties` is defined in the cloud config with a GCP backend service.
  