Ccna routing and Switching Complete Study Guide

telnet 172.16.20.254 80

Trying 172.16.20.254, 80 ... Open

Yes—finally! Server1 is responding to requests on port 80, so we’re in the clear.

Using IP SLA for Troubleshooting

I want to mention one more thing that can help you troubleshoot your IP network, and this 

is using IP service-level agreements (SLAs), which will allow us to use IP SLA ICMP echo to 

test far-end devices instead of pinging manually.

There are several reasons to use the IP SLA measurements:

 

■

Edge-to-edge network availability monitoring

 

■

For example, packet loss statistics

 

■

Network performance monitoring and network performance visibility

 

■

For example, network latency and response time

 

■

Troubleshooting basic network operation

 

■

For example, end-to-end network connectivity

Step 1: Enable an IP SLA operation that enters the IP SLA configuration mode. Chose 

any number from 1 to 2.1 billion as an operation number.

R1(config)#

ip sla 1

Step 2: Configure the IP SLA ICMP echo test and destination.

R1(config-ip-sla)#

icmp?

icmp-echo  icmp-jitter

 

R1(config-ip-sla)#

icmp-echo ?

  Hostname or X:X:X:X::X

  Hostname or A.B.C.D  Destination IPv6/IP address or hostname

 

R1(config-ip-sla)#