From: Kalsaria Prakash [mailto:[email protected]] 
Sent: Saturday, May 01, 2010 5:21 PM
To: '[email protected]'
Subject: Re: [OSL | CCIE_SP] CCIE_SP Digest, Vol 37, Issue 9 TE problemen

 

Hello, RICK wood 

Thanks for going through problem 

 

My tunnels are working its UP UP 

Well I think while pasting a config into mail I would have done that mistake
Explicit path name on both side are properly configured 

I think issue is related to PBR is that fine,,, ?????  do  I have to config
anything  on R7 for PBR 

 

 

Here are the debug Outputs 

 

ON R8   is  a 7200 router and using IOS (C7200-K91P-M), Version 12.2(25)S14

 

 

Policy Routing(20), rtype 0, forus FALSE, sendself FALSE, mtu 0

03:38:41: IP: s=172.8.0.88 (local), d=172.8.0.22 (FastEthernet0/0.78), len
236, sending

03:38:41: IP: s=172.8.0.88 (local), d=172.8.0.22 (FastEthernet0/0.78), len
236, sending full packet

R8(config-subif)#, Policy Routing(20), rtype 0, forus FALSE, sendself FALSE,
mtu 0, Policy Routing(20), rtype 0, forus FALSE, sendself FALSE, mtu 0,
Policy Routing(20), rtype 0, forus FALSE, sendself FALSE, mtu 0

R8(config-subif)#, Policy Routing(20), rtype 0, forus FALSE, sendself FALSE,
mtu 0, Policy Routing(20), rtype 0, forus FALSE, sendself FALSE, mtu 0

 

 on R2   ----- - - -  2600 Software (C2691-ADVENTERPRISEK9-M), Version
12.4(11)T1, 

*Mar  1 03:40:11.847: IP-CEF: process switch tunnel:
Tunnel28->FastEthernet0/0.27

 

*Mar  1 03:40:26.223: IP: s=172.8.0.22 (local), d=172.8.0.88
(FastEthernet0/0.27), already routed

*Mar  1 03:40:26.223: IP: s=172.8.0.22 (local), d=172.8.0.88
(FastEthernet0/0.27), len 224, sending

 

*Mar  1 03:40:53.535: IP: s=172.8.0.22 (local), d=172.8.0.88
(FastEthernet0/0.27), already routed

*Mar  1 03:40:53.535: IP: s=172.8.0.22 (local), d=172.8.0.88
(FastEthernet0/0.27), len 224, sending

 

 

I didn't understand this debug output please help me out 

Thanks :) 

 

_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to