Dec. 18, 2015
Custom tasks are user-defined configuration tasks that you can add in Command Center to perform a defined set of operations on the managed devices. These tasks may contain a heterogeneous set of commands, such as CLI commands, SHELL, or Secure File Transfer Protocol (SFTP), that you can execute on a single device or a set of devices grouped together in a device list.
Use the following procedures for configuring custom tasks:
You can add custom tasks using one of the following methods:
With custom tasks, you have the option to configure task operations in the following ways:
Execute Sequentially: Execute a task on a set of devices, one device at a time. If task execution fails on any device, it does not continue on the remaining devices . By default, if you do not select this option, the task will be executed in parallel.
If a command fails, Command Center stops executing the remaining commands. If you have selected the Execute Sequentially option and the command fails on one of the devices, execution does not proceed on the remaining devices.
If you have not selected the Execute Sequentially option , task execution continues on the remaining devices even if the command fails on one of the devices.
If a command fails, Command Center ignores the failed command and continues executing the remaining commands on the device . However, if you have selected the Execute Sequentially option and the command fails and continues executing the remaining commands, execution does not proceed on the remaining devices.
If you have not selected the Execute Sequentially option , and the command fails and continues executing the remaining commands, task execution does not proceed on the remaining devices.
Generate rollback commands at run time by fetching these commands based on the version of the device. If command execution within a task fails, the entire task is rolled back.
Device specific rollback commands have precedence over the user defined rollback commands.
When executing tasks, click Preview to display the system-generated rollback commands .
If you configure a task to support the auto rollback feature, the preview screen displays the actual executable commands and the corresponding rollback commands in a tabular format for devices selected in the device list. However, if you configure a task to not support the auto rollback feature, the preview screen displays the actual commands sequentially.
add filter policy $policyname$ -rule $expression$ -$actionType$ $actionname$ bind filter global $policyname$
You can add a custom task from a command file that contains the commands to be executed on the devices.
A command file is a text file containing a list of commands that constitute a task; the content could be a snippet of the ns.conf file. Each command may be a NetScaler CLI, Shell, or FTP command. You must have the command file present on the Command Center server or on your local system.
You can add a custom task from an existing task file. You can also enhance or modify an existing task to create a new task. For example, you can create a new task from a built-in task, or import a task already created on another Command Center server. You must have the task file present on the Command Center server or on your local system.
You can execute a custom task on multiple devices at the same time. You can either select devices individually or select a device list for the tasks. You can execute the same task several times on different devices or device lists. You can also preview a task (the commands and rollback commands) before executing it.
After executing a task, you can view the following execution details of that task instantly or at a later time.
You can schedule custom tasks to execute at a later period or recur at regular intervals. For example, you can schedule tasks to be executed at specific hours daily, at specific hours on specific days of the week, and at specific hours on specific days of the month.
You can save the custom tasks in XML format on the Command Center server. This XML file, also known as task file, can be used to create a new custom task in the existing server, or can be copied to another Command Center server.
You can modify the values of the fields in a custom task.
If you do not want to use a custom task again, you can delete it.