Table Of Contents

Getting Started with Command Builder

Opening Command Builder

Command Builder Wizard

Table of Commands

Menu Options

Toolbar

A Workflow to Define a New Command

Creating a Command

Defining a Combo Field Type

Defining ANA Macro Language Script Lines

Defining Bean Shell Script Lines

Managing Commands

Previewing and Executing Commands

Publishing Commands

Editing Commands

Exporting Commands

Importing Commands

Updating Commands

Reviewing Command History

Deleting Commands

Getting Started with Command Builder

---

This chapter describes the Command Builder wizard's working environment and how to access Command Builder tools. In addition, it describes how to create, execute, and publish a command.

This chapter includes the following topics:

•Opening Command Builder

•Command Builder Wizard

•A Workflow to Define a New Command

•Creating a Command

•Defining ANA Macro Language Script Lines

•Defining Bean Shell Script Lines

•Previewing and Executing Commands

•Publishing Commands

•Exporting Commands

•Importing Commands

•Updating Commands

•Reviewing Command History

•Deleting Commands

Opening Command Builder

This section provides instructions for launching the Command Builder wizard. Command Builder is launched from a specific managed element, which could be a managed element or a selected object within a managed element, such as a port. This managed element is used to develop and test the command. Once the command has been completed, it can be published and attached to a wider scope of managed elements.

To open Command Builder:

---

Step 1 In Cisco ANA NetworkVision, select the desired element:

•Right-click a managed element in the tree pane or context panel.

•Open the Inventory window for the required managed element, then right-click the required VNE inventory item.

---

Note For more information about the Inventory window, see the Cisco Active Network Abstraction 3.6.6 User Guide.

---

Step 2 Choose Management > Command Builder. The Command Builder wizard is displayed.

---

Command Builder Wizard

Figure 14-1 shows an example of the Command Builder wizard.

Figure 14-1 Command Builder Wizard

The Command Builder wizard consists of:

•Table of Commands

•Menu Options

•Toolbar

Table of Commands

The Command Builder wizard displays a table of all existing commands that are available for the selected managed element or network element. Command Builder enables you to:

•Add a new command, which enables you to execute a programmable sequence of Telnet or SNMP command lines.

•Edit an existing command.

•Delete a command that has not been published.

•Import and export command definitions.

•Import an updated version of an existing command definition.

•Test or run a command on the selected managed element.

•Publish a command and attach it to a wider scope of managed elements.

Table 14-1 describes the fields in the Command Builder table.

Table 14-1 Command Builder Table 

Column	Description
Name	The command name. This name is unique in the entire system.
Menu Caption	The text that is displayed in the menu when launching the command.
IMO Context	The inventory object associated with this command. Note A command is always associated with a selected object within a managed element, which enables it to use the properties of this object inside the script lines. For example, if you select a port object, the port's properties, such as portAlias and status, are automatically made available to the script.
Local	Specifies whether the command is inherited from a higher level or is defined locally on the selected managed element. A command that is defined for a scope of managed elements (such as "All devices" or a specific device type) is automatically assigned to all managed elements in that scope. When modifications are made to a command that is inherited from a higher level, a local copy of the command is created for the specific managed element and overrides the generic definition. Once the local copy is tested and accepted, it can be published to update the higher-level definition.

A table can be sorted:

•According to a column by clicking the required column heading. The icon is displayed next to the selected column heading.

•In ascending or descending order by clicking the column heading. A triangle displayed next to the selected column heading indicates the sort order.

Clicking a red triangle displayed in a cell expands the cell to display all information in the cell.

The Location field displays the number of selected rows and the total number of rows in the table, such as 2/16 Selected. In addition, it displays the location of the selected rows in the table, such as Line 3.

Menu Options

Table 14-2 describes the menu options available in the Command Builder wizard.

Table 14-2 Command Builder Wizard Menu Options 

Menu	Description
File
New Element	Creates a new command definition. For more information, see Creating a Command.
Edit Element	Edits an existing command definition. For more information, see Editing Commands.
Delete Element	Deletes an existing locally defined command; that is, a command that has not yet been published. For more information, see Deleting Commands.
Tools
Export Element	Saves a full command definition that can later be imported to another managed element. For more information, see Exporting Commands.
Import Element	Performs one of the following actions, depending upon whether or not a version of the command definition already exists in Command Builder: •For new command definitions, imports a full command definition to a managed element. For more information, see Importing Commands. •For existing command definitions, replaces the existing command definition with an updated version of the command definition. For more information, see Updating Commands.
Hierarchy Manager	Moves the command definition to a different location or changes the scope of the command across the network hierarchy. For more information, see Publishing Commands.
Run Command	Previews or executes the command. For more information, see Previewing and Executing Commands.

Toolbar

Table 14-3 identifies the buttons that appear in the Command Builder wizard.

Table 14-3 Command Builder Wizard Icons 

Button	Name	Description
	New Element	Creates a new command definition. For more information, see Creating a Command.
	Edit Element	Edits an existing command definition. For more information, see Editing Commands.
	Delete Element	Deletes a command that exist locally; that is, a command that has not yet been published. For more information, see Deleting Commands.
	Export Element	Saves a full command definition to a file that can later be imported to another managed element. For more information, see Exporting Commands.
	Import Element	Performs one of the following actions, depending upon whether or not a version of the command definition already exists in Command Builder: •For new command definitions, imports a full command definition to a managed element. For more information, see Importing Commands. •For existing command definitions, replaces the existing command definition with an updated version of the command definition. For more information, see Updating Commands.
	Hierarchy Manager	Moves the command definition to a different location or changes the scope of the command across the network hierarchy. For more information, see Publishing Commands.
	Run Command	Previews or executes a command. For more information, see Previewing and Executing Commands.

The Close button closes the Command Builder wizard.

A Workflow to Define a New Command

Figure 14-2 illustrates the steps required to define a new command definition using Command Builder and the order in which the steps must be performed.

Figure 14-2 Define a New Command Workflow

At any time after the command has been defined, it can be tested, executed, and published to a wider scope of managed elements and network elements.

---

Note After you perform any action on the command (such as create, modify, or update), we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the correct version from the registry.

---

For more information about:

•Creating a command, see Creating a Command.

•Defining security access roles and defining input parameters, see Creating a Command.

•Defining script lines and saving commands, see:

–Defining ANA Macro Language Script Lines.

–Defining Bean Shell Script Lines.

Creating a Command

Command Builder enables you to create a command definition which, by default, is created as a local instance. For more information about publishing a local instance of a command to a higher level in the hierarchy, see Publishing Commands.

In addition, you can edit an existing command. For information about editing an existing command, see Editing Commands.

To create a command:

---

Step 1 In the Command Builder dialog box, open the New Command dialog box in one of the following ways:

•Click New Element in the toolbar.

•Choose File > New Element.

The New Command dialog box is displayed (Figure 14-3).

Figure 14-3 New Command Dialog Box

Step 2 Enter the command identification information:

Field	Description
Name	A unique name that identifies the command.
Menu Caption	Text that describes the command in the menu; that is, the menu option.
Menu Visible	Indicates whether or not the command is to appear as a menu option in Cisco ANA NetworkVision. Check the check box for the command to appear as a menu option. Uncheck the check box to prevent the command from appearing as a menu option. Note A command that is defined as not visible in the menu can still be executed via the API.
Menu Path	If you check the Menu Visible check box, enter the location in the menu where the command is to be displayed.
Context IMO	The inventory object that is associated with the command (and exposes its data properties to the command). If the inventory object has subobjects that do not appear in the inventory tree (such as parameter groups of a port), they are listed in a drop-down list.
Language	The scripting language to be used for the command: •ANA Macro—Simple mode. •Bean Shell—Programmable mode; full scripting language.
Protocol	The protocol to use: •Telnet—Supported by both ANA Macro and Bean Shell. •SNMP—Supported by Bean Shell only. This option does not appear if you choose ANA Macro in the Language field. Note Cisco ANA provides an SNMP Bean Shell template that enables easy creation of SNMP commands.

Step 3 Click Next. The Command Authorizations dialog box is displayed.

Step 4 Select the security access roles that are authorized to execute the command:

•Administrator

•Configurator

•Operator Plus

•Operator

•Viewer

Step 5 Click Next. The User Input Arguments dialog box is displayed.

Command Builder enables you to define any number of input parameters. Input parameter attributes determine the structure and format of the input form. When the command is executed, the input form is generated automatically.

---

Note The order of the input parameters determines the sequence in which they are presented in the input form.

---

ANA Macro Language supports two types of script parameters: built-in parameters and user-defined parameters, both of which are replaced in runtime. All parameters (both built-in and user-defined) are available during command editing via a selection list.

For information about ANA Macro Language scripts, see Defining ANA Macro Language Script Lines.

Step 6 Click Next in the Command Authorizations dialog box. The User Input Arguments dialog box is displayed (Figure 14-4).

Figure 14-4 User Input Arguments Dialog Box

Step 7 To add a new argument, click New. The Add/Edit User Argument dialog box is displayed (Figure 14-5).

Figure 14-5 Add/Edit User Argument for Command Dialog Box

Step 8 Enter the required information:

Property	Explanation
Name	Parameter name. This entry must be unique and can contain only letters, numbers, hyphens (-), and underscores (_).
Caption	Parameter display name. This entry is displayed in the Command Builder script execution window.
Type	The type of input value: •String •Integer •IPSubnet •Combo •IP Address •Float •Long For more information about defining a Combo field type, see Defining a Combo Field Type. Note Only input values that are valid for the selected type are accepted. These values are validated during runtime.
Width	Field width, in number of characters. Relevant for the Command Builder script execution window.
Visible	Indicates whether this parameter appears in the Command Builder script execution window. Check this check box to display the parameter, or uncheck the check box to hide the parameter from the user. If the argument is hidden, it can still be used in the command (with its default value). Note When the parameter is not visible and has been assigned a default value, it can serve as a constant argument.
Default	A default value for the parameter.

---

Note A discussion of the Advanced option does not fall within the scope of this guide.

---

Step 9 Click OK. The newly created argument is displayed in the User Input Arguments dialog box.

Step 10 To specify the sequence in which multiple arguments are presented when they are executed, select an argument and click Move Up or Move Down.

Step 11 Click Next to define the command:

•For ANA Macro Language commands, see Defining ANA Macro Language Script Lines.

•For Bean Shell commands, see Defining Bean Shell Script Lines.

---

Defining a Combo Field Type

When Combo is selected in the Type field of the Add/Edit User Argument for x Command dialog box, the Browse button is enabled. This enables you to create a selection list (drop-down list) of the valid options that are displayed in the combo box of the input form, such as Up = 1 and Down = 2.

To define the combo entries:

---

Step 1 Select Combo in the Type field of the Add/Edit User Argument for x Command dialog box.

Step 2 Click Browse. The Selection List dialog box is displayed (Figure 14-6).

Figure 14-6 Selection List Dialog Box

Step 3 Enter the required information:

Field	Description
Value	The actual value of the option; for example, 1.
Label	The description of the entry that is displayed in the selection list (drop-down list) of the input form, such as Up.

Step 4 Click Add.

Step 5 Repeat Steps 3 and 4 as needed until you have added all entries.

Step 6 Click Close. The Add/Edit User Argument dialog box is displayed.

---

Defining ANA Macro Language Script Lines

You can specify either ANA Macro Language or Bean Shell as the script language. ANA Macro Language scripts consist of a simple sequence of Telnet commands, runtime-replaced user-defined input parameters, and inline execution directives that are executed sequentially as Telnet configuration commands on a networking device.

ANA Macro Language represents both types of parameters (built-in and user-defined) in script lines within dollar signs; for example, $...$. For instance, in a VRF configuration command, the input variable vrfName can be defined as ip vrf $vrfName$.

To define ANA Macro Language script lines (continuing from Step 11 in Creating a Command):

---

Step 1 In the User Input Arguments dialog box, click Next. The Script Lines dialog box is displayed, enabling you to add or edit a script line, as shown in Figure 14-7.

Figure 14-7 Script Lines Dialog Box

Step 2 Enter the required information, using the following guidelines:

•To view all user-defined and built-in parameters in the Command Builder application, position the cursor in the Script or Rollback field and press Ctrl-Spacebar. A dialog box is displayed that lists all available arguments (containing both the user-defined input argument and the built-in properties of the IMO context). Select an entry from the list and then click OK to add it to the Script or Rollback field.

•Pragmas are enclosed with square brackets: [...].

•It is possible to use multiple pragmas in a single line, in which case all pragmas are analyzed. If the same type of pragma is repeated, only the last one is used.

•If carriage returns are required in the command line, enter the escape sequence &cr.

Field	Description
Script	The actual Telnet script lines sent to the device. The script lines can contain optional inline directives (pragmas) for finer granularity control. For more information about the supported pragmas, see Supported Pragmas, page 17-4.
Rollback	(Optional) The rollback script that is used when the command fails. Note If the rollback script fails, no additional actions are performed.
Failure Condition	(Optional) A general failure condition that applies to all script lines. To specify a failure condition: 1. Check the Failure Condition check box. 2. In the Failure Condition field, enter the text that is to be looked for during script execution. If the specified text appears in the reply, the command is aborted.

Step 3 Click Finish. The Create Command dialog box is displayed.

An LED indicates the progress or status of the command as it is being saved to the registry:

•Blue—The command definition is being saved.

•Green—The command has been created or updated successfully.

•Red—The Command Builder wizard failed to create or update the command.

Step 4 Click Close when the command has been successfully saved. The newly created command is displayed in the Command Builder table.

See Previewing and Executing Commands to preview or execute the command.

See Publishing Commands to publish the command.

---

After you create, modify, or update a command, we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the correct version from the registry.

Defining Bean Shell Script Lines

You can define the language of the script as either ANA Macro Language or Bean Shell. Bean Shell uses a fully programmatic logic via scripting language (including conditions, loops, and external files).

For information about ANA Macro Language scripts, see Defining ANA Macro Language Script Lines.

To define Bean Shell script lines (continuing from Step 11 in Creating a Command):

---

Step 1 In the User Input Arguments dialog box, click Next. The Bean Shell Script dialog box is displayed.

Step 2 Enter the required information, using the following guidelines:

•To view all user-defined and built-in parameters in the Command Builder application, position the cursor in the Script or Rollback field and press Ctrl-Spacebar. A dialog box is displayed that lists all available arguments (containing both the user-defined input argument and the built-in properties of the IMO context). Select an entry from the list and then click OK to add it to the Script or Rollback field.

•Unlike ANA Macro Language, in Bean Shell user arguments, do not embed inventory properties within dollar signs ($...$).

Field	Description
Script	The actual Telnet script lines sent to the device. The script lines can contain optional inline directives (pragmas) for finer granularity control. For more information about the supported pragmas, see Supported Pragmas, page 17-4.
Rollback	(Optional) The rollback script that is used when the command fails. Note If the rollback script fails, no additional actions can be performed.

Step 3 Click OK. The selected field is displayed in the Bean Shell Script dialog box.

Step 4 Click Finish. The Create Command dialog box is displayed.

An LED indicates the progress or status of the command as it is being saved to the registry:

•Blue—The command definition is being saved.

•Green—The command has been created or updated successfully.

•Red—The Command Builder wizard failed to create or update the command.

For more information, see Defining ANA Macro Language Script Lines.

Step 5 Click Close when the command has been saved successfully. The newly created command is displayed in the Command Builder table.

See Previewing and Executing Commands to preview or execute the command.

See Publishing Commands to publish the command.

---

After you create, modify, or update a command, we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the correct version from the registry.

Managing Commands

Cisco ANA enables you to manage commands in the following ways:

•Preview or execute a command. See Previewing and Executing Commands.

•Publish a command. See Publishing Commands.

•Edit a command. See Editing Commands.

•Export a command for use with other network elements. See Exporting Commands.

•Import a new command. See Importing Commands.

•Import an updated version of a command. See Updating Commands.

•Review the history of a command. See Reviewing Command History.

•Delete a command. See Deleting Commands.

Previewing and Executing Commands

Command Builder enables you to preview the command (including variables) before it is executed. The input form is automatically generated and opened displaying all user-defined input fields for the command. Command Builder supports multiple activations, meaning that a command can be invoked to run concurrently on multiple managed elements or network elements.

To preview or execute the command:

---

Step 1 Select the required command in the Command Builder wizard table.

Step 2 Run the command in one of the following ways:

•Click Run Command in the toolbar.

•Choose Tools > Run Command.

•Right-click the command, then choose Run Command.

The input form is generated and displayed (Figure 14-8).

Figure 14-8 Input Form

The input form heading displays the name of the command and contains two tabs:

•Input—Displays the input parameters.

•Result—Displays the preview or the actual interaction of the command in the output console with full execution audit.

Step 3 Click Preview to see how the command, including variables, looks before it is executed. The result is displayed in the Result tab as shown in Figure 14-9.

Figure 14-9 View Command Before Executing

Step 4 Click Execute to view the results of the actual command that is being executed. The result is displayed in the Result tab as shown in Figure 14-10.

Figure 14-10 Actual Command Results

Step 5 Close the input form to return to the Command Builder wizard.

---

Publishing Commands

After you have defined a command and tested it on a specific instance of a managed element, you can publish it and apply it to a wider scope of managed elements in the network.

The Command Builder Hierarchy Manager dialog box enables you to publish the command to one or more locations across the inheritance hierarchy (as defined in the system). In other words, you define the scope where the command is to be applied in the hierarchy.

Different variations of a command can be used for different managed elements and network elements, where the implementation of the command is different for each managed element or network element.

Figure 14-11 shows an example of an inheritance hierarchy. In this example, the top level of the hierarchy is All devices and the lowest level of the hierarchy is Device XYZ.

Figure 14-11 Inheritance Hierarchy Example

When a command is published to a node in the hierarchy, it overrides any inherited command from a higher level and automatically applies to all its children. For example, if a command is published to Cisco 7200, it overrides any variant of this command defined at a higher level and is assigned to all devices of type Cisco 7200 in the system.

To publish a command:

---

Step 1 Select the required command in the Command Builder wizard table.

Step 2 Open the Hierarchy Manager dialog box in one of the following ways:

•Click Hierarchy Manager in the toolbar.

•Choose Tools > Hierarchy Manager.

•Right-click the command, then choose Hierarchy Manager.

---

Note If user-friendly VNE names exist in the schema, the hierarchy manager table displays these user-friendly registry location names in the VNE Hierarchy Location column. A user-friendly VNE name is a hierarchy path that has been defined in the registry and is then displayed in the hierarchy manager table.

---

Each row that is displayed in the Hierarchy Manager dialog box represents a different level of the hierarchy. The rows are displayed in descending order with the top row representing the highest level of the hierarchy and the bottom row representing the lowest level of the hierarchy.

The following information is displayed in the table:

•Exist—A check mark in this column indicates that a local variant of the command exists for that VNE hierarchy location.

•Registry Key—The hierarchy path, as defined in the registry.

Table 14-4 describes the tools that are displayed in the Hierarchy Manager dialog box.

Table 14-4 Hierarchy Manager Dialog Box Tools 

Button	Description
	Copies the command from a selected node in the hierarchy so that it can be pasted onto another node in the hierarchy. A copy icon is displayed to the left of the selected node.
	Cuts the command from a selected node in the hierarchy so that it can be moved to another node in the hierarchy. A cut icon is displayed to the left of the selected node.
	Pastes the command that was copied or cut from a selected node in the hierarchy onto another node in the hierarchy. A paste icon is displayed to the left of the selected node.
	Deletes the command from the selected node in the hierarchy. Note If the command has been deleted from all nodes, it is removed from the list in the main dialog box of the Command Builder Wizard.
	Saves a full command definition to a file that can later be imported to another managed element. For more information, see Exporting Commands.
	Performs one of the following actions, depending upon whether or not a version of the command definition already exists in Command Builder: •For new command definitions, imports a full command definition to a managed element. For more information, see Importing Commands. •For existing command definitions, replaces the existing command definition with an updated version of the command definition. For more information, see Updating Commands.

Step 3 Select the node in the hierarchy where you want to publish the command.

Step 4 Click Copy or Cut in the toolbar to copy or cut the command.

Step 5 Select the node in the hierarchy where you want to publish the command.

Step 6 Click Paste on the toolbar to paste the command. The command is published to the selected node in the hierarchy.

---

Editing Commands

You can edit an existing command definition, and the command that is edited affects only the local instance. When an inherited command is edited, the new local instance overrides the generic command definition for the specific managed element.

To edit a command:

---

Step 1 Select the command that you want to edit in the table of the Command Builder wizard, and then do one of the following:

•Click Edit Element in the toolbar.

•Choose File > Edit Element.

•Right-click the command, then choose Edit Element.

The Hierarchy Manager dialog box is displayed.

---

Note If user-friendly VNE names exist in the schema, the hierarchy manager table displays these user-friendly registry location names in the VNE Hierarchy Location column. A user-friendly VNE name is a hierarchy path that has been defined in the registry and is then displayed in the hierarchy manager table.

---

Step 2 Select the required version of the command from the hierarchy manager, then click Next. The Edit Command dialog box is displayed for the selected command.

Step 3 Edit the command as required by using the Command Builder wizard. For more information, see Creating a Command.

Step 4 Click Finish in the script dialog box to save the modified command.

Step 5 When the command has been successfully saved, click Close. The edited command is supported and displayed in the Command Builder wizard.

---

After you create, modify, or update a command, we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the correct version from the registry.

For information about previewing and executing the edited command, see Previewing and Executing Commands.

For information about publishing the edited command, see Publishing Commands.

Exporting Commands

To export commands:

---

Step 1 In the Command Builder wizard, select the command that you want to export. You can export only one command at a time.

Step 2 Open the Export dialog box in one of the following ways:

•Click Export Element in the toolbar.

•Choose Tools > Export Element.

•Right-click the command, then choose Export Element.

Step 3 Select the command that you want to export by checking the check box in the Selected column. The version is selected in the table.

Step 4 Click OK. The Export Property dialog box is displayed.

Step 5 Browse to the directory where you want to save the command.

Step 6 In the File name field, enter a name and extension (for example, .txt) for the command.

Step 7 Click Save. The command is saved in the selected directory. The Export dialog box is displayed.

Step 8 Click Close. The Command Builder wizard is displayed.

---

Importing Commands

You can import multiple commands using this procedure as long as all of the commands are associated with the same VNE.

To import commands:

---

Step 1 In Cisco ANA NetworkVision, select the required managed element.

Step 2 Right-click the element, then choose Management > Command Builder. The Command Builder wizard is displayed.

Step 3 Open the Import Element dialog box in one of the following ways:

•Click Import Element in the toolbar.

•Choose Tools > Import Element.

Step 4 Browse to the directory that contains the commands that you want to import.

Step 5 Select the commands that you want to import. To select multiple commands, press Shift or Ctrl while choosing the commands.

Step 6 Click Open. The Import Elements dialog box is displayed.

If you select multiple files, Command Builder presents an Import Element dialog box for each command.

Step 7 In the Import Element dialog box, select the VNE hierarchy location for the specified command.

Step 8 Click OK. The Command Builder wizard is displayed.

Step 9 Click Close. The commands are imported and displayed in the opening window of the Command Builder wizard.

---

After you create, modify, or update a command, we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the correct version from the registry.

Updating Commands

Beginning with Cisco ANA 3.6.6, you can import an updated version of a command. When you import an updated version of the command, the existing version in Command Builder is replaced with the new command. If the existing command has been published, the updated version replaces the specific command that you selected in the inheritance hierarchy.

---

Note After you update a command, we recommend that you wait a few seconds before executing it. If the gateway is busy, waiting a few seconds allows sufficient time for Command Builder to obtain the updated version from the registry.

---

To update a command:

---

Step 1 In Cisco ANA NetworkVision, select the required managed element.

Step 2 Right-click the element, then choose Management > Command Builder. The Command Builder wizard is displayed.

Step 3 Open the Import Element dialog box in one of the following ways:

•Click Import Element in the toolbar.

•Choose Tools > Import Element.

Step 4 Browse to the directory that contains the updated version of the command definition.

Step 5 Select the updated command definition that you want to import. You can import only one updated command definition at a time.

Step 6 Click Open. The Import Elements dialog box is displayed.

Step 7 In the Import Elements dialog box, select the VNE hierarchy location for the updated command definition.

Step 8 Click OK. A window appears, asking you to confirm the operation.

Step 9 Click Yes to confirm the operation, or No to cancel the operation.

If you click Yes, the updated version of the command definition replaces the existing version of the command definition, and the Command Builder wizard is displayed.

Step 10 Click Close to close the Command Builder wizard.

---

Reviewing Command History

Every command that is executed is logged in the Cisco ANA event database. The command's execution history can be viewed using the Cisco ANA EventVision application. For more information about Cisco ANA EventVision, see the Cisco Active Network Abstraction 3.6.6 User Guide.

Deleting Commands

By default, a command created by a user is created as a local instance. A command that is defined locally can be seen in the Command Builder wizard. You can only delete commands that exist locally; that is, commands that have not yet been published.

You can delete multiple commands at a time as long as all of the commands are associated with the same VNE.

To delete commands:

---

Step 1 In the Command Builder wizard, select the commands you want to delete. To select multiple commands, press Shift or Ctrl while choosing the commands.

Step 2 Do one of the following:

•Click Delete Element in the toolbar.

•Choose File > Delete Element.

•Right-click one of the selected commands, then choose Delete Element.

Step 3 When prompted, confirm or cancel the deletion process.

If you confirm the deletion, the commands are deleted and are no longer displayed in the Command Builder table.

---

When you have finished working with Command Builder, click Close.