RTR tracking without IP SLA feature

Discussion in 'Cisco' started by seabird505, May 27, 2010.

  1. seabird505

    seabird505

    Joined:
    May 27, 2010
    Messages:
    2
    Hi

    We are using the following image on our production layer-3 switch
    Code:
    IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF11, RELEASE SOFTWARE (fc1)
    There is no support for IP SLA in the current version. But it seems there is no support for "track 2 rtr 10 reachability" and "ip route x y z track 1" type of commands either. While the following commands are accepted
    Code:
    # rtr 10
              # type echo protocol ipIcmpEcho 10.10.10.10
              # frequency 2 
              # request-data-size 32
              # timeout 1000
                            
    # rtr schedule 10 life forever start-time now
    
    How to make the following work on the current IOS. Is there an alternative to achieve the same or is IOS upgrade a must???
    Code:
    # track 2 rtr 10 reachability 
    # track 1 list boolean and
              # object 2 not
                            
    ip route 11.11.11.0 255.255.255.0 12.12.12.12 track 1
    
    P.S. The objective is to install a static route for network 11.11.11.0/24 towards 12.12.12.12 when the device at 10.10.10.10 (not directly connected) is NOT reachable. This will be backup route for the remote 10 network. We don't have dynamic routing or vpn in between. Any ideas??

    Thanks.
     
    seabird505, May 27, 2010
    #1
    1. Advertising

  2. seabird505

    seabird505

    Joined:
    May 27, 2010
    Messages:
    2
    Solution

    Got the solution from another forum.

    For the benefit of others, I am pasting the sample config in here.


    Code:
    rtr 10
      type echo protocol ipIcmpEcho 10.10.10.10
      timeout 1000
      frequency 3
      request-data-size 32
    rtr schedule 10 life forever start-time now
    !
    event manager applet EEM_PRIMARY_DOWN
      event snmp oid 1.3.6.1.4.1.9.9.42.1.2.9.1.6.10 get-type exact entry-op eq entry-val 1 exit-op eq exit-val 2 poll-interval 3
      action 1.0 syslog msg "Primary link DOWN - Failing over to backup link"
      action 1.1 cli command "enable"
      action 1.2 cli command "configure terminal"
      action 1.3 cli command "ip route 11.11.11.0 255.255.255.0 12.12.12.12"
    !
    event manager applet EEM_PRIMARY_UP
      event snmp oid 1.3.6.1.4.1.9.9.42.1.2.9.1.6.10 get-type exact entry-op eq entry-val 2 exit-op eq exit-val 1 poll-interval 3
      action 1.0 syslog msg "Primary link UP - Failing over to primary link"
      action 1.1 cli command "enable"
      action 1.2 cli command "configure terminal"
      action 1.3 cli command "no ip route 11.11.11.0 255.255.255.0 12.12.12.12"
    
    !
    

    Explanation for OID value can be found here
    tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=rttMonCtrlOperTimeoutOccurred


    The last .10 in the OID value is your RTR (or IP SLA) number.
     
    seabird505, May 28, 2010
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Bob Simon
    Replies:
    8
    Views:
    7,190
    John Lamar
    Jan 19, 2005
  2. Edw. Peach

    Tracking Someone Tracking Me

    Edw. Peach, Jun 15, 2005, in forum: Computer Security
    Replies:
    4
    Views:
    701
    Olden Doode
    Jul 7, 2005
  3. AM

    IP SLA or RTR.

    AM, Jan 13, 2007, in forum: Cisco
    Replies:
    1
    Views:
    1,229
    Darren Green
    Jan 14, 2007
  4. Christian Schuetz

    SNMP MIB Object - <RTR> or <IP SLA>

    Christian Schuetz, Aug 9, 2007, in forum: Cisco
    Replies:
    0
    Views:
    774
    Christian Schuetz
    Aug 9, 2007
  5. Rudi
    Replies:
    2
    Views:
    6,190
Loading...

Share This Page