We have a Cisco 6500 at our main site that is running CatOS and has a MSFC2 L3 module. The 6500 is the VTP server for all local 3750 switches which are vtp clients. On the local 3750 switches the iphones use vlan 20 and data is vlan 10. This all works fine for our main campus where all switches are connected back to the 6500 via 1gbps fiber.
We are now adding a remote site which will be connected via a 10mbps fiber circuit (provided by a telco). We only have a 3750 at the new site, the current configuration (implemented last week) is the L3 routing is carried out on the 6500, i.e the WAN link is currently part of the remote sites subnet and broadcast domain - which is less than ideal!
What is the recommended way to properly configure both switches to enable us to vlan the data and voice for remote sites. At present the new site has both voice and data on the same vlan (40) the gateway address for this vlan is the interface on the 6500 (which is conneted to the NTE of the telco), the interface on the 6500 is also in vlan 40 making this port part of the remote sites broadcast domain.
So what is the best way to configure the remote site to allow vlans, or should we not really be doing this configuration.
Any thoughts would be apprecaited.
Jon, thanks for the info
1 and 2 fine no probs follow that!
3 what is an SVI how is it different?
4 and 5 fine
no probs with the commands, this is what i thought it would be, this assigns vlan 20 to this port on the 6500 and on the 3750 i also assign vlan 20 to the gigabit int connected to the fibre NTE?
So it doesnt matter that the 3750 is not getting the vlan info from VTP server then? i tried assigning a port to vlan 20, but not assigning the remote site 3750 gigabit interface to vlan 20, this appeared to generate a native vlan mismatch error?
So as for the 3750 at the remote site, i can understand that the int connected to the NTE needs to be on the same subnet and also vlan, do i then just create vlans for voice and data standalone on that switch and then the default-gateway for clients then becomes the LAN interface on that switch. the switch in turn will have a default gateway passing traffic over the 192.168.5.2 network.
Is this how it would work? is the 3750 switch effectivly becoming a router now?
3 - SVI = Switched Virtual Interface ie.
ip address x.x.x.x
So when i say create a vlan in point 2) i mean create a vlan in the vlan database ie. a vlan at L2. You then need to configure a L3 interface for that vlan ie. an SVI.
No it doesn't matter that the 3750 is not getting vlan info with VTP because the vlan info on the 6500 is irrelevant to the 3750. As you correctly say the 3750 would now be acting as a L3 device so the vlans in the branch site would be created on the 3750 and routed on the 3750. The only common vlan to both sites would be vlan 20 from my example.
And yes again you are correct when you say the clients in the local vlans on the 3750 will have their default-gateways set to their respective L3 vlan interface IP addresses on the 3750.
As for the native vlan mismatch easiest thing to do is configure the 3750 as the 2nd option i suggested. Just to be clear though the link between the 6500 and the 3750 should not be a trunk link, it should be an access link with both ports at either end allocated to vlan 20. So on 3750 -
1) create vlan 20
2) create an SVI for vlan 20
3) allocate the port on the 3750 to be in vlan 20.
Again, the only port on the 3750 in vlan 20 should be the port connecting to the 6500.
And don't forget to enable ip routing on the 3750 ie.
3750(config)# ip routing