Hi, I have a problem with routing across VLANs.
I have two data vlans set up on the above boxes: 192.168.6.0/24 & 192.168.3.0/24.
There is a UC520 box with its default ip in the 6.0 range, and all of the CE520s (three of them) also have an ip in the 6.0 range. All of the equipment are connected by the trunk ports.
The 6.0 network's default route is the UC520 and all clients can route correctly and more importantly see the CME/CUE web page at 10.1.10.1.
The 3.0 network's default route is an SBS server which is connected to one of the CE520 switches. All clients can route between each other and the SBS server no problem. However none of the clients including the SBS Server can see 10.1.10.1.
What I have done to fix this is set up one of the ports in the UC520 as being assigned to the 3.0 VLAN and connected one of the two switches with the 3.0 clients to that port. This hasn't worked.
I can't really experiment as it is a live network.
Any suggestions as to what is wrong?
If I understand what your set up is, it sounds like you are routing 192.168.3.0/24 client traffic to the SBS server which does not have a route to the 10.1.10.0/24 network on the UC500. Typically, client traffic would be routed to the UC500 and coincidently is how the 192.168.6.0/24 is routing as you expected.
There are a couple of ways to solve this problem.
1) Add a VLAN3 interface on the UC500 with an IP address that is in the 192.168.3.0/24 subnet.
1a) Configure a DHCP server on the UC500 for this subnet and have clients get an address with a default gateway address of the UC500 IP address assigned to VLAN3.
1b) Add a default route in the SBS server to also point to the UC500 IP address assigned to VLAN3
This will allow full routing to all subnets the UC500 has in its routing table including the internet.
2) If you only want the 192.168.3.0/24 subnet to be able to reach the SBS server and the 10.1.10.1 subnet and prefer to use the SBS as your DHCP server and router for the 192.168.3.0/24 subnet, then you will need to add a static route in the SBS server to point to a UC500 interface.
So you'd repeat step 1) from above and then add the static route in the SBS server pointing at that newly configured UC500 IP address.
If you still have trouble getting to the 10.1.10.1 address, make sure you have a trunk set up between the UC500 and CE520 and VLAN3 is permitted through the trunk.
Hint: Using a tracert command on the Windows PCs can help you see each hop as it traverses the network to the destination. If it stops at the SBS server IP address then you know that's as far as the packet makes it and indicates that the SBS does not know how to route the packet forward. Typically the last IP address is the device that needs the routing table updated to pass the packet on to its destination.
Hope this helps,