FortiGate 200E and 201E fast path architecture
The FortiGate 200E and 201E include two SOC3 NP6XLite processors. The SOC3 CPUs and CP9Lite processors are not used. Instead, the FortiGate 200E and 201E architecture includes separate CPU resources and a standard CP9 processor.
The processors are connected to network interfaces as follows:
- NP6Lite_0 is connected to six 1GE RJ-45 interfaces (port9-port14) and four 1GE SFP interfaces (port15-18).
- NP6Lite_1 is connected to ten 1GE RJ45 interfaces (wan1, wan2, port1-port8).
As a result of the NP Direct configuration, traffic will only be offloaded if it enters and exits the FortiGate 200E or 201E on interfaces connected to the same NP6 processor.
The following diagram also shows the RGMII and QSGMII port connections between the NP6Lite processors and the front panel interfaces. Both RGMII and QSGMII interfaces operate at 1000Mbps. However, QSGMII interfaces can also negotiate to operate at lower speeds: 10, 100, and 1000Mbps. To connect the FortiGate 200E to networks with speeds lower than 1000Mbps use the QSGMII interfaces (port1-8 and port11-18).
You can use the following get command to display the FortiGate 200E or 201E NP6Lite configuration. You can also use the diagnose npu np6lite port-list
command to display this information.
get hardware npu np6lite port-list Chip XAUI Ports Max Cross-chip Speed offloading ------ ---- ------- ----- ---------- np6lite_0 2 port9 1000M NO 1 port10 1000M NO 4 port11 1000M NO 3 port12 1000M NO 6 port13 1000M NO 5 port14 1000M NO 9 port15 1000M NO 10 port16 1000M NO 8 port17 1000M NO 7 port18 1000M NO np6lite_1 2 wan1 1000M NO 1 wan2 1000M NO 4 port1 1000M NO 3 port2 1000M NO 6 port3 1000M NO 5 port4 1000M NO 8 port5 1000M NO 7 port6 1000M NO 10 port7 1000M NO 9 port8 1000M NO
The FortiGate- 200E and 201E supports creating LAGs that include interfaces connected to different NP6Lite processors. Because the FortiGate-200E and 201E does not have an internal switch fabric, when you set up a LAG consisting of interfaces connected to different NP6Lite processors, interfaces connected to each NP6Lite processor are added to a different interface group in the LAG. One interface group becomes the active group and processes all traffic. The interfaces in the other group become passive. No traffic is processed by interfaces in the passive group unless all of the interfaces in the active group fail or become disconnected.
Since only one NP6Lite processor can process traffic accepted by the LAG, creating a LAG with multuple NP6Lite processors does not improve performance in the same way as in a FortiGate with an internal switch fabric. However, other benefits of LAGs, such as redundancy, are supported.
For details, see Increasing NP6 offloading capacity using link aggregation groups (LAGs).