Question 810
At the Elmhurst network modernization program, several managed switches disconnect immediately after a FortiGate version upgrade. Which underlying issue most directly explains this situation?
Explanation
Correct Answer
The evidence indicates that an incompatible controller and switch software combination can disrupt FortiLink management. The appropriate response is to check FortiOS and FortiSwitchOS version compatibility before changing discovery parameters and demonstrate that a pilot switch reconnects reliably after moving to a documented supported release combination.
Incorrect Answers
A redundant path cannot preserve operation if the topology enters an unsupported loop or multiple failures. That is not the mechanism that accounts for the stated failure at the Elmhurst network modernization program.
The offered principle is: The DHCP failure could occur before relay or after server response and needs packet-level isolation. In the source material it is associated with: The DHCP failure could occur before relay or after server response and needs packet-level isolation. This case has a different controlling cause: An incompatible controller and switch software combination can disrupt FortiLink management. Its keyed mechanism is: An incompatible controller and switch software combination can disrupt FortiLink management.
Although missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS, the presented symptoms do not support that as the primary cause; they indicate that an incompatible controller and switch software combination can disrupt FortiLink management. For the Elmhurst network modernization program, the direct corrective action is to check FortiOS and FortiSwitchOS version compatibility before changing discovery parameters.