Using the CLI : Connecting to the CLI using a local console : Connecting to the CLI using a local console
Connecting to the CLI using a local console
Local console connections to the CLI are formed by directly connecting your management computer or console to the FortiADC appliance, using its DB-9 console port.
Requirements
• A computer with an available serial communications (COM) port
• Console cable (RJ-45-to-DB-9 or null modem cable) included in your FortiADC package
• Terminal emulation software such as
PuTTY To connect to the CLI using a local console connection
1. Using the null modem or RJ-45-to-DB-9 cable, connect the FortiADC appliance’s console port to the serial communications (COM) port on your management computer.
2. On your management computer, start PuTTY.
3. In the Category tree on the left, go to Connection > Serial and configure the following:
Serial line to connect to | COM1 (or, if your computer has multiple serial ports, the name of the connected serial port) |
Speed (baud) | 9600 |
Data bits | 8 |
Stop bits | 1 |
Parity | None |
Flow control | None |
4. In the Category tree on the left, go to Session (not the sub-node, Logging) and from Connection type, select Serial.
5. Click Open.
6. Press the Enter key to initiate a connection.
The login prompt appears.
7. Type a valid administrator account name (such as admin) then press Enter.
8. Type the password for that administrator account and press Enter. (In its default state, there is no password for the admin account.)
The CLI displays the following text, followed by a command line prompt:
Welcome!
You can now enter CLI commands, including configuring access to the CLI through SSH or Telnet.