Multiple Connections between locations

[fnbt]

We recently installed a 768k Frame Realy connection to an office that is already serviced by a T1 connection.

We want to use this FR connection to carry traffic for 2 specific hosts.

I have been looking at various methods in order to do this, but have been unable to get one to work properly.

They both terminate at the same place (our head end 7206)...

Config for new interface

interface Serial0/1

description This the 768 Frame for IP

bandwidth 768

no ip address

encapsulation frame-relay IETF

no ip mroute-cache

load-interval 30

keepalive 8

max-reserved-bandwidth 100

frame-relay traffic-shaping

frame-relay lmi-type ansi

!

interface Serial0/1.111 point-to-point

description 768 for IP

bandwidth 768

ip address 192.168.4.78 255.255.255.252

ip access-group 125 out

frame-relay interface-dlci 111

!

Any ideas would be apreciated.

[a.awan]

Is this new link terminating on the same router that terminates the existing T1 on the remote side? Have you looked at policy based routing? Using policy based routing you can force traffic to/from these two hosts out an interface of your choice while the normal traffic follows the paths established via your routing configurations (static or dynamic).

[fnbt]

Yes the links terminate on the same router on this end. One comes into a channelized DS3 and the other is a Frame Relay DS3.

[geoff.belknap]

Is the traffic you describe:

1. Traffic TO 2 specific hosts, OR

2. Traffic FROM 2 specific hosts

Traffic TO 2 Specific hosts can be handled simply with static routes.

Traffic FROM 2 Specific hosts can be routed down the correct path via Policy Based Routing.

For example:

access-list 140 permit ip host 192.168.1.1 192.168.2.1 0.0.0.255

! (ACL Matches Traffic from Host 192.168.1.1 to 192.168.2.1)

!

route-map SBR permit 10

match ip address 140

set ip next-hop 192.168.3.1

! (Route-Map set the new next-hop of traffic matching ACL 140)

!

interface FastEthernet1/1

ip policy route-map SBR

! (Traffic passing this interface is evaluated by the route-map)

!

Hope this helps,

-Geoff

[fnbt]

The next hop, does that need to be the IP on the serial interface on the router or the ip address on the interface on the router at the other end?

[a.awan]

Next hop will be the ip address of the remote router's serial interface. With policy based routing do keep in mind that it applies only to traffic coming into an interface so place your maps accordingly.

[fnbt]

Yes yit is the second of those 2 options.

The other question that comes to mind is the ACL.

If we want to limit traffic to that interface then the ACL would be like this?

access-list 140 permit ip host 192.168.1.50 any

access-list 140 permit ip host 192.168.1.51 any

access-list 140deny ip any any

[geoff.belknap]

This ACL will work. But, you dont need the deny statement. The ACL has an implicit deny at the end and only applies to the policy route-map.

[fnbt]

Thanks for the help. That is working great for us.