Using the CLI
Using the CLI
The command-line interface (CLI) is an alternative to the web UI.
You can use either interface or both to configure the FortiADC appliance. In the web UI, you use buttons, icons, and forms, while, in the CLI, you either type text commands or upload batches of commands from a text file, like a configuration script.
If you are new to Fortinet products, or if you are new to the CLI, this section can help you to become familiar.
Connecting to the CLI
You can access the CLI in two ways:
Locally — Connect your computer, terminal server, or console directly to the console port.
Through the network — Connect your computer through any network attached to one of the network ports. To connect using an Secure Shell (SSH) or Telnet client, enable the network interface for Telnet or SSH administrative access. Enable HTTP/HTTPS administrative access to connect using the CLI Console widget in the web UI.
Local access is required in some cases.
If you are installing your FortiADC appliance for the first time and it is not yet configured to connect to your network, unless you reconfigure your computer’s network settings for a peer connection, you might only be able to connect to the CLI using a local console connection. See the FortiADC Handbook.
Restoring the firmware utilizes a boot interrupt. Network access to the CLI is not available until after the boot process completes, and therefore local CLI access is the only viable option.
Before you can access the CLI through the network, you usually must enable SSH and/or HTTP/HTTPS and/or Telnet on the network interface through which you will access the CLI.