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
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring 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
Configuring 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
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
Configure a high-availability setup with multiple IP addresses and NICs
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure 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
Configuring authentication, authorization, and auditing policies
Configuring 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
-
-
-
-
-
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 for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
Configuring CloudBridge Connector between Datacenter and AWS Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Virtual Private Gateway on AWS
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Cisco IOS Device
配置一个CloudBridge连接器之间的隧道a Citrix ADC Appliance and Fortinet FortiGate Appliance
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
How to download core or crashed files from Citrix ADC Appliance
How to collect performance statistics and event logs
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!
How to collect performance statistics and event logs
You can collect performance statistics of virtual servers and associated services from an archivednewnslog
file present in the/var/nslog
directory. Thenewnslog
files are interpreted by running/netscaler/nsconmsg
.
Collect performance statistics and event logs using the CLI
You can run thensconmsg
command from the Citrix ADC shell prompt to report events.
At the command prompt, type:
/netscaler/nsconmsg -K /var/nslog/newnslog -d event
Displaying event information NetScaler V20 Performance Data NetScaler NS10.5: Build 57.7.nc, Date: May 14 2015, 07:35:21 rtime: Relative time between two records in milliseconds seqno rtime event-message event-time 11648 16310 PPE-0 MonServiceBinding_10.104.20.110:443_(tcp-default)
View the time span covered by a given “newnslog” file
At the command prompt, type:
/netscaler/nsconmsg -K /var/nslog/newnslog -d setime
The current data is appended to the/var/nslog/newnslog
file. NetScaler archives thenewnslog
file automatically every two days by default. To read the archived data, you must extract the archive as shown in the following example:
cd /var/nslog
- Command to go to a particular directory from NetScaler Shell Prompt.tar xvfz newnslog.100.tar.gz
- Command to extract the tar file./netscaler/nsconmsg -K newnslog.100 -d setime
- Command to check the time span covered by the particular file, in this examplenewnslog.100
.
ls -l
Command checks all the logs file and time stamp associated with those files.
root@NETSCALER# cd /var/nslog
root@NETSCALER# ls -l
wheel 461544 Aug 7 2014 newnslog.1.tar.gz -rw-r--r-- 1 root wheel 191067 Aug 7 2014 newnslog.10.tar.gz -rw-r--r-- 1 root wheel 11144873 Apr 26 22:04 newnslog.100.tar.gz -rw-r--r-- 1 root wheel 11095053 Apr 28 22:04 newnslog.101.tar.gz -rw-r--r-- 1 root wheel 11114284 Apr 30 22:04 newnslog.102.tar.gz -rw-r--r-- 1 root wheel 11146418 May 2 22:04 newnslog.103.tar.gz -rw-r--r-- 1 root wheel 11104227 May 4 22:04 newnslog.104.tar.gz -rw-r--r-- 1 root wheel 11297419 May 6 22:04 newnslog.105.tar.gz -rw-r--r-- 1 root wheel 11081212 May 8 22:04 newnslog.106.tar.gz -rw-r--r-- 1 root wheel 11048542 May 10 22:04 newnslog.107.tar.gz -rw-r--r-- 1 root wheel 11101869 May 12 22:04 newnslog.108.tar.gz -rw-r--r-- 1 root wheel 11378787 May 14 22:04 newnslog.109.tar.gz -rw-r--r-- 1 root wheel 44989298 Apr 11 2014 newnslog.11.gz
Display the time span within a file
Use thensconmsg
command to only display a span of time within the given file, as shown in the following example:
/netscaler/nsconmsg -K /var/nslog/newnslog -s time=22Mar2007:20:00 -T 7 -s ConLb=2 -d oldconmsg
Where,
s
- time=22Mar2007:20:00:00 is start at March 22, 2007 at exactly 20:00.
T 7
- Displays seven seconds of datas
is ConLb=2 is a detail level for load balancing statistics.
d
- Displays statistical information.
Note:
From ADC release 12.1 you need add at the “time” seconds as well, that is: 22Mar2007:20:00:00
The statistical information provided by the-d oldconmsg
parameter is recorded every seven seconds. The following is a sample output.
VIP(10.128.58.149:80:UP:WEIGHTEDRR): Hits(38200495, 18/sec) Mbps(1.02) Pers(OFF) Err(0) Pkt(186/sec, 610 bytes) actSvc(4) DefPol(NONE) override(0) Conn: Clt(253, 1/sec, OE[252]) Svr(3) S(10.128.49.40:80:UP) Hits(9443063, 4/sec, P[2602342, 0/sec]) ATr(5) Mbps(0.23) BWlmt(0 kbits) RspTime(112.58 ms) Other: Pkt(36/sec, 712 bytes) Wt(10000) RHits(31555) Conn: CSvr(42, 0/sec) MCSvr(20) OE(16) RP(11) SQ(0) S(10.128.49.39:80:UP) Hits(9731048, 4/sec, P[2929279, 0/sec]) ATr(9) Mbps(0.27) BWlmt(0 kbits) RspTime(161.69 ms) Other: Pkt(41/sec, 756 bytes) Wt(10000) RHits(31555) Conn: CSvr(32, 0/sec) MCSvr(19) OE(13) RP(4) SQ(0) S(10.128.49.38:80:UP) Hits(9341366, 5/sec, P[2700778, 0/sec]) ATr(4) Mbps(0.27) BWlmt(0 kbits) RspTime(120.50 ms) Other: Pkt(42/sec, 720 bytes) Wt(10000) RHits(31556) Conn: CSvr(37, 0/sec) MCSvr(19) OE(13) RP(9) SQ(0) S(10.128.49.37:80:UP) Hits(9685018, 4/sec, P[2844418, 0/sec]) ATr(3) Mbps(0.23) BWlmt(0 kbits) RspTime(125.38 ms) Other: Pkt(38/sec, 670 bytes) Wt(10000) RHits(31556) Conn: CSvr(32, 0/sec) MCSvr(20) OE(10) RP(7) SQ(0)
Note:
The client connection counts of the individual services do not add up to the client connection count of the virtual server. The reason is because of session reuse between the Citrix ADC appliance and the back-end service.
Virtual Server Output
VIP(10.128.58.149:80:UP:WEIGHTEDRR): Hits(38200495, 18/sec) Mbps(1.02) Pers(OFF) Err(0) Pkt(186/sec, 610 bytes) actSvc(4) DefPol(NONE) override(0) Conn: Clt(253, 1/sec, OE[252]) Svr(3)
The following list describes the virtual server statistics:
- IP (IP address:port:state:Load balancing method). The IP address and port of the Virtual IP address as configured. The virtual server state or virtual IP address is UP, DOWN, or OUT OF SERVICE; Load balancing method configured for the Virtual IP address.
Hits (#)
. Number of requests that reached the virtual server.Mbps (#)
. Total traffic Volume on the virtual server (Rx + Tx) converted into Mbits/sPers
: Type of persistence configured.Err (#)
. Number of times an error page was generated by the virtual server.Pkt (#/sec, # bytes)
: Volume of network traffic (as packets) passing through the virtual server and average packet size flowing through the virtual server.actSvc(#)
. Number of active services that are bound to the virtual server.DefPol (RR)
:指示是否默认负载平衡hod is active. Default load balancing method is used for some number of initial requests to smooth the behavior of the other methods.Clt (#, #/sec)
. Number of current client connections to the virtual server rate.OE [#]
. Number of server connections from the virtual server in open established state.Svr (#)
. Number of current server connections from the virtual server.
In the preceding output,Svr(3)
indicates the command collects he statistical sample. There are three active connections for the virtual server to the back-end server, even though there are four services in total. When a client establishes a connection with the virtual server, it is not necessary that the client sends or receives any traffic when the command collects the information. Therefore, it is common to see theSvr
counter lower than theOE[]
number. TheSvr
counter represents the number of active connections that are actively sending or receiving data. The Mapped IP address (MIP) or Subnet IP address (SNIP) is connected to the associated back-end server. And, the Citrix ADC tracks the virtual server connected to the back-end server and calculates the counter.
Virtual service output
S(10.128.49.40:80:UP) Hits(9443063, 4/sec, P[2602342, 0/sec]) ATr(5) Mbps(0.23) BWlmt(0 kbits) RspTime(112.58 ms) Other: Pkt(36/sec, 712 bytes) Wt(10000) RHits(31555) Conn: CSvr(42, 0/sec) MCSvr(20) OE(16) RP(11) SQ(0)
The following list describes the service statistics:
- S (IP address:port:state): IP address, port, and state of the service such as, DOWN, UP, or OUT OF SERVICE.
- Hits (#, P[#]): Number of requests directed to the service, Number of requests directed to the service due to configured server persistence.
- ATr (#): Number of active connections to the service.
Note:
Active connections are ones which have the outstanding request to the service or currently have traffic activity.
Mbps (#.##)
. Total traffic Volume on the Service (Rx + Tx) converted into Mbits/sBWlmt (# kbits)
: Defined bandwidth limit.RspTime (# ms)
. Average response time of the service in milliseconds.Pkt(#/sec, #bytes)
. Traffic volume in terms of packets per second going to the service; Average size of the packets.Wt (#)
. Weight index, used in load balancing algorithm.
Note:
If you divide this value by 10,000, then you get the actual configured weight of the service.
- RHits (#): Running requests counter used in Round Robin load balancing algorithm.
- CSvr (#, #/sec): Number of connections to the service rate.
- MCSvr (#): Maximum number of connections to the service.
- OE (#): Number of connections to the service in the established state.
- RP (#): Number of connections to the service, residing in the reuse pool.
- SQ (#): Number of connections to the service, waiting in the surge queue.
Collect performance statistics and event logs using the Citrix ADC GUI
- Navigate toSystem > Diagnostics > Maintenance > Delete/Download log files.
- Select a file and clickDownloadto download the file.
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.