Re: IP SLA and ROUTE-MAP

Alcides Miguel · ‎04-02-2011

Hello!

i need help configuring a route-map to forward traffic to another ISP, i have 3 LINK's in my router 2 of theme are tracked with ip sla for failover porpuse... but i need also to forward email traffic to the 2 line, the 1 line for web and the 3 line i want to use for internal guest web access... failover is working as spected... didin't try yet use the second line for email traffic...

please se config bellow:

ip sla 1

icmp-echo 8.8.8.8 source-interface Dialer0

timeout 500

threshold 150

frequency 3

ip sla schedule 1 life forever start-time now

ip sla 2

icmp-echo 208.67.222.222 source-interface FastEthernet1

timeout 500

threshold 150

frequency 3

ip sla schedule 2 life forever start-time now

ip sla 3

icmp-echo 4.2.2.2 source-interface Vlan31

timeout 1000

threshold 500

frequency 5

ip sla schedule 3 life forever start-time now

!

track 1 rtr 1 reachability

delay down 15 up 10

!

track 2 rtr 2 reachability

delay down 15 up 10

!

track 3 rtr 3 reachability

delay down 15 up 10

!

interface Vlan27

description *** VLAN_VST_RT ***

ip address 172.16.27.1 255.255.255.252

ip nat inside

ip virtual-reassembly

ip policy route-map VISITORS_POLICY_ROUTE

!

interface Dialer0

ip address negotiated

ip access-group ACL-INFRASTRUCTURE-IN in

ip verify unicast reverse-path

no ip redirects

no ip unreachables

no ip proxy-arp

ip nbar protocol-discovery

ip flow ingress

ip nat outside

ip inspect sec_inspect out

ip virtual-reassembly

encapsulation ppp

dialer pool 1

dialer-group 1

ppp authentication chap callin

ppp chap hostname cuca.bgi

ppp chap password 7 040A59555B741A

!

ip route 0.0.0.0 0.0.0.0 66.110.117.33 track 2

ip route 0.0.0.0 0.0.0.0 64.30.154.81 10 track 3

ip route 4.2.2.2 255.255.255.255 64.30.154.81 permanent

ip route 8.8.8.8 255.255.255.255 196.46.76.1 permanent

ip route 10.10.0.0 255.255.254.0 10.10.50.254

ip route 10.10.12.0 255.255.255.0 10.10.50.254

ip route 208.67.222.222 255.255.255.255 66.110.117.33 permanent

!

ip nat inside source route-map NAT-DIALER0 interface Dialer0 overload

!

ip access-list standard VISITORS_ACCESS

remark --- Access List to forward VISITORS traffic to SNET Line

permit 172.16.27.0 0.0.0.3

!

ip access-list extended NAT-ACL

permit ip 172.16.14.0 0.0.0.3 any

permit ip 172.16.60.0 0.0.0.3 any

permit ip 172.16.26.0 0.0.0.3 any

permit ip 172.16.27.0 0.0.0.3 any

!

route-map VISITORS_POLICY_ROUTE permit 10

match ip address VISITORS_ACCESS

set ip next-hop 196.46.76.1

!

route-map NAT-DIALER0 permit 10

match ip address NAT-ACL

match interface Dialer0

!

route-map NAT-FASTETHERNET1 permit 10

match ip address NAT-ACL

match interface FastEthernet1

!

route-map NAT-VLAN31 permit 10

match ip address NAT-ACL

match interface Vlan31

!

David Salazar · ‎04-02-2011

Hi, Alcides.

Is the route-map doing the job for the Guests access to Web Access?

Is the answer is yes.

You only need to create a route-map that match the email traffic from Vlan of LAN Users and set the ip next-hop to the 2 link.

Example:

!

ip access-list ext EMAIL_TRAFFIC

permit tcp any any eq 25

!

route-map INTERNAL_USERS_EMAIL permit 10

match ip address EMAIL_TRAFFIC

set ip next-hop Y.Y.Y.Y (IP of 2 link next hop)

!

interface VLAN YY

description *** VLAN_INSIDE_USERS ***

ip address .Z.Z.Z.Z W.W.W.W

ip nat inside

ip virtual-reassembly

ip policy route-map INTERNAL_USERS_EMAIL

hope that help you.

DS

Alcides Miguel · ‎04-03-2011

Hi David,

thanks for your quickly response... this is the big deal! the first question is where my problem reside for now... so the answer is no.

David Salazar · ‎04-03-2011

Hi, Alcides.

Was you used the debug ip policy command? If not, can you use it?

The following link is so useful:

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009481d.shtml (Undestanding Policy Routing)

can you show me the output of show route-map command?

Can you show me the output of show ip access-list VISITORS_ACCESS?

Is posible to change the standard access-list to a extend access-list more specify:

ip access-list standard VISITORS_ACCESS
remark --- Access List to forward VISITORS traffic to SNET Line
permit 172.16.27.0 0.0.0.3
!

to

ip access-list extended VISITORS_ACCESS
remark --- Access List to forward VISITORS traffic to SNET Line
permit tcp 172.16.27.0 0.0.0.3 0.0.0.0 0.0.0.0 eq 80 443
!

A question if you are modified the next-hop to all traffic, who resolve the DNS request? are you try to access a web site using the ip address directly?

I hope help you.

Alcides Miguel · ‎04-04-2011

Hi, David

A question if you are modified the next-hop to all traffic, who resolve the DNS request? are you try to access a web site using the ip address directly?

R: i want to all traffic from this network(VISITORS) get routed to Dailer0, all traffic since dns to http

thks for your attention

output below

CUCALDA_N1_RTBorder#show route-map

route-map VISITORS_POLICY_ROUTE, permit, sequence 10

Match clauses:

ip address (access-lists): VISITORS_ACCESS

Set clauses:

ip next-hop verify-availability 196.46.76.1 10 track 1 [up]

Policy routing matches: 6413 packets, 547372 bytes

route-map NAT-DIALER0, permit, sequence 10

Match clauses:

ip address (access-lists): NAT-ACL

interface Dialer0

Set clauses:

Policy routing matches: 0 packets, 0 bytes

route-map NAT-FASTETHERNET1, permit, sequence 10

Match clauses:

ip address (access-lists): NAT-ACL

interface FastEthernet1

Set clauses:

Policy routing matches: 0 packets, 0 bytes

route-map NAT-VLAN31, permit, sequence 10

Match clauses:

ip address (access-lists): NAT-ACL

interface Vlan31

Set clauses:

Policy routing matches: 0 packets, 0 bytes

CUCALDA_N1_RTBorder#

CUCALDA_N1_RTBorder#show ip access-list VISITORS_ACCESS

Standard IP access list VISITORS_ACCESS

10 permit 172.16.27.0, wildcard bits 0.0.0.3 (18136 matches)

CUCALDA_N1_RTBorder#show ip access-list VISITORS_ACCESS

Standard IP access list VISITORS_ACCESS

10 permit 172.16.27.0, wildcard bits 0.0.0.3 (18394 matches)

CUCALDA_N1_RTBorder#debug ip policy

Policy routing debugging is on

CUCALDA_N1_RTBorder#

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, FIB policy match

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, FIB policy match

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, policy match

*Apr 4 11:40:43.310 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 65, policy routed

*Apr 4 11:40:43.310 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, policy match

*Apr 4 11:40:43.310 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:43.310 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 65, policy routed

*Apr 4 11:40:43.310 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:43.514 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, FIB policy match

*Apr 4 11:40:43.514 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:43.514 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, policy match

*Apr 4 11:40:43.514 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:43.514 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 65, policy routed

*Apr 4 11:40:43.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:43.514 GMT: %FW-6-SESS_AUDIT_TRAIL_START: Start udp session: initiator (172.16.27.2:53581) -- responder (208.67.220.220:53)

*Apr 4 11:40:44.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, FIB policy match

*Apr 4 11:40:44.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:44.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, policy match

*Apr 4 11:40:44.510 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:44.514 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 65, policy routed

*Apr 4 11:40:44.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:44.514 GMT: %FW-6-SESS_AUDIT_TRAIL_START: Start udp session: initiator (172.16.27.2:53581) -- responder (8.8.4.4:53)

CUCALDA_N1_RTBorder#

*Apr 4 11:40:45.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, FIB policy match

*Apr 4 11:40:45.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:45.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, policy match

*Apr 4 11:40:45.510 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:45.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 65, policy routed

*Apr 4 11:40:45.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:47.334 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:61211) sent 135 bytes -- responder (8.8.4.4:53) sent 0 bytes

*Apr 4 11:40:47.334 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:61211) sent 180 bytes -- responder (208.67.220.220:53) sent 0 bytes

*Apr 4 11:40:47.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, FIB policy match

*Apr 4 11:40:47.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:47.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, FIB policy match

*Apr 4 11:40:47.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:47.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, policy match

*Apr 4 11:40:47.514 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:47.514 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 65, policy routed

CUCALDA_N1_RTBorder#

*Apr 4 11:40:47.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:47.514 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, policy match

*Apr 4 11:40:47.514 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:47.514 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 65, policy routed

*Apr 4 11:40:47.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:50.406 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:65444) sent 148 bytes -- responder (208.67.220.220:53) sent 0 bytes

*Apr 4 11:40:50.406 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:65444) sent 111 bytes -- responder (8.8.4.4:53) sent 0 bytes

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, FIB policy match

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, FIB policy match

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 65, FIB policy routed

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 65, policy match

*Apr 4 11:40:51.510 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:51.510 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 65, policy routed

*Apr 4 11:40:51.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:51.514 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 65, policy match

*Apr 4 11:40:51.514 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:51.514 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 65, policy routed

*Apr 4 11:40:51.514 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:51.686 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, FIB policy match

*Apr 4 11:40:51.686 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:51.686 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, policy match

*Apr 4 11:40:51.686 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:51.686 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 68, policy routed

*Apr 4 11:40:51.686 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:51.686 GMT: %FW-6-SESS_AUDIT_TRAIL_START: Start udp session: initiator (172.16.27.2:63528) -- responder (208.67.220.220:53)

*Apr 4 11:40:52.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, FIB policy match

*Apr 4 11:40:52.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:52.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, policy match

*Apr 4 11:40:52.682 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:52.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 68, policy routed

*Apr 4 11:40:52.682 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:52.682 GMT: %FW-6-SESS_AUDIT_TRAIL_START: Start udp session: initiator (172.16.27.2:63528) -- responder (8.8.4.4:53)

CUCALDA_N1_RTBorder#

*Apr 4 11:40:53.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, FIB policy match

*Apr 4 11:40:53.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:53.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, policy match

*Apr 4 11:40:53.682 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:53.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 68, policy routed

*Apr 4 11:40:53.682 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, FIB policy match

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, FIB policy match

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, policy match

*Apr 4 11:40:55.682 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:55.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 68, policy routed

CUCALDA_N1_RTBorder#

*Apr 4 11:40:55.682 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:55.686 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, policy match

*Apr 4 11:40:55.686 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:55.686 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 68, policy routed

*Apr 4 11:40:55.686 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:40:56.038 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:137) sent 150 bytes -- responder (172.16.27.3:137) sent 0 bytes

CUCALDA_N1_RTBorder#

*Apr 4 11:40:58.598 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:53581) sent 148 bytes -- responder (208.67.220.220:53) sent 0 bytes

*Apr 4 11:40:58.598 GMT: %FW-6-SESS_AUDIT_TRAIL: Stop udp session: initiator (172.16.27.2:53581) sent 111 bytes -- responder (8.8.4.4:53) sent 0 bytes

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, FIB policy match

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, FIB policy match

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 68, FIB policy routed

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 68, policy match

*Apr 4 11:40:59.682 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 68, policy routed

CUCALDA_N1_RTBorder#

*Apr 4 11:40:59.682 GMT: IP: Vlan27 to Dialer0 196.46.76.1

*Apr 4 11:40:59.682 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 68, policy match

*Apr 4 11:40:59.686 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:40:59.686 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 68, policy routed

*Apr 4 11:40:59.686 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:41:02.074 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 73, FIB policy match

*Apr 4 11:41:02.078 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, g=196.46.76.1, len 73, FIB policy routed

*Apr 4 11:41:02.078 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220, len 73, policy match

*Apr 4 11:41:02.078 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:41:02.078 GMT: IP: s=172.16.27.2 (Vlan27), d=208.67.220.220 (Dialer0), len 73, policy routed

*Apr 4 11:41:02.078 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

*Apr 4 11:41:02.078 GMT: %FW-6-SESS_AUDIT_TRAIL_START: Start udp session: initiator (172.16.27.2:51885) -- responder (208.67.220.220:53)

*Apr 4 11:41:03.074 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 73, FIB policy match

*Apr 4 11:41:03.074 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, g=196.46.76.1, len 73, FIB policy routed

*Apr 4 11:41:03.074 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4, len 73, policy match

*Apr 4 11:41:03.074 GMT: IP: route map VISITORS_POLICY_ROUTE, item 10, permit

*Apr 4 11:41:03.074 GMT: IP: s=172.16.27.2 (Vlan27), d=8.8.4.4 (Dialer0), len 73, policy routed

*Apr 4 11:41:03.074 GMT: IP: Vlan27 to Dialer0 196.46.76.1

CUCALDA_N1_RTBorder#

Alcides Miguel · ‎04-05-2011

Thanks you all for your attention finally i found the solution using vrf feature