-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a Citrix NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for Installing NetScaler VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the NetScaler Virtual Appliance by using OpenStack
-
Provisioning the NetScaler Virtual Appliance by using the Virtual Machine Manager
-
Configuring NetScaler Virtual Appliances to Use SR-IOV Network Interface
-
Configuring NetScaler Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the NetScaler Virtual Appliance by using the virsh Program
-
-
Deploying NetScaler VPX Instances on AWS
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
-
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
-
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
-
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Use source IP address of the client when connecting to the server
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
MPX 9700/10500/12500/15500 FIPS appliances
-
Configure FIPS appliances in a high availability setup
-
-
Support for Gemalto SafeNet Network hardware security module
-
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configure FIPS appliances in a high availability setup
You can configure two appliances in a high availability (HA) pair as FIPS appliances. For information about configuring an HA setup, see High availability.
Note: Citrix recommends that you use the configuration utility (GUI) for this procedure. If you use the command line (CLI), make sure that you carefully follow the steps as listed in the procedure. Changing the order of steps or specifying an incorrect input file might cause an inconsistency that requires you to restart the appliance. In addition, if you use the CLI, the
create ssl fipskey
command is not propagated to the secondary node. When you run the command with the same input values for modulus size and exponent on two different FIPS appliances, the keys generated are not identical. Create the FIPS key on one of the nodes and then transfer it to the other node. But if you use the configuration utility to configure FIPS appliances in an HA setup, the FIPS key that you create is automatically transferred to the secondary node. The process of managing and transferring the FIPS keys is known as secure information management (SIM).
Important: On the MPX 9700/10500/12500/15500 FIPS appliances, the HA setup must be completed within six minutes. If the process takes longer than six minutes, the internal timer of the FIPS card expires and the following error message appears:
ERROR: Operation timed out or repeated, please wait for 10 mins and redo the SIM/HA configuration steps.
If this message appears, restart the appliance or wait for 10 minutes, and then repeat the HA setup procedure.
In the following procedure, appliance A is the primary node and appliance B is the secondary node.
Configure FIPS appliances in a high availability setup by using the CLI
-
On appliance A, open an SSH connection to the appliance by using an SSH client, such as PuTTY.
-
Log on to the appliance, using the administrator credentials.
-
Initialize appliance A as the source appliance. At the command prompt, type:
init ssl fipsSIMsource <certFile> <!--NeedCopy-->
Example:
init fipsSIMsource /nsconfig/ssl/nodeA.cert
-
Copy this
<certFile>
file to appliance B, in the /nconfig/ssl folder.Example:
scp /nsconfig/ssl/nodeA.cert nsroot@198.51.100.10:/nsconfig/ssl
-
On appliance B, open an SSH connection to the appliance by using an SSH client, such as PuTTY.
-
Log on to the appliance, using the administrator credentials.
-
Initialize appliance B as the target appliance. At the command prompt, type:
init ssl fipsSIMtarget <certFile> <keyVector> <targetSecret> <!--NeedCopy-->
Example:
init fipsSIMtarget /nsconfig/ssl/nodeA.cert /nsconfig/ssl/nodeB.key /nsconfig/ssl/nodeB.secret
-
Copy this
<targetSecret>
file to appliance A.Example:
scp /nsconfig/ssl/fipslbdal0801b.secret nsroot@198.51.100.20:/nsconfig/ssl
-
On appliance A, enable appliance A as the source appliance. At the command prompt, type:
enable ssl fipsSIMSource <targetSecret> <sourceSecret> <!--NeedCopy-->
Example:
enable fipsSIMsource /nsconfig/ssl/nodeB.secret /nsconfig/ssl/nodeA.secret
-
Copy this
<sourceSecret>
file to appliance B.Example:
scp /nsconfig/ssl/fipslbdal0801b.secret nsroot@198.51.100.10:/nsconfig/ssl
-
On appliance B, enable appliance B as the target appliance. At the command prompt, type:
enable ssl fipsSIMtarget <keyVector> <sourceSecret> <!--NeedCopy-->
Example:
enable fipsSIMtarget /nsconfig/ssl/nodeB.key /nsconfig/ssl/nodeA.secret
-
On appliance A, create a FIPS key, as described in Create a FIPS key.
-
Export the FIPS key to the appliance’s hard disk, as described in Export a FIPS key.
-
Copy the FIPS key to the hard disk of the secondary appliance by using a secure file transfer utility, such as SCP.
-
On appliance B, import the FIPS key from the hard disk into the HSM of the appliance, as described in Import an existing FIPS key.
Configure FIPS appliances in a high availability setup by using the GUI
- On the appliance to be configured as the source appliance, navigate to Traffic Management > SSL > FIPS.
- In the details pane, on the FIPS Info tab, click Enable SIM.
- In the Enable HA Pair for SIM dialog box, go to the Certificate File Name text box. Type the file name, with the path to the location at which the FIPS certificate must be stored on the source appliance.
- In the Key Vector File Name text box, type the file name, with the path to the location at which the FIPS key vector must be stored on the source appliance.
- In the Target Secret File Name text box, type the location for storing the secret data on the target appliance.
- In the Source Secret File Name text box, type the location for storing the secret data on the source appliance.
- Click OK. The FIPS appliances are now configured in HA mode.
- Create a FIPS key, as described in Create a FIPS key. The FIPS key is automatically transferred from the primary to the secondary.
The following diagram summarizes the transfer process.
Figure 1. Transfer the FIPS key-summary
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.