The following are parameters to configure in this panel:

Name -- A unique identifier for this action. For example: “Retrieve MyDevice MAC addresses.”

For a new action to appear on the right-click Action menu, begin its name with the vendor name. For example, Force10-showversion would appear under Actions in that menu. Otherwise, it appears under and Adaptive CLI classification.

Description -- A text description of the action.

Type -- Select a type from the pick list (Configure, External or Show Command).

You can use Open Manage Network Manager’s optional Proscan policies to scan the results of Adaptive CLI show commands for compliance, and trigger actions (alarms, e-mail, and so on) based on their contents. See Change Management / ProScan.

The External command refers to a script. Making this an ACLI means Open Manage Network Manager can schedule such scripts or include them in a workflow. See External Commands for more about these.

Target Type -- Select a type of target from the pick list (Card, Equipment and Subcomponents, Interfaces, Managed Devices, Ports). Adaptive CLI targets can also be None (Targetless). On execution, if you create an Adaptive CLI type with port target, then the selection view panel lets you choose ports. When the Adaptive CLI type is External then Target Type can be None; otherwise it is not an option

Export File Location -- This is a file name and path (C:\mypath\myfile.txt) where you elect to store the result of an adaptive CLI execution. You must specify an extension for the file, and may specify the variable $IPAddress in the filename for pattern substitution.

Overwrite on Export -- Check to overwrite the result file. This overwrites any existing results file with new results (if checked). If it is unchecked, any new results append to the exported file, with a time / date stamp and target-identifying information.

Is Batch Execution Enabled -- Check to allow consolidation of related Adaptive CLI scripts, provided the associated device driver supports such consolidation when provisioning a service.

Batching is valuable for instances like the following: if an Adaptive CLI-provisioned service has 10 sub-services, Open Manage Network Manager runs commands for the first service, then if it’s successful, commits, and logs off. Then Open Manage Network Manager repeats this procedure nine times more, logging on, committing and logging off for each command. If batching is turned on, then Open Manage Network Manager sends the 10 Adaptive CLIs to the device as a single unit before committing and logging off. (This logic does not apply if you are running a procedure against 10 devices.)

Batching is best practice, since if one line of a command fails, the device rolls back the entire block of commands. Cisco devices typically skip and do not commit failing lines.

Last Executed On -- Displays the last execution date. This is blank for New Adaptive CLIs.

Action Associations

Click the Add button to add associations to vendors and device models. For example, you can confine an Adaptive CLI to Dell devices, even to certain Dell models. When you right-click your discovered Dell device in the Managed Resource portlet, the associated Adaptive CLIs appear listed among the available actions you can request.