NetScaler

Deprecated features and functionalities

Some of the NetScaler functionalities are deprecated in 12.0 and in its subsequent releases. Citrix recommends that you do not use these features through the NetScaler command interface, NetScaler GUI, or NITRO automation. However, to ease the transition to new alternatives, the deprecated features are usable for a limited time and will be removed in future releases. Citrix recommends you to use the below alternatives for the following set of deprecated functionalities.

Deprecated features and Its alternatives in NetScaler 12.0

A list of NetScaler features and functionalities are deprecated. For complete information, You can refer to Deprecated List pdf.

Deprecated classic policy-based features and its alternatives

Classic policy-based features and functionalities are deprecated from NetScaler 12.0 build 56.20 onwards. As an alternative, Citrix strongly recommends you to use the Advanced policy infrastructure. As part of this effort, when you upgrade your appliance to NetScaler 12.0 build 56.20 or later, you must replace the Classic policy-based features and functionalities to its corresponding non-deprecated features and functionalities. Also, you must convert Classic policies and their expressions to Advanced policies and expressions. Also, all new Citrix ADC features support only Advanced policy infrastucture.

You can migration your Classic policies and expressions either manually or by using the nspepi tool. The tool helps you to auto-convert Classic policies and their expressions (in the Citrix ADC commands, expressions, and configurations) to Advanced policy infrastructure.

For deprecated features and their alternatives, see Deprecated List pdf.

Using NSPEPI conversion tool

You can use the nspepi tool to convert commands, expressions, and configurations. For more information, see Converting Expressions by Using NSPEPI Tool topic. Here is a list of conversion from Classic expressions to Advanced expressions.

  • ns_true -> true
  • ns_false -> false
  • REQ.HTTP -> HTTP.REQ
  • RES.HTTP -> HTTP.RES
  • HEADER “foo” -> HEADER(“foo”)
  • CONTAINS ”bar” -> .CONTAINS(“bar”) [Note use of “.”.]
  • REQ.IP -> CLIENT.IP
  • RES.IP -> SERVER.IP
  • SOURCEIP -> SRC
  • DESTIP -> DST
  • REQ.TCP -> CLIENT.TCP
  • RES.TCP -> SERVER.TCP
  • SOURCEPORT -> SRCPORT
  • DESTPORT -> DSTPORT
  • STATUSCODE -> STATUS
  • REQ.SSL.CLIENT.CERT -> CLIENT.SSL.CLIENT_CERT

AppQoE Use Cases

When using AppQoE as an alternative for SureConnect feature, you can refer to the following use case configurations.

Use Case 1: To limit simultaneous download of huge files and display loading screen:

add appqoe action NS_RESP -respondWith NS -maxConn 50

add appqoe policy POL_DWN_PKG -rule “HTTP.REQ.URL.CONTAINS(\“tar.gz\”)” -action NS_RESP

bind lb vserver v1 -policyName POL_DWN_PKG -priority 8

Use Case 2: To limit simultaneous download of huge files and display loading screen with alternate content:

add appqoe action ACS_RESP -respondWith ACS -altContentsvcName s2 -altContentPath /netscaler/alt.html -maxConn 50

add appqoe policy POL_DWN_ACS -rule “HTTP.REQ.URL.CONTAINS(\“tar.gz\”)” -action ACS_RESP

bind lb vserver v1 -policyName POL_DWN_ACS -priority 9

Use Case 3: Custom loading screen:

import appqoCe customResp [http://<location>]|[local:<file>] simple_custom_resp

add appqoe action CUST_RESP -respondWith NS simple_custom_resp -maxConn 50

add appqoe policy POL_CRESP -rule “HTTP.REQ.URL.CONTAINS(\“tar.gz\”)” -action CUST_RESP

bind lb vserver v1 -policyName POL_CRESP -priority 10

Deprecated features and functionalities