Using the CLI : Connecting to the CLI
 
Connecting to the CLI
You can access the CLI in two ways:
Locally — Connect your computer directly to the FortiVoice unit’s console port.
Through the network — Connect your computer through any network attached to one of the FortiVoice unit’s network ports. The network interface must have enabled Telnet or SSH administrative access.
Local access is required in some cases.
If you are installing your FortiVoice unit 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 may only be able to connect to the CLI using a local serial console connection. See the FortiVoice Setup and Administration Guide.
Restoring the firmware utilizes a boot interrupt. Network access to the CLI is not available until after the boot process has completed, 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 Telnet on the network interface through which you will access the CLI.
This section includes:
Connecting to the CLI using a local console
Enabling access to the CLI through the network (SSH or Telnet)
Connecting to the CLI using SSH
Connecting to the CLI using Telnet