Quick Start Installation and Configuration

Quick Start Installation and Configuration

Configuration Requirements

Determine the following information for performing the initial configuration.

• NetScaler IP address: The management IP address of the appliance.

• Subnet IP address or Mapped IP address: The IP address used by the appliance to represent the client when communicating with a server.

• Default gateway: The IP address of the router that forwards traffic out of the appliance’s subnet.

• Root password: The root user (nsroot) has full administrative privileges on the appliance. The root password is used to authenticate the root user.

Setting Up Connectivity

Connect the appliance to a management workstation or the network by using the NetScaler configuration utility, the command-line interface (CLI), or the LCD keypad.

Configuration Utility Setup

To set up the appliance by using the configuration utility, you need a management workstation or laptop configured on the same network as the appliance. To run the configuration utility, the Java RunTime Environment (JRE) version 1.4.2_04 or later must be installed on the workstation or laptop.

Note: The Setup Wizard automatically opens upon log on when the appliance is configured with the default IP address, when licenses are not installed on the appliance, and when either the mapped IP address or subnet IP address is not configured.

To configure the NetScaler by using the configuration utility

1. Connect the NetScaler to a management workstation or network.

2. Open a browser and type: http://192.168.100.1 Note: The NetScaler is preconfigured with the IP address 192.168.100.1.

3. In User Name, type nsroot.

4. In Password, type nsroot.

5. In the Setup Wizard, click Next and follow the instructions in the wizard.

6. To confirm that the NetScaler is configured correctly, you can either ping the new NetScaler IP address (NSIP) or use the new NSIP to open the configuration utility in a browser.

CLI Setup

To set up the appliance by using the command-line interface (CLI), connect the serial cable to the console port. Access the command line with a terminal or terminal emulator with the following settings:

• Baud rate: 9600

• Data bits: 8

• Parity: None

• Stop bits: 1

• Flow control: None

Log on to the NetScaler with the following credentials:

User name: nsroot

Password: nsroot

To configure the NetScaler by using the NetScaler command line

At the NetScaler command prompt, type:

• set ns config -ipaddress<IPAddress> -netmask<subnetMask>

• add ns ip<IPAddress> <subnetMask> -type<type>

• add route Network<subnetMask> <gateway>

• set system user<userName> <password>

• save ns config

• reboot

LCD Keypad Setup

To set up the appliance by using the LCD keypad on the front panel of the appliance, enter the following initial settings in the following order:

1. Subnet mask

2. NSIP

3. Gateway

The NSIP and the default gateway should be on the same subnet. The subnet mask, NSIP, and gateway values are saved in the configuration file. You can then use the NSIP to connect to the appliance remotely. For more information, see the Citrix NetScaler Hardware Installation and Setup Guide at http://support.citrix.com/ article/ CTX132365.

Adding Controllers to Your Farm

Adding Controllers to Your Farm

After you install your first controller and create a farm, as described in “Installing Desktop Delivery Controller on a Single Server” on page 47, you can add controllers to the farm.

Before you start adding a controller to a farm, ensure that you know the details of the farm data store, because you have to specify these during installation.

Citrix recommends that Desktop Delivery Controller installation be carried out by a domain user with local administrator rights. Before you start the installation process, ensure that you read “Using Active Directory with Desktop Delivery Controller” on page 15, and that the necessary Active Directory permissions are in place.

To add a controller to a farm

1. Insert the Desktop Delivery Controller installation media in the appropriate drive.

If the Welcome page does not appear automatically, use Windows Explorer to open Autorun.exe.

2. On the Welcome page, click Install Server Components.

The End User License Agreement appears.

3. Select I accept the license agreement, then click Next.

You cannot click Back on this page. To change the installation option you chose, you must click Cancel, then restart the installation.

4. On the Select Components page, clear the check boxes for any components you do not want to install on this server. As a guideline, if licensing and the management consoles are already installed on at least one other controller in the farm, you do not need to install them again.

5. On the Create or Join a Farm page, select Join existing farm.

6. Type the name of any controller that is already in the farm. This must be the NetBIOS name, not the DNS name; for example, serversc, rather than serversc.eng.glarox.net.

Click Next.

7. On the Optional Server Configuration page, you must specify where the farm data store is.
If the farm data store is on a controller in the farm, leave the check box cleared.

If the farm data store is on a separate database server, select the check box.

You are prompted for the server’s details; make sure you specify the same database server for all controllers in the farm.

Click Next.

8. On the Start Installation page, click Next. A progress indicator page appears that shows you the installation progress for each component.

When installation is complete, click Next.

9. On the Setup Complete page, click Finish.

Using the Configuration Utility

Using the Configuration Utility

The Configuration Utility is a graphical interface program that helps you to configure a NetScaler

If your computer does not have a supported Java plug-in installed, the first time you log on to the NetScaler, the Configuration Utility will prompt you to download and install the plug-in.

Note: Prior to installing the Java 2 Runtime Environment, ensure that you have installed the full set of required operating system patches needed for the current Java release

To log on to the Configuration Utility

1. Open your Web browser and enter the NSIP as an HTTP address: 

http://<NSIP>

The Citrix Logon page appears.

Caution: If you have two NetScaler units in a high availability setup, make sure that you do not access the GUI by entering the IP address of the secondary NetScaler. If you do so and use the GUI to configure the secondary NetScaler, your configuration changes will not be applied to the primary NetScaler.

2. In the Username text box, type nsroot.

3. In the Password text box, type the administrative password you assigned to the nsroot account during initial configuration.

4. In the Start in list, click Configuration and click Login. The Configuration Utility page appears.

Note: If your workstation does not already have a supported version of the Java runtime plug-in installed, the NetScaler prompts you to download the Java Plugin. After the download is complete, the Configuration Utility page appears.

Note: If you need to access the online help, select Help from the Help menu at the top right corner.

If automatic installation of the Java plug-in the previous procedure fails, you can install the plug-in separately before you attempt to log on to the Configuration Utility.

To install the Java Runtime Plug-In separately

1. In your web browser, enter the NSIP and port number of your NetScaler:

http://<NSIP>:80

The Java plug-in icon appears.

2. Click the Java plug-in icon and follow the screen prompts to copy the plugin installer to your workstation hard disk. The Java plug-in setup icon (for example, j2re-1.4.2_04 -win) appears on your computer at the location you specified.

3. Double click the plug-in setup icon, and follow the screen prompts to install the plug-in.

4. Return to your Web browser and click the Java plug-in icon a second time to display the GUI logon screen.

Using the Statistical Utility

The Statistical Utility is a browser-based application that displays charts and tables on which you can monitor the performance of a NetScaler.

To log on to the Statistical Utility

1. Open your Web browser and enter the NSIP as an HTTP address:

http://<NSIP>

The Citrix Logon page appears.

2. In the Username text box, type nsroot.

3. In the Password text box, type the administrative password you assigned to the nsroot account during initial configuration.

4. In the Start in list, click Dashboard and click Login.

Note: If your workstation does not already have a supported version of the Java runtime plug-in installed, the NetScaler prompts you to download the Java Plugin. After the download is complete, the Statistical Utility page is displayed.

Connecting a Citrix NetScaler to the Network

Connecting a Citrix NetScaler to the Network

Connect the ports on a NetScaler to the network ports on the appropriate switches using the Ethernet/Fiber optic cables.

Caution: Be careful not to create a network loop by connecting more than one port on the NetScaler to the same switch or VLAN.

If your configuration does not require all of the available ports, you can use any of the ports. However, disabling the unused ports is advisable, and is mandatory in an HA configuration.

By default a NetScaler is configured to use auto negotiation. For a first-time installation, you should configure your switch to use auto negotiation for those ports that are connected to the NetScaler. After initial login and configuration, you can disable auto negotiation.

Connecting the Console Cable

Use the provided console cable when connecting the NetScaler to a PC or terminal. The PC or terminal must support VT100 terminal emulation and must be configured for 9600 baud, 8 data bits, 1 stop bit, and no parity.

Note: For instructions on how to access and configure a NetScaler using a command line interface, refer to the Accessing and Configuring a Citrix NetScaler chapter.

Connecting a Citrix NetScaler to the Power Source

The 7000 system has one power supply. The 9010, 10010, 12010, 15000, and 17000 systems each have two power supplies but can operate with a single power supply. The extra power supply is a backup.

To connect the 7000 system to the power source

1. Plug the power cord into the inlet receptacle on the back of the chassis.

2. Plug the other end of the power cord into a standard 110V/220V power outlet.

3. Turn the NetScaler on by pressing the ON/OFF switch on the back of the chassis. The LCD on the front should appear backlit once the NetScaler is operational.

To connect the 9010/10010/12000 system to the power source

1. Plug the power cord to the inlet receptacle on the back of the chassis.

2. Plug the other end of the power cord into a standard 110V/220V power outlet.

3. Repeat steps 1 and 2 to connect the other power inlet to a standard 110V/ 220V power outlet using another power cord.

4. Turn the NetScaler on by pressing the ON/OFF switch on the back of the chassis. The green LED on the back begins to glow, indicating that the NetScaler is powered on. The LCD on the front appears backlit once the NetScaler is operational.

Caution: The flash disk and hard disk are not hot swappable components and can be removed only when the NetScaler is powered down. Also note that neither the flash disk nor the hard disk should ever be removed except by certified Citrix NetScaler technicians. Doing otherwise voids the warranty.

The 9010/10010/12000 systems emit a high pitched alert if one power supply fails or if you connect only one power cord to the chassis. To silence the alarm, press the small red button on the back of the chassis.

Note: You might need to upgrade the system software. For details, refer to the Citrix NetScaler Migration Guide.

Installing the Citrix NetScaler Hardware

Installing the Citrix NetScaler Hardware

This chapter describes how to install the Citrix NetScaler hardware and then connect it to a network and the power source.

In This Chapter

Reviewing the Pre-Installation Checklist

Rack Mounting a Citrix NetScaler

Installing an SFP

Installing an XFP

Connecting a Citrix NetScaler to the Network

Connecting the Console Cable

Connecting a Citrix NetScaler to the Power Source

Reviewing the Pre-Installation Checklist

Before installing your NetScaler, you should prepare all equipment and materials required for installation. Completing this preparation in advance will help ensure a smooth installation, with minimal interruptions.

Review the following checklist to ensure that you have all the equipment required to complete the installation:

Hardware Requirements

Open the box that contains the NetScaler, and verify that it contains the following components and accessories:

• One NetScaler

• One RJ-45-to-RS-232 serial cable

• One RJ-45-to-DB-9 adapter

• One (with 7000 system) or two (with 9010/10010/12000/15000/17000 system) AC power cables (Make sure a power outlet is available for each cable.)

• One mounting rail kit 

In addition to the items listed above, the following items may also be required:

• Ethernet cables

• Ethernet switch ports to connect to the NetScaler

• Management workstation (PC or laptop)

Rack Mounting a Citrix NetScaler

Most appliances can be installed in standard server racks. The appliances ship with a set of rails, which you must install before you mount the appliance. The only tool you will need to install an appliance is a Phillips screwdriver.

Caution: If you are installing the appliance as the only unit in the rack, mount it at the bottom. If the rack contains other units, make sure that the heaviest unit is at the bottom. If the rack has stabilizing devices available, install them before mounting the appliance.

The 7000 appliance requires one rack unit. The 9010, 10010, 12000, MPX 15000, and MPX 17000 appliances each require two rack units. Each of these units ships with a mounting rail kit that contains two rail assemblies, one for the left side and the other for the right side of the appliance, and screws to attach the rails. You must install the assemblies before mounting the appliance in the rack.

To rack mount a Citrix NetScaler

1. Install the rear inner rails just behind the preinstalled front inner rails.

A. Starting with the right side of the chassis, align the two square holes on the rail against the hooks.

B. Attach the rail to the chassis with screws.

C. Repeat steps A and B to install the left rear inner rail.

2. Install the rack rails.

A. Determine where you want to place a NetScaler in the rack.

B. Position the chassis rail guides at the desired location in the rack, keeping the sliding rail guide facing inward.

C. Screw the assembly to the rack using the brackets provided.

D. Repeat steps B and C to attach the assembly to the other side of the rack. Be sure that both the rack rails are at same height and that the rail guides are facing inward.

Note: Before installing a NetScaler in the rack, be sure that the rear inner rails and the rack rails have been fitted.

3. Install the NetScaler in the rack.

A. Line up the rear inner rails with the rack rails.

B. Slide the chassis rails into the rack rails, keeping the pressure even on both sides. You may need to depress the locking tabs when inserting the chassis.

C. When the NetScaler is pushed completely into the rack, the locking tabs should "click."

D. Insert and tighten the thumbscrews to secure the front of the chassis to the rack.

Understanding Services

Understanding Services

Services represent applications on a server. While services are normally combined with vservers, in the absence of a vserver, a service can still manage application-specific traffic. For example, you can create an HTTP service on a NetScaler to represent a Web server application. When the client attempts to access a Web site hosted on the Web server, the NetScaler intercepts the HTTP requests and creates a transparent connection with the Web server.

In service-only mode, a NetScaler functions as a transparent proxy. It terminates client connections, uses the MIP to establish a connection to the server, and translates incoming client requests to the MIP. Although the clients send requests directly to the IP address of the server, the server sees them as coming from the MIP. The NetScaler translates the IP addresses, port numbers, and sequence

numbers.

A service is also a point for applying features. However, only a limited set of features can be configured in the service-only case. Consider the example of SSL acceleration. To use this feature, you must create an SSL service and bind an SSL certificate to the service. When the NetScaler receives an HTTPS request, it decrypts the traffic and sends it, in clear text, to the server.

Services use entities called monitors to track the health of applications. Every service has a default monitor, which is based on the service type, bound to it. As specified by the settings configured on the monitor, the NetScaler sends probes to the application at regular intervals to determine its state. If the probes fail, the NetScaler marks the service as down. In such cases, the NetScaler responds to client requests with an appropriate error message or re-routes the request as determined by the configured load balancing policies.

Understanding Policies and Expressions

A policy defines specific details of traffic filtering and management on a NetScaler. It consists of two parts: the expression and the action. The expression defines the types of requests that the policy matches. The action tells the NetScaler what to do when a request matches the expression. As an example, the expression might be to match a specific URL pattern to a type of security attack, with the action being to drop or reset the connection. Each policy has a priority, and the priorities determine the order in which the policies are evaluated.

When a NetScaler receives traffic to or from any server it manages, the appropriate policy list determines how to process the traffic. Each policy on the list contains one or more expressions, which together define the criteria that a connection must meet to match the policy.

For all policy types except Rewrite policies, a NetScaler implements only the first policy that a request matches, not any additional policies that it might also match. For Rewrite policies, the NetScaler evaluates the policies in order and, in the case of multiple matches, performs the associated actions in that order. Policy priority is important for getting the results you want.

Processing Order of Features

Depending on requirements, you can choose to configure multiple features. For example, you might choose to configure both compression and SSL offload. As a result, an outgoing packet might be compressed and then encrypted before being sent to the client. The following figure shows the interaction and processing order of the NetScalerfeatures.

A Simple Load Balancing Configuration

A Simple Load Balancing Configuration

In the example shown in the diagram, the NetScaler is configured to function as a load balancer. For this configuration, you need to configure virtual entities specific to load balancing and bind them in a specific order. As a load balancer, a NetScaler distributes client requests across several servers and thus optimizes the utilization of resources.

The basic building blocks of a typical load balancing configuration are services and load balancing vservers. The services represent the applications on the servers. The vservers abstract the servers by providing a single IP address to which the clients connect. To ensure that client requests are sent to a server, you need to bind each service to the vserver. That is, you must create services for every server and bind the services to the vserver. Clients use the VIP to connect to a NetScaler. When the NetScaler receives client requests on the VIP, it sends them to a server determined by the load balancing algorithm. Load balancing uses a virtual entity called a monitor to track whether a specific configured service (server plus application) is available to receive requests.

In addition to configuring the load balancing algorithm, you can configure several parameters that affect the behavior and performance of the load balancing configuration. For example, you can configure the vserver to maintain persistence based on source IP address. The NetScaler then directs all requests from any specific client to the same server.

Understanding Virtual Servers

A vserver represents one or more applications in a server farm. The vserver is a named NetScaler entity that external clients can use to access applications hosted on the servers. It is represented by an alphanumeric name, virtual IP address (VIP), port, and protocol. The name of the vserver is only of local significance and is designed to make the vserver easier to identify. When a client attempts to

access applications on a server, it sends a request to the VIP instead of the IP address of the physical server. When the NetScaler receives a request on the VIP, it terminates the connection at the vserver and uses its own connection with the server on behalf of the client. The port and protocol settings of the vserver determine the applications that the vserver represents. For example, a Web server can be represented by a vserver and a service whose port and protocol are set to 80 and HTTP, respectively. Multiple vservers can use the same VIP but different protocols and ports.

Vservers are points for delivering features. Most features, like compression, caching, and SSL offload, are normally enabled on a vserver. When the NetScaler receives a request on a VIP, it chooses the appropriate vserver by the port on which the request was received and its protocol. The NetScaler then processes the request as appropriate for the features configured on the vserver.

In most cases, vservers work in tandem with services. You can bind multiple services to a vserver. These services represent the applications running on physical servers in a server farm. After the NetScaler processes requests received on a VIP, it forwards them to the servers as determined by the load balancing algorithm configured on the vserver. The following diagram illustrates these concepts.

The preceding diagram illustrates a configuration consisting of two vservers with a common VIP but different ports and protocols. Each of these vservers has two services bound to it. The services s1 and s2 are bound to VS_HTTP and represent the HTTP applications on Server 1 and Server 2. The services s3 and s4 are bound to VS_SSL and represent the SSL applications on Server 2 and Server 3 (Server 2 provides both HTTP and SSL applications). When the NetScaler receives an HTTP request on the VIP, it processes the request based on the settings of VS_HTTP and sends it to either Server 1 or Server 2. Similarly, when the NetScaler receives an HTTPS request on the VIP, it processes it based on the settings of VS_SSL and it sends it to either Server 2 or Server 3.

Vservers are not always represented by specific IP address, port numbers, or protocols. They can be represented by wildcards, in which case they are known as wildcard vservers. For example, when you configure a vserver with a wildcard instead of a VIP, but with a specific port number, the NetScaler intercepts and processes all traffic conforming to that protocol and destined for the predefined

port. For vservers with wildcards instead of VIPs and port numbers, the NetScaler intercepts and processes all traffic conforming to the protocol.

Vservers can be grouped into the following categories:

• Load balancing vserver. Receives and redirects requests to an appropriate server. Choice of the appropriate server is based on which of various load balancing methods the user configures.

• Cache redirection virtual server. Redirects client requests for dynamic content to origin servers and static content to cache servers. Cache redirection vservers often work in conjunction with load balancing vservers.

• Content switching virtual server. Directs traffic to a server on the basis of the content that the client has requested. For example, you can create a content switching vserver that directs all client requests for images to a server that serves images only. Content switching vservers often work in

conjunction with load balancing vservers.

• Virtual private network (VPN) virtual server. Decrypts tunneled traffic and sends it to intranet applications.

Note: For more information about features, see the Citrix NetScaler Traffic Management Guide.

Understanding the Citrix NetScaler

Where Does a Citrix NetScaler Fit in the Network?

A NetScaler resides between the clients and the servers, so that client requests and server responses pass through it. In a typical installation, virtual servers (vservers) configured on the NetScaler provide connection points that clients use to access the applications behind the NetScaler. In this case, the NetScaler owns public IP addresses that are associated with its vservers, while the real servers are

isolated in a private network. It is also possible to operate the NetScaler in a transparent mode as an L2 bridge or L3 router, or even to combine aspects of these and other modes.

Physical Deployment Modes

A NetScaler logically residing between clients and servers can be deployed in either of two physical modes: inline and one-arm.

In the normal inline mode, multiple network interfaces are connected to different Ethernet segments and the NetScaler is placed between the clients and the servers. The NetScaler has a separate network interface to each client network and a separate network interface to each server network. The NetScaler and the servers can exist on different subnets in this configuration. It is possible for the

servers to be in a public network and the clients to directly access the servers through the NetScaler, with the NetScaler transparently applying the L4-L7 features. Usually, vservers (described later) are configured to provide an abstraction of the real servers. The following diagram illustrates a typical inline deployment.

In a less common version of one-arm mode, only one network interface of the NetScaler is connected to an Ethernet segment. The NetScaler in this case does not isolate the client and server sides of the network, but provides access to applications through configured vservers. This version of one-arm mode can simplify network changes needed for NetScaler installation in some environments.

Citrix NetScaler as an L2 Device

A NetScaler functioning as an L2 device is said to operate in L2 mode. In L2 mode, the NetScaler forwards packets between network interfaces when all of the following conditions are met:

• The packets are destined to another device's media access control (MAC) address.

• The destination MAC address is on a different network interface.

• The network interface is a member of the same virtual LAN (VLAN).

By default all network interfaces are members of a pre-defined VLAN, VLAN 1. Address Resolution Protocol (ARP) requests and responses are forwarded to all network interfaces that are members of the same VLAN. To avoid bridging loops, L2 mode must be disabled if another L2 device is working in parallel with the NetScaler.

Citrix NetScaler as a Packet Forwarding Device

A NetScaler can function as a packet forwarding device, and this mode of operation is called L3 mode. When a NetScaler in L3 mode receives, on its MAC address, unicast packets that are destined for an unknown IP address, it forwards them if there is a proper route to the destination. A NetScaler can also route packets between VLANs.

In both modes of operation, L2 and L3, a NetScaler generally drops packets that are in:

•Multicast frames

• Unknown protocol frames destined for a NetScaler's MAC address (non-IP and non-ARP)

• Spanning Tree protocol

Quick Start Installation and Configuration

Quick Start Installation and Configuration

Configuration Requirements

Determine the following information for performing the initial configuration.

• NetScaler IP address: The management IP address of the appliance.

• Subnet IP address or Mapped IP address: The IP address used by the appliance to represent the client when communicating with a server.

• Default gateway: The IP address of the router that forwards traffic out of the appliance’s subnet.

• Root password: The root user (nsroot) has full administrative privileges on the appliance. The root password is used to authenticate the root user.

Setting Up Connectivity

Connect the appliance to a management workstation or the network by using the NetScaler configuration utility, the command-line interface (CLI), or the LCD keypad.

Configuration Utility Setup

To set up the appliance by using the configuration utility, you need a management workstation or laptop configured on the same network as the appliance. To run the configuration utility, the Java RunTime Environment (JRE) version 1.4.2_04 or later must be installed on the workstation or laptop.

Note: The Setup Wizard automatically opens upon log on when the appliance is configured

with the default IP address, when licenses are not installed on the appliance, and when either

the mapped IP address or subnet IP address is not configured.

To configure the NetScaler by using the configuration utility

1. Connect the NetScaler to a management workstation or network.

2. Open a browser and type: http://192.168.100.1

Note: The NetScaler is preconfigured with the IP address 192.168.100.1.

3. In User Name, type nsroot.

4. In Password, type nsroot.

5. In the Setup Wizard, click Next and follow the instructions in the wizard.

6. To confirm that the NetScaler is configured correctly, you can either ping the new NetScaler

IP address (NSIP) or use the new NSIP to open the configuration utility in a browser.

CLI Setup

To set up the appliance by using the command-line interface (CLI), connect the serial cable to

the console port. Access the command line with a terminal or terminal emulator with the

following settings:

• Baud rate: 9600

• Data bits: 8

• Parity: None

• Stop bits: 1

• Flow control: None

Log on to the NetScaler with the following credentials:

User name: nsroot

Password: nsroot

To configure the NetScaler by using the NetScaler command line

At the NetScaler command prompt, type:

• set ns config -ipaddress<IPAddress> -netmask<subnetMask>

• add ns ip<IPAddress> <subnetMask> -type<type>

• add route Network<subnetMask> <gateway>

• set system user<userName> <password>

• save ns config

• reboot

LCD Keypad Setup

To set up the appliance by using the LCD keypad on the front panel of the appliance, enter the

following initial settings in the following order:

1. Subnet mask

2. NSIP

3. Gateway

The NSIP and the default gateway should be on the same subnet.

The subnet mask, NSIP, and gateway values are saved in the configuration file. You can then use the NSIP to connect to the appliance remotely. For more information, see the Citrix NetScaler Hardware Installation and Setup Guide at http://support.citrix.com/ article/ CTX132365.

Additional Information

A complete set of documentation is available on the Documentation tab of your NetScaler and from

http://support.citrix.com/. (Most of the documents require Adobe Reader, available at http://adobe.

com/ .)

To view the documentation

1. From a Web browser, log on to the NetScaler.

2. Click the Documentation tab.

3. To view a short description of each document, hover your cursor over the title. To open a

document, click the title.

If you have support questions, please contact Citrix Technical Support at 1-800-4-CITRIX (1-800-

424-8749). For additional contact information, see Support Phone Numbers at http://support.

citrix.com/. If you have comments or feedback on this documentation, please email to nsdocs_

feedback@citrix.com.