Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.
COURSE of the MONTH
13 days, 6 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
metro-e , e-line, point-to-point networking
Posted on 2012-12-27
Greetings,
I am setting up a 50 Mb point-to-point circuit (TW calls it a e-line or metro-e) between the office and the datacenter. I currently have a VPN between the two. I also currently have two distinct LAN IP networks (192.168.25 at the office and 192.168.35 at the datacenter).
Do I have to keep two separate IP networks with a point-to-point (metro-e) or can I extend the .25 LAN network from the office to the datacenter since it is a point-to-point?
thanks
I am setting up a 50 Mb point-to-point circuit (TW calls it a e-line or metro-e) between the office and the datacenter. I currently have a VPN between the two. I also currently have two distinct LAN IP networks (192.168.25 at the office and 192.168.35 at the datacenter).
Do I have to keep two separate IP networks with a point-to-point (metro-e) or can I extend the .25 LAN network from the office to the datacenter since it is a point-to-point?
thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5-
4
9 Comments
As long as this is a true Layer 2 offering, then the pipe is unaware of the layer 3 traffic inside it - and you can extend your LAN using the circuit.
For example, how are you communicating over that pipe right now? What's doing your Layer 3 switching/routing to get from one segment to another?
Best to check with your provider. Metro-e comes in a few flavors.
For example, how are you communicating over that pipe right now? What's doing your Layer 3 switching/routing to get from one segment to another?
Best to check with your provider. Metro-e comes in a few flavors.
Active 6 days ago
thanks rharland2009. I have not set it up yet. I have a sonicwall NSA 240 at the office and a NSA 220 at the datacenter. they will handle the traffic between the two. I will check with TW.
thanks again
thanks again
Active 6 days ago
I am still waiting to hear back from them. However, if it is possible, is it recommended or is there a better way to do it?
thanks again
thanks again
Not sure what you mean.
As far as a point-to-point, you don't really need devices on either end - because the two ends are only connected to stuff that you control! Now, I'm sure you could nail up a VPN if you want between the two sites, but there's just not much reason - except to protect your two locations from Internet-based attacks or malicious traffic - coming from the far end of the point-to-point - that might impact your LANs.
Since it also sounds like you have two /24 networks, you *could* extend both locations to use the .25 network without a problem. 512 possible hosts is not too bad for a single segment from a broadcast chattiness perspective, as long as your switching is good at either location.
Just my opinion.
As far as a point-to-point, you don't really need devices on either end - because the two ends are only connected to stuff that you control! Now, I'm sure you could nail up a VPN if you want between the two sites, but there's just not much reason - except to protect your two locations from Internet-based attacks or malicious traffic - coming from the far end of the point-to-point - that might impact your LANs.
Since it also sounds like you have two /24 networks, you *could* extend both locations to use the .25 network without a problem. 512 possible hosts is not too bad for a single segment from a broadcast chattiness perspective, as long as your switching is good at either location.
Just my opinion.
Active 6 days ago
I meant is it better, or recommended, to segment into two IP networks and set up a new site Active Directory (already done as currently we have a VPN between the two), or is just one IP network acceptable, supported, best practice, etc.?
If I did go with one IP network for both the office and datacenter, how is DHCP and DNS affected? I already have a DC with DNS (it is a global catalog too) in the datacenter. I am putting our new exchange 2010 box as well as our terminal server at the datacenter as soon as our new storage comes in and is configured. one /24 network will fit us but since two are already configured, should we just leave as is?
This is what TW said:
The service is layer 2 to us and you can use layer 3 without issues. You do not need to segment the network if you do not want to do so.
Thanks again for your help
If I did go with one IP network for both the office and datacenter, how is DHCP and DNS affected? I already have a DC with DNS (it is a global catalog too) in the datacenter. I am putting our new exchange 2010 box as well as our terminal server at the datacenter as soon as our new storage comes in and is configured. one /24 network will fit us but since two are already configured, should we just leave as is?
This is what TW said:
The service is layer 2 to us and you can use layer 3 without issues. You do not need to segment the network if you do not want to do so.
Thanks again for your help
That extra info helps.
If you've already got everything in place, then leave it.
If you went with one network, you'd be changing a couple of things re DHCP/DNS...you'd have one server for DHCP at one location or the other taking care of both locations. You'd have multiple DNS servers - maybe one at each location. You'd spend more time putting the networks together than it's worth. You've already got two segmented, well-designed LANs - who already talk successfully with each other! String up that point-to-point and leave the rest alone...it's a good thing.
If you've already got everything in place, then leave it.
If you went with one network, you'd be changing a couple of things re DHCP/DNS...you'd have one server for DHCP at one location or the other taking care of both locations. You'd have multiple DNS servers - maybe one at each location. You'd spend more time putting the networks together than it's worth. You've already got two segmented, well-designed LANs - who already talk successfully with each other! String up that point-to-point and leave the rest alone...it's a good thing.
Active 6 days ago
OK. thanks for the help. last quick question:
currently our sonicwall is the DHCP server at the datacenter. should I move that to a windows DHCP server since we'll be putting our exchange and terminal servers there permanently?
thanks again
here is another question I just posted in case you have any insight into this issue
http://www.experts-exchange.com/Networking/Misc/Q_27983903.html
currently our sonicwall is the DHCP server at the datacenter. should I move that to a windows DHCP server since we'll be putting our exchange and terminal servers there permanently?
thanks again
here is another question I just posted in case you have any insight into this issue
http://www.experts-exchange.com/Networking/Misc/Q_27983903.html
Featured Post
Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
What if you have to shut down the entire Citrix infrastructure for hardware maintenance, software upgrades or "the unknown"? I developed this plan for "the unknown" and hope that it helps you as well. This article explains how to properly shut down …
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses
Course of the Month13 days, 6 hours left to enroll
777 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.