mirror of
https://github.com/yuriskinfo/cheat-sheets.git
synced 2025-12-24 06:28:18 +01:00
Fortigate: added Fortitoken section
This commit is contained in:
@@ -966,6 +966,41 @@ Google or documentation.
|
||||
|
||||
|===
|
||||
|
||||
== FortiTokens
|
||||
|
||||
[cols=2, options="header"]
|
||||
|===
|
||||
|Command
|
||||
|Description
|
||||
|
||||
|*diagnose fortitoken info*
|
||||
|Show all existing on the Fortigate Fortitokens, including their status:
|
||||
|
||||
* `new` - new token, available to be assigned to a user.
|
||||
* `active` - normal state, assigned to a user, hardware Fortitoken.
|
||||
* `provisioning` - Fortitoken Mobile (FTM), assigned to a user, waits for end
|
||||
user to activate it on his/her mobile phone.
|
||||
* `provisioned` - FTM, assigned to a user and activated by him/her as well.
|
||||
* `provision timeout` - user hasn't activated the assigned token in the given
|
||||
time window (3 days default), the token needs to be re-provisioned to a user again.
|
||||
`locked` - token was locked either manually by administrator, or because
|
||||
Fortigate was not able to reach Fortiguard servers.
|
||||
|
||||
|
||||
|*exec ping fds1.fortinet.com*
|
||||
|
||||
*exec ping directregistration.fortinet.com*
|
||||
|
||||
*exec ping globalftm.fortinet.net*
|
||||
|
||||
|Verify that Fortigate can resolve and ping the FortiGuard servers
|
||||
responsible for FortiToken activation/license validation.
|
||||
|
||||
|*show user fortitoken*
|
||||
|Display all Fortitokens info on license number, activation expiration (in epoch
|
||||
format).
|
||||
|
||||
|===
|
||||
|
||||
== Alerts Sending debug
|
||||
|
||||
|
||||
Reference in New Issue
Block a user