FortiSwitch
FortiSwitch: secure, simple and scalable Ethernet solutions
pprince
Staff
Staff
Article Id 356951
Description

This article describes how to troubleshoot the 'Port1 not enabled' issue when FortiSwitch is offline on FortiSwitch Manager.

 

Below is an example of the error: 

 

FSWMVMTM24000XXX # execute switch-controller get-conn-status

 

Managed-devices in current vdom root:

FortiLink interface : port1

SWITCH-ID VERSION STATUS FLAG ADDRESS JOIN-TIME NAME

S424ENTF2300XXXX N/A Authorized/Down 3 N/A -


Flags: C=config sync, U=upgrading, S=staging, D=delayed reboot pending, E=config sync error, 3=L3
Managed-Switches: 1 (UP: 0 DOWN: 1 MAX: 10000)

FSWMVMTM24000XXX # execute switch-controller diagnose-connection S424ENTF230XXXX


Fortilink interface ... OK
port1 enabled

NTP server ... FAIL
port1 not enabled
NTP server sync ... OK


synchronized: yes, ntpsync: enabled, server-mode: disabled

ipv4 server(ntp2.fortiguard.com) 208.91.112.62 -- reachable(0xff) S:3 T:119 selected
server-version=4, stratum=2
reference time is eadb398f.878b502f -- UTC Sun Nov 10 13:54:23 2024
clock offset is 0.333997 sec, root delay is 0.207062 sec
root dispersion is 0.014023 sec, peer dispersion is 1418 msec

ipv4 server(ntp1.fortiguard.com) 208.91.112.63 -- reachable(0xff) S:3 T:127
server-version=4, stratum=2
reference time is eadb398f.878b502f -- UTC Sun Nov 10 13:54:23 2024
clock offset is 0.336433 sec, root delay is 0.207062 sec
root dispersion is 0.014038 sec, peer dispersion is 1168 msec

ipv4 server(ntp2.fortiguard.com) 208.91.112.60 -- reachable(0xff) S:3 T:143
server-version=4, stratum=2
reference time is eadb398f.878b502f -- UTC Sun Nov 10 13:54:23 2024
clock offset is 0.337116 sec, root delay is 0.207062 sec
root dispersion is 0.014053 sec, peer dispersion is 1311 msec

ipv4 server(ntp1.fortiguard.com) 208.91.112.61 -- reachable(0xff) S:3 T:107
server-version=4, stratum=2
reference time is eadb398f.878b502f -- UTC Sun Nov 10 13:54:23 2024
clock offset is 0.336218 sec, root delay is 0.207062 sec
root dispersion is 0.014023 sec, peer dispersion is 828 msec


HA mode ... disabled

 

No CAPWAP IP address retrieved for FortiSwitch S424ENTF23004620
CAPWAP
Remote Address : N/A
Status ... Idle

 

Scope All versions of  FortiSwitch and FortiSwitch Manager.
Solution

Refer to the documentation (fortiswitch-manager/7.2.4/administration-guide) to configure FortiSwitch over a layer-3 network to manage FortiSwitch on FortiSwitch Manager.

 

Login to the FortiSwitch Manager CLI and configure the following settings:

 

config system ntp
    set interface "port1"
end

 

Use the GUI to configure the same or verify the setting that Port1 is added as the listening interface for NTP:

 

Go to Systems -> Settings -> Listen on Interface -> add Port1.

 

Screenshot 2024-11-11 231852.png

Note: The FortiSwitch Manager VM uses port1 to communicate by default and must be configured with an IP address and administrative access.