You can set the default values for the following Command Center server settings:
- SNMP Trap Destination: A Simple Network Management Protocol (SNMP) trap is a notification event issued by a managed device to the network management station when a significant event (not necessarily an outage, a fault, or a security violation) occurs. The SNMP trap destination in the Command Center context is the IP address to be used on managed devices to send SNMP traps when the Command Center server is multihomed or if there is a Network Address Translation (NAT) device between the server and the managed devices.
- SNMP Trap Port: You can specify either a single port number or multiple port numbers (separated by commas) to receive the traps. The default SNMP trap port number is 162. However, if you specify a different port number, you must configure the SNMP agent of the managed device to send the trap on the new port.
- Device Label: A device label is used when the discovered devices are displayed on a map. The default device label is the IP address of the managed device. If you choose System Name as the device label, the SNMP system names configured on the devices are shown. If you choose Host Name the devices are labeled by their DNS host names. Note that the host names are displayed only when the devices are discovered using host names. The devices located on the Citrix Network tab reflect the change.
Note: By default, NetScaler devices have the sysname NetScaler.
- SSL Certificate Management: You can centrally manage the Secure Sockets Layer (SSL) certificates installed on the managed devices. You can poll all the managed devices for certificate status, install SSL certificates, update existing certificates, generate new certificate signing requests (CSRs), and set up polling intervals and severity levels. This feature is enabled by default. So, if you do not want to use the SSL Certificate Management feature to centrally manage the SSL certificates on all the managed devices, you must disable this feature.
Note: Command Center supports this feature on NetScaler 7.0 and later.
- Task Execution User Credentials: You can set up authentication using the user credentials of the device for executing tasks on managed devices. You can execute tasks on the managed devices from Command Center using the same credentials used for discovering devices. However, the role-based access capabilities of Command Center allow you to override the credentials for task execution and prompt users to input their user credentials. This provides administrators the ability to control users to execute only those commands that are configured on the device using the device role-based access privileges for those user IDs.
- Performance Data Configuration: You can access the collected performance data using quick report, custom report, and trend report generators. Note that trend reports are available only in the HTML client.
By default, for quick and custom reports, you can view performance data for the last 14 days in 5-minute granularity. In trend reports, you can view consolidated hourly data for the last 30 days and daily data for the last 365 days. However, you can customize the number of days for which you want to collect and maintain performance data.
- Monitoring: You can centrally manage the Monitoring feature for monitoring the real-time status of virtual servers, services, and service group members configured on all discovered NetScaler devices. This feature is enabled by default. In an environment with multiple NetScaler devices and many vservers, services, and service groups configured on the devices, the regular monitoring of these entities may add to the network load. If you find that this network load is too high in your environment and results in other issues, you can disable the monitoring feature for that environment.
- Syslog Clean Interval: To limit the amount of syslog data stored in the database, you can specify the interval at which you want to purge syslog data. A purge job is enabled by default, and is scheduled to run at 1:00 AM daily. By default, Command Center stores syslog messages for the last 90 days. To customize the purge interval, you can specify the number of days in the Syslog Clean interval (in days) field. Only the records older than the number of days that you specify are purged. For example, if you specify as 45 days, Command Center purges syslog messages that are older than 45 days.