[What are the choices for using BLX vs VPX? Why would you use one vs another?]

One should choose BLX if they have custom baremetal server , where they want to have overall control of the system and may need to install other linux based applications.

One should choose a VPX if they want a ready made appliance(VM), which they want to install over a hypervisor, and want to leave the overall control of the appliance to NetScaler.

[When a machine is converted into NetScaler BLX, is management traffic to SSH affected by the license limitations? Is there a way to get that traffic isolated, so that it is not affected?]

Yes, there will be license limitations for Management Traffic of BLX.

There is no way to isolate traffic as of now.

This is an interesting use case & we will surely brainstorm to support this.

[NetScaler BLX Coexistence is an interesting use case - Are there are gotchas/requirements e.g. Port conflicts or resource conflicts with all CPU offloaded to NetScaler?]

Yes, there are few gotchas which needs to be considered.

Underlying Host shouldn't use Netscaler Ports ( like 9022, 9080, 9443, etc. ) otherwise it will result in conflict.

[Are there any plans to support BLX on ARM64? And what about ARM64 for CPX, as it is closely related to BLX.]

Yes, we do have plans to support BLX on ARM64 in future.

If support is there for BLX, ARM64 will work for CPX too.

[Can we use a Linux distribution other than CentOS to install NetScaler BLX?]

Yes, we support all popular Linux Distribution in BLX.

Below Link gives details of support versions of various distros -

https://docs.citrix.com/en-us/citrix-adc-blx/current-release/deploy-blx.html#before-you-begin

[Does NetScaler BLX supports pooled capacity licensing ? Do you have any license limitation for BLX?]

Yes, BLX supports Pooled Licensing.

There is no License limitation for BLX.

[Can you cluster a NetScaler BLX?]

Yes, we do support Cluster (both L2& L3 ) in BLX.

[Is there any difference when it comes to ns.conf or APIs between VPX, MPX, BLX and CPX?]

No, there is no difference.

It is exactly same ns.conf which is used in all Netscaler form factors.

[Does BLX have GUI support as VPX & MPX?]

Yes GUI-Support is there on BLX which is exactly same as VPX & MPX.

[How does BLX handle the linux firewall/iptables or the linux firewall needs to be disabled ?]

Linux Firewall need not be disabled to run BLX.

BLX open some ports and have ip table rules which gets activated during BLX bring up.

Below Link helps to run BLX with SE-linux enabled -

https://community.netscaler.com/s/question/0D58b0000AYZo5LCQT/it-is-possible-to-run-netscaler-adc-blx-when-the-host-linux-selinux-is-configured-to-be-enforcing-

[Could BLX (in the future ) have a deployment mode that could offer 'instances' a bit like SDX? To offer BLX different instances within a Linux partition of some sort?]

Yes, we already have a POC for this solution , but there is no active development activity at the moment.

[Can BLX be deployed on a Virtual machine? If yes, how it is different from Bare-metal deployment?]

Yes, BLX can be deployed on an Linux based Virtual Machine.

There is no difference in BLX Bring up, Start and Functioning.

[Do you have any plans on adding BLX packages to the platform package managers? (Like apt, yum)]

No, we do not have plans to add BLX packages in public repositories ( like apt, yum) in short-term.

[Does NetScaler BLX support SSL offload acceleration? Can cards be added to speed that up?]

As of now, BLX supports Software based SSL offload acceleration.

Exploration is going on to support Hardware based SSL acceleration, we hope to deliver it soon in future releases.

[What is the limitation on total number of NICs that can be dedicated to NetScaler BLX? Does the limitation vary with DPDK and NON-DPDK capable NICs?]

Yes, there is a limitation on number of Nic Interfaces / Ports that can be dedicated to Netscaler BLX.

As of now we can dedicate upto 8 Interfaces on both DPDK & Non-DPDK based BLX.

In future releases we hope to increase the number of Interfaces that can be dedicated to BLX.