anchor.diff:  For more information, see [Understanding backend services](https://cloud.google.com/compute/docs/load-balancing/http/backend-service) in the GCP documentation and the [bosh-google-cpi-release](https://github.com/cloudfoundry-incubator/bosh-google-cpi-release/tree/master/src/bosh-google-cpi) repository on GitHub.
   
   
  -## <a name='sharding-routers-isolation-segment'></a> Sharding Routers for Isolation Segments
  +## <a name='sharding-routers-isolation-segment'></a> Sharding Gorouters for Isolation Segments
   
   <% if vars.platform_code == 'CF' %>
  -To provide security guarantees in addition to the firewall rules described above, an operator can configure sharding of the Gorouter's routing table, resulting in a router dedicated for an isolation segment having knowledge only of routes for apps in the same isolation segment. The flexibility of the configuration also supports deployment of a router that is responsible for multiple isolation segments, or that excludes all isolation segments.
  +To provide security guarantees in addition to the firewall rules described above, an operator can configure sharding of the Gorouter's routing table, resulting in a Gorouter dedicated for an isolation segment having knowledge only of routes for apps in the same isolation segment. The flexibility of the configuration also supports deployment of a Gorouter that is responsible for multiple isolation segments, or that excludes all isolation segments.
   
   ### Bypass Cloud Controller Bridge
   
  -Support for router sharding depends on bypassing the Cloud Controller Bridge (CC Bridge), which is now the default behavior of [cf-deployment](https://github.com/cloudfoundry/cf-deployment). To manually bypass the CC bridge, set `cc.diego.temporary_local_apps: true` in your `cloud_controller_ng`, `cloud_controller_worker`, and `cloud_controller_clock` jobs in your deployment manifest. This enables the Cloud Controller to send app creation requests containing routing isolation segment information directly to the Diego BBS, rather than through the CC Bridge.
  +Support for Gorouter sharding depends on bypassing the Cloud Controller Bridge (CC Bridge), which is now the default behavior of [cf-deployment](https://github.com/cloudfoundry/cf-deployment). To manually bypass the CC bridge, set `cc.diego.temporary_local_apps: true` in your `cloud_controller_ng`, `cloud_controller_worker`, and `cloud_controller_clock` jobs in your deployment manifest. This enables the Cloud Controller to send app creation requests containing routing isolation segment information directly to the Diego BBS, rather than through the CC Bridge.
   
   For more information about the CC Bridge, see [Diego Components and Architecture](../concepts/diego/diego-architecture.html).
   
  -### Configure Routers for Sharding
  +### Configure Gorouters for Sharding
   
   Configuration is achieved using two manifest properties, `routing_table_sharding_mode` and `isolation_segments`.
   
  
positive.code:       <th width="20%">Reason</th>
        </tr>
        <tr> 
        <td><code><%= vars. app_runtime_abbr_lc %>-to-bosh</code></td>
        <td><%= vars. app_runtime_abbr %> isolation segment</td>
        <td><code>tcp</code></td>
        <td>BOSH Director</td>
        <td>BOSH Agent on VMs in the <%= vars. app_runtime_abbr %> Diego Cells to reach BOSH Director</td>
        </tr>
        <tr>
        <td><code>bosh-to-<%= vars. app_runtime_abbr_lc %></code></td>
        <td>BOSH Director</td>
        <td><code>tcp</code></td>
        <td><%= vars. app_runtime_abbr %> Diego Cells</td>
        <td>BOSH director to control VMs in the <%= vars. app_runtime_abbr %> Diego Cells</td>
        </tr>
        <tr>
        <td><code><%= vars. app_runtime_abbr_lc %>-internal</code></td>
        <td><%= vars. app_runtime_abbr %> Diego Cells</td>
        <td><code>tcp</code></td>
        <td><%= vars. app_runtime_abbr %> Diego Cells</td>
        <td>VMs within the <%= vars. app_runtime_abbr %> Diego Cells to reach one another</td>
        </tr>
        <tr>
        <td><code><%= vars. app_runtime_abbr_lc %>-to-is1</code></td>
        <td><%= vars. app_runtime_abbr %> Diego Cells</td>
        <td><code>tcp:1801,8853,9100</code></td>
        <td>Isolation segment</td>
        <td>Diego BBS in <%= vars. app_runtime_abbr %> Diego Cells to reach Diego Cells in isolation segment</td>
        </tr>
        <tr>
        <td><code>is1-to-bosh</code></td>
  
negative.code:     cloud_properties:
        ephemeral_external_ip: true
        <strong>network_name: sample-network</strong>
        <strong>subnetwork_name: sample-subnet-<%= vars.app_runtime_abbr_lc %>-az1</strong>
        tags:
        - <strong>sample-<%= vars.app_runtime_abbr_lc %>-is</strong>
    - range: 10.1.16.0/20
      gateway: 10.1.16.1
      reserved:
  