After upgrade

Check the integrity of the system Service Protection Policies (SPPs) using the following CLI commands.

diagnose debug rrd_files_check

Output:

Global expected:5, found:5 (this is the global SPP)

SPP:0 expected:1857, found:1857 (this SPP is used internally)

SPP:1 expected:1857, found:1857 (this is the default SPP)

SPP:2 expected:1857, found:1857

SPP:3 expected:1857, found:1857

SPP:4 expected:1857, found:1857 (Limit for VM-04)

SPP:5 expected:1857, found:1857

SPP:6 expected:1857, found:1857

SPP:7 expected:1857, found:1857

SPP:8 expected:1857, found:1857 (Limit for 200F/VM08)

SPP:9 expected:1857, found:1857

SPP:10 expected:1857, found:1857

SPP:11 expected:1857, found:1857

SPP:12 expected:1857, found:1857

SPP:13 expected:1857, found:1857

SPP:14 expected:1857, found:1857

SPP:15 expected:1857, found:1857

SPP:16 expected:1857, found:1857 (Limit for 1500F/VM16)

If the expected and found numbers above do not match (they may not be 1857 as above, but must match), you must follow the directions below to recreate/reset the RRDs.

Recreating/resetting the SPP RRDs removes all previous traffic and drop graphing information for that SPP. However, Logs are retained. If you are unsure on how to proceed, contact FortiCare for support.

Repair the SPP using the following CLI commands.

If one or a few SPPs from 1-4/8/16 are missing RRDs:

execute spp-rrd-reset spp <rule_name> (where rule_name is the textual name from the GUI)

If many SPPs are missing RRDs:

execute rrd-reset All

Note: All is case-sensitive.

If Global is missing RRDs:

execute global-rrd-reset

If any SPP is missing, contact FortiCare for support.