Manual Chapter : Setting Up an iSession Connection Using the Quick Start Screen

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.0.1, 13.0.0, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
Manual Chapter

Setting Up an iSession Connection Using the Quick Start Screen

Overview: Setting up an iSession connection using the Quick Start screen

The Quick Start screen for WAN acceleration provides the settings you need to configure an iSession™ connection on one side of the WAN. To complete the iSession connection, you must use the Quick Start screen on the BIG-IP system on the other side of the WAN.

The Quick Start screen is for the initial BIG-IP symmetric acceleration setup. To change the settings for any iSession acceleration objects after you have completed the initial configuration on the Quick Start screen, use the screen that pertains to that object. For example, to change the settings for the local endpoint, use the Local Endpoint screen.

Setting up an iSession connection using the Quick Start screen

You cannot view the Quick Start screen until you have defined at least one VLAN and at least one self IP on a configured BIG-IP® system that is licensed and provisioned for acceleration.
Use the Quick Start screen to quickly set up the iSession™ endpoints on a BIG-IP system. To optimize WAN traffic, you must configure the iSession endpoints on the BIG-IP systems on both sides of the WAN.
  1. Log in to the BIG-IP system that you want to configure.
    The default login value for both user name and password is admin.
  2. On the Main tab, click Acceleration > Quick Start > Symmetric Properties .
  3. In the WAN Self IP Address field, type the local endpoint IP address, if it is not already displayed.
    This IP address must be in the same subnet as a self IP address on the BIG-IP system, and to make sure that dynamic discovery properly detects this endpoint, the IP address must be the same as a self IP address on the BIG-IP system.
  4. Verify that the Discovery setting is set to Enabled.
    If you disable the Discovery setting, or discovery fails, you must manually configure any remote endpoints and advertised routes.
  5. Specify the VLANs on which the virtual servers on this system receive incoming traffic.
    Option Description
    LAN VLANs Select the VLANs that receive incoming LAN traffic destined for the WAN.
    WAN VLANs Select the VLANs that receive traffic from the WAN through an iSession™ connection.
  6. In the Authentication area, for the Outbound iSession to WAN setting, select the SSL profile to use for all encrypted outbound iSession connections.
    To get WAN optimization up and running, you can use the default selection serverssl, but you need to customize this profile for your production environment.
  7. For the Inbound iSession from WAN setting, select the SSL profile to use on the incoming iSession connection.
    To get WAN optimization up and running, you can use the default selection wom-default-clientssl.
    Note: If you configure the iSession connection to not always encrypt the traffic between the endpoints, this profile must be a client SSL profile for which the Non-SSL Connections setting is enabled, such as wom-default-clientssl.
  8. In the IP Encapsulation area, from the IP Encapsulation Type list, select the encapsulation type, if any, for outbound iSession traffic.
    1. If you select FEC, select a FEC profile from the FEC Profile list that appears, or retain the default, default-ipsec-policy-isession.
    2. If you select IPsec, select an IPsec policy from the IPSEC Policy list that appears, or retain the default, default-ipsec-policy-isession.
    3. If you select IPIP, the system uses the IP over IP tunneling protocol, and no additional encapsulation setting is necessary.
    4. If you select GRE, select a GRE profile from the GRE Profile list that appears, or retain the default, gre.
  9. Click Apply.
To complete the setup, repeat this task on the BIG-IP system on the other side of the WAN.