FORTINET FG-71F-BDL-950-36 Firewalls

FG-71F-BDL-950-36 Purchase Identity

FG-71F-BDL-950-36 combines the physical FG-71F firewall, the Unified Threat Protection (UTP) 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.

Storage-bearing branch acceptance

The appliance context is storage-equipped 70F-family branch firewall. Verify the storage-bearing 71F identity, local event-retention purpose and export destination before activation.

Test SSD monitoring, branch evidence continuity, configuration recovery and WAN handoffs independently from the subscription term.

For the 71F, document the local-retention reason and test evidence export after restart or replacement. Preserve SSD monitoring, circuit handoffs, configuration custody and the migration path so local logs cannot become an unplanned dependency.

UTP quotation reconciliation

Fortinet's current ordering guide describes UTP as the web and network defense bundle and includes FortiCare Premium support. Confirm the authorized quote because service composition changes over time.

Check whether Enterprise-specific attack-surface, DLP, inline malware or other specialist services are required rather than inferring them from UTP.

Compare the authorized UTP line item with the current Fortinet ordering description and the functions actually required by the deployment. Record FortiCare level, service start, registration region and any specialist capability that must be quoted separately; do not expand the package from marketing shorthand.

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.

Serial custody

Record how the appliance serial moves from receiving to the Fortinet account, who can approve an ownership transfer and which evidence closes the handoff.

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.

Lifecycle trigger

Define the event that forces migration, such as support status, capacity, architecture or risk acceptance, and identify the funded successor decision.

Manufacturer evidence: Fortinet ordering evidence and FortiGate hardware documentation.