Getting Started with Citrix ADC
Configuring a FIPS Appliance for the First Time
Deploy a Citrix ADC VPX instance
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
Configure a high-availability setup with multiple IP addresses and NICs
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure address pools (IIP) for a Citrix Gateway appliance
Upgrade and downgrade a Citrix ADC appliance
年代olutions for Telecom Service Providers
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
Authentication, authorization, and auditing application traffic
Configuring authentication, authorization, and auditing policies
Configuring Authentication, authorization, and auditing with commonly used protocols
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
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
Retrieve location details from user IP address using geolocation database
Use source IP address of the client when connecting to the server
Use client source IP address for backend communication in a v4-v6 load balancing configuration
年代et 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 12: Configure Citrix Virtual Desktops for load balancing
Use case 13: Configure Citrix Virtual Apps for load balancing
-
-
-
-
-
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 Citrix ADC 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 a FIPS appliance for the first time
Notes
- FIPS FAQ can be found here:FIPS FAQ.
- VPX FIPS configuration can be found here:Citrix ADC VPX FIPS certified appliances.
A certificate-key pair is required for HTTPS access to the configuration utility and for secure remote procedure calls. RPC nodes are internal system entities used for system-to-system communication of configuration and session information. One RPC node exists on each appliance. This node stores the password, which is checked against the one provided by the contacting appliance. To communicate with other Citrix ADC appliances, each appliance requires knowledge of the other appliances, including how to authenticate on the other appliance. RPC nodes maintain this information, which includes the IP addresses of the other Citrix ADC appliances and the passwords used to authenticate on each.
On a Citrix ADC MPX appliance virtual appliance, a certificate-key pair is automatically bound to the internal services. On a FIPS appliance, a certificate-key pair must be imported into the hardware security module (HSM) of a FIPS card. To do so, you must configure the FIPS card, create a certificate-key pair, and bind it to the internal services.
Configure secure HTTPS by using the CLI
To configure secure HTTPS by using the CLI, follow these steps
Initialize the hardware security module (HSM) on the FIPS card of the appliance. For information about initializing the HSM, seeConfigure the HSM.
If the appliance is part of a high availability setup, enable the SIM. For information about enabling the SIM on the primary and secondary appliances, see “Configure FIPS appliances in a high availability setup.
Import the FIPS key into the HSM of the FIPS card of the appliance. At the command prompt, type:
import ssl fipskey serverkey -key ns-server.key -inform PEM
Add a certificate-key pair. At the command prompt, type:
add certkey server -cert ns-server.cert -fipskey serverkey
Bind the certificate-key created in the previous step to the following internal services. At the command prompt, type:
bind ssl service nshttps-127.0.0.1-443 -certkeyname server
bind ssl service nshttps-::11-443 -certkeyname server
Configure secure HTTPS by using the GUI
To configure secure HTTPS by using the GUI, follow these steps:
Initialize the hardware security module (HSM) on the FIPS card of the appliance. For information about initializing the HSM, seeConfigure the HSM.
- If the appliance is part of a high availability setup, enable the secure information system (SIM). For information about enabling the SIM on the primary and secondary appliances, seeConfigure FIPS appliances in a high availability setup.
- Import the FIPS key into the HSM of the FIPS card of the appliance. For more information about importing a FIPS key, see theImport an existing FIPS keysection.
- Navigate toTraffic Management > SSL > Certificates.
- In the details pane, clickInstall.
- In the Install Certificate dialog box, type the certificate details.
- ClickCreate, and then clickClose.
- Navigate toTraffic Management > Load Balancing > Services.
- In the details pane, on theActiontab, clickInternal Services.
- 年代elect
nshttps-127.0.0.1-443
from the list, and then clickOpen. - On the年代年代L Settingstab, in theAvailablepane, select the certificate created in step 7, clickAdd, and then clickOK.
- 年代elect
nshttps-::11-443
from the list, and then clickOpen. - On the年代年代L Settingstab, in theAvailablepane, select the certificate created in step 7, clickAdd, and then clickOK.
- ClickOK.
Configure secure RPC by using the CLI
To configure secure RPC by using the CLI, follow these steps:
Initialize the hardware security module (HSM) on the FIPS card of the appliance. For information about initializing the HSM, seeConfigure the HSM.
Enable the secure information system (SIM). For information about enabling the SIM on the primary and secondary appliances, seeConfigure FIPS appliances in a high availability setup.
Import the FIPS key into the HSM of the FIPS card of the appliance. At the command prompt, type:
import ssl fipskey serverkey -key ns-server.key -inform PEM
Add a certificate-key pair. At the command prompt, type:
add certkey server -cert ns-server.cert -fipskey serverkey
Bind the certificate-key pair to the following internal services. At the command prompt, type:
bind ssl service nsrpcs-127.0.0.1-3008 -certkeyname server
bind ssl service nskrpcs-127.0.0.1-3009 -certkeyname server
bind ssl service nsrpcs-::1l-3008 -certkeyname server
Enable secure RPC mode. At the command prompt, type:
set ns rpcnode
-secure YES 关于改变一个RPC节点pa的更多信息ssword, seeChange an RPC node password.
Configure secure RPC by using the GUI
To configure secure RPC by using the GUI, follow these steps:
- Initialize the hardware security module (HSM) on the FIPS card of the appliance. For information about initializing the HSM, seeConfigure the HSM.
- Enable the secure information system (SIM). For information about enabling the SIM on the primary and secondary appliances,Configure FIPS appliances in a high availability setup.
- Import the FIPS key into the HSM of the FIPS card of the appliance. For more information about importing a FIPS key, theImport an existing FIPS keysection.
- Navigate toTraffic Management > SSL > Certificates.
- In the details pane, clickInstall.
- In theInstall Certificatedialog box, type the certificate details.
- ClickCreate, and then clickClose.
- Navigate toTraffic Management > Load Balancing > Services.
- In the details pane, on theActiontab, clickInternal Services.
- 年代elect
nsrpcs-127.0.0.1-3008
from the list, and then clickOpen. - On the年代年代L Settingstab, in theAvailablepane, select the certificate created in step 7, clickAdd, and then clickOK.
- 年代elect
nskrpcs-127.0.0.1-3009
from the list, and then clickOpen. - On the年代年代L Settingstab, in theAvailablepane, select the certificate created in step 7, clickAdd, and then clickOK.
- 年代elect
nsrpcs-::11-3008
from the list, and then clickOpen. - On the年代年代L Settingstab, in theAvailablepane, select the certificate created in step 7, clickAdd, and then clickOK.
- ClickOK.
- Navigate to年代ystem > Network > RPC.
- In the details pane, select the IP address, and clickOpen.
- In theConfigure RPC Nodedialog box, select年代ecure.
- ClickOK.
年代hare
年代hare
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.