FAQ(ECL2.0)
Load Balancer - FAQ
- All(66)
-
How to use SSL Offload function.ECL2.0, Load Balancer
Please refer to following URL to use SSL Offload function.
Linking of an intermediate certificate and a server certificate
How to use SSL as a protocol for a Virtual Server
How to confirm a Virtual Server that uses a server certificate
How to delete a server certificate
How to specify the encryption scheme of SSL communication (TLS1.2-ECDHE-RSA-AES-128-SHA256)
How to specify the encryption scheme of SSL communication (TLS1.2-AES-256-SHA256)
How to specify the encryption scheme of SSL communication (TLS1.2-AES-128-SHA256)
How to specify the encryption scheme of SSL communication (TLS1.2-DHE-RSA-AES-256-SHA256)
How to specify the encryption scheme of SSL communication (TLS1.2-DHE-RSA-AES-128-SHA256)
-
When SSL is installed on the load balancer, is SSL communication between the Internet side and the load balancer possible?ECL2.0, Load Balancer
Yes, SSL communication is possible.
Please also refer to the configuration example below.10.3.2. Firewall / load balancer configuration example on WEB site publication (one arm)
-
Can I ping unlimitedly at the NetScaler VPX portal?ECL2.0, Load Balancer
If you do not specify the count value in the portal, the ping execute three times. If you set the count value to a very large value, you can ping in virtually unlimited state.
In the CLI you can run unlimited without specifying arguments.
-
Can I browse the certificate (CSR) created by the load balancer?ECL2.0, Load Balancer
Regarding the certificate placed on the load balancer (NetScaler VPX), it is a service specification that can not confirm content/delete/download.
SSL communication can be realized even if you import the certificate created on the external server to the load balancer (NetScaler VPX). Even in this case, you can not only check the contents of the certificate placed on the load balancer (NetScaler VPX) but also delete/download it. So you need to save it in the local environment.
-
What is the difference between versions?ECL2.0, Load Balancer
In the load balancer (NetScaler VPX), the provided information of the version is described in service manual.
-
Why HTTPS communication can not be used up to the bandwidth indicated in plan name?ECL2.0, Load Balancer
SSL communication and HTTPS compressed communication have different restrictions from the plan name display band. Please refer to Service Descriptions .
-
How to sync the configuration when VRRP redundancy?ECL2.0, Load Balancer
There is no way to sync configuration in relation to the VRRP function in NetScaler.
It is possible to synchronize with the following two methods.
- Submit the same configuration on the first and second on the GUI
- Copy the configuration via the CLIa― In the GUI with the first and second Submitting the same configuration
(1) Log in to the copy source LB [NetScaler VPX portal GUI screen] and extract the settings you want to copy from
Configuration > System > Diagnostics > Running Configuration,2) Log in to the copy destination LB [NetScaler VPX portal GUI screen] and paste it with
Configuration > System > Diagnostics > Command line interface.*After pasting, NetScaler VPX Portal GUI screen: Save the Config by pressing the overwrite button on the upper right.
a― Copy the configuration via the CLI
* Since it is now possible to connect by SSH from VPX11.0-67.12, the CLI command can be used easily. -
How to download the MIB file.ECL2.0, Load Balancer
Please login to "Citrix NetScaler VPX" page.
Click "Downloads" tab upper right corner then you can download the file. -
The error message "Error in retriving Remote File Dir. Not authorized" is displaied in the Authorization of Licence field after login the NetScaler.ECL2.0, Load Balancer
Please go ahead to click the "Continue" button to skip the authentication of the License.
In detail, please visit the tutorial. -
Do Load Balancers have the function of "resend the request from client"?ECL2.0, Load Balancer
Load Balancers reactively resend the request when the client or server request Load Balancers do not proactively resend the request on them own.