Table Of Contents
Getting Started with Command Builder
Opening Command Builder
Command Builder Wizard
Table of Contents
Menu Bar
File Menu
Tools Menu
Toolbar
A Workflow to Define a New Command
Creating or Editing a Command
Creating a Command
Editing a Command
Defining the User Input Parameters
Defining a Combo Field Type
Defining Cisco ANA Macro Language Script Lines
Defining Bean Shell Script Lines
Previewing and Executing the Command
Publishing Commands
Deleting Commands
Exporting and Importing Commands
Exporting Commands
Importing Commands
Reviewing the Command History
Closing Command Builder
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 or Editing a Command
•Defining the User Input Parameters
•Defining Cisco ANA Macro Language Script Lines
•Defining Bean Shell Script Lines
•Previewing and Executing the Command
•Publishing Commands
•Deleting Commands
•Exporting and Importing Commands
•Reviewing the Command History
•Closing Command Builder
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 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.5 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 Contents
•Menu Bar
•Toolbar
Table of Contents
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.
•Run or test a command on the selected managed element.
•Publish a command and attach it to a wider scope of managed elements.
The following information is displayed in the table of the Command Builder wizard:
•Name—The identifier of the command. This name is unique to the entire system.
•Menu Caption—The text that describes the command in the menu when launching the command.
•IMO Context—The inventory object with which the command is associated.
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 is displayed next to the selected column heading.
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 Bar
This section provides a description of each option available in Command Builder menus. The menus are:
•File Menu
•Tools Menu
File Menu
The File menu provides the following options:
•New Element—Create a new command definition. For more information, see Creating or Editing a Command.
•Edit Element—Edit an existing command definition. For more information, see Editing a Command.
•Delete Element—Delete existing locally defined commands; that is, commands that have not yet been published. For more information, see Deleting Commands.
Tools Menu
The Tools menu provides the following options:
•Export Element—Save a full command definition to a file that can later be imported to another managed element. For more information, see Exporting and Importing Commands.
•Import Element—Copy a full command definition from an exported file and import this command to another managed element. For more information, see Exporting and Importing Commands.
•Hierarchy Manager—Move the command definition to a different location or change the scope of the command across the network hierarchy. For more information, see Publishing Commands.
•Run Command—Preview or execute the command. For more information, see Previewing and Executing the Command.
Toolbar
Table 14-1 identifies the buttons that appear in the Command Builder wizard.
Table 14-1 Command Builder Wizard Icons
Button
|
Name
|
Description
|
|
New Element
|
Create a new command definition. For more information, see Creating or Editing a Command.
|
|
Edit Element
|
Edit an existing command definition. For more information, see Editing a Command.
|
|
Delete Element
|
Delete commands that exist locally; that is, commands that have not yet been published. For more information, see Deleting Commands.
|
|
Export Element
|
Save a full command definition to a file that can later be imported to another managed element. For more information, see Exporting and Importing Commands.
|
|
Import Element
|
Copy a full command definition from an exported file and import this command to another managed element. For more information, see Exporting and Importing Commands.
|
|
Hierarchy Manager
|
Move the command definition to a different location or change the scope of the command across the network hierarchy. For more information, see Publishing Commands.
|
|
Run Command
|
Preview or execute a command. For more information, see Previewing and Executing the Command.
|
The Close button closes the Command Builder wizard. For more information, see Closing Command Builder.
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 they 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.
For more information about:
•Creating or editing a command, see Creating or Editing a Command.
•Defining security access roles, see Creating or Editing a Command.
•Defining te input parameters, see Defining the User Input Parameters.
•Defining script lines and saving commands, see Defining Cisco ANA Macro Language Script Lines for Cisco ANA Macro Language and Defining Bean Shell Script Lines for Bean Shell.
•Previewing and executing commands, see Previewing and Executing the Command.
•Publishing commands, see Publishing Commands.
•Deleting commands, see Deleting Commands.
•Importing and exporting commands, see Exporting and Importing Commands.
•Reviewing command history, see Reviewing the Command History.
Creating or Editing 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 a Command.
Creating a Command
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
The following information is displayed in the New Command dialog box:
•Name—The name identifying the command, unique to the entire system.
•Menu Caption—Text that describes the command in the menu; that is, the menu option.
•Menu Visible—Indicates whether this option is to appear as a menu option in NetworkVision.
Note A command that is defined as not visible in the menu can still be executed via the API.
•Menu Path—The location in the menu where the command is added or displayed.
•Context IMO—Displays 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—Select either Macro Language (simple mode) or Bean Shell (programmable mode/full scripting language).
•Protocol—Select the protocol:
–Cisco ANA Macro Language uses only Telnet.
–Bean Shell can use either Telnet or SNMP.
Note Cisco ANA provides an SNMP Bean Shell template that enables easy creation of SNMP commands.
The following buttons are displayed in the New Command dialog box:
•Next—Displays the Command Authorizations dialog box.
•Cancel—Returns to the opening window of the Command Builder wizard.
Step 2 Define the command identification information.
Step 3 Click Next. The Command Authorizations dialog box is displayed.
This Command Authorizations dialog box enables you to specify the security access roles that are authorized to execute the command:
•Administrator
•Configurator
•Operator Plus
•Operator
•Viewer
The following buttons are displayed:
•Prev—Displays the New Command dialog box.
•Next—Displays the User Input Arguments dialog box.
•Cancel—Returns to the opening window of the Command Builder wizard.
Step 4 Select the required security access roles.
Step 5 Click Next. The User Input Arguments dialog box is displayed.
Proceed to Defining the User Input Parameters to continue creating the command.
Editing a Command
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.
•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; change the existing information using the Command Builder wizard.
Step 4 Save the modified command:
•For Cisco ANA Macro Language commands, click Finish in the Script Lines dialog box.
•For Bean Shell commands, click Finish in the Bean Shell Script dialog box.
Step 5 When the command has been successfully saved, click Close. The edited command is supported and displayed in the Command Builder wizard.
For information about previewing and executing the edited command, see Previewing and Executing the Command.
For information about publishing the edited command, see Publishing Commands.
Defining the User Input Parameters
Command Builder enables you to define any number of input parameters. The input parameter's 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 order in which they are presented in the input form.
Cisco ANA Macro Language supports two types of script parameters: User-defined parameters and built-in 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 Cisco ANA Macro Language scripts, see Defining Cisco ANA Macro Language Script Lines.
To define the input parameters:
Step 1 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
Table 14-2 identifies the user-defined parameter properties that can be defined in the Add/Edit User Arguments dialog box.
Table 14-2 User-Defined Parameter Properties
Property
|
Explanation
|
Name
|
Parameter name. Can contain only letters, numbers, hyphen (-), and underscore (_), and must be unique.
|
Caption
|
Parameter display name. Visible in the Command Builder script execution window.
|
Type
|
String, Integer, IPSubnet, Combo, IP Address, Float, Long. For more information about defining a Combo, see Defining Cisco ANA Macro Language Script Lines.
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 option to display the parameter, or clear it 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.
|
In the User Input Arguments dialog box, the Move Up and Move Down buttons enable you to specify the order of the user input parameters, thereby determining the order in which they are presented when they are executed.
The following additional buttons are displayed in the User Input Arguments dialog box:
•New—Create a new input argument for the command.
Note A discussion of the Advanced option does not fall within the scope of this guide.
•Edit—Edit the selected input argument.
•Delete—Delete the selected input argument from the User Input Arguments table.
•Prev—Display the Command Authorizations dialog box.
•Next—Display the Script Lines dialog box.
•Cancel—Return to the opening window of the Command Builder wizard.
Step 2 Open the Add/Edit User Argument for x Command dialog box:
•To add a new input argument, click New.
•To modify an existing input argument, select the input argument, then click Edit.
The Add/Edit User Argument for x Command dialog box is displayed.
Step 3 Enter or edit the information for the input argument.
Step 4 Click OK. The new or edited user input argument is displayed in the User Input Arguments dialog box.
Note Select a user-defined input parameter and click Move Up or Move Down to reorder the user-defined input parameters.
Step 5 Click Next to define:
•Cisco ANA Macro Language command. The Script Lines dialog box is displayed.
See Defining Cisco ANA Macro Language Script Lines to continue creating the command.
•Bean Shell command. The Bean Shell Script dialog box is displayed.
See Defining Bean Shell Script Lines to continue creating the command.
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-5).
Figure 14-5 Selection List Dialog Box
The following information is displayed in the Selection List dialog box:
•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."
The following buttons are displayed in the Selection List dialog box:
•Add—Adds a new entry to the selection list.
•Delete—Deletes the selected entry from the selection list.
•Close—Closes the Selection List dialog box. The Add/Edit User Argument dialog box is displayed.
Step 3 Enter the required information in the Value and Label fields.
Step 4 Click Add. The entry (Value and Label) is added to the table.
Step 5 Repeat Step 3 and Step 4 for all required entries.
Step 6 Click Close. The Add/Edit User Argument dialog box is displayed.
Defining Cisco ANA Macro Language Script Lines
You can define the language of the script as either Cisco ANA Macro Language or Bean Shell. Cisco 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.
Cisco 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 Cisco ANA Macro Language script lines:
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-6.
Figure 14-6 Script Lines Dialog Box
Note To view all user-defined and built-in parameters in the Command Builder application, press Ctrl-Spacebar to open the selection list of available arguments (containing both the user-defined input argument and the built-in properties of the IMO context).
The following areas are displayed in the Script Lines dialog box:
•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—The rollback script that is used when the command fails (optional).
Note If the rollback script fails, no additional actions can be performed.
•Failure Condition—A general failure condition, which applies to all script lines (optional). Aborts the command if the specified text exists in the reply.
The following buttons are displayed in the Script Lines dialog box:
•Prev—Displays the User Input Arguments dialog box.
•Finish—Saves the command to the registry. The Create Command dialog box is displayed while the command is being created.
•Cancel—Returns to the opening window of the Command Builder wizard.
Step 2 Define the script lines in the Script area.
Note•Pragmas are enclosed with square brackets: [...].
•To view all user-defined and built-in parameters in the Command Builder application, press CTRL-Spacebar to open the selection list of available arguments (containing both the user-defined input argument and the built-in properties of the IMO context).
•If carriage returns are required in the command line, enter the escape sequence &cr.
•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.
Step 3 (Optional) Define the Rollback and Fail Condition criteria.
Step 4 Click Finish. The Create Command dialog box is displayed.
LEDs indicate the progress or status of the command as it is being saved to the registry:
•Blue—The command definitions are now being saved.
•Green—The command has been created or has been updated successfully.
•Red—The Command Builder wizard failed to create or update the command.
Step 5 Click Close when the command has been successfully saved. The newly created command is displayed in the Command Builder table.
See Previewing and Executing the Command to preview or execute the command.
See Publishing Commands to publish the command.
Defining Bean Shell Script Lines
You can define the language of the script as either Cisco 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 Cisco ANA Macro Language scripts, see Defining Cisco ANA Macro Language Script Lines.
To define Bean Shell script lines:
Step 1 In the User Input Arguments dialog box, click Next. The Bean Shell Script dialog box is displayed.
Note To view all user-defined and built-in parameters in the Command Builder application, press Ctrl-Spacebar to open the selection list of available arguments (containing both the user-defined input argument and the built-in properties of the IMO context).
Note Unlike Cisco ANA Macro Language, in Bean Shell user arguments, do not embed inventory properties within dollar signs ($...$).
The following areas are displayed in the Bean Shell Script dialog box:
•Script—The actual Telnet script lines sent to the device. The script lines can contain optional inline directives (pragmas) for finer granularity control.
•Rollback—The rollback script that is used when the command fails (optional).
The following buttons are displayed in the Bean Shell Script dialog box:
•Prev—Displays the User Input Arguments dialog box.
•Finish—Saves the command to the registry. The Create Command dialog box is displayed.
•Cancel—Returns to the opening window of the Command Builder wizard.
Step 2 Press Ctrl-Spacebar and select the required field.
Step 3 Click OK. The selected field is displayed in the Bean Shell Script dialog box.
Step 4 Repeat Step 2 and Step 3 to add all required fields.
Step 5 Click Finish. The Create Command dialog box is displayed. LEDs indicate the progress or status of the command as it is being saved to the registry. For more information, see Defining Cisco ANA Macro Language Script Lines.
Step 6 Click Close when the command has been saved successfully. The newly created command is displayed in the Command Builder table.
See Previewing and Executing the Command to preview or execute the command.
See Publishing Commands to publish the command.
Previewing and Executing the Command
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-7).
Figure 14-7 Input Form
The input form heading displays the name of the command and comprises 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.
The following buttons are displayed in the input form:
•Preview—See how the command, including variables, looks before it is executed. The result is displayed in the Result tab; Figure 14-8 shows example output.
Figure 14-8 View Command Before Executing
•Execute—View the results of the actual command that is being executed. The result is displayed in the Result tab as shown in Figure 14-9.
Figure 14-9 Actual Command Results
•Close—Return to the opening window of the Command Builder wizard.
Step 3 Do one of the following:
•Click Preview to see how the command looks before it is executed.
•Click Execute to view the actual results of the command that is being executed.
Step 4 Close the input form to return to the Command Builder wizard.
Publishing Commands
After the command has been defined and tested on a specific instance of a managed element, it can be published and applied 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.
An example of an inheritance hierarchy is displayed below. In this example, the top level of the hierarchy is All devices and the lowest level of the hierarchy is Device XYZ.
Figure 14-10 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: The top row is the highest level of the hierarchy and the bottom row is the lowest level of the hierarchy.
The following information is displayed in the table:
•Exist—When a node in the hierarchy is selected, this indicates that a local variant of the command exists for that node.
•Registry Key—The hierarchy path, as defined in the registry.
Table 14-3 describes the tools that are displayed in the Hierarchy Manager dialog box.
Table 14-3 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.
|
The following button is displayed in the Hierarchy Manager dialog box:
•Close—Closes the Hierarchy Manager dialog box without publishing the command.
Step 3 Select the required node in the hierarchy from which 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.
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.
Beginning with Cisco ANA 3.6.5, 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 no longer displayed in the Command Builder table.
Exporting and Importing Commands
Command Builder enables you to export (save) a full command definition to a file. The command definition can be imported (copied) later to another managed element.
In addition, you can export and import a full command definition to a file and publish it to multiple places in the Hierarchy Manager window.
See the following topics for more information:
•Exporting Commands
•Importing Commands
Exporting Commands
To export commands:
Step 1 In the Command Builder wizard, select the command that you want to export. You cannot select multiple commands to export.
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 version that you want to export in the table of the Export window 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
Beginning with Cisco ANA 3.6.5, you can import multiple commands at a time as long as all of the commands are associated with the same VNE.
To import commands:
Step 1 In 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.
Reviewing the 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 EventVision application. For more information about EventVision, see the Cisco Active Network Abstraction 3.6.5 User Guide.
Closing Command Builder
When you have finished working with Command Builder, close the Command Builder wizard by clicking Close.
