Internet Sharing on MPLS Network with L2 Switch

Pain Area and things for consideration:

  • How can IT Team provide Internet Connection to all the users in every location?
  • By taking Internet connection at all the location will it be a cost effective solution?
  • Can Service Provider offer Centralized Internet which will be shared to all the locations?
  • Will it be workable if customer have Layer2 switch at HUB location?
  • Will it increase Latency by taking Centralized Internet?
  • Is there any Security concerns?
  • What type of QOS is required for their application?
  • How Internet Traffic flows from spoke locations?

- Solution Proposed

While running MPLS VPN most of the customer required Internet access for their users from that particular location. To do this IT Team takes separate link from the ISP and terminates into their LAN to fulfill the Internet requirement and this current scenario gives better uptime in terms of MPLS and Internet services but it also increase COST component which is unavoidable. To have separate Internet link for every location, it is better to have single Internet link with the bigger bandwidth from any ISP and share this through your existing MPLS Cloud to all the respective locations. This Scenario also called Centralized Internet over MPLS Cloud. Internet Sharing can be work on any of the Topology (HUB and Spoke or Mesh).It gives you better control in terms of Internet Policy which would be applicable for all the users through that Centralized Internet. But in this scenario MPLS Router and Internet Router/Firewall have to be Back-to-Back connected and MPLS Router will be further connected to Layer 2 Switch because in PC we can only configure Single IP as Default Gateway which would be MPLS Router LAN Interface. Packet FlowHUB location users can use Internet directly as Internet Leased Line already installed at that location and if request generates from Spoke location for accessing Server, MPLS HUB Router will forward the traffic to Layer2 Switch and if request is for accessing any Website in that case MPLS HUB location Router will direct the traffic towards Internet Router/Firewall.


HUB and Spoke with Internet


Technical Arrangement:

  1. Customer can terminate Internet Bandwidth on any Router or Firewall.
  2. Topology would be either HUB and Spoke or MESH.
  3. MPLS Router and Internet Router have to be back-to-back connected.
  4. Services Provider will advertise the Default route into Customer’s MPLS VRF and do the reverse Routing in HUB location.
  5. Default Gateway IP Address will be MPLS LAN Interface.
  6. Configure Default Route pointing towards Internet CE Router.
  7. CE Router should have 2 Layer3 port + 1 Layer2 port.
  8. CE-PE recommendation is static or BGP Routing protocol.

Akshay Sharma

AKshay has a rich experience of 10+ years in data and telecom domains. He is working as a solution architect in a reputed Telecom in India from the last 5 yrs and has diversified experience in providing robust network solution to SMB and enterprise segment. His core expertise is in DSL broadband/IP/MPLS/Routing and switching with hands on multiple telecom equipment’s and had done multiple certifications into his long career.

You may also like...

2 Responses

  1. RamiroYMaura says:

    Things i don’t understood is the simple truth is how you’re now not really much more neatly-preferred than you might be
    now. You’re very intelligent. You understand thus considerably when it comes to this matter, made me inside my view believe it from numerous various
    angles. Its like people aren’t interested unless it’s something to
    do with Girl gaga! Your very own stuffs great.
    All the time maintain it up!

    My web site: RamiroYMaura

  1. September 7, 2014

    internet switch

    How are you? I am a great friend from Internet Sharing on MPLS Network with L2 Switch – IP-MPLS.COM

Leave a Reply

Your email address will not be published. Required fields are marked *

one × two =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>