FortiNAC
NOTE: FortiNAC is now named FortiNAC-F. For post-9.4 articles, see FortiNAC-F. FortiNAC is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks.
cmaheu
Staff
Staff
Article Id 264502
Description

This article describes the grab-device-debug report as one utility that automates the collection of information to diagnose a device integration-related behavior such as:

  • L2 polling.
  • L3 polling.
  • Validating credentials.
  • VLAN reading.
  • VLAN switching.

 

Note:

Ensure the basic troubleshooting steps have been performed first. Refer to the applicable KB articles:

Troubleshooting Poll failures

Troubleshooting CLI credential failure

Unable to read VLANs from the device

Troubleshooting wireless clients moved to the wrong VLAN

VLANs not changing on a wired switch 

 

This report may be required in addition to collecting the logs generated using the Download Logs/grab-log-snapshot utility.

Scope FortiNAC v9.2.7, v9.4.2 and greater
Solution

CLI Instructions (CentOS appliance):

  1.  Log into the CLI of the appliance as root.
  2.  Execute the script:

 

grab-device-debug <device IP address>


The script will collect and zip a number of files. This will take several minutes. The resulting zip file (<device IP address>.debug.tar.gz) is located in /bsc/logs directory.

 

Example:

 

> grab-device-debug 10.12.240.5
Debug script grab-device-debug starting for 10.12.240.5
Getting Device Info
Getting Dump Ports
Getting Device Tree
Enabling global debug: SnmpV1 TelnetServer BridgeManager ClientInterface DeviceInterface TrapHandler
Enabling device model debug:ForwardingInterface
Capturing output.master data
Running UpdateClients
Running ReadForwardingTbl
Running ReadArpCache
Sleeping for 15 seconds to let things run
Disabling debug and stopping logging
Capturing FNAC Version

*************************************
Creating debug file tar -cvzf with:
FNACversion.txt
10.12.240.5.device.txt
10.12.240.5.ports.txt
10.12.240.5.tree.txt
10.12.240.5.rfdb.txt
10.12.240.5.arp.txt
10.12.240.5.output.master.txt
Debug file ipAddr.debug.tar.gz located in /bsc/logs
Attach /bsc/logs/10.12.240.5.debug.tar.gz to the TAC ticket.
*************************************

 

  1. Retrieve the file to submit to Support. This can be done using WinSCP or a similar application (specify SCP protocol) to download the files from the appliance.
  2. Submit to Support. Open a support ticket and upload the files.

 

Note:

A comment must be added for the file to be saved. If the file(s) are too big, contact Support for assistance.