Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
有限公司nfiguring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
有限公司nfiguring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
有限公司nfiguring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
有限公司nfigure multiple IP addresses for a Citrix ADC VPX standalone instance
有限公司nfigure a high-availability setup with multiple IP addresses and NICs
有限公司nfigure HA-INC nodes by using the Citrix high availability template with Azure ILB
有限公司nfigure GSLB on an ctive-standby high availability setup
有限公司nfigure address pools (IIP) for a Citrix Gateway appliance
Upgrade and downgrade a Citrix ADC appliance
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
有限公司nfiguring authentication, authorization, and auditing policies
有限公司nfiguring Authentication, authorization, and auditing with commonly used protocols
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
AppFlow
-
-
-
-
-
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
有限公司nfigure automatic state transition based on percentage health of bound services
使用case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
使用case 3: Configure load balancing in direct server return mode
使用case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
使用case 7: Configure load balancing in DSR mode by using IP Over IP
使用case 10: Load balancing of intrusion detection system servers
使用case 12: Configure Citrix Virtual Desktops for load balancing
使用case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization
-
有限公司nfiguring a CloudBridge Connector Tunnel between two Datacenters
有限公司nfiguring CloudBridge Connector between Datacenter and AWS Cloud
有限公司nfiguring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
有限公司nfiguring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
有限公司nfiguring a CloudBridge Connector Tunnel Between a Citrix ADC 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!
AppFlow
The Citrix ADC appliance is a central point of control for all application traffic in the data center. It collects flow and user-session level information valuable for application performance monitoring, analytics, and business intelligence applications. It also collects webpage performance data and database information. AppFlow transmits the information by using the Internet Protocol Flow Information eXport (IPFIX) format, which is an open Internet Engineering Task Force (IETF) standard defined in RFC 5101. IPFIX (the standardized version of Cisco’s NetFlow) is widely used to monitor network flow information. AppFlow defines new Information Elements to represent application-level information, webpage performance data, and database information.
Using UDP as the transport protocol, AppFlow transmits the collected data, calledflow records, to one or more IPv4 collectors. The collectors aggregate the flow records and generate real-time or historical reports.
AppFlow provides visibility at the transaction level for HTTP, SSL, TCP, SSL_TCP flows, and HDX Insight flows. You can sample and filter the flow types that you want to monitor.
Note
For more information on HDX Insight, seeHDX Insight.
演示applow f使用行动和政策来发送记录or a selected flow to specific set of collectors. An AppFlow action specifies which set of collectors receive the AppFlow records. Policies, which are based on Advanced expressions can be configured to select flows for which flow records are sent to the collectors specified by the associated AppFlow action.
To limit the types of flows, you can enable AppFlow for a virtual server. AppFlow can also provide statistics for the virtual server.
You can also enable AppFlow for a specific service, representing an application server, and monitor the traffic to that application server.
Note: This feature is supported only on Citrix ADC nCore builds.
How AppFlow Works
In the most common deployment scenario, inbound traffic flows to a Virtual IP address (VIP) on the Citrix ADC appliance and is load balanced to a server. Outbound traffic flows from the server to a mapped or subnet IP address on the Citrix ADC and from the VIP to the client. A flow is a unidirectional collection of IP packets identified by the following five tuples: sourceIP, sourcePort, destIP, destPort, and protocol.
The following figure describes how the AppFlow feature works.
Figure 1. Citrix ADC Flow Sequence
As shown in the figure, the network flow identifiers for each leg of a transaction depend on the direction of the traffic.
The different flows that form a flow record are:
Flow1:Client-IP, Client-Port, VIP-IP, VIP-port, Protocol
Flow2:NS-SNIP, NS-port, Server-IP, Server-Port, Protocol
Flow3:Server-IP, Server-Port, NS-SNIP, NS-Port, Protocol
Flow4:VIP-IP, VIP-port, Client-IP, Client-Port, Protocol
To help the collector link all four flows in a transaction, AppFlow adds a custom transactionID element to each flow. For application-level content switching, such as HTTP, it is possible for a single client TCP connection to be load balanced to different back end TCP connections for each request. AppFlow provides a set of records for each transaction.
Flow Records
AppFlow records contain standard NetFlow or IPFIX information, such as time stamps for the beginning and end of a flow, packet count, and byte count. AppFlow records also contain application-level information (such as HTTP URLs, HTTP request methods and response status codes, server response time, and latency). Webpage performance data (such as page load time, page render time, and time spent on the page). And database information (such as database protocol, database response status, and database response size). IPFIX flow records are based on templates that need to be sent before sending flow records.
Templates
AppFlow defines a set of templates, one for each type of flow. Each template contains a set of standard Information Elements (IEs) and Enterprise-specific Information Elements (EIEs). IPFIX templates define the order and sizes of the Information Elements (Internet Explorer) in the flow record. The templates are sent to the collectors at regular intervals, as described in RFC 5101.
A template can include the following EIEs:
transactionID
一个联合国signed 32-bit number identifying an application-level transaction. For HTTP, it corresponds to a request and response pair. All flow records that correspond to this request and response pair have the same transaction ID. In the most common case, there are four uniflow records that correspond to this transaction. If the Citrix ADC generates the response by itself (served from the integrated cache or by a security policy), there might be only two flow records for this transaction.
connectionID
一个联合国signed 32-bit number identifying a layer-4 connection (TCP or UDP). The Citrix ADC flows are bidirectional, with two separate flow records for each direction of the flow. This information element can be used to link the two flows.
For the Citrix ADC, a connectionID is an identifier for the connection data structure to track the progress of a connection. In an HTTP transaction, for instance, a given connectionID might have multiple transactionID elements corresponding to multiple requests that were made on that connection.
tcpRTT
The round trip time, in milliseconds, as measured on the TCP connection. It can be used as a metric to determine the client or server latency on the network.
httpRequestMethod
An 8-bit number indicating the HTTP method used in the transaction. An options template with the number-to-method mapping is sent along with the template.
httpRequestSize
一个联合国signed 32-bit number indicating the request payload size.
httpRequestURL
The HTTP URL requested by the client.
httpUserAgent
The source of incoming requests to the Web server.
httpResponseStatus
一个联合国signed 32-bit number indicating the response status code.
httpResponseSize
一个联合国signed 32-bit number indicating the response size.
httpResponseTimeToFirstByte
一个联合国signed 32-bit number indicating the time taken to receive the first byte of the response.
httpResponseTimeToLastByte
一个联合国signed 32-bit number indicating the time taken to receive the last byte of the response.
flowFlags
一个联合国signed 64-bit flag used to indicate different flow conditions.
EIEs for webpage performance data
clientInteractionStartTime
Time at which the browser receives the first byte of the response to load any objects of the page such as images, scripts, and style sheets.
clientInteractionEndTime
Time at which the browser received the last byte of response to load all the objects of the page such as images, scripts, and style sheets.
clientRenderStartTime
Time at which the browser starts to render the page.
clientRenderEndTime
Time at which a browser finished rendering the entire page, including the embedded objects.
EIEs for database information
dbProtocolName
一个联合国signed 8-bit number indicating the database protocol. Valid values are 1 for MS SQL and 2 for MySQL.
dbReqType
一个联合国signed 8-bit number indicating the database request method used in the transaction. For MS SQL, valid values are 1 is for QUERY, 2 is for TRANSACTION, and 3 is for RPC. For valid values for MySQL, see the MySQL documentation.
dbReqString
Indicates the database request string without the header.
dbRespStatus
一个联合国signed 64-bit number indicating the status of the database response received from the web server.
dbRespLength
一个联合国signed 64-bit number indicating the response size.
dbRespStatString
The response status string received from the web server.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.