anchor.diff:      - cf-router-lb-security-group # to allow traffic to the load balancer
   ```
   
  +<p class="note"><strong>Note</strong>:  The load balancer `sample-is1-elb` must be created separately.</p>
  +
   <p class="note"><strong>Note</strong>: If necessary, configure a firewall rule to allow traffic from your load balancer to the Gorouters.</p>
   
   
  
positive.code: 
  <%= image_tag('routing-is.png') %>
  
  Operators who want to prevent all isolation segments and system components from using the same network resources can deploy an additional set of routers for each isolation segment. Use cases include:
  
  * Requests for applications in an isolation segment must not share networking resources with requests for other applications.
  * The Cloud Foundry management plane should only be accessible from a private network. As multiple IaaS load balancers cannot typically share the same pool of backends, such as Cloud Foundry routers, each load balancer requires an additional deployment of routers.
  
negative.code: <tr>
  <td><code>udp</code></td>
  <td><code>8301</code></td>
  <td>Consul**</td>
  <td></td>
  </tr>
  <tr>
  <td><code>udp</code></td>
  <td><code>8302</code></td>
  <td>Consul**</td>
  <td></td>
  </tr>
  <tr>
  <td><code>udp</code></td>
  <td><code>8600</code></td>
  <td>Consul**</td>
  <td></td>
  </tr>
  