
The Run Command tab allows Organization-Admins to execute ad-hoc CLI commands on the managed devices or clusters and view the responses in the A10 Control GUI. It provides options to save commands as templates, use frequently used commands, and leverage CLI templates for efficient execution.
The following panels are available under the Run Command tab:
| Panel | Description | |||
|---|---|---|---|---|
|
Command Editor |
Enter CLI commands and access the frequently used commands or CLI templates.
|
|||
|
Select Device and Partition |
Search and select the devices or clusters where the commands will run. |
|||
|
Run Command History (Recent n) |
View executed commands, filter by CLI template name, refresh history, and expand command details. |
To execute a CLI command, perform the following steps:
On the Run Command tab, enter the required command in the Command Editor.
Example: show disk, show ip, show version.
Save the command as a snippet:
(Optional) Use predefined or past commands:
Choose the target device(s) or cluster partition(s) in the Select Device and Partition panel:
Click Run on Selected Device & Partition to execute the command or click Clear to reset the editor for new command.
Review the results in the Run Command History panel where 'n' is the number of most recent command executions displayed in the panel.
| Column | Description |
|---|---|
|
Commands |
The CLI command that was executed. |
|
CLI Template Name |
The template applied. Displays N/A if no template is associated. |
|
Device : Partition |
The device and partition on which the command was executed. |
|
Timestamp |
The date and time when the command was executed. |
Expand a command to view the following additional details:
| Field | Description |
|---|---|
|
User |
Administrator who executed the command. |
|
Duration |
Time taken to execute the command. |
|
Commands |
The command executed. |
|
Response |
The CLI output. Use the search option to find specific keywords within the response. |
| NOTE: | If a command fails, all subsequent commands in the batch are skipped. Remove the failed commands and re-run the batch. |