Owners Manual

Actions Portlet | Actions and Adaptive CLI
564 OMNM 6.5.2 User Guide
Ty p e
—Select a type from the pick list ( CLI Configure Command, External Executable, Config
File Generation
or CLI Show Command ).
The
External Executable command refers to a script. Making this an ACLI means
OpenManage Network Manager can schedule such scripts or include them in a workflow. See
External Executable on page 582 for more about these.
NOTE:
You can use OpenManage 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 and Compliance.
See How to: Use Config File Generation on page 578 for more about that.
Tar get Typ e —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
If you want the target to be a OpenManage Network Manager group after you right-click an
Adaptive CLI, and select
Execute , select (Group Membership ) in the target selector filter.
Click the icon to the left of the
Go button, and to the right of the empty field to see available
groups. Select the group(s), and click
Done . Click the Go button. Control click if you want a
subset of the group’s devices, or simply click
Add All and then click Done.
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.
(Currently supported by the Juniper JUNOS driver only.)
Batching is valuable for instances like the following: if an Adaptive CLI-provisioned service
has 10 sub-services, OpenManage Network Manager runs commands for the first service, then
if it’s successful, commits, and logs off. Then OpenManage Network Manager repeats this
procedure nine times more, logging on, committing and logging off for each command. If
batching is turned on, then OpenManage 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 for Juniper devices, 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.