-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
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!
Configure system settings
Before you start using Citrix ADM to manage and monitor your instances and applications, it is recommended that you configure a few system settings that will ensure optimal performance of your Citrix ADM server.
Configure system alarms
You should configure system alarms to make sure you are aware of any critical or major system issues. For example, you might want to be notified if the CPU usage is high or if there are multiple login failures to the server. For some alarm categories, such as cpuUsageHigh or memoryUsageHigh, you can set thresholds and define the severity (such as Critical or Major) for each. For some categories, such as inventoryFailed or loginFailure, you can define only the severity. When the threshold is breached for an alarm category (for example, memoryUsageHigh) or when an event occurs corresponding to the alarm category (for example, loginFailure), a message is recorded in the system and you can view the message as syslog message.
To configure system alarms:
-
Navigate to System > Alarms, select the alarm you want to configure, and click Edit.
-
On the Configure Alarm page, select the alarm severity, and set the Threshold.
-
To view the alarms that have breached the threshold or for which an event has occurred, navigate to System > Auditing and click Syslog Messages.
Configure system notifications
You can send notifications to select groups of users for a number of system-related functions. You can set up a notification server in Citrix ADM, and you can configure email and Short Message Service (SMS) gateway servers to send email and text notifications to users. This ensures that you are notified of any system-level activities such as user login or system restart.
To configure system notifications:
-
Navigate to System > Notifications. Under Settings, click Change Notification Settings.
-
On the Configure System Notification Settings page, select the category or category of events generated by Citrix ADM.
-
Then, configure either the email server or the SMS server to receive notification through email or SMS or both.
Configure system prune settings
To limit the amount of reporting data being stored in your Citrix ADM server’s database, you can specify the interval for which you want Citrix ADM to retain network reporting data, events, audit logs, and task logs. By default, this data is pruned every 24 hours (at 00.00 hours).
To configure system prune setting:
-
Navigate to System > System Administration. Under Prune Settings, click System Prune Settings.
-
In the Configure System Prune Settings page, specify the number of days for which to retain data, and click OK.
Configure system backup settings
Citrix ADM automatically backs up the system everyday at 00:30 hours. By default, it saves three backup files. You might want to retain more number of backups of the system. You can also encrypt the backup file. You can also choose to save the backup on an external server.
To configure system backup settings:
-
Navigate to System > System Administration.
-
Under Backup Settings, click System Backup Settings.
-
On the Confgure System Backup Settings page, specify the required values.
Configure instance backup settings
If you back up the current state of a Citrix ADC instance, you can use the backup files to restore stability in the event that the instance becomes unstable. Doing so is especially important before performing an upgrade. By default, a backup is taken every 12 hours and three backup files are retained in the system.
To configure instance backup settings:
-
Navigate to System > System Administration.
-
Under Backup Settings, select Instance Backup Settings, and specify the required values.
Configure instance event prune settings
To limit the amount of event messages data being stored in your Citrix ADM server’s database, you can specify the interval for which you want Citrix ADM to retain network reporting data, events, audit logs, and task logs. By default, this data is pruned every 24 hours (at 00:00 hours).
To configure instance event prune settings:
-
Navigate to System > System Administration.
-
Under Prune Settings, click Instance Events Prune Settings.
-
Enter the time interval, in days, for which you want to retain data on the Citrix ADM server and click OK.
Configure instance syslog purge settings
To limit the amount of syslog data stored in the database, you can specify the interval at which you want to purge syslog data. You can specify the number of days after which the Generic syslog data will be deleted from Citrix ADM.
To configure instance syslog purge settings:
-
Navigate to System > System Administration. Under Prune Settings, click Instance Syslog Purge Settings.
-
In Configure Instance Syslog Purge Settings page, specify the number of days between 1 and 180 in Retain Syslog Generic Data field.
-
Click OK.
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.