RTR Parameters

[rmujeeb81]

Hi All,

Is there any option available to use some timer in rtr configuration like I want to use rtr with type echo in order to check reachability to an specific IP address and based on the status, static route using rtr should wait for specific time period before becoming active in the routing table.

Actually OSPF is running over primary WAN link however I want to configure floating static route with RTR option for backup WAN link. But I also want to avoid traffic flow via backup WAN link in case there is minor flap on the primary WAN link.

Thanks & Regards,

Mujeeb

[Alexander Cousins]

This is possible using a tracked object. With a delay defined under the track object as shown below. 

IP SLA 1 

Icmp-echo 3.3.3.3 

Track 1 IP SLA 1 reachability

Delay down 60 up 60

IP route 1.1.1.1 255.255.255.1 2.2.2.2 track 1 

Apologies for the format I am on a mobile device. 

HTH

[rmujeeb81]

Hi All,

Thanks for your responses. The IOS version running on customer devices is 12.2 and IP SLA option is not available. Only rtr command is available without "track 1 rtr " command. Only track 1 command supported is "track 1 interface ......"

so in this case, that requirement ( which I mentioned in my first post ) can be meet ?

Thanks

[cadet alain]

Hi,

if the Delay command is available under track rtr, yes it is.

if not then maybe it is doable in another way but first let's see if this feature is available.

Regards

Alain

[rmujeeb81]

Hi All,

Thanks for your responses. As the IP SLA monitor command is not supported on current IOS version on respective devices what could be done within OSPF ?

As I mentioned in my first post that OSPF is running over primary WAN link and there is minor flapping on primary WAN link. Now customer wants not to withdraw OSPF routes for some specified time from the routing table in case of primary link gets flapped. Is there a way in OSPF to achieve this ?

Thanks

[Craig Budrodeen]

Hi Mujeeb,

I just tried to run Paul's config from above on my older router that has 'rtr' but not 'ip sla monitor'.

There is no 'event track' option and no 'action <WORD> cli' option so I think you are right you might need to upgrade your IOS if you want to do this.

The operation I used was:

(config)#rtr 1

(config-rtr)#type echo protocol ipIcmpEcho 1.1.1.1 source-ipaddr 2.2.2.2

(config-rtr-echo)#frequency 5

(config-rtr-echo)#exit

(config)#event manager applet Float-Static-Down

(config-applet)#event ?    
  snmp    Add snmp event to Event Manager applet
  syslog  Add syslog event to Event Manager applet

(config-applet)#action 6.0 ?
  cns-event         Add CNS-event action to Event Manager applet
  force-switchover  Add force-switchover action to Event Manager applet
  reload            Add reload action to Event Manager applet
  syslog            Add syslog action to Event Manager applet

[paul driver]

Hello

Yes there is various ways of doing that, object tracking with ip sla.or EEM come to mind

object tracking with ip sla

(Note: next hop interface in example is FastEthernet0/1)

ip sla 1
 icmp-echo (dest ip) source-ip | interface (scr ip or interface)
 frequency 5
ip sla schedule 1 life forever start-time now

track 1 rtr 1 reachability
 delay down 30 up 30

ip route 0.0.0.0 0.0.0.0 FastEthernet0/1 track 1 250

EEM

ip sla 1
 icmp-echo (dest ip) source-ip | interface (scr ip or interface)
 frequency 5
ip sla schedule 1 life forever start-time now

track 1 rtr 1 reachability
 delay down 30 up 30

event manager applet Float-Static-Down

event track 1 state down

action 5.0 cli command "enable"

action 5.1 cli command "conf t"

action 5.2 cli command "ip route 0.0.0.0 0.0.0.0 FastEthernet0/1"

action 5.3 cli command "end"

event manager applet Float-Static-up

event track 1 state up

action 6.0 cli command "enable"

action 6.1 cli command "conf t"

action 6.2 cli command "no "ip route 0.0.0.0 0.0.0.0 FastEthernet0/1"

action 6.3 cli command "end"

res

Paul

[Craig Budrodeen]

Will demonstrate by example.

Say you configured a new RTR operation number 555

PROBE(config)#rtr 555
PROBE(config-rtr)#type tcpConnect dest-ipaddr 2.2.2.2 dest-port 443 control disable
PROBE(config-rtr-tcp)#timeout 1000
PROBE(config-rtr-tcp)#frequency 62
PROBE(config-rtr-tcp)#exit
PROBE(config)#

You then schedule it.

For example, if you wanted to run it for 1 hour (3600 seconds) every day at 0800 hrs you would enter

PROBE(config)#rtr schedule 555 recurring start-time 08:00 life 3600

If you want it to run again at anothher time, add a new schedule.

RTR has been superceded by IP SLA so most of the doco will be found under 'IP SLA' or 'IP SLA MONITOR'.

Hope that helps....

Some of the help...

PROBE(config)#rtr schedule ?
  <1-2147483647>  Entry number

PROBE(config)#rtr schedule 555 ?
  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>

PROBE(config)#rtr schedule 555 recurr
PROBE(config)#rtr schedule 555 recurring ?
  ageout      How long to keep this Entry when inactive
  life        Length of time to execute in seconds
  start-time  When to start this entry
  <cr>

PROBE(config)#rtr schedule 555 recurring star
PROBE(config)#rtr schedule 555 recurring 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

PROBE(config)#rtr schedule 555 recurring start-time 08:00 ?
  <1-31>  Day of the month
  MONTH   Month of the year
  ageout  How long to keep this Entry when inactive
  life    Length of time to execute in seconds
  <cr>

PROBE(config)#rtr schedule 555 recurring start-time 08:00 life 3600 ?
  ageout  How long to keep this Entry when inactive
  <cr>

[paul driver]

Hello

If ils isnt available you can track the line protocol of an interface

track 1 interface xxx line-protocol
delay down 30 up 30
 

res

Paul