Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
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 AWS
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
Configure a Citrix ADC VPX instance to use SR-IOV network interface
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
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 a Citrix ADC VPX instance to use Azure accelerated networking
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure a high-availability setup with Azure external and internal load balancers simultaneously
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
-
-
-
-
-
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 14: ShareFile wizard for load balancing Citrix ShareFile
Use case 15: Configure layer 4 load balancing on the Citrix ADC 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 Citrix ADC Appliance and Cisco IOS Device
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
Synchronizing Configuration Files in a High Availability Setup
Restricting High-Availability Synchronization Traffic to a VLAN
Understanding the High Availability Health Check Computation
Managing High Availability Heartbeat Messages on a Citrix ADC Appliance
Remove and Replace a Citrix ADC in a High Availability Setup
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)
此内容已动态机器翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
How to configure log file rotation
The Citrix ADC appliance generates logs in multiple directories and in various formats. Some of these logs are not rotated by default and can grow in size consuming too much disk space. By using the included utilities for log rotation (newsyslog
), you can manage these logs consistently, by keeping only relevant information for easier management and administration.
Thenewsyslog
utility included in the Citrix ADC firmware archives log files and rotates the system logs so the current log is empty during rotation. The system crontab runs this utility every hour and it reads the configuration file which specifies the files to rotate and the conditions. The archived files might be compressed if necessary.
The existing configuration is located in/etc/newsyslog.conf
. However, because this file resides in the memory filesystem, the administrator must save the modifications to/nsconfig/newsyslog.conf
so the configuration survives restarting the NetScaler.
The entries contained in this file have the following format:logfilename [owner:group] mode count size when flags [/pid_file] [sig_num]
Note:
Fields within squared brackets are optional and can be omitted.
Each line on the file represents a log file and the conditions under which rotation must occur.
In the example, thesize
field indicates that the size ofns.log
as 100 Kilobytes. Thecount
field indicates that the number of archivedns.log
files as 25. A size of 100 K and count of 25 are the default size and count values.
Note:
When the field is configured with an asterisk ( * ), meaning that the ns.log file is not rotated based on time. Every hour, a crontab job runs the
newsyslog
utility which checks if the size of ns.log is greater than or equal to the size configured in this file. In this example, if it is greater than or equal to 100 K, it rotates that file.
root@ns #猫/etc/newsyslog.conf # Netscaler报童slog.conf # This file is present in the memory filesystem by default, and any changes # to this file will be lost following a reboot. If changes to this file # require persistence between reboots, copy this file to the /nsconfig # directory and make the required changes to that file. # # logfilename [owner:group] mode count size when flags [/pid_file] [sig_num] /var/log/cron 600 3 100 * Z /var/log/amd.log 644 7 100 * Z /var/log/auth.log 600 7 100 * Z /var/log/ns.log 600 25 100 * Z
Thesize
field can be changed to modify the minimum size of thens.log
file or the field can be changed to rotate thens.log
file based on a certain time.
The daily, weekly, and/or monthly specification is given as:[Dhh]
, and[Dhh [Mdd]]
, respectively. The time-of-day fields, which are optional, default to midnight. The ranges and meanings for these specifications are:
Hh hours, range 0 ... 23 w day of week, range 0 ... 6, 0 = Sunday dd day of month, range 1 ... 31, or the letter L or l to specify the last day of the month.
Examples:
Here are some examples with explanations for the logs that are rotated by default:
/var/log/auth.log 600 7 100 * Z
The authentication log is rotated when the file reaches 100 K, the last 7 copies of the auth.log are archived and compressed with gzip (Z flag), and the resulting archives are assigned the following permissions –rw——-.
/var/log/all.log 600 7 * @T00 Z
The catch-all log is rotated 7 times at midnight every night (@T00) and compressed with gzip. The resulting archives are assigned the following permissions –rw-r—–.
/var/log/weekly.log 640 5 * $W6D0 Z
The weekly log is rotated 5 times at midnight every Monday. The resulting archives are assigned with permissions.
Common Rotation Patterns:
D0
. rotate every night at midnightD23
. rotate every day at 23:00W0D23
. rotate every week on Sunday at 23:00W5
. rotate every week on Friday at midnightMLD6
. rotate at the last day of every month at 6:00M5
. rotate on every fifth day of the month at midnight
If an interval and a time specification are both given, then both conditions must be met. That is, the file must be as old as or older than the specified interval and the current time must match the time specification.
You can control the minimum file size but there is no limit on the file size before thenewsyslog
utility gets its turn in the next hour slot.
Debug newsyslog:
To debug the behavior of thenewsyslog
utility, add the verbose flag.
root@dj_ns# newsyslog -v /var/log/cron <3Z>: size (Kb): 31 [100] --> skipping /var/log/amd.log <7Z>: does not exist, skipped. /var/log/auth.log <7Z>: size (Kb): 2 [100] --> skipping /var/log/kerberos.log <7Z>: does not exist, skipped. /var/log/lpd-errs <7Z>: size (Kb): 0 [100] --> skipping /var/log/maillog <7Z>: --> will trim at Tue Mar 24 00:00:00 2009 /var/log/sendmail.st <10>: age (hr): 0 [168] --> skipping /var/log/messages <5Z>: size (Kb): 7 [100] --> skipping /var/log/all.log <7Z>: --> will trim at Tue Mar 24 00:00:00 2009 /var/log/slip.log <3Z>: size (Kb): 0 [100] --> skipping /var/log/ppp.log <3Z>: does not exist, skipped. /var/log/security <10Z>: size (Kb): 0 [100] --> skipping /var/log/wtmp <3>: --> will trim at Wed Apr 1 04:00:00 2009 /var/log/daily.log <7Z>: does not exist, skipped. /var/log/weekly.log <5Z>: does not exist, skipped. /var/log/monthly.log <12Z>: does not exist, skipped. /var/log/console.log <5Z>: does not exist, skipped. /var/log/ns.log <5Z>: size (Kb): 18 [100] --> skipping /var/log/nsvpn.log <5Z>: size (Kb): 0 [100] --> skipping /var/log/httperror.log <5Z>: size (Kb): 1 [100] --> skipping /var/log/httpaccess.log <5Z>: size (Kb): 1 [100] --> skipping root@dj_ns#
Share
Share
In this article
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.