Routing between Vlans for internal traffic and over GW for internet (6024)

Hi Daniel,

Thanks for your reply. I have removed the configuration on my switch and want to start over.

Do you have any example of how to enable the Vlan Routing ? Maybe an example config so I can compare things ?

Hi Daniel,

Wasn't it the idea that the 6024 does recognize the Vlan Headers itself and use this to route from vlan to vlan ?

I have indeed read about the static routes, the WRT54G with DDwrt supports Static routes, I'm not sure about vlan routing but because this device is connected using a 100Mbps port against a 1Gbps I would like to avoid any travic between the vlans over this WRT54G.

Do you understand what I mean ?

OK, thanks. I have read on a lot of sites, and also the forum here, that this should be possible on the 6024. I also saw that the router function was not in the Vlan interface as a command.

You would say to add a static route for each vlan for my solution ? If this works, it would be great.

Hi,

Indeed, this document is the way I should do it.

What I wonder is what I shall do with the route and the vlan IP. My Vlan IP's are known and should be the gateway for the subnet as far as I know. The issue is that I get the following error in that case:

console(config)# ip route 172.16.4.0 255.255.255.0 172.16.4.254
Gateway cannot be one of the addresses configured on this device.

The document sets a gateway where the IP, .2 is not known in the config. I have seen this question a lot of times with no clear answer.

What do I need to use as an IP to use my Vlan as GW for my subnet ?

OK, thanks so far, this makes it more clear!

Here is my simple config so far:

console# sh running-config


Router Configuration
-----------------------------

interface port-channel 1
switchport mode general
exit
interface port-channel 2
switchport mode general
exit
interface range ethernet g(1,7)
switchport mode general
exit
vlan database
vlan 4,8,12
exit
interface ethernet g7
switchport general pvid 8
exit
interface port-channel 1
switchport general pvid 12
exit                                        
interface port-channel 2                    
switchport general pvid 12
exit
interface range ethernet g(1,7)
switchport general allowed vlan add 8
exit
interface range port-channel (1-2)
switchport general allowed vlan add 12
exit
interface vlan 4
name MANAGEMENT
exit
interface vlan 8
name HOSTS
exit
interface vlan 12
name STORAGE
exit
interface port-channel 1
switchport general acceptable-frame-type tagged-only
exit
interface port-channel 2
exit
interface ethernet g7
switchport general acceptable-frame-type tagged-only
exit
interface range ethernet g(19-21)
channel-group 1 mode on
exit
interface range ethernet g(22-24)
channel-group 2 mode on
exit
interface vlan 1
ip address 172.16.0.251 255.255.255.0
exit
interface vlan 4
ip address 172.16.4.254 255.255.255.0
exit
interface vlan 8
ip address 172.16.8.254 255.255.255.0
exit
interface vlan 12
ip address 172.16.12.254 255.255.255.0      
exit
username
crypted
snmp-server community Dell_Network_Manager rw view DefaultSuper


OOB host Configuration
-----------------------------

Empty configuration







 
_____________________________
>> Default settings:
>> Default settings:
_____________________________
                                            
>> Router Configuration
-----------------------------
>> Service tag:

>> SW version 2.0.0.19 (date  05-May-2008 time  16:33:30)
 
>> Gigabit Ethernet Ports
=============================
>> no shutdown
>> speed 1000
>> duplex full
>> negotiation
>> flow-control off
>> mdix auto
>> no back-pressure
 
>> interface vlan 1
>> interface port-channel 1 - 7
 
>> no router RIP
 
>> no router OSPF enable                    
 
>> spanning-tree
>> spanning-tree mode STP
 
>> qos basic
 
>> OOB host Configuration
-------------------------
 
>> interface out-of-band-eth
>> no shutdown
>> speed 100
>> duplex full
>> negotiation
>> flow-control off
>> no back-pressure
>> exit

Let's hope I don't need a Vlan router as this would cause some issues with outbound/inbound speed with such a setup that routes storage too.

It's true, this config is not 100% designed, but is more an idea how my previous setup was.

The issue is that the routing between the VLans is not happening also not when ports are connected and the "direct connected" routes are show when I do a "show ip route".

What could be wrong in that case ?

Here an output of my routes:

# show ip route

Maximum Parallel Paths: 4 (4 after reset)

Codes: C - connected, S - static, R - RIP, O - OSPF, E - OSPF external

C  172.16.0.0/24      is directly connected                        vlan 1    

C  172.16.8.0/24      is directly connected                        vlan 8    

C  172.16.12.0/24     is directly connected                        vlan 12  

Hi Daniel, Nice you are helping out here.

This is my connection status at the moment. Because I'm also testing and remote at the moment this is the setup for now, I can change this later on.

# show interfaces status
                                             Flow Link          Back   Mdix
Port     Type         Duplex  Speed Neg      ctrl State       Pressure Mode
........ ............ ......  ..... ........ .... ........... ........ .......
g1       1G-Copper    Full    100   Enabled  Off  Up          Disabled Off    
g2       1G-Copper    Full    1000  Enabled  Off  Up          Disabled On     
g3       1G-Copper    Full    1000  Enabled  Off  Up          Disabled Off    
g4       1G-Copper      --      --     --     --  Down           --     --    
g5       1G-Copper    Full    1000  Enabled  Off  Up          Disabled On     
g6       1G-Copper      --      --     --     --  Down           --     --    
g7       1G-Copper    Full    1000  Enabled  Off  Up          Disabled On     
g8       1G-Copper      --      --     --     --  Down           --     --    
g9       1G-Copper      --      --     --     --  Down           --     --    
g10      1G-Copper      --      --     --     --  Down           --     --    
g11      1G-Copper      --      --     --     --  Down           --     --    
g12      1G-Copper      --      --     --     --  Down           --     --    
g13      1G-Copper      --      --     --     --  Down           --     --    
g14      1G-Copper      --      --     --     --  Down           --     --    
g15      1G-Copper      --      --     --     --  Down           --     --    
g16      1G-Copper      --      --     --     --  Down           --     --    
g17      1G-Combo-C   Full    1000  Enabled  Off  Up          Disabled On     
g18      1G-Combo-C     --      --     --     --  Down           --     --    
g19      1G-Combo-C     --      --     --     --  Down           --     --    
g20      1G-Combo-C     --      --     --     --  Down           --     --    
g21      1G-Combo-C     --      --     --     --  Down           --     --    
g22      1G-Combo-C   Full    1000  Enabled  Off  Up          Disabled On     
g23      1G-Combo-C   Full    1000  Enabled  Off  Up          Disabled Off    
g24      1G-Combo-C   Full    1000  Enabled  Off  Up          Disabled On     

                                          Flow    Link          Back
Ch       Type    Duplex  Speed  Neg      control  State       Pressure
........ ....... ......  .....  ........ .......  ........... ........
ch1      1G        --      --      --       --    Down           --   
ch2      1G      Full    1000   Enabled  Off      Up          Disabled
ch3         --     --      --      --       --    Not Present    --   
ch4         --     --      --      --       --    Not Present    --   
ch5         --     --      --      --       --    Not Present    --   
ch6         --     --      --      --       --    Not Present    --   
ch7         --     --      --      --       --    Not Present    --   

                                              Link
Oob-eth   Type         Duplex  Speed Neg      State
........  ............ ......  ..... ........ ...........
Oob-eth 1 100M-Copper    --      --     --    Down  

Daniel,

Did you already found a workaround or solution for this ?

Thanks!

Mhh, OK but that makes it all traffic go over this router and would need some Laggs to be fast, which is not the idea at all.

I hope we can sort something out...

Is it a Software feature or really a switch feature ?

Hi Daniel,

Thanks, I'm going to try that.

At the moment I have Vlan tagging on ports on, so my ports are General.

Is this needed for the Vlan or not to isolate it at max? I'm investigating this at the moment also because when a ports has a device which is not sending tagged packages, the switch will tag them so the device can function on the Vlan.

I hope I'm right.

Your explanation sounds good indeed.

My idea about the Vlan isolation is to have devices that can communicate using tags from the device or tags from the switch itself.

If a device can tag it's own packages, it's already OK, when another device can't the switch will do this for it.

My question was indeed, what happens with inbound/outbound packages on ports even when they are tagged from the sending device itself.

Hi Daniel,

With the setup, as you have displayed it above but a ping between the vlans is not possible yet.

I can ping another host in a vlan/subnet but not the VlanIP/Gateway from these same hosts.

I'm investigating what could be wrong in the setup, do you have some extra tips there maybe ?

Thanks

OK, this is good, I can ping between Vlans, it's very important that you set the IP of the vlan as GW, if you don't the ping cannot be routed.

So far so good, but what would be the right command to get IP traffic from a several of subnets over the 172.16.0.252 GW to the outside world ?

Also, I can ping between Vlans which is nice, but what if I want to avoid a connection between some Vlans ?