Fortinet FG-100F-BDL-811-36

FG-100F-BDL-811-36 Purchase Identity

FG-100F-BDL-811-36 combines the physical FG-100F firewall, the legacy Enterprise Protection bundle code order code and 3 years (36 months). It is a BDL hardware line rather than an FC service-only SKU. Accessories outside the quoted bill of materials remain separate.

Branch handoff review

The appliance context is compact F-series firewall. Confirm branch WAN media, PoE or switch dependencies, central logging and recovery ownership before accepting this bundle.

Treat the 100F as a site security appliance: document circuit handoffs, remote access, configuration backup and the outage escalation route.

Build the acceptance record around branch-circuit ownership, remote recovery and the dependency between this firewall and the local switching or wireless design. A site contact should be able to identify the WAN demarcation, backup configuration and replacement path without relying on the subscription description.

Historical 811 entitlement audit

This is a historical 811 bundle identifier. Current Fortinet material uses different ordering codes, so the authorized quote and registration record control the exact Enterprise services and support level.

Do not convert 811 to a current package by name alone; verify renewal eligibility, included services and migration SKU with Fortinet before purchase.

Use the original contract and Fortinet registration record to reconstruct the 811 service set. A current quote must state the replacement package, retained and removed functions, support level, activation rules and renewal eligibility; the historical code by itself is not sufficient evidence.

Three-year governance

A three-year term reduces yearly purchasing work but must remain inside the hardware support and refresh window. Schedule a formal midpoint review.

Retain co-termination dates, registration owner, deployment location and a funded response if lifecycle or architecture changes before the contract ends.

Record co-termination, annual entitlement checks and a formal midpoint review for the 36-month commitment. The contract file should explain what happens if the platform, owner, region or architecture changes before the prepaid term ends.

HA pair treatment

State whether the line supports a standalone node or one member of an HA pair and verify that peer coverage, software and replacement planning remain aligned.

Decommission path

Describe data removal, registration transfer, configuration archive and asset disposal steps so retirement remains possible even during a prepaid term.

Delivery identity

Receiving should match chassis label, power variant, storage variant and ordered SKU, quarantine substitutions and retain photographs with the asset record.

Manufacturer evidence: Fortinet ordering evidence and FortiGate hardware documentation.