ip policy route-map 1721 Problem.

Unanswered Question
Jan 30th, 2007

Hello,

I have a router 1721 with three interfaces.

- FastEthernet0 is LAN.

- Ethernet0 is WAN and is connected to provider1.

- Ethernet1 is WAN and is connected to provider2.

The two providers are up and they are routing traffic without problems.

I have too the following "ip policy route-map" for SMTP since 4th of January:

access-list 160 permit tcp any any eq smtp

route-map correo permit 10

match ip address 160

set interface Ethernet0 Ethernet1

!

route-map correo permit 20

!

interface FastEthernet0

ip address 10.100.50.2 255.255.255.248

ip policy route-map correo

end

Everything was working ok for SMTP untill this afternoon. The ip policy started to not to route and I couldn't route SMTP.

I had to remove the config "ip policy route-map correo" from FasEthernet0 and then SMTP started to be routed ok again.

After this I tried to shutdown Provider1 and then Provider2 (to see if someone was filtering) but everything was ok.

This is the router:

Cisco IOS Software, C1700 Software (C1700-IPBASE-M), Version 12.4(1c), RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2005 by Cisco Systems, Inc.

Compiled Wed 26-Oct-05 06:46 by evmiller

ROM: System Bootstrap, Version 12.2(7r)XM2, RELEASE SOFTWARE (fc1)

cbcnrvue7 uptime is 21 hours, 17 minutes

System returned to ROM by power-on

System restarted at 02:17:10 UTC Tue Jan 30 2007

System image file is "flash:c1700-ipbase-mz.124-1c.bin"

Cisco 1721 (MPC860P) processor (revision 0x500) with 58373K/7163K bytes of memory.

Processor board ID FOC101917X4 (3369828695), with hardware revision 0000

MPC860P processor: part number 5, mask 2

2 Ethernet interfaces

1 FastEthernet interface

32K bytes of NVRAM.

32768K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

Is there any bug that can do the ip policy not to work suddenly when it was working ok untill today?

Thanks for your help.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
b.hsu Tue, 02/06/2007 - 06:27

The most common reason for this problem is a misconfigured or missing Access Control List (ACL).For each combination of match and set commands in a route map statement, all sequential match clauses must be met simultaneously by the packet for the set clauses to be applied. There may be multiple sets of combinations of match and set commands in a full route map statement. For more information on configuring match and set clauses, refer to http://www.cisco.com/en/US/products/ps6599/products_white_paper09186a00800a4409.shtml#wp14009

Actions

This Discussion