CLI Command Generation

Command generation now become easier with XML based Command Set and Data Set. The commands can be configured in CLI Browser to have a list of commands in the CLI tree.

The Command Structure: The Command Set basically has a list of Command templates. Each command template represents a particular CLI command for a specific device. The command can be generally represented as follows:

Where,

<command> : Is the name of the command. For example in UNIX OS, listing the directory <command> can take the value 'ls'. Following are a few examples of various commands that are used in a UNIX system.

• netstat

• who

• pwd

<object>: Represents the object on which the command takes effect. In UNIX OS for the command 'ls' the value of the object can be the directory for which the contents are to be listed. Objects in turn can have sub objects, which can have more sub objects and so on. The following are a few examples on a UNIX system.

• Directory name for an 'ls' command.

• eth0 (Ethernet interface for which the statistics is required for the netstat command)

• User name or group name for user/group management commands.

<parameters>: Represents the parameters for the command. The parameters can also occur in the form <parameter name>=<value> in certain commands.

<options> :It could be the various options that the command can accept and configuration parameters.

The following are some examples:

• -l for the 'ls' command (long listing)

• -u for displaying the udp statistics for a netstat command

The Command Generation section includes the following topics :

Message Set API topic contains classes for constructing commands based on a Command set and Data Set.

Command Set: This is used to define a set of Command Templates for a particular device, which is an XML based template. All the possible commands (configuration, monitoring commands, etc.) for a particular device can be included in this file.