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!
Memory
Following are some of the best practices to follow when encountered with Web 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 Web 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 Web 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.
Web 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 Web App Firewall memory:
- There is no CLI option to increase Web App Firewall memory. Web 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 Web 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 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.