Solved

metro-e , e-line, point-to-point networking

Posted on 2012-12-27
9
302 Views
Last Modified: 2013-01-07
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
0
Comment
Question by:rpliner
  • 5
  • 4
9 Comments
 
LVL 11

Assisted Solution

by:rharland2009
rharland2009 earned 500 total points
ID: 38724704
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.
0
 
LVL 7

Author Comment

by:rpliner
ID: 38724754
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
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 38724762
Sure thing.
0
 
LVL 7

Author Comment

by:rpliner
ID: 38740771
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
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 38740812
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.
0
 
LVL 7

Author Comment

by:rpliner
ID: 38740928
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
0
 
LVL 11

Accepted Solution

by:
rharland2009 earned 500 total points
ID: 38740950
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.
0
 
LVL 7

Author Comment

by:rpliner
ID: 38741099
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
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 38741661
Re: DHCP - yeah, I'd flip that to your Windows box. It's a better plan long-term.
0

Join & Write a Comment

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now