From: Mike Ollington (Mike.Ollington@uk.didata.com)
Date: Thu Jan 05 2006 - 18:57:01 GMT-3
You could use PBR and RTR to track the ISPs serial interface.
If the pings fail, the PBR will fall back to the normal EIGRP-derived routing
table.
hostname R2
interface fa0/0
ip addr 192.168.64.4 255.255.255.0
ip policy route-map PBR
rtr 1
type echo protocol ipicmpecho x.x.x.x (ISPs out side interface)
rtr schedule 1 start-time now life forever
!
track 1 rtr 1 reachability
route-map PBR permit 10
match ip address name someinteresting-traffic
set ip next-hop verify-availability 192.168.64.1 10 track 1
ip access-list extended someinteresting-traffic
permit ip host 1.1.1.1 host 2.2.2.2
-----Original Message-----
From: nobody@groupstudy.com on behalf of Anh Tran
Sent: Thu 1/5/2006 9:40 PM
To: Cisco certification
Cc:
Subject: Solution for this scenario
Hello Group,
There is 2 router. One is ISP's router (R1) that I can't touch and other is
my core router (R2) that I can do anything I want.
The R1e0/0 is 192.168.64.1 and there is a static route 0.0.0.0/0 to it
serial interface.
My E2 e0/0 is 192.168.64.4 running EIGRP to my company.
Is there any solution, if I put my LAN gateway is 192.168.64.4 and R2 will
route to 192.168.64.1 if R1's serial is up and if R1's serial down (PTT
problem) R2 will route via it's EIGRP. There problem here is R1 can be
modify (ISP rule) and there is only one static route here in this router.
Many thank for your help.
Best regards.
Thach Anh
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:47 GMT-3