Applies To:

Show Versions Show Versions

Manual Chapter: Customizing Optimization Policies
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

You use optimization policies to specify where and how you want the WAN Optimization Module to optimize traffic. Optimization policies on the initiating side designate the TCP ports on which the WAN Optimization Module applies symmetric data deduplication optimization algorithms and symmetric adaptive compression. On the other side of the WAN, an iSession-terminating virtual server completes the connection.
On the WAN Optimization Module, an optimization policy is a virtual server with an iSession profile and other relevant WAN Optimization profiles associated with it. This virtual server handles application traffic on the initiating (client) side WAN Optimization Module. You need to create a virtual server called isession-virtual on the system as a terminating virtual server; it handles activity on the receiving (server) side WAN Optimization Module. You can configure the system so it automatically creates the isession-virtual virtual server, or you can create it manually. For particular types of traffic (for example, CIFS and FTP), you also need to add an application-specific virtual server on the receiving side.
The optimization policies you create require several profiles that are included with the system. If you use the Optimization Policies screens to create the optimization policies and isession-virtual, the system automatically associates these profiles with the virtual servers it creates, as appropriate.
isession: Required for WAN Optimization to prepare traffic for optimization or to complete the iSession connection on the remote endpoint. Any virtual server that optimizes or received optimized traffic needs to have an iSession profile, either the default provided with the system or one that you create. iSession profiles need to be on the WAN side of the system (that is, on the server side of the initiating system and the client side of the receiving system).
wom-tcp-lan-optimized: Tunes the TCP stack to work well over the LAN. It is required for WAN Optimization on the client side of the virtual server. For more information about TCP tuning, depending on the BIG-IP hardware platform, see Appendix A, TCP Profile Tuning.
wom-tcp-wan-optimized: Tunes the TCP stack to work well over the WAN. It is required for WAN Optimization on the server side of the virtual server. For more information about TCP tuning, depending on the BIG-IP hardware platform, see Appendix A, TCP Profile Tuning.
wom-default-clientssl: A pre-defined SSL profile that allows the system on the remote side of the WAN to receive unencrypted traffic as well as encrypted traffic. It decrypts the encrypted traffic coming from the iSession connection.
wom-default-serverssl: A pre-defined server SSL profile that the system uses to ensure that traffic passes through the system even when remote endpoints are not present and the WAN Optimization Module is not optimizing traffic.
serverssl: A built-in SSL profile that the system uses for the outbound connection on the initiating WAN Optimization Module. Use this profile only if you want to encrypt the traffic going into the iSession connection.
Note: You can use the pre-configured value, serverssl. to get the WAN Optimization Module up and running, but you need to customize this profile for your production environment. For information about customizing SSL profiles, refer to the Configuration Guide for BIG-IP® Local Traffic Manager.
cifs: A built-in profile specifically tailored to optimize CIFS traffic. This profile is specified on both the cifs_optimize_client and cifs_optimize_server virtual servers.
ftp: A built-in profile specifically tailored to optimize FTP traffic. This profile is specified on both the ftp_optimize_client and ftp_optimize_server virtual servers.
mapi: A built-in profile specifically tailored to optimize MAPI traffic. This profile is specified on the mapi_optimize_client virtual server.
Common Application Optimization Policies: Let you automatically create virtual servers to support optimizing HTTP, CIFS, FTP, and MAPI traffic.
Custom Application Optimization Policies: Let you create virtual servers to optimize any type of TCP traffic.
Note: You need to configure optimization policies so that VLAN traffic is restricted to the VLAN where the connections are initiated (for example, the LAN side or internal VLAN). You need to configure the iSession-terminating virtual server so that VLAN traffic is restricted to the VLAN that is connected to the WAN link.
You need to be sure that the traffic that you plan to optimize is not encrypted by an existing application. Encrypted traffic does not optimize well.
The WAN Optimization Module makes it easy to set up common optimization policies for HTTP, CIFS, FTP, and MAPI traffic. You can create the following common optimization policies (that is, virtual servers with optimization profiles):
cifs_optimize_client: optimizes any CIFS traffic on port 445 and associates the cifs and isession profiles. For details on CIFS, see Optimizing CIFS traffic.
cifs_optimize_server: receives CIFS traffic after the iSession connection has been terminated by isession-virtual.
ftp_optimize_client: optimizes any FTP traffic on port 21 and associates the isession profile. It also listens and optimizes any related data connections established for control port (21) sessions.
ftp_optimize_server: receives the FTP traffic after the iSession connection has been terminated by isession-virtual. It also receives any optimized related data connections established for control port (21) sessions.
http_optimize_client: optimizes any HTTP traffic on port 80 and associates the cifs and isession profiles.
mapi_optimize_client: optimizes any MAPI traffic on port 135 and associates the mapi and isession profiles. For details on MAPI, see Optimizing MAPI traffic.
A custom application optimization policy optimizes traffic for applications and service ports in addition to that handled by the common application optimization policies for HTTP, CIFS, FTP, and MAPI traffic. It is a virtual server to which you assign profiles to optimize traffic for that application. For example, you may want to create custom optimization policies (that is, virtual servers) if your network configuration does not use the standard ports for applications.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing the virtual servers that have been created.
3.
Click the Create button.
The Common Application Optimization Policies screen opens listing the preconfigured policies that are available.
4.
Click the Create Custom Policy button.
The New Optimization Policy screen opens.
The settings on the New Optimization Policy screen are similar to a wizard. You answer a series of questions to determine what type of virtual server to create, and then associate the iSession and application profiles, as necessary. As you answer the questions, other questions may hide or appear so that the system can use your answers to define one of the following:
A virtual server that listens for application traffic to optimize over the WAN, which the system creates on the initiating side of the WAN.
An application virtual server at the receiving side of the WAN, which negotiates with the initiating application virtual server to determine the optimizations that take place.
2.
Indicate whether this is an iSession terminating virtual server (Yes/No).
If you select No, inapplicable settings disappear.
4.
Type the service port for the application traffic you are optimizing, or select an application from the list. When you select from the list, the value in the box changes to reflect the associated default port, which you can change.
5.
Indicate whether clients will be connection over a LAN (Yes/No).
If this virtual server initiates application traffic through an iSession connection over the WAN, select Yes.
7.
Specify the VLANs on which the virtual server listens for incoming traffic. Use the Move button (<<) to move the VLANs from the Available list to the Selected list.
8.
For the Profile Settings, select the type of application traffic that this virtual server will handle:
iSession Profile: Specifies the iSession profile to associate with this virtual server. An iSession profile is required for WAN optimization. Select this profile for all virtual servers you create on the initiating side of the WAN and for any tunnel-terminating virtual server you create on the receiving side of the WAN.
CIFS: Specifies that this is for CIFS traffic and associates the CIFS profile with this virtual server. For details, see Optimizing CIFS traffic.
MAPI: Specifies that this is for MAPI traffic and associates the MAPI profile with this virtual server. To optimize MAPI traffic, you also need to create virtual servers for the Microsoft Exchange servers in your network. For details, see Optimizing MAPI traffic.
FTP: Specifies that this is for FTP traffic and associates the FTP profile with this virtual server.
Click Repeat to save this custom application optimization policy and add another custom policy.
Click Finished when you are done adding custom policies.
The system creates a customized optimization policy: it creates a virtual server and automatically associates the profiles necessary for WAN optimization, in addition to the profiles you specified.
To optimize traffic that is not SSL encrypted, you can configure the application virtual server with its common application policy default values. Figure 4.1 shows a pair of systems configured for non-SSL application traffic. The iSession profile applies optimization techniques to the traffic on the iSession connection. The client SSL profile on the terminating side must have the Non-SSL Connections setting enabled, such as the pre-defined wom-default-clientssl profile.
To handle SSL encrypted traffic all the way from the request initiator (client) to the receiver (server), you need to include the following settings when you configure the virtual servers:
Add a server SSL profile to the same optimized application policy (virtual server) to encrypt the traffic over the iSession connection.
Add a third virtual server with the appropriate server SSL profile to re-encrypt the iSession traffic on the other side of the WAN.
Figure 4.2 shows the additional profiles you need to add to the virtual servers to decrypt incoming traffic from the WAN, encrypt it through the iSession connection, de-encrypt it at the receiving side, and then re-encrypt it to send it to its destination.
To complete the tunnel between the local and remote endpoints, the receiving side WAN Optimization Module needs to have an iSession-terminating virtual server. The terminating virtual server receives the iSession connection, handles decryption and re-encryption as configured, and reconstitutes any data that was optimized before the traffic continues on its way to the application server. By default, the system automatically creates an iSession-terminating virtual server, called isession-virtual, when you configure the local endpoint.
The Create iSession Virtual Server setting on the local endpoint screen, set to Yes by default, creates the iSession-terminating virtual server. If you change this setting to No, you need to manually create a terminating virtual server before you can optimize traffic in that direction.
Use the Create Custom Policy button on the Common Application Optimization Policies screen (simpler method). The WAN Optimization Module uses the appropriate default values for many of the settings.
Create a virtual server using Local Traffic Manager (for advanced BIG-IP system administrators). You can access more settings, but you need to understand how to set them appropriately for WAN optimization. You can find in-depth information about creating virtual servers in the Configuration Guide for BIG-IP® Local Traffic ManagerTM.
You create iSession-terminating virtual servers on the receiving (server) side WAN Optimization Module. If file transfers initiate from clients on both sides of the WAN, you need a terminating virtual server on both WAN Optimization Modules. If the endpoint you are configuring only initiates requests and the remote endpoint on the other side of the WAN will never initiate requests, you do not need a terminating virtual server on this WAN Optimization Module.
Important: Do not add additional profiles to the iSession-terminating virtual server. Instead, create another virtual server to match traffic after the iSession connection has been terminated by isession-virtual, and associate any additional profiles with this new virtual server.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing the virtual servers that have been created, if any.
3.
Click the Create button.
The Common Application Optimization Policies screen opens.
4.
Click the Create Custom Policy button.
The New Optimization Policies screen opens. The settings on this screen are similar to a wizard.
For Type, click Host.
For Address, type the IP address of the local endpoint.
d)
Leave the All Ports setting.
e)
Specify the VLANs on which the virtual server listens for incoming traffic (WAN link). Use the Move button (<<) to move the VLANs from the Available list to the Selected list.
g)
Click Finished to create the terminating virtual server.
1.
On the Main tab of the navigation pane, expand Local Traffic and click Virtual Servers.
2.
On the upper right portion of the screen, click the Create button.
The New Virtual Server screen opens.
3.
For the Configuration settings, select Advanced.
In the Name box, type a name for the iSession-terminating virtual server (it is a good idea to include isession-virtual in the name).
Make sure the Destination Type is set to Host.
In the Destination Address box, type the IP address of the local endpoint.
For the Service Port, select *All ports so the virtual server intercepts all traffic destined for this WAN Optimization Module (that is, the one at the end of the tunnel).
For the Protocol Profile (Client), select wom-tcp-wan-optimized.
For the Protocol Profile (Server), select wom-tcp-lan-optimized.
For the SSL Profile (Client), select wom_default_clientssl to manage client-side SSL traffic for incoming connections.
For the VLAN and Tunnel Traffic setting, select All VLANs and Tunnels.
For the Port Translation setting, clear the check box.
For the iSession Profile, select isession or a customized iSession profile that descends from isession, and set the Context to client.
5.
Click Finished to create the iSession-terminating virtual server.
No matter how you create WAN optimization policies, they appear in a list on the same screen, where you can view them, modify them, enable or disable them, and delete them.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing all the application optimization policies (virtual servers) that have been created.
3.
To enable or disable an optimization policy, check the Select box to the left of the policy, and then click Enable or Disable.
a)
In the Name column, click the name of the policy.
The properties screen for that application optimization policy opens and shows that it is a virtual server with profiles and settings that allow it to optimize traffic.
c)
Click Update.
The WAN Optimization Module can perform symmetric adaptive compression on traffic that travels between the local and remote endpoint. Symmetric adaptive compression reduces the size of data that is being transferred over the WAN to save transmission time and improve performance.
You can adjust the compression method (also called codec) on the iSession profile. The following compression methods are available:
Adaptive
This compression method chooses the best algorithm (Deflate, LZO, or Null) for the current traffic, and changes as traffic conditions change. The system selects only from the compression algorithms that are enabled. If it selects Deflate, it also selects an optimum Deflate level.
Deflate
This is a high-quality compression algorithm that is typically slower than the LZO algorithm, unless the system platform supports hardware acceleration. If you enable Deflate and disable Adaptive, you can also select the Deflate Level.
LZO
This is a fast, medium-quality compression algorithm with low latency. the Lempel_Ziv_Oberhumer (LZO) algorithm is best for interactive protocols (such as telnet) or high-bandwidth protocols that compress easily (such as those used for data replication).
Null
This option specifies that no compression occurs between the two systems. You must use Null for connections if you do not want to allow compression. You can also use it for traffic that cannot be compressed, such as streaming media (already compressed), or encrypted protocols (such as HTTPS), but may still benefit from symmetric data deduplication.
By default, all methods are enabled on the iSession profiles on both WAN Optimization Modules on either side of the WAN. The compression method that the systems use depends on the negotiated settings. The common set of enabled options between the two systems determines which method to use.
Important: At least one compression method needs to be the same on both systems (even if it is Null, meaning no compression), otherwise, the two systems cannot establish a tunnel connection.
Symmetric adaptive compression requires that the systems on both sides of the WAN have virtual servers with an associated isession profile that has at least one enabled compression method that is the same for both systems.
Note: If you configured your system as described in Chapter 2, Configuring WAN Optimization, your system is set up for symmetric adaptive compression.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing all the application optimization policies (virtual servers) that have been created.
3.
In the iSession Profile column, click the profile for the optimization policy you want to check.
The iSession profile properties screen opens.
Note: If you want no compression, set Null to Enabled, and disable all other options.
5.
If you disable the Adaptive option and enable the Deflate option, you can also select a level of compression for Deflate Level.
The valid range is from 1 to 9. A higher value causes the CPU to spend more time looking for matches, which may result in better compression. The default level is 1.
6.
Log on to the WAN Optimization Modules on the other side of the WAN to make sure that the corresponding iSession profiles they use have the same compression options enabled on them.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
3.
Click the name of an optimization policy, select the Advanced configuration setting, and note the name of the iSession profile.
4.
In the iSession Profile column, click the profile for the optimization policy you want to check.
The iSession profile properties screen opens.
5.
For the Compression Settings, set Adaptive, Deflate, and LZO to Disabled, and set Null to Enabled.
6.
Log on to the WAN Optimization Modules on the other side of the WAN to make sure that the corresponding iSession profiles that they use have Null set to Enabled, and the other compression options set to Disabled.
Common Internet File System (CIFS) is a remote file access protocol that forms the basis of Microsoft® Windows file sharing. Various CIFS implementations (for example, Samba) are also available on other operating systems such as Linux. CIFS is the protocol most often used for transferring files over the network.
Important: By default, Microsoft®Windows clients do not require SMB signing, except when communicating with their domain controller. If SMB signing settings have been changed, you need to make sure SMB signing is optional on all servers and clients.
The WAN Optimization Module can optimize CIFS traffic, resulting in faster performance in situations such as the following:
Transfer of files that use CIFS protocol: Optimization makes it faster to download and upload files.
Opening Microsoft applications: Optimization makes it faster to open files over the network.
Saving files: Optimization makes it faster to save files over the network.
By default, when you configure the WAN Optimization Module, CIFS traffic is not optimized. Optimizing CIFS traffic on the initiating (client) side involves two main tasks:
Creating CIFS optimization policies, which are virtual servers that identifies the CIFS traffic and have associated profiles that determine how to optimize the traffic. The WAN Optimization Module can create CIFS policies automatically, or you can create them manually using Local Traffic Manager. The CIFS optimization policy listens on port 445.
Creating an iSession virtual server to terminate the tunnel connection on the remote endpoint.
Optimizing CIFS traffic requires optimization policies on the WAN Optimization Modules on both sides of the WAN, One policy is on the initiating side, and the other is on the receiving side.
The easiest way to create CIFS optimization policies is from the Optimization Policies screen. The CIFS optimization policy that the system creates on the initiating side of the WAN is a virtual server called cifs_optimize_client. The system also creates a virtual server on the receiving side of the WAN called cifs_optimize_server.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing all the optimization policies (virtual servers) that have been created. If you see cifs_optimize and cifs_optimize_server on the list, the system already has CIFS optimization policies.
If isession-virtual is not on the list, see Manually creating a terminating virtual server.
Tip: To view or edit the settings of a virtual server on the list, click its name to go to the virtual server screen.
3.
Click the Create button.
The Common Application Optimization Policies screen opens, listing the pre-defined policies that are available.
4.
Click the Select boxes next to cifs_optimize_client and cifs_optimize_server.
5.
For LAN VLANS, in the Available box, select the VLANs on the internal (LAN) side through which the selected optimization policies (virtual servers) receive incoming LAN traffic destined for the WAN. Use the Move button (<<) to move those VLANs to the Selected box.
6.
For WAN VLANS, in the Available box, select the VLAN connected to the WAN link. Use the Move button (<<) to move that VLAN to the Selected box.
7.
Click Apply.
The system creates cifs_optimize_client and cifs_optimize_server virtual servers and associates the appropriate profiles with them.
When both WAN Optimization Modules are configured, the systems can begin to optimize CIFS traffic. You can use the dashboard to see how much bandwidth gain is being saved (using compression and deduplication) and how much latency is reduced as a result of optimizing CIFS traffic.
The Bandwidth Gain window of the dashboard shows the amount of improved throughput as a result of compression and deduplication for CIFS data transfers. The Current Ratio gauge shows the ratio of increased bandwidth gain by comparing the raw data to the optimized data. The graph shows both the raw CIFS data and the optimized CIFS data in bits per second.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Dashboard.
The WAN Optimization screen of the dashboard opens in a separate browser.
2.
In the Bandwidth Gain window, from the bandwidth gain Filters menu, choose CIFS, then select one of the following:
From WAN:CIFS to show the gain in bandwidth for CIFS traffic coming in from the WAN.
This is where you view bandwidth gain for CIFS traffic on the initiating (client) side for files coming from the other side of the WAN.
This is where you view bandwidth gain for CIFS traffic on the receiving (server) side for files transferring to the other side of the WAN.
To WAN to show the gain in bandwidth for CIFS traffic going out to the WAN.
This is where you view CIFS bandwidth gain on the initiating (client) side for files transferring to the other side of the WAN.
This is where you view CIFS bandwidth gain on the receiving (server) side for files coming from the other side of the WAN.
This is where you view the percentage of read requests and write requests that were faster because of CIFS optimization techniques.
MAPI (Messaging Application Program Interface) is the email protocol that Microsoft® Exchange Server and Outlook® clients use to exchange messages. It enables applications to send and receive email (with document attachments) and calendar appointments. Because companies transfer so much information through email, optimizing MAPI traffic can lead to an increase in application performance and user productivity.
The WAN Optimization Module can optimize MAPI traffic to reduce the amount of bandwidth required to transfer the data across the WAN for any application that uses MAPI. You can configure MAPI to optimize traffic on any WAN Optimization Module, but it is most important on the client side, the side that initiates the requests to the Exchange Server.
Disabling encryption for clients (on the Microsoft Exchange settings, Security tab, clear the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box) because encrypted traffic cannot be optimized.
Creating virtual servers for all Exchange Servers by configuring the WAN Optimization Module to automatically discover them, or by creating them manually using Local Traffic Manager.
Creating a MAPI optimization application policy, which is a virtual server that identifies the MAPI traffic and has associated profiles that determine how to optimize the traffic. The WAN Optimization Module can create a MAPI policy automatically, or you can create it manually using Local Traffic Manager. The MAPI optimization policy listens on port 135, the port on which the Endpoint Mapper typically operates. (The Endpoint Mapper service maps services to their currently assigned ports.)
The receiving (server) side WAN Optimization Module needs to have an iSession virtual server that completes the connection with the initiating or client side.
On the initiating (client) side WAN Optimization Module, you need to create a MAPI optimization policy. The easiest way to do this is from the Optimization Policies screen. The MAPI optimization policy that the system creates is a virtual server called mapi_optimize_client. To create a MAPI optimization policy
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing all the optimization policies (virtual servers) that have been created.
Tip: To view or edit the settings of a virtual server on the list, click its name to go to the virtual server screen.
3.
Click the Create button.
The Common Application Optimization Policies screen opens, listing the pre-defined policies that are available.
4.
Click the Select box next to mapi_optimize_client.
5.
For LAN VLANS, in the Available box, select the VLANs on the internal (LAN) side through which the selected optimization policies (virtual servers) receive incoming LAN traffic destined for the WAN. Use the Move button (<<) to move those VLANs to the Selected box.
6.
For WAN VLANS, in the Available box, select the VLAN connected to the WAN link. Use the Move button (<<) to move that VLAN to the Selected box.
7.
Click Apply.
The system creates the mapi_optimize_client virtual server and associates the appropriate profiles with it.
After you create the mapi_optimize_client virtual server, you also need to create a virtual server for each Exchange server, either automatically (see Enabling automatic discovery of Exchange Servers) or manually (see Manually creating virtual servers for Exchange Servers).
For MAPI optimization to work, the WAN Optimization Module on the other side of the WAN (the receiving side) needs to have an isession-virtual virtual server. By default, the WAN Optimization Module automatically creates an iSession virtual server that accepts optimization traffic when you configure the local endpoint.
For MAPI optimization, you need to have a virtual server for each Exchange Server so that the system can locate the MAPI traffic (by using the Exchange Server IP address) and can then optimize it. You can modify the MAPI profile to automatically discover the Exchange Servers and create a virtual server for each one. Then, if the company adds new Exchange Servers to the network or the IP addresses of existing ones change, the WAN Optimization Module discovers the changes and creates new MAPI virtual servers for the new and moved Exchange Servers.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Configuration.
2.
On the menu bar, click Optimization Policies.
The Optimization Policies screen opens, listing all the optimization policies (virtual servers) that have been created.
3.
Click mapi_optimize_client to open the properties screen for the mapi_optimize_client virtual server.
If mapi_optimize_client is not on the list, see Creating a MAPI optimization policy.
5.
On the Main tab of the navigation pane, expand Local Traffic, click Profiles, point to Services, and click MAPI.
7.
For Discover Exchange Servers, select Enabled.
8.
Click Update to save the change.
If you do not want the WAN Optimization to automatically create virtual servers for Exchange Servers, you can create them using Local Traffic Manager. You can find details about creating virtual servers in the Configuration Guide for BIG-IP® Local Traffic Manager.
The following procedure describes the settings and profiles needed if you are going to manually configure virtual servers for Exchange Servers in order to optimize MAPI traffic. You create virtual servers for Exchange Servers on the initiating (client) side WAN Optimization Module.
Note: Skip this procedure if you changed the Discover Exchange Servers setting in the mapi profile to Enabled.
2.
On the Main tab of the navigation pane, expand Local Traffic and click Virtual Servers.
3.
Click the Create button.
The New Virtual Server screen opens.
4.
For the Configuration setting, select Advanced.
a)
In the Destination Address box, type the address of the Microsoft Exchange Server.
b)
For the Service Port, select * All Ports so the virtual server intercepts all traffic headed for the destination address.
c)
For the Protocol Profile (Client), select wom-tcp-lan-optimized.
d)
For the Protocol Profile (Server), select wom-tcp-wan-optimized.
e)
For the SSL Profile (Server), select wom-default-serverssl.
f)
If you specified a Host Address for the Destination, click to clear the Address Translation setting.
g)
For the iSession Profile, select isession or a customized iSession profile that descends from isession, and set the Context to server.
h)
For the MAPI profile, select mapi.
Click Repeat to save this virtual server and add more virtual servers for other Exchange Servers.
Click Finished if you are done adding virtual servers.
After you begin to optimize MAPI traffic, you can use the dashboard to see how much bandwidth is being saved as a result of optimizing MAPI traffic.
1.
On the Main tab of the navigation pane, expand WAN Optimization and click Dashboard.
The WAN Optimization screen of the dashboard opens in a separate browser window.
2.
From WAN to show the gain in bandwidth for MAPI traffic coming in from the WAN.
To WAN to show the gain in bandwidth for MAPI traffic going out to the WAN.
To optimize HTTPS traffic, you need to perform some additional configuration on the initiating and receiving WAN Optimization Modules. The following points provide an overview of the procedure.
Initiating WAN Optimization Module
Configure the initiating WAN Optimization Module as described in Chapter 2, Configuring WAN Optimization. Here are additional steps you need to take:
2.
Include https in the name of the optimization policy (for example, https_optimize_client).
4.
Configure the SSL Profile (Client) to use the profile appropriate for decrypting SSL traffic.
6.
Configure the SSL Profile (Server) to use a profile appropriate for re-encypting SSL traffic.
Receiving WAN Optimization Module
Configure the receiving WAN Optimization Module as described in Chapter 2, Configuring WAN Optimization. Here are additional steps you need to take:
1.
Create a virtual server to re-encrypt the HTTPS traffic on its way to the server (for details, see Configuring Virtual Servers, in the Configuration Guide for BIG-IP® Local Traffic Manager).
2.
On the re-encrypt virtual server, configure the SSL Profile (Server) setting to use the default serverssl profile (or one you created).
3.
On the Local Endpoint screen, include the IP address of the re-encrypt virtual server as an advertised route.
The iSession profile tells the system how you want to optimize traffic. You associate the iSession profile with any application optimization policy (virtual server) on the initiating (client) side of the WAN and any iSession-terminating virtual server. On the iSession profile, you can enable or disable several settings:
The isession profile itself
The WAN Optimization Module includes an isession profile, by default. In certain circumstances, you may want to create a custom iSession profile to change the way it handles traffic. We recommend not changing the default isession profile and creating a custom profile in this case.
1.
On the Main tab of the navigation pane, expand Local Traffic and click Profiles, then Services and then iSession.
The iSession Profiles screen opens.
2.
Click the Create button.
The New Profile screen opens.
3.
In the Name box, type a name for the iSession profile.
4.
Leave the Mode set to Enabled.
5.
For the Deduplication setting, leave the default of Enabled if you want to use this feature.
The iSession profile on the system on the other side of the tunnel must also have this setting Enabled. For additional details, see Configuring symmetric data deduplication.
6.
For the Reuse Connection setting, select either:
Enabled: Specifies that the system saves and reuses the tunnel between the local and remote endpoints for multiple connections. This is the default setting.
Disabled: Specifies that the system creates a new tunnel for each connection.
Note: In the case of an abnormal TCP connection reset, the iSession tunnel connection will be terminated and reset. While transparent to the user, this action may appear in diagnostics.
7.
For the Target Virtual setting, set it to none on the initiating WAN Optimization Module. On the receiving WAN Optimization Module, if you want the isession-virtual (or other terminating virtual server) to target another virtual server before going to the server, select the option for the matching criteria that the system uses:
none: Specifies that the system should send the iSession traffic directly to the server.
host match no isession: Specifies that the system matches only host virtual servers with no iSession profile.
host match all: Specifies that the system selects the closest match from all the host virtual servers.
match all: Specifies that the system selects the closest match from all the virtual servers. This is the default setting.
8.
For the Port Transparency setting, select either:
Enabled: Specifies that the destination port of the traffic is preserved over the WAN. This is the default setting.
Disabled: Specifies that the destination port is not preserved. The system sends traffic to the tunnel port.
9.
For the Compression Settings, enable at least one of the options.
At least one option must match an option on the iSession profile on the system on the other side of the tunnel. For details, see Configuring symmetric adaptive compression.
Click Repeat to save this iSession profile and add another iSession profile.
Click Finished if you are done adding iSession profiles.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)