Supported NetScaler configurations

Depending on the NetScaler configuration and the partition in which the configuration is performed, NetScaler configurations can be categorized into three types of configurations as given below.

Note

• Admin partitions cannot be set up on a NetScaler cluster. This means that a NetScaler cluster cannot be partitioned.
• Admin partitions cannot be set up on a NetScaler MPX-FIPS appliance.
• Case 3 lists the NetScaler features that are not supported in admin partitions.

Case 1 (global configurations)

Configurations that can be performed ONLY in the default partition and which are available or impact all the admin partitions.

• Updates to built-in entities for monitors, TCP profiles, HTTP profiles, and so on.
• Updates to global parameters for syslog, nslog, weblog, content switching, IPSEC, SIP, DHCP, Surge protection, TCP buffering, and system collection.
• High availability (HA) configurations
• Interface and VLAN changes
• User configurations

Case 2 (partition-specific configurations)

Configurations that can be performed independently in default and admin partitions. These configurations are applicable only to the partition in which they are performed.

• Getting traffic level statistics for a partition.
• Partition admin can update IP bindings for VLAN which is bound to that partition. But cannot update the interface bindings.
• Clearing NetScaler configurations.
• Feature-specific parameters for the following features: AppFlow, AppQoE, HTTP compression, DNS, TCP, HTTP, encryption, responder, rewrite, and SSL.
• Feature-specific configurations such as virtual servers, services, monitors, and so on.

Case 3

Configurations that cannot be performed on admin partitions. These features can be configured in the default partition, but there is no impact on admin partitions.

Note

Configurations that are supported on admin partitions for a particular release are marked as Yes.