Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I need help moving over to using our layer 3 switch as the inter vlan routing device rather than our cisco router. I've mostly got it working but I've got stuck near the end and need some advice (I think I just need a bit of education on the subject really). Cur

I have a Dell PowerConnect 7048 connecting to a Cisco 1841 router. I've got a few key excerpts from the configs to provide the key information. On the powerconnect I have the following:

ip routing
ip default-gateway 172.31.14.1
ip route 0.0.0.0 0.0.0.0 172.31.14.1 253
!
interface vlan 1
ip address 172.31.14.254 255.255.255.0
exit
interface vlan 2
ip address 172.31.19.254 255.255.255.0
exit
interface vlan 4
ip address 172.31.16.254 255.255.255.0
!
interface Gi1/0/1
description 'Link to L7Router01'
switchport mode trunk
switchport trunk allowed vlan except 3,7-4093
exit
!

and on the Cisco the following:

 interface FastEthernet0/0
  ip address 172.31.14.1 255.255.255.0
  ip nat inside
  ip virtual-reassembly
 !
 interface FastEthernet0/0.2
  description Accounts VLAN
  encapsulation dot1Q 2
  ip address 172.31.19.1 255.255.255.0
  ip nat inside
  ip virtual-reassembly
 !
 interface FastEthernet0/0.4
  description Voice VLAN
  encapsulation dot1Q 4
  ip address 172.31.16.1 255.255.255.0
  ip nat inside
  ip virtual-reassembly
 !

So what I'm doing is moving clients over so that their default gateway is a 172.31.x.254 address rather than a 172.31.x.1 address. This works great for inter-vlan routing, I have no issues with this. The switch can also access the router no worries, and users on the 172.31.14.0/24 network can access all interfaces and sub-interfaces on the router, including 172.31.14.1. They can also access all of the interfaces that the router connects off to, no worries there.

The problem I have is that users on the 172.31.16.0/24 and 172.31.19.0/24 subnets cannot access either 172.31.14.1 or any of the subnets the router connects to. They can, however, connect to BOTH of the sub interfaces on the router from either subnet.

What am I missing here? Why can't the vlans connect to the non-sub interface on the router? Are tagged packets being sent to this interface?

share|improve this question
    
What are the port configurations to which your clients are connected? Are the ports tagged, untagged or trunked (client does the encapsulation/tagging and can access multiple vlans)? I need this data because VLAN 1 is the default VLAN. But other VLANs require tagging from the client end or forced tagging from the switch's end. –  nearora Jun 12 '12 at 4:00
    
The client ports are access ports on whatever vlan they are assigned to. The clients do no tagging themselves, the switch takes care of that. –  Yoshiwaan Jun 12 '12 at 5:17
    
Can you print the routing table on the L3 switch and the router and post it here? –  nearora Jun 12 '12 at 5:29
    
Switch: Default Gateway is 172.31.14.1 S 0.0.0.0/0 [253/0] via 172.31.14.1, Vl1 S 10.200.200.0/24 [1/0] via 172.31.14.1, Vl1 S 10.200.201.0/24 [1/0] via 172.31.14.1, Vl1 S 10.210.200.0/24 [1/0] via 172.31.14.1, Vl1 S 10.210.201.0/24 [1/0] via 172.31.14.1, Vl1 C 172.31.14.0/24 [0/1] directly connected, Vl1 C 172.31.16.0/24 [0/1] directly connected, Vl4 C 172.31.18.0/24 [0/1] directly connected, Vl6 C 172.31.19.0/24 [0/1] directly connected, Vl2 –  Yoshiwaan Jun 12 '12 at 6:01
    
Router (Trimmed): Gateway of last resort is 10.255.255.1 to network 0.0.0.0 C 172.31.19.0 is directly connected, FastEthernet0/0.2 C 172.31.18.0 is directly connected, FastEthernet0/0.6 C 172.31.17.0 is directly connected, FastEthernet0/0.5 C 172.31.16.0 is directly connected, FastEthernet0/0.4 C 172.31.21.0 is directly connected, FastEthernet0/0.7 S 172.31.20.0 [1/0] via 172.31.14.248 C 172.31.14.0 is directly connected, FastEthernet0/0 –  Yoshiwaan Jun 12 '12 at 6:11
show 11 more comments

2 Answers

If you'd like the switch to be performing inter-VLAN routing then why are you still running an 802.1q trunk back to the router? You need an L3 link between the router and the switch, the default route on the switch to the router via that gateway and then return routes on the router pointing back to the switch's L3 interface.

share|improve this answer
    
I think the OP is migrating machines from having the router as the gateway to the L3 switch as the gateway. What you say seems to be the OP's ultimate goal. However, from purely a functional perspective, I don't see anything wrong with the OP having the router and the L3 switch on all the same VLANs. –  nearora Jun 12 '12 at 4:32
    
Correct Nearora, In addition, according to this guide: cisco.com/en/US/tech/tk389/tk815/… (step-by-step instructions, step 6, the note) it seems to indicate that if you connect to the router via a vlan it should work, at least for a cisco device (but why would the Dell differ on that?). –  Yoshiwaan Jun 12 '12 at 5:20
add comment
up vote 0 down vote accepted

As I stated in the comment above I didn't find a proper solution for this, the only option was to disable the additional virtual interfaces on the router so there was only 1 path.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.