Static Ip Network Interfaces

This article shows how to setup an active-passive session-aware load balancing cluster (SLBC) consisting of two FortiGate-5000 chassis, four FortiController-5103Bs two in each chassis, and six FortiGate-5001Bs acting as workers, three in each chassis.

This recipe provides an example of how to set up a FortiGate for redundant Internet connectivity using SD-WAN and then convert this single FortiGate into an FGCP HA cluster of two FortiGates.

In this article, you can learn how to configure a Fortinet Security Fabric that consists of four FortiGate devices and a FortiAnalyzer.

In this recipe, you add FortiTelemetry traffic to an existing IPsec VPN site-to-site tunnel between two FortiGate devices, in order to add a remote FortiGate to the Security Fabric. You also allow the remote FortiGate to access the FortiAnalyzer for logging.

Hyper-V is the new concept of a recently virtualized network, with news that many of its most recent features affect network design. In previous articles, we briefly described some improvements in network virtualization and some improvements in virtual machine networks. This article introduces another network improvement: Network card Aggregation (NIC teaming), and a brief introduction to some of the new Hyper-V options for data center design. Network card aggregation is also called load balance failover (load balancing Fail over ...)

This recipe provides an example of how you can configure redundant Internet connectivity for your network using SD-WAN. This allows you to load balance your Internet traffic between multiple ISP links and provides redundancy for your network’s Internet connection if your primary ISP is unavailable.

In this recipe, you use virtual domains (VDOMs) to provide Internet access for two different companies (called Company A and Company B) using a single FortiGate.

In this article we cover a VXLAN over IPsec configuration using FortiGate as VTEP.

This example shows how to create a dynamic IPsec VPN tunnel and allowing BGP peering through it.

I believe you have seen in many places "Docker based on Mamespace, Cgroups, chroot and other technologies to build containers," but have you ever wondered why the construction of containers requires these technologies? 　　Why not a simple system call? The reason is that the Linux kernel does not have the concept of "Linux container", the container is a user state concept. Docker software engineer Michael Crosby will write some blog posts and dive into Docke ...