Skip to main content
vchauhan
Staff
Staff
September 18, 2025

Troubleshooting Tip: Resolving the error 'Cannot set management port 'port2' as the cluster internal communication port'

  • September 18, 2025
  • 0 replies
  • 173 views
Description

This article describes an issue encountered when attempting to configure port2 (or any other port) as the cluster’s internal communication port while it is already configured as an 'admin-port'.

Scope FortiSandbox.
Solution

To illustrate the configuration and resulting error, consider the following example:

 

hc-settings -sc -tM -nPrimaryA -cTestHCsystem -ppassw0rd -iport2
ERROR: Cannot set management port 'port2' as cluster internal communication port.

 

The command output below shows the current interface configuration:

 

> show
Configured parameters:
port1 IPv4 IP: 10.5.62.51/20 MAC: 00:90:0B:66:E4:CF
MTU: 1500
speed: 1000Mb/s
duplex: full
port2 IPv4 IP: 10.84.14.51/20 MAC: 00:90:0B:66:E4:D0
MTU: 1500
speed: 1000Mb/s
duplex: full
port3 IPv4 IP: 10.5.30.51/20 MAC: 00:90:0B:66:E4:D1
MTU: 1500
speed: 1000Mb/s
duplex: full
port4 IPv4 IP: 10.101.14.51/20 MAC: 00:90:0B:66:E4:D2
MTU: 1500
speed: 1000Mb/s
duplex: full
port5 IPv4 IP: 192.168.4.99/24 MAC: 00:90:0B:66:F5:A9
MTU: 1500
speed: 10000Mb/s
duplex: full
port6 IPv4 IP: 192.168.5.99/24 MAC: 00:90:0B:66:F5:AA
MTU: 1500
speed: 10000Mb/s
duplex: full
IPv4 Default Gateway: 10.5.63.254
Administration interface(s): port1 port2 port4
API interface(s):

 

To resolve this error, remove the admin-port assignment from port2 before designating it as the internal cluster communication port. This can be done by executing the following command:

 

unset admin-port port2

 

Once this is done, port2 can be successfully configured for internal cluster communication.