Troubleshooting Tip: When it is not possible to configure interfaces with Virtual Hardware Switch
Description
This article provides some areas to check when the following message is seen after trying to configure a virtual hardware switch:
FGT1240B (port) # edit port30
The interface port30 is in use
node_check_object fail! for name port30
value parse error before 'port30'
Command fail. Return code -23
The interface port30 is in use
node_check_object fail! for name port30
value parse error before 'port30'
Command fail. Return code -23
Scope
FortiOS v5.0 and later.
Solution
Check the following items before configuring a virtual hardware switch:
- No IP address is assigned to the interface.
- No firewall policy uses the interface.
- No static route is configured on the interface.
- No HA heartbeat interface is configured on the interface.
Check the references in the CLI if GUI access is not available:
diagnose sys cmdb refcnt show <path.object.mkey>
Or:
show full-configuration | grep -f port30
Example:
diagnose sys cmdb refcnt show system.interface.name port30
entry used by table system.interface:name 'VPN_Winds_1'
entry used by table vpn.ipsec.phase1-interface:name 'VPN_Winds_1'
entry used by child table dstintf:name 'port30' of table firewall.policy:policyid '1'
entry used by child table dstintf:name 'port30' of table firewall.policy:policyid '2'
entry used by table router.static:seq-num '1'
The opposite situation can be observed when trying to configure, i.e., the HA heartbeat interface with the port that is currently being used by the virtual hardware switch. To resolve this issue, it is necessary to remove the required port from the virtual switch port list configuration before assigning this port as an HA heartbeat interface.
Note:
It is not possible to configure a virtual hardware switch with interfaces that have been configured as HA heartbeat interfaces by default.