Hello 

We are trying to migrate an  existing configuration form an older 6500  with 
SUB 720 and  12.2(17d)SXB1 to  VSS system. There are 10 VRF used. Some subnets 
are static routed between some VRFs (Inter-VRF Routing) like:  ip route vrf AAA 
172.24.192.0 255.255.248.0 Vlan400 172.24.193.1 

On the older 6500 this configuration is running fine since years. But on the 
new system it works not, I cannot ping the SVI in different VRFs and also not 
from any host in  vlan 100 to any  host in  vlan 400 . I s this behavior  
documented? 

 If I try  "VRF SVI to VRF SVI"  ping i get a traceback: 

------------------------
95: src=172.24.193.1, dst=192.168.0.252, hl=20, tl=100, prot=1, sport=0, dport=0
96: in=Vlan100, nexthop=192.168.0.252, out=Vlan100
97: options=none -Process= "IP Input", ipl= 0, pid= 319
98: -Traceback= 409F35A0 409F3858 409F58C0 409F6174 409F3DB4 409E44DC 409E4948 
409E3784 409E3960 409E3A28 409E3D14 41394B94 41394B80
--------------------------------
Host to host ping:  CEF debug says :

Jun  6 15:01:32 10.1.1.1 544: *Jun  6 12:57:32.711: CEF-Drop: Packet from 
192.168.0.1 (Vl100) to 172.24.193.10, Neighbor resolution req


Configuration section
----------------------
ip vrf BBB
rd 401:401
!
ip vrf AAA
rd 100:100
!

vlan 100
name AAA
!
vlan 400
name BBB
! 

interface Vlan100
description AAA Inside LAN Cat6509
ip vrf forwarding AAA
ip address 192.168.0.252 255.255.255.0
no ip redirects
!

interface Vlan400
description BBB Inside LAN
ip vrf forwarding BBB
ip address 192.168.143.210 255.255.255.252 secondary
ip address 172.24.193.1 255.255.248.0
no ip redirects
!
...

ip route vrf AAA 172.24.192.0 255.255.248.0 Vlan400 172.24.193.1
ip route vrf BBB 192.168.0.0 255.255.255.0 Vlan100 192.168.0.252 

-----------------------------------------------------------------------


Thanks for any hint

Gregor



_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to