Connecting to the FortiRecorder CLI
For initial installation, you can connect to the CLI from your management computer, either:
-
Through the network — Connect your computer either directly (a peer connection) or through any network attached to one of the FortiRecorder unit’s network ports.
- Locally — Connect your computer directly to the FortiRecorder unit’s serial console port.
Local serial console connection is required if:
-
Restoring the firmware. This utilizes a boot interrupt. Network access to the CLI is not available until after the boot process has completed, and therefore local serial access to the CLI is the only method that you can use.
-
Installing your FortiRecorder unit for the first time, only if don't want to reconfigure your computer's network settings for a peer connection. (In its factory default settings, during initial setup, FortiRecorder is not yet configured to connect to your network. Peer connection is the only method that you can use until you configure the network interfaces.)
Command syntax for FortiRecorder is similar to other Fortinet products.
CLI connection via SSH
By default, SSH and HTTPS administrative access are enabled so that you can connect to the CLI during initial setup.
After initial setup, if you will connect using Telnet client, then enable SSH or Telnet on the network interface. If you will connect using the Dashboard > Console in the GUI, then enable HTTPS administrative access.
Requirements
- a computer with an Ethernet port
- a crossover Ethernet cable
- an SSH client, such as PuTTY
|
The following procedure uses PuTTY. Steps may vary with other SSH clients. |
To connect to the CLI using an SSH connection
-
On your management computer, configure the Ethernet port with the static IP address 192.168.1.2 and a netmask of 255.255.255.0.
-
Using the Ethernet cable, connect your computer's Ethernet port to the FortiRecorder unit's port1.
-
Verify that the FortiRecorder unit is powered on.
-
On your management computer, start PuTTY.
-
In Host Name (or IP Address), type
192.168.1.99. -
In Port, type 22.
-
From Connection type, select SSH.
-
Click Open.
The SSH client connects to the FortiRecorder unit. The SSH client might display a warning if this is the first time you are connecting to the FortiRecorder unit and its SSH key is not yet recognized by your SSH client, or if you have previously connected to the FortiRecorder unit but it used a different IP address or SSH key. If your management computer is directly connected to the FortiRecorder unit with no network hosts between them, this is normal.
Click Yes to verify the fingerprint and accept the FortiRecorder unit's SSH key. You will not be able to log in until you have accepted the key.
The CLI displays a login prompt.
-
Type
adminand press Enter twice. (In its factory default state, there is no password for this account.)
CLI connection via local serial console
Requirements
- a computer with a serial communications (COM) port
- the RJ-45-to-DB-9 serial or null modem cable included in your FortiRecorder package
- terminal emulation software, such as PuTTY
|
|
The following procedure describes connection using PuTTY. Steps may vary with other terminal emulators. |
To connect to the CLI using a local serial connection
-
Using the console cable, connect the FortiRecorder unit’s console port to the serial communications (COM) port on your management computer.
- On your management computer, start PuTTY.
- In the Category tree on the left, go to Connection > Serial and configure the following:
- In the Category tree on the left, go to Session (not the sub-node, Logging) and from Connection type, select Serial.
- Click Open.
- Press the Enter key to initiate a connection.
- Type
adminand press Enter twice. (In the factory default state, there is no password for this account.)
|
Serial line to connect to |
COM1 (or, if your computer has multiple serial ports, the name of the connected serial port) |
|
9600 |
|
|
Data bits |
8 |
|
Stop bits |
1 |
|
None |
|
|
None |