I have an application, and I am wondering if I can or need to route VLANS.
****
I have a Main Site and a Remote Site. I have CISCO 2620 Routers at both ends of a Point to Point T1 link. Both routers's Fa0 ports are plugged into CISCO 2950 switches.
****
I have a group of devices at either end that need to communicate to each other with high priority and need to be isolated. Each group of devices at either end have their own subnet, and their own VLAN. The subnet routing is handled by secondary IP addresses on each router's Fa/0 port.
****
The switch ports going to the routers are programed as VLAN trunks, and the switch ports for the End Devices are programmed as VLAN2 only, static access (?).
****
Question 1) I believe that I need to have 801.2q available on the routers to allow the traffic to remain 'isolated' on the appropriate VLAN when it gets to the far end. Do I? If so, do I need to build subinterfaces (assign IP addresses, apply 802.1q encapsulation, and add an appropriate VLAN IDs) on the Fa/0 ports on each router? Do I then make the Gateway of these devices be the far end's subinterface? Or, do I need to have seperate physical ports on the router?
****
Question 2) Eventually, On one end, the devices will be set up to send frames either "untagged" or tagged with VLAN2. I understand that the cooresponding switch ports will then need to be changed to trunk ports with the native VLAN being 1. What would happen if a device is programmed to send out information with VLAN2 tags, but the port is already set to VLAN2 static access? Is it double-tagged? :)
*****
When I leave everything in VLAN 1, I can ping across from end-to-end no problem. So my overall routing seems to be okey.