End-of-Life (EoL)

Configure the Citrix NetScaler VPX

This section shows you how to set up the NetScaler VPX load balancer for this use case. These instructions are included solely for the purpose of taking you through the implementation in this use case. For set up and conceptual information on the NetScaler VPX, refer to the Citrix documentation.
  1. Configure the Virtual IP and the Subnet IP on the NetScaler VPX.
    1. On the NetScaler management console, select
      Configuration
      System
      Network
      IPs
      .
    2. Add
      the Virtual IP and the Subnet IP addresses.
      AWS-use-case-Internet-facing-apps_VPX_IPs.png
  2. Add static routes to direct traffic to the web servers. Make sure to add routes for the web servers in both Availability Zones.
    Add
    the routes in
    Configuration
    System
    Network
    Routes
    . In this example, we add routes to direct traffic from web1 and web2 through eth 1/1 on AZ1-FW1 and traffic from web 3 and web4 to eth1/1 on AZ1-FW2.
    AWS-use-case-Internet-facing-apps_VPX_Routes.png
  3. Create a service for each web server.
    Add the web services in
    Configuration
    Traffic Management
    Load Balancing
    Services
    .
    AWS-use-case-Internet-facing-apps_VPX_Services.png
  4. Configure the virtual server. The Virtual server IP address is the only IP address that is exposed to users who connect to the web server from the internet.
    1. Add
      a Virtual Server IP address in
      Configuration
      Traffic Management
      Load Balancing
      Virtual Servers
      .
      AWS-use-case-Internet-facing-apps_VPX_VserverIP.png
    2. Bind the web services you created in step 4 to this virtual server.
    3. Edit the settings for the virtual server to enable IP address persistence. IP address persistence is required for the application to authenticate properly. Based on your preference, select
      Cookie-based
      or
      Source-IP-based
      persistence.
  5. Test your configuration.
    Verify that you can log in to the web server.
    The WordPress application in this use case would be accessible at
    http://ignite-aws-demo.com/wordpress
    .

Recommended For You