-
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
-
AI capabilities
-
-
-
-
-
-
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
-
-
-
-
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!
AI capabilities
NetScaler® AI capabilities extend the platform’s core application delivery and security functions to address the specific demands of AI workloads. As organizations deploy large language models (LLMs) and AI agents at scale, they face challenges that standard application gateways are not designed to handle, such as token-based traffic patterns, prompt governance, and agent tool access.
NetScaler addresses these challenges through four components:
- AI Gateway manages and governs traffic between applications and LLM backends.
- AI Gateway for Kubernetes extends AI Gateway capabilities into Kubernetes environments using the Gateway API.
- MCP Gateway secures and controls traffic between AI agents and external MCP servers.
- NetScaler Console MCP Server exposes NetScaler operational data to AI agents through MCP.
AI Gateway
AI Gateway acts as a centralized control plane between applications and AI model backends, such as Azure OpenAI and OpenAI. It introduces token awareness into the NetScaler routing and policy engine, understanding prompt size, response volume, and token generation rate, and applies that understanding to load balancing, rate limiting, governance, and observability decisions.
For more information, see AI Gateway.
AI Gateway for Kubernetes
AI Gateway for Kubernetes extends the same token-aware traffic management, governance, and observability capabilities to AI workloads running in Kubernetes environments. It uses the Kubernetes Gateway API, enabling platform and infrastructure teams to govern how applications access large language models through declarative, Kubernetes-native configuration, without modifying application code or building custom integration logic.
Standard Kubernetes ingress and gateway configurations treat all requests as equivalent. AI workloads are not: a single prompt can consume a handful of tokens or hundreds of thousands, making request-count controls an inaccurate proxy for resource usage, cost, or backend load. AI Gateway for Kubernetes addresses this by introducing token awareness into the Kubernetes data plane.
MCP Gateway
Model Context Protocol (MCP) is the protocol used by AI agents to interact with external tools and data sources, such as code repositories, databases, internal APIs, and SaaS platforms. Each MCP server exposes a set of tools that an agent can invoke to complete tasks.
MCP Gateway sits between AI agents and the MCP servers that they connect to, providing a centralized point to enforce access control, apply rate limits, monitor tool usage, and manage authentication. This gives security and infrastructure teams the same level of visibility and control over agent-to-tool traffic that AI Gateway provides over application-to-model traffic.
For more information, see MCP Gateway.
NetScaler Console MCP Server
While AI Gateway and MCP Gateway govern how AI workloads access external models and tools, the NetScaler Console MCP Server operates in the other direction. It makes NetScaler itself consumable by AI agents.
The NetScaler Console MCP Server is a remote MCP server that acts as an adapter between MCP-compatible AI clients and NetScaler Console. It exposes selected NetScaler Console capabilities as structured MCP tools, giving AI agents governed, well-defined access to NetScaler operational data without requiring custom integrations.
For more information, see NetScaler Console MCP Server.
AI Gateway is a rapidly evolving space, and we are continuously expanding our capabilities and integrations. Visit this section regularly for the latest updates and new features.
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.