Hi All,
I've recently taken over a network that is in full swing with multiple projects. The network has multiple sites that are connected betwen IPSec VPN's and relatively slow connections between (T1's and bonded T's)
I have a new facility that was handed to me and partially set up, but not in production, it needs to be soon though. This site will eventually have a fiber connection going to it, which is great, but is still not ready. I currently have Internet access to it via a cradlepoint that I was able to obtain and activate.
The big issue is I was not involved in the intial planning. The goal / idea was to have two separate physical LANs for our data LAN and VoIP LAN. The data LAN was already configured at 192.168.4.0/24 and the VoIP at 192.168.5.0/24. Our Voip system is a shortel system that has a communicator application that will run on the desktops, so of course communication between the desktops and the phone server are a requirement. The original installer was going to multi-home the DC and the Shortel server. I squashed the multihomed DC as I know this is not best practice (it was already killing AD replication), and the phone guys squashed the multihomed phone server.
The physical lan's are on separate racks. I have Extreme Networks layer 3 switches for everything.
My router will be a monowall device as it is at all other sites, connecting everything with a site to site VPN.
My data LAN switches are stacked via stacking ports/cables on one rack and my VOIP switches are stacked on the other side. There are no VLAN's created as they are separate.
My question is, what is my best bet (best practice) for getting the two networks to route traffic between each other, but not losing the planned isolation for data and voice traffic on the separate physical networks?
I've not worked inside a L3 switch before, so please be easy on me :) I've done a good bit of reading up on them before asking this but still am weak on some concepts.
Hell of a first time question right?
