4.4. Load Balancer(NetScaler VPX)

4.4.1. About This Menu

4.4.1.1. About This Menu

  • This menu, Load Balancer (NetScaler VPX), provides a Virtual Server installed Citrix NetScaler VPX.

  • Creating, configuring and deleting Load Balancer (NetScaler VPX), are completely automated. Customers are able to utilize them on-demand.

4.4.1.2. Features

The following are features of Load Balancer (NetScaler VPX) menu:

  • Offering NetScaler VPX’s functions as much as possible

    • NetScaler VPX enables almost all of its functions to Customers; as such, its functions for load-balancing, secured offloading with high-speed processing of web / application.

  • Automated provisioning with SDN-utilized technologies:

    • Customers can flexibly utilize their resources which is auto-provisioned without operating complex maneuvers with Load Balancer (NetScaler VPX) which activates SDN technologies.

  • Flexible network architecture in combination with Logical Network


4.4.1.3. Definition of Terms

  • Customer Portal/API: Portal/API provided by NTT Com

  • Citrix NetScaler VPX Portal/API/CLI: Portal/API/CLI provided as a standard function of Citrix NetScaler VPX

4.4.2. Available Functions

4.4.2.1. List of Functions

  • The following are functions available in this menu.This menu provide Portal/API/CLI for using each function.

No.

Function

Overview

Method of Operation

1

Instance Control Function

Provide functions such as creation, deletion of Load Balancer (NetScaler VPX), plan change and reboot, password reset and so on.

Customer Portal / API

2

Network Function

Provide the function to connect / disconnect Load Balancer (NetScaler VPX) to the Logical Network.

Customer Portal / API

3

Network Configuration for VRRP Function

Provide the function to register / clear the virtual address and VRID when redundantly configuring Load Balancer (NetScaler VPX) with the VRRP protocol.

Customer Portal / API

4

Syslog Transfer Function

  • Provide the function to register / clear the virtual address and VRID when redundantly configuring Load Balancer (NetScaler VPX) with the VRRP protocol.

  • ※ This function can be used only with 11.0-67.12 Standard Edition.

Customer Portal / API

5

Load Balancer Function

Open the NetScaler VPX control panel to customers and provide most of the Load Balancer functionality of NetScaler VPX.

NetScaler VPX Portal/API/CLI


4.4.2.2. Description of Functions


1.Instance Control Function

Create Load Balancer (NetScaler VPX)

  • Customer can create a new Load Balancer (NetScaler VPX) on Customers’ own via Customer Portal/API.

  • They can assign the following parameters while creating a Load Balancer (NetScaler VPX):

Available Parameters

Details

Name

Specify name of Load Balancer (NetScaler VPX).

Description

Specify description of Load Balancer (NetScaler VPX).

Plan

Specify a plan of Load Balancer (NetScaler VPX).

Zone / Group

Specify a Zone / Group where Load Balancer (NetScaler VPX) is accommodated.


Modify Load Balancer (NetScaler VPX)

  • Customer can create a new Load Balancer (NetScaler VPX) on Customers’ own via Customer Portal/API.

  • They can assign the following parameters while editing a Load Balancer (NetScaler VPX):

Available Parameters

Details

Name

Specify name of Load Balancer (NetScaler VPX).

Description

Specify description of Load Balancer (NetScaler VPX).

Load Balancer Plan

Specify plan for Load Balancer (NetScaler VPX). Plan can be changed.

Default Gateway

Edit the Default Gateway of Load Balancer (NetScaler VPX).

Note

  • In Load Balancer (NetScaler VPX), the number of interface is different for each plan.
    Please refer to Plan list.
  • For changing the plan by reducing the number of interfaces, it is necessary to disconnect the interface of the slot number that is not supported by Load Balancer (NetScaler VPX) after the change in advance from the Logical Network.
    For example, if you want to change the plan from 8 interfaces to 4 interfaces, it is necessary to disconnect the interfaces of the slot number 5 to 8 (4 slots) in advance from the Logical Network.
  • If there is a change plan to increase the number of interfaces, or if there is no change of the number of interfaces before and after the change plan, it is not necessary to disconnect the interface from the Logical Network in advance.
  • Please note that if you implement the change plan, Load Balancer (NetScaler VPX) will restart.

Reboot Load Balancer (NetScaler VPX)

  • Customers can reboot the subscribed Load Balancer (NetScaler VPX) via Customer Portal/API.


Reset Password of Load Balancer (NetScaler VPX) Account

  • Reset password of Customers’ account for accessing to Load Balancer (NetScaler VPX).

Important

  • Resetting passwords for Load Balancer (NetScaler VPX) is executable only with initial account (i.e., user-admin., user-read).

  • Reset password of Customers’ account for accessing to Load Balancer (NetScaler VPX) via Citrix NetScaler VPX Portal/API/CLI.


Delete Load Balancer (NetScaler VPX)

  • Delete Load Balancer (NetScaler VPX)


View Load Balancer (NetScaler VPX) Information

  • Customers can view Load Balancer (NetScaler VPX)’s information on Customers’ own via Customer Portal/API.

  • Following are available information details.

Categories

Available Information

Details

Information

Name

View name of Load Balancer (NetScaler VPX).

Information

ID

View ID of Load Balancer (NetScaler VPX).

Information

Description

View description of Load Balancer (NetScaler VPX).

Information

Tenat ID

View tenant ID of Load Balancer (NetScaler VPX).

Information

Default Gateway

View default gateway of Load Balancer (NetScaler VPX).

Information

Zone / Group

View Zone/Group where Load Balancer (NetScaler VPX) is accommodated.

Information

User Name

View user name of Load Balancer (NetScaler VPX).

Information

Administrator Name

View name of administrator of Load Balancer (NetScaler VPX).

Information

Status

View operation status of Load Balancer (NetScaler VPX).

Plan

Name

View plan name.

Plan

ID

View plan ID.

Plan

Description

View plan description.

Plan

Vendor

View plan version.

Plan

Version

View plan version.

Plan

Model Size

View the model size of Load Balancer (NetScaler VPX).

Plan

Model Edition

View the model edition of Load Balancer (NetScaler VPX).

Interface

Name

View interface name of Load Balancer (NetScaler VPX).

Interface

Description

View interface description of Load Balancer (NetScaler VPX).

Interface

Slot Number

View interface slot number of Load Balancer (NetScaler VPX).

Interface

Logical Network

View the connected logical network of Load Balancer (NetScaler VPX) interface.

Interface

IP Address

View IP address of Load Balancer (NetScaler VPX) interface.

Interface

Virtual IP Address

View virtual IP address of Load Balancer (NetScaler VPX) interface.

Interface

Status

View status of Load Balancer (NetScaler VPX) interface.

Interface

Action

View operating menu of Load Balancer (NetScaler VPX) interface.


Network Function

Connect Load Balancer (NetScaler VPX) Interface

  • Customers can connect the interface of the subscribed Load Balancer (NetScaler VPX) to Logical Network via Customer Portal/API.

  • Following parameters can be set when connecting the interface of Load Balancer (NetScaler VPX):

Available Parameters

Details

IP Address

Assign IP address for Load Balancer (NetScaler VPX) interface.
-The IP address mentioned above will be assigned to Load Balancer (NetScaler VPX) as the static IP address.

Logical Network

Specify a destination Logical Network.

Note

  • Customers need to prepare Logical Network to connect with Load Balancer (NetScaler VPX) and its Subnet in advance.

  • In order to have extensibility of resource expansion, please set a wide range of address range belongs to Logical Network.

  • Load Balancer (NetScaler VPX) can connect to the Logical Network (Data Plane) only. It cannot connect to the Logical Network (Storage Plane)

  • Customers are advised that the Load Balancer (NetScaler VPX) is rebooted when they connect to the interface.

  • Customers are advised that the MAC address is changed once interface is connected.

  • IP Address which Customers have set via Customer Portal/API cannot be deleted via Citrix NetScaler VPX Portal/API/CLI.


Disconnect Load Balancer (NetScaler VPX) Interface

  • Customers can disconnect subscribed Load Balancer (NetScaler VPX) interface from Logical Network via Customer Portal/API.

  • Following parameters can be viewed when disconnecting Load Balancer (NetScaler VPX) Interface:

Available Parameters

Details

Logical Network

View Logical Network to be detached.

IP Address

View IP address of Load Balancer (NetScaler VPX) interface.

Important

  • Customers are advised that the Load Balancer (NetScaler VPX) is rebooted once the interface is disconnected.

  • Customers are advised that the MAC address is changed once interface is disconnected.


Modify Load Balancer (NetScaler VPX) Interface

  • Customers can modify interface of contracted Load Balancer (NetScaler VPX) via Customer Portal/API.

  • Following parameters can be set when editing interface of Load Balancer (NetScaler VPX):

Available Parameters

Details

Description

Specify a description for interface.


Network Configuration for VRRP Function

Register Network Configuration for VRRP of Load Balancer (NetScaler VPX)

  • Customers can register the network configuration for VRRP of subscribed Load Balancer (NetScaler VPX) via Customer Portal/API.

  • Following parameters can be specified when registering the network configuration for VRRP of Load Balancer (NetScaler VPX).

Available Parameters

Details

Subnet

Specify the Subnet of Logical Network to connect.

Virtual IP Address

Specify the virtual IP address for VRRP.

VRID

Specify the VRRP group identifier.

Important

  • This configuration is required for each Load Balancer (NetScaler VPX) configuring VRRP.

  • In order to communicate using VRRP, it is necessary to perform VRRP setting at Citrix NetScaler VPX Portal/API/CLI after implementing this setting.

  • In VRRP configuration, customer can set only a pair of Virtual IP address and VRID at one interface.


Clear Network Configuration for VRRP of Load Balancer (NetScaler VPX)

  • Customers can clear the network configuration for VRRP of subscribed Load Balancer (NetScaler VPX) via Customer Portal/API.

  • Following parameters can be viewed when clearing the network configuration for VRRP of Load Balancer (NetScaler VPX).

Available Parameters

Details

Virtual IP Address

This configuration is required for each Load Balancer (NetScaler VPX) configuring VRRP.

VRID

Specify the VRRP group identifier.

Important

  • This configuration is required for each Load Balancer (NetScaler VPX) configuring VRRP.

  • In addition to this configuration, it is mandatory to clear VRRP configuration via Citrix NetScaler VPX Portal/API/CLI.


4.Syslog Transfer Function

  • It is possible to set syslog transfer settings from the load balancer to the syslog server prepared by the customer.

  • This function is not a function to create a syslog server as a log transfer destination.

  • If customers use this function, they need to prepare Load Balancer (NetScaler VPX) in advance.

  • For one Load Balancer (NetScaler VPX), Up to 8 syslog transfer settings can be set. Also, for one Load Balancer (NetScaler VPX), it is not possible to set multiple syslog transfer settings for the same syslog server.

Register of syslog transfer settings

  • Customer can register the syslog transfer settings of subscribed Load Balancer (NetScaler VPX) of Customers’ own via Customer Portal/API.

  • When registering syslog forwarding settings, customers can specify the following parameters.

Categories

Available Parameters

Details

General

Name

Customers can specify a name to manage as syslog forwarding settings.

General

Description

Customers can specify a description to manage as syslog forwarding settings.

General

IP Address

  • Customers can specify the IP address for transferring the log set in the syslog transfer setting.

  • If the IP address specified by the syslog transfer function is already used in Load Balancer (registered in Server and it is the load balancing destination, etc.), a setting error occurs. In case of error occurrence, please re-register after canceling the setting.

  • Example) If the load balancing destination WEB server is also used as the syslog server, an error occurs.

General

Transport type

Customers can specify the transport type (UDP) for transferring logs set in syslog forwarding settings.

General

Port number

Customers can specify the port number for transferring the log set in the syslog forwarding setting.

General

Log level

  • Customers can specify the log level (ALL, NONE, CUSTOMIZE) when transferring the log set in the syslog transfer setting.

  • If CUSTOMIZE is selected, customers can specify more than one of the following log levels, but only log messages corresponding to the specified log level are subject to log transfer.

  • Log Level customers can specify: ALERT,ERROR,CRITICAL,WARNING,NOTICE,EMERGENCY,DEBUG,INFORMATIONAL

General

Log facility

  • Customers can specify the log facility (LOCAL 0 - LOCAL 7) when transferring logs set in syslog forwarding settings.

  • If customer specify a log facility, NetScaler VPX logs are transferred to the syslog server as the specified log facility.

Designated

Date format

Customers can specify the date format for transferring logs set in syslog forwarding settings.

Designated

TimeZone

Customers can specify the time zone when transferring the log set in the syslog transfer setting.

Designated

Priority

Customers can specify the order of priority when transferring logs set in syslog forwarding settings.

Designated

TCP logging

It is possible to specify whether the TCP log is to be additionally output for the log set in the syslog transfer setting.

Designated

ACL logging

Customers can also specify whether to set the logs of ACLs to be additionally output for logs set in syslog forwarding settings.


Important

  • In this setting, Syslog transfer is performed using load balancing function of load balancer. Therefore, the load balancing function that is invalid at the time of initial construction is activated.


Edition of Syslog Transfer Settings

  • Customer can modify the syslog transfer settings of subscribed Load Balancer (NetScaler VPX) of Customers’ own via Customer Portal/API.

  • When editing the syslog forwarding settings, customers can specify the following parameters.

Categories

Available Parameters

Details

General

Description

Customers can specify a description to manage as syslog forwarding settings.

General

Log level

Customers can specify the log level when transferring the log set in the syslog transfer setting.

General

Log facility

Customers can specify the log facility for transferring the log set in the syslog transfer setting.

Designated

Date format

Customers can specify the date format for transferring logs set in syslog forwarding settings.

Designated

TimeZone

Customers can specify the time zone when transferring the log set in the syslog transfer setting.

Designated

Priority

Customers can specify the order of priority when transferring logs set in syslog forwarding settings.

Designated

TCP logging

It is possible to specify whether the TCP log is to be additionally output for the log set in the syslog transfer setting.

Designated

ACL logging

Customers can also specify whether to set the logs of ACLs to be additionally output for logs set in syslog forwarding settings.


Important

  • Anything other than those specified above can not be edited.


Release of syslog transfer setting

  • Customer can delete the syslog transfer settings of subscribed Load Balancer (NetScaler VPX) of Customers’ own via Customer Portal/API.


Important

  • After releasing the syslog setting, the load balancing function will remain enabled.


See information on syslog transfer setting

  • Customer can view the syslog transfer settings of subscribed Load Balancer (NetScaler VPX) of Customers’ own via Customer Portal/API.

  • Following are available information details.

Available Information

Details

Name

Names managed as syslog forwarding settings can be referred.

ID

IDs managed as syslog transfer settings can be referred.

Description

The description managed as syslog forwarding settings can be referred.

Tenat ID

The tenant ID to which the load balancer that is setting the syslog transfer setting belongs can be referred.

Load Balancer ID

The load balancer ID for the syslog transfer setting can be referred.

Status

The customer can see the status of the syslog forwarding settings.

IP Address

Customers can refer to the IP address for transferring the log set in the syslog transfer setting.

Transport type

Customers can refer to the transport type when transferring the log set in the syslog transfer setting.

Port number

Customers can refer to the port number for transferring the log set in the syslog transfer setting.

Log level

Customers can refer to the log level at the time of transferring the log set in the syslog transfer setting.

Log facility

Customers can refer to the log facility at the time of transferring the log set in the syslog transfer setting.

Date format

Customers can refer to the date format when transferring the log set in the syslog transfer setting.

TimeZone

Customers can refer to the time zone when transferring the log set in the syslog transfer setting.

Priority

Customers can refer to the order of priority when transferring logs set in syslog forwarding settings.

TCP logging

Customers can refer to whether the TCP log is set to be additionally outputted to the log set in the syslog transfer setting.

ACL logging

Customers can refer to the logs set in the syslog forwarding settings to see if the ACL log is also set to be outputted additionally.


5.Load Balancer Function

Function Overview

Provided Version

  • In the load balancer (NetScaler VPX), the provided information of the version is as follows.

No

Product Name

Provided Version

Improved content

1 NetScaler VPX 10.5-57.7 Standard Edition  
2 NetScaler VPX 11.0-67.12 Standard Edition
In the 11.0-67.12 Standard Edition, the following points of the 10.5-57.7 Standard Edition were improved.
  • In addition to the access by GUI / API to NetScalerVPX, customers are able to access by CLI.

  • In addition to the access by HTTP to the NetScalerVPX Portal (GUI) , customers can also access by HTTPS.

  • From NetScalerVPX, Ping command and Traceroute command can be executed.

  • For the NetScalerVPX, the settable SHA2 cipher suites has been increased.

  • A function to transfer NetScaler VPX logs to any syslog server created by Customer has been added.

2 NetScaler VPX 12.0-53.13 Standard Edition
In the 12.0-53.13 Standard Edition, the following points of the 10.5-57.7 Standard Edition were improved.
  • SSL performance is improved.

  • Troubles that can not view, download, or delete registration certificates, etc have been resolved.

  • The maximum value of VRRP Dead Interval has been expanded. (Changed from 1 second to 60 seconds)

  • When using VRRP, there was a possibility that the communication interruption might continue at the time of switching, but this trouble was resolved. For details of this trouble, please refer to Restrictions <https://ecl.ntt.com/documents/service-descriptions/loadbalancer/loadbalancer.html#id30> _ “Redundancy (VRRP) related” .


Lifecycle Policy

Lifecycle policy of LoadBalancer (NetScaler VPX) is described below.

  • Basic Policy
    • Provides up to 2 versions.(As an exceptions, provides 3 versions at the same time considering replacement time from old version to new one.)

    • Provided version is decided by NTTCom considering stability, use condition, support term and so on.

    • When a new region is released on ECL 2.0, only the latest version at the time of region release will be offered.

  • End of Sales (EOS) Policy
    • When new version is provided, if exceeding the number provided above(2 versions), stop selling old version about 1 year after offering date.

    • When EOM (* 1) / EOL (※ 2) is notified from the product maker, stop selling the corresponding version about 1 year after notification for the customer.

    • Please refer to the NetScaler ADC of Product Matrix <https://www.citrix.com/support/product-lifecycle/product-matrix.html> _ for the EOM / EOL information of the software (Citrix NetScaler VPX) provided in this menu.本

    • ※1 End of Maintenance(EoM):Date on which code level maintenance will not be performed except for security-related updates Citrix has deemed necessary.

    • ※2 End of Life(EoL):The day when security related maintenance Build and technical support ends.

  • End of Life (EOL) Policy
    • Inquiries / troubleshooting support of our offerred version including those newly suspended is provided until EOL of the product maker.

    • For the support content, please see Scope of support . However, support on failing virtual server infrastructure will continue even after EOL.

  • How to replace version
    • Since this menu does not provide upgrade to the new version, customers need to subscribe to the new version of Load Balancer (Citrix NetScaler VPX) and switch from the old version of Load Balancer (Citrix NetScaler VPX). Please refer to Replacing between different version for the procedure for switching load balancers .

    • Please consider replacing plan with customer’s cost and responsibility referring to the following EOS / EOL information.

  • EOS/EOL Information

Version

EOS EOL
10.5-57.7 Standard Edition

Planned for February 2020

Pending

11.0-67.12 Standard Edition

Planned for February 2020

Planned for May 2020

  • This information is subject to change without prior notice to customers.

4.4.3. Service Plan

4.4.3.1. Plan List

  • Following Plans are provided:

Plan

CPU MEM DISK

Number of Interfaces

Description

50Mbps 2CPU-8GB-4IF 2 8(GB) 20(GB) 4

The maximum throughput is 50Mbps.

200Mbps 2CPU-8GB-4IF 2 8(GB) 20(GB) 4

The maximum throughput is 200Mbps.

1000Mbps 4CPU-16GB-8IF 4 16(GB) 20(GB) 8
The maximum throughput is 1000Mbps.
(In the case of HTTP compression, the maximum is 750Mbps)
3000Mbps 4CPU-16GB-8IF 4 16(GB) 20(GB) 8
The maximum throughput is 3000Mbps.
(In the case of SSL communication, the maximum is 1000Mbps)
(In the case of HTTP compression, the maximum is 750Mbps)

4.4.3.2. Subscription Methods

  • The type of application is as follows. It should be noted, by the following application, that the billing amount is subject to change.

Subscription Type

Subscription Methods

Offered Date

Create Load Balancer (NetScaler VPX)

Customers are able to order via Customer Portal / API

Instance Offering

Changing the load balancer’s plan (NetScaler VPX)

Customers are able to order via Customer Portal / API

Instance Offering

Delete Load Balancer (NetScaler VPX)

Customers are able to order via Customer Portal / API

Instance Offering


4.4.3.3. Delete Load Balancer (NetScaler VPX)

  • The maximum, minimum and sales unit per tenant of the load balancer (NetScaler VPX) is as follows.

Maximum Number

Minimum Number

Unit

16 0 1

4.4.4. Terms and Conditions

4.4.4.1. Conditions of Usage with Other Menus

  • There is no specific conditions. Customers may subscribe this menu in combination with all the menus of Enterprise Cloud 2.0.


4.4.4.2. Minimum Contract Period

  • There is no minimum contract period.


4.4.5. Pricing

4.4.5.1. Initial Fee

  • There is no initial fee.

4.4.5.2. Monthly Fee

  • Monthly fee is applied for this menu.

  • Monthly fee is per-minute-basis with capped pricing per month.

4.4.6. Quality of Service

4.4.6.1. Support Coverage

  • Virtual Server, Citrix NetScaler VPX and Customer Portal/API is covered.

  • For inquiries about functions to operate with Customer Portal/API, NTT Com support the setting method.

  • Inquiries about function to operate with Citrix NetScaler VPX Portal/API/CLI.

    • Example of setting function verified by NTTCom and usage models verified by NTTCom are supported free of charge.

    • With regard to the functions that NTT Com have not verified, for customers who applied for the advanced plan (charged) NTT Com can escalate vendors and confirm them. However, in this case NTT Com will exclude inquiries about technical support such as architecture and design support, performance tuning of customer environment, verification of applications individually introduced by customers. Please refer to Service Description of Support for the specification details about the advanced plan.

  • NTT Com will support at the time of breakdown such as when the function Customer used can not be used.


4.4.6.2. Operation

  • Quality of this menu’s Operations corresponds to that of standardized regulations which NTTCom defines thereof in details.

4.4.6.3. SLA

  • The SLA for this Service Menu meets the SLA Standards defined by Enterprise Cloud 2.0.

4.4.7. Restrictions

Note

  • Setting method and performance information are posted , so please be sure to check the tutorial.

Providing Method

  • This menu provide Citrix NetScaler VPX installed on Virtual Server.

  • Maximum of 16 Load Balancer (NetScaler VPX)s are available for 1 tenant.

  • Provide Customer Portal/API for implementing creation, deletion, plan change, reboot, password reset, interface connection, VRRP communication setting, syslog transfer setting etc. of Load Balancer (NetScaler VPX). Provide Citrix NetScaler VPX Portal/API/CLI for configuring Citrix NetScaler VPX configuration.

  • Partial functions of Citrix NetScaler VPX are restricted to realize functions provided by Customer Portal/API. For details, refer to others in “Restrictions”.

  • Please note that Load Balancer (NetScaler VPX) restarts when plan change is done.

  • Example of setting the function verified by NTTCom (https://ecl.ntt.com/en/documents/tutorials/rsts/LoadBalancer/netscaler-vpx/index.html) and usage models verified by NTTom (https://ecl.ntt.com/en/documents/tutorials/rsts/networkfunction/index2.html) are posted in the tutorial.

  • For other functions with Citrix NetScaler VPX Portal/API/CLI, please refer to the Citrix documentation (https://ecl.ntt.com/en/documents/tutorials/rsts/LoadBalancer/netscaler-vpx/guide.html) Please check as a reference.

  • Customer can not shut down Load Balancer (NetScaler VPX) via Citrix NetScaler VPX Portal/API/CLI and Customer Portal/API.

  • Do not delete the license file from the Citrix NetScaler VPX Portal. After restarting Netscaler VPX, license authentication can not be performed and the load balancer function can not be used. Also, do not upload your customer’s license file to Citrix NetScaler VPX Portal. (You can not activate with customer’s brought in license file.)

  • When connecting to Citrix NetScaler VPX portal using Internet Explorer, you need to activate “active script” by clicking “Customize level” on the “Security” tab of Internet option.

  • If you want to access via Citrix NetScaler VPX CLI, it is necessary to allow SSH access to the IP address assigned to Load Balancer (NetScaler VPX) beforehand, so please refer to the tutorial (https://ecl.ntt.com/en/documents/tutorials/rsts/LoadBalancer/netscaler-vpx/login.html) as a reference.

  • Configurations including managed settings will not be available for Customers to view, modify or delete.(Only “show running” Config. is available for view; however, neither Saved Config. or ns.confi will not be available for Customers’ view)


Interface related

  • In this menu, the number of interfaces differs for each plan. Please check the plan list for the number of available interfaces.

  • To connect the interface of Firewall (Brocade 5600 vRouter) to Logical Network , please refer to “Connect Firewall (Brocade 5600 vRouter) Interface” and execute via Customer Portal/API.

  • Customers need to prepare Logical Network and Subnet to connect with Load Balancer (NetScaler VPX) in advance.

  • Load Balancer (NetScaler VPX) can connect to Logical Network (Data Plane) only. It cannot connect to Logical Network (Storage Plane)

  • Customers are advised that Load Balancer (NetScaler VPX) is rebooted when they connect / disconnect to the interface. If necessary, please save the configuration fie before connecting / disconnecting to the interface.

  • Customers are advised that the MAC address is changed once interface is connected / disconnected.

  • Enable/Disable of the interface and Duplex/Speed can not be set via Citrix NetScaler VPX Portal/API/CLI and Customer Portal/API.

  • In case of changing the plan to reduce the number of interfaces, it is necessary to disconnect the interface of the slot number that is not supported by the plan after the change from the Logical Network in advance . For example, if you want to change the plan from 8 interfaces to 4 interfaces, it is necessary to disconnect the interfaces of the slot number 5 to 8 (4 slots) from the Logical Network in advance.

  • In case of changing the plan to increase the number of interfaces, or changing the plan with no change of the number of interface, it is not necessary to disconnect the interface from the Logical Network in advance.

  • The IP address setting for management (“NSIP (NetScalerIP)”, “SNIP (SubNetIP) with 100.xx.xx.xx allocated address”), VLAN interface setting (VLAN0,Interface0/1) can not be viewed, changed, deleted.

  • When the SNIP address is created, ssh, telnet, ftp can not be set as Enable in 10.5-57.7 Standard Edition.

  • When the SNIP address is created, telnet, ftp can not be set as Enable in 11.0-67.12 Standard Edition.

  • VLAN of NetScaler VPX is internal settings; therefore, Customers are not required to set VLAN.

  • This operation may take about 10 minutes.

  • Please specify IP address range not overlapped with those used inside of LoadBalancer. If customers specify value overlapped with , error is occurred and recreation of LoadBalancer may be needed.

  • MTU size supports up to 1500 bytes.


Address/Routing/Filtering related

  • Customers cannot view / modify / delete managed routing.

  • IP Address which Customers have set via Customer Portal/API cannot be deleted via Citrix NetScaler VPX Portal/API/CLI.

  • The IP address specified via Customer Portal/API is the access point to Citrix NetScaler VPX Portal/API/CLI.

  • Please set the default gateway in “Modify Load Balancer (NetScaler VPX)” of Customer Portal/API. Default gateway can not be set via Citrix NetScaler VPX Portal/API/CLI.

  • Priority order for Access Control List and / or Policy-Based Routing cannot be modified.

  • Customers can use Priority of Access control list and Policy base routing from over 200. (They cannot use 1 to 199 because these are used for management.)

  • Access Control List and / or Policy-Based Routing cannot be deleted in bulk.


SNMP related

  • Managed SNMP settings are not available for Customers to view or modify or delete.

  • SNMP Manager is not available for Customers to assign.


Traffic Domain related

  • Customers are noted only Traffic Domain 10 can be viewed. (Managed Traffic Domain 0 cannot be viewed, utilized, or deleted.)

  • Customers are required to always assign Traffic Domain 10 when they need to assign Traffic Domain in server settings such as in “Virtual Server” in NetScaler VPX.


Redundancy (VRRP) related

  • When using VRRP, please make DHCP function (address setting function) of the Logical Network to be connected “valid”. When the DHCP function is “invalid”, the ARP request is executed at the source address of 0.0.0.0 on ECL2.0 Network. In this case, it is confirmed that this product do not reply ARP, and it may affect VRRP redundancy.

    •  With the following version, it is confirmed that NetScaler VPX does not reply ARP.

    • NetScaler VPX Version11.0 Build67.12 Standard Edition
    • NetScaler VPX Version10.5 Build57.7 Standard Edition
  • For VRRP setting, you need to do the VRRP set via Citrix NetScaler VPX Portal/API/CLI after “Register Network Configuration for VRRP of Load Balancer” via Customer Portal/API. Set the same value for parameters such as VRID.

  • For VRID (VRRP group ID), specify a value that does not overlap in the same segment

  • The VRRP setting must be made for all Load Balancer (NetScaler VPX)s that make up VRRP.

  • For one interface, please set only one pair of virtual IP address and VRID set in Register Network Configuration for VRRP via Customer Portal/API. Setting multiple pairs does not work properly.

  • Please enable preempt setting. It has been confirmed that the status will not return to Master / Backup when the VRRP status goes into the Master / Master for some reason.

  • Asymmetric communication is not supported in this service. Citrix NetScaler VPX can not synchronize VRRP status of multiple interfaces. Please make the redundancy with VRRP only on the client side and activate Source NAT of Citrix NetScaler VPX so that the communication goes the same route back and forth.


System Log related

  • Customers can use the syslog transfer function to perform log transfer settings on the Load Balancer, but syslog servers to which logs are forwarded are not created.

  • In case of using the function of syslog transfer, make sure to prepare Load Balancer (NetScaler VPX) in advance.

  • For one Load Balancer (NetScaler VPX), Up to 8 syslog transfer settings can be set. Also, for one Load Balancer (NetScaler VPX), it is not possible to set multiple syslog transfer settings for the same syslog server.

  • If the IP address specified by the syslog transfer function is already used in Load Balancer (registered in Server and it is the load balancing destination, etc.), a setting error occurs. In case of error occurrence, please re-register after canceling the setting.

    Example) If the load balancing destination WEB server is also used as the syslog server, an error occurs.

  • If CUSTOMIZE is selected, customers can specify more than one of the following log levels, but only log messages corresponding to the specified log level are subject to log transfer.

    Log Level customers can specify: ALERT,ERROR,CRITICAL,WARNING,NOTICE,EMERGENCY,DEBUG,INFORMATIONAL

  • If customer specify a log facility, NetScaler VPX logs are transferred to the syslog server as the specified log facility.


Account related

  • Customers cannot modify user’s account-related permissions.

  • Only Local Authority Functions are available. Authenticating servers such as LDAP, RADIUS, TACACS+, SAML, Negotiate (Active Directory) etc. are not utilized.

  • Resetting passwords for Load Balancer (NetScaler VPX) is executable only with initial account (i.e., user-admin., user-read). Reset password of Customers’ account for accessing to Load Balancer (NetScaler VPX) via Citrix NetScaler VPX Portal/API/CLI.

  • Customers can freely create accounts belonging to one of the following two groups, but accounts starting with nsroot and provider- are administrative accounts and can not be used / created.

  • Customers are not allowed to modify the default settings on groups.

  • Customers are not allowed to create any new additional group.

Users in Scenario

Assigned Group

Initialized Account Name

Permissions Overview

Administrator

user-admin-group(administrator) user-admin

The user has a permission to view / add / modify / delete Load Balancer functions.

User

user-read-group(operator) user-read

The user has a permission to view Load Balancer functions.


Version upgrade for

  • Separately, a contract with the new version of the Load Balancer (NetScaler VPX) has to be made, and customers need to switch from the old version Load Balancer (NetScaler VPX) to the new version Load Balancer (NetScaler VPX) .


Others

  • Customers cannot view/change/delete the resource which include the word “PROVIDER”. (It is because this resource is used for management. e.g. “IN_PROVIDER_01” in access control list. )

  • Customers are noted that Global System Set Parameters are not viewed, edited or deleted by them.

  • Load Balancer (NetScaler VPX) can not perform content checking, deletion, or downloading of server certificates registered in the following versions.

    • NetScaler VPX Version11.0 Build67.12 Standard Edition
  • The following functions can not be used.

    • Cooperation with external system Function

      • DNS(Server, Client), NTP(Client)
    • Network related

      • IPSec, IPTunnel, IP6Tunnel, bridgegroup, forwardingSession, NetworkVisualizer
    • Redundancy related

      • Redundancy by NetScaler’s HA (High Availablity) function

    • Syslog related

      • Syslog, Nslog (11.0 - 67.12 Standard Edition allows you to use the syslog transfer function.)

    • Others

      • batch, source, install, import / export application (AppExpert function), scp, shutdown, reboot, show techsupport, start / stop / dump nstrace (packet capture), shell command, GUI function using these

Reference Performance Information

  • Performance information of LoadBalancer (NetScaler VPX) is posted in tutorial.

  • The maximum value in each performance item is measured and not all the maximum values of each performance item are measured at the same time.

  • Please note that this verification result is a reference value, it does not guarantee performance.

  • Regarding the number of sessions, there is restrictions of virtual server installed Load Balancer(NetScaler VPX). For details, please refer to Restrictions of Instance .