You could accompish what is essentially source-routing using policy
routing either via subnet or service. General guidelines below:
access-list 1 permit 192.168.1.0 0.0.0.255
route-map production
match 1
set ip next-hop *atmnexthop*
ip policy route-map production
or like:
access-list 101 permit tcp any any eq 25
access-list 101 permit tcp any any eq 110
route-map production
match 101
set ip next-hop *t1nexthop*
ip policy route-map production
I'm really not sure how it will play into a backup senerio. I think that
if there is a valid route for the traffic that the route will be used as
opposed to policy-routing. This would make things harder. Good luck.
andy
On Wed, 3 Jan 2001, Todd Norton wrote:
> I have two routers, both going to the same location.
>
> 1. Is a dual T1's via Cisco 2610 routers that I manage.
>
> 2. Is a Telco provided 100MB ATM via a managed Cisco 3600 series router.
>
> I want to use the T1 lines for everyday mail and inter-office traffic and
at
> the same time also use the ATM for only "production grade" traffic. I
would
> also like to have each of these services back each other in case of
failures
> if possible.
>
> How can I accomplish one or both of these tasks? Is it possible to say
only
> certain subnets can use specific paths to a desination etc?
>
> Help......
>
>
>
>
> Message Posted at:
> http://www.groupstudy.com/form/read.php?f=1&i=1360&t=1360
> --------------------------------------------------
> You are reading GroupStudy's Associate Mailing List. To unsubscribe follow
> the directions on http://www.groupstudy.com/list/Associates.html
>
Message Posted at:
http://www.groupstudy.com/form/read.php?f=1&i=1361&t=1360
--------------------------------------------------
You are reading GroupStudy's Associate Mailing List. To unsubscribe follow
the directions on http://www.groupstudy.com/list/Associates.html
