You can access the FortiMail CLI commands via SSH, Telnet, or direct serial connection.
Local serial access is required in some cases. For example:
- If you are installing your FortiMail 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.
- 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.
The following recipe details how to connect to your FortiMail unit through a local serial console connection and then quickly goes over some initial FortiMail setup using the CLI.
Connecting to the FortiMail serial console |
|
Local console connections to the CLI are formed by directly connecting your management computer to the FortiMail unit, using its DB-9 or RJ-45 console port. Requirements
Note: To connect to FortiMail CLI using a local serial console connection
|
|
Basic CLI configurations |
|
Once you’ve physically connected your computer to the FortiMail unit, you can configure the basic FortiMail system settings through the CLI. If you require more information on other CLI commands, see the FortiMail CLI Guide. To change the admin password:
To change the operation mode:
To configure the interface IP address:
To configure the system route/gateway:
To configure the DNS servers:
To configure the NTP time synchronization:
To configure the SNMP v3 user settings:
|
The post FortiMail Serial Console Connection and Configuration appeared first on Fortinet Cookbook.