FCSS_LED_AR-7.6 · Question #18
Refer to the exhibits. You are adding a new FortiSwitch to FortiGate for management. All necessary settings have been configured on FortiGate, but FortiSwitch remains offline. The cabling has been…
The correct answer is A. The DHCP server setting vci-string is misconfigured. On FortiLink, FortiGate's built-in DHCP server is what gives FortiSwitch its IP so it can come under management. For automatic FortiSwitch onboarding, the DHCP server is usually set with: set vci-match enable set vci-string "FortiSwitch" "FortiExtender" In the exhibit, the DHCP…
Question
Refer to the exhibits. You are adding a new FortiSwitch to FortiGate for management. All necessary settings have been configured on FortiGate, but FortiSwitch remains offline. The cabling has been verified and is correctly connected. Which misconfiguration might be preventing FortiGate from detecting FortiSwitch?
Exhibits
Options
- AThe DHCP server setting vci-string is misconfigured.
- BThe Fortilink interface has the wrong interface member.
- CThe Fortilink interface setting ip-managed-by-fortiipam must be enabled.
- DThe Fortilink interface setting type must be physical.
How the community answered
(35 responses)- A60% (21)
- B23% (8)
- C11% (4)
- D6% (2)
Explanation
On FortiLink, FortiGate's built-in DHCP server is what gives FortiSwitch its IP so it can come under management. For automatic FortiSwitch onboarding, the DHCP server is usually set with: set vci-match enable set vci-string "FortiSwitch" "FortiExtender" In the exhibit, the DHCP server for fortilink has: set vci-match enable set vci-string "FortiExtender" Because theVCI string doesn't include "FortiSwitch", DHCP offers are only sent to clients whose Vendor Class Identifier matchesFortiExtender. The FortiSwitch never receives an IP, so it
Topics
Community Discussion
No community discussion yet for this question.