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.
FortiKoala
Staff
Staff
Article Id 194143

Description


This article describes the case when adding a network device in UI, a question mark (?) appears for the device icon. 

This indicates the device is not supported in the currently running version. 

Solution

 

  1. Determine if support for the device was added in a more recent version of the code. Contact Support and supply the sysObjectID information:
 
Administration UI:
 
  1. If the device is already in the UI, navigate to:
    Version 8.x:  Network Devices -> Topology.
    Version 9.x/F7.x: Network -> Inventory.

  2. Select the switch's container in Topology and locate the sysObjectID listed in the Raw Type column (Example: 1.3.6.1.4.1.9.6.1.82.8.1).
 
snmpwalk application:
 
  1. Ensure the device is on the network configured with an IP address and SNMP credentials. 
  2. Perform snmpwalk of the System OID via Control Server CLI or some other tool. 
To obtain SNMP System OID information using Control Server CLI, establish an SSH session and type the following:
 
SNMP version 1 or 2:
 
CentOS:

snmpwalk -v 1 -c <community string> <device ip_address> system
 
FortiNAC-OS:

execute enter-shell
snmpwalk -v 1 -c <community string> <device ip_address> system
 
SNMP version 3:

CentOS:
 
snmpwalk -v 3 -u <username> -l <AuthPriv or NoAuthPriv> -a <MD5 or SHA> -A <password> -x <DES or AES> -X <password> <device ip_address> system
 
FortiNAC-OS:
 
execute enter-shell
snmpwalk -v 3 -u <username> -l <AuthPriv or NoAuthPriv> -a <MD5 or SHA> -A <password> -x <DES or AES> -X <password> <device ip_address> system 
 
This may need to use single quotes (') with passwords.
 
  1. If the model is not currently supported in available code, it may be possible to use an existing device mapping from a similar model. See the KB article 198477 for instructions.

  2. If using an existing device mapping does not work, submit a request to support the device. 
    See the KB article 192664.
 
Related Articles:

Technical Note: Options for devices unable to be modeled in Topology