It is correct that you can't modify type of packet will simulate the IP SLA once created, but you can edit their parameters (like frequencya and others) of a created IP SLA by stoping or placing the "no" on the "ip scheduled ". After desactivate, you can enter and modify the properties.
i am using packet tracer and selected 2811 routers for this, but in the global configuration mode the "ip sla 1" command is considered unrecognized. is this because I am using virtual routers or due to the ios version. any alternate to this command?
Hi Ben, If we have 2 end router connecting to each other via MPLS cloud but can ping WAN ip of each other. In that case configuring one as responder and other with the ip sla config for either jitter or echo will work ? R1 >> PE>>PE >>> R2 | R1 & R2 can ping WAN and sub interfaces of the each other So putting R1 as responder and R2 with destination of sub interfaceof R1 sourcing R2 subinterface | we can ping all. Will it work
It is correct that you can't modify type of packet will simulate the IP SLA once created, but you can edit their parameters (like frequencya and others) of a created IP SLA by stoping or placing the "no" on the "ip scheduled ". After desactivate, you can enter and modify the properties.
Great Vid, easily helped me understand ICMP echo-based IP SLA which is on the criteria for the CCNA now. Thanks!
CCNA cert does not have too much IP SLA... just the concepts.
Great video, Thanks a lot. It'll work fine for my current issue
Good stuff, but dude do u need to hit ur enter key that loud?
that and he could afford to go a little slower too
i am using packet tracer and selected 2811 routers for this, but in the global configuration mode the "ip sla 1" command is considered unrecognized. is this because I am using virtual routers or due to the ios version. any alternate to this command?
Hi Ben,
If we have 2 end router connecting to each other via MPLS cloud but can ping WAN ip of each other. In that case configuring one as responder and other with the ip sla config for either jitter or echo will work ?
R1 >> PE>>PE >>> R2 | R1 & R2 can ping WAN and sub interfaces of the each other
So putting R1 as responder and R2 with destination of sub interfaceof R1 sourcing R2 subinterface | we can ping all.
Will it work
hi, can i ask if the R2 refers to ISP(PE)?
Thanks!
+iamHas Dib (frEEzE89) Hiya, yes R2 is the remote router (PE)
can you stop slamming the enter key
just kidding
Please don't hit your enter key hardly... We are useing headphone..