Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Cisco IP SLA and EEM: multi-exit Optimization Design of data Center

2025-04-13 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Network Security >

Share

Shulou(Shulou.com)06/01 Report--

This article will demonstrate the multi-egress optimization design of medium-sized data center through Cisco IP SLA and EEM, and introduce the background of data center construction:

1. The data center has applied for multiple egress links from ISP. This document demonstrates three. The first two are enabled by default. After any one of them fails, the third is automatically enabled, each connected to the same or different equipment of the operator.

2. Static routing technology is mainly used.

3. Use IP SLA and EEM to optimize data center failure switching speed.

2. The design topology is as follows:

3. Configuration (basically all the main configurations are on 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"

!

Four verifications

①, initial statu

R1#show ip route static

S* 0.0.0.0 via 0 [1max 0] 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

② down the fa1/0 port of R4 and open the debug of EEM on R1

* Mar 1 00 rtr 54 reachability Up- 30.027:% TRACKING-5-STATE: 2 rtr 2 reachability Up- > Down----Track2 has been down

Ringing-next start to execute the EEM function

* Mar 1 00 DEBUG 54 DEBUG 30.063:% HA_EM-6-LOG: test: DEBUG (cli_lib):: CTL: cli_open called.

* Mar 1 00 DEBUG 54 DEBUG 30.071:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: R1 >

* Mar 1 00 test 54 DEBUG 30.071:% HA_EM-6-LOG: test: DEBUG (cli_lib):: IN: R1 > enable

* Mar 1 00 DEBUG 54 DEBUG 30.135:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: ringing

* Mar 1 00 DEBUG 54 DEBUG 30.139:% HA_EM-6-LOG: test: DEBUG (cli_lib):: IN: R1#conf t

* Mar 100 DEBUG 54 DEBUG 30.199:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: Enter configuration commands, one per line. End with CNTL/Z.

* Mar 1 00 DEBUG 54 DEBUG 30.199:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: R1 (config) #

* Mar 1 00 DEBUG 54 30. 203:% HA_EM-6-LOG: test: DEBUG (cli_lib):: IN: R1 (config) # int fa1/1

* Mar 1 00 DEBUG 54 DEBUG 30.267:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: R1 (config-if) #

* Mar 1 00 DEBUG 54 DEBUG 30.267:% HA_EM-6-LOG: test: DEBUG (cli_lib):: IN: R1 (config-if) # no sh

* Mar 1 00 DEBUG 54 DEBUG 30.359:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: R1 (config-if) #

* Mar 1 00 cli_lib 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 DEBUG 54 DEBUG 30.451:% HA_EM-6-LOG: test: DEBUG (cli_lib):: OUT: R1 (config) #

* Mar 1 00 DEBUG 54 DEBUG 30.455:% HA_EM-6-LOG: test: DEBUG (cli_lib):: CTL: cli_close called.

③ to view the static routes on R1

R1#show ip route static

S* 0.0.0.0 via 0 [1Accord 0] 3.3.3.2-you can see that the route has been switched to R5

[1/0] via 1.1.1.2

Five summaries

The ① static route default always exists in the routing table, unless the default route becomes invalid when the R1 router's own interface fails.

② when the interface directly connected to R1 fails, the default route does not disappear, and a traffic anomaly occurs. This problem can be solved by monitoring the end interface IP through IP SLA.

③ when the traffic is high, if a link fails, it is bound to cause traffic congestion. Through EEM, new interfaces can be automatically enabled to increase bandwidth.

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

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Network Security

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report