intervlan routing

[mellert]

I am replacing a 4006 switch in the Admin building of a manufacturing facility with a L3 4507 switch. I have configured multiple vlan interfaces and the routing seems to be working correctly in all of my test scenarios except one.

Hanging off a second 4006 in the operations building in a third location is an old 2500 router with a linksys unmanaged switch in front of and behind it. This router routes one of the vlans I have created and general network traffic hangs off the unmanage switch in front of the router. FYI - intervlan routing from the 4006 switch works fine.

Since the unmanaged switch does not trunk, is there any way I can configure multiple vlan access on the 4006 to the Linksys switch?

[ankurbhasin]

Hi Friend,

According to me if linksys switch is unmanaged you cannot create anythin on linksys so it is just acting as a extension to your network and giving you port density.

I do not think it should restrict anything so you can you please update where do you want to pass vlan information to and you can configure trunk between 4006 and the other end device which is connecte to linksys switch.

Regards,

Ankur

[Richard Burts]

Don

If I have understood your post correctly it boils down to: you are installing a 4507 switch which is configured for multiple VLANs. The 4507 switch will connect to an unmanaged Linksys switch which does not trunk. The Linksys switch connects to a 2500 router (which does not trunk either). You wonder if you can get multiple VLANs from the 4507 to the Linksys.

I believe that part of the answer is obvious and part may require some additional information. If the Linksys does not trunk then you can not send multiple VLANs over a single connection. There may be an option (note that I did not say it was an attractive option) to send a single VLAN over one connection, establish a second connection from the 4507 to the Linksys and send a second VLAN to the Linksys over the second connection. The think that I do not understand yet is whether the Linksys is capable of defining VLANs. The fact that it does not trunk leads me to suspect that it does not have capability to separate VLANs internally. If this is the case then you would not be able to send multiple VLANs to it.

HTH

Rick