In order to support more complex ADC configurations this template includes the ability to create multiple pools and/or listeners as part of a single deployment.

Important

When creating multiple listeners the protocol and profile configuration will be duplicated. The only exception to this rule is the option to exclude SSL/TLS specific profiles.

2.7.1. Deploy HTTP Service on Multiple TCP Ports

In this lab we will deploy a HTTP Service that listens on TCP/80 and TCP/8080

1. Create a new deployment with the following values:

   Field Name	Value
   Name	Lab2.7
   Template	appsvcs_integration_v2.0.003
   Virtual Server: Address	10.1.20.171
   `Virtual Server: Port <AppSvcsiAp p_presoref.html# preso-pool-port> `__	80
   Pool: Pool Table	Row 1: Index: 0 Monitor(s): 0
   Pool: Members	Row 1: Pool Idx: 0 IP/Node Name: 10.1.10.100 Port: 80 Row 2: Pool Idx: 0 IP/Node Name: 10.1.10.101 Port: 80
   Monitor: Monitor Table	Row 1: Index: 0 Name: /Common/http
   Virtual Server: Additional Listeners	Row 1: Listener: 10.1.20.171:8080 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: default Note Specifying ‘default’ as the destination for the TCP/8080 listener sets the pool index by reading the value of the `Virtual Server: Default Pool Index <AppSvcsiApp_presoref.html#preso-p ool-defaultpoolindex>`__ field. The default value of this field is ‘0’ resulting in the listener sending traffic to the pool with Index 0 in the Pool table.
   Virtual Server: Client-side L4 Protocol Profile	/Common/tcp-wan-optimized
   Virtual Server: Server-side L4 Protocol Profile	/Common/tcp-lan-optimized
   Virtual Server: HTTP Profile	/Common/http

   
   

2. Review the deployed config and deployment log

   • Notice that two listeners were created.

2.7.2. Modify HTTP Service on Multiple TCP Ports

In this lab we will modify the service deployed above and create two pools. We will then route traffic destined to TCP/8080 to the newly created pool.

1. Click iApps -> Application Services -> Lab2.7 -> Reconfigure

2. Modify the following values and click ‘Finished’:

   Field Name	Value
   Pool: Pool Table	Row 1: Index: 0 Monitor(s): 0 Row 2: Index: 1 Monitor(s): 0
   Pool: Members	Row 1: Pool Idx: 0 IP/Node Name: 10.1.10.100 Port: 80 Row 2: Pool Idx: 0 IP/Node Name: 10.1.10.101 Port: 80 Row 3: Pool Idx: 1 IP/Node Name: 10.1.10.102 Port: 80 Row 4: Pool Idx: 1 IP/Node Name: 10.1.10.103 Port: 80
   Monitor: Monitor Table	Row 1: Index: 0 Name: /Common/http
   Virtual Server: Additional Listeners	Row 1: Listener: 10.1.20.171:8080 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: 1

   
   

3. Review the deployed config and deployment log

   • Notice that there are now two pools
   • Notice that the listeners now route traffic to different pools

2.7.3. Deploy Complex IPv4/v6 HTTP/HTTPS Service

In this lab we will deploy a complex service that consists of the following:

• 2 Pools

  • Pool 0: Members listen on TCP/80 (HTTP)
  • Pool 1: Members listen on TCP/443 (HTTPS)

• 5 Listeners

  • 10.1.20.172:443 -> Pool 1
  • 10.1.20.172:80 -> Pool 0
  • 10.1.20.173:80 -> HTTP Redirect
  • 10.1.20.173:443 -> Pool 0
  • 2001:f5f5:1::17.443 -> Pool 1
  • 2001:f5f5:1::17.80 -> HTTP Redirect

All HTTPS traffic will be decrypted and then re-encrypted towards Pool 1.

1. Click iApps -> Application Services -> Lab2.7 -> Reconfigure

2. Modify the following values and click ‘Finished’:

   Field Name	Value
   Virtual Server: Address	10.1.20.172
   `Virtual Server: Port <AppSvcsiAp p_presoref.html# preso-pool-port> `__	443
   Virtual Server: Default Pool Index	1
   Pool: Pool Table	Row 1: Index: 0 Monitor(s): 0 Row 2: Index: 1 Monitor(s): 1
   Pool: Members	Row 1: Pool Idx: 0 IP/Node Name: 10.1.10.100 Port: 80 Row 2: Pool Idx: 0 IP/Node Name: 10.1.10.101 Port: 80 Row 3: Pool Idx: 1 IP/Node Name: 10.1.10.102 Port: 443 Row 4: Pool Idx: 1 IP/Node Name: 10.1.10.103 Port: 443
   Monitor: Monitor Table	Row 1: Index: 0 Name: /Common/http Row 2: Index: 1 Name: /Common/https
   Virtual Server: Additional Listeners	Row 1: Listener: 10.1.20.172:80 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: 0;nossl Row 2: Listener: 10.1.20.173:80 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: redirect Row 3: Listener: 10.1.20.173:443 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: 0;noserverssl Row 4: Listener: 2001:f5f5:1::17.443 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: default Row 5: Listener: 2001:f5f5:1::17.80 `Destination <AppSvcsiApp_presoref.html#pre so-vs-listeners-destination>`__: 1;noclientssl
   Virtual Server: Client-side L4 Protocol Profile	/Common/tcp-wan-optimized
   Virtual Server: Server-side L4 Protocol Profile	/Common/tcp-lan-optimized
   Virtual Server: HTTP Profile	/Common/http
   Virtual Server: Server SSL Profile	/Common/serverssl
   Virtual Server: Client SSL Profile	/Common/clientssl

   
   

3. Review the deployed config and deployment log