-
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 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
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
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
-
-
-
-
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!
Configuration of cluster ECMP by using Cisco Nexus 7000 switch with routing Protocol
With ECMP over a cluster setup, a NetScaler appliance is able to handle the traffic through a routing protocol. The ECMP mechanism helps in advertising the virtual server IP addresses through all active cluster nodes.
To use ECMP, you must first enable the BGP protocol on the cluster IP address. Bind the interfaces and the spotted IP address (with dynamic routing enabled) to a VLAN. Configure the selected routing protocol and redistribute the kernel routes on the ZebOS by using the VTYSH shell.
Use Case: Cluster ECMP by using Cisco Nexus 7000 switch with routing Protocol
Consider an example of a cluster deployment with a Cisco Nexus 7000 switch:
- Two NetScaler appliances (Node 1 and Node 2), connected to the Nexus switch (upstream).
- Two Cisco Nexus 7000 switch.
- Client and server (drawing HTTP traffic through the Nexus switch). With Hot Standby Router Protocol (HSRP) enabled on the client-side.

Prerequisites
Consider the following points before configuring cluster nodes on a NetScaler appliance.
- All appliances must be of the same platform type.
- Border Gateway Protocol (BGP) must be enabled on the cluster nodes.
Configuring by using the CLI on a NetScaler appliance
-
Log on to an appliance (for example, appliance with NSIP address 1.1.1.1)
-
To add a cluster node.
add cluster node 0 1.1.1.2 –state ACTIVE –backplane 0/10/8 -
To add the cluster IP address
add ns ip 1.1.1.10 255.255.255.254 –type clip -
Save the configuration
save ns config -
Warm reboot the appliance
reboot -warm -
To add node 1 using CLIP
add cluster node 1 2.2.2.2 –state ACTIVE –backplane 1/10/8 -
To join a node to the cluster
join cluster –clip 1.1.1.10 –password nsroot -
Perform the following configuration on CLIP
-
enable ns feature bgp ospf DYNAMICROUTING -
add ns ip 11.1.1.3 255.255.255.254 –dynamicRouting ENABLED –ownerNode 0 -
add ns ip 11.1.1.7 255.255.255.254 –dynamicRouting ENABLED –ownerNode 0 -
add ns ip 11.1.1.5 255.255.255.254 –dynamicRouting ENABLED –ownerNode 1 -
add ns ip 11.1.1.9 255.255.255.254 –dynamicRouting ENABLED –ownerNode 1
-
On the Cisco Nexus router (11.1.1.2/31 and 11.1.1.4/31), you must perform the following configurations by using the command line:
feature ospffeature bgpfeature interface-vlan-
feature hsrp> interface vlan100 no shutdown ip address 50.1.1.1/8 hsrp 50 ip 50.50.50.50 > interface Ethernet 4/15 ip address 11.1.1.2/31 no shutdown > interface Ethernet 4/19 ip address 11.1.1.4/31 no shutdown > interface Ethernet 4/22 switchport switchport access vlan 100
On the Cisco Nexus router (11.1.1.6/31 and 11.1.1.8/31), you must perform the following configurations by using the command line:
feature ospffeature bgpfeature interface-vlan-
feature hsrp> interface vlan100 no shutdown no ip redirects ip address 50.1.1.2/8 hsrp 50 ip 50.50.50.50 > interface Ethernet 4/13 ip address 11.1.1.6/31 no shutdown > interface Ethernet 4/15 ip address 11.1.1.8/31 no shutdown > interface Ethernet 4/22 switchport switchport access vlan 100
For the BGP protocol, you must perform the following configurations on CLIP of the NetScaler appliance:
> vtysh
ns# router bgp 1
redistribute kernel
owner-node 0
neighbor 11.1.1.2 remote-as 2
neighbor 11.1.1.2 as-origination-interval 1
neighbor 11.1.1.2 advertisement-interval 0
neighbor 11.1.1.6 remote-as 2
neighbor 11.1.1.6 as-origination-interval 1
neighbor 11.1.1.6 advertisement-interval 0
owner-node 1
neighbor 11.1.1.4 remote-as 2
neighbor 11.1.1.4 as-origination-interval 1
neighbor 11.1.1.4 advertisement-interval 0
neighbor 11.1.1.8 remote-as 2
neighbor 11.1.1.8 as-origination-interval 1
neighbor 11.1.1.8 advertisement-interval 0
exit-owner-node
Perform the following configurations on the Cisco Nexus router (11.1.1.3 and 11.1.1.5)
> ip access-list acl1
10 permit ip 50.0.0.0/8 any
route-map test permit
match ip address acl1
router bgp 2
address-family ipv4 unicast
redistribute direct route-map test
maximum-paths 2
neighbor 11.1.1.3 remote-as 1
address-family ipv4 unicast
neighbor 11.1.1.5 remote-as 1
address-family ipv4 unicast
Perform the following configurations on the Cisco Nexus router (11.1.1.7 and 11.1.1.9)
> ip access-list acl1
10 permit ip 50.0.0.0/8 any
route-map test permit 1
match ip address acl1
router bgp 2
address-family ipv4 unicast
redistribute direct route-map test
maximum-paths 2
neighbor 11.1.1.7 remote-as 1
address-family ipv4 unicast
neighbor 11.1.1.9 remote-as 1
address-family ipv4 unicast
For the OSPF protocol, you must perform the following configurations on CLIP of the NetScaler appliance:
> vtysh
ns# router osfp 1
redistribute kernel
owner-node 0
network 15.1.1.2/31 area 0
network 15.1.1.6/31 area 0
exit-owner-node
owner-node 1
network 15.1.1.4/31 area 0
network 15.1.1.8/31 area 0
exit-owner-node
route-map map2 permit 1
set metric 10
On the Cisco Nexus router (11.1.1.2/31 and 11.1.1.4/31), you must perform the following configurations by using the command line:
> route-map- map2 permit 1
set metric 10
interface Ethernet4/15
ip address 15.1.1.2/31
ip router ospf 1 area 0.0.0.0
no shutdown
interface Ethernet4/19
ip address 15.1.1.4/31
ip router ospf 1 area 0.0.0.0
no shutdown
router ospf 1
router-id 1.1.1.1
redistribute direct route-map map2
On the Cisco Nexus router (11.1.1.7/31 and 11.1.1.9/31), you must perform the following configurations by using the command line:
> route-map- map2 permit 1
set metric 10
interface Ethernet4/13
ip address 15.1.1.6/31
ip router ospf 1 area 0.0.0.0
no shutdown
interface Ethernet4/15
ip address 15.1.1.8/31
ip router ospf 1 area 0.0.0.0
no shutdown
router ospf 1
router-id 1.1.1.2
redistribute direct route-map map2
Share
Share
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.