FORTINET FC-10-00307-179-02-DD FortiGate 301E FortiManager Cloud Legacy Subscription

FC-10-00307-179-02-DD Central Management Check

FC-10-00307-179-02-DD is the historical per-device FortiManager Cloud subscription for one existing FortiGate 301E. It provided cloud-based central management and orchestration; it did not include the firewall appliance, security subscriptions, managed operations or replacement hardware.

Supported Successor Path

Fortinet states that the FC-[model]-179-02-DD individual FortiGate subscription family is EOL/EOO. Current procurement uses capacity-based multi-device subscriptions, so a buyer must size managed devices or VDOMs and confirm the FortiCare account, region and migration path instead of ordering this old SKU as if it were current.

• Confirm appliance serial, FortiOS, FortiCare account, region, device or VDOM capacity and current replacement SKU.
• Back up configuration and inventory policy packages, local exceptions, scripts, administrator roles and revision history.
• Preview and test one reversible change, local result, audit trail, rollback and cloud-outage procedure.
• Record configuration authority, approvers, emergency access, unsupported items and migration acceptance.

Operational Evidence

The 301E migration record should reconcile centralized policy management with its local operational evidence. Capture policy packages, device database revisions and administrator assignments before changing the entitlement. After onboarding to the supported multi-device subscription, install a controlled address-object change, verify the device revision, retrieve the related local event and restore the prior package. Record who owns backups, who approves installations and how an operator works during a cloud-management outage.

Because the 301E can retain local operational records, define a two-part audit test. The manager proves who proposed and installed the package; the appliance record proves what actually changed and when. Reconcile the identifiers in one change ticket, then repeat the check after rollback. This prevents centralized history from being treated as proof when the device result differs.

Official sources: FortiManager Ordering Guide and EOL/EOO notice; FortiGate 301E data sheet.