Thanks for the reply. My idea was to let the PC6248 handle the vlans because it routes between vlans faster than the firewall would (ASA 5520).

How do I add static routes to the 172.16.33.0 network on each vlan?

Hi Daniel

I know how to enter a static route. I just didn't understand your statement and was hoping you could clarify it.

"In order to get all VLANs on the 6248 to traverse over the connection to the other devices, you will need to either continue adding static routes for each VLAN."

Does this mean I can enter specific routes to specific vlan interfaces? If so how do I do that?

Thanks

Either you are not understanding my question or I am not understanding you..

The problem is that the switch only forward the traffic for the clients that resides on the vlan that is physically connected to the next hop router. In my case that is vlan 5

E.g.  a client PC from vlan 4 trying to reach a host on 172.16.33.0 with ping command gets "destination host unreacheable" as an answer from the PC6248

So my conclusion is that the switch do NOT look in it's routing table when traffic coming from vlans other than vlan 5 which is physically connected to the router. It just drops the packets.

Or am I wrong here?

Thanks for your clear answer.

Could you enlight me on how to enter static routes for each of the VLANs?

Thank you

I added the static routes and it didn't make any difference. Funny thing is that when entering show ip route command doesn't show those static routes. When issuing show running-config though it shows the static routes but nether less it doesn't make any difference.

#sh ip route

S      0.0.0.0/0 [1/0] via 192.168.2.1,   vlan 2

S      172.16.33.0/24 [1/0] via 172.16.22.1,   vlan 5

C      172.16.22.0/24 [0/1] directly connected,   vlan 5

C      192.168.3.0/24 [0/1] directly connected,   vlan 3

C      192.168.4.0/24 [0/1] directly connected,   vlan 4

C      192.168.2.0/24 [0/1] directly connected,   vlan 2

#sh ru

ip route 0.0.0.0 0.0.0.0 192.168.2.1

ip route 172.16.33.0 255.255.255.0 172.16.22.1

ip route 192.168.2.0 255.255.255.0 172.16.22.1

ip route 192.168.3.0 255.255.255.0 172.16.22.1

ip route 192.168.4.0 255.255.255.0 172.16.22.1

Just to clarify for others, I marked DELL-Daniel Co's post as an answer because his question "On the router with the 172 network, does it have the VLANs in it's database?" woke me up realizing the router also needed a route back to the vlans even though he was referring to vlan databases.

Thanks again