Troubleshooting Tip: Cisco 9300 managed by Meraki Cloud display as '?'

[cmaheu]

Description	This article describes the behavior where a Cisco C9300 switch displays as a '?' in Inventory when managed by the Meraki Cloud, as well as how to resolve this discrepancy.
Scope	FortiNAC-F 7.x.
Solution	When the C9300 is installed with Meraki firmware, the switch's system OID changes. The new system OID may not be recognized by FortiNAC. To resolve this issue, run through the following procedure: Navigate to Network -> Inventory. Right-click the device model in the tree and select Set Device Mapping. Select the Model this OID from an existing device. Select one of the Cisco C9300 Device Models from the list. If none are present, select a Meraki Switch (models start with MS, such as Meraki MS125-24). Select OK Add the switch to the L3 group by right-clicking on it Enable the following CLI debugs in a logged SSH session and provide the output to FortiNAC TAC: nacdebug -name Meraki true nacedbug -name merakiSwitch true device -ip <ip_address> -setATTR -name DEBUG -value 'TelnetServer ForwardingInterface' Change the URI associated with the switch: execute enter-shell device -ip <ip_address> -setAttr -name URIHost -value api.meraki.com device -ip <ip_address> -setAttr -name ForceInitialize -value true Run the API call from FortiNAC's underlying Linux host to Cisco Meraki, replacing the switch serial number and the Meraki API token with the appropriate value: curl -H 'X-Cisco-Meraki-API-Key: <meraki_API_key>' \ -H 'Content-Type: application/json' \ 'https://api.meraki.com/api/v1/devices/<switch_serial_number>/switch/ports>' | sed 's/[,{]/\n&/g' In the FortiNAC GUI, go back to Network -> Inventory, right-click on the switch, and select Resync Interfaces Collect additional debug logs as specified by the following KB article: Technical Tip: How to get a debug log report from FortiNAC-CA or FortiNAC-Manager Disable the debug commands from Steps 7 and 8 by removing the 'true' keyword at the end of the nacdebug commands. If necessary, open a FortiNAC-F support ticket and upload the SSH debug logs obtained from the above procedure (including those specified by the linked KB article) as well as the IP address and hostname of the device. For additional details on Cisco Meraki integrations, see Cisco Meraki Wired Integration in the Fortinet Document Library.