not sure why you would ever do this (well the CCIE lab i guess??? and i used
static routes i guess you could do the same with tracking and dynmaic
routes??? not sure about that one...) or if this meets the requirements but
it 'works' for lack of a better term...
Router1---(f0/0 1.1.1.2), int tunnel 200 192.168.1.1)
ip sla monitor 2
type echo protocol ipIcmpEcho 100.100.100.1
frequency 30
ip sla monitor schedule 2 life forever start-time now
track 2 rtr 2 reachability
interface Tunnel200
ip address 192.168.1.1 255.255.255.0
keepalive 10 3
tunnel source 1.1.1.2
tunnel destination 200.200.200.1
ip route 200.200.200.0 255.255.255.0 1.1.1.1 10 track 2
ip route 100.100.100.0 255.255.255.0 1.1.1.1 100
ip route 200.200.200.0 255.255.255.0 Null0 22
|
|
|
Router 0 ----(f0/0 1.1.1.1, f0/1 3.3.3.1, int tunnel 200 192.168.1.2)
|
|
|
Router 2---(Loop 0 100.100.100.1, f0/0 3.3.3.2)
R1:
R1#sh ip route
Gateway of last resort is not set
S 200.200.200.0/24 [10/0] via 1.1.1.1
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, FastEthernet0/0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [100/0] via 1.1.1.1
R 3.0.0.0/8 [120/1] via 1.1.1.1, 00:00:03, FastEthernet0/0
C 192.168.1.0/24 is directly connected, Tunnel200
R1#sh ip int br
Interface IP-Address OK? Method Status
Protocol
FastEthernet0/0 1.1.1.2 YES manual up
up
FastEthernet0/1 unassigned YES unset administratively down
down
Tunnel200 192.168.1.1 YES manual up
up
R2:
R2(config)#int loopback 0 ***SHUTTING DOWN THE TRACKED 100.100.100.1
HERE****
R2(config-if)#shut
R2(config-if)#
*Mar 1 00:30:12.535: %LINK-5-CHANGED: Interface Loopback0, changed state to
administratively down
*Mar 1 00:30:13.535: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Loopback0, changed state to down
R2(config-if)#do sh ip int br
Interface IP-Address OK? Method Status
Protocol
FastEthernet0/0 3.3.3.2 YES manual up
up
FastEthernet0/1 unassigned YES unset administratively down
down
Loopback0 100.100.100.1 YES manual administratively down
down
R1: wait for the KEEPALIVES to KICK IN
R1#
*Mar 1 02:24:08.035: %TRACKING-5-STATE: 2 rtr 2 reachability Up->Down
*Mar 1 02:24:24.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Tunnel200, changed state to down
R1#sh ip route
Gateway of last resort is not set
S 200.200.200.0/24 is directly connected, Null0
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.1.0 is directly connected, FastEthernet0/0
100.0.0.0/24 is subnetted, 1 subnets
S 100.100.100.0 [100/0] via 1.1.1.1
R 3.0.0.0/8 [120/1] via 1.1.1.1, 00:00:05, FastEthernet0/0
R 192.168.1.0/24 [120/1] via 1.1.1.1, 00:00:05, FastEthernet0/0
R1#sh ip int br
Interface IP-Address OK? Method Status
Protocol
FastEthernet0/0 1.1.1.2 YES manual up
up
FastEthernet0/1 unassigned YES unset administratively down
down
Tunnel200 192.168.1.1 YES manual up
down
On Sun, Oct 18, 2009 at 1:08 PM, Thameem Maranveetil Parambath <
security.goodie_at_gmail.com> wrote:
> dears I have a scenario like this.. can some one give some solution?
>
>
> Router1
> |
> |
> |
> Router 2
> |
> |
> |
> Router 3 ---(10.119.0.0)
>
> Router1 and Router2 should have interface tunnel up and running. In router
> 2 , i have to create an object tracking(IPSLA) on one IP (10.119.0.2) which
> is beyound Router 3. When the IP is not reachable, i have to bring down
> the
> interface tunnel between Router 1 and Router 2.
>
> Can some one help?
>
> Regards,
> Thameem
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Garry L. Baker "There is no 'patch' for stupidity." - www.sqlsecurity.com Blogs and organic groups at http://www.ccie.netReceived on Sun Oct 18 2009 - 14:37:07 ART
This archive was generated by hypermail 2.2.0 : Sun Nov 01 2009 - 07:51:00 ART