-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for installing NetScaler VPX virtual appliances on Linux-KVM platform
-
Provisioning the NetScaler virtual appliance by using OpenStack
-
Provisioning the NetScaler virtual appliance by using the Virtual Machine Manager
-
Configuring NetScaler virtual appliances to use SR-IOV network interface
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
Configuring NetScaler virtual appliances to use PCI Passthrough network interface
-
Provisioning the NetScaler virtual appliance by using the virsh Program
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler 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
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler 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
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
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
-
-
-
-
-
-
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
-
-
-
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!
How to free space on the /var directory
The following article explains how an administrator can free the space from the /var
directory of NetScaler. You can follow the steps when the GUI is not accessible.
When the amount of disk space is low in the /var directory of NetScaler, you might not be able to sign in to the GUI. In this scenario, you can remove the old log files to create free space in the /var
directory.
Important
Make sure to back up the files before deleting them from NetScaler.
Free up disk space in the /var directory on NetScaler
To free space in the /var
directory of NetScaler, complete the following procedure:
- Log on to the CLI of NetScaler by using SSH. For more information to complete this task, see the NetScaler Documentation.
- After you log on to the NetScaler CLI, switch to the shell prompt using the
shell
command. - Check the space available on NetScaler by running the
df -h
command. -
If the memory capacity of the
/var
directory reaches 90%, you must delete some files to free up space.Note:
Before performing an upgrade, make sure that there is enough available space in the
/var
directory. The/var
directory requires 7 GB of free space: 1 GB for the upgrade bundle, 2 GB for extraction, and 4 GB for the upgrade process. -
View the contents of the
/var
directory by running thels -l /var
command.The directories that are usually of interest are as follows:
- /var/nstrace - This directory contains trace files. This is the most common reason for HDD being filled on NetScaler. This is due to a nstrace being left running for an indefinite amount of time. Delete all traces that are not required. To stop an nstrace, run
stop nstrace
command from the CLI. - /var/log - This directory contains system specific log files.
- /var/nslog - This directory contains NetScaler log files.
- /var/tmp/support - This directory contains technical support files, also known as, support bundles. All files not of interest should be deleted.
- /var/core - Core dumps are stored in this directory. There will be directories within this directory and they will be labeled with numbers starting with 1. These files can be quite large in size. Clear all files unless the core dumps are recent and investigation is required.
- /var/crash - Crash files, such as process crashes are stored in this directory. Clear all files unless the crashes are recent and investigation is required.
- /var/nsinstall - Firmware is placed in this directory when upgrading. Clear all files, except the firmware that is currently being used.
- /var/nstrace - This directory contains trace files. This is the most common reason for HDD being filled on NetScaler. This is due to a nstrace being left running for an indefinite amount of time. Delete all traces that are not required. To stop an nstrace, run
-
Check the memory usage of different files and directories within the
/var
directory by running thedu -hs /var/*
command.du -hs * 44k cache 2.0k clusterd 2.0k configdb 6.0k core 989M crash 4.0k cron 2.0k dev 6.0k download 2.0k gui 2.0k install 2.0k krb 2.0k learnt_data 122M log 366M NetScaler 14k ns_gui 86k ns_sys_backup 631M nsinstall 883M nslog 32k nsproflog 2.0k nssynclog 16k nstemplates 36k nstmp 4.5G nstrace 8.1M opt 6.0k pubkey 52k run 28M safenet 72M tmp 2.0k vmtools 14k vpn
-
Delete or compress any unnecessary files or those using excessive memory.
-
In the preceding example,
nstrace
directory is taking up more space. If it is not required, delete the files in this directory by running the following command:rm -r nstrace/*
.For more help on deleting files, see the FreeBSD documentation.
- If the
log
ornslog
directory is using more space.-
View the contents of the
log
ornslog
directories by running the following commands:cd /var/log ls -l cd /var/nslog ls -l <!--NeedCopy-->
-
Compress all the files. The
.tar.gz
file name extension indicates that the file is both archived and compressed.If the file is not already compressed, you must compress them.
To compress the file to .gz format:
cd /var/log gzip <filename> <!--NeedCopy-->
The compressed file is placed at the
/var/log
directory.To compress the file to .tar.gz format:
cd /var/nslog tar -cz <filename>.tar.gz <filename> <!--NeedCopy-->
The compressed file is placed at the
/var/nslog
directory.
-
- If you are using NetScaler Console, verify the
/var/ns_system_backup
directory. Ensure that NetScaler Console clears the backup files it creates.
-
More resources
For information on any of the commands mentioned in the preceding procedure, see Linux commands.
Share
Share
In this article
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.