Alteon Application Switch Operating System Application Guide
Virtual Private Network Load Balancing
704 Document ID: RDWR-ALOS-V2900_AG1302
3. Enter the policy server IP address: 192.168.10.120. You have the option of adding a nickname.
4. Launch a browser (such as Netscape or Internet Explorer) and go to http://30.0.0.100.
5. Enter vpnuser for user name and alteon for the password.
A message displays verifying that you were authenticated.
6. Browse to the Web site.
If there are other services running on other servers in the internal network, you should reach
those services. All traffic traveling over the VPN is decrypted at the VPN device. You can verify
which VPN device is being used by looking at the Log Viewer. You should also see the client
authentication as well as the decrypted traffic.
7. To verify that the FWLB and hash metric is working correctly on the dirty-side Alteons (that is,
hashed on client IP address/destination IP address), do one of the following:
— Configure your current client with an IP address one higher (or lower) in the last octet, and
try to re-establish the VPN connection.
— Add another PC on the dirty side and connect to it.
Note: When many clients are coming from behind a VPN gateway (for example, not using the
SecuRemote clients but using a VPN 1 Gateway or other compatible VPN Gateway), you do not see
load balancing across those clients. Each SecuRemote client is treated differently, but each VPN 1
Gateway is treated as one client each (that is, one Client IP address). VPN Device 1 and VPN Device
2 belong to one cluster IP.
To Next Page
Loading...
Need help?
General