-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
-
Web proxy support for outbound calls to IDP or third party endpoints
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
Authentication and authorization for System Users
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Sample cluster configurations
The following example can be used to configure a four-node cluster with ECMP, cluster LA, or Linksets.
-
Create the cluster.
-
Log on to the first node.
-
Add the cluster instance.
> add cluster instance 1 -
Add the first node to the cluster.
> add cluster node 0 10.102.33.184 -backplane 0/1/1 -
Enable the cluster instance.
> enable cluster instance 1 -
Add the cluster IP address.
> add ns ip 10.102.33.185 255.255.255.255 -type CLIP -
Save the configurations.
> save ns config -
Warm reboot the appliance.
> reboot -warm
-
-
Add the other three nodes to the cluster.
-
Log on to cluster IP address.
-
Add the second node to the cluster.
> add cluster node 1 10.102.33.187 -backplane 1/1/1 -
Add the third node to the cluster.
> add cluster node 2 10.102.33.188 -backplane 2/1/1 -
Add the fourth node to the cluster.
> add cluster node 3 10.102.33.189 -backplane 3/1/1
-
-
Join the added nodes to the cluster. This step is not applicable for the first node.
-
Log on to each newly added node.
-
Join the node to the cluster.
> join cluster -clip 10.102.33.185 -password nsroot -
Save the configuration.
> save ns config -
Warm reboot the appliance.
> reboot -warm
-
-
Configure the NetScaler cluster through the cluster IP address.
// Enable load balancing feature
> enable ns feature lb// Add a load balancing virtual server
> add lb vserver first_lbvserver http .... .... -
Configure any one of the following (ECMP, cluster LA, or Linkset) traffic distribution mechanisms for the cluster.
ECMP
-
Log on to the cluster IP address.
-
Enable the OSPF routing protocol.
> enable ns feature ospf -
Add a VLAN.
> add vlan 97 -
Bind the interfaces of the cluster nodes to the VLAN.
> bind vlan 97 -ifnum 0/1/4 1/1/4 2/1/4 3/1/4 -
Add a spotted SNIP on each node and enable dynamic routing on it.
> add ns ip 1.1.1.10 255.255.255.0 -ownerNode 0 -dynamicRouting ENABLED > add ns ip 1.1.1.11 255.255.255.0 -ownerNode 1 -dynamicRouting ENABLED > add ns ip 1.1.1.12 255.255.255.0 -ownerNode 2 -dynamicRouting ENABLED > add ns ip 1.1.1.13 255.255.255.0 -ownerNode 3 -dynamicRouting ENABLED -
Bind one of the SNIP addresses to the VLAN.
> bind vlan 97 -ipAddress 1.1.1.10 255.255.255.0 -
Configure the routing protocol on ZebOS by using the VTYSH shell.
Static cluster LA
-
Log on to the cluster IP address.
-
Add a cluster LA channel.
> add channel CLA/1 -speed 1000 -
Bind the interfaces to the cluster LA channel.
> bind channel CLA/1 0/1/5 1/1/5 2/1/5 3/1/5 -
Perform an equivalent configuration on the switch.
Dynamic cluster LA
-
Log on to the cluster IP address.
-
Add the interfaces to the cluster LA channel.
> set interface 0/1/5 -lacpmode active -lacpkey 5 -lagtype cluster > set interface 1/1/5 -lacpmode active -lacpkey 5 -lagtype cluster > set interface 2/1/5 -lacpmode active -lacpkey 5 -lagtype cluster > set interface 3/1/5 -lacpmode active -lacpkey 5 -lagtype cluster -
Perform an equivalent configuration on the switch.
Linksets. Assume that the node with nodeId 3 is not connected to the switch. You must configure a linkset so that the unconnected node can use the other node interfaces to communicate with the switch.
-
-
Log on to the cluster IP address.
-
Add a linkset.
> add linkset LS/1 -
Bind the connected interfaces to the linkset.
> bind linkset LS/1 -ifnum 0/1/6 1/1/6 2/1/6
-
-
-
Update the state of the cluster nodes to ACTIVE.
> set cluster node 0 -state ACTIVE > set cluster node 1 -state ACTIVE > set cluster node 2 -state ACTIVE > set cluster node 3 -state ACTIVE
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.