-
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
-
-
Upgrade and downgrade a NetScaler appliance
-
Upgrade considerations for configurations with classic policies
-
Upgrade considerations for customized configuration files
-
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!
Upgrade considerations for customized configuration files in the /etc directory
The following configuration files are supported to be modified in the /etc
directory:
inetd.conf
syslog.conf
newsyslog.conf
ntp.conf
crontab
host.conf
hosts
ttys
sshd_config
httpd.conf
monitrc
rc.conf
ssh_config
localtime
issue
issue.net
ldap.conf
motd
Note:
New files might be added to the above list depending on the NetScaler build running on the appliance. You can display an updated list of files by running the following shell command in the NetScaler command line interface:
grep NSETC= /etc/rc
If you have modified any of the configuration files in the /etc
directory and copied it to the /nsconfig
directory, to maintain persistency, the NetScaler appliance creates a symlink in /etc
pointing to the file in /nsconfig
.
For example: /etc/httpd.conf -> /nsconfig/httpd.conf
A release package might contain its own version of the configuration files in the /etc
directory. These configuration files include important updates that are required for the NetScaler appliance to properly function. Upgrading a NetScaler appliance to a release replaces the configuration files in the /etc
directory with the configuration files containing the release updates.
Consider an example of a customized configuration file, example.conf
, which is present in the /etc
directory. The example.conf
file is copied to the /nsconfig
directory to maintain persistency. The NetScaler appliance creates a symlink in /etc
pointing to the file in /nsconfig
: /etc/example.conf -> /nsconfig/example.conf
Also, a release package includes its own version of example.conf
, which contains important updates. The following behavior is observed when you upgrade the NetScaler appliance to the release:
Because the symlink /etc/example.conf
is already present, the NetScaler appliance does not place the release package copy of the example.conf
in the /etc
directory during the upgrade process.
As the release package copy of example.conf
contains important updates, the absence of it in the /etc
directory can cause the NetScaler appliance to fail or to not properly function.
Steps to preserve upgrade changes and customization
To ensure that both release updates and your customizations are not lost, perform the following steps:
- Pre-upgrade steps:
- Post-upgrade steps:
-
Apply customizations to upgraded file and add persistency after upgrade
Important:
Do NOT directly replace your customized file in the
/etc
folder. Directly replacing a/etc
file with the back-up customized file removes any release updates added to the file during the upgrade process.
-
Back up customized file before upgrade
Take a backup of the customized files present in the /nsconfig
directory before upgrading the appliance.
Create a /var/nsconfig_backup
directory and move the customized files to this directory. That is, move any files that you modified in the /etc
directory and copied to /nsconfig
by running the following command at the shell prompt:
mv /nsconfig/<filename> /var/nsconfig_backup/
Example:
mv /nsconfig/httpd.conf /var/nsconfig_backup/
Remove persistency of customized file before upgrade
Delete the /etc
symlinks that are pointing to the /nsconfig
files before upgrading the appliance.
-
Check the existing symlinks in the
/etc
directory by running the following command at the shell prompt:ls -la /etc
-
Delete a
/etc
symlink pointing to a/nsconfig
file by running the following command at the shell prompt:unlink /etc/<filename>
Example:
unlink /etc/httpd.conf
-
Verify that the symlink is removed by running the following command at the shell prompt:
cat /etc/<filename>
Example:
cat /etc/httpd.conf
This command does not display any content if the symlink is removed.
Apply customizations to upgraded file and add persistency after upgrade
If you have taken a backup of any modified /nsconfig
config file to the /var/nsconfig_backup
, do the following after upgrading the appliance:
-
Compare the file present in the
/var/nsconfig_backup
and the/etc
directories. Manually add the appropriate changes to the/etc
file already containing the release updates.Important:
Directly replacing the
/etc
file with the/var/nsconfig_backup
file removes any release updates added to the file during the upgrade process. This removal of updates can cause the related NetScaler functionalities to fail or to not work properly. -
To maintain persistency, copy the updated file present in the
/etc
directory to the/nsconfig
directory by running the following command at the shell prompt:cp /etc/<filename> /nsconfig/
Example:
cp /etc/httpd.conf /nsconfig/
-
Repeat the above two steps for each customized file present in the
/var/nsconfig_backup
directory. -
Restart the appliance to put the changes into effect.
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.