FCSS_NST_SE-7.4 · Question #42
Which three common FortiGate-to-collector-agent connectivity issues can you identify using the FSSO real-time debug? (Choose three.)
The correct answer is B. Inability to reach IP address of the collector agent. C. Refused connection. Potential mismatch of TCP port. D. Mismatched pre-shared password. When you enable FSSO real‑time debug you'll see explicit socket errors if the FortiGate can't reach the collector's IP (e.g. timeout or "no route to host"), which tells you the agent isn't reachable. If the TCP port is wrong or the listener isn't running, you'll see "Connection…
Question
Which three common FortiGate-to-collector-agent connectivity issues can you identify using the FSSO real-time debug? (Choose three.)
Options
- ALog is full on the collector agent.
- BInability to reach IP address of the collector agent.
- CRefused connection. Potential mismatch of TCP port.
- DMismatched pre-shared password.
- EIncompatible collector agent software version.
How the community answered
(37 responses)- A19% (7)
- B73% (27)
- E8% (3)
Explanation
When you enable FSSO real‑time debug you'll see explicit socket errors if the FortiGate can't reach the collector's IP (e.g. timeout or "no route to host"), which tells you the agent isn't reachable. If the TCP port is wrong or the listener isn't running, you'll see "Connection refused" in the debug output, pinpointing a port mismatch. And if the configured pre‑shared secret doesn't match, the logs show an authentication failure or "invalid key" message, clearly indicating a password mismatch. These three conditions - unreachable IP, refused connection, and bad PSK - are all directly diagnosable via the real‑time debug.
Topics
Community Discussion
No community discussion yet for this question.