CLI Overview

The Guardium® command line interface (CLI) is an administrative tool that allows for configuration, troubleshooting, and management of the Guardium system.

Documentation Conventions

All CLI command examples are written in courier text (for example, show system clock).

To illustrate syntax rules, some command descriptions use dependency delimiters. Such delimiters indicate which command arguments are mandatory, and in what context. Each syntax description shows the dependencies between the command arguments by using special characters:

CLI Command Usage Notes®

Accessing the CLI

An administrator can access the CLI though:

Physical Console Access

Interactive access to the Guardium appliance is through the serial port or the system console.

PC keyboard and monitor – A PC video monitor can be attached to either the front panel video connector or the video connector on the back of the appliance.

A PC keyboard with a PS/2 style connector can be attached to the PS/2 connector on the back of the appliance. Alternatively, a USB keyboard can be connected to the USB connectors located at the front or back of the appliance.

Serial port access – Using a NULL modem cable, connect a terminal or another computer to the 9-pin serial port at the back of the appliance. The terminal or a terminal emulator on the attached computer should be set to communicate as 19200-N-1 (19200 baud, no parity, 1 stop bit).

A login prompt displays once the terminal is connected to the serial port, or the keyboard and monitor are connected to the console. Enter cli as the user name, and continue with CLI Login.

Network SSH Access

Remote access to the CLI is available on the management IP address or domain name, using an SSH client. SSH clients are freely or commercially available for most desktop and server platforms. A Unix SSH connect command to log in as the cli user might look like this:
ssh –l cli 192.168.2.16

The SSH client may ask you to accept the cryptographic fingerprint of the Guardium appliance. Accept the fingerprint to proceed to the password prompt.

Note: If, after the first connection, you are asked again for a fingerprint, someone may be trying to induce you to log into the wrong machine.

CLI Login

Access to the CLI is either through the admin CLI account cli or one of the five CLI accounts (guardcli1,...,guardcli5). The five CLI accounts (guardcli1,...,guardcli5) exist to aid in the separation of administrative duties.

Access to the GuardAPI, which is a set of CLI commands to aid in the automation of repetitive tasks, requires the creation of a user (GUI username/guiuser) by access manager and giving those accounts either the admin or cli role. Proper login to the CLI for the purpose of using GuardAPI requires the login with one of the five CLI accounts (guardcli1,...,guardcli5) and an additional login with guiuser by issuing the 'set guiuser' command. See GuardAPI Reference Overview or  Set guiuser Authentication for additional information.

Password Hardening

In order to meet various auditing and compliancy requirements the following password enforcements will be in effect for CLI accounts:

Limited CLI commands during maintenance of internal database

CLI has three sets of commands - general commands, specialized support commands, and recovery commands. Support commands are to used by Technical Support to analyze the system. Recovery commands are to recover the system when the database is down.

The initial CLI login is:
Welcome to CLI - your last login was <date>

The welcome message will add further information if the internal database is down due to maintenance or during an upgrade.

If this is the case, the number of CLI commands available will be limited.
The internal database on the appliance is currently down and CLI will be working
in "recovery mode";  only a limited set of commands will be available.
The CLI commands that available for use during recovery mode are as follows:
support reset-password root
restart mysql
restart stopped_services
restart system
restore pre-patch-backup
restore system