Table Of Contents
Getting Started with the Command Builder
Opening the Command Builder
Command Builder Wizard
Menu Bar
File Menu
Tools Menu
Toolbar
A Workflow To Define a New Command
Creating or Editing a Command
Editing a Command
Defining the User Input Parameters
Defining a Combo Field Type
Defining ANA Macro Language Script Lines
Defining Bean Shell Script Lines
Previewing and Executing the Command
Publishing Commands
Deleting a Command
Importing and Exporting a Command
Reviewing the Command History
Closing the Command Builder
Getting Started with the Command Builder
This chapter describes the Command Builder wizard's working environment and how to access the Command Builder tools. In addition, it describes how to create, execute, and publish a command.
•
Opening the Command Builder—Describes how to open the Command Builder wizard.
•Command Builder Wizard—Describes the Command Builder wizard, including, the toolbar and menu options.
•A Workflow To Define a New Command—Describes the steps required to create a new command.
•Creating or Editing a Command—Describes how to start creating a command. In addition, it describes how to edit a command.
•Defining the User Input Parameters—Describes how to define the input parameters and properties, which will be used when the command is executed.
•Defining ANA Macro Language Script Lines—Describes how to define ANA Macro Language script lines.
•Defining Bean Shell Script Lines—Describes how to define Bean Shell script lines.
•Previewing and Executing the Command—Describes how to preview and/or execute a command.
•Publishing Commands—Describes how to publish a command to one or more locations across the inheritance hierarchy.
•Deleting a Command—Describes how to delete a local instance of a command.
•Importing and Exporting a Command—Describes how to export and import commands between managed elements.
•Reviewing the Command History—Describes how to view the command's execution history.
•Closing the Command Builder—Describes how to close the Command Builder wizard.
Opening the Command Builder
This section provides instructions for launching the Command Builder wizard. The 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 will be 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 the Command Builder:
Step 1 Right-click on a managed element in the tree pane or context pane of the NetworkVision window.
Note For more information about the NetworkVision window, see the Cisco Active Network Abstraction NetworkVision User Guide.
or
Open the Inventory window for the required managed element and right-click on the required VNE inventory item.
Note For more information about the Inventory window, see the Cisco Active Network Abstraction NetworkVision User Guide.
Step 2 Select Management | Command Builder from the shortcut menu. The Command Builder wizard is displayed.
Command Builder Wizard
An example of the Command Builder wizard is displayed below.
Figure 14-1 Command Builder Wizard
The Command Builder wizard consists of the following:
•The table of commands for the selected managed element or network element, as described below.
•Menu Bar
•Toolbar
The Command Builder wizard displays a table of all the existing commands that are available for the selected managed element and/or network element. The Command Builder enables the user to:
•Add a new command, which enables the user 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/or 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, by selecting a port object, the port's properties like 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 the 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 in order to update the higher-level definition.
A table can be sorted:
•According to a column by clicking on the required column heading. The 
icon is displayed next to the selected column heading.
•In ascending or descending order by clicking on the column heading. A triangle is displayed next to the selected column heading.
Clicking on a red triangle displayed in a cell expands the cell to display all the information in the cell.
The Location field displays the number of selected rows and the total number of rows in the table, for example, 2/16 Selected. In addition, it displays the location of the selected row(s) in the table, for example, Line 3.
Menu Bar
This section provides a description of each option available in the Command Builder menus. The following menus are available:
•File Menu
•Tools Menu
File Menu
The File menu provides the following options:
•New Element—Enables the user to create a new command definition. For more information see Creating or Editing a Command.
•Edit Element—Enables the user to edit an existing command definition. For more information see Editing a Command.
•Delete Element—Enables the user to delete existing locally defined commands, namely, commands that have not yet been published. For more information see Deleting a Command.
Tools Menu
The Tools menu provides the following options:
•Export Element—Enables the user to save a full command definition to a file that can later be imported to another managed element. For more information see Importing and Exporting a Command.
•Import Element—Enables the user to copy a full command definition from an exported file and import this command to another managed element. For more information see Importing and Exporting a Command.
•Hierarchy Manager—Enables the user to 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—Enables the user to preview and/or execute the command. For more information see Previewing and Executing the Command.
Toolbar
The following buttons are displayed in the Command Builder wizard:
Button
|
Description
|
|
New Element—Enables the user to create a new command definition. For more information see Creating or Editing a Command.
|
|
Edit Element—Enables the user to edit an existing command definition. For more information see Editing a Command.
|
|
Delete Element—Enables the user to delete commands that exist locally, namely, commands that have not yet been published. For more information see Deleting a Command.
|
|
Export Element—Enables the user to save a full command definition to a file that can later be imported to another managed element. For more information see Importing and Exporting a Command.
|
|
Import Element—Enables the user to copy a full command definition from an exported file and import this command to another managed element. For more information see Importing and Exporting a Command.
|
|
Hierarchy Manager: Enables the user to 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: Enables the user to preview and/or execute the command. For more information see Previewing and Executing the Command.
|
The Close button closes the Command Builder wizard. For more information see Closing the Command Builder.
A Workflow To Define a New Command
The workflow below describes the steps required to define a new command definition using the Command Builder and the order in which they must be performed.
Figure 14-2 Define A New Command Workflow
At any point after the command has been defined, it can be tested, executed, and published to a wider scope of managed elements and/or network elements.
For more information about:
•Creating or editing a command, see Creating or Editing a Command.
•Defining the security access roles, see Creating or Editing a Command.
•Defining the input parameters, see Defining the User Input Parameters.
•Defining the script lines and saving the command, see Defining ANA Macro Language Script Lines for ANA Macro Language and Defining Bean Shell Script Lines for Bean Shell.
•Previewing and executing the command, see Previewing and Executing the Command.
•Publishing the command, see Publishing Commands.
•Deleting a command, see Deleting a Command.
•Importing and exporting a command, see Importing and Exporting a Command.
•Reviewing the command history, see Reviewing the Command History.
Creating or Editing a Command
The Command Builder enables the user 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, the user can edit an existing command. For information about editing an existing command see Editing a Command.
To create a command:
Step 1 Click New Element on the toolbar of the Command Builder wizard.
or
Select New Element from the File menu or shortcut menu.
The New Command dialog box is displayed.
Figure 14-3 New Command Dialog Box
The following information is displayed in the New Command dialog box:
•Name—The name identifying the command and this name is unique to the entire system.
•Menu Caption—The text that describes the command in the menu when launching the command, namely, the menu option.
•Menu Visible—Select this option to display the menu option in the NetworkVision shortcut menu or clear this option to hide the menu option from the user.
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 will be added or displayed.
•Context IMO—Displays the inventory object that is associated with the command (and exposes its data properties to the command). In a case where the inventory object has sub-objects, which do not appear in the inventory tree (for example, parameter-groups of a port), they will be listed in the dropdown list.
•Language—Select either ANA Macro Language (Simple mode) or Bean Shell (programmable mode/full scripting language).
•Protocol—Select the protocol:
–ANA Macro Language uses only Telnet.
–Bean Shell can use either Telnet or SNMP.
Note Cisco ANA provides a 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.
The Command Authorizations dialog box enables the user to specify which security access roles will be authorized to execute the command, namely:
•Administrator
•Configurator
•Operator Plus
•Operator
•Viewer
The following buttons are displayed in the Command Authorizations dialog box:
•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 role/s.
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
The user can edit an existing command definition and the command that is edited will affect 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.
Step 2 Click Edit Element on the toolbar of the Command Builder wizard.
or
Select Edit Element from the File menu or shortcut menu.
The Hierarchy Manager dialog box is displayed.
Note If user-friendly VNE names exist in the schema then the hierarchy manager table will display 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 3 Select the required version of the command from the hierarchy manager, and click Next. The Edit Command dialog box is displayed for the selected command.
Step 4 Edit the command as required by changing the existing information using the Command Builder wizard.
Step 5 Click Finish in the Script Lines dialog box to save the edited ANA Macro Language command.
or
Click Finish in the Bean Shell Script dialog box save the edited Bean Shell command.
Step 6 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
The Command Builder enables the user 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.
ANA Macro Language supports two types of script parameters. User-defined parameters and built-in parameters, both are replaced in runtime. All parameters (both built-in and user-defined ones) are available during command editing via a selection list.
For information about ANA Macro Language scripts see Defining 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 User Input Arguments Dialog Box
The following is the complete list of user-defined parameter properties that can be defined in the Add/Edit User Argument for x Command dialog box:
Property
|
Explanation
|
Name
|
Parameter name. Can contain only letters, numbers, "-" and "_". Unique within the script scope.
|
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 ANA Macro Language Script Lines.
Note Only input values that are valid for the selected Type will be accepted. These values are validated during runtime.
|
Width
|
Field width, in characters. Relevant for the Command Builder script execution window.
|
Visible
|
Select this option to show this parameter in the Command Builder script execution window or clear this option to hide the parameter from the user. In the case where 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.
|
The User Input Arguments dialog box Move Up and Move Down buttons enable the user to determine 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—The Add/Edit User Argument for x Command dialog box is displayed enabling the user to 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—The Add/Edit User Argument for x Command dialog box is displayed enabling the user to edit the selected input argument.
•Delete—Deletes the selected input argument from the User Input Arguments table.
•Prev—Displays the Command Authorizations dialog box.
•Next—Displays the Script Lines dialog box.
•Cancel—Returns to the opening window of the Command Builder wizard.
Step 2 Click New.
or
Select the input argument and 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 the Move Up or Move Down buttons to reorder the user-defined input parameters.
Step 5 Click Next to define:
•ANA Macro Language command, the Script Lines dialog box is displayed.
See Defining 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 the user to create a selection list (dropdown list) of the valid options that will be displayed in the combo box of the input form, for example, 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 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 (dropdown list) of the input form, for example, "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 Value and Label in their respective fields.
Step 4 Click Add. The entry (Value and Label) is added to the table.
Step 5 Repeat Step 3 and Step 4 to enter all the required entries.
Step 6 Click Close. The Add/Edit User Argument dialog box is displayed.
Defining ANA Macro Language Script Lines
The user can define the language of the script as either ANA Macro Language or Bean Shell. ANA Macro Language scripts are 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 (namely, built-in and user-defined ones) in script lines within dollar symbols, namely, $...$. For example, in a VRF configuration command, the input variable vrfName can be defined as ip vrf $vrfName$.
For information about ANA Macro Language scripts see Defining ANA Macro Language Script Lines.
To define ANA Macro Language script lines:
Step 1 In the User Input Arguments dialog box click Next. The Script Lines dialog box is displayed enabling the user to add or edit a script line, as displayed.
Figure 14-6 Script Lines Dialog Box
Note To view all the user-defined and built-in parameters in the Command Builder application press CTRL + Space 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 will be 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 the 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 and 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, namely, [...].
Note To view all the user-defined and built-in parameters in the Command Builder application press CTRL + Space 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 Wherever carriage returns are required in the command line the programmer must use &cr.
Note It is possible to use multiple pragmas in a single line, in which case all the pragmas will be analyzed. If the same type of pragma is repeated only the last one will be used.
Step 3 Define the Rollback and Fail Condition criterion (optional).
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 as follows:
•Blue—The command definitions are now being saved.
•Green—The command has been created/updated successfully.
•Red—The Command Builder wizard failed to create/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 and/or execute the command.
See Publishing Commands to publish the command.
Defining Bean Shell Script Lines
The user 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 (conditions, loops, external files, etc.).
For information about ANA Macro Language scripts see Defining 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 the user-defined and built-in parameters in the Command Builder application press CTRL + Space 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 Important: Unlike ANA Macro Language, in Bean Shell user arguments inventory properties should NOT be embedded within $...$ symbols.
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 will be 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 and 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 the 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 ANA Macro Language Script Lines.
Step 6 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 and/or execute the command.
See Publishing Commands to publish the command.
Previewing and Executing the Command
Command Builder enables the user to preview the command (including the variables) before it is executed. The input form is automatically generated and opened displaying all the user-defined input fields for the command. The 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 Click Run Command on the toolbar of the Command Builder wizard.
or
Select Run Command from the Tools menu or shortcut menu. The input form is generated and displayed.
Figure 14-7 Input Form
The input form heading displays the name of the command and is comprised of two tabs:
•The Input tab—Displays the input parameters.
•The Result tab—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—Enables the user to see how the command, including, the variables look before it is executed. The result is displayed in the Result tab, an example of which is displayed.
Figure 14-8 View Command Before Executing
•Execute—Enables the user to view the results of the actual command that is being executed. The result is displayed in the Result tab.
Figure 14-9 Actual Command Results
•Close—Returns to the opening window of the Command Builder wizard.
Step 3 Click Preview to see how the command looks before it is executed.
or
Click Execute to view the actual results of the command that is being executed.
Step 4 Close the input form and display 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 wider scope of managed elements in the network.
The Command Builder Hierarchy Manager dialog box enables the user to publish the command to one or more locations across the inheritance hierarchy (as defined in the system). In other words the user defines the scope where the command will 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, this 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 will override any variant of this command which is defined at a higher level, and will be 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 Click Hierarchy Manager on the toolbar of the Command Builder wizard.
or
Select Hierarchy Manager from the Tools menu or shortcut menu.
The Hierarchy Manager dialog box is generated and displayed.
Note If user-friendly VNE names exist in the schema then the hierarchy manager table will display 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.
The following tools are displayed in the Hierarchy Manager dialog box:
Button
|
Description
|
|
Copies the command from a selected node in the hierarchy in order to copy it to 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 in order to move it 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 to 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 the nodes, the command will be removed from the list in the main dialog 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 on the toolbar to copy or cut the command.
Step 5 Select the required 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 a Command
Commands created by the user are by default always created as a local instance. A command that is defined locally is selected in the Command Builder wizard. The user can only delete commands that exist locally, namely, commands that have not yet been published.
To delete a command:
Step 1 Select the command that you want to delete in the table of the Command Builder wizard.
Step 2 Click Delete Element on the toolbar of the Command Builder wizard.
or
Select Delete Element from the File menu or shortcut menu.
The command is deleted and no longer displayed in the Command Builder table.
Importing and Exporting a Command
Command Builder enables the user to export (save) a full command definition to a file. The command definition can be imported (copied) later to another managed element.
In addition, the user can export and import a full command definition to a file and publish it to multiple places in the Hierarchy Manager window.
To export a command:
Step 1 Select the command that you want to export in the table of the Command Builder wizard.
Step 2 Click Export Element on the toolbar of the Command Builder wizard.
or
Select Export Element from the Tools menu or shortcut menu.
The Export dialog box is displayed.
Step 3 Select the version that you want to export in the table of the Export window, by checking the checkbox 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.
To import a command:
Step 1 Shortcut on the required managed element in the tree pane or context pane of the NetworkVision window.
or
Open the Inventory window for the required managed element and shortcut on the required network element.
Step 2 Select Edit | Command Builder from the shortcut menu. The Command Builder wizard is displayed.
Step 3 Click Import Element on the toolbar of the Command Builder wizard.
or
Select Import Element from the Tools menu or shortcut menu.
The Import Element dialog box is displayed.
Step 4 Browse to the directory and command that you want to import.
Step 5 Click Open. The Import elements window is displayed.
Step 6 Select the version that you want to import in the table of the Import Elements window. The version is selected in the table.
Step 7 Click OK. The Command Builder wizard is displayed.
Step 8 Click Close. The command is imported to the selected managed element or network element 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 EventVision User Guide.
Closing the Command Builder
When the user has finished working with the Command Builder the user can close the Command Builder wizard.
To close the Command Builder, click Close. The Command Builder wizard is closed.
