Creating redundant network interfaces with os 2.8
来源:互联网 发布:淘宝优惠卷怎么赚钱 编辑:程序博客网 时间:2024/04/30 16:03
About redundant interfaces
You can combine two or more physical interfaces to provide link redundancy, to ensure that Internet services remain active if one physical interface fails.
You can set up this feature on any FortiGate unit that has two spare interfaces.
For example, if you have two Internet services connected to a FortiGate unit, T1 on Wan 1 and DSL on Wan 2, you can configure Wan 2 to take over Internet traffic if Wan 1 fails.
Creating redundant interfaces
Creating redundant interfaces includes these steps:
- Creating new static routes
- Configuring a ping server on each interface
- Setting route preferences
- Creating a firewall policy
Creating new static routes
The redundant interfaces will use these static routes.
The distance value specifies the priority of every route going to the same destination. The route with the lower distance is added to the route table and used first. The second route will not be used until the first route fails. Thus, the route using the primary interface must have a lower distance value, so that it will be used instead of the route using the secondary interface.
To create new static routes
- Go to Router > Static.
- Select Create New.
- Enter the destination IP for the primary route.
- Select the device for the primary route.
- Set a distance of 10.
- Select OK.
- Enter the same destination IP for the secondary route.
- Select the device for the secondary route.
- Set a distance of 11.
- Go to Router > Monitor to confirm the new routes.
Configuring a ping server
The FortiGate unit tests the connection through an interface by sending a ping to a reliable server. If the connection is active, the server will send a ping back to the FortiGate unit. If a ping test repeatedly fails, the FortiGate unit considers that connection to have failed, and will select an alternate connection. You can set the interval between pings and the number of times the ping test can fail before a connection is considered failed in Network Options.
To test a connection, a ping must be sent to a reliable server, usually a DNS server. The local gateway or a common website are not reliable enough to confirm a connection.
To configure a ping server
- Go to System > Network > Interface.
- Select the Edit icon for the devices using the two new static routes.
- Enter an IP address for Ping Server.
- Select Enable for Ping Server.
Verifying and setting the route preference
You can set up multiple routes to a destination in the network. The FortiGate unit uses the best route for each destination, specified by the lowest priority value.
To verify the route preference
- Open the Command Line Interface (CLI).
- Log in to the FortiGate unit.
- To verify the route preferences, enter the following:
config router static
show
The main route should have a lower priority value than the secondary route. If this is not the case, you can set priority values manually.
To set the route preference in the CLI, enter the following:
 config router static
 edit 2
set device <secondary device>
set gateway <secondary IP>
next
edit 2
set device <primary device>
set gateway <primary IP>
end
Creating a firewall policy
You must define a firewall policy for the new route from your primary device to the secondary device to function.
To create a firewall policy
- Go to Firewall > Policy.
- Select Create New
- Select the primary interface for Source
- Select the secondary interface for Destination.
- Select the IP address of the primary interface for Source.
- Select the IP address of the secondary interface for Destination.
- Leave other options at the default settings.
- Select OK.
- Creating redundant network interfaces with os 2.8
- Creating redundant network interfaces with os 3.0
- QEMU/KVM Bridged Network with TAP interfaces
- Attaching Multiple Network Interfaces and Floating IPs to OpenStack Instances with Neutron
- LTE Interfaces and Network Elements
- network-manager与interfaces冲突
- network-manager与interfaces冲突
- ubuntu修改interfaces for network
- network-manager与interfaces冲突
- iOS and OS X Network Programming Cookbook |Creating an echo server(BSD)
- iOS and OS X Network Programming Cookbook |Creating an echo server(CFSocket)
- iOS and OS X Network Programming Cookbook |Creating an echo server(Bonjour)(上)
- iOS and OS X Network Programming Cookbook |Creating an echo server(Bonjour)(下)
- iOS and OS X Network Programming Cookbook |Creating an echo Client(Bonjour)
- iOS and OS X Network Programming Cookbook |Creating an echo Client(CFSocket)
- Phidgets How To: Creating a Windows CE 6.0 OS Design for Development With Phidgets Devices
- linux 下 /etc/network/interfaces 作用
- Ubuntu IP设置 /etc/network/interfaces
- Loading FortiGate firmware using TFTP
- Limiting YouTube bandwidth for fortios 3.0
- 关注HP正式及外包职位
- 最近求职经历
- FortiOS 3.0 部分网站及MSN无法登陆解决方法
- Creating redundant network interfaces with os 2.8
- Creating redundant network interfaces with os 3.0
- FortiGate to SonicWall VPN setup
- Using the FortiOS built-in packet sniffer
- FortiOS v3.0 HA Cluster virtual MAC addresses
- How do I configure a Virtual IP
- Making FortiGate completely invisible to probes
- Link Aggregation how tos
- 802.3ad Link Aggregation FAQ