Technical Tip: FortiNAC displays FortiSwitch port status as down in Link Mode integration

Description

This article describes the steps to resolve the FortiSwitch port status down issue. The user may encounter this issue when the FortiSwitch port status is not updating correctly, and the steps outlined in this article will help to troubleshoot and resolve the problem.

Scope

FortiNAC, FortiGate, REST API, FortiSwitch.

Solution

To resolve the FortiSwitch port status down issue, follow these steps:

Enable debugging on FortiNAC CLI:

execute enter-shell 
device -ip <FortiGate IP address> -setAttr -name DEBUG -value "ForwardingInterface TelnetServer"

From the Network Inventory, right-click the switch and select Resync interfaces, validate credentials, and L2 poll. Repeat this step several times and note the timestamps.

Collect the debug logs from the FortiNAC GUI. See Technical Tip: How to get a debug log report from FortiNAC-CA or FortiNAC-Manager.

Disable debugging on the FortiNAC CLI:

execute enter-shell 
device -ip <FortiGate IP address> -setAttr -name DEBUG -value "ForwardingInterface TelnetServer"

In the CLI logs and output.master, the following error will appear:

[PollThread-trap5] INFO yams - PollThread-trap5 request uri = https://10.10.10.10:10443/api/v2/monitor/user/device/query

[PollThread-trap5] INFO yams - PollThread-trap5 request details = https://10.10.10.10:10443/api/v2/monitor/user/device/query?filter=is_online==true&timestamp_to=1424525646&vdom=*&query_type=unified_latest

[PollThread-trap5] INFO yams - PollThread-trap5 request status = 500, response =
HttpResponseProxy{HTTP/1.1 500 Internal Server Error [X-Frame-Options: SAMEORIGIN, Content-Security-Policy: frame-ancestors 'self', Strict-Transport-Security: max-age=63072000, date: DDD, DD MM YYYY HH:MM:SS GMT, cache-control: no-cache, must-revalidate, content-length: 198, content-type: application/json, Connection: keep-alive] ResponseEntityProxy{[Content-Type: application/json,Content-Length: 198,Chunked: false]}}

[PollThread-trap5] INFO yams - PollThread-trap5 request response = null

[PollThread-trap5] INFO yams - PollThread-trap5 readAPI result for readClientsFW = null

[PollThread-trap5] INFO yams - PollThread-trap5 Fortigate:readForwardingDatabase failed reading FW entries for 10.10.10.10

HTTP 500 means FortiNAC successfully reached the remote server, but the server failed while processing the request.

Execute the following command on the FortiGate to clear the sessions and resolve the issue:

diagnose user-device-store unified clear