-
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!
Geneve tunnels
A NetScaler appliance supports the Generic Network Virtualization Encapsulation (Geneve) protocol as defined in RFC 8926. Server virtualization and cloud computing architecture have increased the demand for isolated Layer-2 networks in a data center.
The VLAN limit of 4094 has proven to be inadequate and encapsulation protocols like VXLAN and NVGRE were introduced to overcome this limitation. These protocols differ mainly in the control plane implementation. Geneve protocol does not define specifications for the control plane. The protocol leaves to the implementation to define the control plane specifications.
Geneve protocol is an encapsulation technology that aims to create Layer-2 overlay networks over Layer-3 infrastructure by encapsulating Layer-2 frames in UDP packets.
A unique 24-bit identifier called the VNID identifies each VLAN. Only within the same segment ID (VNID) can communicate with each other. A NetScaler appliance supports the Geneve encapsulation on UDP port 6081.
There are two types of Geneve tunnel that can be created:
-
Tunnels can extend an existing VLAN in L2 or L3 mode. In L2 mode, bridging happens between VLAN and tunnel and the entries are updated in the bridge table.
In L3 mode, proxy ARP comes into effect to learn the MAC address and the tunnel information of the client/server address. The ARP table includes the corresponding MAC and tunnel information.
-
Geneve Tunnel can work with different VLANs in L3 mode by using policy-based routes (PBRs). When a packet must be sent to a host which is reachable on a Geneve Tunnel segment, the NetScaler appliance encapsulates the packet in a Geneve Tunnel header and sends it to the tunnel endpoint.
NetScaler can act as a tunnel endpoint as well. A tunnel endpoint originates and terminates Geneve tunnels. When Layer 2 mode is turned ON, the NetScaler appliance acts as a tunnel endpoint and bridges packets between VLANs and Geneve Tunnels. The NetScaler learns the VNID and tunnel endpoint on which a MAC address is reachable. Then it stores this information in the bridging table.
Geneve tunnel is supported in NetScaler admin partitions, NetScaler high availability setups, and NetScaler cluster setups.
In a high availability setup, a Geneve tunnel configuration is propagated or synchronized to the secondary node. In a cluster setup, the Geneve tunnel configuration (striped) is identical and present on all cluster nodes.
Configuring Geneve tunnels
Configuring a Geneve tunnel on a NetScaler appliance consists of the following tasks:
- Add an IP tunnel with protocol
- Add a net bridge
- bind the geneve tunnel to the net bridge
To add an IP tunnel with Geneve protocol by using the CLI:
At the command prompt, type:
- **add iptunnel** <name> <remote> <remoteSubnetMask> <local> -**protocol** <Geneve> -**destPort** <port> -**tosInherit** (**ENABLED** | **DISABLED**) -**vlanTagging** (**ENABLED** | **DISABLED**) -**vnid** <positive_integer>
- show iptunnel
To add a net bridge by using the CLI:
At the command prompt, type:
- add netbridge <name>
- show netbridge
To bind the geneve tunnel to the netbridge by using the CLI:
At the command prompt, type:
- bind netbridge <name> -vlan <Vlan ID> -tunnel <tunnel name>
- show netbridge
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.