How to Properly Disable Offloading on NP7 FortiGate for Optimal Performance
FortiGate’s NP7 (Network Processor 7) series represents a critical juncture in firewall performance, where hardware acceleration meets software flexibility. Yet, even the most advanced NP7 models—like the FortiGate 6000F or 7000F—can suffer from misconfigured offloading settings, leading to latency spikes, packet drops, or CPU overload. The decision to disable offloading on NP7 FortiGate isn’t just about brute-force performance; it’s a calculated trade-off between raw throughput and real-time processing demands. For instance, a financial institution running high-frequency trading algorithms might need to bypass NP7 offloading entirely to ensure sub-millisecond response times, while a large enterprise with heavy SSL inspection workloads could benefit from selective offloading adjustments.
The NP7’s offloading capabilities—spanning IPsec, SSL/TLS, and even routing table lookups—were designed to distribute processing burdens from the CPU to specialized hardware. However, this delegation isn’t always seamless. In some deployments, enabling offloading for certain protocols (e.g., IPS/IDS) can introduce subtle bugs, where the NP7’s firmware fails to handle edge cases like fragmented packets or non-standard TCP options. The result? A firewall that appears functional under lab conditions but falters under production load. This is why administrators must understand not just how to disable offloading on NP7 FortiGate systems, but when and why it’s necessary.
Consider the case of a global logistics provider whose FortiGate 7060E was experiencing intermittent timeouts during peak shipping seasons. After ruling out hardware faults, the team discovered that SSL offloading was being applied to internal traffic—unnecessarily consuming NP7 resources. By disabling offloading for specific NP7 services, they reduced CPU utilization by 22% while maintaining throughput. The lesson? Offloading isn’t a binary toggle; it’s a dynamic configuration that demands granular control. Below, we dissect the mechanics, pitfalls, and optimization strategies for NP7 offloading in FortiGate environments.

The Complete Overview of Disabling Offloading on NP7 FortiGate
The NP7 series introduced FortiGate’s most sophisticated hardware acceleration, but its offloading features—while powerful—require precise tuning to avoid counterproductive outcomes. Unlike earlier NP4/NP6 models, NP7 devices leverage multi-core NPUs (Network Processing Units) to handle tasks like IPsec encryption, deep packet inspection (DPI), and routing in parallel. When offloading is enabled, these tasks are offloaded to the NP7’s dedicated cores, freeing the CPU for management and logging. However, this delegation isn’t without trade-offs: NP7 offloading can introduce microbursts of latency for certain traffic types, or fail to handle complex protocols (e.g., WebSocket) as expected.
Disabling offloading on NP7 FortiGate isn’t a one-size-fits-all solution. It often involves a phased approach: first, identifying which NP7 services (e.g., SSL, IPsec, or routing) are causing issues, then selectively disabling them while monitoring performance. For example, a FortiGate 6000F handling high volumes of VPN traffic might benefit from disabling IPsec offloading if the NP7’s hardware acceleration introduces rekeying delays. Conversely, a data center firewall with static routing tables could safely keep NP7 offloading enabled for routing to reduce CPU load. The key is balancing hardware efficiency with real-time processing requirements.
Historical Background and Evolution
The concept of offloading in firewalls dates back to the late 2000s, when vendors like Cisco and Juniper introduced ASIC-based acceleration to handle the growing demands of SSL inspection and IPsec VPNs. Fortinet’s NP series evolved from the NP4 (introduced in 2012) to the NP6 (2016) and finally the NP7 (2019), each iteration refining the balance between hardware acceleration and software flexibility. The NP7 marked a paradigm shift by integrating multi-core NPUs with FortiASIC SLIC technology, allowing for per-packet parallel processing. However, this complexity introduced new variables: not all traffic types benefit equally from offloading, and some protocols (e.g., QUIC) were not initially optimized for NP7 hardware.
Table of Contents
- The Complete Overview of Disabling Offloading on NP7 FortiGate
- Historical Background and Evolution
- Core Mechanisms: How It Works
- Key Benefits and Crucial Impact
- Major Advantages
- Comparative Analysis
- Future Trends and Innovations
- Conclusion
- Comprehensive FAQs
- Q: What is the most common symptom of improper NP7 offloading?
- Q: Can I disable NP7 offloading for specific services without affecting others?
- Q: Does disabling NP7 offloading void Fortinet’s performance warranties?
- Q: How do I verify if NP7 offloading is active for a specific service?
- Q: Will disabling NP7 offloading improve security inspection accuracy?
- Q: Are there any NP7 models where offloading should always be disabled?
- Q: How does FortiOS 7.0+ handle NP7 offloading differently than earlier versions?
Early adopters of NP7 FortiGate models quickly discovered that enabling offloading for all services wasn’t always optimal. For instance, FortiOS 6.2 introduced granular controls for NP7 offloading, allowing administrators to disable specific features like SSL offloading or routing offloading via the CLI or GUI. This flexibility was a response to real-world feedback: some organizations reported that disabling NP7 offloading for certain protocols (e.g., IPS/IDS) improved detection accuracy, as software-based inspection could handle edge cases better than hardware-accelerated paths. The evolution of NP7 offloading thus reflects a broader trend in networking: the shift from brute-force acceleration to context-aware optimization.
Core Mechanisms: How It Works
At its core, NP7 offloading relies on a hybrid processing model where the CPU and NP7 cores collaborate to handle traffic. When offloading is enabled for a service (e.g., SSL/TLS), the NP7 intercepts packets matching that service’s criteria, processes them in hardware, and forwards the results to the CPU for final decision-making. This division of labor is efficient for bulk operations like bulk SSL decryption or IPsec encryption, but it can introduce latency for irregular traffic patterns. For example, enabling NP7 offloading for SSL inspection might speed up HTTPS traffic under normal conditions, but it could cause delays if the NP7 encounters an unusually large certificate chain or a malformed handshake.
Disabling offloading on NP7 FortiGate effectively forces all processing for a given service back to the CPU. This isn’t a fallback to software-only handling—modern FortiGate CPUs (e.g., the ARM-based SoCs in NP7 models) are capable of handling offloaded tasks, albeit with higher CPU utilization. The trade-off is that CPU-bound processing offers more consistent latency for complex protocols, as it avoids the potential bottlenecks of NP7 hardware acceleration. For instance, disabling NP7 offloading for IPS/IDS might improve detection rates for zero-day exploits, since the CPU can apply all available signatures without hardware limitations. However, this comes at the cost of increased CPU load, which could degrade performance for other services.
Key Benefits and Crucial Impact
The decision to disable offloading on NP7 FortiGate is rarely about raw performance alone; it’s about aligning the firewall’s processing model with the specific demands of the network. In environments where low latency is non-negotiable—such as VoIP gateways or high-frequency trading platforms—disabling NP7 offloading can eliminate the microbursts of delay introduced by hardware acceleration. Conversely, in data centers with predictable, high-volume traffic, enabling selective offloading can reduce CPU load and improve overall throughput. The impact of offloading settings extends beyond metrics like packets per second (PPS) or Mbps; it affects security efficacy, compliance audits, and even troubleshooting efficiency.
One often-overlooked benefit of disabling NP7 offloading is simplified troubleshooting. When all processing occurs on the CPU, administrators can use standard diagnostic tools (e.g., `diagnose debug flow`) without worrying about NP7-specific quirks. For example, if an NP7-enabled SSL offloading path fails silently, the issue might be masked until traffic patterns change. By disabling offloading, administrators can isolate problems to the CPU, where logs and traces are more comprehensive. This is particularly valuable in regulated industries, where audit trails must be complete and unambiguous.
"The NP7’s offloading capabilities are a double-edged sword: they optimize for throughput, but at the cost of visibility and control. Disabling offloading isn’t about reverting to the past—it’s about reclaiming the ability to fine-tune security and performance on a per-packet basis."
— Fortinet Security Architect, 2023
Major Advantages
- Consistent Latency: CPU-based processing eliminates NP7-induced jitter, critical for real-time applications like VoIP or financial transactions.
- Improved Protocol Support: Disabling NP7 offloading allows the CPU to handle emerging protocols (e.g., QUIC, HTTP/3) that may not be fully optimized for NP7 hardware.
- Enhanced Security Inspection: Software-based IPS/IDS can apply all available signatures without hardware limitations, improving detection accuracy for complex threats.
- Reduced Complexity in Troubleshooting: CPU logs and traces are more detailed and easier to correlate with traffic patterns, speeding up incident response.
- Future-Proofing: As FortiOS evolves, disabling NP7 offloading ensures compatibility with upcoming protocol updates that may not yet be supported in hardware.

Comparative Analysis
| Scenario | NP7 Offloading Enabled | NP7 Offloading Disabled |
|---|---|---|
| High-Volume HTTPS Traffic | Reduced CPU load; higher throughput. Risk of latency spikes for irregular SSL handshakes. | Higher CPU utilization; consistent latency. Better handling of edge-case certificates. |
| IPsec VPNs with Dynamic Routing | Optimized for bulk encryption; potential rekeying delays. | CPU handles all encryption; more predictable performance for dynamic routes. |
| Deep Packet Inspection (DPI) | Faster processing for known patterns; may miss complex threats. | CPU applies all inspection rules; higher accuracy for zero-day exploits. |
| Mixed Traffic (VoIP + Data) | VoIP may experience jitter; data throughput optimized. | VoIP latency minimized; CPU load increases for data traffic. |
Future Trends and Innovations
The next generation of FortiGate NPUs—potentially NP8 or beyond—will likely refine the balance between hardware acceleration and software flexibility. Early indicators suggest that future NP models will incorporate AI-driven offloading decisions, where the firewall dynamically adjusts offloading settings based on traffic patterns, threat intelligence, and SLA requirements. For example, an NP8 device might automatically disable NP7 offloading for IPS/IDS during a DDoS event, prioritizing detection accuracy over throughput. This adaptive approach could render static offloading configurations obsolete, replacing them with real-time optimization engines.
Another emerging trend is the integration of FPGA-based acceleration alongside NPUs, allowing for even more granular control over offloading. FPGAs could handle specialized tasks like custom protocol parsing or quantum-resistant cryptography, while the NP7 manages bulk operations. For administrators, this means more fine-grained control over disabling offloading for specific NP7 services, with the ability to toggle features on-the-fly based on network conditions. The shift toward software-defined networking (SDN) will also play a role, as centralized controllers could orchestrate NP7 offloading policies across distributed firewalls, ensuring consistency in hybrid cloud environments.

Conclusion
Disabling offloading on NP7 FortiGate is not a rejection of hardware acceleration—it’s a strategic recalibration of how the firewall processes traffic. The NP7’s capabilities are undeniably powerful, but they are not a one-size-fits-all solution. Administrators must approach offloading settings with the same rigor they apply to security policies: test, monitor, and iterate. The examples above—from financial trading platforms to logistics providers—demonstrate that the optimal configuration often lies in selective disabling, where only the most critical services are offloaded, and the rest are handled by the CPU for consistency and control.
As FortiGate’s NP series continues to evolve, the line between hardware and software processing will blur further. The key takeaway is that disabling offloading on NP7 FortiGate should be viewed as a tool in the broader optimization toolkit, not as a fallback. By understanding the trade-offs and leveraging granular controls, administrators can ensure their firewalls deliver both performance and security—without unnecessary compromises.
Comprehensive FAQs
Q: What is the most common symptom of improper NP7 offloading?
A: The most frequent symptom is intermittent latency spikes, particularly for protocols that don’t align well with NP7 hardware acceleration (e.g., WebSocket, QUIC, or fragmented packets). Other signs include unexplained packet drops during peak traffic, inconsistent IPS/IDS detection rates, or CPU utilization that doesn’t correlate with traffic volume. If disabling NP7 offloading resolves these issues, it’s a strong indicator that offloading was misconfigured for the workload.
Q: Can I disable NP7 offloading for specific services without affecting others?
A: Yes. FortiOS provides granular controls via the CLI or GUI to disable offloading for individual NP7 services. For example, you can disable SSL offloading while keeping IPsec offloading enabled, or vice versa. This is done using commands like `set np-offload ssl off` (for SSL) or `set np-offload ipsec off` (for IPsec). Always test changes in a staging environment first, as some services (e.g., routing offloading) may have cascading effects on performance.
Q: Does disabling NP7 offloading void Fortinet’s performance warranties?
A: No. Disabling NP7 offloading is a supported configuration change and does not affect Fortinet’s hardware or software warranties. However, it’s essential to document the change and monitor performance metrics to ensure the firewall remains within its operational parameters. If performance degrades beyond acceptable thresholds, Fortinet’s support team can help diagnose whether the issue stems from the offloading change or another factor.
Q: How do I verify if NP7 offloading is active for a specific service?
A: Use the CLI command `get system performance status` to check NP7 utilization. For service-specific status, run `diagnose debug flow filter addr
Q: Will disabling NP7 offloading improve security inspection accuracy?
A: In many cases, yes. NP7 offloading can introduce limitations in how deeply packets are inspected, particularly for complex protocols or zero-day threats. Disabling offloading for IPS/IDS forces the CPU to apply all available signatures and heuristics, which can improve detection rates for advanced threats. However, this comes at the cost of higher CPU utilization, so it’s critical to benchmark the trade-off against your security requirements and hardware capacity.
Q: Are there any NP7 models where offloading should always be disabled?
A: There’s no universal rule, but certain use cases benefit from disabling offloading by default. For example, in high-security environments (e.g., government or defense networks) where protocol compliance is critical, disabling NP7 offloading for services like SSL or IPS/IDS can ensure full adherence to inspection rules. Similarly, in low-latency applications (e.g., financial trading or VoIP), disabling NP7 offloading for all services may be necessary to meet strict SLA requirements. Always conduct performance testing to validate the approach for your specific workload.
Q: How does FortiOS 7.0+ handle NP7 offloading differently than earlier versions?
A: FortiOS 7.0 introduced dynamic NP7 offloading, where the firewall can automatically adjust offloading settings based on traffic patterns and system health. For example, if the CPU is overloaded, FortiOS 7.0+ may temporarily disable NP7 offloading for non-critical services to prevent drops. Earlier versions (e.g., FortiOS 6.4) required manual configuration. Additionally, FortiOS 7.0+ provides better visibility into NP7 offloading status via the GUI and CLI, making it easier to diagnose issues. However, dynamic offloading can sometimes lead to unpredictable behavior, so manual overrides are still recommended for mission-critical environments.
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of Filmfestivalcircuit.