Cisco's IP SLA instance application-end-to-end availability dynamic monitoring

The IP SLA is an abbreviation for the Internet Protocol Service-level Agreement, which means the Internet Protocol Service level agreement. IP SLAs are mainly used in the following situations:

1. Static route Next-hop detection.

2.HSRP out interface detection.

The 3.PBR policy routes the next hop detection.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/57/FC/wKioL1SmILHwbsxeAACejqdLipI961.jpg "title=" catch. PNG " alt= "Wkiol1smilhwbsxeaacejqdlipi961.jpg"/> This article is mainly to static routing next hop accessibility detection, as an example of the role and configuration of IP SLA:

For some reason, R1 and R2 pass through the intermediate transmission equipment.

After the interface has been configured by the experiment, two default routes are configured on R1 and R2 respectively, so that the R2 of R1 192.168.1.0 and 192.168.2.0 can communicate with each other.

R1#sh Run | Se IP route

IP Route 0.0.0.0 0.0.0.0 1.1.1.3

IP Route 0.0.0.0 0.0.0.0 2.2.2.3

R2#sh Run | Se IP route

IP Route 0.0.0.0 0.0.0.0 1.1.1.1

IP Route 0.0.0.0 0.0.0.0 2.2.2.2

To view routes:

R1#sh IP route

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

[1/0] via 1.1.1.3

R2#sh IP route

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

[1/0] via 1.1.1.1

R1 and R2 two equivalent load balanced routes

1, in the middle of the transparent setting, R2 on the E0/1 port down, R1 E0/1 will be down, this route will automatically disappear, switch to another route. Business is not affected;

2, after the transparent equipment, R2 on the E0/1 port down, due to R1 E0/1 connection transparent equipment, the port will not be down. At this point the R1 router thinks the route is still valid, so the packet is thrown to the routing, resulting in packet loss, affecting the business.

So in R1 and R2 is the SLA can be configured to implement route tracking, the main configuration commands:

(config) # IP SLA monitor 1

Create a service entry

(config-sla-monitor) # type echo protocol Ipicmpecho 1.1.1.1 SOURCE-IPADDR 1.1.1.3

Set up monitoring ICPM echo monitoring routing entries for the next hop IP packets leaving the router's out-of-Interface IP address

(Config-sla-monitor) #timeout 1000

Set the time-out to 1000ms

(Config-sla-monitor) #frequency 3

Set the frequency to 3 (3s a package)

(config) #ip SLA monitor Schedule 1 life Forever Start-time Now

Set the start time of the SLA as immediate and valid for forever

(config) #track 1 rtr 1reachability

Associated with track entry and response entries, track cares for accessibility

(config) #ip Route 0.0.0.0 0.0.0.0 1.1.1.3 Track 1

Set up static routes and use entry 1 to monitor

Edit this section IP SLA effect view

# show IP SLA monitor configuration//view Config

Configure R1

R1#sh Run | SE IP SLA

IP SLA Monitor 1

Type echo protocol Ipicmpecho 1.1.1.3 Source-ipaddr 1.1.1.1

Timeout 1000

Frequency 3

IP SLA Monitor Schedule 1 life Forever Start-time Now

IP SLA Monitor 2

Type echo protocol Ipicmpecho 2.2.2.3 SOURCE-IPADDR 2.2.2.2

Timeout 1000

Frequency 3

IP SLA Monitor Schedule 2 life Forever Start-time Now

R1#sh Run | SE Track

Track 1 RTR 1 reachability

Track 2 RTR 2 reachability

IP Route 0.0.0.0 0.0.0.0 1.1.1.3 Track 1

IP Route 0.0.0.0 0.0.0.0 2.2.2.3 Track 2

r1#

R2 configuration is basically consistent with R1 ~

This article is from the "It Rookie" blog, make sure to keep this source http://slliang.blog.51cto.com/6959776/1598407

Cisco's IP SLA instance application-end-to-end availability dynamic monitoring