anchor.diff:  1. Modify the `reservable_ports`:
   
       <pre class="terminal">
  -    $ cf curl /routing/v1/router_groups/f7392031-a488-4890-8835-c4a038a3bded -X PUT -d '{"reservable_ports":"1024-1199"}'
  +    $ cf curl \
  +    -X PUT -d '{"reservable_ports":"1024-1199"}' \
  +    /routing/v1/router_groups/f7392031-a488-4890-8835-c4a038a3bded
       </pre>
  
positive.code: cf create-space-quota QUOTA --reserved-route-ports X
  ```
  
  
  ## <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
  
  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.
  
  
negative.code: 1. <%= partial vars.tcp_port %>
  
  
  <% if vars.platform_code == "PCF" %>
  ### <a id="config-tcp"></a> Configure TCP Routing
  
  TCP routing is disabled by default.
  
  To enable TCP routing:
  
  1. Navigate to the <%= vars.ops_manager_full %> Installation Dashboard.
  
  1. Click the <%= vars.app_runtime_abbr %> tile.
  
  1. Select **Networking**.
  
  1. Under **TCP routing**, select **Enable**.
  
  1. For **TCP router IPs**, enter the IP addresses to assign to the TCP routers as multiple values as a comma-separated list or as a range. For example, `10.254.0.1, 10.254.0.2` or `10.254.0.1-10.254.0.2`. These addresses must be within your subnet CIDR block. The addresses are the same IP addresses with which you configured your load balancer in the [Pre-Deployment Steps](#pre-deploy) section of _Enable TCP Routing_, unless you configured DNS to resolve the TCP domain name directly to an IP for the TCP router.
  
  1. For **TCP routing ports**, enter one or more ports to which the load balancer forwards requests. To support multiple TCP routes, <%= vars.company_name %> recommends allocating multiple ports. Do one of the following:
      * To allocate a single port or range of ports, enter a single port or a range of ports.
        <p class="note"><strong>Note:</strong> If you configured AWS for <%= vars.app_runtime_abbr %> manually, enter <code>1024-1123</code> which corresponds to the rules you created for <code><%= vars.platform_name_lc %>-tcp-elb</code>.</p>
      * To allocate a list of ports:
        1. Enter a single port in the **TCP routing ports** field.
        1. After deploying <%= vars.app_runtime_abbr %>, follow the procedure in [Router Groups: Modify TCP port reservations](#modify-ports) to add TCP routing ports using the cf CLI.
  
  1. (Optional) For **TCP request timeout**, modify the default value of `300` seconds. This field determines when the TCP router closes idle connections from clients to apps that use TCP routes. You may want to increase this value to enable developers to push apps that require long-running idle connections with clients.
  
  1. For **AWS**, **Azure**, or **GCP** <%= vars.platform_name %> deployments, add the name of your load balancer to the **TCP Router** field in the **Resource Config** pane of the <%= vars.app_runtime_abbr %> tile. For more information, see [Configuring Load Balancing for <%= vars.app_runtime_abbr %>](configure-lb.html).
  
  <% end %>
  
  ### <a id="post-deploy"></a> Post-Deployment Steps
  
  In the following procedures, you use the Cloud Foundry Command Line Interface (cf CLI) to add the TCP shared domain and configure org quotas to grant developers the ability to create TCP routes. This requires an admin user account.
  
  For more information about the cf CLI, see [Using the Cloud Foundry Command Line Interface (cf CLI)](../cf-cli/index.html).
  
  #### <a id="configure-domain"></a> Configure <%= vars.app_runtime_abbr %> with Your TCP Domain
  
  After deployment, you must configure <%= vars.app_runtime_abbr %> with the domain that you configured in the pre-deployment step above so developers can create TCP routes from it.
  
  