ADC / NetScaler – Page 8

NetScaler Gateway 11 RADIUS Authentication

Last Modified: Nov 7, 2020 @ 6:35 am

Navigation

RADIUS Overview
Two-factor Policies Summary
Create Two-factor Policies
Bind Two-factor Policies to Gateway

RADIUS Overview

For two-factor authentication using Azure Multi-factor Authentication, see Jason Samuel How to deploy Microsoft Azure MFA & AD Connect with Citrix NetScaler Gateway

Citrix CTX125364 How to Configure Dual Authentication on NetScaler Gateway Enterprise Edition for Use with iPhone and iPad.

Some two-factor products (e.g. SMS Passcode) require you to hide the 2nd password field. Receiver 4.4 and newer supports hiding the 2nd field if you configure a Meta tag in index.html. See CTX205907 Dual-Password Field Shows in First Authentication When Connecting to NetScaler Gateway from Windows Receiver for instructions. 💡

Two-factor authentication to NetScaler Gateway requires the RADIUS protocol to be enabled on the two-factor authentication product.

On your RADIUS servers you’ll need to add the NetScaler appliances as RADIUS Clients. When NetScaler uses a local (same appliance) load balanced Virtual Server for RADIUS authentication, the traffic is sourced from the NetScaler SNIP (Subnet IP). When NetScaler uses a direct connection to a RADIUS Server without going through a load balancing Virtual Server, or uses a remote (different appliance) Load Balancing Virtual Server, the traffic is sourced from the NetScaler NSIP (NetScaler IP). Use the correct IP(s) when adding the appliances as RADIUS Clients. And adjust firewall rules accordingly.

For High Availability pairs, if you locally load balance RADIUS, then you only need to add the SNIP as a RADIUS Client since the SNIP floats between the two appliances. However, if you are not locally load balancing RADIUS then you’ll need to add the NSIP of both appliances as RADIUS Clients. Use the same RADIUS Secret for both appliances.

Two-factor Policies Summary

When configuring the NetScaler Gateway Virtual Server, you can specify both a Primary authentication policy and a Secondary authentication policy. Users are required to successfully authenticate against both before being authorized for NetScaler Gateway.

For browser-based StoreFront, you need two authentication policies:

Primary = LDAPS authentication policy pointing to Active Directory Domain Controllers.
Secondary = RADIUS authentication policy pointing to RSA servers with RADIUS enabled.

For Receiver Self-service (native Receiver on mobile, Windows, and Mac), the authentication policies are swapped:

Primary = RADIUS authentication policy pointing to RSA servers with RADIUS enabled.
Secondary = LDAPS authentication policy pointing to Active Directory Domain Controllers.

If you need to support two-factor authentication from both web browsers and Receiver Self-Service, then you’ll need at least four authentication policies as shown below.

Primary:

Priority 90 = RADIUS policy. Expression = REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver
Priority 100 = LDAP policy. Expression = REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver

Secondary:

Priority 90 = LDAP policy. Expression = REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver
Priority 100 = RADIUS policy. Expression = REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver

Create Two-factor Policies

Do the following to create the Two-factor policies:

Create an LDAP server.
For RADIUS, on the left, expand Authentication, and click Dashboard.
On the right, click Add.
Change Choose Server Type to RADIUS.
Give the server a name.
Specify the IP address of the RADIUS load balancing Virtual Server.
Enter the secret key specified when you added the NetScalers as RADIUS clients on the RADIUS server. Click Create.
```
add authentication radiusAction RSA -serverIP 10.2.2.210 -serverPort 1812 -radKey Passw0rd
```
Since you can’t create authentication policies from the authentication dashboard, go to NetScaler Gateway > Policies > Authentication > RADIUS.
On the right, in the Policies tab, click Add.
Name it RSA-SelfService or similar.
Select the RADIUS server created earlier.
Enter an expression. You will need two policies with different expressions. The expression for Receiver Self-Service is HTTP.HEADER User-Agent CONTAINS CitrixReceiver.

Click Create.

add authentication radiusPolicy RSA-Web "REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver" RSA

add authentication radiusPolicy RSA-SelfService "REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver" RSA

add authentication ldapPolicy Corp-Gateway-Web "REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver" Corp-Gateway

add authentication ldapPolicy Corp-Gateway-SelfService "REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver" Corp-Gateway

Create another policy to match the ones shown below. Both RADIUS policies are configured with the same RADIUS server. The only difference between them is the expression (CONTAINS vs NOTCONTAINS):

Name Expression Server

RSA-SelfService REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver RSA

RSA-Web REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver RSA
Go to the NetScaler Gateway\Policies\Authentication\LDAP node.
On the Policies tab, create two policies with the expressions shown below. Both LDAP policies are configured with the same LDAP server. The only difference between them is the expression (CONTAINS vs NOTCONTAINS).

Name Expression Server

LDAP-Corp-SelfService REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver LDAP-Corp

LDAP-Corp-Web REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver LDAP-Corp

Bind Two-factor Policies to Gateway

When you create the NetScaler Gateway Virtual Server, bind the policies as shown in the following table. Priority doesn’t matter because they are mutually exclusive.

Policy Name	Type	Bind Point
LDAP-Corp-Web	LDAP	Primary
RSA-SelfService	RADIUS	Primary
LDAP-Corp-SelfService	LDAP	Secondary
RSA-Web	RADIUS	Secondary

bind vpn vserver gateway.corp.com -policy Corp-Gateway-Web -priority 100

bind vpn vserver gateway.corp.com -policy RSA-SelfService -priority 110

bind vpn vserver gateway.corp.com -policy RSA-Web -priority 100 -secondary

bind vpn vserver gateway.corp.com -policy Corp-Gateway-SelfService -priority 110 -secondary

The session policy/profile for Receiver Self-Service needs to be adjusted to indicate which authentication field contains the Active Directory password. In the Session Profile, on the Client Experience tab is Credential Index. This needs to be changed to SECONDARY. Leave the session policy for Web Browsers set to Primary.
```
set vpn sessionAction "Receiver Self-Service" -ssoCredential SECONDARY
```
On the StoreFront server, when creating the NetScaler Gateway object, change the Logon type to Domain and security token.

NetScaler 11 Certificates

Last Modified: Nov 7, 2020 @ 6:35 am

12 Comments

Navigation

Here are three methods of creating certificates for NetScaler:
If the server certificate is signed by an intermediate authority, import the intermediate certificate and bind it.
Default Management Certificate Key Length
Replace the management certificate and then force SSL access for management.
Update certificates before they expire.

💡 = Recently Updated

Convert .PFX Certificate to PEM Format

You can export a certificate from Windows and import it to NetScaler. However, Windows certificates can’t be imported on NetScaler in their native PFX format and must first be converted to PEM as detailed below:

On the Windows server that has the certificate, run mmc.exe and add the certificates snap-in.
Right-click the certificate and click Export.
On the Export Private Key page, select Yes, export the private key and click Next.
On the Export File Format page, ensure Personal Information Exchange is selected and click Next.
Save it as a .pfx file. Don’t put any spaces in the filename.
In NetScaler 11, it is no longer necessary to first convert the .PFX file to PEM format since Traffic Management > SSL > Certificates > Install will convert the .PFX file for you. Note: when the PFX is converted to PEM, the key is not encrypted.
Browse (Local) to the PFX file in both the certificate file and key file fields, enter the PFX password, and then click Install.
If you click the arrow next to the certificate you’ll see that NetScaler created a new file with a .ns extension.
If you look inside this file by going to Traffic Management > SSL > Manage Certificates / Keys / CSRs, notice that the RSA Private Key is not encrypted, encoded, or password protected.
If you want to encrypt your key file (recommended), use the older method of converting from PFX to PEM. In the NetScaler Configuration GUI, on the left expand Traffic Management and click SSL.
In the right column of the right pane, click Import PKCS#12 in the Tools section.
In the Import PKCS12 File dialog box:
1. In the Output File Name field, enter a name (e.g. Citrix.cer) for a new file where the PEM certificate and key will be placed.
2. In the PKCS12 File field, click Browse and select the previously exported .pfx file.
3. In the Import Password field, enter the password you specified when you previously exported the .pfx file.
4. Change the Encoding Format selection to DES3. This causes the new Output file to be encrypted.
5. Enter a password for the Output file and click OK.
If you browse to the /nsconfig/ssl directory on the NetScaler and view the new .cer file you just created, you’ll see both the certificate and the private key in the same file. You can use the Manage Certificates / Keys / CSRs link to view the files.
Notice that the file contains both the certificate and the RSA Private key.
On the left side of the NetScaler Configuration GUI, expand Traffic Management > SSL, and click Certificates.
On the right, click Install.
In the Install Certificate dialog box:
1. In the Certificate-Key Pair Name field, enter a friendly name for this certificate.
2. In the Certificate File Name field, browse the appliance and select the .cer file you just created.
3. In the Private Key File Name field, browse the appliance and select the same .cer file you just created. Both the certificate and the private key are in the same file.
4. If the private key is encrypted, enter the password.
5. Click Install. You can now link an intermediate certificate to this SSL certificate and then bind this SSL certificate to SSL and/or NetScaler Gateway Virtual Servers.
To automatically backup SSL certificates and receive notification when the certificates are about the expire, deploy Citrix Command Center or NetScaler Management and Analytics System. Also see Citrix CTX213342 How to handle certificate expiry on NetScaler.

Create Key and Certificate Request

You can create a key pair and Certificate Signing Request directly on the NetScaler appliance. The Certificate Signing Request can then be signed by an internal or public Certificate Authority.

Most Certificate Authorities let you add Subject Alternative Names when submitting the Certificate Signing Request to the Certificate Authority and thus there’s no reason to include Subject Alternative Names in the Certificate Signing Request. You typically create a Certificate Signing Request with a single DNS name. Then when submitting the Certificate Signing Request to the Certificate Authority you type in additional DNS names. For a Microsoft Certificate Authority, you can enter Subject Alternative Names in the Attributes box of the Web Enrollment wizard. For public Certificate Authorities, you purchase a UCC certificate or purchase a certificate option that lets you type in additional names.

If you instead want to create a Certificate Signing Request on NetScaler that has Subject Alternative Names embedded in it as request attributes, see Citrix Blog Post How to Create a CSR for a SAN Certificate Using OpenSSL on a NetScaler Appliance. These instructions are performed on the NetScaler command line using OpenSSL. Or you can instead create a Subject Alternative Name certificate on Windows.

On the left, expand Traffic Management, and click SSL.
On the right, in the left column, click Create RSA Key.
Give the .key file a descriptive name.
Set the Key Size to 2048 bits
Set the PEM Encoding Algorithm to DES3 and enter a password. This encrypts the key file.
Click OK. You will soon create a certificate using the keys in this file.
On the right, in the right column, click Create Certificate Signing Request (CSR).
In the Request File Name field, enter the name of a new file.
In the Key Filename field, browse to the previously created .key file.
If the key file is encrypted, enter the password.
In the State field, enter your state name without abbreviating.
In the Organization Name field, enter your official Organization Name.
Enter the City name.
Enter IT or similar as the Organization Unit.
In the Common Name field, enter the FQDN of the SSL enabled-website. If this is a wildcard certificate, enter * for the left part of the FQDN.
Scroll down and click Create.
At the top of the screen you’ll see a green banner. Click here to view.
You can then copy the contents and send it to your Certificate Authority.
Or, on the right side of the right pane, click Manage Certificates / Keys / CSRs.
Find the .csr file you just created and View it.
Copy the contents of the file and send it to the certificate administrator. Request the signed certificate to be returned in Apache or Base64 format.
After you get the signed certificate, on the left side of the NetScaler Configuration GUI, expand Traffic Management > SSL, and click Certificates.
On the right, click Install.
In the Install Certificate dialog box:
1. In the Certificate-Key Pair Name field, enter a friendly name for this certificate.
2. In the Certificate File Name field, browse Local and select the .cer file you received from the Certificate Authority.
3. In the Private Key File Name field, browse the appliance and select the key file you created earlier.
4. If the key file is encrypted, enter the password.
5. Click Install.
The certificate is now added to the list. Notice the Expiry Date. You can now bind this certificate to any SSL Offload, NetScaler Gateway, or Content Switching Virtual Server.
To automatically backup SSL certificates and receive notification when the certificates are about the expire, deploy Citrix Command Center. Also see Citrix CTX213342 How to handle certificate expiry on NetScaler.

Intermediate Certificate

If your Server Certificate is signed by an intermediate Certificate Authority, then you must install the intermediate Certificate Authority’s certificate on the NetScaler. This Intermediate Certificate then must be linked to the Server Certificate.

Sometimes the public Certificate Authority will give you the Intermediate certificate as one of the files in a bundle. If not, log into Windows and double-click the signed certificate.
On the Certification Path tab, double-click the intermediate certificate (e.g. Go Daddy Secure Certificate Authority. It’s the one in the middle).
On the Details tab, click Copy to File.
In the Welcome to the Certificate Export Wizard page, click Next.
In the Export File Format page, select Base-64 encoded and click Next.
Give it a file name and click Next.
In the Completing the Certificate Export Wizard page, click Finish.
In the NetScaler configuration GUI, expand Traffic Management, expand SSL, and click Certificates.
On the right, click Install.
Name it Intermediate or similar.
Browse locally for the Intermediate certificate file.
Click Install. You don’t need a key file.
Highlight the server certificate, open the Action menu and click Link.
The previously imported Intermediate certificate should already be selected. Click OK.

Create Certificate with NetScaler as Certificate Authority

If you don’t have an internal Certificate Authority, you can use NetScaler as a Certificate Authority. The NetScaler Certificate Authority can then be used to sign Server Certificates. This is a simple method for creating a new management certificate. The main problem with this method is that the NetScaler root certificate must be manually installed on any machine that connects to the NetScaler.

On the left, expand Traffic Management, and click SSL.
On the right, in the left column, click Root-CA Certificate Wizard.
In the Key Filename field, enter root.key or similar. This is a new file.
In the Key Size field, enter at least 2048.
Optionally, to encrypt the key file, change the PEM Encoding Algorithm to DES3, and enter a new password.
Click Create.
In the Request File Name field, enter root.csr or similar. This is a new file.
If the key file is encrypted, enter the password.
Scroll down.
In the State field, enter the non-abbreviated state name.
In the Organization Name field, enter the name of your organization.
Fill in other fields as desired.
In the Common Name field, enter a descriptive name for this Certificate Authority.
Click Create .
In the Certificate File Name field, enter root.cer or similar. This is a new file.
Change the Validity Period to 3650 (10 years) or similar.
If the key file is encrypted, enter the password in the PEM Passphrase field.
Click Create.
In the Certificate-Key Pair Name field, enter a friendly name for this Certificate Authority certificate.
If the key file is encrypted, enter the password in the Password field.
Click Create.
Click Done.
In the right pane, in the left column, click Server Certificate Wizard.
In the Key Filename field, enter mgmt.key or similar. This is a new file.
In the Key Size field, enter at least 2048.
Optionally, to encrypt the key file, change the PEM Encoding Algorithm to DES3, and enter a new password.
Click Create.
In the Request File Name field, enter mgmt.csr or similar. This is a new file.
If the key file is encrypted, enter the password.
Scroll down.
In the State field, enter the non-abbreviated state name.
In the Organization Name field, enter the name of your organization.
Fill in other fields as desired.
In the Common Name field, enter the hostname (FQDN) of the appliance.
Click Create.
In the Certificate File Name field, enter mgmt.cer or similar. This is a new file.
Change the Validity Period to 3650 (10 years) or similar.
Scroll down.
In the CA Certificate File Name field, browse to the root.cer file.
In the CA Key File Name field, browse to the root.key file.
If the key file is encrypted, enter the password.
In the CA Serial File Number field, enter the name of a new file that will contain serial numbers.
Click Create.
In the Certificate-Key Pair Name field, enter a friendly name for this management certificate.
If the key file is encrypted, enter the password in the Password field.
Click Create.
Click Done.

Default Management Certificate Key Length

In older NetScaler builds, the default management certificate (ns-server-certificate) key size is only 512 bits. To see the key size, right-click ns-server-certificate, and then click Details.

If you try to use Internet Explorer to connect to the NSIP using SSL, Internet Explorer will consider 512 bits to be unsafe and probably won’t let you connect. Notice there’s no option to proceed.

You can configure Internet Explorer to accept the 512-bit certificate by running Certutil ?setreg chain\minRSAPubKeyBitLength 512 on the same machine where Internet Explorer is running.

When you upgrade NetScaler, the management certificate remains at whatever was installed previously. If it was never replaced, then the management certificate is still only 512 bits. To replace the certificate with a new 2048-bit self-signed certificate, simply delete the existing ns-server-certificate certificate files and reboot.

Go to Traffic Management > SSL.
On the right, in the right column, click Manage Certificates / Keys / CSRs.
Highlight any file named ns-* and delete them. This takes several seconds.
Then go to System and reboot.
After a reboot, if you view the Details on the ns-server-certificate, it will be recreated as self-signed with 2048-bit key size.

Replace Management Certificate

You can replace the default management certificate with a new trusted management certificate.

Only one certificate will be loaded on both nodes in a High Availability pair so make sure the management certificate matches the names of both nodes. This is easily doable using a Subject Alternative Name certificate. Here are some names the management certificate should match (note: a wildcard certificate won’t match all of these names):

The FQDN for each node NSIP in a High Availability pair. Example: ns01.corp.local and ns02.corp.local
The shortnames (left label) for each node NSIP in a High Availability pair. Example: ns01 and ns02
The NSIP IP address for each node in a High Availability pair. Example: 192.168.123.14 and 192.168.123.29
If you enabled management access on your SNIPs, add names for the SNIPs:
- FQDN for the SNIP. Example: ns.corp.local
- Shortname for the SNIP. Example: ns
- SNIP IP address. Example: 192.168.123.30

If you are creating a Subject Alternative Name certificate, it’s probably easiest to do the following:

Create the certificate using the Certificates snap-in on a Windows box. You can add the Subject Alternative Names in the certificate request wizard. The Subject Alternative Names for the IP addresses must be added as IP address (v4). The other Subject Alternative Names are added as DNS.
Export the certificate and Private Key to a .pfx file.
On the NetScaler, use the Import PKCS#12 tool to convert the .pfx to PEM format. Then follow one of the procedures below to replace the management certificate.

There are two methods of replacing the management certificate:

Use the Update Certificate button for ns-server-certificate in the NetScaler GUI. This automatically updates all of the Internal Services bindings too.
- You cannot rename the certificate in the NetScaler GUI. It remains as ns-server-certificate.
- If your new management certificate is a wildcard that you need to use for other SSL entities, then you will bind ns-server-certificate to those entities instead of a more descriptive name. You can’t re-upload the wildcard certificate again with a different GUI name.
Or manually Bind the new certificate to the Internal Services.

Update Certificate Method

The Update Certificate button method is detailed below:

You can’t update the certificate while connected to the NetScaler using https so make sure you connect using http.
On the left, expand Traffic Management, expand SSL, and click Certificates.
On the right, highlight ns-server-certificate, and click Update.
Check the box next to Click to update Certificate/Key.
Browse to the new management certificate. It could be on the appliance or it could be on your local machine.
If the PEM certificate is encrypted, enter the password.
Check the box next to No Domain Check. Click OK.
Click Yes to update the certificate.
You can now connect to the NetScaler using https protocol. The certificate should be valid and it should have a 2048 bit key.
Putty (SSH) to the appliance.
Run the following command to see the internal services.
show service –internal | grep –i "ns"
For each internal service, run the following command to disable SSL3. Replace ServiceName with the name of each internal service.
set ssl service ServiceName -ssl3 disabled
For each internal service, run the following command to remove RC4 ciphers. Replace ServiceName with the name of each internal service.
unbind ssl service ServiceName -cipherName RC4
Repeat this process on the second appliance.

Manual Binding Method

The manual Binding to Internal Services method is detailed below:

You can’t update the certificate while connected to the NetScaler using https so make sure you connect using http.
On the left, expand Traffic Management, expand SSL and click Certificates.
On the right, use the Install button to install the certificate if you haven’t already done so.
On the right, highlight the new management certificate, open the Action menu, and click Details.
Verify that the Public Key Size is 2048. Click OK.
On the left, expand Traffic Management, expand Load Balancing, and click Services.
On the right, switch to the Internal Services tab.
You will see multiple services. Edit one of them.
Scroll down and click where it says 1 Client Certificate.
Highlight the existing management certificate, and click Unbind.
Click Yes to remove the selected entity.
Click Add Binding.
Click where it says Click to select.
Select the new management certificate, and click Select.
Click Bind, and click Close.
Scroll to the SSL Parameters section, and click the pencil icon.
Uncheck the box next to SSLv3. Make sure TLSv11 and TLSv12 are enabled. Click OK.
On the right, in the Advanced Settings column, click SSL Ciphers.
On the left, in the SSL Ciphers section, select the Cipher Group that has all RC4 ciphers removed. and click OK.
If you see a warning about No usable ciphers, click OK and ignore it.
Repeat for the rest of the internal services.

Force Management SSL

By default, administrators can connect to the NSIP using HTTP or SSL. This section details how to disable HTTP.

Internet Explorer will not accept the default 512-bit management certificate included on the appliance so make sure you replace the default management certificate or use a different browser.

Connect to the NSIP using https.
On the left, expand System, expand Network, and click IPs.
On the right, highlight your NetScaler IP, and click Edit.
Near the bottom, check the box next to Secure access only, and then click OK.
Citrix CTX204217 How to redirect users from HTTP to HTTPS while accessing NSIP/Management IP. Requires a Responder policy, and a nsapimgr command. 💡
Repeat this on the secondary appliance.
Repeat for any SNIPs that have management access enabled.

SSL Certificate – Update

If your certificate is about to expire, do the following:

Create updated certificate files in PEM format. One option is to create a key file and Certificate Signing Request directly on the NetScaler. Another option is to convert a PFX file to a PEM file. Don’t install the certificate yet, but instead, simply have access to the key file and certificate file in PEM format.
In NetScaler, navigate to Traffic Management > SSL > Certificates.
On the right, highlight the certificate you intend to update, and click Update.
Check the box next to Click to update the Certificate/Key.
Browse to the updated certificate and key files (if you imported a PFX then the certificate and key files are the same file).
Click Yes to update the certificate.
Click OK. This will automatically update every Virtual Server on which this certificate is bound.
Certificates can also be updated in Citrix Command Center or NetScaler Management and Analytics System.

NetScaler Gateway 11 Virtual Server

Last Modified: Nov 7, 2020 @ 6:35 am

107 Comments

Navigation

NetScaler Gateway Universal Licenses
Create NetScaler Gateway Virtual Server
Verify SSL Settings
Gateway Portal Theme
SSL Redirect
DNS SRV Records for Email-based discovery
Block Citrix VPN for iOS
View ICA sessions
Customize Logon Page
UDP Audio Through Gateway
Unified Gateway
StoreFront – Rewrite X-Citrix-Via

💡 = Recently Updated

NetScaler Gateway Universal Licenses

For basic ICA Proxy connectivity to XenApp/XenDesktop, you don’t need to install any NetScaler Gateway licenses on the NetScaler appliance. However, if you need SmartAccess features (e.g. EPA scans) or VPN then you must install NetScaler Gateway Universal licenses. These licenses are included with the Platinum editions of XenApp/XenDesktop, Advanced or Enterprise Edition of XenMobile, and the Platinum version of NetScaler.

When you create a NetScaler Gateway Virtual Server, the ICA Only setting determines if you need NetScaler Gateway Universal licenses or not. If the Virtual Server is set to ICA Only then you don’t need licenses. But if ICA Only is set to false then you need a NetScaler Gateway Universal license for every user that connects to this NetScaler Gateway Virtual Server. Enabling ICA Only disables all SmartAccess, SmartControl, and VPN features.

If you don’t need any non-ICA Proxy features, then you don’t need any Gateway Universal licenses, and you can skip to the next section.

The Gateway Universal licenses are allocated to the case sensitive hostname of each appliance. If you have an HA pair, and if each node has a different hostname, allocate the Gateway Universal licenses to the first hostname, and then reallocate the same licenses to the other hostname.

To see the hostname, click the version info on the top right.

To change the hostname, click the gear icon on the top right.

To upload the allocated Gateway Universal licenses to the appliance, go to System > Licenses. A reboot is required.

After NetScaler Gateway Universal licenses are installed on the appliance, they won’t necessarily be available for usage until you make a configuration change as detailed below:

On the left, expand System, and click Licenses.
On the right, in the Maximum NetScaler Gateway Users Allowed field is the number of licensed users for NetScaler Gateway Virtual Servers that are not set to ICA Only.
On the left, under NetScaler Gateway, click Global Settings.
In the right column of the right pane, click Change authentication AAA settings.
Change the Maximum Number of Users to your licensed limit. This field has a default value of 5, and administrators frequently forget to change it thus only allowing 5 users to connect.
If desired, check the box for Enable Enhanced Authentication Feedback. Click OK.
```
set aaa parameter -enableEnhancedAuthFeedback YES -maxAAAUsers 200
```
Then edit the NetScaler Gateway Virtual Server.
In the Basic Settings section, click the pencil icon near the top right.
Click More.
In the Max Users field, either enter 0 (for unlimited/maximum) or enter a number that is equal to or less than the number of licensed users. Click OK.
```
set vpn vserver gateway.corp.com -maxAAAUsers 0
```

Create Gateway Virtual Server

Create a certificate for the NetScaler Gateway Virtual Server. The certificate must match the name users will use to access the Gateway. For email discovery in Citrix Receiver, the certificate must have subject alternative names (SAN) for discoverReceiver.email.suffix (use your email suffix domain name). If you have multiple email domains then you’ll need a SAN for each one.
On the left, right-click NetScaler Gateway and click Enable Feature.
On the left, expand NetScaler Gateway and click Virtual Servers.
On the right, click Add.
Name it gateway.corp.com or similar.
Enter a new VIP that will be exposed to the Internet. Note: new to NetScaler 11.0 is the ability to set it to Non Addressable, which means you can place it behind a Content Switching Virtual Server.
Click More.
In the Max Users field enter 0.
In the Max Login Attempts field, enter your desired number. Then enter a timeout in the Failed Login Timeout field.
Check the box next to ICA Only. This option disables SmartAccess and VPN features but does not require any additional licenses.
Check the box next to DTLS and click OK. DTLS enables UDP Audio and Framehawk. Note: DTLS is not yet supported for double-hop ICA.
In the Certificates section, click where it says No Server Certificate.
Click the arrow next to Click to select.
Select a previously created certificate that matches the NetScaler Gateway DNS name, and click Select.
Click Bind.
If you see a warning about No usable ciphers, click OK.
Click Continue.
In the Authentication section, click the plus icon in the top right.
Note: it’s also possible to disable authentication on Gateway and make StoreFront do it instead as described in Citrix CTX200066 How to Log On to StoreFront When Authentication is Disabled on NetScaler Gateway VIP. However, it’s more secure to require Gateway to authenticate the users before the user can communicate with StoreFront.
Select LDAP, select Primary and click Continue.
If you used the authentication dashboard to create the LDAP server then you probably haven’t create the corresponding policy yet. Click the plus icon to create a new policy.
Use the Server drop-down to select the previously created LDAP server.
Give the policy a name. It can match the LDAP Server name.
In the Expression box, enter ns_true or select it from the Saved Policy Expressions drop-down. Click Create.
Click Bind.
Or for two-factor authentication, you will need to bind two policies to Primary and two polices to Secondary:
- Primary = LDAP for Browsers (User-Agent does not contain CitrixReceiver)
- Primary = RADIUS for Receiver Self-Service (User-Agent contains CitrixReceiver)
- Secondary = RADIUS for Browsers (User-Agent does not contain CitrixReceiver)
- Secondary = LDAP for Receiver Self-Service (User-Agent contains CitrixReceiver)
Click Continue.
Scroll down to the Profiles section and click the pencil icon.
In the TCP Profile drop-down select nstcp_default_XA_XD_profile and click OK.
In the Policies section, click the plus icon near the top right.
Select Session, select Request and click Continue.
Click the arrow next to Click to select.
Select one of the Receiver session policies and click Select. It doesn’t matter which order you bind them.
There’s no need to change the priority number. Click Bind.
Repeat these steps to bind the second policy. In the Policies section, click the plus icon near the top right.
Select Session, select Request and click Continue.
Click Add Binding.
Click the arrow next to Click to select.
Select the other Receiver session policy and click Select.
There’s no need to change the priority number. Click Bind.
The two policies are mutually exclusive so there’s no need to adjust priority. Click Close.
On the right, in the Advanced Settings section, click Published Applications.
Click where it says No STA Server.
Add a Controller in the https://<Controller_FQDN> or http://<Controller_FQDN> format, depending on if SSL is enabled on the XenApp Controller or not. This must be a FQDN or IP address. Short names don’t work.
For the Address Type, select IPV4. Click Bind.
To bind another Secure Ticket Authority server, on the left, in the Published Applications section, click where it says 1 STA Server.
Click Add Binding. Enter the URL for the second controller.
The State is probably down. Click Close.
In the Published Applications section, click STA Server.

Now they should be up and there should be a unique Auth ID for each server. Click OK.

add vpn vserver gateway.corp.com SSL 10.2.2.200 443 -icaOnly ON -dtls ON -tcpProfileName nstcp_default_XA_XD_profile

bind vpn vserver gateway.corp.com -policy "Receiver Self-Service" -priority 100

bind vpn vserver gateway.corp.com -policy "Receiver for Web" -priority 110

bind vpn vserver gateway.corp.com -policy Corp-Gateway -priority 100

bind vpn vserver gateway.corp.com -staServer "http://xdc01.corp.local"
bind vpn vserver gateway.corp.com -staServer "http://xdc02.corp.local"

bind vpn vserver gateway.corp.com -portaltheme X1

If you haven’t enabled the Default SSL Profile, then perform other normal SSL configuration including: disable SSLv3, bind a Modern Cipher Group, and enable Strict Transport Security.

bind ssl vserver MyvServer -certkeyName MyCert

set ssl vserver MyvServer -ssl3 DISABLED -tls11 ENABLED -tls12 ENABLED

unbind ssl vserver MyvServer -cipherName ALL

bind ssl vserver MyvServer -cipherName Modern

bind ssl vserver MyvServer -eccCurveName ALL

bind vpn vserver MyvServer -policy insert_STS_header -priority 100 -gotoPriorityExpression END -type RESPONSE

Verify SSL Settings

After you’ve created the Gateway Virtual Server, run the following tests:

Citrix CTX200890 – Error: “1110” When Launching Desktop and “SSL Error” While Launching an Application Through NetScaler Gateway: You can use OpenSSL to verify the certificate. Run the command: openssl s_client -connect gateway.corp.com:443. Replace the FQDN with your FQDN. OpenSSL is installed on the NetScaler or you can download and install it on any machine.
Go to https://www.digicert.com/help/ to verify the certificate chain.
Go to https://www.ssllabs.com/ssltest/ and check the security settings of the website. Citrix Blogs – Scoring an A+ at SSLlabs.com with Citrix NetScaler – 2016 update

Gateway Portal Theme

Citrix Blog Post Branding your Deployment Part 2: Matching NetScaler to StoreFront explains NetScaler Gateway Portal Themes, how to edit the Portal Theme CSS, and warns about GUI changes overwriting CSS file changes.

If you want the logon page for NetScaler Gateway to look more like StoreFront 3.0, NetScaler 11.0 build 62 and newer have a built-in X1 theme:

Go to NetScaler Gateway > Virtual Servers and edit an existing Virtual Server.
On the right, in the Advanced Settings section, click Portal Themes.
On the left, click where it says No Portal Theme.
Click to select.
Select the built-in X1 theme and click Select.
Click Bind.

Click Done.

bind vpn vserver gateway.corp.com -portaltheme X1

When you access the NetScaler Gateway login page you’ll see the theme.

You can also create your own theme by starting from one of the built-in themes:

Go to NetScaler Gateway > Portal Themes.
On the right, click Add.
Give it a name and select X1 as the Template Theme.
In the Look and Feel section there are two sub-sections: one for Home Page and one for Other Pages. In each of these sections is an Attribute Legend link that shows you what you can edit.
The Home Page is for Unified Gateway (aka VPN Clientless Access).
If you want to modify the logon page, use the Other Pages sub-section.
Make changes as desired and click OK.
In the Locale section, select a language and click OK.
On the right, in the Advanced Settings section, click Login Page.
Make changes as desired (e.g. Password Field Titles) and click OK.
At the top of the screen, click the link to Click to bind and view configured theme.
Select a Gateway Virtual Server and click Preview.
The logon page is displayed.
You could go to /var/netscaler/logon/themes/StoreFront3/css and make more changes to custom.css but this file gets overwritten any time you make a change in the Portal Themes section of the NetScaler GUI.
Citrix CTX209526 NetScaler; How to Copy a Portal Theme from the Device running version 11.0 to another Device running 11.0. 💡

Jason Samuel – How to fix Green Bubble theme after upgrading to NetScaler 11 Unified Gateway details the following:

Change the NetScaler Unified Gateway logo to match the older Citrix Receiver logo.
Restore the older favicon.
And other observations regarding the Green Bubbles theme in NetScaler 11.0

SSL Redirect – Down vServer Method

This procedure details the Down vServer method of performing an SSL redirect. An alternative is to use the Responder method.

On the left, expand Traffic Management, expand Load Balancing, and click Virtual Servers.
On the right, click Add.
Give it a name of Gateway-HTTP-SSLRedirect or similar.
Set the IP Address so it matches the VIP of the NetScaler Gateway vServer. Click OK.
Do not select any services. This redirect only works if the vServer is Down. Click Continue.
On the right, in the Advanced Settings column, click Protection.
Enter https://gateway.corp.com or similar into the Redirect URL Click Save.

Then click Done.

add lb vserver gateway.corp.com-HTTP-SSLRedirect HTTP 10.2.2.200 80 -redirectURL "https://gateway.corp.com"

All SSL Redirect Virtual Servers are supposed to be Down. They don’t work if they are not down. By contrast, the Responder method uses redirect Virtual Servers that are Up.

Public DNS SRV Records

For email-based discovery, add a SRV record to each public email suffix DNS zone. Here are sample instructions for a Windows DNS server:

In Server Manager, click Tools > DNS Manager
In the left pane of DNS Manager, select your DNS domain in the forward or reverse lookup zones. Right-click the domain and select Other New Records.
In the Resource Record Type dialog box, select Service Location (SRV) and then click Create Record.
In the New Resource Record dialog box, click in the Service box and enter the host value _citrixreceiver.
Click in the Protocol box and enter the value _tcp.
In the Port number box, enter 443.
In the Host offering this service box, specify the fully qualified domain name (FQDN) for your NetScaler Gateway Virtual Server in the form servername.domain (e.g. gateway.company.com)

Block Citrix VPN for iOS

Citrix CTX201129 Configuration for Controlled Access to Different VPN Plugin Through NetScaler Gateway for XenMobile Deployments: do one or both of the following:

Create an AppExpert > Responder > Policy with Action = DROP and Expression = HTTP.REQ.HEADER("User-Agent").CONTAINS("CitrixReceiver/NSGiOSplugin"). Either bind the Responder Policy Globally or bind it to the Gateway vServers.
In your Gateway Session Policies, do not set the Plugin type to Windows/Mac OS X.

View ICA Sessions

To view active ICA sessions, click the NetScaler Gateway node on the left and then click ICA Connections on the right.

show vpn icaconnection

Customize Logon Page

Logon Page Labels

When two factor authentication is configured on NetScaler Gateway, the user is prompted for User name, Password, and Password 2.

The Password field labels can be changed to something more descriptive, such as Active Directory or RSA:

To change the labels, edit a Portal Theme:

Go to NetScaler Gateway > Portal Themes and edit an existing theme. You can’t edit the built-in themes so you’ll have to create one if you haven’t already.
On the right, in the Advanced Settings column, click Login Page.
In the Login Page section, change the two Password fields to your desired text.
Click OK.
In the Portal Theme section you can Click to bind and view configured theme to Preview your changes.
On Platinum Edition appliances, you might have to invalidate the loginstaticobjects Content Group (Optimization > Integrated Caching > Content Groups) before the changes appear. This seems to be true even if Integrated Caching is disabled.

Logon Security Message (Disclaimer, EULA)

You can force users to agree to a EULA before they are allowed to login.

Clicking the Terms & Conditions link allows the user to view the EULA text that you have entered.

Do the following to configure the EULA:

Go to NetScaler Gateway > Resources > EULA.
On the right, click Add.
Give the EULA a name and enter some text. You can even enter HTML code. See the example posted by Chris Doran at Citrix Discussions.
Click Create.
Edit a Gateway Virtual Server.
On the right, in the Advanced Settings column click EULA.
Click where it says No EULA.
Click the arrow next to Click to select.
Select the EULA and click Select.
Click Bind.
Mike Roselli at Automatic EULA Acceptance by Cookie Rewrite Guide at Citrix Discussions details Rewrite policies that change the behavior so that users only have to accept the EULA once. It records acceptance in a cookie. 💡

Logon Page Links

Citrix CTX202444 How to Customize NetScaler Gateway 11 logon Page with Links shows how to add links to the NetScaler Gateway 11 logon page.

In WinSCP, go to /netscaler/ns_gui/vpn/js and edit the file gateway_login_form_view.js.
Scroll down to line 40 and insert the code copied from the article. Feel free to change the link.
Scroll down to line 140 and insert the line form.append(link_container);
Since this is an if block, insert the line in both the if section and the else section (line 148). Both should be after the append field_login line and before the append(form) line.
Save the file and verify your results.
If you reboot your appliance then your changes will be lost. To preserve your changes after a reboot, copy the modified file to /var.
Then edit /nsconfig/rc.netscaler and add a cp line to copy the modified file from /var to /netscaler/ns_gui/vpn/js. This is the same procedure as older NetScaler firmware. Feel free to reboot your appliance to confirm that the changes are still applied.

Other Customizations

Citrix CTX215817 NetScaler : How to Customize Footer of NetScaler Gateway Login Page. 💡

Mike Roselli at Netscaler 11 Theme Customization – How to Add Links and Verbiage at discussions.citrix.com has sample rewrite policies to customize the NetScaler Gateway logon page with additional HTML.

Craig Tolley Customising the NetScaler 11 User Interface – Adding Extra Content: add new sections to login page. These sections pull content from local HTML files.

Daniel Ruiz Set up a maintenance page on Netscaler Gateway: configure a Responder policy (see the blog post for sample HTML code). During maintenance, manually bind the Responder policy to the Gateway. Manually remove the policy after maintenance is complete. 💡

UDP Audio Through Gateway

From John Crawford at Citrix Discussions and Marius Sandbu Enabling Citrix Receiver audio over Netscaler Gateway with DTLS

Note: If you have NetScaler 11 build 62 or newer then enabling DTLS on the Gateway also enables Framehawk. See VDA > Framehawk for Framehawk configuration.

Requirements for UDP Audio:

Citrix Receiver 4.2 or newer
NetScaler Gateway 10.5.e (enhancement build) or NetScaler 11
UDP 443 allowed to NetScaler Gateway Virtual Server
UDP 16500-16509 allowed from NetScaler SNIP to VDAs

To enable UDP Audio through Gateway, make changes on both the NetScaler Gateway Virtual Server and in Receiver:

Edit the NetScaler Gateway Virtual Server. In the Basic Settings section click the edit (pencil) icon.
Click More.
Enable the DTLS option and click OK.
After enabling DTLS, it probably won’t work until you unbind the Gateway certificate and rebind it.

Client-side configuration

There are two methods of enabling RTP on the client side:

Edit default.ica on the StoreFront server
Use GPO to modify the client-side config

To edit the default.ica file on the StoreFront server (h/t Vipin Borkar): Edit the file C:\inetpub\wwwroot\Citrix\Store\App_Data\default.ica and add the following lines to the Application section:

EnableRtpAudio=true
EnableUDPThroughGateway=true
AudioBandwidthLimit=1

To use GPO to modify the client-side config:

Copy the receiver.admx (and .adml) policy template into PolicyDefinitions if you haven’t already.
Edit a GPO that applies to Receiver machines. You can also edit the local GPO on a Receiver machine.
Go to Computer Configuration > Policies > Administrative Templates > Citrix Components > Citrix Receiver.
Edit the setting Client audio settings.
Enable the setting.
Set audio quality as desired. Higher quality = higher bandwidth.
Check to Enable Real-Time Transport.
Check to Allow Real-Time Transport through Gateway. Click OK.

Next step

Configure StoreFront to use NetScaler Gateway

Unified Gateway

Unified Gateway FAQ at docs.citrix.com

The Unified Gateway wizard in NetScaler 11 relies on Clientless Access and the built-in portal. See Jens Trendelkamp NetScaler Gateway Single Sign-On to Storefront in Clientless Access Mode and Citrix CTX202890 How to Integrate StoreFront into Clientless Access Page from NetScaler When Using CVPN to learn how to enable iFrame in StoreFront so it can be embedded in the Clientless Access portal.

Unified Gateway means Content Switching for NetScaler Gateway. There are two methods of Content Switching:

Create a Content Switching Virtual Server that has a Content Switching policy that directs requests to a NetScaler Gateway
Create a NetScaler Gateway Virtual Server that has Content Switching policies that direct requests to Load Balancing Virtual Servers.

In either case you can only have one Gateway Virtual Server in the Content Switching configuration.

Content Switching vServer with Gateway as Target

When creating a Gateway Virtual Server, you can change the IP Address Type to Non Addressable. This means you can only access the Gateway through a Content Switching Virtual Server.
On the left, go to Traffic management > Content Switching > Policies.
On the right click Add.
Give the policy a name.
Click the plus icon next to the Action field.
Give the Action a name.
Change the selection to NetScaler Gateway Virtual Server.
Click the arrow to select a Gateway Virtual Server and click Create.
Back in the policy screen, enter an expression. There are several options for selecting traffic that should be directed to the Gateway:
- Hostname
- The built-in is_vpn_url expression
- Any path that starts with /Citrix/.
```
http.REQ.HOSTNAME.SET_TEXT_MODE(IGNORECASE).EQ("mygateway.corp.com") && (is_vpn_url || http.REQ.URL.PATH.SET_TEXT_MODE(IGNORECASE).STARTSWITH("/Citrix/"))
```
Click Create when done.
Add or Edit a Content Switching Virtual Server.
Click where it says No Content Switching Policy Bound.
Click the arrow to select a Content Switching policy and click Bind.

Gateway vServer with Load Balancing vServer as Target

Another option is to bind Content Switching policies to a Gateway Virtual Server:

On the left, go to Traffic Management > NetScaler Gateway > Policies > Content Switching.
On the right, click Add to create a Content Switching Policy with an Action that points to a Load Balancing Virtual Server.
On the left, go to NetScaler Gateway > Virtual Servers.
On the right, edit an existing NetScaler Gateway Virtual Server.
On the right in the Advanced Settings section, click Content Switching Policies.
Click where it says No Content Switching Policies.
Select a Content Switching policy that sends traffic to a Load Balancing Virtual Server and click Bind.
Repeat for additional Content Switching policies that redirect to Load Balancing Virtual Servers. You cannot bind Content Switching policies that redirect to NetScaler Gateway Virtual Servers.

StoreFront – Rewrite X-Citrix-Via

When NetScaler Gateway communicates with StoreFront, it adds a header called X-Citrix-Via that contains the FQDN entered in the user’s address bar. StoreFront uses this header to find a matching Gateway object so StoreFront knows how to handle the authentication. In NetScaler 11.0 and newer, you can create a rewrite policy to change this header. This is useful when changing URLs or using DNS aliases for Gateways. See CTX202442 FAQ: Modify HTTP Header X-Citrix-Via on NetScaler for more details.

Here’s a sample rewrite policy for this header:

enable ns feature REWRITE

add rewrite action rwact_storefront replace "HTTP.REQ.HEADER(\"X-Citrix-Via\")" "\"mystorefront.mydomain.com\""

add rewrite policy rwpol_storefront "HTTP.REQ.HEADER(\"X-Citrix-Via\").NE(\"mystorefront.mydomain.com\")" rwact_storefront

bind vpn vserver mygateway-vs -policy rwpol_storefront -priority 100 -type REQUEST

Session Policies for StoreFront – NetScaler Gateway 11

Last Modified: Nov 7, 2020 @ 6:35 am

31 Comments

This page details creation of session profiles and policies for NetScaler Gateway 11 where ICA Only (formerly known as Basic Mode) is checked.

Partly based on Citrix Knowledgebase Article CTX139963 – How to Configure NetScaler Gateway with StoreFront

Session Profiles/Policies CLI Commands

The CLI commands are shown below:

add vpn sessionAction "Receiver Self-Service" -transparentInterception OFF -defaultAuthorizationAction ALLOW -SSO ON -icaProxy ON -wihome "https://storefront.corp.com" -ntDomain Corp -clientlessVpnMode OFF -storefronturl "https://storefront.corp.com"

add vpn sessionAction "Receiver for Web" -transparentInterception OFF -defaultAuthorizationAction ALLOW -SSO ON -icaProxy ON -wihome "https://storefront.corp.com/Citrix/StoreWeb" -ntDomain Corp -clientlessVpnMode OFF

add vpn sessionPolicy "Receiver Self-Service" "REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver" "Receiver Self-Service"

add vpn sessionPolicy "Receiver for Web" "REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver" "Receiver for Web"

Session Profiles

Or use the GUI to create the policies/profiles:

On the left, expand NetScaler Gateway, expand Policies, and click Session.
On the right, switch to the Session Profiles tab, and click Add.
Name the first one ReceiverSelfService or similar. This is for Receiver Self-Service (not in a web browser).
Switch to the Client Experience tab.
Check the Override Global box next to Clientless Access and set it to Allow. Scroll down.
Check the Override Global box next to Plug-in Type and set it to Java.
Check the Override Global box next to Single Sign-on to Web Applications and enable it. Scroll up.
If you need two-factor authentication, the session policy for Receiver Self-Service needs to be adjusted to indicate which authentication field contains the Active Directory password. On the Client Experience tab is Credential Index. This needs to be changed to SECONDARY. Leave the session policy for Web Browsers set to PRIMARY.
On the Security tab, check the Override Global box next to Default Authorization Action and set it to Allow.
On the Published Applications tab, check the Override Global box next to ICA Proxy and set it to ON.
If you only have one domain, then check the Override Global box next to Single Sign-on Domain and enter the name of your Active Directory domain. StoreFront needs to accept this domain name (Configure Trusted Domains).
If you have multiple domains, then leave Single Sign-on Domain field blank, and ensure the LDAP authentication servers have userPrincipalName in the SSO Name Attribute field.
For Account Services Address, enter the Base URL for StoreFront. NetScaler needs to be able to resolve this DNS name.
Highlight the existing session profile and click Add. This copies the settings from the existing profile into the new one.
Change the name of the second Session Profile to ReceiverForWeb or similar.
On the Client Experience tab, Clientless Access should be set to Allow. Scroll down.
Plug-in Type should still be set to Java.
Single Sign-on to Web Applications should be enabled.
If you need two-factor authentication, the session policy for Receiver for Web needs Credential Index set to PRIMARY. Only the Receiver Self-Service policy needs SECONDARY as detailed earlier.
On the Security tab, the Default Authorization Action should still be Allow.
On the Published Applications tab, for the Web Interface Address field, add the path to your Receiver for Web site (e.g. /Citrix/StoreWeb).
Account Services Address only applies to Receiver Self-Service so you can leave it or clear it.
Everything else should be the same. If you only have one domain, then check the Override Global box next to Single Sign-on Domain and enter the NetBIOS name of your Active Directory domain. If you have multiple domains, then leave this field blank and ensure the LDAP authentication servers have userPrincipalName in the SSO Name Attribute field.
Account Services Address is not needed in this profile but there’s no harm in leaving it.
Click Create.

Session Policies

On the right, switch to the Session Policies tab, and click Add.
Name the Policy ReceiverSelfService or similar.
Change the Request Profile to ReceiverSelfService.
Either type in or use the Expression Editor link to build the following expression:
```
REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver
```
Then click Create.
Add another policy, and name it ReceiverForWeb or similar.
Change the Action to ReceiverForWeb.
In the Expression box, either type in the following or use the Expression Editor. It’s the same as the previous expression, except it’s NOTCONTAINS instead of CONTAINS.
```
REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver
```
Click Create.

Next Step

Create NetScaler Gateway Virtual Server

NetScaler Gateway 11 LDAP Authentication

Last Modified: Nov 6, 2020 @ 7:30 am

78 Comments

Navigation

Verify Domain Controller Certificates
LDAP Load Balancing
Create LDAP Authentication Server
Authentication Feedback and Global Licenses
Multiple Active Directory Domains

Verify LDAPS

Use the tool ldp.exe to verify that the Domain Controllers have valid certificates installed and the service account is able to bind to the LDAP tree.

ldp.exe is included with the Remote Server Administration Tools (AD DS Snap-Ins and Command-Line Tools)
Run ldp.exe
Open the Connection menu and click Connect.
Check the box next to SSL. Change the port to 636. Then enter the FQDN of a Domain Controller and click OK.
If it connected successfully, you can then attempt a bind. If the connection was unsuccessful then there’s probably an issue with the certificate installed on the Domain Controller.
Open the Connection menu and click Bind.
Change the Bind type to Simple bind. Then enter the service account credentials. You can use DOMAIN\Username or you can use Username@Domain.com. Click OK.
Look on the right pane to verify a successful bind. If not, fix the credentials and try again.
Once you have successfully binded, you can view the directory tree by opening the View menu and click Tree.
Click the drop-down to view the directory partitions.
Repeat these steps to verify each Domain Controller and any load balanced LDAPS.

LDAP Load Balancing

Before you create an LDAP authentication policy, setup LDAPS load balancing:

You can create multiple load-balancing Virtual Servers to load balance multiple domains. These load-balancing Virtual Servers can share the same VIP if their port numbers are different. Or you can use a different VIP for each domain.

LDAP Server

To create the LDAP Authentication Server, do the following:

On the left, expand Authentication and click Dashboard.
On the right, click Add.
In the Choose Server Type drop-down, select LDAP.
Enter LDAP-Corp as the name. If you have multiple domains, you’ll need a separate LDAP Server per domain so make sure you include the domain name.
Change the selection to Server IP. Enter the VIP of the load balancing vServer for LDAP.
Change the Security Type to SSL.
Enter 636 as the Port. Scroll down.
In the Connection Settings section, in the Base DN field, enter your Active Directory DNS domain name in LDAP format.
Enter the credentials of the LDAP bind account in userPrincipalName format. Domain\Username also works.
Check the box next to BindDN Password and enter the password. Scroll down.
In the Other Settings section, use the drop-down next to Server Logon Name Attribute, Group Attribute, and Sub Attribute Name to select the default fields for Active Directory.
On the right, check the box next to Allow Password Change.
Note: there is a checkbox for Validate LDAP Server Certificate. If you want to do this, see Citrix Discussions for instructions for loading the root certificate to /nsconfig/truststore.
If you want to restrict access to only members of a specific group, in the Search Filter field, enter memberOf=<GroupDN>. See the example below:
memberOf=CN=CitrixRemote,OU=Citrix,DC=corp,DC=local

You can add :1.2.840.113556.1.4.1941: to the query so it searches through nested groups. Without this users will need to be direct members of the filtered group.

memberOf:1.2.840.113556.1.4.1941:=CN=CitrixRemote,OU=Citrix,DC=corp,DC=local

Citrix CTX132802 How to Use the ldapsearch Utility on the NetScaler Gateway Enterprise Edition Appliance to Validate a Search Filter
1. An easy way to get the full distinguished name of the group is through Active Directory Administrative Center. Double-click the group object and switch to the Extensions page. On the right, switch to the Attribute Editor tab.
2. Or in Active Directory Users & Computers, enable Advanced view, browse to the object (don’t use Find), double-click the object, and switch to the Attribute Editor tab.
3. Scroll down to distinguishedName, double-click it and then copy it to the clipboard.
4. Back on the NetScaler, in the Search Filter field, type in memberOf= and then paste the Distinguished Name right after the equals sign. Don’t worry about spaces.
Scroll down and click More.
For Nested Group Extraction, if desired, change the selection to Enabled.
Set the Group Name Identifier to samAccountName.
Set the Group Search Attribute to memberOf. Select << New >> first.
Set the Group Search Sub-Attribute to CN. Select << New >> first
For the Group Search Filter field, see CTX123795 Example of LDAP Nested Group Search Filter Syntax.

Scroll down and click Create.

add authentication ldapAction Corp-Gateway -serverIP 10.2.2.210 -serverPort 636 -ldapBase "dc=corp,dc=local" -ldapBindDn "corp\\ctxsvc" -ldapBindDnPassword Passw0rd -ldapLoginName samaccountname -searchFilter "memberOf=CN=Citrix Remote,CN=Users,DC=corp,DC=local" -groupAttrName memberOf -subAttributeName CN -secType SSL -passwdChange ENABLED

The status of the LDAP Server should be Up.
The Authentication Dashboard doesn’t allow you to create the LDAP Policy at this time. Instead the LDAP Policy will be created later when you bind the LDAP Server to the NetScaler Gateway vServer.

Authentication Feedback and Licenses

On the left, under NetScaler Gateway, click Global Settings.
On the right, in the right column, click Change authentication AAA settings.
If you are using Gateway features that require Gateway Universal licenses, then change the Maximum Number of Users to the number of Gateway Universal licenses you have installed on this appliance. This field has a default value of 5, and administrators frequently forget to change it, thus only allowing 5 users to connect.
If desired, check the box for Enable Enhanced Authentication Feedback. This feature provides a message to users if authentication fails. The message users receive include password errors, account disabled or locked, or the user is not found, to name a few. Click OK.
```
set aaa parameter -enableEnhancedAuthFeedback YES -maxAAAUsers 200
```

Next Step

For two-factor, configure RADIUS Authentication
Otherwise, Configure NetScaler Gateway Session Policies

Multiple Domains

To support multiple Active Directory domains on a NetScaler Gateway, you create multiple LDAP authentication policies, one for each Active Directory domain, and bind all of the LDAP policies to the NetScaler Gateway Virtual Server. When the user logs into NetScaler Gateway, only the username and password are entered. The NetScaler will then loop through each of the LDAP policies in priority order until it finds one that contains the entered username/password.

What if the same username is present in multiple domains? As NetScaler loops through the LDAP policies, as soon as it finds one with the specified username, it will try to authenticate with that particular LDAP policy. If the password doesn’t match the user account for the attempted domain then a failed logon attempt will be logged in that domain and NetScaler will try the next domain.

Unfortunately, the only way to enter a realm name during user authentication is to require users to login using userPrincipalNames. To use userPrincipalName, set the LDAP Policy/Server with the Server Logon Name Attribute set to userPrincipalName.

You can even do a combination of policies: some with samAccountName and some with userPrincipalName. The samAccountName policies would be searched in priority order and the userPrincipalName policies can be used to override the search order. Bind the userPrincipalName policies higher (lower priority number) than the samAccountName policies.

Note: NetScaler 11.0 build 64 supports adding a domain name drop-down list to the logon page. Then use Cookie expressions in the auth policies and session policies. However, this probably doesn’t work for Receivers. See CTX203873 How to Add Drop-Down Menu with Domain Names on Logon Page for NetScaler Gateway 11.0 64.x and later releases for details. 💡
User-added image

After authentication is complete, a Session Policy will be applied that has the StoreFront URL. The NetScaler Gateway will attempt to log into StoreFront using SSO so the user doesn’t have to login again. When logging into NetScaler Gateway, only two fields are required: username and password. However, when logging in to StoreFront, a third field is required: domain name. So how does NetScaler specify the domain name while logging in to StoreFront?

There are two methods of specifying the domain:

Configure multiple session policies with unique Single Sign-on Domains. Inside the Session Policy is a field called Single Sign-on Domain for specifying the domain name. If there is only one Active Directory domain then you can use the same Session Policy for all users. However, if there are multiple domains then you would need multiple Session Policies, one for each Active Directory domain. But as the NetScaler loops through the LDAP policies during authentication, once a successful LDAP policy is found, you need a method of linking an LDAP policy with a Session Policy that has the corresponding SSO Domain. This is typically done using AAA groups. This method is not detailed here but the general steps are: In the LDAP policy, specify a Default Authentication Group. Create a AAA group that matches it. Then bind the corresponding Session Policy to that AAA group.
Alternatively, configure the LDAP policy/server to extract the user’s UPN and then authenticate to StoreFront using UPN. This is the easiest method but some domains don’t have userPrincipalNames configured correctly.

This userPrincipalName method is detailed below:

In each of your NetScaler LDAP policies/servers, in the Other Settings section, in the SSO Name Attribute field, enter userPrincipalName (select –<< New >>– first). Make sure there are no spaces after this name. NetScaler will use this attribute to authenticate the user against StoreFront.
In StoreFront Console, right-click the Store, and click Manage Authentication Methods.
On the right, click the gear icon, and then click Configure Trusted Domains.
In the Trusted domains box, select Any domain.
Or add your domains in DNS format. The advantage of entering domain names is that you can select a default domain if internal users forget to enter a domain name during login. The DNS format is required for UPN logins (e.g. SSO from NetScaler Gateway).
On the NetScaler Gateway Virtual Server, bind LDAP authentication polices in priority order. It will search them in order until it finds a match.
In your session policies, make sure Single Sign-on Domain is not configured. Since NetScaler is using the userPrincipalName, there’s no need to specify a domain. If Single Sign-on Domain is configured, then Single Sign-on authentication will fail.

SSL Virtual Servers – NetScaler 11

Last Modified: Nov 6, 2020 @ 7:10 am

86 Comments

This page contains generic instructions for all SSL Virtual Servers including: Load Balancing, NetScaler Gateway, and Content Switching.

Navigation

Cipher Group
Default SSL Profile
SSL vServer Configuration – Bind Cert, Ciphers, ECC, and STS
SSL Tests
SSL Redirect – Down vServer Method
SSL Redirect – Responder Method

💡 = Recently Updated

Cipher Group

References:

Citrix Blogs – Scoring an A+ at SSLlabs.com with Citrix NetScaler – 2016 update 💡
CJHarms Perfect Forward Secrecy and NetScaler MPX Revisited
Anton van Pelt Make your NetScaler SSL VIPs more secure (Updated)
Citrix CTX201710 Cipher/Protocol Support Matrix of NetScaler Appliances:
- VPX 11.0 build 64 and older support fewer ciphers than MPX. This was corrected in 11.0 build 65.

Ryan Butler has a PowerShell script at Github that can automate NetScaler SSL configuration to get an A+. 💡
The easiest way to create a cipher group is from the CLI. See Citrix Blogs Scoring an A+ at SSLlabs.com with Citrix NetScaler – 2016 update for cipher group CLI commands.
Go to Traffic Management > SSL > Cipher Groups.
On the right, click Add.
Name it Modern or similar.
In the middle, click Add.
Use the search box to find a particular cipher.
Check the box next to one of the results and click the arrow to move it to the right. See Citrix Blogs Scoring an A+ at SSLlabs.com with Citrix NetScaler – 2016 update for recommended ciphers. The recommended ciphers vary based on the hardware platform and support for older clients.
Click Create when done.

Default SSL Profile

In NetScaler 11.0 build 64 and newer, SSL Profiles are much more functional. You can use SSL Profiles to disable SSLv3, bind ciphers, and bind ECC curves.

Note: the default SSL Profile affects all SSL Virtual Servers unless you create additional SSL Profiles and bind the additional SSL Profiles to individual SSL Virtual Servers.

Citrix CTX201710 Cipher/Protocol Support Matrix of NetScaler Appliances – VPX 11.0 build 64 and older supports fewer ciphers than MPX. This was corrected in 11.0 build 65.

NetScaler 11.0 build 65 adds TLS 1.2 for back-end connections from VPX appliances. However, it does not appear to be possible to enable TLS 1.2 on SSL Profiles on VPX. If you don’t enable the default SSL profiles then you can enable TLS 1.2 on each Service Group or Service. If you are using VPX, don’t enable Default SSL profile as detailed in this section. 💡

NetScaler 11.0 build 64 and older does not do a proper handshake with TLS 1.2 IIS servers. To work around this problem, disable TLS 1.2 on the load balancing services as detailed at CTX205578 Back-End Connection on TLS 1.1/1.2 from NetScaler to IIS Servers Break. Or upgrade to 11.0 build 65.

Also see CTX205576 NetScaler to Back-End SSL Handshake Failure on Disabling SSL 3.0 on Back-End (Physical) Servers. These articles describe both SSL services and SSL_BRIDGE services.

Go to Traffic Management > SSL.
On the right, in the right column, click Change advanced SSL settings.
Near the bottom, check the box next to Enable Default Profile. Note: this will change SSL settings on all SSL Virtual Servers to match the default SSL profile. You might want to do this during a maintenance window. Click OK when done.
If you go back into Advanced SSL Settings, notice that the Default Profile is enabled and there’s no way to disable it.
To change the default SSL profile, on the left, go to System > Profiles.
On the right, switch to the SSL Profile tab.
Highlight the frontend or backend default profile and click Edit. Note: this is the same place where you can create more SSL profiles.
Notice that SSLv3 is disabled by default.
If you do any SSL Offload (SSL on the client side, HTTP on the server side) then you’ll need to edit the Basic Settings section and enable SSL Redirect. Or you can create a new SSL Profile with this option enabled. It’s near the bottom of the section. With this option enabled, any 301/302 redirects from the server with HTTP locations are rewritten to HTTPS locations. You might need this option for StoreFront load balancing if doing SSL Offload.
It’s currently not possible to bind user-defined cipher groups using the GUI but you can easily do this using the CLI. First unbind the DEFAULT cipher group and then bind the Modern cipher group.
```
unbind ssl profile ns_default_ssl_profile_frontend -cipherName DEFAULT
bind ssl profile ns_default_ssl_profile_frontend -cipherName Modern
```
If you edit one of your SSL Virtual Servers, there’s an SSL Profile section indicating that the default profile is being used. You can change the binding to a different SSL Profile.

Bind Certificate, Bind Cipher Group, Disable SSLv3, Enable STS

NetScaler 11.0 build 64 and older do not do a proper handshake with TLS 1.2 IIS servers. To work around this problem, disable TLS 1.2 on the load balancing services as detailed at CTX205578 Back-End Connection on TLS 1.1/1.2 from NetScaler to IIS Servers Break. Also see CTX205576 NetScaler to Back-End SSL Handshake Failure on Disabling SSL 3.0 on Back-End (Physical) Servers. These articles describe both SSL services and SSL_BRIDGE services.

When creating the SSL Virtual Server, on the left, in the Certificates section, click where it says No Server Certificate.
Click where it says Click to select.
Select a certificate and click Select.

Click Bind.

bind ssl vserver MyvServer -certkeyName MyCert

If the SSL Parameters section isn’t added, on the right, in the Advanced Settings column, click SSL Parameters.
On the left, in the SSL Parameters section, click the pencil icon.
Uncheck the box next to SSLv3. This removes a security vulnerability. Make sure TLSv11 and TLSv12 are enabled. Click OK.
```
set ssl vserver MyvServer -ssl3 DISABLED -tls11 ENABLED -tls12 ENABLED
```
On the right, in the Advanced Settings column, click SSL Ciphers.
On the left, in the SSL Ciphers section, select the previously created Modern Cipher Group and click OK.
```
unbind ssl vserver MyvServer -cipherName ALL
bind ssl vserver MyvServer -cipherName Modern
```
If you see a warning about No usable ciphers, click OK and ignore it.
SSL Virtual Servers created on newer versions of NetScaler will automatically have ECC Curves bound to them. However, if this appliance was upgraded from an older version then the ECC Curves might not be bound. On the right, in the Advanced Settings section, click ECC Curve.
On the left, in the ECC Curve section, click where it says No ECC Curve.
Click to select.

Choose ALL and click Select.

bind ssl vserver MyvServer -eccCurveName ALL

Click Bind.

Consider enabling Strict Transport Security by creating a rewrite policy and binding it to this SSL Virtual Server. See Anton van Pelt Make your NetScaler SSL VIPs more secure (Updated). Also see CTX205221 How Do I Do HSTS on NetScaler?

enable ns feature rewrite

add rewrite action insert_STS_header insert_http_header Strict-Transport-Security "\"max-age=157680000\""

add rewrite policy insert_STS_header true insert_STS_header

bind lb vserver MyvServer -policyName insert_STS_header -priority 100 -gotoPriorityExpression END -type RESPONSE

SSL Tests

After you’ve created an SSL Virtual Server, run the following tests:

Go to https://www.digicert.com/help/ to verify the certificate chain.
Go to https://www.ssllabs.com/ssltest/ and check the security settings of the website.

SSL Redirect – Down vServer Method

If you created an SSL Virtual Server that only listens on SSL 443, then users must enter https:// when navigating to the website. To make it easier for the users, create another load balancing Virtual Server on the same VIP but listens on HTTP 80 and then redirects the user’s browser to reconnect on SSL 443.

The Down Virtual Server Method is easy but the Redirect Virtual Server must be down in order for the redirect to take effect. Another option is to use Responder policies to perform the redirect.

On the left, under Traffic Management > Load Balancing, click Virtual Servers.
On the right, find the SSL Virtual Server you’ve already created, right-click it and click Add. Doing it this way copies some of the data from the already created Virtual Server.
Change the name to indicate that this new Virtual Server is an SSL Redirect.
Change the Protocol to HTTP on Port 80.
The IP Address should already be filled in. It must match the original SSL Virtual Server. Click OK.
Don’t select any services. This vServer must intentionally be marked down so the redirect will take effect. Click Continue.
On the right, in the Advanced Settings column, click Protection.
In the Redirect URL field, enter the full URL including https://. For example: https://storefront.company.com/Citrix/StoreWeb. Click OK.
Click Done.
When you view the SSL redirect Virtual Server in the list, it will have a state of DOWN. That’s OK. The Port 80 Virtual Server must be DOWN for the redirect to work.

SSL Redirect – Responder Method

The Down Virtual Server Method is easy but the Redirect Virtual Server must be down in order for the redirect to take effect. Another option is to use Responder policies to perform the redirect. This method requires the Redirect Virtual Server to be UP.

Create a dummy Load Balancing service. This dummy service can be bound to multiple Redirect Virtual Servers.
Name it AlwaysUp or similar.
Use a loopback IP address (e.g. 127.0.0.1). After the service is created it changes to a NetScaler-owned IP.
Click the More link.
This dummy service must always be UP so uncheck the box next to Health Monitoring. Click OK and then click Done.
```
add server 127.0.0.1 127.0.0.1
add service AlwaysUp 127.0.0.1 HTTP 80 -healthMonitor NO
```
On the left, expand AppExpert and click Responder.
If Responder is not enabled, right-click Responder and click Enable Feature.
```
enable ns feature RESPONDER
```
Under Responder, click Actions.
On the right, click Add.
Give the action a name.
Change the Type to Redirect.

Enter an expression. The following expression can be used by multiple Redirect Virtual Servers. Or you can create a Responder Action with a more specific Target. Click Create.

"https://" + HTTP.REQ.HOSTNAME.HTTP_URL_SAFE + HTTP.REQ.URL.PATH_AND_QUERY.HTTP_URL_SAFE

add responder action http_to_ssl_redirect_responderact redirect "\"https://\" + HTTP.REQ.HOSTNAME.HTTP_URL_SAFE + HTTP.REQ.URL.PATH_AND_QUERY.HTTP_URL_SAFE" -responseStatusCode 302

On the left, under Responder, click Policies.
On the right, click Add.
Give the policy a name.
Select the previously created Responder action.

For the expression, enter the following. Then click Create.

HTTP.REQ.IS_VALID

add responder policy http_to_ssl_redirect_responderpol HTTP.REQ.IS_VALID http_to_ssl_redirect_responderact

Create a Load Balancing Virtual Server with Protocol HTTP and Port 80. The VIP should match an existing SSL Virtual Server or NetScaler Gateway Virtual Server.
Bind the Dummy (AlwaysUp) service, and click OK.
On the right, in the Advanced Settings column, click Policies.
Click the plus icon in the top right of the Policies box.
Select Responder and click Continue.

Select the Redirect Responder policy and click Bind. Then click Done.

add lb vserver MyvServer-HTTP-SSLRedirect HTTP 10.2.2.201 80

bind lb vserver storefront.corp.com-HTTP-SSLRedirect AlwaysUp

bind lb vserver storefront.corp.com-HTTP-SSLRedirect -policyName http_to_ssl_redirect_responderpol -priority 100 -gotoPriorityExpression END -type REQUEST

The primary advantage of this method is that the Redirect Virtual Server is UP.

Domain Controller (LDAPS) Load Balancing – NetScaler 11

Last Modified: Nov 7, 2020 @ 6:35 am

32 Comments

Navigation

Overview
Monitor to verify that LDAP server is UP
Server Objects
Service Groups
Virtual Server

Overview

If you plan to use LDAP (Active Directory) for NetScaler Gateway or NetScaler management authentication, load balance the Domain Controllers that are used for authentication.

An alternative to load balancing is to configure NetScaler Gateway and NetScaler management authentication with multiple authentication policies, each pointing to a single Domain Controller. However, NetScaler will try each authentication policy until it finds one that works. If the user enters a wrong password and if you have three authentication policies pointing to different Domain Controllers in the same domain then three different failure attempts will be recorded thus causing premature account lockout. Use Load Balancing to avoid this behavior.

This page details LDAPS, aka Secure LDAP. This protocol requires certificates to be installed on the Domain Controllers. When a user’s password expires, Active Directory does not allow password changes over clear text LDAP so LDAPS must be used instead. Make sure you have certificates installed on your Domain Controllers. The easiest way to accomplish that is to deploy a Microsoft Certificate Authority. Once that’s done the Domain Controllers will request certificates automatically.

An ldaps monitor can be used to verify that the Domain Controller is functional. The ldaps monitor will login as an account, perform an LDAP query, and look for a successful response. The ldaps monitor uses a service account to login. Make sure the service account’s password does not expire. Domain User permissions are sufficient. Since this monitor is a Perl script, it uses NSIP as the source IP.

If you have Domain Controllers in multiple datacenters, you can create multiple load balancing Virtual Servers and cascade them so that the local Domain Controllers are used first, and if they’re not available, then the Virtual Server fails over to Domain Controllers in remote datacenters.

The Load Balancing Virtual Server for LDAPS can be TCP or SSL_TCP:

If the protocol is TCP, then SSL-encrypted LDAP traffic is not terminated on the NetScaler, and is simply forwarded to the LDAP servers. If your LDAP client needs to verify the LDAP server certificate, then this Load Balancing configuration will not work, since each back-end LDAP server will have a different certificate.
If your Load Balancing Virtual Server is protocol SSL_TCP, then a certificate must be installed on the NetScaler and bound to the Load Balancing Virtual Server. SSL is terminated at the NetScaler and re-encrypted before sending it to the destination Domain Controller. The primary benefit of NetScaler SSL termination is that your LDAP clients can verify the Virtual Server SSL certificate.

When NetScaler uses a local (same appliance) load balanced Virtual Server for LDAPS authentication, the traffic is sourced from the NetScaler SNIP (Subnet IP). When NetScaler uses a direct connection to a Domain Controller without going through a local Load Balancing Virtual Server, or if NetScaler uses a remote (different appliance) Load Balancing VIP, then the traffic is sourced from the NetScaler NSIP (NetScaler IP). Adjust firewall rules accordingly.

LDAPS Monitor

Note: Perl monitor uses NSIP as the source IP.

In the NetScaler Configuration Utility, expand Traffic Management, expand Load Balancing, and click Monitors.
On the right, click Add.
Name the monitor ldaps-Corp or similar. The ldaps monitor logs into Active Directory, performs an LDAP query, and looks for a successful response. The monitor configuration has domain specific information, so if you have multiple Active Directory domains, then you will need multiple ldaps monitors. Include the domain name in the monitor name.
Change the Type to LDAP.
Scroll down and check the box next to Secure.
Scroll back up and switch to the Special Parameters tab.
On the Special Parameters tab, use the Script Name drop-down list to select the nsldap.pl file.
In the Base DN field, enter your domain name in LDAP format (e.g. dc=company,dc=com)
In the Bind DN field, enter the UPN login (e.g. ctxsvc@company.com) of a service account in the domain that can browse all objects. Any normal Domain User should be sufficient. Just make sure the password doesn’t expire.
In the Filter field, enter cn=builtin. This limits the search results.
In the Password field, enter the password for the service account. Make sure there is no semicolon in the password or the script will be unable to parse the parameters.

Click Create.

add lb monitor LDAP-Corp LDAP -scriptName nsldap.pl -dispatcherIP 127.0.0.1 -dispatcherPort 3013 -password Passw0rd -secure YES -baseDN "dc=corp,dc=local" -bindDN "corp\\ctxsvc" -filter cn=builtin

If you have multiple domains, then create additional monitors: one for each domain.

Servers

On the left, expand Traffic Management, expand Load Balancing, and click Servers.
On the right, click Add.
Enter a descriptive server name, usually it matches the actual server name.
Enter the IP address of the server.

Enter comments to describe the server. Click Create.

add server AD01 10.2.2.11
add server AD01 10.2.2.12

Continue adding Domain Controllers.

Service Groups

On the left, expand Traffic Management, expand Load Balancing, and click Service Groups.
On the right, click Add
.
You will create one Service Group per datacenter. Enter a name reflecting the name of the data center. Also, you will create a set of service groups per Active Directory domain so include the domain name.
Change the Protocol to SSL_TCP. Scroll down, and click Continue.
On the left, in the Service Group Members section, click where it says No Service Group Member.
If you did not create server objects then enter the IP address of a Domain Controller in this datacenter. If you previously created a server object then change the selection to Server Based, and select the server object. In the Port field, enter 636 (LDAPS).
Note: Any Domain Controller you add to this list must have an SSL certificate installed. The easiest way to install SSL certificates on the Domain Controllers is with Active Directory Certificate Services since it installs the certificates automatically.
To add more members, click where it says 1 Service Group Member, and then click Add. Click Close when done.
On the right, in the Advanced Settings column, click Monitors.
On the left, in the Monitors section, click where it says No Service Group to Monitor Binding.
Click the arrow next to Click to select.
Select your new LDAPS monitor and click Select.
Click Bind.
To verify the member is up, click in the Service Group Members section.
Highlight a member, and click Monitor Details.
It should say Probe successful. Click OK.
If the monitor doesn’t work, use ldp.exe to verify the Domain Controller certificate.

Click Done to finish creating the Service Group.

add serviceGroup svcgrp-LDAP-Corp SSL_TCP
bind serviceGroup svcgrp-LDAP-Corp AD01 636
bind serviceGroup svcgrp-LDAP-Corp AD02 636
bind serviceGroup svcgrp-LDAP-Corp -monitorName LDAP-Corp

The Service Group is displayed as UP. If not, click the refresh icon on the top right.
Add additional service groups for Domain Controllers in each data center.

Virtual Server

Create or import a certificate that matches the FQDN that resolves to the new Load Balancing VIP for LDAPS.
On the left, expand Traffic Management, expand Load Balancing, and click Virtual Servers.
On the right, click Add.
Name it lbvip-LDAPS-Corp-HQ or similar. You will create one Virtual Server per datacenter so include the datacenter name. Also, each domain has a separate set of Virtual Servers so include the domain name.
Change the Protocol drop-down to SSL_TCP.
Enter a Virtual IP. This VIP cannot conflict with any other IP/Port already being used. You can use an existing VIP that is not already listening on TCP 636.
Enter 636 as the Port. Click OK.
On the left, in the Service Group section, click where it says No Load Balancing Virtual Server ServiceGroup Binding.
Click the arrow next to Click to select.
Select the previously created Service Group, and click Select.
Click Bind.
Click Continue.
On the left, in the Certificates section, click where it says No Server Certificate.
Click the arrow next to Click to select.
Select a certificate that matches the FQDN that will resolve to this VIP. Click Select.
Click Bind.

Click Continue.

add lb vserver lbvip-LDAP-Corp SSL_TCP 10.2.2.210 636 -persistenceType NONE -cltTimeout 9000

bind lb vserver lbvip-LDAP-Corp svcgrp-LDAP-Corp

If you haven’t enabled the Default SSL Profile, then perform other normal SSL configuration including: disable SSLv3, and bind a Modern Cipher Group.

bind ssl vserver MyvServer -certkeyName MyCert

set ssl vserver MyvServer -ssl3 DISABLED -tls11 ENABLED -tls12 ENABLED

unbind ssl vserver MyvServer -cipherName ALL

bind ssl vserver MyvServer -cipherName Modern

bind ssl vserver MyvServer -eccCurveName ALL

Click Done to finish creating the Virtual Server.
The new Virtual Server should show as Up.
Create additional Virtual Servers for each datacenter. These additional Virtual Servers do not need a VIP so change the IP Address Type to Non Addressable. Only the first Virtual Server will be accessible.
```
add lb vserver lbvip-LDAP-Corp-Backup SSL_TCP 0.0.0.0 0
```
Notice that the additional datacenter Virtual Servers show up with an IP Address of 0.0.0.0 and port of 0.
After you are done creating a Virtual Server for each datacenter, right-click the primary datacenter’s Virtual Server, and click Edit.
On the right, in the Advanced Settings column, click Protection.
On the left, in the Protection section, change the Backup Virtual Server to one of the other datacenter Virtual Servers. If all of the services in this datacenter are DOWN, the backup Virtual Server will be used instead. You can cascade multiple Virtual Servers using this method. Click OK and Done.
```
set lb vserver lbvip-LDAP-Corp -backupVServer lbvip-LDAP-Corp-Backup
```

Clear Text LDAP

Citrix Command Center does not support Secure LDAP so you will need to do the following:

Create a regular LDAP monitor that does not have the secure box checked.
Create Service Groups of Protocol TCP and Port 389.
Create a Load Balancing Virtual Server of Protocol TCP on port 389. Bind the Service Groups to it.

Next Steps

You may now use this Virtual IP in your LDAP authentication policies for NetScaler Gateway or NetScaler management login.

NetScaler SDX 10.5

Last Modified: Nov 6, 2020 @ 7:09 am

53 Comments

Navigation

SDX IP Configuration
Service VM Firmware – Upgrade
XenServer – Upgrade
XenServer Supplemental Pack
XenServer Hotfixes
Service VM Hostname
Service VM Time Zone and NTP
Licensing
Service VM Alerting
Service VM nsroot Password and AAA
SSL Certificate and Encryption
XenServer LACP Channels
VPX Instances:
Service VM Monitoring
Service VM Backup

SDX IP Configuration

Default IP for Management Service VM is 192.168.100.1/16 bound to interface 0/1. Use laptop with crossover cable to reconfigure. Point browser to http://192.168.100.1. Default login is nsroot/nsroot.

Default IP for XenServer is 192.168.100.2/16. Default login is root/nsroot. Use the Management Service virtual machine to configure. XenServer and Management Service IPs must be on the same subnet.

When you first login to the SDX Service virtual machine, the Setup Wizard appears. In the Network Configuration page, configure the IP addresses. Management Service IP Address and XenServer IP Address must be different but on the same subnet. Scroll down.
In the System Settings page, select the time zone.
Check the box next to Change Password, enter the new password. Click Continue.
In the Manage Licenses section, allocate licenses normally. Click Continue when done.
Then click Done.

To modify the network configuration of the SDX appliance:

Switch to the Configuration tab.
In the navigation pane, click System.
In the System pane, under Setup Appliance, click Network Configuration.
In the Modify Network Configuration dialog box, specify values for the following parameters:
- Interface*—The interface through which clients connect to the Management Service. Possible values: 0/1, 0/2. Default: 0/1.
- XenServer IP Address*—The IP address of the XenServer.
- Management Service IP Address*—The IP address of the Management Service.
- Netmask*—The netmask for the subnet in which the SDX appliance is located.
- Gateway*—The default gateway for the network.
- DNS Server—The IP address of the DNS server.
Click OK.

Another way to login to the Management Service virtual machine is through the serial port. This is actually the XenServer Dom0 console. Once logged in to XenServer, run ssh 169.254.0.10 to access the Management Service virtual machine. Then follow instructions at http://support.citrix.com/article/CTX130496 to change the IP.

The console of the Management Service virtual machine can be reached by running the following command in the XenServer Dom0 shell (SSH or console):

xe vm-list params=name-label,dom-id name-label=”Management Service VM“

Then run /usr/lib/xen/bin/xenconsole <dom-id>.

Service VM Firmware – Upgrade

If the webpage says NetScaler SDX on top then you are connected to the Service VM.
Switch to the Configuration tab.
In the navigation pane, expand Management Service, and then click Software Images.
In the right pane, click Upload.
In the Upload Management Service Software Image dialog box, click Browse, navigate to the folder that contains the build-svm file, and then double-click the build file.
Click Upload.

To upgrade the Management Service:

In the navigation pane, click System.
In the System pane, under System Administration, click Upgrade Management Service.
In the Upgrade Management Service dialog box, in Build File, select the file of the build to which you want to upgrade the Management Service.
If you see a Documentation File field, ignore it.
Click OK.
Click Yes if asked to continue.
If desired, go back to the Software Images node and delete older firmware files.

XenServer – Upgrade

SDX Service VM 10.1 or newer requires XenServer 6.1 to be installed on the SDX appliance. Make sure you use the XenServer 6.1 media that is specific to SDX. It should be named XenServer-6.1.0-install-sdx.iso. Installing XenServer will cause the physical appliance (and all VPX instances) to reboot.

Switch to the Configuration tab.
In the navigation pane, expand Management Service, and then click XenServer Files.
In the right pane, in the ISO Images tab, click Upload.
In the Upload XenServer ISO Image File dialog box, click Browse, navigate to the folder that contains the build file, and then double-click the build file.
Click Upload.

To upgrade the XenServer software:

In the Configuration tab navigation pane, click System.
In the details pane, click Upgrade XenServer.
In the Upgrade XenServer section, select the Image file from the list. Then click OK.
Click Yes to confirm that a connection failure will occur.

XenServer Supplemental Pack

A full reboot of the physical appliance will occur.

Download the XenServer 6.1 Supplemental Pack from the same download page containing the SDX Service VM firmware. It’s in the Additional Components section.
On the Configuration page, on the left, expand Management Service and click XenServer Files.
On the right, switch to the Supplemental Packs tab and click Upload.
Browse to the Supplemental Pack and click Upload.
Select the Supplemental Pack and click Install.
Click Yes when prompted to reboot the appliance.

XenServer Hotfixes

A full reboot of the physical appliance will occur.

On the left, expand Management Service and click XenServer Files.
On the right, switch to the Hotfixes tab and click Upload.
Upload XenServer 6.1 Hotfix 44.
Also upload XenServer 6.1 Hotfix 45.
Also upload XenServer 6.1 Hotfix 48.
Highlight one of the hotfixes and click Apply.
Click Yes when asked to apply.
Apply the next hotfix.
Click Yes when asked to apply. Repeat for the remaining hotfixes.
On the left, click the System node.
On the right, in the right column, click Reboot Appliance.
Click Yes when asked to reboot.

Service VM Hostname

On the Configuration tab, click System.
In the right pane, click Change Hostname in the System Settings section.
Enter a new hostname and click OK.

Service VM Time Zone and NTP

Go to Configuration tab and click System on the left.
On the right, under System Settings click Change Time Zone.
Select the time zone. For Central time, look for UTC-0500 and Chicago.

To configure an NTP server:

On the Configuration tab, in the navigation pane, expand System, and then click NTP Servers.
To add a new NTP server, in the right pane, click Add.
In the Create NTP Server dialog box, set the following parameters:
- Server Name/IP Address*—The domain name of the NTP server or the IP address of the NTP server. The name or IP address cannot be changed for an existing NTP server.
- Preferred—Synchronize with this server first. Applicable if more than one server is configured.
Click Add.
In the right pane click NTP Synchronization.
In theNTP Synchronization dialog box, select Enable NTP Sync. Click OK.

Licensing

To upload a license file to the SDX appliance:

Login to Citrix.com and go to Account.
Click Allocate Licenses, find a NetScaler SDX license, and allocate it. There is no need to specify a hostname. You can use the same license file on multiple SDX appliances.
On the Configuration tab, in the navigation pane, expand System, and then click Licenses.
In the right pane, click Manage Licenses.
In the Manage Licenses page, select Upload License Files and click Upload.
In the Upload License File dialog box, do the following:
1. Click Browse.
2. Navigate to the folder that contains the license file you want to upload, and then double-click the license file.
3. Click Upload.
In the License Files pane, click Apply Licenses.
In the Confirm message box, click Yes.

Service VM Alerting

Syslog:

On the Configuration tab, expand System > Notifications and click Syslog Servers.
In the right pane click the Add button.
Enter a name for the server.
Enter the IP address of the Syslog server.
Select log levels and click Add.

Mail Notification

On the Configuration tab, expand System > Notifications and click Email.
In the right pane, on the SMTP Server tab, click Add.
Enter the DNS name of the mail server and click Create.
In the right pane, switch to the Email Distribution List tab and click Add.
Enter a name for the mail profile.
Enter the destination email address and click Create.
The instances will send SNMP traps to the Service VM. To get alerted for these traps, in the Configuration page, in the navigation pane, expand NetScaler, expand Events, and click Event Rules.
On the right, click Add.
Give the rule a name.
Select the Major and Critical severities and move them to the right. Scroll down.
For the other sections, if you don’t configure anything then you will receive alerts for all of the devices, categories, and failure objects. If you configure any of them then only the configured entities will be alerted. Scroll down.
Click Save.
Select an Email Distribution List and click Done.

Service VM nsroot Password and AAA

To change the password of the default user account:

On the Configuration tab, in the navigation pane, expand System, and then click Users.
In the Users pane, click the default user account, and then click Edit.
In the Configure System User dialog box, in Password and Confirm Password, enter the password of your choice. Click OK.

To create a user account:

In the navigation pane, expand System, and then click Users. The Users pane displays a list of existing user accounts, with their permissions.
To create a user account, click Add.
In the Create System User or Modify System User dialog box, set the following parameters:
- Name*—The user name of the account. The following characters are allowed in the name: letters a through z and A through Z, numbers 0 through 9, period (.), space, and underscore (_). Maximum length: 128. You cannot change the name.
- Password*—The password for logging on to the appliance.
- Confirm Password*—The password.
- Session Timeout
- Groups —The user’s privileges on the appliance. Possible values:
  - owner—The user can perform all administration tasks related to the Management Service.
  - readonly—The user can only monitor the system and change the password of the account.
Click Create. The user that you created is listed in the Users pane.

AAA Authentication:

If you would like to enable LDAP authentication for the Service VM, do that under Configuration > System > Authentication > LDAP.
In the right pane, click Add.
Enter the LDAP settings. Change the port to 636 if using Secure LDAP (recommended). Enter the bind account. Scroll down.
Change the Security Type to SSL. Check the box next to Enable Change Password. Click Create.
Expand System, expand User Administration and click Groups.
Click Add.
Enter the case sensitive name of the Active Directory group.
Select the admin permission.
Configure the Session Timeout. Click Create.

SSL Certificate and Encryption

Replace SDX Service VM Certificate:

Before enabling secure access to the Service VM web console, you probably want to replace the Service VM certificate.

PEM format: The certificate must be in PEM format. The Service VM does not provide any mechanism for converting a PFX file to PEM. You can convert from PFX to PEM by using the Import PKCS#12 task in a NetScaler instance.
On the Configuration tab, expand Management Service and click SSL Certificate Files.
On the right, click Upload.
Browse to the certificate PEM file and click Upload.
On the right, switch to the SSL Keys tab and click Upload.
Browse to the PEM key file. This could be the same file containing the certificate or a separate file. Click Upload.
On the left, click System.
On the right, click Install SSL Certificate.
Select the uploaded certificate and key files. If the key file is encrypted, enter the password. Then click OK. The Service VM will restart so there will be an interruption.
After the Service VM restarts, connect to it using HTTPS. You can’t make this change if you are connected using HTTP.
On the Configuration tab, click System.
On the right, click Change System Settings.
Check the box next to Secure Access Only and click OK. This forces you to use HTTPS to connect to the Service VM.

SSL Encrypt Management Service to NetScaler Communication:

From http://support.citrix.com/article/CTX134973: Communication from the Service Virtual Machine to the NetScaler VPX instances is HTTP by default. If you want to configure HTTPS access for the NetScaler VPX instances, then you have to secure the network traffic between the Service Virtual Machine and NetScaler VPX instances. If you do not secure the network traffic from the Service Virtual Machine configuration, then the NetScaler VPX Instance State appears as Out of Service and the Status shows Inventory from instance failed.

Log on to the Service Virtual Machine Graphical User Interface (GUI) management.
On the Configuration tab, click System.
On the right, click Change System Settings.
Change Communication with NetScaler Instance to https, as shown in the following screen shot:
Run the following command on the NetScaler VPX instance, to change the Management Access (-gui) to SECUREONLY:

set ns ip ipaddress -netmask netmask -arp ENABLED -icmp ENABLED -vServer DISABLED -telnet ENABLED -ftp ENABLED -gui SECUREONLY -ssh ENABLED -snmp ENABLED - mgmtAccess ENABLED -restrictAccess DISABLED -dynamicRouting ENABLED -ospf DISABLED -bgp DISABLED -rip DISABLED -hostRoute DISABLED -vrID 0

Or in the NetScaler instance management GUI go to Network > IPs, open the NSIP and then check the box next to Secure access only.

XenServer LACP Channels

To use LACP, configure Channels in the Service VM, which creates them in XenServer. Then when provisioning an instance, connect it to the Channel. If you are instead using static port channels, you can configure them inside a VPX instance.

In the Service VM, on the Configuration tab, expand System and click Channels.
On the right, click Add.
Select a Channel ID.
For Type, select LACP or STATIC. The other two options are for switch independent load balancing.
In the Interfaces tab, click Add.
Move the Channel Member interfaces to the right by clicking the plus icon.
On the Settings tab, you can select Long or Short, depending on switch configuration. Long is the default.
Click Create when done.
Click Yes when asked to proceed.
The channel will then be created on XenServer.

VPX Instances – Provision

To create an admin profile:

Admin profiles specify the user credentials that are used by the Management Service when provisioning the NetScaler instances, and later when communicating with the instances to retrieve configuration data. The user credentials specified in an admin profile are also used by the client when logging on to the NetScaler instances through the CLI or the configuration utility.

The default admin profile for an instance specifies a user name of nsroot, and the password is also nsroot. This profile cannot be modified or deleted. However, you should override the default profile by creating a user-defined admin profile and attaching it to the instance when you provision the instance. The Management Service administrator can delete a user-defined admin profile if it is not attached to any NetScaler instance.

Important: Do not change the password directly on the NetScaler VPX instance. If you do so, the instance becomes unreachable from the Management Service. To change a password, first create a new admin profile, and then modify the NetScaler instance, selecting this profile from the Admin Profile list.

On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and then click Admin Profiles.
In the Admin Profiles pane, click Add.
In the Create Admin Profile dialog box, set the following parameters:
- Profile Name*—Name of the admin profile. The default profile name is nsroot. You can create user-defined profile names.
- User Name—User name used to log on to the NetScaler instances. The user name of the default profile is nsroot and cannot be changed.
- Password*—The password used to log on to the NetScaler instance. Maximum length: 31 characters.
- Confirm Password*—The password used to log on to the NetScaler instance.
Click Create. The admin profile you created appears in the Admin Profiles pane.

To upload a NetScaler VPX .xva file:

You must upload a NetScaler VPX .xva file to the SDX appliance before provisioning the NetScaler VPX instances.

On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and then click Software Images.
On the right, switch to the XVA Files tab and then click Upload.
In the Upload NetScaler Instance XVA dialog box, click Browse and select the XVA image file that you want to upload. Click Upload. The XVA image file appears in the NetScaler XVA Files pane after it is uploaded.

To provision a NetScaler instance:

On the Configuration tab, in the navigation pane, expand NetScaler Configuration, and then click Instances.
In the NetScaler Instances pane, click Add.
In the Provision NetScaler Wizard follow the instructions in the wizard.
Click Create. The NetScaler instance you provisioned appears in the NetScaler Instances pane.

The wizard will ask for the following info:

Name* – The host name assigned to the NetScaler instance.
IP Address* – The NetScaler IP (NSIP) address at which you access a NetScaler instance for management purposes. A NetScaler instance can have only one NSIP. You cannot remove an NSIP address.
Netmask* – The subnet mask associated with the NSIP address.
Gateway* – The default gateway that you must add on the NetScaler instance if you want access through SSH or the configuration utility from an administrative workstation or laptop that is on a different network.
XVA File* – The .xva image file that you need to provision. This file is required only when you add a NetScaler instance.
Feature License* – Specifies the license you have procured for the NetScaler. The license could be Standard, Enterprise, and Platinum.
Admin Profile* – The profile you want to attach to the NetScaler instance. This profile specifies the user credentials that are used by the Management Service to provision the NetScaler instance and later, to communicate with the instance to retrieve configuration data. The user credentials used in this profile are also used while logging on to the NetScaler instance by using the GUI or the CLI. It is recommended that you change the default password of the admin profile. This is done by creating a new profile with a user-defined password. For more information, see Configuring Admin Profiles.
Total Memory (MB)* – The total memory allocated to the NetScaler instance.
#SSL Cores* – Number of SSL cores assigned to the NetScaler instance. SSL cores cannot be shared. The instance is restarted if you modify this value.
Throughput (Mbps)* – The total throughput allocated to the NetScaler instance. The total used throughput should be less than or equal to the maximum throughput allocated in the SDX license. If the administrator has already allocated full throughput to multiple instances, no further throughput can be assigned to any new instance.
Packets per second* – The total number of packets received on the interface every second.
CPU – Assign a dedicated core or cores to the instance or the instance shares a core with other instance(s).
User Name* – The root user name for the NetScaler instance administrator. This user has superuser access, but does not have access to networking commands to configure VLANs and interfaces. (List of non-accessible commands will be listed here in later versions of this document)
Password* – The password for the root user.
Shell/Sftp/Scp Access* – The access allowed to the NetScaler instance administrator.
Interface Settings – This specifies the network interfaces assigned to a NetScaler instance. You can assign interfaces to an instance. For each interface, if you select Tagged, specify a VLAN ID.
- Important:The interface ID numbers of interfaces that you add to an instance do not necessarily correspond to the physical interface numbering on the SDX appliance. For example, if the first interface that you associate with instance 1 is SDX interface 1/4, it appears as interface 1/1 when you log on to the instance and view the interface settings, because it is the first interface that you associated with instance 1.
- If a non-zero VLAN ID is specified for a NetScaler instance interface, all the packets transmitted from the NetScaler instance through that interface will be tagged with the specified VLAN ID. If you want incoming packets meant for the NetScaler instance that you are configuring to be forwarded to the instance through a particular interface, you must tag that interface with the VLAN ID you want and ensure that the incoming packets specify the same VLAN ID.
- For an interface to receive packets with several VLAN tags, you must specify a VLAN ID of 0 for the interface, and you must specify the required VLAN IDs for the NetScaler instance interface.
NSVLAN ID – An integer that uniquely identifies the NSVLAN. Minimum value: 2. Maximum value: 4095.
Tagged – Designate all interfaces associated with the NSVLAN as 802.1q tagged interfaces.
Interfaces – Bind the selected interfaces to the NSVLAN.

Here are screenshots from the wizard:

On the Provision NetScaler page, enter a name for the instance.
Enter the NSIP, mask, and Gateway.
Select the XVA File with your desired firmware build.
Change the Feature License to Platinum.
Select an Admin Profile created earlier.
Enter a Description. Scroll down.
In the Resource Allocation section, change the Total Memory to
For SSL Chips, specify between 1 and 16.
For Throughput, partition your licensed bandwidth. If you are licensed for 8 Gbps, make sure the total of all VPX instances does not exceed that number.
For CPU, select one of the Dedicated options. Then scroll down.
In the Instance Administration section, enter a new local account that will be created on the VPX. This is in addition to the nsroot user. Note, not all functionality is available to this account. Scroll down.
In the Network Settings section, leave 0/1 selected and deselect 0/2.
Click Add to connect the VPX to more interfaces.
If you have Port Channels, select one of the LA interfaces.
Try not configure any VLAN settings here. If you do, XenServer filters the VLANs available to the VPX instance. Changing the VLAN filtering settings later probably requires a reboot. Click Add.
In the Management VLAN Settings section, do not configure anything in this section unless you need to tag the NSIP VLAN. Click Done.
After a couple minutes the instance will be created. Click Close.
In your Instances list, click the IP address to launch the VPX management console. Do the following at a minimum (instructions in the NetScaler System Configuration section):
1. Create Policy Based Route for the NSIP – System > Settings > Network > PBRs
2. Add SNIPs for each VLAN – System > Network > IPs
3. Add VLANs and bind to SNIPs – System > Network > VLANs
4. Create Static Routes for internal networks – System > Network > Routes
5. Change default gateway – System > Network > Routes > 0.0.0.0
6. Create another instance on a different SDX and High Availability pair them together – System > High Availability

Applying the Administration Configuration

At the time of provisioning a NetScaler VPX instance, the Management Service creates some policies, instance administration (admin) profile, and other configuration on the VPX instance. If the Management Service fails to apply the admin configuration at this time due to any reason (for example, the Management Service and the NetScaler VPX instance are on different subnetworks and the router is down or if the Management Service and NetScaler VPX instance are on the same subnet but traffic has to pass through an external switch and one of the required links is down), you can explicitly push the admin configuration from the Management Service to the NetScaler VPX instance at any time.

On the Configuration tab, in the navigation pane, click NetScaler.
In the NetScaler Configuration pane, click Apply Admin Configuration.
In the Apply Admin Configuration dialog box, in Instance IP Address, select the IP address of the NetScaler VPX instance on which you want to apply the admin configuration.
Click OK.

VPX Instances – Manage

You may login to the VPX instance and configure everything normally. SDX also offers the ability to manage IP address and SSL certificates from SDX rather than from inside the VPX instance. The SDX Management Service does not have the ability to create certificates so it’s probably best to do that from within the VPX instance.

To view the console of a NetScaler instance:

Connect to the Service VM using https.
Viewing the console might not work unless you replace the Service VM certificate.
In the Service VM, go to Configuration > NetScaler > Instances.
On the right, right-click an instance and click Console.
The instance console then appears.
Another option is to use the Lights Out Module and the xl console command as detailed at Citrix Blog Post SDX Remote Console Access of VIs.

To start, stop, delete, or restart a NetScaler instance:

On the Configuration tab, in the navigation pane, expand NetScaler and click Instances.
In the Instances pane, right-click the NetScaler instance on which you want to perform the operation, and then click Start or Shut Down or Delete or Reboot.
In the Confirm message box, click Yes.

Creating a Subnet IP Address on a NetScaler Instance:

You can create or delete a SNIP during runtime without restarting the NetScaler instance.

On the Configuration tab, in the navigation pane, click NetScaler.
In the NetScaler Configuration pane, click Create IP.
In the Create NetScaler IP dialog box, specify values for the following parameters.
- IP Address* – Specify the IP address assigned as the SNIP or the MIP address.
- Netmask* – Specify the subnet mask associated with the SNIP or MIP address.
- Type* – Specify the type of IP address. Possible values: SNIP.
- Save Configuration* – Specify whether the configuration should be saved on the NetScaler. Default value is false.
- Instance IP Address* – Specify the IP address of the NetScaler instance.
Click Create.

To save the configuration on a NetScaler instance:

On the Configuration tab, in the navigation pane, click NetScaler.
In the NetScaler pane, click Save Configuration.
In the Save Configuration dialog box, in Instance IP Address, select the IP addresses of the NetScaler instances whose configuration you want to save.
Click OK.

Change NSIP of VPX Instance:

If you change NSIP inside of VPX instead of using the Modify Instance wizard in the Service VM, see article http://support.citrix.com/article/CTX139206 to adjust the XenServer settings.

Enable Call Home:

On the Configuration tab, in the navigation pane, click the NetScaler node.
On the right, click Call Home.
Enter an email address to receive communications regarding NetScaler Call Home.
Check the box next to Enable Call Home.
Select the instances to enable Call Home and click OK.

VPX Instance – Firmware Upgrade

Upload NetScaler Firmware Build Files:

To upgrade a VPX instance from the Service VM, first upload the firmware build file.

In the Configuration tab, on the left, expand NetScaler and click Software Images.
On the right, in the Software Images tab click Upload.
Browse to the build…tgz file and click Upload.

Upgrading Multiple NetScaler VPX Instances:

You can upgrade multiple instances at the same time.

To prevent any loss of the configuration running on the instance that you want to upgrade, save the configuration on the instance before you upgrade the instance.
On the Configuration tab, in the navigation pane, expand NetScaler and click Instances.
Click an instance to highlight it. Open the Action menu and click Upgrade.
In the Upgrade NetScaler dialog box, in Build File, select the NetScaler upgrade build file of the version you want to upgrade to. Ignore the Documentation File. Click OK.

Service VM Monitoring

To view the audit log, in the navigation pane, expand System, and then click Audit Logs.
To view the task log, in the navigation pane, expand Diagnostics, and then click Task Log.
To view events, on the Dashboard tab, in the System Health Events section on the bottom right, click Show All Events.

Service VM Backups

The SDX appliance automatically keeps three backups of the Service VM configuration that are taken daily at 12:30 am. Only configuration files and logs are backed up. This task does not backup the VPXs. You can go to Management Service > Backup Files to backup or restore the appliance’s configuration. And you can download the backup files.

Global Server Load Balancing (GSLB) – NetScaler 10.5

Last Modified: Nov 6, 2020 @ 7:11 am

174 Comments

Navigation

GSLB Planning
ADNS
Metric Exchange Protocol
GSLB Services
GSLB Virtual Server
Test GSLB
DNS Delegation
Geo Location Database

This article was written for NetScaler 10.5.

For NetScaler 12.0 or Citrix ADC 12.1, see https://www.carlstalhood.com/global-server-load-balancing-gslb-netscaler-12/
For NetScaler 11.1, see https://www.carlstalhood.com/global-server-load-balancing-gslb-netscaler-11-1/

GSLB Planning

GSLB is nothing more than DNS. GSLB is not in the data path. GSLB receives a DNS query and GSLB sends back an IP address, which is exactly how a DNS server works. However, GSLB can do some things that DNS servers can’t do:

Don’t give out an IP address unless it is UP (monitoring)
- If active IP address is down, give out the passive IP address (active/passive)
Give out the IP address that is closest to the user (proximity load balancing)
Give out different IPs for internal vs external (DNS View)

GSLB is only useful if you have a single DNS name that could resolve to two or more IP addresses. If there’s only one IP address then use normal DNS instead.

Citrix Blog Post Global Server Load Balancing: Part 1 explains how DNS queries work and how GSLB fits in.

Citrix has a good DNS and GSLB Primer.

When configuring GSLB, don’t forget to ask “where is the data?”. For XenApp/XenDesktop, DFS multi-master replication of user profiles is not supported so configure “home” sites for users. More information at Citrix Blog Post XenDesktop, GSLB & DR – Everything you think you know is probably wrong!

GSLB can be enabled both externally and internally. For external GSLB, configure it on the DMZ NetScaler appliances and expose it to the Internet. For internal GSLB, configure it on internal NetScaler appliances. Note: Each NetScaler appliance only has one DNS table so if you try to use one NetScaler for both public and internal then be aware that external users can query for internal GSLB-enabled DNS names.

For internal and external GSLB of the same DNS name on the same appliance, you can use DNS Policies and DNS Views to return different IP addresses depending on where users are connecting from. Citrix CTX130163 How to Configure a GSLB Setup for Internal and External Users Using the Same Host Name.

However, GSLB monitoring applies to the entire GSLB Service so it would take down both internal and external GSLB. If you need different GSLB monitoring for internal and external of the same DNS name, try CNAME:

External citrix.company.com:
- Configure NetScaler GSLB for citrix.company.com.
- On public DNS, delegate citrix.company.com to the NetScaler DMZ ADNS services.
Internal citrix.company.com:
- Configure NetScaler GSLB for citrixinternal.company.com or something like that.
- On internal DNS, create CNAME for citrix.company.com to citrixinternal.company.com
- On internal DNS, delegate citrixinternal.company.com to NetScaler internal ADNS services.

Some IP Addresses are needed on each NetScaler pair:

ADNS IP: An IP that will listen for ADNS queries. For external, create a public IP for the ADNS IP and open UDP 53 so Internet-based DNS servers can access it. This can be an existing SNIP on the appliance.
GSLB Site IP / MEP IP: A GSLB Site IP that will be used for NetScaler-to-NetScaler communication, which is called MEP or Metric Exchange Protocol. The IP for ADNS can also be used for MEP / GSLB Site.
- RPC Source IP: RPC traffic is sourced from a SNIP, even if this is different than the GSLB Site IP. It’s less confusing if you use a SNIP as the GSLB Site IP.
- Public IP: For external GSLB, create public IPs that are NAT’d to the GSLB Site IPs. The same public IP used for ADNS can also be used for MEP. MEP should be routed across the Internet so NetScaler can determine if the remote datacenter has Internet connectivity or not.
- MEP Port: Open port TCP 3009 between the two NetScaler GSLB Site IPs. Make sure only the NetScalers can access this port on the other NetScaler. Do not allow any other device on the Internet to access this port. This port is encrypted.
- GSLB Sync Ports: To use GSLB Configuration Sync, open ports TCP 22 and TCP 3008 from the NSIP (management IP) to the remote public IP that is NAT’d to the GSLB Site IP. The GSLB Sync command runs a script in BSD shell and thus NSIP is always the Source IP.
DNS Queries: The purpose of GSLB is to resolve a DNS name to one of several potential IP addresses. These IP addresses are usually public IPs that are NAT’d to existing Load Balancing, SSL Offload, Content Switching, or NetScaler Gateway VIPs in each datacenter.
IP Summary: In summary, for external GSLB, you will need a minimum of two public IPs in each datacenter:
- One public IP that is NAT’d to the IP that is used for ADNS and MEP (GSLB Site IP). You only need one IP for ADNS / MEP no matter how many GSLB names are configured. MEP (GSLB Site IP) can be a different IP, if desired.
- One public IP that is NAT’d to a Load Balancing, SSL Offload, Content Switching, or NetScaler Gateway VIP.
- If you GSLB-enable multiple DNS names, each DNS name usually resolves to different IPs. This usually means that you will need additional public IPs NAT’d to additional VIPs.

ADNS

Identify a SNIP that you will use for MEP and ADNS.
Configure a public IP for the SNIP and configure firewall rules.
If you wish to use GSLB configuration sync then management access (SSH) must be enabled on this SNIP.
On the left, expand Traffic Management > Load Balancing, and click Services.
On the right, click Add.
Name the service ADNS or similar.
In the IP Address field, enter an appliance SNIP.
In the Protocol field, select ADNS. Then click OK.
Scroll down and click Done.
On the left of the console, expand System, expand Network, and then click IPs.
On the right, you’ll see the SNIP is now marked as the ADNS svc IP. If you don’t see this yet, click the Refresh icon.
Repeat on the other appliance in the other datacenter.
Your NetScaler appliances are now DNS servers.

Metric Exchange Protocol

Open the firewall rules for Metric Exchange Protocol. You can use the same SNIP and same public IP used for ADNS.
On the left, expand Traffic Management, right-click GSLB, and enable the feature.
Expand GSLB, and click Sites.
On the right, click Add.
Add the local site first. Enter a descriptive name and in the Site Type drop-down, select LOCAL.
In the Site IP Address field, enter an appliance SNIP. This SNIP must be in the default Traffic Domain. The NetScaler listens for GSLB MEP traffic on this IP.
For Internet-routed GSLB MEP, in the Public IP Address field, enter the public IP that is NAT’d to the GSLB Site IP (SNIP). For internal GSLB, there is no need to enter anything in the Public IP field. Click Create.
Go back to System > Network > IPs, and verify that the IP is now marked as a GSLB site IP. If you don’t see it yet, click the Refresh button.
If you want to use the GSLB Sync Config feature, then you’ll need to edit the GSLB site IP, and enable Management Access.
Scroll down and enable Management Access. SSH is all you need.
Go to the other appliance and also create the local GSLB site using its GSLB site IP and its public IP that is NAT’d to the GSLB site IP.
In System > Network > IPs on the remote appliance, there should now be a GSLB site IP. This could be a SNIP. If GSLB Sync is desired, enable management access on that IP and ensure SSH is enabled.
Now on each appliance add another GSLB Site, which will be the remote GSLB site.
Enter a descriptive name and select REMOTE as the Site Type.
Enter the other appliance’s actual GSLB Site IP as configured on the appliance. This IP does not need to be reachable.
In the Public IP field, enter the public IP that is NAT’d to the GSLB Site IP on the other appliance. For MEP, TCP 3009 must be open from the local GSLB Site IP to the remote public Site IP. For GSLB sync, TCP 22, and TCP 3008 must be open from the local NSIP to the remote public Site IP. Click Create.
Repeat on the other appliance.
MEP will not function yet since the NetScaler appliances are currently configured to communicate unencrypted on TCP 3011. To fix that, on the left, expand System, expand Network, and click RPC.
On the right, edit the new RPC address (the other site’s GSLB Site IP), and click Edit.
On the bottom, check the box next to Secure, and click OK.
Do the same thing on the other appliance.
If you go back to GSLB > Sites, you should see it as active.

GSLB Services

GSLB Services represent the IP addresses that are returned in DNS Responses. DNS Query = DNS name. DNS Response = IP address.

GSLB should be configured identically on both NetScalers. Since you have no control over which NetScaler will receive the DNS query, you must ensure that both NetScalers are giving out the same DNS responses.

Create the same GSLB Services on both NetScalers:.

Start on the appliance in the primary data center. This appliance should already have a traffic Virtual Server (NetScaler Gateway, Load Balancing, or Content Switching) for the DNS name that you are trying to GSLB enable.
On the left, expand Traffic Management > GSLB, and click Services.
On the right, click Add.
The service name should be similar to the DNS name that you are trying to GSLB. Include the site name in the service name.
Select the LOCAL Site.
On the bottom part, select Virtual Servers, and then select a Virtual Server that is already defined on this appliance. It should automatically fill in the other fields. If you see a message asking if you wish to create a service object, click Yes.
Scroll up and make sure the Service Type is SSL. It’s annoying that NetScaler doesn’t set this drop-down correctly.
The Public IP field contains the actual IP Address that the GSLB ADNS service will hand out. Make sure this Public IP is user accessible. It doesn’t even need to be a NetScaler owned IP.
Scroll down and click OK.
If the GSLB Service IP is a VIP on the local appliance, then GSLB will simply use the state of the local traffic Virtual Server (Load Balancing, Content Switching, or Gateway). If the GSLB Service IP is a VIP on a remote appliance, then GSLB will use MEP to ask the other appliance for the state of the remote traffic Virtual Server. In both cases, there’s no need to bind a monitor to the GSLB Service.
However, you can also bind monitors directly to the GSLB Service. Here are some reasons for doing so:
- If the GSLB Service IP is a NetScaler-owned traffic VIP, but the monitors bound the traffic Virtual Server are not the same ones you want to use for GSLB. When you bind monitors to the GSLB Services, the monitors bound to the traffic Virtual Server are ignored.
- If the GSLB Service IP is in a non-default Traffic Domain, then you will need to attach a monitor since GSLB cannot determine the state of Virtual Servers in non-default Traffic Domains.
- If the GSLB Service IP is not hosted on a NetScaler, then only GSLB Service monitors can determine if the Service IP is up or not.
If you intend to do GSLB active/active and if you need site persistence then you can configure your GSLB Services to use Connection Proxy or HTTP Redirect. See Citrix Blog Post Troubleshooting GSLB Persistence with Fiddler for more details.
Click Done.
On the other datacenter NetScaler, create a GSLB Service.
Select the REMOTE site that is hosting the service.
Since the service is on a different appliance and not this one, you won’t be able to select it using the Virtual Servers option. Instead, select New Server.
For the Server IP, enter the actual VIP configured on the other appliance. This local NetScaler will use GSLB MEP to communicate with the remote NetScaler to find a traffic Virtual Server with this VIP. The remote NetScaler respond if the remote traffic Virtual Server is up or not. The remote Server IP configured here does not need to be directly reachable by this local appliance. If the Server IP is not owned by either NetScaler, then you will need to bind monitors to your GSLB Service.
In the Public IP field, enter the IP address that will be handed out to clients. This is the IP address that users will use to connect to the service. For Public DNS, you enter a Public IP that is usually NAT’d to the traffic VIP. For internal DNS, the Public IP and the Server IP are usually the same.
Scroll up and change the Service Type to match the Virtual Server defined on the other appliance..
Click OK.
Just like the other appliance, you can also configure Site Persistence and GSLB Service Monitors. Click Done when done.
Create more GSLB Services, one for each traffic VIP. GSLB is useless if there’s only one IP address to return. You should have multiple IP addresses (VIPs) through which a web service (e.g. NetScaler Gateway) can be accessed. Each of these VIPs is typically in different datacenters, or on different Internet circuits. The mapping between DNS name and IP addresses is configured in the GSLB vServer, as detailed in the next section.

GSLB Virtual Server

The GSLB Virtual Server is the entity that the DNS name is bound to. GSLB vServer then gives out the IP address of one of the GSLB Services that is bound to it.

Configure the GSLB vServer identically on both appliances:

On the left, expand Traffic Management > GLSB and click Virtual Servers.
On the right, click Add.
Give the GSLB vServer a descriptive name. For active/active, you can name it the same as your DNS name. For active/passive, you will create two GSLB Virtual Servers, one for each datacenter, so include Active or Passive in the Virtual Server name.
Make sure Service Type is set correctly.
If you intend to bind multiple GSLB Services to this GSLB vServer, then you can optionally check the box for Send all “active” service IPs. By default, GSLB only gives out one IP per DNS query. This checkbox always returns all IPs, but the IPs are ordered based on the GSLB Load Balancing Method and/or GSLB Persistence.
Click OK.
On the right, in the Advanced column, click Service.
On the left, click where it says No GSLB Virtual Server to GSLBService Binding.
Click the arrow next to Click to select.
Check the box next to an existing GSLB Service and click OK. If your GSLB is active/passive then only bind one service.
If your GSLB is active/active then bind multiple GSLB Services. Also, you’d probably need to configure GSLB persistence (Source IP or cookies).
Click Bind.
On the right, in the Advanced column, click Domains.
On the left, click where it says No GSLB Virtual Server Domain Binding.
Enter the FQDN that GSLB will resolve.
If this GSLB is active/passive, there are two options:
- Use the Backup IP field to specify the IP address that will be handed out if the primary NetScaler is inaccessible or if the VIP on the primary appliance is marked down for any reason.
- Or, create a second GSLB Virtual Server that has the passive GSLB service bound to it. Don’t bind a Domain to the second GSLB Virtual Server. Then edit the Active GSLB Virtual Server and use the Backup Virtual Server section to select the second GSLB Virtual Server.
Click Bind.
If this is active/active GSLB, you can edit the Method section to enable Static Proximity. This assumes the Geo Location database has already been installed on the appliance.
Also for active/active, if you don’t want to use Cookie-based persistence, then you can use the Persistence section to configure Source IP persistence.
Click Done.
If you are configuring active/passive using the backup GSLB Virtual Server method, create a second GSLB Virtual Server that has the passive GSLB service bound to it. Don’t bind a Domain to the second GSLB Virtual Server. Then edit the Active GSLB Virtual Server and use the Backup Virtual Server section to select the second GSLB Virtual Server.
On the left, if you expand Traffic Management > DNS, expand Records, and click Address Records, you’ll see a new DNS record for the GSLB domain you just configured. Notice it is marked as GSLB DOMAIN.
Create identical GSLB Virtual Servers on the other NetScaler appliance. Both NetScalers must be configured identically.
You can also synchronize the GSLB configuration with the remote appliance by going to Traffic Management > GSLB.
On the right, click Sychronize configuration on remote sites.
Use the check boxes on the top, if desired. It’s usually a good idea to Preview the changes before applying them. Then click OK to begin synchronization.

Some notes regarding GSLB Sync:

It’s probably more reliable to do it from the CLI by running sync gslb config and one of the config options (e.g. -preview).
GSLB Sync runs as a script on the BSD shell and thus always uses the NSIP as the source IP.
GSLB Sync connects to the remote GSLB Site IP on TCP 3008 (if RPC is Secure) and TCP 22.

Test GSLB

To test GSLB, simply point nslookup to the ADNS services and submit a DNS query for one of the DNS names bound to a GSLB vServer. Run the query multiple times to make sure you’re getting the response you expect.
Both NetScaler ADNS services should be giving the same response.
To simulate a failure, disable the traffic Virtual Server.
Then the responses should change. Verify on both ADNS services.
Re-enable the traffic Virtual Server, and the responses should return to normal.

DNS Delegation

If you are enabling GSLB for the domain gateway.corp.com, you’ll need to create a delegation at the server that is hosting the corp.com DNS zone. For public GSLB, you need to edit the public DNS zone for corp.com.

DNS Delegation instructions will vary depending on what product host’s the public DNS zone. This section details Microsoft DNS, but it should be similar in BIND or web-based DNS products.

There are two ways to delegate GSLB-enabled DNS names to NetScaler ADNS:

Delegate the individual record. For example, delegate gateway.corp.com to the two NetScaler ADNS services (gslb1.corp.com and gslb2.corp.com).
Delegate an entire subzone. For example, delegate the subzone gslb.corp.com to the two NetScaler ADNS services. Then create a CNAME record in the parent DNS zone for gateway.corp.com that is aliased to gateway.gslb.corp.com. When DNS queries make it to NetScaler, they will be for gateway.gslb.corp.com and thus gateway.gslb.corp.com needs to be bound to the GSLB Virtual Server instead of gateway.corp.com. For additional delegations, simply create more CNAME records.

This section covers the first method – delegating an individual DNS record:

Run DNS Manager.
First, create Host Records pointing to the ADNS services running on the NetScalers in each data center. These host records for ADNS are used for all GSLB delegations no matter how many GSLB delegations you need to create.
The first Host record is gslb1 (or similar) and should point to the ADNS service (Public IP) on one of the NetScaler appliances.
The second Host record is gslb2 and should point to the ADNS Service (public IP) on the other NetScaler appliance.
If you currently have a host record for the service that you are delegating to GSLB (gateway.corp.com), delete it.
Right-click the parent DNS zone and click New Delegation.
In the Welcome to the New Delegation Wizard page, click Next.
In the Delegated Domain Name page, enter the left part of the DNS record that you are delegating (e.g. gateway). Click Next.
In the Name Servers page, click Add.
This is where you specify gslb1.corp.com and gslb2.corp.com. Enter gslb1.corp.com and click Resolve. Then click OK. If you see a message about the server not being authoritative for the zone, ignore the message.
Then click Add to add the other GSLB ADNS server.
Once both ADNS servers are added to the list, click Next.
In the Completing the New Delegation Wizard page, click Finish.
If you run nslookup against your Microsoft DNS server, it will respond with Non-authoritative answer. That’s because it got the response from NetScaler and not from itself.

That’s all there is to it. Your NetScalers are now DNS servers. For active/passive, the NetScalers will hand out the public IP address of the primary data center. When the primary data center is not accessible, GSLB will hand out the GSLB Service IP bound to the Backup GSLB vServer.

Geo Location Database

If you want to use DNS Policies or Static Proximity GSLB Load Balancing or Responders based on user’s location, import a geo location database. Common free databases are:

GeoLite Legacy – http://dev.maxmind.com/geoip/legacy/geolite/
IP2Location Lite – http://lite.ip2location.com/.

For IP2Location, see the blog post Add IP2Location Database as NetScaler’s Location File for instructions on how to import.

For GeoLite Legacy:

Download the GeoLite Country database CSV from http://dev.maxmind.com/geoip/legacy/geolite/.
Note: GeoLite City is actually two files that must be merged as detailed at Citrix Blog Post GeoLite City as NetScaler location database. GeoLite Country doesn’t need any preparation.
Upload the extracted database (.csv file) to the NetScaler appliance at /var/netscaler/locdb.

To import the Geo database:

In the NetScaler GUI, on the left, expand AppExpert, expand Location, and click Static Database (IPv4).
On the right, click Add.
Browse to the location database file.
In the Location Format field, select geoip-country and click Create.
When you open a GSLB Service, the public IP will be translated to a location.

You can use the Geo locations in a DNS Policy, static proximity GSLB Load Balancing, or Responders:

Citrix Knowledgebase article – How to Block Access to a Website Using a Location Database Based on User’s Country
Neil Spellings blog post – Using Netscaler HTTP callouts for real-time GeoIP and anonymous proxy detection
Citrix Docs – Overriding Static Proximity Behavior by Configuring Preferred Locations

Horizon View Load Balancing – NetScaler 10.5

Last Modified: Nov 6, 2020 @ 7:11 am

26 Comments

Navigation

Use this procedure to load balance Horizon View Connection Servers, Horizon View Security Servers, and/or VMware Access Points.

Overview
Monitors
Servers
Services
Load Balancing Virtual Servers
Persistency Group
Horizon View Configuration

Overview

A typical Horizon View Installation will have at least six connection servers:

Two Internal View Connection Servers – these need to be load balanced on an internal VIP
Two DMZ View Security Servers – these need to be load balanced on a DMZ VIP
The DMZ View Security Servers are paired with two additional internal View Connection Servers. There is no need to load balance the internal Paired Connection Servers. However, we do need to monitor them.

If you are using Access Points instead of Security Servers then you’ll have the following machines. Server pairing is not necessary.

Two Internal View Connection Servers – these need to be load balanced on an internal VIP
Two DMZ VMware Access Point appliances – these need to be load balanced on a DMZ VIP

This topic is focused on traditional View Security Servers but could be easily adapted for Access Point appliances. The difference is that with Access Points there are no paired servers and thus there’s no need to monitor the paired servers. The VIP ports are identical for both solutions.

Monitors

Users connect to Horizon View Connection Server, Horizon View Security Server, and Access Point appliances on four ports: TCP 443, TCP 8443, TCP 4172, and UDP 4172. Users will initially connect to port 443 and then be redirected to one of the other ports on the same server initially used for the 443 connection. If one of the ports is down, the entire server should be removed from load balancing. To facilitate this, create a monitor for each of the ports (except UDP 4172).

On the left, expand Traffic Management, expand Load Balancing, and click Monitors.
On the right, click Add.
Name it View-PCOIP or similar.
Change the Type drop-down to TCP.
In the Destination Port field, enter 4172.
Scroll down and click Create.
On the right, click Add.
Name it View-Blast or similar.
Change the Type drop-down to TCP.
In the Destination Port field, enter 8443.
Scroll down and click Create.
On the right, click Add.
Name it View-SSL or similar.
Change the Type drop-down to HTTP-ECV.
In the Destination Port field, enter 443.
Scroll down and check the box next to Secure.
On the Special Parameters tab, in the Send String section, enter GET /broker/xml/
In the Receive String section, enter clientlaunch-default.
Scroll down and click Create.
View Security Servers are paired with View Connection Servers. If the paired View Connection Server is down, then we should probably stop sending users to the corresponding View Security Server. Let’s create a monitor that has a specific IP address in it. Right-click the existing View-SSL or View-SSLAdv monitor and click Add.
Note: this step does not apply to Access Points. Normally a monitor does not have any Destination IP defined, which means it uses the IP address of the service that it is bound to. However, we intend to bind this monitor to the View Security Server but we need it to monitor the paired View Connection Server, which is a different IP address. Type in the IP address of the paired View Connection Server. Then rename the monitor so it includes the View Connection Server name.
Note: this step does not apply to Access Points. Since we are embedding an IP address into the monitor, you have to create a separate monitor for each paired View Connection Server IP.

Servers

Create Server Objects for the DMZ Security Servers and the internal non-paired Connection Servers. Do not create Server Objects for the Paired Connection Servers.

On the left, expand Traffic Management, expand Load Balancing, and click Servers.
On the right, click Add.
Enter a descriptive server name, usually it matches the actual server name.
Enter the IP address of the View Connection Server or View Security Server.
Enter comments to describe the server. Click Create.
Continue adding View Connection Servers or View Security Servers.

Services

If deploying View Security Servers, create Services Objects for the DMZ Security Servers and the internal non-paired Connection Servers. Do not create Services Objects for the Paired Connection Servers.

If deploying Access Points, create Services Objects for the DMZ Access Point appliances and the internal Connection Servers

Each connection server and security server needs separate Service objects. Each Security Server listens on multiple port numbers and thus there will be multiple Services Objects for each Security Server.

For Internal Connection Servers (not the paired servers), load balancing monitoring is very simple:

Create services for SSL 443
To verify server availability, monitor port TCP 443 on the same server.
If tunneling is disabled then internal users connect directly to View Agents and UDP/TCP 4172 and TCP 8443 are not used on Internal Connection Servers. There’s no need to create services and monitors for these ports.

Security Servers and Access Points are more complex:

The PCoIP Secure Gateway and HTML Blast Secure Gateway are typically enabled on Security Servers and Access Points but they are not typically enabled on internal Connection Servers.
All traffic initially connects on TCP 443. For Security Servers and Access Points, the clients then connect to UDP 4172 or TCP 8443 on the same Security Server. If UDP 4172 or TCP 8443 are down, then you probably want to make sure TCP 443 is also brought down.
Each Security Server is paired with an internal Connection Server. If the internal Connection Server is down then the Security Server should be taken down. This does not apply to Access Points.
To accommodate these failure scenarios, bind multiple monitors to the View Security Server or Access Point load balancing Services. If any of the monitors fails then NetScaler will no longer forward traffic to 443 on that particular server.

If you have two View Security Servers or Access Points named VSS01 and VSS02, the configuration is summarized as follows (scroll down for detailed configuration):

Service = VSS01, Protocol = SSL_BRIDGE, Port = 443
- Monitors = PCoIP (TCP 4172), SSL (443), and Blast (8443)
- Monitor = SSL (443) on paired View Connection Server VCS01. This monitor is not needed on Access Points.
Service = VSS02, Protocol = SSL_BRIDGE, Port = 443
- Monitors = PCoIP (TCP 4172), SSL (443), and Blast (8443)
- Monitor = SSL (443) on paired View Connection Server VCS02. This monitor is not needed on Access Points.
Service = VSS01, Protocol = TCP, Port = 4172
- Monitor = PCoIP (TCP 4172)
Service = VSS02, Protocol = TCP, Port = 4172
- Monitor = PCoIP (TCP 4172)
Service = VSS01, Protocol = UDP, Port = 4172
- Monitor = PCoIP (TCP 4172)
Service = VSS02, Protocol = UDP, Port = 4172
- Monitor = PCoIP (TCP 4172)
Service = VSS01, Protocol = SSL_BRIDGE, Port = 8443
- Monitor = Blast (8443)
Service = VSS02, Protocol = SSL_BRIDGE, Port = 8443
- Monitor = Blast (8443)

If you are not using HTML Blast then you can skip 8443. If you are not using PCoIP Secure Gateway, then you can skip the 4172 ports.

On the left, expand Traffic Management, expand Load Balancing, and click Services.
On the right, click Add.
Give the Service a descriptive name (e.g. svc-VSS01-SSL).
Change the selection to Existing Server and select the View Security Server or internal (non-paired) View Connection Server you created earlier.
Change the Protocol to SSL_BRIDGE and click OK.
On the left, in the Monitors section, click where it says 1 Service to Load Balancing Monitor Binding.
Click Add Binding.
Click the arrow next to Click to select.
Select the View-SSL monitor and click OK.
Then click Bind.
If this is a View Security Server, add monitors for PCoIP and HTML Blast. If any of those services fails, then 443 needs to be marked DOWN.
If this is a View Security Server, also add a monitor that has the IP address of the paired View Connection Server. If the paired View Connection Server is down, then stop sending connections to this View Security Server.
The Last Response should indicate Success. If you bound multiple monitors to the Service, then the member will only be UP if all monitors succeed. There’s a refresh button on the top-right. Click Close when done.
Then click Done.
Right-click the first service and click Add.
Change the name to match the second View Server.
Use the Server drop-down to select to the second View Server.
The remaining configuration is identical to the first server. Click OK.
You will need to configure the monitors again. They will be identical to the first server except for the monitoring of the paired View Connection Server. Click Done when done.
Add another Service for PCoIP on TCP 4172.
1. Name = svc-VSS01-PCoIPTCP or similar.
2. Server = Existing Server, select the first View Server.
3. Protocol = TCP
4. Port = 4172.
5. Monitors = View-PCoIP. You can add the other monitors if desired.
Repeat for the 2^nd View Security Server.
Add another Service for PCoIP on UDP 4172.
1. Name = svc-VSS01-PCoIPUDP or similar.
2. Existing Server = first View Server
3. Protocol = UDP
4. Port = 4172.
5. Monitors = View-PCoIP. You can add the other monitors if desired.
Repeat for the 2^nd View Server.
Add another Service for HTML Blast on SSL_BRIDGE 8443.
1. Name = svc-VSS01-HTMLBlast or similar.
2. Existing Server = the first View Server
3. Protocol =
4. Port = 8443.
5. Monitors = View-Blast. You can add the other monitors if desired.
Repeat for the 2^nd View Server.
The eight services should look something like this:
Repeat these instructions to add the internal (non-paired) View Connection Servers except that you only need to add services for SSL_BRIDGE 443 and only need monitoring for 443.

Load Balancing Virtual Servers

Create separate load balancers for internal and DMZ.

Internal load balances the two non-paired Internal View Connections Servers.
DMZ load balances the two View Security Servers or Access Point appliances.

The paired View Connection Servers do not need to be load balanced.

For the internal View Connection Servers you only need a load balancer for SSL_BRIDGE 443. If tunneling is disabled then you don’t need load balancers for the other ports (UDP/TCP 4172 and SSL_BRIDGE 8443).

However, tunneling is enabled on the View Security Servers and Access Point appliances so you will need separate load balancers for each port number. Here is a summary of the Virtual Servers:

Virtual Server on SSL_BRIDGE 443 – bind both View SSL Services.
Virtual Server on UDP 4172 – bind both View PCoIPUDP Services.
Virtual Server on TCP 4172 – bind both View PCoIPTCP Services.
Virtual Server on SSL_BRIDGE 8443 – bind both View Blast Services.

Do the following to create the Virtual Servers:

On the left, under Traffic Management > Load Balancing, click Virtual Servers.
On the right click Add.
Name it View-SSL-LB or similar.
Change the Protocol to SSL_BRIDGE.
Specify a new internal VIP. This one VIP will be used for all of the Virtual Servers.
Enter 443 as the Port.
Click OK.
On the left, in the Services and Service Groups section, click where it says No Load Balancing Virtual Server Service Binding.
Click the arrow next to Click to select.
Select the two View-SSL Services and click OK.
Click Bind.
Click OK.
Then click Done. Persistency will be configured later.
If this is a View Security Server or Access Point or if tunneling is enabled then create another Load Balancing Virtual Server for PCoIP UDP 4172:
1. Same VIP as the 443 Load Balancer.
2. Protocol = UDP, Port = 4172
3. Services = the PCoIP UDP Services.
If this is a View Security Server or Access Point or if tunneling is enabled then create another Load Balancing Virtual Server for PCoIP TCP 4172:
1. Same VIP as the 443 Load Balancer.
2. Protocol = TCP, Port = 4172
3. Services = the PCoIP TCP Services.
If this is a View Security Server or Access Point or if tunneling is enabled then create another Load Balancing Virtual Server for HTML Blast SSL_BRIDGE 8443:
1. Same VIP as the 443 Load Balancer.
2. Protocol = SSL_BRIDGE, Port = 8443
3. Services = the HTML Blast SSL_BRIDGE Services.
This gives you four Virtual Servers on the same VIP but different protocols and port numbers.

Persistency Group

For Security Servers and Access Point appliances, users will first connect to SSL_BRIDGE 443 and be load balanced. Subsequent connections to the other port numbers must go to the same load balanced server. Create a Persistency Group to facilitate this.

If tunneling is disabled on the internal View Connection Servers then you probably only have one load balancer for those servers and thus you could configure persistence directly on that one load balancer instead of creating a Persistency Group. However, since the View Security Servers have multiple load balancers then you need to bind them together in a Persistency Group.

On the left, under Traffic Management, expand Load Balancing and click Persistency Groups.
On the right, click Add.
Give the Persistency Group a name (e.g. View).
Change the Persistence to SOURCEIP.
Enter a timeout that is equal to or greater than the timeout in View Administrator, which defaults to 10 hours (600 minutes).
In the Virtual Server Name section, click Add.
Move all four View Security Server / Access Point Load Balancing Virtual Servers to the right. Click Create.

Horizon View Configuration

On the View Security Servers (or View Connection Servers), request a certificate that matches the FQDN that resolves to the Load Balancing VIP.
Make sure the private key is exportable.
Set the Friendly Name to vdm and restart the View Security Server services.
In View Administrator, go to View Configuration > Servers.
On the right, switch to the Security Servers tab.
Highlight a server and click Edit.
Change the URLs to the FQDN that resolves to the load balancing VIP.
Change the PCoIP URL to the VIP. For View Security Servers, this is typically a public IP that is NAT’d to the DMZ Load Balancing VIP.

Name	Expression	Server
RSA-SelfService	REQ.HTTP.HEADER User-Agent CONTAINS CitrixReceiver	RSA
RSA-Web	REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver	RSA