Getting started
Step 1 - Review the system requirements
-
License information. You can manage and monitor any number of instances and entities without a license. However, you can only manage 30 discovered apps and view analytics information for only two virtual servers without applying a license. To manage more than 30 apps or to view analytics for more than two virtual servers, you must purchase appropriate licenses. Learn More.
-
Operating system and receiver requirements. Review this information to make sure you have the correct receiver version for the supported operating systems. Learn More.
-
Browser requirements. To access NetScaler ADM GUI, you must make sure you have the required browser and the correct version. Learn More.
-
Ports. Make sure that the required ports are open for NetScaler ADM to communicate with NetScaler instances. Learn More.
-
NetScaler instance requirements. Different NetScaler ADM features are supported on different NetScaler software versions. Review this information to make sure you have upgraded your NetScaler instances to the correct version. Learn More.
Step 2 - Deploy NetScaler ADM
-
Single-server deployment. In a NetScaler ADM single server deployment, the database is integrated with the server and a single server processes all the traffic. You can deploy NetScaler ADM with Citrix Hypervisor™, VMware ESXi, Microsoft Hyper-V, and Linux KVM. See:
-
High availability deployment. A high availability deployment (HA) of two NetScaler ADM servers provides uninterrupted operations. In a high availability setup, both the NetScaler ADM nodes must be deployed in active-passive mode, on the same subnet using the same software version and build, and must have the same configurations. With HA deployment the ability to configure the floating IP address on the NetScaler ADM primary node eliminates the need of a separate NetScaler load balancer. To learn more, see Configure in high availability deployment.
Step 3 - Add instances to NetScaler ADM
-
NetScaler
-
NetScaler MPX
-
NetScaler VPX
-
NetScaler SDX
-
NetScaler CPX
-
NetScaler BLX
-
NetScaler Gateway
-
Step 4 - Enable analytics on virtual servers
Step 5 - Configure NTP server on NetScaler ADM
Step 6 - Configure system settings for optimal NetScaler ADM performance
-
Configure system alarms. 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.
-
Configure system notifications. You can send notifications to select groups of users for various system-related functions. You can set up a notification server in NetScaler 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.
-
Configure system prune settings. To limit the amount of reporting data being stored in your NetScaler ADM server's database, you can specify the interval for which you want NetScaler 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).
-
Configure system backup settings. NetScaler ADM automatically backs up the system every day at 00:30 hours. By default, it saves three backup files. You might want to retain more number of backups of the system.
-
Configure instance backup settings. If you back up the current state of a NetScaler instance, you can use the backup files to restore stability in case 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.
-
Configure instance event prune settings. To limit the amount of event messages data being stored in your NetScaler ADM server's database, you can specify the interval for which you want NetScaler 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).
-
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 following syslog data will be deleted from NetScaler ADM:
-
Generic Syslog data
-
AppFirewall data
-
NetScaler Gateway data.
-