FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
azhunissov
Staff
Staff
Article Id 298359
Description This article describes causes and fixes for an issue where FortiManager does not provide FortiGuard service to hidden devices and they are not counted in the device/ADOM license.
Scope FortiManager 6.2 and higher versions.
Solution

If a device is hidden, it is not used in a device license count and FortiManager does not provide FortiGuard services to that device:

 

FortiGate:

 

get_fcpr_response[298]-Unpacked obj: Protocol=3.2|Firmware=FMG-VM64-FW-7.02-1460|SerialNumber=FMG-VMTMXXXXXX|Response=401|

upd_fds_fmg_info_update[1667]-Updated FMG [FMG-VMTMXXXXXX], ver=7.2-1460, code=401

upd_pkg_verify_update_rsp[1187]-Unexpected update rsp code 401

__upd_act_update[308]-Received invalid update rsp

 

FortiManager:

 

__check_unreg_device: device FG101FXXXXXXXXX is hidden, skip update

__process_client_request,2980; check unreg failed for FG101FXXXXXXXXX

[FMG-->FGT] Response: Protocol=3.2|Firmware=FMG-VM64-FW-7.02-1460|SerialNumber=FMG-VMTMXXXXXX|Response=401|

 

1.png

 

 
 
 

If the device is not hidden but is unregistered, it is counted in a device license count and FortiManager provides the FortiGuard service to that device:

 

FortiGate:

 

upd_fds_fmg_info_update[1793]-Updated FMG [FMG-VMTMXXXXXX], ver=7.2-1530, code=300

 

FortiManager:

 

[FMG-->FGT] Response: Protocol=3.2|Firmware=FMG-VM64-FW-7.02-1530|SerialNumber=FMG-VMTMXXXXXX|Response=300|

 

2.png

 

To allow FortiGuard services for unregistered devices (not hidden devices), it is necessary to have a sufficient FortiManager device/domain license.