Master CCNA

How to Master CCNA Ebook

 

 

My book will help you Master CCNA

Master CCNP SWITCH

How to master CCNP SWITCH ebook

 

 

My book will help you Master CCNP SWITCH

Master CCNP ROUTE

How to master CCNP ROUTE Ebook

 

 

My book will help you Master CCNP ROUTE

Print

IP Service Level Agreement (SLA)

Written by Rene Molenaar on . Posted in Network Services

Scenario:

As the senior network engineer for "Groceries 'r' Us" you are responsible for all routing within the company. Every now and then you have links that are still in the up/up state but you are unable to send any IP packets over them. You also would like something that could generate different traffic streams like RTP to simulate VoIP or HTTP. You heard good things about IP SLA so you decide to build a lab and test some things...

Goal:

  • All IP addresses have been preconfigured for you.
  • OSPF has been configured for full connectivity.
  • Configure router Lettuce to send ICMP echo packets to IP address 4.4.4.4 every 9 seconds. It should never stop.
  • Configure router Cucumber to send DNS request packets to IP address 1.1.1.1 every 8 seconds. It should never stop.
  • Configure router Pickle to send G711 packets to IP address 2.2.2.2 port 16384 with a codec-size of 160 bytes with an interval of 20ms. It should never stop.
  • Configure router Cucumber to respond to the G711 packets.
  • Configure router Tomato to send G729 packets to IP address 3.3.3.3 port 16374 with a codec-size of 20 bytes. It should never stop.
  • Configure router Pickle to respond to the G729 packets.
  • Configure router Lettuce to send HTTP GET packets to IP address 192.168.34.4 every 60 seconds.

IOS:

c3640-jk9o3s-mz.124-16.bin

Topology:

IP SLA

Video Solution:

You need to a flashplayer enabled browser to view this YouTube video

You need to register to download the GNS3 Topology File. (Registration is Free!)

Related Articles
Only registered users can write comments!

Comments (6)

  • avatar
    burleyman

    Thanks for the IP SLA lab. I am going to give it a go. I want to ipmliment this in our enviroment and this will be of great help.

    Thanks for all you time and effort!!

    Mike

  • avatar
    ReneMolenaar

    Hi Mike,

    Your welcome. Keep in mind you can use IP SLA in combination with many things, VRRP, HSRP, GLBP, routing protocols. Everything that works with Object tracking.

    If you have a good real life example after implementing it I'd love to hear it

    Rene8)

  • avatar
    marthin

    Hi Rene,

    Found the following while doing this lab:
    1. Not working

    1.1. The IP SLA operations using "timeout 0" never reached an OK state but stayed down.

    Code:

    Bilbo#sh ip sla mon stat 2
    Round trip time (RTT) Index 2
    Latest RTT: NoConnection/Busy/Timeout
    Latest operation start time: *00:11:58.799 UTC Fri Mar 1 2002
    Latest operation return code: Timeout
    Number of successes: 0
    Number of failures: 90
    Operation time to live: Forever

    1.2. The config is as follows:

    Code:

    ip sla monitor 2
    type echo protocol ipIcmpEcho 192.168.24.4 source-interface Serial2/0
    timeout 0
    frequency 3
    ip sla monitor schedule 2 life forever start-time now

    1.3. Debug output

    Code:

    Bilbo#deb ip sla monitor trace 2
    IP SLA Monitor TRACE debugging for entry 2 is on
    Bilbo#
    *Mar 1 00:08:37.799: IP SLA Monitor(2) Scheduler: Starting an operation
    *Mar 1 00:08:37.803: IP SLA Monitor(2) echo operation: Sending an echo operation
    *Mar 1 00:08:37.807: IP SLA Monitor(2) echo operation: Timeout
    *Mar 1 00:08:37.811: IP SLA Monitor(2) Scheduler: Updating result
    Bilbo#

    2. Worked

    Increasing the timeout value to a reasonable level as expected from the operation in question.

    Code:

    ip sla monitor 1
    type echo protocol ipIcmpEcho 192.168.24.4 source-interface Serial2/0
    timeout 150
    frequency 10
    ip sla monitor schedule 1 life forever start-time now

    Reference:

    http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_05.html#wp1074927

    From the website -

    Quote:

    timeout (IP SLA)

    To set the amount of time a Cisco IOS IP Service Level Agreements (SLAs) operation waits for a response from its request packet, use the timeout (IP SLA) command in the appropriate submode of IP SLA configuration, auto IP SLA MPLS configuration, IP SLA auto Ethernet configuration, IP SLA monitor configuration or IP SLA template parameters configuration mode. To return to the default value, use the no form of this command.

    timeout milliseconds

    no timeout

    Syntax Description

    milliseconds

    Length of time the operation waits to receive a response from its request packet, in milliseconds (ms). Range is 0 to 604800000.

    We recommend that the value of the milliseconds argument be based on the sum of both the maximum round-trip time (RTT) value for the packets and the processing time of the IP SLAs operation.

    Seems like setting the "timeout 0" would actually render the operation unusable.

    This would require peer verification?

    Thanks a stack

    groete
    Marthin

  • avatar
    ReneMolenaar

    Hi Marthin,

    I see you configured one router for IP SLA. Did you set the other for "ip sla monitor responder" ?

    Rene

  • avatar
    shaheer

    Hey Rene,

    I think Martin is right. If you try to enable the responder on router Tomato (4.4.4.4) with timeout value = 0, then the operation would not work because it would timeout at 0 seconds. When I tried to follow your solution and set the timeout to 0, the operation did not work. But, when I left the timeout to value to default (I think its 5 seconds), the operation worked....

    What do you think ??

  • avatar
    ReneMolenaar

    Hi Shaheer,

    I haven't given it much thought yet but it's probably correct. I assumed a timeout of 0 would probably mean "never timeout" but I think that's not the case.

    Rene