Recently, some netizens asked me about the backup of multiple external routes and the load is sparse. Due to time constraints, I briefly wrote about the configuration... The following is an example of dual external route backup. Multiple external routes are nothing more than adding corresponding policy routing on the original basis... If there are any omissions, please give me advice...
The premise is that when the basic configuration of each interface and other is completed.
(1) You can add two default routes first for two lines: the first one is preferred. If the first line fails, it will automatically jump to the second line.
ip route 0.0.0.0 0.0.0.0
ip route 0.0.0.0 0.0.0.0
(2) If the first line is normal and the second line needs to be loaded, policy routing can be done based on (1). as follows:
A. Make strategies for some network segments, for example, jump 192.168.1.0 and 192.168.2.0 to some load on the line.
access-list 12 permit 192.168.1.0 0.0.0.255
access-list 12 permit 192.168.2.0 0.0.0.255
route-map yy permit 10 (Define policy yy)
match ip address 12 (match control list 12)
set ip next-hop (set the next hop address, that is, the next router interface address [gateway] where the packet passes)
B. Make policies for some hosts, such as jumping host 192.168.3.11 and host 192.168.4.12 to part of the load on the line (the default address of these two network segments is the first default route, that is).
access-list 101 permit ip host 192.168.3.11 any
access-list 101 permit ip host 192.168.4.12 any
route-map yy permit 20 (Define the policy yy)
match ip address 101 (match control list 101)
set ip next-hop (Set the next hop address, that is, the next router interface address where the packet passes [gateway])
In this way, by default, except for the network segments and hosts defined in the above policy routing, all hosts in other network segments are connected to the external network through lines. If this line fails, the default route will become, and the policy routing is on the line, so it will not be affected... Article entry: csh Editor in charge: csh
The premise is that when the basic configuration of each interface and other is completed.
(1) You can add two default routes first for two lines: the first one is preferred. If the first line fails, it will automatically jump to the second line.
ip route 0.0.0.0 0.0.0.0
ip route 0.0.0.0 0.0.0.0
(2) If the first line is normal and the second line needs to be loaded, policy routing can be done based on (1). as follows:
A. Make strategies for some network segments, for example, jump 192.168.1.0 and 192.168.2.0 to some load on the line.
access-list 12 permit 192.168.1.0 0.0.0.255
access-list 12 permit 192.168.2.0 0.0.0.255
route-map yy permit 10 (Define policy yy)
match ip address 12 (match control list 12)
set ip next-hop (set the next hop address, that is, the next router interface address [gateway] where the packet passes)
B. Make policies for some hosts, such as jumping host 192.168.3.11 and host 192.168.4.12 to part of the load on the line (the default address of these two network segments is the first default route, that is).
access-list 101 permit ip host 192.168.3.11 any
access-list 101 permit ip host 192.168.4.12 any
route-map yy permit 20 (Define the policy yy)
match ip address 101 (match control list 101)
set ip next-hop (Set the next hop address, that is, the next router interface address where the packet passes [gateway])
In this way, by default, except for the network segments and hosts defined in the above policy routing, all hosts in other network segments are connected to the external network through lines. If this line fails, the default route will become, and the policy routing is on the line, so it will not be affected... Article entry: csh Editor in charge: csh