cisco ccna-ccnp ip sla configuration

Cisco CCNA IP SLA Configuration

To watch our Cisco CCNA Video Trainings Please Check out the link below:www.asmed.com/c1

ASM Educational Center Inc. (ASM)Where Training, Technology & Service ConvergePhone: (301) 984-7400


Cisco IP SLA (Service Level Agreement) is very similar to concept of Frame-relay – Like Committed information rate. That is your Service Provider ISP, will tell you that you are guaranteed to get particular BW from them , with Min value of something ; but can go to higher value. Same Concept apply to Ip SLA A IP SLA setup consist of source and Responder It is like Agreement between source and responder, we will do a lab on it but we will use the concept of ping , as we see when I put ? , I will see choice of ftp , Http and so on.


Now we will do small Lab;


Now I will do small Lab: R1 will be SLA source =200.1.1.1R2 will be SLA responder =200.1.1.2 R1#config tEnter configuration commands, one per line. End with CNTL/Z.R1(config)#ip slR1(config)#ip sla ? <1-2147483647> Entry Number enable Enable Event Notifications ethernet-monitor IP SLAs Auto Ethernet configuration group Group Configuration or Group Scheduling key-chain Use MD5 authentication for IP SLAs Control Messages logging Enable Syslog low-memory Configure Low Water Memory Mark reaction-configuration IP SLAs Reaction-Configuration reaction-trigger IP SLAs Trigger Assignment reset IP SLAs Reset responder Enable IP SLAs Responder restart Restart An Active Entry schedule IP SLAs Entry Scheduling


R1(config)#ip sla 1R1(config-ip-sla)#?IP SLAs entry configuration commands: dhcp DHCP Operation dns DNS Query Operation ethernet Ethernet Operations exit Exit Operation Configuration frame-relay Frame-relay Operation ftp FTP Operation http HTTP Operation icmp-echo ICMP Echo Operation icmp-jitter ICMP Jitter Operation path-echo Path Discovered ICMP Echo Operation path-jitter Path Discovered ICMP Jitter Operation tcp-connect TCP Connect Operation udp-echo UDP Echo Operation udp-jitter UDP Jitter Operation voip Voice Over IP Operation


as we see we can do a lots of stuff but we will do simple Ping ( and test it with icmp-echo) Now we will use 200.1.1.2 as target of test Also in here I can use the source address , but i press enter ( sicne it will be 200.1.1.1) R1(config-ip-sla)#R1(config-ip-sla)#icmp-echo ? Hostname or A.B.C.D Destination IP address or hostname, broadcast disallowed R1(config-ip-sla)#icmp-echo 200.1.1.2 ? source-interface Source Interface (ingress icmp packet interface) source-ip Source Address <cr> R1(config-ip-sla)#icmp-echo 200.1.1.2R1(config-ip-sla-echo)#


Step 2) Now set the frequency test between R1 and R2 , Default value=60 sec , R1(config-ip-sla-echo)#?IP SLAs echo Configuration Commands: default Set a command to its defaults exit Exit operation configuration frequency Frequency of an operation history History and Distribution Data no Negate a command or set its defaults owner Owner of Entry request-data-size Request data size tag User defined tag threshold Operation threshold in milliseconds timeout Timeout of an operation tos Type Of Service verify-data Verify data vrf Configure IP SLAs for a VPN Routing/Forwarding instance


R1(config-ip-sla-echo)#frequency ? <1-604800> Frequency in seconds (default 60) R1(config-ip-sla-echo)#frequency 60 ? <cr> R1(config-ip-sla-echo)#frequency 60R1(config-ip-sla-echo)# here is show run as we see the frequency 60 sec does notshow up , but I will change it to 30 sec R1#show run ip sla 1 icmp-echo 200.1.1.2


R1#config tEnter configuration commands, one per line. End with CNTL/Z.R1(config)#ip slR1(config)#ip sla 1R1(config-ip-sla-echo)#frR1(config-ip-sla-echo)#frequency 30R1(config-ip-sla-echo)# here is show run ip sla 1 icmp-echo 200.1.1.2 frequency 30

!


step 3) Now we go to global configuration and schedule this test to run right now---- R1#config tEnter configuration commands, one per line. End with CNTL/Z.R1(config)#ip sla ? <1-2147483647> Entry Number enable Enable Event Notifications ethernet-monitor IP SLAs Auto Ethernet configuration group Group Configuration or Group Scheduling key-chain Use MD5 authentication for IP SLAs Control Messages logging Enable Syslog low-memory Configure Low Water Memory Mark reaction-configuration IP SLAs Reaction-Configuration reaction-trigger IP SLAs Trigger Assignment reset IP SLAs Reset responder Enable IP SLAs Responder restart Restart An Active Entry schedule IP SLAs Entry Scheduling R1(config)#ip sla schR1(config)#ip sla schedule ? <1-2147483647> Entry number


R1(config)#ip sla schedule 1 ? ageout How long to keep this Entry when inactive life Length of time to execute in seconds recurring Probe to be scheduled automatically every day start-time When to start this entry <cr> R1(config)#ip sla schedule 1 stR1(config)#ip sla schedule 1 start-time ? after Start after a certain amount of time from now hh:mm Start time (hh:mm) hh:mm:ss Start time (hh:mm:ss) now Start now pending Start pending


R1(config)#ip sla schedule 1 start-time noR1(config)#ip sla schedule 1 start-time now ? ageout How long to keep this Entry when inactive life Length of time to execute in seconds recurring Probe to be scheduled automatically every day <cr> R1(config)#ip sla schedule 1 start-time nowR1(config)#


Here is show run up to now: ip sla 1 icmp-echo 200.1.1.2 frequency 30ip sla schedule 1 start-time now!!


Let’s look at some show commands R1#show ip sla configurationIP SLAs Infrastructure Engine-IIEntry number: 1Owner:Tag:Type of operation to perform: echoTarget address/Source address: 200.1.1.2/0.0.0.0Type Of Service parameter: 0x0Request size (ARR data portion): 28Operation timeout (milliseconds): 5000Verify data: NoVrf Name:


Schedule: Operation frequency (seconds): 30 (not considered if randomly scheduled) Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Randomly Scheduled : FALSE Life (seconds): 3600 Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): ActiveThreshold (milliseconds): 5000 (not considered if react RTT is configured)Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20History Statistics: Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: NoneEnhanced History:


Here we see IP SLA number =1 Frequency every 30 secwe see this (Next Scheduled Start Time: Start Time already passed) it means it startedtype of operation is echoTarget address/Source address: 200.1.1.2/0.0.0.0 (this means the destination is 200.1.1.2 and source is same as R1 interface which we did not tell the router that is why it is 0.0.0.0) TTL=3600 sec Here is another show command: R1#show ip sla stR1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:05:08.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 22Number of failures: 1Operation time to live: 2924 sec


R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:05:38.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 23Number of failures: 1Operation time to live: 2892 sec R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:06:08.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 24Number of failures: 1Operation time to live: 2874 sec


as we see the number increase from success 22 to 23 Hint: If you made mistake ip SLA you cannot edit it , let’s see what I mean: here is show run R1#ip sla 1 icmp-echo 200.1.1.2 frequency 30ip sla schedule 1 start-time now R1(config)#ip sla 1%Entry already running and cannot be modified (only can delete (no) and start over) (check to see if the probe has finished exiting)


notice That I did not go to destination R2 and do Ip SLA responder , since I was running the basic ICMP echo test, and i did not need to do it ,since the responder can handle pinging , for other test , we need go to R2 and do the commands IP SLA responder


Now lest go to R2 and shut down the port f0/1=200.1.1.2 Here is before changes: R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:11:08.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 34Number of failures: 1Operation time to live: 2577 sec R2#config tEnter configuration commands, one per line. End with CNTL/Z.R2(config)#int f0/0R2(config-if)#shut


As we see in below it went from Number of failure to 2

R1#show ip sla statistics

IPSLAs Latest Operation Statistics

IPSLA operation id: 1

Latest RTT: NoConnection/Busy/Timeout ( here we see this new message )

Latest operation start time: *01:12:08.035 UTC Thu Dec 8 2016

Latest operation return code: Timeout

Number of successes: 35

Number of failures: 2

Operation time to live: 2508 sec


Now it went to 3 R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: NoConnection/Busy/Timeout ( here we see this new message )Latest operation start time: *01:12:38.035 UTC Thu Dec 8 2016Latest operation return code: TimeoutNumber of successes: 35Number of failures: 3Operation time to live: 2467 sec


R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: NoConnection/Busy/Timeout ( here we see this new message )Latest operation start time: *01:13:08.035 UTC Thu Dec 8 2016Latest operation return code: TimeoutNumber of successes: 35Number of failures: 4Operation time to live: 2443 sec


Now I go to R2 and put IP SLA responder under the global configuration R2#config tEnter configuration commands, one per line. End with CNTL/Z.R2(config)#int f0/0R2(config-if)#no shutR2(config-if)#*Dec 7 21:08:37.623: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up*Dec 7 21:08:38.623: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upR2(config-if)#

Cisco CCNA IP SLA ConfigurationR2(config)#ip sla ? <1-2147483647> Entry Number enable Enable Event Notifications ethernet-monitor IP SLAs Auto Ethernet configuration group Group Configuration or Group Scheduling key-chain Use MD5 authentication for IP SLAs Control Messages logging Enable Syslog low-memory Configure Low Water Memory Mark reaction-configuration IP SLAs Reaction-Configuration reaction-trigger IP SLAs Trigger Assignment reset IP SLAs Reset responder Enable IP SLAs Responder restart Restart An Active Entry schedule IP SLAs Entry Scheduling R2(config)#ip sla responder ? auto-register Setup auto-register to hub tcp-connect Setup tcp-connect responder udp-echo Setup udp-echo responder <cr>

Cisco CCNA IP SLA ConfigurationStep 5) we can secure our SLA config with a Keychain and IP sla key-chain commands make sure the key-string ( which is your password is the same) the name which is CCNP1 and CCNP2 are local significance ; but key has be same First I do R1 R1#R1#config tEnter configuration commands, one per line. End with CNTL/Z.R1(config)#key ? chain Key-chain management config-key Set a private configuration key for general use R1(config)#key chR1(config)#key chain ? WORD Key-chain name R1(config)#key chain CCNP1 ? <cr>

Cisco CCNA IP SLA ConfigurationR1(config)#key chain CCNP1R1(config-keychain)#?Key-chain configuration commands: default Set a command to its defaults exit Exit from key-chain configuration mode key Configure a key no Negate a command or set its defaults R1(config-keychain)#key ? <0-2147483647> Key identifier R1(config-keychain)#key 1R1(config-keychain-key)#?Key-chain key configuration commands: accept-lifetime Set accept lifetime of key default Set a command to its defaults exit Exit from key-chain key configuration mode key-string Set key string no Negate a command or set its defaults send-lifetime Set send lifetime of key

Cisco CCNA IP SLA ConfigurationR1(config-keychain-key)#keyR1(config-keychain-key)#key-string TESTR1(config-keychain-key)#R1(config-keychain-key)#exitR1(config-keychain)#exitR1(config)#R1(config)#R1(config)#ip sla keyR1(config)#ip sla key-chain CCNP1R1(config)#

Cisco CCNA IP SLA ConfigurationHere is show run on R1: R1#show run key chain CCNP1 key 1 key-string TEST ip sla key-chain CCNP1ip sla 1 icmp-echo 200.1.1.2 frequency 30ip sla schedule 1 start-time now

Cisco CCNA IP SLA ConfigurationNow I go to R2 and do same concept with CCNP2 name but same key-string (since it is our password) R2#R2#config tEnter configuration commands, one per line. End with CNTL/Z.R2(config)#key ? chain Key-chain management config-key Set a private configuration key for general use R2(config)#key chR2(config)#key chain ? WORD Key-chain name

Cisco CCNA IP SLA ConfigurationR2(config)#key chain CCNP2R2(config-keychain)#?Key-chain configuration commands: default Set a command to its defaults exit Exit from key-chain configuration mode key Configure a key no Negate a command or set its defaults

Cisco CCNA IP SLA ConfigurationR2(config-keychain)#key 1 ? <cr> R2(config-keychain)#key 1R2(config-keychain-key)#?Key-chain key configuration commands: accept-lifetime Set accept lifetime of key default Set a command to its defaults exit Exit from key-chain key configuration mode key-string Set key string no Negate a command or set its defaults send-lifetime Set send lifetime of key

Cisco CCNA IP SLA ConfigurationR2(config-keychain-key)#keysR2(config-keychain-key)#key-R2(config-keychain-key)#key-string ? 0 Specifies an UNENCRYPTED password will follow 7 Specifies a HIDDEN password will follow LINE The UNENCRYPTED (cleartext) user password R2(config-keychain-key)#key-string TESTR2(config-keychain-key)#exitR2(config-keychain)#exitR2(config)#R2(config)#R2(config)#ip sla key-R2(config)#ip sla key-chain CCNP2R2(config)#

Cisco CCNA IP SLA ConfigurationHere is show run: R2# key chain CCNP2 key 1 key-string TEST! !ip sla responderip sla key-chain CCNP2 Now let’s check the show statistic commands

Cisco CCNA IP SLA ConfigurationR1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 milliseconds ( This means life is good) Latest operation start time: *01:26:08.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 56Number of failures: 9Operation time to live: 1673 sec

Cisco CCNA IP SLA ConfigurationR1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:28:08.035 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 60 ( as we see after some time ,it is good now)Number of failures: 9Operation time to live: 1552 sec

Cisco CCNA IP SLA ConfigurationHere notice I removed IP SLA with no commands and rebuild it and that is why it started from low number again... R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:42:24.651 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 5Number of failures: 0Operation time to live: 3463 sec

Cisco CCNA IP SLA ConfigurationR1#R1#R1#R1#R1#show ip sla statisticsIPSLAs Latest Operation Statistics IPSLA operation id: 1 Latest RTT: 1 millisecondsLatest operation start time: *01:43:24.651 UTC Thu Dec 8 2016Latest operation return code: OKNumber of successes: 7Number of failures: 0Operation time to live: 3403 sec

ASM Educational Center Inc. (ASM)Where Training, Technology & Service Converge

To watch our Cisco CCNA Video Trainings Please Check out the link below:www.asmed.com/c1

Phone: (301) 984-7400