using win2003 routing with a 2950

[umbletech]

newbie question.

Setting up a home lab. Got a 2950 on the latest image. Have a win2003 rras VM doing routing. Two clients on different subnets can ping each other so seems to be working. Now I'd like to setup VLANs on the 2950 and have RRAS route across them. Is it just a matter of making the switche's default gateway the primary NIC on the RRAS VM?

Anyone have a setup link?

 

[vipergg]

No the switches default gateway command is just to manage the switch and has no function in any kind of routing decisions as this is a layer 2 switch only. Do you have 2 nics in the server and this is how it is routing ? The only way this could work is if your nics in your server have trunking ability in which case you could pass multiple vlans down the same link .

 

[umbletech]

Sidestepping the issue of vmware support for 802.1q for the moment I assume that the physical nic in the vmware host server will need to support 802.1q? Something like an intel pro 1000

 

[zinkann]

the NIC's will need to support 802.1q trunking

 

[burtsbees]

Two clients on different subnets can ping each other so seems to be working."
They're not connected to the same switch, right?

Burt

 

[burtsbees]

You can set up vlans in the 2950 and route between them with the server, as long as the server can route between its own 2 interfaces. The server (or any router with multiple interfaces) will treat the 2 VLANs as separate subnets, and therefore do not have to trunk. Trunking is only necessary on one link that carries more that one subnet/vlan. If you create more vlans than there are interfaces, then that's where you get into "router-on-a-stick" and trunking configurations. With 2 NICs, you can only create 2 vlans. Creating the switchports in vlan access mode causes the packets to be assumed to belong to those vlans.

Burt