From 999c024eaf806878c39605691c749bb14886cdf8 Mon Sep 17 00:00:00 2001 From: Yuri Slobodyanyuk Date: Sun, 2 May 2021 07:48:08 +0000 Subject: [PATCH] ongoing additions, changes, and fixes --- ...e-debug-diagnose-complete-cheat-sheet.adoc | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Fortigate-debug-diagnose-complete-cheat-sheet.adoc b/Fortigate-debug-diagnose-complete-cheat-sheet.adoc index 34a9ceb..267541b 100644 --- a/Fortigate-debug-diagnose-complete-cheat-sheet.adoc +++ b/Fortigate-debug-diagnose-complete-cheat-sheet.adoc @@ -534,4 +534,24 @@ a|View the kernel routing table (FIB). This is the list of resolved routes actua +|=== + + +== Virtual Fortigate License Status +.Verify status of VM Fortigate License +[cols=2, options='header"] +|=== +|Command +|Description + +|*get sys status \| grep -i lic* +|Get status o fthe license (valid for Hardware Fortigate as well as VM). The corect status is `Valid`. + +|*diagnose debug vm-print-license* +| Show detailed info on VM Fortigate license status: allowed CPUs and memory, date of license activation, license expiration date (if set), serial number. + +|*diagnose hardware sysinfo vm full* +|Show license data as seen by FortiGuard: status (should be `valid=1`), last time it was checked (`recv`), answer code, should be `code: 200`, `code: 401` is for duplicate license found, `code: 502` is for VM cannot connect to FortiGuard, and `code: 400` is for invalid license. + + |===