cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1139
Views
0
Helpful
17
Replies

2801 with 4-esw. Can't get Switched VLAN to go over T1

aeubanks
Level 1
Level 1

Here is the run down. 2801 w/4esw module

I have two Vlans (Data and VoIP)

Below is a snippet of I have.

interface Vlan64

ip address 172.29.64.x 255.255.255.192

ip helper-address 172.29.x.x

!

interface Vlan200

ip address 172.29.64.y 255.255.255.192

ip helper-address 172.29.x.x

interface FastEthernet0/1/0

switchport access vlan 64

switchport trunk native vlan 64

switchport mode trunk

switchport voice vlan 200

switchport priority extend trust

!

interface FastEthernet0/1/1

switchport access vlan 64

switchport trunk native vlan 64

switchport mode trunk

switchport voice vlan 200

switchport priority extend trust

!

interface FastEthernet0/1/2

switchport access vlan 64

switchport trunk native vlan 64

switchport mode trunk

switchport voice vlan 200

switchport priority extend trust

interface Serial0/3/0

ip address 172.29.254.z 255.255.255.252

service-policy output QoS-Policy-T1

I have added the Vlans to VLAN Database. but I can't route the traffic over the Serial 0/3/0

The only way I can get this to work is to have a cable going from the router interface fa0/0 to the switch interface 0/1/3 and configure those ports with the following.

interface FastEthernet0/1/3

switchport trunk allowed vlan 1,64,200,1002-1005

switchport mode trunk

interface FastEthernet0/0

no ip address

duplex auto

speed auto

!

interface FastEthernet0/0.64

encapsulation dot1Q 64

!

interface FastEthernet0/0.200

encapsulation dot1Q 200

How can I avoid using the cable.

17 Replies 17

Edison Ortiz
Hall of Fame
Hall of Fame

Alan,

Please post the output from typing

show ip route

from this router and from the router located in the other side of the T1.

You need to be able to advertise these subnets (Subnet 172.29.64.x and 172.29.64.y) with some kind of dynamic routing protocol or static routes.

I don't see that as part of the config that you've posted nor it was mentioned in the post.

HTH,

__

Edison.

Routing doesn't appear to be the issue. I have all the routes. my issue is more along the lines that I can't pass the VLANs over the CSU/DSU from the 4esw card without setting up sub-interfaces on the router port to reflect the vlan interface I have created on the 4-esw module.

Im running the below routing protocol

router ospf 1

redistribute connected

network 172.29.0.0 0.0.255.255 area 0

my sh ip route snippet

C 172.29.64.0/26 is directly connected, Vlan64

I can't pass the VLANs over the CSU/DSU

You mean, you want Layer2 information from those Vlans from site-to-site? You don't want those Vlans routed?

If so, you need to configure bridging in the router but I highly suggest NOT to do that. Extending your Layer2 topology over slow and unreliable WAN links is not the best design.

__

Edison.

Let me just re-phrase this a bit.

All I want to accomplish is to avoid using a switch at this remote site. That's why I picked up a 4-esw to eliminate that need. However, when I create the

Interface VLAN xx.

I can't get any of the traffic from that VLAN to go anywhere except on that router. Even with a route in the table. my default route is 0.0.0.0 0.0.0.0 serial 0/3/0

That's why I created the Sub-interfaces on fa 0/0 and then plugged a cable from fa0/0 to fa 0/3/0 in order to get everthing to work. but this can't be correct.

Hope that helps clear things up a bit.

That's the reason I asked to see the route table from both devices.

You can have a default route on this router and any networks on this router will use it but you also need to inform the remote routers about the networks being held on this router. In other words, you need to address the return traffic.

Without seeing your route table, I'm not sure what the problem is...

You also have to make sure the default gateway on the devices sitting on each Vlan is pointing to the IP address on their respective Vlan.

HTH,

__

Edison.

her is the ip route from both devices. I only included the routes in question.

ROUTER A:

C 172.29.64.0/26 is directly connected, Vlan64

C 172.29.64.64/26 is directly connected, Vlan200

ROUTER B:

O 172.29.64.64/26 [110/66] via 172.29.254.58, 2d23h, Serial2/6:0

O 172.29.64.0/26 [110/66] via 172.29.254.58, 2d23h, Serial2/6:0

So, you are able to ping the subnets from the remote location via the T1, aren't you?

__

Edison.

Correct. I can ping the VLAN Interfaces from the remote network, but cannot ping any nodes on the VLANs located on the router.

What are the nodes' default gateway?

It should be the IP address listed in the router's Vlan interface.

__

Edison.

The Gateway is set to the VLAN interface ip address.

Can you ping between Vlans ?

In other words, can workstations on Vlan 64 ping workstations on Vlan 200?

Can workstations on Vlan 64 ping the IP address listed under interface Vlan 200 on the router?

__

Edison.

Yes. They can.

Then, inter-vlan routing is working on this router/switch.

Can you post a traceroute from the remote router to a node located in Vlan 64 and Vlan 200?

__

Edison.

I have just erased started config and re-applied all exsisting settings and everything seems to be working now. Thanks for all your help.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco