System Configuration – NetScaler 14.1 – Citrix ADC 13

Last Modified: Apr 25, 2024 @ 1:39 pm


💡 = Recently Updated

Change Log

VPX Virtual Hardware

Magnus Andersson Deploy Citrix ADC VPX On Nutanix AHV

VMware Compatibility (source = Support matrix for Citrix ADC at Citrix Docs)

  • Citrix ADC 13.1 build 21.50 and newer support VMware ESXi 7.0 update 3c.
  • Citrix ADC 13.0 build 71 and newer supports ESXi 7.0.

Download and import VPX:

  1. Download Citrix ADC VPX Release 13.1 or NetScaler Release 14.1 Virtual Appliance.

  2. Download one of the VPX Packages for New Installation.

  3. Extract the downloaded .zip file.
  4. In vSphere Client, Deploy OVF template.

Before powering on the appliance, edit the virtual hardware.

  1. If you are licensed for VPX 1000 or higher, increase the CPU count. VPX 1000 is licensed for 4 vCPUs.
  2. Consider setting Memory to 4 GB for each packet engine. A VPX 200 has one packet engine. A VPX 1000 has three packet engines.
  3. Change the NIC Adapter type to VMXNET3 or SR-IOV.
    • Citrix CTX224576 NetScaler VPX Loses Network Connectivity Intermittently on VMware ESXi After Upgrading to Version 12.0 recommends VMXNET3 as a workaround to network connectivity issues in recent Citrix ADC VPX builds.
    • If you choose to use VMXNET3 instead of E1000, make sure all of the NICs are VMXNET3. You cannot mix NIC types.
    • If you already licensed your appliance, jot down the E1000 MAC address, and configure the new VMXNET3 NIC with the same MAC address as the E1000 NIC so you don’t have to redo your license file.
    • To change the NIC Adapter Type, remove the existing NIC, click OK to close Edit Settings, then go back into Edit Settings and Add New Device.
  4. NetScaler 14.1 build 21 and later let you expand size of Hard Disk 1 and after the reboot NetScaler will automatically expand the /var partition, which you can see by running df -h in the shell.

  5. ADC 13.1 build 21.50 and later let you add a second disk to the ADC for storage of logs and crash files. These log and crash files tend to consume disk space on the main drive, which prevents firmware updates, so moving them to a second disk should allow firmware updates to succeed. You can add the second disk at any time, but pre-existing files will not be moved, so it’s best to add the second disk when the VPX is first deployed.

    • The new disk is mounted under /var/crash.
    • The /var/crash directory has several folders that are symlinked from the first drive to the second drive.

  6. NetScaler 14.1 build 21 and later let you expand size of Hard Disk 1 and after the reboot NetScaler will automatically expand the /var partition, which you can see by running df -h in the shell.

  7. Or see NetScaler Article Manually adjust NetScaler VPX Disk Space to use gpart to increase the partition size.

Auto-Provision IP Address

When importing VPX into a hypervisor, you can use VM advanced configuration parameters to set the NSIP. See CTX128250 How to Auto-Provision NetScaler VPX Appliance on a VMware ESX or ESXi Host, and CTX128236 How To Auto-Provision NetScaler VPX on XenServer.

Power On VPX and configure NSIP

  1. After importing the VPX OVF file and changing the NICs to VMXNET3, power on the Citrix ADC VPX appliance.
  2. Configure the management IP from the VM’s console.
  3. Then point your browser to the management IP using either http or https and login as nsroot with password nsroot.
  4. In ADC 13.0 build 67 and newer, you’ll be prompted to change the default nsroot password.

Customer User Experience Improvement Program

  1. You might be prompted to enable the Customer User Experience Improvement Program. Either click Enable, or click Skip.
  2. You can also enable or disable the Customer Experience Improvement Program by going to System > Settings.
  3. On the right is Change CUXIP Settings.
  4. Make your selection and click OK.
  5. See for additional places where CEIP is enabled.
set system parameter -doppler ENABLED

Welcome Wizard

Citrix ADC has a Welcome! Wizard that lets you set the NSIP, hostname, DNS, licensing, etc. It appears automatically the first time you login.

  1. Click the Subnet IP Address box.
  2. You can either enter a SNIP for one of your production interfaces, or you can click Do it later and add SNIPs later after you configure Port Channels and VLANs.
    Note: If you have a dedicated management network, to prevent the management network from being used for outgoing traffic, don’t put a SNIP on the management subnet.

    add ns ip -type SNIP
  3. Click the Host Name, DNS IP Address, Time Zone and NTP Server box.
  4. Enter a hostname. In a High Availability pair each node can have a different hostname. You typically create a DNS record that resolves the hostname to the NSIP (management IP).
  5. Enter one or more DNS Server IP addresses. Use the plus icon on the right to add more servers.
  6. Change the time zone to GMT-05:00-CDT-America/Chicago or similar.
  7. Add one or more NTP Servers.
  8. Click Done.

    set ns hostname ns02
    add dns nameServer
    set ns param -timezone "GMT-06:00-CST-America/Chicago"
  9. Click Yes to save and reboot.
  10. Click the Licenses box.
  11. On the far right side of the screen you’ll see the Host ID. You’ll need this to allocate your licenses at See below for detailed instructions on how to allocate the license to this Host ID.
  12. On the left, select Upload license files, and click Browse.
  13. Browse to the license file, open it, and click Reboot when prompted.

    • License files are stored in /nsconfig/license.
  14. After the reboot and logging in, a box will pop up showing you the installed license, including Days to Expiration.
  15. Also look in the top left corner to make sure it doesn’t say ADC VPX (Freemium). The number in the parentheses should match the MPX or VPX model number.

  16. 30 days prior to license expiration will be a banner at the top of the GUI. It also sends an SNMP trap.
  17. In ADC 13.1 build 24 and newer, you can adjust the number of days before expiration by clicking Manage Licenses, and then edit the Notification Settings on the bottom.

Licensing – VPX Mac Address

To license a Citrix ADC VPX appliance, you will need its MAC address.

  1. Go to the Configuration tab.
  2. In the right pane, look down for the Host Id field. This is the MAC address you need for license allocation.
  3. Another option is to SSH to the appliance and run shell.
  4. Then run lmutil lmhostid. The MAC address is returned.

License Allocation at

Allocate a Citrix ADC VPX license:

  1. Login to
  2. On the left, click Manage Licenses.
  3. If you are activating an eval license, at the bottom of the page, click Don’t see a new license and enter the eval license key.

  4. In the blue Find a license by… box, change the drop-down to Product name, enter adc in the text box, and click Search.
  5. Select one of your ADC VPX licenses, open the Select an action menu, and click Allocate licenses.
  6. Change the quantity to 1.
  7. In the Host field, enter the Host ID (Mac Address) you got from your VPX appliance.
  8. Click Create license file.
  9. Click Yes, create license file.
  10. Click Download license file and save it somewhere.

In Citrix ADC Standard Edition or higher, some Citrix Gateway Universal Licenses are included in your Citrix ADC platform license. There is no need to allocate a license file for these built-in licenses.

  • Citrix ADC Standard Edition comes with 500 Gateway Universal licenses
  • Citrix ADC Advanced Edition comes with 1,000 Gateway Universal licenses
  • Citrix ADC Premium Edition comes with unlimited Gateway Universal licenses

Citrix Gateway VPX Enterprise Edition does not come with any Gateway Universal Licenses. Citrix Gateway VPX Enterprise Edition is a Gateway-only edition that has fewer features than Citrix ADC Standard Edition.

If you need more Gateway Universal licenses than your ADC Edition provides, then you can acquire Gateway Universal licenses by purchasing Citrix Virtual Apps and Desktops (CVAD) Premium Edition, Citrix Endpoint Management Enterprise Edition, or a la carte. Then allocate the additional Citrix Gateway Universal licenses at

  1. Search for gateway licenses, select Citrix Gateway Universal License, open the Select an action menu, and click Allocate licenses.
  2. Change the quantity, or leave it set to allocate all licenses.
  3. Enter your appliance hostname (not Mac address). If you have two appliances in a HA pair, allocate these licenses to the first appliance hostname, then reallocate them to the second appliance hostname.

    1. To get a Citrix ADC’s hostname, login to the ADC as nsroot, and then click the gear icon on the top right.
    2. In the third row, notice the case sensitive Host Name.
  4. Click Create license file.
  5. Click Yes, create license file.
  6. Click OK when prompted to download your license file. Save it somewhere you know where you are saving it.
  7. If you have two appliances in a High Availability pair with different hostnames then you will need to return the Citrix Gateway Universal licenses and reallocate them to the other hostname. The Select an action menu has a Return allocations option.

Install Licenses on Appliance

If you haven’t already installed licenses on your appliance, then do the following:

  1. If the Setup wizard is open, click the fourth row for Licenses.
  2. Otherwise, in the Citrix ADC Configuration GUI, on the left, expand System, and click Licenses.
  3. On the top right, click Manage Licenses.
  4. Click Add New License.
  5. If you have a license file, select Upload license files, and then click Browse. Select the license file(s), and click Open.

    • License files are stored in /nsconfig/license.
  6. Click Reboot when prompted.

  7. After reboot, log in. If you allocated and installed your license correctly, then the top left should no longer say Freemium.
  8. A window will appear showing the installed license.

    1. Notice that Maximum ICA Users Allowed is set to Unlimited.
    2. Maximum NetScaler Gateway Users Allowed will vary depending on your Citrix ADC Edition.
    3. Days to Expiration is shown.
  9. Note: the Citrix ADC SNMP counter allnic_tot_rx_mbits must remain less than the licensed bandwidth or packets will drop.

VPX 100% CPU

Citrix ADC VPX packet engine consumes 100% of the hypervisor CPU. VPX 200 and lower only have one packet engine, so it’s probably consuming around 50% CPU.

You can change this behavior by doing the following:

  1. On the left, go to System > Settings.
  2. On the right, in the bottom of the second column, click Change VPX Configuration Settings.
  3. Change the CPU Yield drop-down to YES, and click OK.

  4. After making this change, you can see an immediate drop-off in CPU consumption.

Upgrade Firmware

Citrix CTX241500 Citrix ADC Firmware Release Cycle:

  • Versions that end in x.1 (e.g. 11.1, 12.1, 13.1, 14.1 etc.) get three years of maintenance releases after one year of feature releases (new features).
  • Versions that end in x.0 (e.g. 12.0, 13.0, 14.0, etc.) get one year of maintenance releases after one year of feature releases (new features).

See the Health Check article for the latest firmware versions that resolve security vulnerabilities.

License – Newer firmware is enforcing license subscription dates in the license file. If you don’t have pooled licensing, then check the CSS dates in your license file:

  1. On NetScaler ADC, go to /nsconfig/license and edit your license file.
  2. Make sure the left date is newer than today. If not, then you’ll need to go to and re-download the license file for this appliance. The newer license file should have a newer date.

Classic Policies – Gateway Classic Policies (classic authentication policies, classic Session Policies, classic Authorization Policies, etc.) still work in NetScaler 14.1, so it’s not necessary to convert your Gateway Classic Policies to Gateway Advanced Policies before you upgrade.

In ADC 13.1 and newer, some non-Gateway features have been removed. To verify that your config does not use the removed features, see Citrix’s Github for a validation script. NetScaler 14.1 build 17 and newer have an upgrade option in the GUI to Enable NSPEPI Tool to check the config before upgrading.

  1. Go to the root of the Github ADC-scripts repository, click the green Code button and then click Download ZIP. Unzip it after downloading.
  2. Use WinSCP or similar to upload the files to the ADC. In the nspepi folder, upload the files nspepi and check_invalid_config to /netscaler on the ADC. Also upload the \nspepi\nspepi2 folder to the /netscaler/nspepi2 folder on the ADC. Replace the existing files.
  3. SSH to ADC and run shell.
  4. Run the following commands and then review the output:
    cd /netscaler
    chmod +x check_invalid_config
    ./check_invalid_config /nsconfig/ns.conf

NetScaler Console (formerly known as Citrix ADM) can upgrade firmware. NetScaler Console can also schedule the firmware upgrade instead of doing it immediately. NetScaler Console does a precheck to make sure there are no upgrade issues. For more details, see Creating Maintenance Tasks at NetScaler Docs.

To upgrade firmware using the NetScaler GUI (source = Upgrade a high availability pair at NetScaler Docs):

  1. To do an ISSU upgrade (zero downtime, no TCP disconnects), NetScaler Docs says that HA Sync VLAN should be configured. In a typical deployment where NSIP is not on a tagged VLAN, set it to VLAN 1. Set it on each node at System > High Availability > Nodes > 0 > Edit.
  2. Download firmware. Ask your Citrix Partner or Citrix Support for recommended versions and builds. You want the Firmware Build, not the VPX (Virtual Appliance).
    Note: Firmware for NetScaler Gateway is identical to firmware for NetScaler. Either one will work on either appliance type.

  3. Watch the Security Bulletins to determine which versions and builds resolve security issues. You can subscribe to the Security Bulletins at by clicking your avatar on the top right after logging in and then clicking My support alerts.

    • Some security updates require additional configuration. For example, CTX330728 requires the command. -ys maxclientForHttpdInternalService=30
  4. Save config – Make sure you Save the config before beginning the upgrade. If you do this on the Primary, then both nodes will save their configs.
  5. License – Transferring the firmware upgrade file to the appliance will be slow unless you license the appliance first. An unlicensed appliance will reduce the maximum upload speed to 20 Mbps.
  6. Backup – Before upgrading the appliance, consider using WinSCP or similar to back up the /flash/nsconfig directory.
  7. Start with the Secondary appliance.
  8. Disk Cleanup – VPXs usually don’t have enough free space to perform the upgrade.

    • NetScaler 14.1 build 21 and later let you expand size of Hard Disk 1 and after the reboot NetScaler will automatically expand the /var partition, which you can see by running df -h in the shell.

    • If you SSH to the appliance, run shell, run cd /var, then you can run the following command to see disk space consumption sorted by highest:
      du -d 1 | sort -n -r

    • /var/nsinstall has old firmware upgrades that can be deleted.
    • Check /var/netscaler/nsbackup for old backup files.
    • A common consumer of disk is the counter files located in /var/nslog.
    • Also look in /var/core for crash dumps.
  9. In the Citrix ADC GUI, with the top left node System selected, on the right, click System Upgrade.
  10. Click Choose File and browse to the build…tgz file.
  11. NetScaler 14.1 build 17 and newer have an upgrade option to Enable NSPEPI Tool to check the config before upgrading.
  12. Click Upgrade.
  13. The firmware will upload.
  14. You should eventually see a System Upgrade window with text in it. If you previously saved your config, then click Yes when asked to reboot. Otherwise, click No, save your config, and then click Reboot.
  15. Go back to the System node. On the right, click the Reboot button.
  16. Click OK to reboot.
  17. After the reboot, after you login, you can see the firmware version by clicking your name on the top right of the browser window.
  18. Once the Secondary is done, login, go to System, and click the Migration button to start the zero downtime upgrade as detailed at NetScaler Docs. This is a new feature in ADC 13.

    • Or go to System > High Availability > Nodes and do a Force Failover.
  19. Click Start Migration. It will take some time for client connections to drain off of the Primary and move to the upgraded appliance.
  20. You can go back into the Migration window and click the link labelled Click to show migration details to see if the failover is complete or not.

  21. Then upgrade the firmware on the former Primary.
  22. Go to System > HA > Nodes and verify the Synchronization State. If one of them is disabled, then edit the node, and check the box next to Secondary node will fetch the configuration from Primary.

To install firmware by using the command-line interface

  1. To upload the software to the Citrix ADC, use a secure FTP client (e.g. WinSCP) to connect to the appliance.
  2. Create a version directory under /var/nsinstall (e.g. /var/nsinstall/
  3. Copy the software from your computer to the /var/nsinstall/<version> (e.g. /var/nsinstall/ directory on the appliance.
  4. Open a Secure Shell (SSH) client (e.g. Putty) to open an SSH connection to the appliance.
  5. At a command prompt, type shell.
  6. At a command prompt, type cd /var/nsinstall/<version> to change to the nsinstall directory.
  7. To view the contents of the directory, type ls.
  8. To unpack the software, type tar -xvzf build_X_XX.tgz, where build_X_XX.tgz is the name of the build to which you want to upgrade.
  9. To start the installation, at a command prompt, type ./installns.
  10. When the installation is complete, restart Citrix ADC.
  11. When the Citrix ADC restarts, at a command prompt type what or show version to verify successful installation.
  12. To failover the pair without downtime, enter migrate ns and wait for connections to drain off the former primary appliance.
  13. Then repeat these steps to upgrade the former primary appliance.

High Availability

Configure High Availability as soon as possible to ensure that almost all configurations are synchronized across the two appliances. The synchronization exceptions are mainly network interface configurations (e.g. LACP).

High Availability will also sync files between the two appliances. See CTX138748 File Synchronization in NetScaler High Availability Setup for more information.

  1. Prepare the secondary appliance:
    1. The secondary appliance must be the same hardware as the primary appliance.
    2. Login to the second appliance and configure a NSIP.
    3. Don’t configure a SNIP. In Step 2, Subnet IP Address, you can click Do It Later to skip the wizard. You’ll get the SNIP later when you pair it with the primary.
    4. Configure Hostname, Time Zone, and NTP Servers.
    5. Don’t configure DNS since you’ll get those addresses when you pair it. However, if NTP points to a DNS name, then NTP won’t work until you pair the appliance.
    6. License the secondary appliance. The new secondary appliance must be the same edition (License Type) as the former primary appliance.

    7. Upgrade firmware on the secondary appliance. The firmware of both nodes must be identical.
  2. On the secondary appliance, go to System > High Availability > Nodes.
  3. On the right, edit the local node.

    1. Change High Availability Status to STAY SECONDARY and click OK. If you don’t do this then you run the risk of losing your config when you pair the appliances.

      set ha node -hastatus STAYSECONDARY
  4. On the primary appliance, on the left, expand System, expand Network, and click Interfaces.

    1. On the right, look for any interface that is currently DOWN.
    2. You need to disable those disconnected interfaces before enabling High Availability. Right-click the disconnected interface, and click Disable. Repeat for the remaining disconnected interfaces.

      show interface
      disable interface 1/1
  5. On the primary appliance, on the left, expand System, expand High Availability, and click Nodes.
  6. On the right, edit node 0.

    1. Change the High Availability Status to STAY PRIMARY, and click OK.
  7. On the right, click Add.

    1. Enter the other Citrix ADC’s NSIP address.
    2. Enter the other Citrix ADC’s login credentials, and click Create.

      add ha node 1
      Note: this CLI command must be run separately on each appliance.
  8. If you click the refresh icon near the top right, Synchronization State will probably say IN PROGRESS. Keep refreshing until it says SUCCESS.
  9. Edit Node ID 0 (the local appliance).

    1. Change High Availability State back to ENABLED.
    2. Under Fail-safe Mode, check the box next to Maintain one primary node even when both nodes are unhealthy.
    3. Scroll down, and click OK.

      set ha node -failSafe ON
  10. If you login to the Secondary appliance, you might see a message warning you against making changes. Always apply changes to the Primary appliance.
  11. On the secondary appliance, go to System > High Availability > Nodes and edit the local node 0.
  12. Change it from STAY SECONDARY to ENABLED. Also enable Fail-safe Mode. Click OK.
  13. On the new secondary appliance, go to System > Network > Routes, and make sure you don’t have two routes. Joining an appliance to an HA pair causes the default route on the primary appliance to sync to the secondary appliance. But, it doesn’t delete the default gateway that was formerly configured on the secondary appliance.
  14. From the Citrix ADC CLI (SSH), run “sh ha node” to see the status. You should see heartbeats on all interfaces. If not, configure VLANs as detailed later..
  15. You can also disable HA heartbeats on specific network interfaces (System > Network > Interfaces).

    1. Note: Make sure HA heartbeats are enabled on at least one interface/channel.
    2. Note: this is an interface configuration, which means this configuration change is not propagated to the other node.
  16. To do an ISSU upgrade (zero downtime, no TCP disconnects), Citrix Docs says that HA Sync VLAN should be configured. In a typical deployment where NSIP is not on a tagged VLAN, set it to VLAN 1. Set it on each node at System > High Availability > Nodes > 0 > Edit.

HA Failover

  1. HA Failover changes the MAC address associated with VIPs and SNIPs. If your firewall (e.g. Cisco ASA) doesn’t like Gratuitous ARP, then see CTX112701 – The Firewall Does not Update the Address Resolution Protocol Table
  2. ADC 13 adds a graceful node Migrate operation which drains sessions instead of drops sessions.
    1. Once migration is started, the two nodes no longer synchronize their configurations. The only way to clear the migration status is to reboot the Secondary. See zero downtime upgrade at Citrix Docs.
    2. Go to System, and click the Migrate button to start the Migrate operation.
    3. Click Start Migration. It will take some time for client connections to drain off of the Primary and move to the upgraded appliance.

      migrate ns
    4. To clear the migration and allow nodes to be failed over again, reboot the secondary.
    5. Go to System > HA > Nodes and verify the Synchronization State. If one of them is disabled, then edit the node, and check the box next to Secondary node will fetch the configuration from Primary.

  3. Instead of Migrate, you can do a Force Failover, which does not require a reboot, and the nodes continue synchronizing.
    1. Go to System > High Availability > Nodes, open the menu named Select Action, and do a Force Failover.

      force ha failover

Port Channels on Physical Citrix ADC MPX

If you are configuring a Citrix ADC MPX (physical appliance), and if you plugged in multiple cables, and if more than one of those cables is configured on the switch for the same VLAN(s), then you must bond the interfaces together by configuring a Port Channel.

  • On the switch, create a Port Channel, preferably with LACP enabled.
  • The Port Channel can be an Access Port (one VLAN), or a Trunk Port (multiple VLANs).
  • On the Citrix ADC, configure LACP on the network interfaces, or create a Channel manually. Both methods are detailed below.

Also see Webinar: Troubleshooting Common Network Related Issues with NetScaler.

LACP Port Channel

To configure Port Channels on a Citrix ADC, you can either enable LACP, or you can configure a Channel manually. If your switch is configured for LACP, do the following on Citrix ADC to enable LACP on the member interfaces.

  1. Go to System > Network > Interfaces.
  2. On the right, edit one of the Port Channel member interfaces.
  3. Scroll down.
  4. Check the box next to Enable LACP.
  5. In the LACP Key field, enter a number. The number you enter here becomes the channel number. For example, if you enter 1, Citrix ADC creates a Channel named LA/1. All member interfaces of the same Port Channel must have the same LACP Key. Click OK when done.
  6. Continue enabling LACP on member interfaces and specifying the key (channel number). If you are connected to two port channels, one set of member interfaces should have LACP Key 1, while the other set of member interfaces should have LACP Key 2.
  7. In an HA pair, you must perform this interface configuration separately on both nodes. The LACP commands are not propagated across the HA pair.
  8. If you go to System > Network > Channels.
  9. You’ll see the LACP Channels on the right. These were created automatically after you set the LACP Key on the interface.
  10. If you edit a Channel, there’s a LACP Details tab that shows you the member interfaces.

Manual Channel

If your switch ports are not configured for LACP, then you can instead create a Channel manually.

  1. Go to System > Network > Channels.
  2. On the right, click Add.
  3. At the top, choose an unused Channel ID (e.g. LA/1).
  4. On the bottom, in the Bind/Unbind section, click Add.
  5. Click the plus icon next to each member interface to move it to the right. Then click Create.

Redundant Interface Set

You can also configure the Citrix ADC for switch-independent teaming. Create a Channel manually, but select a Channel ID starts with LR instead of LA. This is called Link Redundancy or Redundant Interface Set.

Channel Minimum Throughput

Channels can be configured so that a High Availability failover occurs when the Channel throughput drops below a configured value. For example, if you have four members in a Channel, you might want a High Availability failover to occur when two of the member interfaces fail.

  1. Go to System > Network > Channels, and edit a Channel.
  2. Near the top, enter a minimum threshold value in the Throughput field. If the total bonded throughput drops below this level, a High Availability failover will occur.

Trunk Port and High Availability

If you are trunking multiple VLANs across the channel, and if every VLAN is tagged (no native VLAN), then a special configuration is needed to allow High Availability heartbeats across the channel.

  1. Go to System > Network > VLAN.
  2. Add a VLAN object.
  3. Bind the VLAN to a channel or interface. To bind multiple VLANs to a single interface/channel, the VLANs must be tagged.
  4. Configure one of the VLANs as untagged. Only untag one of the VLANs. Which one you untag doesn’t matter. If your switch doesn’t allow untagged packets, don’t worry, we’ll fix that soon.
  5. If your switch doesn’t allow untagged packets, go to System > Network > Channels, and edit the channel.
  6. Scroll down and switch to the tab named Settings.
  7. Set Tag all VLANs to ON to cause Citrix ADC to tag all packets, including the VLAN you formerly marked as untagged.
    • We essentially moved the VLAN tagging from the VLAN to the Channel/Interface, which means VLAN tagging happens lower in the network stack so High Availability heartbeat packets are also tagged.
  8. Note: in an HA pair, you must perform this Tagall configuration separately on both nodes. The Tagall command is not propagated across the HA pair.

Common physical interface configuration

Here is a common Citrix ADC networking configuration for a physical Citrix ADC MPX that is connected to both internal and DMZ.

Note: If the appliance is connected to both DMZ and internal, then be aware that this configuration essentially bypasses (straddles) the DMZ-to-internal firewall. That’s because if a user connects to a public/DMZ VIP, then Citrix ADC could use an internal SNIP to connect to the internal server: in other words, traffic comes into a DMZ VLAN, but goes out an internal VLAN. A more secure approach is to have different appliances for internal and DMZ. Or use Citrix ADC SDX, partitioning, or traffic domains.

  • 0/1 connected to a dedicated management network. NSIP is on this network.
    • No data on 0/1 – 0/1 is not optimized for high throughput so don’t put data traffic on this interface. If you don’t have a dedicated management network, then put your NSIP on one of the other interfaces (1/1, 10/1, LA/1, etc.) and don’t connect any cables to 0/1.
    • No SNIP on management network – To prevent Citrix ADC from using this dedicated management interface for outbound data traffic, don’t put a SNIP on this management network, and configure the default gateway (route to use a router on a different data network (typically the DMZ VLAN). However, if there’s no SNIP on this VLAN, and if the default gateway is on a different network, then there will be asymmetric routing for management traffic, since inbound management traffic goes in 0/1, but reply traffic goes out LA/1 or LA/2. To work around this problem, enable Mac Based Forwarding, or configure Policy Based Routing. Both of these options are detailed in the next section.
    • Management VLAN tagging – It’s easiest if the switch port for this dedicated management interface is an Access Port (untagged). If VLAN tagging is required, then NSVLAN must be configured on the Citrix ADC.
  • 10/1 and 10/2 in a LACP port channel (LA/1) connected to internal VLAN(s). Static routes to internal networks through a router on one of these internal VLANs.
    • Access Port – If only one internal VLAN, configure the switch ports/channel as an Access Port.
    • Trunk Port – If multiple internal VLANs, configure the switch ports/channel as a Trunk Port. Set one of the VLANs as the channel’s Native VLAN so it doesn’t have to be tagged.
    • Tag HA heartbeat packets – If the networking team is unwilling to configure a Native VLAN on the Trunk Port, then Citrix ADC needs special configuration (tagall) to ensure HA heartbeat packets are tagged.
  • 1/1 and 1/2 in a LACP port channel (LA/2) connected to DMZ VLAN(s). The default gateway (route points to a router on a DMZ VLAN so replies can be sent to Internet clients.
    • Access Port – If only one DMZ VLAN, configure the switch ports/channel as an Access Port.
    • Trunk Port – If multiple DMZ VLANs, configure the switch ports/channel as a Trunk Port. Set one of the VLANs as the channel’s Native VLAN so it doesn’t have to be tagged.
    • Tag HA heartbeat packets – If the networking team is unwilling to configure a Native VLAN on the Trunk Port, then Citrix ADC needs special configuration (tagall) to ensure HA heartbeat packets are tagged.

Dedicated Management Subnet

If your Citrix ADC is connected to multiple subnets, then one of those subnets could be a Dedicated Management Subnet. If you have a subnet that is for NSIP only, and if you don’t want to use the NSIP subnet for data traffic, then you’ll want to move the default route off of the NSIP subnet and onto a different data subnet. However, moving the default route breaks traffic from the NSIP. To work around this problem, create PBRs for the NSIP traffic, including both replies from NSIP, and traffic sourced by the NSIP (e.g. Syslog).

Citrix Blog Post Separating NetScaler Management and Data Traffic for DISA STIGs also uses PBRs.

  1. Go to System > Network > PBRs. You can also search the menu for PBRs.
  2. On the right, click Add.
  3. Give the PBR a name (e.g. NSIP)
  4. Set the Next Hop Type drop-down to New.
  5. In the Next Hop field, enter the router IP address that is on the same network as the NSIP.
  6. In the Configure IP section, set the first Operation drop-down to =.
  7. In the Source IP Low field, enter the NSIP. This causes the PBR to match all traffic with NSIP as the Source IP address.
    • In an HA pair, the PBR command is synced and applied to both nodes in the pair. To accommodate this, in the Source IP Low field, enter the lower NSIP address. Then in the Source IP High field, enter the higher NSIP address.
  8. You don’t need anything else.
  9. Scroll down, and click Create. This rule routes any traffic with NSIP as source IP address through a router on the NSIP subnet. The default route will be ignored, but only for NSIP traffic.
  10. DNS traffic is special. To handle DNS traffic sourced by the NSIP, create another PBR by right-clicking the existing one, and clicking Add.
  11. Change the name to NSIP-DNS or similar.
  12. Change the Action drop-down to DENY, which tells ADC that traffic matching this PBR should use normal routing instead of overriding to a different gateway.
  13. Change the Priority to a lower number than the original PBR so this rule is matched before the general NSIP rule. Scroll down.
  14. In the Configure IP section, remove all settings.
  15. In the Configure Protocol section, click the Protocol drop-down, and select UDP (17).
  16. Above the two Destination port fields, change the Operation to =.
  17. In the Destination port Low field, enter 53.
  18. Scroll down, and click Create.
  19. Make sure the DENY PBR is higher in the list (lower priority number) than the ALLOW PBR.
  20. Then open the Action menu, and click Apply.
  21. Click Yes to apply.

    add ns pbr NSIP-DNS DENY -destPort = 53 -nextHop -protocol UDP -priority 5
    add ns pbr NSIP ALLOW -srcIP = -nextHop
    apply ns pbrs

Floating Management IP

If you want a floating management IP that is always on the Primary appliance, here’s a method of granting management access without adding a SNIP to the management subnet:

  1. Create a Load Balancing Service on HTTP 80 on IP address Note: Citrix ADC doesn’t allow creating a Load Balancing service on IP address and port 443 (SSL).

    • The IP address you enter is When you view the Load Balancing Service, it shows the local NSIP. After a HA failover, the IP Address will change to the other NSIP.
  2. Create a Load Balancing Virtual Server using a VIP on the management subnet. Protocol = SSL. Port number = 443. Bind a certificate.

    1. Bind the loopback:80 service to the Load Balancing Virtual Server. In summary: the front end is 443 SSL, while the LB Service is 80 HTTP.
  3. Add the new VIP to the PBRs so the replies go out the correct interface. Re-apply the PBRs after you modify them.

  4. You should then be able to point your browser to https://Step2VIP to manage the appliance.
  5. You can perform the same loopback trick for 22 SSH. Create a Load Balancing Service on TCP 22 on IP address
  6. Create a Load Balancing Virtual Server using the same management VIP specified earlier. Protocol = TCP. Port number = 22.

    1. Bind the loopback:TCP:22 service to the Load Balancing Virtual Server.
  7. You should then be able to point your SSH Client to <Step2VIP> to manage the appliance.
  8. CLI Commands for the floating management VIP:
    add service mgmt HTTP 80
    add service mgmt-SSH TCP 22
    add lb vserver mgmt-SSL SSL 443
    add lb vserver mgmt-SSH TCP 22
    bind lb vserver mgmt-SSL mgmt
    bind lb vserver mgmt-SSH mgmt-SSH
    set ns pbr NSIP-DNS DENY -srcIP = -destPort = 53 -protocol UDP -priority 5
    set ns pbr NSIP ALLOW -srcIP = -nextHop
    apply ns pbrs

Multiple Subnets / Multiple VLANs

Best practices for network configurations at Citrix Docs and Citrix CTX214033 Networking and VLAN Best Practices for NetScaler discusses many of the same topics detailed in this section.

If this is a physical MPX appliance, see the previous Port Channel section first.

If you only connected Citrix ADC to one subnet (one VLAN) then skip ahead to DNS servers.

Configuration Overview

The general configuration process for multiple subnets is this:

  1. Create a SNIP for each subnet/VLAN.
  2. Create a VLAN object for each subnet/VLAN.
    1. Bind the VLAN object to the SNIP for the subnet.
    2. Bind the VLAN object to the Port Channel or single interface that is configured for the VLAN/subnet.

SNIPs for each VLAN

You will need one SNIP for each connected subnet/VLAN. VLAN objects (tagged or untagged) bind the SNIPs to particular interfaces. Citrix ADC uses the SNIP’s subnet mask to assign IP addresses to particular interfaces.

NSIP Subnet

The NSIP subnet is special, so you won’t be able to bind it to a VLAN. Use the following SNIP/VLAN method for any network that does not have the NSIP. The remaining interfaces will be in VLAN 1, which is the VLAN that the NSIP is in. VLAN 1 is only locally significant so it doesn’t matter if the switch is configured with it or not. Just make sure the switch has a native VLAN configured, or configure the interface as an access port. If you require trunking of every VLAN, including the NSIP VLAN, then additional configuration is required (NSVLAN or Tagall).

Configure Subnets/VLANs

To configure Citrix ADC with multiple connected subnets:

  1. Add a subnet IP for every network the Citrix ADC is connected to, except the dedicated management network. Expand System, expand Network, and click IPs.
  2. On the right, click Add.

    1. Enter the Subnet IP Address for this network/subnet. The SNIP will be the source IP address the Citrix ADC will use when communicating with any other service/server on this network. The Subnet IP is also known as the Interface IP for the network. You will need a separate SNIP for each connected network (VLAN).
    2. Enter the netmask for this network.
    3. Ensure the IP Type is set to Subnet IP. Scroll down.

      add ns ip -type SNIP
    4. Under Application Access Controls, decide if you want to enable GUI management on this SNIP. This feature can be particularly useful for High Availability pairs, because when you point your browser to the SNIP, only the primary appliance will respond. However, enabling management access on the SNIP can be a security risk, especially if this is a SNIP for a DMZ network.
    5. Click Create when done. Continue adding SNIPs for each connected network (VLAN).

      set ns ip -mgmtAccess ENABLED -telnet DISABLED -ftp DISABLED
  3. On the left, expand System, expand Network, and click VLANs.
  4. On the right, click Add.

    1. Enter a descriptive VLAN ID. The actual VLAN ID only matters if you intend to tag the traffic. If not tagged, then any ID (except 1) will work.
    2. In the Interface Bindings section, check the box next to one physical interface or channel (e.g. LA/1) that is connected to the network.
    3. If this is a trunk port, select Tagged if the switch port/channel is expecting the VLAN to be tagged.
    4. If your switches do not allow untagged packets, then you will need to use the tagall interface option to tag Citrix ADC High Availability heartbeat packets. See CTX122921 Citrix NetScaler Interface Tagging and Flow of High Availability Packets
    5. If you don’t tag the VLAN, then the Citrix ADC interface/channel is removed from VLAN 1, and instead put in this VLAN ID.
    6. Switch to the tab named IP Bindings.
    7. Check the box next to the Subnet IP for this network. This lets Citrix ADC know which interface is used for which IP subnet. Click Create when done.

      add vlan 50
      bind vlan 50 -ifnum LA/1 -IPAddress
  5. Add static routes to the internal networks through an internal router.
    1. On the left, expand System, expand Network, and click Routes.
    2. On the right, click Add.
    3. Make sure NULL Route is set to No.
    4. Set the Gateway (next hop) to an internal router.
    5. Then click Create.

      add route
  6. The default route should be changed to use a router on the DMZ network (towards the Internet). Before deleting the existing default route, either enable Mac Based Forwarding, or create a Policy Based Route, so that the replies from NSIP can reach your machine. You usually only need to do this for dedicated management networks.
    1. Note: PBR is recommended over MBF, because PBR can handle traffic sourced by NSIP (e.g Syslog traffic), while MBF cannot.
    2. Mac Based Forwarding sends replies out the same interface they came in on. However, MBF ignores the routing table, and doesn’t handle traffic sourced by the NSIP (e.g. LDAP traffic). To enable MBF:
      1. On the left, expand System, and click Settings.
      2. On the right, in the left column, click Configure modes.
      3. Check the box next to MAC Based Forwarding (MBF), and click OK. More info on MAC Based Forwarding can be found at Citrix CTX1329532 FAQ: Citrix NetScaler MAC Based Forwarding (MBF).

        enable mode mbf
  7. Go back to System > Network > Routes.
    1. On the right, delete the route. Don’t do this unless the Citrix ADC has a route, PBR, or MBF to the IP address of the machine you are running the browser on.

      rm route
    2. Then click Add.
    3. Set the Network to, and the Netmask to
    4. Make sure NULL Route is set to No.
    5. Enter the IP address of the DMZ (or data) router, and click Create.

      add route

DNS Servers

  1. To configure DNS servers, expand Traffic Management, expand DNS, and click Name Servers.
  2. On the right, click Add.

    1. Enter the IP address of a DNS server, and click Create.
    2. Note: The Citrix ADC must be able ping each of the DNS servers, or they will not be marked as UP. The ping originates from the SNIP.

      add dns nameServer
  3. Citrix ADC includes DNS Security Options, which are useful if you use this Citrix ADC to provide DNS services to clients (e.g. DNS Proxy/Load Balancing, GSLB, etc.). You can configure them at Security > DNS Security.

  4. Additional DNS Security Options are detailed at DNS security options at Citrix Docs.

NTP Servers

  1. On the left, expand System, and click NTP Servers.
  2. On the right, click Add.
  3. Enter the IP Address of your NTP Server (or, and click Create.

    add ntp server
  4. On the right, open the Action menu, and click NTP Synchronization.
  5. Select ENABLED, and click OK. This starts the NTP daemon in BSD to perform the NTP sync.

    enable ntp sync
  6. You can click the System node to view the System Time.
  7. If you need to manually set the time:
    1. SSH (Putty) to the Citrix ADC appliances.
    2. Run shell to access BSD.
    3. Run date to manually set the time. Run date –help to see the syntax.
    4. Ntpdate –u will cause an immediate NTP time update. You’ll need to disable NTP Sync before you can run this command.


Citrix CTX120609 NetScaler Log Rotation and Configuration Using Newsyslog

The Citrix ADC will, by default, store a few syslogs on the local appliance. You can create a syslog policy to also send the syslog entries to an external server, like Citrix Application Delivery Management (ADM).

  1. On the left, expand System, expand Auditing, and click Syslog.
  2. On the right, switch to the Servers tab, and click Add.

    1. Enter a name for the Syslog server.
    2. You can change Server Type to Server Domain Name, and enter a FQDN.
    3. Enter the IP Address or FQDN of the SYSLOG server, and 514 as the port.
    4. Configure the Log Levels you’d like to send to it by clicking CUSTOM – typically select everything except DEBUG.
    5. Select your desired Time Zone and Date Format.
    6. You can optionally enable other logging features. User Configurable Log Messages lets you use Responder policies to generate log entries.
    7. Then click Create.

      add audit syslogAction MySyslogServer -logLevel EMERGENCY ALERT CRITICAL ERROR WARNING -timeZone LOCAL_TIME -userDefinedAuditlog YES
      add audit syslogAction MySyslogServer syslog.corp.local -logLevel EMERGENCY ALERT CRITICAL ERROR WARNING -timeZone LOCAL_TIME -userDefinedAuditlog YES
  3. On the right, switch to the Policies tab, and then click Add.

    1. Give the policy a descriptive name,
    2. Change the Expression Type selection to Advanced Policy.
    3. Select the previously created Syslog server.
    4. And then click Create.

      add audit syslogPolicy MySyslogServer true MySyslogServer
  4. While still on the Policies tab, open the Actions menu, and click Classic Policy Global Bindings or Advanced Policy Global Bindings, depending on which one you chose when creating the Syslog policy.

    1. Click Add Binding.
    2. Click where it says Click to select.
    3. Click the radio button next to the Syslog policy you want to bind, and then click the blue Select button at the top of the page.
    4. Change the Priority to 100 or similar.
    5. If you don’t select anything in Global Bind Type, then it defaults to SYSTEM_GLOBAL.
    6. Click Bind.
    7. Click Done.

      bind audit syslogGlobal -policyName MySyslogServer -priority 100
      bind system global MySyslogServer -priority 100

SNMP – MIB, Traps, and Alarms

  1. On the left, expand System, and click SNMP.
  2. On the right, click Change SNMP MIB.

    1. Change the fields as desired. Your SNMP tool (e.g. Citrix Application Delivery Management (ADM)) will read this information. Click OK.
    2. This configuration needs to be repeated on the other node.

      set snmp mib -contact -name ns02 -location Corp
  3. Expand System, expand SNMP, and click Community.

    1. On the right, click Add.
    2. Specify a community string, and the Permission, and click Create.

      add snmp community public GET
  4. On the left, under SNMP, click Traps.

    1. On the right, click Add.
    2. Specify a trap destination. The fields will vary for V2 vs V3. Click Create. You’ll have to add the Trap Destinations twice so you can select both Generic and Specific.

      add snmp trap generic -communityName public
      add snmp trap specific -communityName public
  5. On the left, under SNMP, click Managers.

    1. On the right, click Add.
    2. Change the selection to Management Network.
    3. Specify the IP of the Management Host, and click Create.

      add snmp manager
  6. The Alarms node allows you to enable SNMP Alarms and configure thresholds.

    1. You can Edit an alarm to set thresholds. For example, CPU-USAGE can be set to 90% alarm, and 50% normal, with a Critical severity.

      set snmp alarm CPU-USAGE -thresholdValue 90 -normalValue 50 -severity Critical
    2. You can also configure the MEMORY alarm.

      set snmp alarm MEMORY -thresholdValue 90 -normalValue 50 -severity Critical

From In addition to the usual OIDs, we have found these very useful to warn of potential problems.

  • ifTotXoffSent – .
  • ifnicTxStalls – .
  • ifErrRxNoBuffs – .
  • ifErrTxNoNSB – .

Call Home

Citrix Blog Post – Protect Your NetScaler From Disaster With Call Home!: If you have a physical Citrix ADC (MPX or SDX) with an active support contract, you may optionally enable Call Home to automatically notify Citrix Technical Support of hardware and software failures.

Call Home at Citrix Docs has information on how it work.

From the Citrix ADC release notes: Call Home is now enhanced to send Citrix ADC usage metrics to Citrix Insight Services (CIS) periodically. Citrix collects the data to understand how the appliance works and how to improve the product. By default, Call Home sends the metrics once in every 7 days. For more information, see Call Home at Citrix Docs.

To enable Call Home:

  1. On the left, expand System, and click Diagnostics.
  2. On the right, in the left column, in the Technical Support Tools section, click Call Home.
  3. Check the box next to Enable Call Home.
  4. Optionally enter an email address to receive notifications from Citrix Technical Support. Click OK.
  5. If you go back into Call Home, it should indicate if registration succeeded or failed. Successful registration requires an active support contract.

Change nsroot Password

  1. In ADC 13.0 build 67 and newer, you’ll be forced to change the default nsroot password.
  2. If you want to force strong passwords for local accounts, go to System > Settings, and on the right, click Change Global System Settings

    1. Scroll down to the Password section.
    2. You can change Strong Password to Enable Local, and also specify a Min Password Length. Click OK.
  3. Expand System, expand User Administration, and click Users.
  4. On the right, right-click nsroot, and click Change Password.
  5. Specify a new password and click OK.

    set system user nsroot Passw0rd

TCP, HTTP, SSL, and Security Settings

Citrix Docs Introduction to best practices for Citrix ADC MPX, VPX, and SDX security

Best practice settings:

  1. On the left, expand System, and click Settings.
  2. On the right, in the right column, click Change TCP parameters.

    1. Check the box for Window scaling (near the top) and set the Factor to 8.
    2. Scroll down and check the box for Selective Acknowledgement.
    3. Nagle’s algorithm should not be checked.
    4. Click OK.

      set ns tcpParam -WS ENABLED -SACK ENABLED
  3. On the right, click Change HTTP parameters.

    1. Under Cookie, change the selection to Version1. This causes Citrix ADC to set Cookie expiration to a relative time instead of an absolute time.

      set ns param -cookieversion 1
    2. Check the box next to Drop invalid HTTP requests. Note: this might break some web sites.
    3. Scroll down, and click OK.

      set ns httpParam -dropInvalReqs ON
  4. From Citrix CTX232321 Recommended TCP Profile Settings for Full Tunnel VPN/ICAProxy from NetScaler Gateway 11.1 Onwards:
    1. Expand System, and click Profiles.
    2. On the right, on the tab named TCP Profiles, edit the nstcp_default_profile.
    3. Enable Window Scaling with a factor of 8.
    4. Set Minimum RTO (in millisec)600.
    5. Set TCP Buffer Size (bytes)600000
    6. Set TCP Send Buffer Size (bytes)600000
    7. Change TCP Flavor = BIC.
    8. Enable Selective Acknowledgement. Don’t enable Nagle’s algorithm.
    9. Click OK when done.
  5. You can run the following command to see statistics on the dropped packets:
    nsconmsg -g http_err_noreuse_ -d stats
  6. See CTX209398 Addressing false positives from CBC and MAC vulnerability scans of SSHD to harden SSHD by editing /nsconfig/sshd_config with the following. Then run kill -HUP `cat /var/run/` to restart SSHD.
    Ciphers aes128-ctr,aes192-ctr,aes256-ctr
    MACs hmac-sha1,hmac-ripemd160

Citrix Knowledgebase articles:

The following security configurations are detailed by Jason Samuel at Mitigating DDoS and brute force attacks against a Citrix Netscaler Access Gateway:

  • Maximum logon attempts on Citrix Gateway Virtual Server
  • Rate Limiting for IP.SRC and HTTP.REQ.URL.
  • nstcp_default_XA_XD_profile TCP profile on the Citrix Gateway Virtual Server.
  • Syslog logging
  • External website monitoring
  • Obfuscate the Server header in the HTTP response
  • Disable management access on SNIPs
  • Change nsroot strong password, use LDAP authentication, audit local accounts
  • Don’t enable Enhanced Authentication Feedback
  • SSL – disable SSLv3, deny SSL renegotiation, enable ECDHE ciphers, disable RC4 ciphers.
  • 2-factor authentication
  • Citrix Application Delivery Management (ADM)
  • Review IPS/IDS & Firewall logs

Management Authentication – LDAP

Load balancing of LDAP servers is strongly recommended. If you bind multiple LDAP servers instead of load balancing them, Citrix ADC will try each of the LDAP servers, and for incorrect passwords, will lock out the user sooner than expected. But if you instead load balance your LDAP servers, the authentication attempt will only be sent to one of them.

  1. Expand System, expand Authentication, expand Basic Policies, and then click LDAP.
  2. On the right, switch to the Servers tab. Then click Add.

    1. Enter LDAPS-Corp-Mgmt or similar 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. Also, the LDAP policy used for management authentication will be different than the LDAP policy used for Citrix Gateway.
    2. Change the selection to Server IP. Enter the VIP of the Citrix ADC load balancing vServer for LDAP.
    3. Change the Security Type to SSL.
    4. Enter 636 as the Port. Scroll down.
    5. In the Connection Settings section, in the Base DN field, enter your Active Directory DNS domain name in LDAP format.
    6. In the Administrator Bind DN field, enter the credentials of the LDAP bind account in userPrincipalName format.
    7. Enter the Administrator Password (bind account password). Click Test LDAP Reachability. Scroll down.
    8. 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.
    9. On the right, check the box next to Allow Password Change.
    10. It is best to restrict access to only members of a specific group. In the Search Filter field, enter memberOf=<GroupDN>. See the example below:
      memberOf=CN=Citrix ADC Administrators,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=Citrix ADC Administrators,OU=Citrix,DC=corp,DC=local
      An easy way to get the full distinguished name of the group is through Active Directory Users & Computers. Make sure Advanced Features is enabled in the View menu. Double-click the group object. Switch to the Attribute Editor tab. Find Distinguished Name and copy it.
      Scroll down to distinguishedName, double-click it, and then copy it to the clipboard.
      Back on the Citrix ADC, in the Search Filter field, type in memberOf=, and then paste the Distinguished Name right after the equals sign. Don’t worry about spaces.
    11. Scroll down and click More to expand it.
    12. For Nested Group Extraction, if desired, change the selection to Enabled.
    13. Set the Group Name Identifier to samAccountName.
    14. Set Group Search Attribute to –<< New >>–, and enter memberOf.
    15. Set Group Search Sub-Attribute to –<< New >>–, and enter CN.
    16. Example of LDAP Nested Group Search Filter Syntax
    17. Scroll down, and click Create.

      add authentication ldapAction Corp-Mgmt -serverIP -serverPort 636 -ldapBase "dc=corp,dc=local" -ldapBindDn "corp\\ctxsvc" -ldapBindDnPassword Passw0rd -ldapLoginName samaccountname -searchFilter "memberOf=CN=Citrix ADC Admins,CN=Users,DC=corp,DC=local" -groupAttrName memberOf -subAttributeName CN -secType SSL -passwdChange ENABLED
  3. On the left, go to System > Authentication > Advanced Policies > Policy.
  4. On the right, click Add.

    1. Enter the name LDAPS-Corp-Mgmt or similar.
    2. Change the Action Type drop-down to LDAP.
    3. Select the previously created LDAPS-Corp-Mgmt server.
    4. On the bottom, in the Expression area, type in true.
    5. Click Create.

      add authentication Policy LDAPS-Corp-Mgmt -rule true -action LDAPS-Corp-Mgmt
  5. Click Global Bindings in the right pane.

    1. Click where it says Click to select.
    2. Click the radio button next to the newly created LDAP policy, and then click the blue Select button at the top of the page.
    3. Click Bind.
    4. Click Done.

      bind system global LDAPS-Corp-Mgmt -priority 100 -gotoPriorityExpression NEXT
  6. Under System, expand User Administration, and click Groups.

    1. On the right, click Add.
    2. In the Group Name field, enter the case sensitive name of the Active Directory group containing the Citrix ADC administrators.

      • ADC 13.0 build 41 and newer lets you restrict a group to the CLI only. Note that GUI access requires API permissions.
    3. In the Command Policies section, click Bind.
    4. Select the superuser policy, and click Insert.
    5. Scroll down, and click Create.

      add system group "Citrix ADC Admins" -timeout 900
      bind system group "Citrix ADC Admins" -policyName superuser 100
  7. To prevent somebody from creating an nsroot account in LDAP (Active Directory) and then using that external nsroot account to login to ADC, disable external authentication on the local nsroot account.
    1. On the left, go to System > User Administration > Users.
    2. On the right, edit the nsroot user.
    3. At the top of the page, in the System User section, click the pencil icon.
    4. Uncheck the box next to Enable External Authentication and then click Continue.
    5. Click Save and then click Done.
  8. If you logout:
  9. You should be able to login to Citrix ADC using an Active Directory account.

Management Authentication – Two Factor

Citrix ADC supports two factor authentication for management access. The technology is based on nFactor but works in all editions of ADC (no licensing restrictions). Here’s a summary of the configuration steps with more detail coming later:

  1. The first authentication factor must be an Advanced Authentication Policy that is bound globally. Classic Authentication Policies will not work.
  2. Create a Login Schema to ask for the second factor password (i.e. passcode).
    • This Login Schema is for second factor only and has no effect on the first factor. The second factor Login Schema should only ask for a single password prompt. It doesn’t appear to be possible to ask for both factors using the same Login Schema.
    • Login Schema for the second factor does not use the normal nFactor language files and you instead must hard code the password prompt label for the second factor logon field directly in the Login Schema .xml file.

  3. Create an Advanced Authentication Server and Policy for the second factor (e.g. RADIUS).
  4. Create an Authentication Policy Label with Feature Type set to RBA_REQ. This is not the default so make sure you change the Feature Type drop-down field.

    1. When creating the Policy Label, select the Login Schema for the second factor.
    2. Bind the second factor Advanced Authentication Policy to the Policy Label.
  5. Go to Global Bindings for Authentication, edit the existing authentication binding, click Next Factor, and select your new Policy Label. That’s it.

Here are detailed configuration instructions for adding a second authentication factor to the management logon page.

  1. Login Schema XML File:
    1. Point WinSCP to your ADC appliance.
    2. Navigate to /nsconfig/loginschema/LoginSchema and download the SingleAuth.xml file.
    3. Rename the file to MgmtNextFactor.xml or something like that.
    4. Edit the file.
    5. Look for the <Requirement> element with ID of passwd. Then look for the Label and set the Text field to whatever you want displayed on the second password page. Save the file when done.
    6. The Label Text you enter will be shown on the second factor logon page.
    7. In WinSCP, change the directory to /nsconfig/loginschema, which is one directory up from where you downloaded the file.
    8. Upload your modified file.
  2. RADIUS Authentication Server:
    1. Follow the link for instructions to create a RADIUS Server. Only create the Server object. The Policy object will be created later when creating the Authentication Policy Label.
      add authentication radiusAction RADIUSMgmt -serverName -serverPort 1812 -radKey b746744 -encrypted -encryptmethod ENCMTHD_3
  3. On the left, go to System > Authentication > Advanced Policies > Policy Label.
  4. On the right, click Add.
  5. Name the Policy Label MgmtNextFactor or similar.
  6. In the Login Schema field, click Add.

    1. Name the Login Schema MgmtNextFactor or similar.
    2. In the Authentication Schema field, click the pencil icon.
    3. On the left, select the Login Schema .xml file you uploaded earlier.
    4. On the top right, click the blue Select button. Do NOT click Create on the bottom left until you’ve clicked this blue Select button.
    5. The window collapses showing you the Login Schema file that you selected. Now you can click Create.

      add authentication loginSchema MgmtNextFactor -authenticationSchema "/nsconfig/loginschema/MgmtNextFactor.xml"
  7. Back in the Authentication Policy Label screen, notice that you can edit the Login Schema object from here.
  8. Change the Feature Type drop-down to RBA_REQ. If you don’t do this, then you won’t be able to bind this later.
  9. Click Continue.

    add authentication policylabel MgmtNextFactor -type RBA_REQ -loginSchema MgmtNextFactor
  10. In the Policy Label’s Policy Binding field, click Add.

    1. Name the Authentication Policy RADIUSMgmt or similar.
    2. Change the Action Type drop-down to RADIUS.
    3. Select the RADIUS server that you created earlier. Or you can Add one from here.
    4. In the Expression box, enter the word true and then click Create.

      add authentication Policy RADIUSMgmt -rule true -action RADIUSMgmt
  11. Back in the Policy Label Policy Binding screen, click Bind.

    bind authentication policylabel MgmtNextFactor -policyName RADIUSMgmt -priority 100 -gotoPriorityExpression NEXT
  12. The Authentication Policy Label configuration is complete so click Done.
  13. On the left, go to System > Authentication > Advanced Policies > Policy.
  14. On the right, click the Global Bindings button.
  15. You should already have an Advanced Authentication Policy bound globally.
    add authentication ldapAction LDAPS-Corp-Mgmt -serverIP -serverPort 636 -ldapBase "dc=corp,dc=local" -ldapBindDn ctxsvc@corp.local -ldapBindDnPassword 5054fc33f673bf4c5c6 -encrypted -encryptmethod ENCMTHD_3 -ldapLoginName sAMAccountName -groupAttrName memberOf -subAttributeName cn -secType SSL -passwdChange ENABLED
    add authentication Policy LDAPS-Corp-Mgmt -rule true -action LDAPS-Corp-Mgmt
    bind system global LDAPS-Corp-Mgmt -priority 100 -gotoPriorityExpression END
  16. Right-click your existing global binding and click Edit Binding.
  17. In the Next Factor field, click where it says Click to select.
  18. Click the small circle next to your Management Next Factor Policy Label and then click the blue Select button at the top of the page.
  19. Back in the Policy Binding screen, click Bind.

    bind system global LDAPS-Corp-Mgmt -priority 100 -nextFactor RADIUSMgmt -gotoPriorityExpression END
  20. Click Done to close the Global Authentication Policy Binding screen.

CLI Prompt

  1. When you connect to the Citrix ADC CLI prompt, by default, the prompt is just a >.
  2. You can run set cli prompt %u@%h to make it the same as a UNIX prompt. See Citrix Docs for the cli prompt syntax.

Backup and Restore

Citrix Application Delivery Management (ADM) can automatically backup your instances. Or you can do it manually:

  1. Save the configuration.
  2. On the left, expand System, and click Backup and Restore.
  3. On the right, click Backup/Import.
  4. Give the backup file a name.
  5. For Level, select Full, and click Backup.
  6. Once the backup is complete, you can download the file.

For a PowerShell script, see John Billekens Create offline backups of the NetScaler config

To restore:

  1. If you want to restore the system, and if the backup file is not currently on the appliance, click the Backup/Import button.
  2. Change the selection to Import.
  3. Browse Local to the previously downloaded backup file.
  4. Then click Backup. This uploads the file to the appliance and adds it to the list of backup files.
  5. Now you can select the backup, and click Restore.

Next Steps

123 thoughts on “System Configuration – NetScaler 14.1 – Citrix ADC 13”

  1. Hi Carl, We recently upgraded to NS 13.1 and have just become aware that HTTP DOS is deprecated in favour of APPQoE.
    The Citrix documentation leaves a lot to be desired – as usual….
    Do you have any guidance on how we can configure APPQoE to achieve DOS protection? I did some searching but couldnt find any relevant article – apologies if i have missed it!

  2. Hi Carl,

    I tried upgrading my ADC to 14.1 this weekend and when I logged into it, everything was unlicensed (LB, CSG, CS, etc). If I’m reading this
    correctly, we have to move to using ADM (now Console) to do the licensing? Do we have to use Citrix Cloud or is ADM still going to be available on-prem?

    I don’t suppose you’ve got a walk through on that yet? 🙂

      1. Thanks, that was it. I thought it was weird that the same license file was fine through all the 13.x upgrades this year but failed on 14.1.

        Do you know if this flex license system is going to be required in the future?


  3. If I use 10/1 and 10/2 in a channel for data, and port 0/1 for a dedicated management network, should I be worried about lack of redundancy on the management network as there’s only a single port being used?

    1. You can move the NSIP to a VLAN that is on a Port Channel and disconnect 0/1.

      HA Heartbeats go out all interfaces, not just 0/1.

  4. Hi Carl, we want to publish the management server via Citrix ADC but because the traffic to the management server is routed (static) over de management IP we can’t.

    Any idea how to force this single virtual server to route ICA traffic via de SNIP and overrule the static route?

      1. Hi Carl, thanks for your reply. If I create a net_profile to specify the SNIP address as source it does not overwrite the /32 route that is present to route to the management server. Sounds logic. As the default route is pointing to the internet. I guess the only thing we can do is enable management on the SNIP. There is a firewall behind it anyway.

  5. Hi Carl,

    Question, is it possible to configure HA and synchronization heartbeat not in NSIP?

    We have a customer that has an HA pair but they want to configure HA pair only via data port where SNIP resides. Also they want that when the time management network down still the the status of HA is normal and the access to applications still working.

    For short they only want the management of Netscaler ADC to work as for management purposes only, so in case the management switches or network down still the ADC serves its purpose to users.

    Thank you,

    1. Is it ok to use the virtual server (load balanced LDAPS) for DNS (SNIP) or should I put my two domain controllers separately? I’m not sure if some part of the ADC uses the management IP address for DNS lookup or it all goes through the SNIP. This has been one interesting learning experience! I’ve never touched a NS before but it sure does make my head hurt 🙂 Thanks for all you do! I have 6 days left on my license (out of 30) and I hope I can make it.

  6. Hi Carl,
    after the upgrade to the NS14.1-8.50 firmware it seems that the floating IP management part for the SSL part no longer works.
    In fact, the part relating to the mgmt service is lost.
    For example:
    > show service -summary
    ————————————————– ——————————————-
    Name State IP Addr Port Protocol MaxClients MaxReqs
    ————————————————– ——————————————-
    1 DC01…OCAL UP 53 DNS 0 0
    2 DC02…OCAL UP 53 DNS 0 0
    3 mgmt-SSH UP 22 TCP 256 0
    If I try to recreate the mgmt service, as per your example, I get the following error:
    > add service mgmt HTTP 80
    ERROR: Resource already exists
    and obviously then I can’t bind the service with the lb mgmt-SSL virtual server and consequently the floating IP for the management GUI over HTTPS doesn’t work.
    In the configuration I don’t find any reference to services that use on port 80 except in the internal services (nshttpd-gui-
    If I connect with this service to the mgmt-SSL lb the floating point seems to work because it shows me the management page er HTTS, but even if I use the correct credentials it DOES NOT allow me to authenticate…
    Do you know how to resolve or other workaround?
    Thank you very much!
    Best regrds,

  7. Hi Carl,
    Can you configure a ‘Floating Management IP’ without the dedicated mgmt subnet in version 14.1?
    I had it working on older versions but keep getting ‘Resource already exists’ when creating the load balancing service as it clashes with Internal Services.

  8. Hi Carl,

    Followed your steps which were great! when i create the first citrix gateway, the state shows as down. netscaler has same routes as the old pair (currently still active) and has the same firewall rules for the new gateway. the netscaler can ping out externally and hit all required internal IPs. i can see that the “web interface” shows as disabled in the licensing features but it is enabled on the old ones – can this be the issue and is there a guide to enable this as i dont see an option in features in the gui for this or on command line?

    Thanks in advance

    1. Web Interface is a really old feature that should not be used.

      Down on Gateway usually means that a certificate is not bound to the Gateway. Or do you mean the STAs are down?

      1. No problem, noted.
        The Gateway had the cert assigned (although the chain was incomplete) i have then recreated it using the gateway wizard and it now works (with the cert chain still incomplete) so not sure where i had gone wrong!

    1. If your NSVLAN is on a trunk port and if your switch requires the VLAN to be tagged, then set tagged to YES.

      NSVLAN restricts the NSIP to a VLAN, which is restricted to an interface channel. I think HA heartbeat still uses all interfaces unless you disable HA Heartbeat on those interfaces. HA Sync is on the NSIP interface/VLAN.

      1. Thank you Carl.

        I have a new pair of MPX 5901,
        for simplicity, NSIP, SNIP, VIP will the same subnet, i will use one interface in netscaler, it is ok?
        Could you provide more best practices design (one arm, two arm) for us, thank you again.

        1. You should do a port channel for interface redundancy. Or you can connect each node in the pair to different switches.

  9. Hello,
    How do I make a connection using the DOMAIN user through the secondary NS
    For some reason it doesn’t work only through the secondary.
    Through the main NS everything is fine

    1. Are you asking about management? Are you load balancing LDAP? Do your NetScalers have a dedicated management interface? If so, did you configure PBRs?

      1. Hi
        Yes it is for managment
        I habe dedicated managment intreface
        No it is no load balnce.
        When I make on the ldap server test connection on the secendary it is fail

  10. Facing issues with HA Synch but HA failover works fine without user interruption.

    Have 2 HA pairs and in both pairs , High Availability Synch fails, “unable to connect to primary, please check the network connectivity from secondary to Primary.” Upgraded Firmware NS13.122.47nc a month before but did not notice the synch issue and not sure its related to firmware upgrade . TLS1.2 is enabled in the SSL profile applied to all Internal services. Any thoughts

  11. Hi Carl,

    I’m sure i’ve seen this somewhere but i can’t find it anywhere.
    I have 2x HA pairs of VPX 13.0, the LDAPS virtual server is configured with an internal IP (ie On one of the HA pairs i can use my domain account to log into the secondary node but on the other HA pair i can’t, it just comes back with the following ‘Invalid username or password’.

    They “should” be configured identically but i can’t figure it out.


  12. We are presently running, can I directly perform inplace upgrade unto build-13.1-37.38_nc_64?
    We are only using if for StoreFront Load balancing.

    I thought I read somewhere once that a migration would be needed to move unto NS13.1.x, but could no longer trace it.


    1. Yes, you can skip minor builds while upgrading.

      13.1 still has all the Classic policies that Citrix Gateway supported in 13.0.

  13. Hi Carl,

    I am working on migrating from two physical MPX appliances to a pair of VPX’s and wanted your take on something. I can’t find documentation on how to deploy VPX’s with 10G interfaces. We are running on a Dell VxRail, of which has all 10G physical interfaces and all of our VM’s are using the VMXNET3 NIC and show a Speed of 10G. That is not the case with our VPX’s, as they are showing only 1G.

    Is there a configuration requirement needed for 10G? Our ESXi environment is vSphere 7.0

    1. Are you able to exceed 1 GB on single NIC in VPX? NIC speed shown in guest doesn’t always match the host uplink. Higher speeds might need SR-IOV.

    2. Hi Taylor, did you find an answer to this question ? We are currently having the same interrogation over here. Our vmxnet3 nics are recognized as 1G instead of 10G. We know that we could use SR-IOV to achieve that, but vmxnet3 should be able to do 10G.

      Please let us know !

  14. Hello Carl,
    I’ve been searching the internet on how to install ADC 13.0 on a VirtualBox VM for lab testing only. I have not really found anything that really help me. Only that it can be done. I know you are the expert. Is this possible? If so, can you point me to something I can follow so I can get this done.

    Thanks in advance if you can help.

  15. I have always appreciated your wonderful instructions of Citrix.
    I have found a weird thing in ADC VPX regarding the CPU 100% on VMware.
    I have installed v13.1 33.47 on VMware 7.0.3
    When I leave it as default in CPU Yield, CPU consumption alerts came up in Vsphere.
    When I change it to Yes in CPU Yield, CPU consumption level turns to low.
    But ping response time is slower than before so I did ping to local interface and it’s slow as well. without CPU Yield ‘YES’ ping results are less than 1ms but with ‘YES’ it is 2~6ms. Ping to gateway is slow as well.
    I am curious if it is known issue.

  16. dear Carl,
    May i ask a stupid question? The nspepi tool creates a new_ns.conf file with updated configuration. This seems to be fine, but how do i get this back into the running configuration?

    The explanation in Github “Move the configuration into production as per your normal configuration upgrade processes”… doesn’t help me much.

    I tried copying it to /nsconfig/ns.conf and rebooting the ADC (secondary) without saving the configuration. but after the reboot, it gots the ‘old’ config back from the primary. I guess there must be an obvious way that i overlooked…

    1. For HA pairs, try updating and replacing the configs on both nodes separately but at the same time. Shut down both. Power on one. Then power on the other.

      Another option is to wipe the config on one, update the config on the other, and then rebuild the pair.

      1. Thanks for the fast response. Before shutting down both ADCs, which would make the whole system unavailable, i first tried another idea (with the snapshots ready to revert to, in case it would fail ;).
        I disabled synchronization on both sides, updated secondary, failover, updated other one, enabled synchronization, force synchronization on both sides.
        It seems to work fine, did you see any danger in this approach?

          1. I ended up doing the same ‘shut down and restart both together’ trick to deal with the same issue Roel had. It works well but it does require an outage.

            The stumbling point for updating configuration like this seems to be the automatic re-enabling of HA sync on reboot. It would be useful in some cases to be able to reboot the secondary while being able to guarantee that HA sync will not restart until I’m ready for it. For software upgrades this isn’t an issue since different versions typically won’t sync. For configuration changes from a prepared ns.conf file it is a bit of a pain.

            Is there something I’m missing that would make this process easier?

  17. Just FYI if anyone runs into HA errors on version 13

    HA Sync Error after Upgrade : “Unable to connect to Primary. Please check the network connectivity from secondary to Primary”

    Enable TLS1.2 on internal services for 3008 port and RPC secure communication will be successful.

  18. HI Carl

    Not sure if this is the right forum.

    We are experiencing intermittent nslog files not getting zipped, after a firmware upgrade, was hoping that you can provide some advice on what we need to look for.

    All our ADC are in Azure, 2 ADC got impacted with this behavior out of HA pairs we have in DR/Prod

    So far we see this happening @5am or @6am. When this first occured couple of nslog file was not getting zipped and caused an outage – we demoted primary and remove this from HA

    FW Updated to NetScaler NS13.0: Build


  19. Hi Carl, amazing work as always. I’ve two questions if you don’t mind. I’ve gone with the setup of a vpx ha pair with the nsips in a mgmt network and the snip in a dmz network. I’m trying to keep the nsip to mgmt only buy using the pbr rules above.
    1. I’ve found the ldap service group will only go through the snip if i create a pbr deny rule for ldaps similiar to your pbr rule nsip-dns, is that expected. Will all monitors try and use the nsip?
    2. In system>authentication>basic poilices>ldap?server I can’t get the authentication ldap server to connect to the ldaps virtual server. Using the ip of the ldaps vip i get, ‘Either ‘’ is not an LDAP server or port ‘636’ is not a LDAP port.’ Using the DNS name is get ‘Either ‘ldap.domain.local’ is not an LDAP server or port ‘636’ is not a LDAP port’. I’ve tried with a cert containing the name about and both domain controllers in the SAN and also a wildcard cert. Any ideas?

    1. Only perl monitors, like the LDAP monitor, use NSIP. You can instead do a generic TCP monitor and that will use the SNIP.

      ADC LDAP uses NSIP as source to reach the VIP. Anything blocking that route? You can run host <Your_LDAP_VIP> to see the source and the traffic.

  20. Hi Carl.

    After a few months with the VPX’s set to HA, now my client wants to use specific certificates on each node for hostname matching.

    I have been checking on the internet and it seems that it is not an easy task thinking about the synchronization.

    So I would like to ask you what should be a better option:
    1.- Create a folder called not_sync_cert (for example) and copy the key and certificate and then install and bind the services.
    2.- import the certificates and simply install them and then link to the services. (this is where I’m worried about timing)
    3.- Create a wildcard certificate to share the service.

    Could you guide me on this issue?


    1. I usually create a cert with Subject Alternative Names for each NSIP and bind it to the internal services.

  21. Carl, I’m seeing a strange issue with my Always On VPN clients. ADC, After the users login to Secure Access Client, DNS and Default Gateway point to a random IP in the Internet IPs Pool vs what is expected which would be This causes DNS to fail for clients. Any thoughts?

    1. Yes. Always SNIP.

      If you don’t deny DNS in your PBRs, then PBRs for NSIP interfere with how ADC resolves DNS names. ADC uses NSIP to talk to, which then uses SNIP to talk to DNS. PBR interferes with the first part of the conversation.

        1. DNS does an internal loopback from NSIP to or something like that. I needed DNS to bypass PBR. I have not tried the PBR in this blog.

          You can do “ port 53” to see the DNS traffic.

  22. I’m running two sites with an VPX and ADC [with a DMZ and Internal interface. If I want to segregate the traffic on a single device is admin partitions the current best practice?

    I also am running a management interface without a SNIP and only the NSIP with the default route on the DMZ port and I don’t seem to lose connection to the NSIP? Havn’t done the entire PRB bit for setup and somehow am getting away with it? Does that make sense?

    1. Sounds like you have “MAC based forwarding” enabled. We had that set on our MPX devices but I made sure to use the proper PBR config when we migrated to VPX.

    2. Admin Partitions are Citrix’s preferred way of creating separate routing tables on a single appliance. However, not everything works.

      MBF handles reply traffic. PBR handles routing of traffic initiated by the NSIP (e.g., syslog, snmp, etc.). If ADC only has a route through the a SNIP network then ADC might use the SNIP instead. You can do a to see what source IP ADC is using.

  23. Hello Carl,

    I was going through your dedicated Management interface where you introduce PBR on the NSIP.

    I’m going to have an ADC sit in a DMZ, but was going to have the NSIP sit in the trusted network. The ADC would have two interfaces, one in the trusted network where the NSIP resides, and one in the DMZ network. I would tag that DMZ network with a VLAN and associate that VLAN with a Traffic Domain. The VIP and SNIP’s would all be in the TD. The idea is that user traffic would pass through the DMZ – the SNIP would be involved with all backend traffic (including monitors). Would that accomplish something similar to your PBR methodology? This way, we can fully manage the ADC (SNMP, HTTPS access, LDAP management auth) without extra inbound firewall rules.


    1. nevermind… looks like Traffic Domains are going to be deprecated (fired up a 13.1 box). Admin Partitions it is!

  24. Hi Carl,

    I have configured 2fa same way you did but some how not receiving the Mfa password .

    After Ldap authentication I am going to Mfa page but not getting the code .

    Can you please suggest.


  25. Thank you Carl for all this great and detailed information. I’m working on deploying new VPX’s to replace our current MPX’s. The planning has been going good so far. One thing we did not have for our MPX’s is a virtual server for floating management via HTTPS and SSH. On our new VPX’s, I set up both.

    However, I’m noticing that the active node always displays this error every 10 seconds on the console:
    ” sshd: error: Fssh_key_exchange_identification: Connection closed by remote host”

    When I delete the management SSH virtual server and service, the error stops. Do you think more configuration is needed if we want to use a management SSH virtual server? Thanks!

    1. It’s the monitor on the SSH service object that’s causing the error messages. Not sure how to get around this since you can’t unbind default monitors.

      1. I was able to bind the “ping” monitor to the service which overwrote the default “tcp-default” monitor.

  26. Hi Carl,

    Something would like to seek your advise;
    I am using responder policy associated with Audit Message Action to log the traffic activities(for content switch, virtual server, global…etc). However, i realized that if the audit message action’s expression has no value return(ie. CLIENT.TCP.LB_VSERVER.NAME), the entire me message will become “blank”. I am wondering how can i get rid of this?

    Say, i have following expression;
    “dropped_connection ” + CLIENT.IP.SRC + “:” + CLIENT.TCP.SRCPORT + ” ” + CLIENT.TCP.LB_VSERVER.NAME + ” (” + CLIENT.IP.SRC.LOCATION + “)”

    If there is no value for “CLIENT.TCP.LB_VSERVER.NAME”, it won’t display the other but the entire message would be blank.


  27. Hi Carl, is there any benefit of using multiple subnets and VLANs for different load balanced services vs if using single network and single VLAN on which you have a SNIP and NSIP and same SNIP is talking to different backend servers. Our Cybersecurity team is purposing to use different subnet, VLAN and SNIP of each service we load balance through ADC. Thanks.

    1. It depends on where you want to control access. If you use one SNIP for everything, then the ADC administrator is responsible for not mis-configuring the ADC to allow access to where it shouldn’t. If you use different SNIPs for different services, then the network firewall can control access.

      One option for configuring multiple SNIPs is Net Profiles.

  28. Carl – thanks so much for all your detailed explanation. I had one question about the new ISSU HA migration feature. Looking through Citrix’s guide, they make it seem like the HA SYNC VLAN config is a prerequisite in order to use the new migration feature: Maybe I’m misinterpreting Citrix’s guidance, but I don’t see the “Sync VLAN” configured in your HA setup. How do you interpret their language on this?

    1. I’m not sure since I haven’t done a 13.0 ISSU upgrade yet since all of my customers are on 12.1. I added a note about the Sync VLAN just in case it’s required.

  29. Citrix ADC HA pair in aws in different zone not working properly the eip migrates to secondary node when failover but when we try to fail over again the EIP doesn’t go back to the primary noe

  30. Upgrading from 12 to 13 broke my multi-domain gateway configuration (2 domains, 2 LDAP 2 Authentication Policies, 2 Session Policies).The session and LDAP policies don’t seem to match post upgrade. I have had a case open with Citrix for a few months on this one Any ideas are greatly appreciated.

  31. I’m trying to update an ADC from 12.1 55.18 to 12.1 57.18. When I run the update in the GUI, it doesn’t work. In running it through a cli session, I see and error “/usr/bin/perl^M: bad interpreter: No such file or directory” and it fails. This system was originally created from an iso image, so do I just need to install a perl package?

    1. From an ISO image? Is this a physical machine with Linux OS? In that case you should be running the BLX image. Or is this a virtual machine? If so, deploy a VPX. In either case, you can move your configs to the new appliances.

      1. I get the same error when trying to run the check_invalid_config command. Tried in both 13.0 and 13.1 clean install VPX. “-bash: ./check_invalid_config: /usr/bin/perl^M: bad interpreter: No such file or directory”

  32. Hi Carl,

    Regarding two factor Management Authentication – do you know if it’s possible to use a combination of LDAP + Local, rather than the second factor being RADIUS?


  33. Hi Carl
    Have you ran into the issue with STAs after upgrade to ver 13? 12.1 was OK but since 13 STAs are DOWN, unless using as IP. DNS works fine. Tried re-adding etc – no go

  34. Hi Carl, any thoughts on what performance hit we might see if we do enable the cpuyield vpxparam setting? I’d like to stop VMware reporting 100%CPU for our NetScaler VPX 1000 machines, but not at the expense of affecting users. Citrix have obviously defaulted to “don’t yield” for a reason, just wondered what you thought? Thanks

    1. 100% CPU is Citrix’s method of reserving CPU. You can enable Yield if you configure CPU reservation in your hypervisor.

  35. Sir,
    I have query, My NSIP is on different subnet & SNIP,VIP & LB IPs are on different Subnet & VLAN.
    Could you please let me know what Network routing I need to do in this scenario.
    Traffic is allowed from firewall even though nothing is working.

  36. Carl, I have a question that I wonder you’d have the answer for.

    I’m using the ADC VPX 12.x Freemium version as a load balancer in front of Horizon Connection Servers. This works just fine. Previous versions required me to go and get a free license, but it looks like the Freemium version has a license built in and there’s nothing else for me to do. In the last month or so, both appliances, one in production and one in DR, have totally lost their config. All that’s left are the base IP addresses. The last time this happened, I know that I had saved the config to the appliance, but it was nowhere to be found. So, I reconfigured it and made sure I had a back up on the appliance and also I downloaded it to my local drive. I then went and did the same thing to my DR one.

    Today, the DR one lost its config. I found the saved config on the appliance and restored it, but nothing came back. I then got the one I’d saved locally and restored it and got the same thing. So, I reconfigure it again and this time created a clone copy of the appliance.

    However, do you have any idea why this would be happening? Is there some gotcha with the free license that comes built into the appliance? If I look at the license item in the config menu, none is listed, but the summary says i have the free express license and that I am licensed for load balancing.

    Also, if I have successfully save off the config, and the restore seems to complete without error, why does it not restore?

      1. NS12.1 build When I look under System and licenses I see license type of standard, model ID 20 and licensing mode of Express. Load balancing has a green check mark. Label at the top of the console says Citrix ADC VPX Freemium. thanx…

          1. I didn’t see anything that looked like a crash. The crash directory had one file called “g” and the core had 2; “1” and “bounds”. The thing that seemed weird to me, which made me ask about the licensing for the Freemium version was the both machines seemed to die around 1 year after I’d installed it, but it was not exactly 1 year.

          2. The Express license used to expire after a year. Maybe there’s a bug in the code.

          3. Should I perhaps upgrade to a newer version? Are they still producing the Freemium versions? However, does any of that explain why I wouldn’t be able to restore from the backup? As I said at the top, the backup seems to go OK and it seems to restore without error, but none of the config is actually restored.

          4. So, perhaps I’m missing something as well. I just downloaded and installed it in my lab. I attempted to restore the file that I saved from the 12.x appliance and that didn’t work. So, I thought that perhaps it was a version difference, So I created a virtual server under the load balancing section and then I did a full backup. Then I deleted the virtual server and restored from the backup; nothing. This seems so simple, but I’m obviously missing something.

          5. What process are you using to restore? If you’re doing the built-in restore function, then you need to reboot after restoring. Make sure you don’t click the Save button when rebooting.

          6. So, in the backup restore, I think I know what the issue was. I’ve tested this in my lab. My guess is that when I was building the VPX appliances, when I finished I neglected to hit the icon for save running config. If that’s true, then, from my understanding, it would reboot into a blank machine and the backup would not back up my config. I’ve tested this by making sure that I’ve saved the running config first and then doing the back up and that seems to restore just fine. For my production attempts, I had tried the restore from the GUI, but again, I’m suspecting I didn’t have anything backed up. In my test, I’ve done the backup from the GUI, but then restored from the CLI.

          7. Carl, a different question. We’re looking to purchase a license from Citrix for our ADC VPX appliances – at least the one we have at the DR site. Here’s my config. I have a VMWare UAG as the first hop, which directs to the ADC VPX appliance which is being used strictly as a load balancer and the load balancer points to the two connection servers. First question: when a user makes a connection from their computer to get a Horizon desktop, once that connection is made is the VPX still involved in the actual data throughput or does it step out of the way so the desktop would talk thru the gateway to the user and the VPX really isn’t used anymore? I’m trying to figure out if the VPX 10 license is good enough or do I need more throughput. And in a similar vein, from what I’ve read it appears that the freemium version allows 250 simultaneous SSL connections. While I “might” have more than that initially coming thru at the same time in a DR scenario, once everyone was connected, I’d only have a handful ever trying to access a new desktop at any one time. So, again, is the VPX 10 standard license good enough or should I look at something else? The guy I was talking to from our VAR seems to think that the VPX steps out of the way once the connection is made and the VPX 10 or perhaps the VPX 25 standard license would be good enough for this, but I’l like a second opinion. Thanx…Jon

          8. UAG sends HTTP traffic to Connection Servers through the load balancing VIP. Once the user launches a session, the connection is now PCoIP or Blast. UAG sends PCoIP or Blast directly to the Horizon Agent, not through a load balancer.

  37. Carl, I run several VMs and containers at home and am looking for a remote access solution. I’m just 1 guy so it is not worth a lot of $, really looking for freemium or opensource solutions. I like the netscaler because ive used those at work before. Do you know if the freemium license will work for 1 user for a remote sslvpn? Or is there some other direction you might recommend?

    1. Freemium does not include Citrix Gateway.

      If Windows, you can install Routing and Remote Access and using VPN to connect.

  38. Hi Carl,

    I have downloaded Netscaler ADC 13.0-47.22 freemium edition with my citrix account(Not a corporate account ),How can i download 30 days platinum license file from citrix site.

    1. Unfortunately you will have to contact a Citrix sales rep to get an eval license. Partners no longer have access.

  39. Hi Carl, I just deploy an ADC VPX 13 on VMWARE. I notice the Guest OS is Oracle Solaris 10 (64-bit). Is this correct or do I need to change it to FreeBSD? So far the ADC is running fine without any issue,

  40. Regarding NTP configuration in initial setup with GUI in v13.0 You will se an error message stating that the “file does not exits”. You will not be able to save host name, dns server, timezone or ntp server. To resolve this problem(bug), you need to ssh in to the shell and execute the command: cp /etc/ntp.conf /nsconfig/ntp.conf. Now you can save the config of hostname, dns ip address, timezone and ntp server:-)

  41. Hi Carl, thanks for your detailed guides, they have been invaluable in setting up our new environment! Could you tell me which Netscaler licence would be required to provide users with a web interface via NS to our storefront? I have been told (and purchased) Citrix Gateway Advanced VPX is correct but when I load the licence Web Interface is not listed as a licenced option?

      1. No I just want to proxy HTTP to the StoreFront, I’m finding my Citrix terminology is quite out of date as I buiilt our last farm back in 2012 based on SG, WebInterface and XA6.5! I’ll look at the page you suggest, thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *