Metric computing and Server Load balancer

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204603-0.jpg "/>

The experiment topology is shown in figure. First, we use the VPN protocol to connect to the above topology.

R1 (config) # int lo 0

R1 (config-if) # ip add 1.1.1.1 255.255.255.0

R1 (config-if) # no shut
R1 (config-if) # exit
R1 (config )#
R1 (config) # int f1/0
R1 (config-if) # ip add 12.1.1.1 255.255.255.0
R1 (config-if) # no shut
R1 (config-if) # exit
R1 (config) # int f1/1
R1 (config-if) # ip add 13.1.1.1 255.255.255.0
R1 (config-if) # no shut

 

R2 (config) # int f1/0
R2 (config-if) # ip add 12.1.1.2 255.255.255.0
R2 (config-if) # no shut
R2 (config-if) # exit
R2 (config) # int f1/1
R2 (config-if) # ip add 24.1.1.1 255.255.255.0
R2 (config-if) # no shut

 

R3 (config) # int f1/0
R3 (config-if) # ip add 13.1.1.2 255.255.255.0
R3 (config-if) # no shut
R3 (config-if) # exit
R3 (config )#
R3 (config) # int f1/1
R3 (config-if) # ip add 34.1.1.1 255.255.255.0
R3 (config-if) # no shut
R3 (config-if) # exit
 

R4 (config) # int lo 0
R4 (config-if) # ip add 4.4.4.4 255.255.255.0
R4 (config-if) # no shut
R4 (config-if) # exit
R4 (config )#
R4 (config) # int f1/0
R4 (config-if) # ip add 24.1.1.2 255.255.255.0
R4 (config-if) # no shut
R4 (config-if) # exit
R4 (config )#
R4 (config) # int f1/1
R4 (config-if) # ip add 34.1.1.2 255.255.255.0
R4 (config-if) # no shut
R4 (config-if) # exit


The IP address is configured successfully. Check for direct connection.

 

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129205963-1.jpg "/>

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/012920JR-2.jpg "/>

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204P0-3.jpg "/>

 

Network-wide interconnection using the VPN Protocol

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204938-4.jpg "/>

R2 (config) # router VPN 90
R2 (config-router) # net 12.1.1.0
R2 (config-router) # net
* Nov 25 21:43:32. 791: % DUAL-5-NBRCHANGE: IP-EIGRP (0) 90: Neighbor 12.1.1.1 (FastEthernet1/0) is up: new adjacency
R2 (config-router) # net 24.1.1.0
R2 (config-router) # no au
R2 (config-router) # no auto-summary
R2 (config-router )#
650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129202112-5.jpg "/> 650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129205519-6.jpg "/>

Advertised Routing Protocol

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/012920M32-7.jpg "/>

Successfully learned from all network entries and successfully communicated

Test the network type of the network type

First, let's check the OSPF neighbor of R1.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129205T3-8.jpg "/>

R1 has two neighbor nodes of the VPN gateway.

Multiple parameters are used to calculate the metric value to the target network. The five parameters, including the bandwidth delay load credibility MTU, are identified by K values. If the k values of the two routers are different, the Calculation Method of metric is different between the two vrouters. Therefore, the relationship between the two vrouters with different K values cannot form the relationship between the two vrouters.

Metric calculation method of the network type.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/01292023N-9.jpg "/>

 

When calculating the METRIC value, only the outbound bandwidth of the interface is calculated. That is, on a link, only the outbound bandwidth of the interface is calculated.

 

Let's take a look at the five K values of the VPN Router R1.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204361-10.jpg "/>

5 K values are 1 0 1 0 0

 

Verify that the value of K is different, and the neighbor relationship of VPN cannot be established, so we can modify the K value of router R2.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204c1-11.jpg "/>

After the K value of R2.

 

Try to calculate the metric value from R1 to destination 4.4.4

First, we need to know the minimum bandwidth and the sum of latency from R1 to 4.4.4.

Minimum bandwidth = Minimum outbound bandwidth

Latency sum = the total latency of all outbound links

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/01292024b-12.jpg "/>

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129203541-13.jpg "/>

The bandwidth of the Ethernet link is 100000, which is the minimum bandwidth of the entire Link.

Sum of latency from R1 to 4.4.4

R1 f1/0 + R2 f1/1 + R4 lo0 = 100 + 100 + 5000 = 5200

Input the preceding values into the metric calculation formula.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129205945-14.jpg "/>

Check whether the value in the route table is the same as that in the route table.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/012920C13-15.jpg "/>

The value is the same as the value in the route table. In this case, METRIC is successfully calculated.

 

Metric from vror2 R2 to 4.4.4 is calculated in the same way.

Bandwidth with = 10000

Delay = 100 + 5000 = 5100

Finally, metric is

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/01292010E-16.jpg "/>

 

Lab:

Modifying the interface bandwidth of R2 affects metric calculation and route table

R2 (config) # int f1/1
R2. (config-if) # bandwidth 50000

At this point we see that there is only one path R1-4.4.4.4 from the R1-R3-R4

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/0129204J2-17.jpg "/>

The next hop of the route to 4.4.4 is 13.1.1.2, that is, R3.

 

Test the non-equivalent Server Load balancer of the MongoDB protocol.

 

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131227/012920B07-18.jpg "/>

The FD value of R1 going up to 4.4.4.4 is 158720 AD value is 156160

We did not see the path of the R1-R2-R4 In the topology table of the network. The topology table stores successor and fessible successor. If a path is not fessible successor, if the AD value of this path is greater than the FD value of successor, We will calculate the metric from R2 to 4.4.4.4.

Bandwidth with = 50000

Delay = 100 + 5000 the formula metric = 181760 is greater than the FD value of successor. Therefore, this path will not be placed in the topology table.

 

 

This article is from the blog "Zhuhai Liu Shuo's blog". For more information, contact the author!