-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a Citrix 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
-
Configuring NetScaler Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the NetScaler Virtual Appliance by using the virsh Program
-
-
Deploying NetScaler VPX Instances on AWS
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
-
-
Adding a Location File to Create a Static Proximity Database
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
-
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
-
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
-
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
-
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
-
Use source IP address of the client when connecting to the server
-
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
-
-
-
-
-
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 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.
Note
- After an upgrade, if the /var/netscaler/inbuilt_db/ directory contains the da tabase file (Citrix_Netscaler_InBuilt_GeoIP_DB.csv) from the earlierNetScaler 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.
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/nsmap/locdb/nsgeo1.0 -format netscaler
Done
show locationFile
Location File: /var/nsmap/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-->
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 or www.ip2location.com.
-
Copy the location database file to the NetScaler appliance using the WinSCP utility.
Note
The default location of the database file on the appliance is /var/netscaler/locdb.
-
Execute the following command to add a static location file:
add location file <locationfile Name> -format LocationFormat <!--NeedCopy-->
-
Execute the following command to ensure that the location database is loaded:
show location parameter <!--NeedCopy-->
This command displays the parameters, such as number of static entries. If the database is not loaded correctly, this command also displays an error message. A maximum of 3M-1 (3 million minus one) entries can be loaded.
-
Execute 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 the appliances are in a high availability setup, then one appliance must copy the database from the other appliance.
- If no match is found for an incoming IP address, the request is processed using the Round Robin method.
-
Execute 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 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.