-
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
-
-
-
-
Add a location file to create a static proximity database
-
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
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!
Add a location file to create a static proximity database
A static proximity database is a UNIX-based ASCII file. Entries added to this database from a location file are called static entries. Only one location file can be loaded on a NetScaler appliance. Adding a new location file overrides the existing file. The number of entries in the static proximity database is limited by the configured memory in the NetScaler appliance.
The static proximity database can be created in the default format or in a format derived from commercially configured third party databases (such as www.maxmind.com
and www.ip2location.com
).
The NetScaler appliance includes the following two IP geolocation database files. These are GeoLite2 files, published by MaxMind.
- Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4
- Citrix_Netscaler_InBuilt_GeoIP_DB_IPv6
These database files are available in a format supported by the NetScaler appliance in the directory /var/netscaler/inbuilt_db.
You can use these IP geolocation databases as the location file for the static proximity based GSLB method, or in location based policies.
These databases vary in the details that they provide. There is no strict enforcement of the database file format, except that the default file has format tags. The database files are ASCII files that use a comma as the field delimiter. There are differences in the structure of fields and the representation of IP addresses in the locations.
The format parameter describes the structure of the file to the NetScaler appliance. Specifying an incorrect value for the format option can corrupt the internal data.
Notes:
- After an upgrade, if the /var/netscaler/inbuilt_db/ directory contains the database file (Citrix_Netscaler_InBuilt_GeoIP_DB.csv) from the earlier NetScaler software versions, the file is retained.
- The default location of the database file is /var/netscaler/locdb, and on a high availability (HA) setup, an identical copy of the file must be present in the same location on both NetScaler appliances.
- If the location file is stored in a location other than the default location, then specify the path of the location file.
- For admin partitions, the default path is: /var/partitions/
<partitionName>
/netscaler/locdb.- Some databases provide short country names according to ISO-3166 and long country names as well. The NetScaler uses short names when storing and matching qualifiers.
- To create a static proximity database, log on to the UNIX shell of the NetScaler appliance and use an editor to create a file with the location details in one of the NetScaler supported formats.
- NetScaler appliance is shipped with the GeoLite2 database (IPv4 and IPv6) but NetScaler does not maintain or update the MaxMind GeoLite2 database regularly. If necessary, you can get the GeoLite2 database from https://www.maxmind.com and convert it to NetScaler database format. For more information, see Script to convert MaxMind GeoLite2 database format to NetScaler database format.
To add a static location file by using the CLI
At the command prompt, type:
add locationFile <locationFile> [-format <format>]
- show locationFile
<!--NeedCopy-->
Example:
add locationFile /var/netscaler/locdb/nsgeo1.0 -format netscaler
Done
show locationFile
Location File: /var/netscaler/locdb/nsgeo1.0
Format: netscaler
Done
>
<!--NeedCopy-->
Example:
add locationFile /var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv4 -format netscaler
add locationFile6 /var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB_IPv6 -format netscaler
<!--NeedCopy-->
To add a static location file by using the GUI:
- Navigate to AppExpert > Location, click the Static Database tab.
- Click Add to add a static location file.
You can view an imported location file database by using the View Database dialog box in the configuration utility. There is no CLI equivalent.
To view a static location file by using the GUI:
- Navigate to AppExpert > Location, click the Static Database tab.
- Select a static location file, and from the Action list, click View Database.
To convert a location file into the NetScaler format:
By default, when you add a location file, it is saved in the NetScaler format. You can convert a location file of other formats into the NetScaler format.
Note:
The
nsmap
option can be accessed only from the command line interface. The conversion is possible only into the NetScaler format.
To convert the static database format, at the CLI prompt, type the following command:
nsmap -f <inputFileFormat> -o <outputFileName> <inputFileName>
<!--NeedCopy-->
Example:
nsmap -f ip-country-region-city -o nsfile.ns ip-country-region-city.csv
<!--NeedCopy-->
Script to convert MaxMind GeoLite2 database format to NetScaler database format
MaxMind GeoIP database cannot be used directly in NetScaler. The MaxMind GeoIP database must be converted into NetScaler format and then loaded for IP location detection in the GSLB static proximity method and other features like policies. You can use a script to convert the GeoLite2 database format to NetScaler database format. This script can be used to convert both IPv4 and IPv6 files. The script is available in the location: https://github.com/citrix/MaxMind-GeoIP-Database-Conversion-Citrix-ADC-Format
Steps to convert GeoIP2 database to NetScaler format
-
Download the GeoLite2 City or GeoLite2 Country database in .csv format from https://dev.maxmind.com/geoip/geoip2/geolite2/.
-
Copy the file in a NetScaler directory (say /var). Unzip the file using the following shell command, which would create a directory with the same name.
tar -xf <filename>
-
Download the script Convert_GeoIPDB_To_Netscaler_Format.pl from https://github.com/citrix/MaxMind-GeoIP-Database-Conversion-Citrix-ADC-Format and copy it to the directory created in step #2.
-
To check the acceptable options for the script execution, run the following command:
perl Convert_GeoIPDB_To_Netscaler_Format.pl –help
Various options available are:
-
<filename>
IPv4 output file. Default output file name: Netscaler_Maxmind_GeoIP_DB_IPv4.csv -
-p <filename>
IPv6 output file. Default output file name: Netscaler_Maxmind_GeoIP_DB_IPv6.csv -
-logfile <filename>
File containing list of events/messages -
-debug
Prints all the messages to STDOUT
-
-
Run the following command to convert the GeoLite2 database format to NetScaler database format.
perl Convert_GeoIPDB_To_Netscaler_Format.pl
Note:
The operation can take up to 5 minutes.
The default file names used in the script are that of the MaxMind GeoLite2 City based database. If you have downloaded the GeoLite2 Country database, you must provide the input file names accordingly as listed.
-
-b <filename>
name of IPv4 block file to be converted. Default file name: GeoLite2-City-Blocks-IPv4.csv -
-i <filename>
name of IPv6 block file to be converted. Default file name: GeoLite2-City-Blocks-IPv6.csv -
-l <filename>
name of location file to be converted. Default file name: GeoLite2-City-Locations-en.csv
Example:
perl Convert_GeoIPDB_To_Netscaler_Format.pl -b GeoLite2-City-Blocks-IPv4.csv -i GeoLite2-City-Blocks-IPv6.csv -l GeoLite2-City-Locations-en.csv <!--NeedCopy-->
The following are the output files generated after running the script.
- Netscaler_Maxmind_GeoIP_DB_IPv4.csv
- Netscaler_Maxmind_GeoIP_DB_IPv6.csv
-
-
Once the conversion of the database into NetScaler format is complete, use the following command to start using it.
add locationFile <locationFile>
Add a third-party static database file on a NetScaler appliance
Perform the following steps to add a third-party static database file on a NetScaler appliance.
-
Obtain the location database file from a third-party vendor, such as
www.maxmind.com
.Note:
If you download the location database file from
www.maxmind.com
, you can use the readily available script to convert it into NetScaler database format. For information on using the script, see Script to convert MaxMind GeoLite2 database format to NetScaler database format.For location databases downloaded from other third-party vendors, you must convert them to NetScaler database format before adding them to a NetScaler appliance.
-
Run the following command to add a static location file:
add location file <locationfile Name> <!--NeedCopy-->
Note:
- If the location database file is not placed in the default /var/netscaler/locdb location, then the
<locationfile Name>
must contain the location of the file along with the file name. - Before you run the
add location file <locationfile Name>
command:- Make sure that the location database file is present in one of the directories of the NetScaler appliance.
- Run the
sync HA files
command on the high availability setup and thesync cluster files
command in a cluster setup. These commands ensure that the location database file is copied to the secondary appliance of the high availability pair and peer nodes of the cluster.
- If the location database file is not placed in the default /var/netscaler/locdb location, then the
-
Run the following command to ensure that the location database is loaded:
show locationParameter <!--NeedCopy-->
This command displays location parameters related to static proximity-based load balancing. A maximum of 3M-1 (3 million minus one) entries can be loaded. When the database loading is in progress, the command displays
Loading: In progress
. After the loading is completed, the command displaysLoading: Idle
. -
Run the following command to view the location of the GSLB site:
show gslb service <!--NeedCopy-->
Note
- If the database is loaded correctly, the location of the GSLB sites is automatically populated in the database.
- You can specify only one location file in the configuration on the appliance.
- If no match is found for an incoming IP address, the request is processed using the Round Robin method.
-
Run the following command to configure the GSLB method on the appliance:
set gslb vserver GSLBVserverName -lbMethod MethodType <!--NeedCopy-->
Share
Share
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.