Tag Archives: fortios 5.4.1 release notes

Chapter 12 – Hardware Acceleration

Chapter 12 – Hardware Acceleration

This FortiOS Handbook chapter contains the following sections:

  • Hardware acceleration overview describes the capabilities of FortiGate content processors (CPs), security processors (SPs) and network processors (NPs). This chapter also describes how to determine the hardware acceleration components installed in your FortiGate unit and contains some configuration details and examples.
  • NP6 Acceleration describes the FortiGate NP6 network processor.
  • FortiGate NP6 architectures contains details about the network processing architectures of FortiGate units that contain NP6 processors.
  • NP4 Acceleration describes the FortiGate NP4 network processor.
  • FortiGate NP4 architectures contains details about the network processing architectures of FortiGate units that contain NP4 processors.

 

Whats New in Hardware Acceleration for FortiOS 5.4

 

NP6 diagnose commands and get command changes (288738)

You can use the get hardware npu np6 command to display information about the NP6 processors in your FortiGate and the sessions they are processing. This command contains a subset of the options available from the diagnose npu np6 command. The command syntax is:

 

get hardware npu np6 {dce <np6-id> | ipsec-stats | port-list | session-stats <np6-id> |

sse-stats <np6-id> | synproxy-stats}

 

<np6-id> identifies the NP6 processor. 0 is np6_0, 1 is np6_1 and so on. dce show NP6 non-zero sub-engine drop counters for the selected NP6. ipsec-stats show overall NP6 IPsec offloading statistics.

port-list show the mapping between the FortiGate’s physical ports and its NP6 processors.

 

session-stats show NP6 session offloading statistics counters for the selected NP6.

 

sse-stats show hardware session statistics counters.

 

synproxy-stats show overall NP6 synproxy statistics for TCP connections identified as being syn proxy DoS

attacks.

 

FortiOS 5.4.1 Release Notes

Change Log

Date Change Description
2016-06-08 Initial release.
2016-06-09 Moved 373739 from Known Issues to Resolved Issues.

Added FOS-VM64, and FOS-VM64-KVM to Supported Models.

   

 

Introduction

This document provides the following information for FortiOS 5.4.1 build 1064:

l Special Notices l Upgrade Information l Product Integration and Support l Resolved Issues l Known Issues l Limitations

See the Fortinet Document Library for FortiOS documentation.

Supported models

FortiOS 5.4.1 supports the following models.

FortiGate FG-30D, FG-30E, FG-30D-POE, FG-50E, FG-51E, FG-60D, FG-60D-POE, FG-70D,

FG-70D-POE, FG-80C, FG-80CM, FG-80D, FG-90D, FGT-90D-POE, FG-92D, FG94D-POE, FG-98D-POE, FG-100D, FG-140D, FG-140D-POE, FG- 200D, FG-200DPOE, FG-240D, FG-240D-POE, FG-280D-POE, FG-300D, FG-400D, FG-500D, FG-

600C, FG-600D, FG-800C, FG-800D, FG-900D, FG-1000C, FG-1000D, FG-1200D,

FG-1500D, FG-1500DT, FG-3000D, FG-3100D, FG-3200D, FG-3240C, FG-3600C,

FG-3700D, FG-3700DX, FG-3810D, FG-3815D, FG-5001C, FG-5001D

FortiWiFi FWF-30D, FWF-30E, FWF-30D-POE, FWF-50E, FWF-51E, FWF-60D, FWF-60DPOE, FWF-80CM, FWF-81CM, FWF-90D, FWF-90D-POE, FWF-92D
FortiGate Rugged FGR-60D, FGR-90D
FortiGate VM FG-SVM, FG-VM64, FG-VM64-AWS, FG-VM64-AWSONDEMAND, FG-VM64-HV, FG-VM64-KVM, FG-VM64-XEN , FG-VMX, FOS-VM64, FOS-VM64-KVM
FortiOS Carrier FortiOS Carrier 5.4.1 images are delivered upon request and are not available on the customer support firmware download page.

Introduction                                                                                                                               Supported models

The following models are released on a special branch based off of FortiOS 5.4.1. As such, the System > Dashboard > Status page and the output from the get system status CLI command displays the build number.

 

FG-52E is released on build 5416.
FGR-30D is released on build 5413.
FGR-30D-A is released on build 5413.
FGR-35D is released on build 5413.

To confirm that you are running the proper build, the output from the get system status CLI command has a branch point field that should read 1064.