Need Cisco Configuration Help...

[KFC911]

I'd wait for a Cisco guru to reply, but from my experience, assigning a routing "metric" will assign a "weight" to that route, thus making it a less desirable path in the routing algorithm. Caveat: I've seen many instances where the "metrics" don't quite work as advertised, so if there is a way to make one route a "default" (typically the first in the list), that may be a "better" option. If not, assign a metric to all the routes you DON'T want to use first.

[Scott R]

Wayne, you may need to configure priority routing and QOSm. Have you done that before?

[masraum]

If I understand correctly, your network is hanging off of F0/0, your current Internet connection is off of the 4 serials, but you have a new internet connection on F0/1 (metro ethernet or SDSL or something), and you want to route based on the source IP of the traffic, not the destination.
something like this


IIRC, what you need is policy routing. Basically you'll create a route-map that says something like "match access-list 101" (acl 101 will define traffic from 66.236.106.66/224 to anywhere) and then it will "set next hop" or "set interface". Then I think you'll have a second policy that is either empty or says match all which will catch the rest of the traffic and allow it to go the normal route.

I think this may help http://cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009481d.shtml

If you need anything else or any assistance just let me know. If I don't have a complete understanding of what you are trying to do let me know.8

[masraum]

I think this is what you are looking for.

!
interface FastEthernet0/0
ip policy route-map test
!
!
access-list 111 permit ip 66.236.106.66 0.0.0.31 any
!
route-map test permit 10
match ip address 111
set interface FastEthernet0/1
!
route-map net-10 permit 20
!

[masraum]

Originally Posted by mikester

What tools do you use to monitor the traffic per interface? My guess is that most of your traffic exits the Serial 0/0 interface. I would be somewhat surprised based on the config snips I've seen if any traffic went out the other interfaces (except local subnet traffic).

By default Cisco routers will load balance using static routes. It may be session based or packet based or flow based, but it should balance with the above settings.

A "show Interface summary" should show traffic per interface.

Here's a snippet from a router that's currently in production that has 3 T1s with 3 default routes on one side and 3 sets of routes on the other.

Interface IHQ IQD OHQ OQD RXBS RXPS TXBS TXPS TRTL
------------------------------------------------------------------------
* Serial0/0/0:0 0 0 0 0 95000 100 222000 131 0
* Serial0/0/1:0 0 0 0 0 118000 170 100000 73 0
* Serial0/1/0:0 0 0 0 0 164000 164 315000 209 0

[mikester]

Steve is correct - I stayed up too late last night.

[mikester]

Show us how you put in Steve's example.

That should have worked.

[ianc]

I don't really understand what you're trying to accomplish, but:

The route statements work like this - when you enter a route, then you are telling the router to use that route to REACH a destination network. The statement:

ip route 66.236.106.64 255.255.255.224 FastEthernet0/0

Is telling the router that to reach destination subnet 66.236.106.64, it should use int Fe0/0. When the router receives traffic bound for this subnet, it will forward it through Fe0/0. Likewise the other explicit route statement you've entered.

The default route statements are just that. If you don't have traffic bound for either 66.236.106.64 or 67.93.43.160, it will use the serial ints.

Try to explain what you're trying to achieve a little more clearly, in terms of both inbound and outbound traffic.

ianc

[masraum]

Wayne, was my summary correct? You have a block of IPs that should use the new connection to get to the internet?

I just realized, there were two mistakes in my previous config, 1, the second part of the policy map had the wrong name, and two the access-list was wrong. .66 isn't the network. .64 is the network. I've made those changes below.

interface FastEthernet1
ip policy route-map test
!
!
access-list 111 permit ip 66.236.106.64 0.0.0.31 any
!
route-map test permit 10
match ip address 111
set interface FastEthernet0/1
!
route-map test permit 20
!

Just a static route won't work, because the route is based on the destination of the traffic. So when you put a route in a router any traffic that hits that router will follow first the most specific, and then the lowest cost route out of the router. The router doesn't care where the traffic came from, only where it's going.

Can you try it again and send me the results of your trace route?

[masraum]

Wayne, ever get it working?