11.2.4.5. Check of the communication to the server specified as a distribution destination

Operation Confirmed Version:
 Citrix Netscaler VPX Version11.0 Build67.12 Standard Edition
Here, we will specify a Web Server as a distribution destination server of communication and check the communication.

Presumed case for sample setting

  • Assume that we want to receive access from Virtual PCs at 192.168.1.200, which is the Virtual Server of the Load Balancer.

  • Also assume that we want to access the Virtual Web Server via the Load Balancer and to display Web pages correctly.

Configuration diagram
Fig8101
Change will be made in the following environment.

Setting Items

Setting value

Virtual PC

192.168.1.103

Load Balancer

192.168.2.11
Virtual Server 192.168.1.200

Distribution destination Web Server (web1)

192.168.2.12

Note

Before executing this procedure, server registration, service registration, and virtual server registration have to be completed in advance.

Operation check result

As a result of access to the Virtual Server IP Address (192.168.1.200), web pages were displayed on the browser of the Virtual PC. And from the access log of the Server side, we could confirm that the server was accessed via the Load Balancer. Therefore we have confirmed that setting and communication check are correctly performed.
Fig6502
Communication records can be checked on the log of the Virtual Web Server.
Fig8103

Note

In this scenario, Source IP NAT is used, and the IP address of the Load Balancer will become the source.

Check of the communication to two servers specified as distribution destinations

Here, we will specify two Web Server as distribution destination servers of communication and check the communication.

Presumed case for sample setting

  • Assume that we want to receive access from Virtual PCs at 192.168.1.200, which is the Virtual Server of the Load Balancer.

  • Also assume that we want to access the Virtual Web Server via the Load Balancer and to display Web pages correctly.

  • We want to confirm that we can correctly access both 192.168.2.12 and 192.168.2.13, that are registered as servers.

Configuration diagram
Fig8201
Change will be made in the following environment.

Setting Items

Setting value

Virtual PC

192.168.1.103

Load Balancer

192.168.2.11
Virtual Server 192.168.1.200

Distribution destination Web Server 1 (web1)

192.168.2.12

Distribution destination Web Server 2 (web2)

192.168.2.13

Operation check result

As a result of access to the Virtual Server IP Address (192.168.1.200), web pages were displayed on the browser of the Virtual PC. And from the access log of the Server side, we could confirm that each server was accessed via the Load Balancer. Therefore we have confirmed that setting and communication check are correctly performed.
    Fig6502
Communication records can be checked on the log of the Virtual Web Server 1.
Fig8203
Communication records can be checked on the log of the Virtual Web Server 2.
Fig8204

Note

In this scenario, Source IP NAT is used, and the IP address of the Load Balancer will become the source.