anchor.diff:  cf create-space-quota QUOTA --reserved-route-ports X
   ```
   
  +<% if vars.platform_code == "PCF" %>
  +## <a id="disable-tcp"></a> Disable TCP Routing
   
  -## <a id="create-tcp-route"></a> Create a TCP Route
  +To disable TCP routing:
  +
  +1. Navigate to the <%= vars.ops_manager %> Installation Dashboard.
  +
  +1. Click the <%= vars.app_runtime_abbr %> tile.
  +
  +1. Select **Networking**.
  +
  +1. Under **TCP routing**, select **Disable**.
  +
  +1. Manually remove the TCP routing domain.
  +
  +<% end %>
  +
  +## <a id="administering-tcp-routing"></a> Further TCP Routing Administration
  +### <a id="create-tcp-route"></a> Create a TCP Route
   
   For information about creating a TCP Route, see the [Create a TCP Route with a Port](../devguide/deploy-apps/routes-domains.html#create-route-with-port) section of the _Configuring Routes and Domains_ topic.
   
  -
  -## <a id="router-groups"></a> Router Groups
  -
  -[Post-Deployment Steps](#configure-domain) describes that in order to create a domain from which to create TCP routes, it must be associated with the TCP router group. A router group is a cluster of identically configured routers. Router groups are a mechanism to support reservation of the same port for multiple TCP routes, thus increasing the capacity for TCP routes. However, only one router group is currently supported. [Pre-Deployment Steps](#pre-deploy) describes how an admin user can configure the port range available for TCP routes in preparation for deployment.
  -
  -### <a id="modify-ports"></a> Modify Your TCP ports
  +### <a id="modify-ports"></a> Router Groups: Modify TCP port reservations
   
   After deployment, you can modify the range of ports available for TCP routes using `cf curl` commands, as demonstrated with the commands below. These commands require an admin user with the `routing.router_groups.read` and `routing.router_groups.write` scopes.
   
  
positive.code: ---
  title: Enabling TCP Routing
  owner: CF for VMs Networking
  ---
  
  This topic describes enabling TCP Routing for your <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>) deployment. This feature enables developers to run apps that serve requests on non-HTTP TCP protocols. You can use TCP routing to comply with regulatory requirements that require your org to terminate the TLS as close to your apps as possible so that packets are not decrypted before reaching the app level.
  
  ## <a id="ports"></a> Route Ports
  
  The diagram below shows the layers of network address translation that occur in <%= vars.app_runtime_abbr %> in support of TCP Routing. The descriptions step through an example work flow that covers route ports, back end ports, and app ports.
  
  
negative.code: - By default, the Diego Cell only routes requests to port `8080`, the app port, on the container internal interface. The app port is the port on which apps must listen. Developers can use the Cloud Controller API to update the ports an app can receive requests on. For more information, see [Configuring Apps to Listen on Custom Ports (Beta)](../devguide/custom-ports.html).
  
  
  ## <a id="enable-tcp-routing"></a> Enable TCP Routing
  ### <a id="pre-deploy"></a> Pre-Deployment Steps
  
  <%= vars.mutual_tls_tcp %>
  
  