FAQs
What is NetScaler BLX?
NetScaler BLX is a bare metal software version of NetScaler that runs as a native application on the Linux host. For more information, see About NetScaler BLX.
Why is there a need for NetScaler BLX?
NetScaler BLX is a bare metal version of NetScaler, which provides simplicity with no virtual machine overhead for better performance. Also, you can run NetScaler BLX on your preferred server hardware. For more information, see Why NetScaler BLX?
What is the difference between NetScaler BLX, CPX, and VPX?
NetScaler BLX, CPX, and VPX are software form factors of NetScaler.
NetScaler VPX™ is a virtual appliance and must run on a hypervisor installed on the server.
NetScaler CPX is a containerized version of NetScaler, which must run in a container.
NetScaler BLX is a software package that runs natively on Linux systems.
When to use NetScaler BLX?
NetScaler VPX, CPX, and NetScaler BLX represent the most comprehensive, software-centric ADC lineup in the industry for supporting the transition to hybrid multi-cloud. The following table gives guidance on the differences and use cases.
| Product | Use Cases | Characteristics |
|---|---|---|
| NetScaler VPX (runs on a hypervisor) | Virtualization of hardware infrastructure, consolidation of workloads over common infrastructure | Hardware and OS agnostic, full isolation, and support for multitenancy |
| NetScaler CPX (runs in a container) | DevOps, micro-services, automated staging, testing, and deployment, East-West traffic | Lightweight, small footprint, API gateway functions, micro-service centric, authentication |
| NetScaler BLX (runs on bare metal servers) | High traffic load, mission-critical applications, latency-sensitive workload, North-South traffic | Native linux software package and no VM overhead |
What difference does the absence of a hypervisor or container make?
With no hypervisor translation layer or container, NetScaler BLX software has more control of the underlying hardware, resulting in better performance. Also, there are no additional costs for hypervisor software.
Can I run NetScaler BLX on any server hardware?
Yes, you can run NetScaler BLX on any server hardware. However, for higher performance, we recommend using DPDK-compatible NICs that are supported by NetScaler BLX. For more information about hardware requirements, see Hardware requirements of Linux host.
How can I deploy NetScaler BLX on a Linux server?
You can deploy NetScaler BLX on any Linux server that supports one of the following package distribution.
-
.rpm(RPM-based package) -
.deb(Debian-based package)
For information about deploying NetScaler BLX, see Deploy NetScaler BLX.
Can I automate the NetScaler BLX software deployment?
Yes, you can use any software deployment tool that supports
.rpm or .deb package to deploy NetScaler BLX.
For example, use can use Terraform to deploy NetScaler BLX. For more information, see NetScaler BLX Deployment using Terraform.
If NetScaler BLX is installed on a server with Linux OS, can I install other standard Linux packages or applications on the same server?
Yes, other standard Linux packages or applications can run alongside NetScaler BLX.
How can I buy a NetScaler BLX License?
By default, NetScaler BLX comes with an express license. You can try NetScaler BLX without any cost.
After you're satisfied with the product, you can upgrade to a subscription-based local license or a NetScaler® pooled capacity license.
For more information about NetScaler BLX licensing, see NetScaler BLX licensing.
Can I use the current NetScaler VPX license for NetScaler BLX?
Yes, you can use the current VPX license for NetScaler BLX. For more information, see NetScaler BLX licensing.
Can I deploy NetScaler BLX in one-arm and two-arm modes?
Yes, you can deploy NetScaler BLX in either one-arm or two-arm mode. For more information, see Physical deployment modes.
Which network stack does NetScaler BLX use?
NetScaler BLX uses its own network stack. For more information about NetScaler BLX architecture, see General architecture.
Does NetScaler BLX support high availability?
High availability is supported for NetScaler BLX. For more information about high availability setup, see High Availability.
Can I set up a high availability pair between NetScaler BLX and NetScaler VPX or CPX?
No, you cannot set up a high availability pair between NetScaler BLX and VPX or CPX.
Can I run NetScaler BLX on a virtualized Linux machine with DPDK?
Yes, you can run NetScaler BLX on a virtualized Linux machine under the following scenarios:
-
BLX can be leveraged when there is a need to run NetScaler® on a customized host image, as required by the customer.
-
BLX is also a recommended virtual machine solution in environments where NetScaler VPX is not officially supported.
Can I run NetScaler BLX on the ARM platform?
No, NetScaler BLX is supported only on Intel or AMD x86-64 (64-bit) Linux platforms.
What is the management IP address of NetScaler BLX?
The NSIP address is the management IP address of NetScaler BLX. It is configured using the
ipaddress parameter in the blx.conf. If you have configured NetScaler BLX managed host without specifying the NSIP address in the ipaddress parameter, the Linux host IP is automatically added as the NSIP address to NetScaler BLX.
Why is the memory usage percentage always high in NetScaler BLX?
The memory usage percentage is determined by comparing the current memory usage of NetScaler BLX to the total memory NetScaler BLX allocates itself from the operating system (OS). NetScaler BLX starts by allocating a minimum necessary memory from the OS for booting and basic operations. Initially, because NetScaler BLX allocates the minimum necessary memory for its operations, the memory consumption percentage is high. Eventually, as the need for more resources grows with the scaling of NetScaler BLX operations, NetScaler BLX incrementally allocates additional memory from the OS and the memory usage is also high, resulting in high memory usage percentage.
Thus, due to NetScaler BLX's dynamic memory allocation strategy, NetScaler BLX typically shows a high memory usage percentage, reflecting its efficient use of resources rather than a lack of available memory.