[nsp] vlans unreachable

Roger grunky at rockriver.net
Wed Dec 17 18:31:44 EST 2003


I've setup two subinterfaces on two seperate routers.  The etherchannel 
links connecting them to the switch are trunks w/ no restrictions.  
Below I've setup two virtual interfaces on the same subnet and same 
vlan...  The layer 3 info is correct as is the vlan encapsulation type 
and vlan number.

RouterA
interface Port-channel1.201
 encapsulation dot1Q 201
 ip address 192.168.201.1 255.255.255.0

RouterB
interface Port-channel1.201
 encapsulation dot1Q 201
 ip address 192.168.201.2 255.255.255.0

When on each router I can ping its local 192.168.201.x address but not 
the far end address.  No acls are in place that would prevent this.  
Also the arp tables on each router do _not_ show the others 
192.168.201.x address - only its own....

I've tried clearing the arp table and uping/downing each interface on 
both routers - still no connectivity between the two.

Now I can put in a static routes on each router -like so

routerA
ip route 192.168.201.2 255.255.255.255 Port-channel1.1 192.168.0.2
routerB
ip route 192.168.201.1 255.255.255.255 Port-channel1.1 192.168.0.1

And that will give me connectivity but I'm not seeing why this is needed 
as subnet+vlan info is the same..

On the main sub-interface port-channel 1.1

RouterA
interface Port-channel1.1
encapsulation dot1Q 1 native
 ip address 192.168.0.1 255.255.255.0

RouterB
interface Port-channel1.1
encapsulation dot1Q 1 native
 ip address 192.168.0.2 255.255.255.0

The above works fine.  I'm at a loss as to how exactly the 'native' tag 
effects vlans in this situation. 

I feel I should have connectivity in the 192.168.201.0/24 subnet

Suggestions?



More information about the cisco-nsp mailing list