Cisco IP SLAs and Eem: Data center multi-egress optimization design scheme

This article will demonstrate the optimal design of multi-egress for medium-sized data centers through the Cisco IP SLA and EEM, and the data center build background:

1, the data center from the ISP applied for a number of export links, this article in three demonstrations, wherein the first 2 is enabled by default, after any one of the failures, automatically enable the third, each connected to the same operator or different devices.

2, the main use of static routing technology.

3, use IP SLA and EEM to optimize the data center fault switching speed.

Second, the design topology is as follows:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/56/B1/wKiom1SKrPOxVH2fAAEvwi77YT0998.jpg "title=" IP Sla.png "alt=" Wkiom1skrpoxvh2faaevwi77yt0998.jpg "/>

Three, configuration (the main configuration is basically in R1)

①R1 Interface Configuration

Interface fastethernet0/0

IP Address 1.1.1.1 255.255.255.0

Duplex Auto

Speed auto

!

Interface fastethernet1/0

No Switchport

IP Address 2.2.2.1 255.255.255.0

!

Interface FASTETHERNET1/1

No Switchport

IP address 3.3.3.1 255.255.255.0

Shutdown

① static Routing and IP SLA configuration

IP SLA 1

Icmp-echo 1.1.1.2 source-interface fastethernet0/0

Timeout 1000

Threshold 10

Frequency 5

IP SLA Schedule 1 life Forever Start-time Now

IP SLA 2

Icmp-echo 2.2.2.2 Source-interface fastethernet1/0

Timeout 1000

Threshold 10

Frequency 5

IP SLA Schedule 2 life Forever Start-time Now

!

Track 1 RTR 1 reachability

!

Track 2 RTR 2 reachability

!

IP Route 0.0.0.0 0.0.0.0 1.1.1.2 Track 1

IP Route 0.0.0.0 0.0.0.0 2.2.2.2 Track 2

IP Route 1.1.1.2 255.255.255.255 fa0/0

IP Route 2.2.2.2 255.255.255.255 fa1/0

③eem Configuration

Event Manager Applet Test

Event Track 1 state down

Action 1 CLI Command "enable"

Action 2 CLI Command "conf t"

Action 3 CLI Command "int FA1/1"

Action 4 CLI Command "no sh"

Action 5 CLI Command "IP route 0.0.0.0 0.0.0.0 3.3.3.2"

!

Event Manager Applet Test2

Event Track 2 state down

Action 1 CLI Command "enable"

Action 2 CLI Command "conf t"

Action 3 CLI Command "int FA1/1"

Action 4 CLI Command "no sh"

Action 5 CLI Command "IP route 0.0.0.0 0.0.0.0 3.3.3.2"

!

Quad Verification

①, initial state

R1#show IP route Static

s* 0.0.0.0/0 [1/0] via 2.2.2.2

[1/0] via 1.1.1.2

R1#show Track

Track 1

Response Time Reporter 1 reachability

Reachability is up

2 changes, last change 00:42:43

Latest Operation return Code:over threshold

Latest RTT (millisecs) 40

Tracked by:

Static-ip-routing 0

EEM Applet Test2

Track 2

Response Time Reporter 2 reachability

Reachability is up

7 changes, last change 00:01:08

Latest Operation return Code:over threshold

Latest RTT (millisecs) 88

Tracked by:

Static-ip-routing 0

EEM Applet test

② R4 fa1/0 mouth down, and in the R1 to open the Eem debug

*mar 1 00:54:30.027:%tracking-5-state:2 RTR 2 reachability up->down----Track2 is down.

r1#------------ next start performing eem functions

*mar 1 00:54:30.063:%ha_em-6-log:test:debug (cli_lib):: Ctl:cli_open called.

*mar 1 00:54:30.071:%ha_em-6-log:test:debug (cli_lib):: out:r1>

*mar 1 00:54:30.071:%ha_em-6-log:test:debug (cli_lib):: in:r1>enable

*mar 1 00:54:30.135:%ha_em-6-log:test:debug (cli_lib):: out:r1#

*mar 1 00:54:30.139:%ha_em-6-log:test:debug (cli_lib):: in:r1#conf t

*mar 1 00:54:30.199:%ha_em-6-log:test:debug (cli_lib):: Out:enter configuration commands, one per line. End with cntl/z.

*mar 1 00:54:30.199:%ha_em-6-log:test:debug (cli_lib):: out:r1 (config) #

*mar 1 00:54:30.203:%ha_em-6-log:test:debug (cli_lib):: in:r1 (config) #int FA1/1

*mar 1 00:54:30.267:%ha_em-6-log:test:debug (cli_lib):: Out:r1 (config-if) #

*mar 1 00:54:30.267:%ha_em-6-log:test:debug (cli_lib):: In:r1 (config-if) #no sh

*mar 1 00:54:30.359:%ha_em-6-log:test:debug (cli_lib):: Out:r1 (config-if) #

*mar 1 00:54:30.359:%ha_em-6-log:test:debug (cli_lib):: In:r1 (config-if) #ip Route 0.0.0.0 0.0.0.0 3.3.3.2

*mar 1 00:54:30.451:%ha_em-6-log:test:debug (cli_lib):: out:r1 (config) #

*mar 1 00:54:30.455:%ha_em-6-log:test:debug (cli_lib):: Ctl:cli_close called.

③ viewing static routes for R1

R1#show IP route Static

s* 0.0.0.0/0 [1/0] via 3.3.3.2 -------------------can see that the route has been switched to R5

[1/0] via 1.1.1.2

Five summary

① static routes are always present in the routing table, unless the default route is invalidated when the R1 router's own interface fails.

② when the interface with the R1 is faulty, the default route does not disappear, the traffic anomaly occurs, and the IP SLA is used to monitor the IP of the peer interface, which can solve the problem.

③ when traffic is high, if one link fails, it is bound to cause traffic congestion, and the new interface can be automatically enabled by Eem to increase bandwidth.

④ above is only a simple application of IP SLA and Eem, please refer to the official website guide for details.

This article is from the "brightest star in the night Sky" blog, be sure to keep this source http://wangxl.blog.51cto.com/621714/1589409

Cisco IP SLAs and Eem: Data center multi-egress optimization design scheme