-
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
-
-
-
-
-
-
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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
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!
Memory
Following are some of the best practices to follow when encountered with App Firewall usage memory related issues:
nsconmsg command usage:
• Look for global memory statistics to ascertain that there is enough memory in the system and there are no memory allocation failures by executing the following command:
* *- nsconmsg -d memstats
• Observe current allocated and maximum memory limits for appsecure, IP reputation, cache and compression by executing the following command:
- nsconmsg -d memstats | egrep -i APPSECURE|IPREP|CACHE|CMP
• Check appfw, DHT, IP reputation activity counters by executing the following command:
- nsconmsg -g as -g appfwreq_ -g iprep -d current
• Check all App Firewall error counters by executing the following command:
- nsconmsg -g as_ -g appfwreq_ -g iprep_ -d stats | grep err
• Check all system error counters by executing the following command:
- nsconmsg -g err -d current
• Inspect for CPU, APPFWREQ, AS and DHT counters by executing the following command:
nsconmsg -g cc_cpu_use -g appfwreq -g as -g dht -d current
• Check the configured Cache memory by executing the following command:
show cacheparameter
• Check the configured memory by executing the following command:
nsconmsg -d memstats | egrep -i CACHE
• Identify distribution of memory in App Firewall components and objects:
Display AS_OBJ_ memory:
nsconmsg -K newnslog -d stats | grep AS_OBJ | egrep -v AppFW_cpu0|total | sort -k3
Display AS_COMPONENT_ memory:
nsconmsg -K newnslog -d stats | grep AS_COMPONENT | egrep -v AppFW_cpu0|total | sort –k3
• Check for number of alive sessions by executing the following command:
Monitor/plot active session counts:
nsconmsg -g as_alive_sessions -d current
Monitor/plot total allocated, free, updated sessions:
-
nsconmsg -g as_tot_alloc_sessions -g as_tot_free_sessions -d current
-
nsconmsg -g as_tot_update_sessions -d current
If required, reduce session timeout to ensure that session limits are not used by executing the following command:
- set appfwsettings -sessionTimeout <300>
If required, set maximum lifetime of session by executing the following command:
- set appfwsettings -sessionLifetime <7200>
Checking allocated and used memory
To check the total allocated memory and used memory:
- Use the nsconmsg –d memstats command. Observe the MEM_APPSECURE field.
- Use the stat appfw command to obtain meory consumption information.
App Firewall does not automatically delete the logs after certain period of time or size.
-
All AppFw logs are archived in the */var/log/ns.log*
file. The ns.log file performs the rollover task.
For more information, refer to the following link: <http://support.citrix.com/article/CTX121898>
Increasing App Firewall memory:
- There is no CLI option to increase App Firewall memory. App Firewall memory is platform-specific.
- You may use the nsapimgr option to increase memory but it is not recommended.
The max allowed memory for App Firewall is determined by the platform and disabling IC does not impact memory allocation.
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.