MPLS Service

Hi,
I would like to know how everyone does their MPLS design. Ideally, you put all sites on one single MPLS service provider, e.g. ATT, with single access link. Data centers will have two access links for redundancy.
However, what if I want to have two MPLS service providers, put half of the sites on one MPLS cloud and another half on the second MPLS cloud? How would you do the routing between them? ATT stated that they would not exchange routes to another SP. I would like to know if anyone has two MPLS SP and how they do it.
Thanks.

Kevin,
What we do is terminate the one Service Provider on one router, and then terminate the other service provider on another and share routes between the two routers through your own infrastructure.
This isn't the only design but one that we have implemented.

Similar Messages

How to implement redundant with 1 CE router to 2 MPLS service providers

Dear all,
Our head-office are currently have 1 Cisco CPE 3825 router with 2 WAN connections to our branches. We are now using static routing protocol in our network infrastructure, we consider how to implement the redundancy for networks by the redundant circuits connection to 2 MPLS providers, only when the primary connection to the primary MPLS L3 provider fail, the backup link to the second MPLS Layer 2 provider automatically active. Anybody knows where can I find information, tips or examples, how we'd handle the routing for that?
We are now have:
1 G0/1 interface connect to primary MPLS L3 Provider (the 2nd G0/2 interface is a leased-line connection to our partner, and we not consider here)
1 HWIC (layer 2) card, with 4 ports, which has interface F0/2/3 connected to the backup MPLS Layer 2 provider.
Thanks in advance.
PS: Current configuration : 3727 bytes
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname Router
boot-start-marker
boot system flash c3825-entservicesk9-mz.123-11.T7.bin
boot-end-marker
logging buffered 4096 debugging
logging monitor xml
no aaa new-model
ip subnet-zero
ip cef
no ftp-server write-enable
no spanning-tree vlan 4
no spanning-tree vlan 5
interface GigabitEthernet0/1
description connect to VDC MPLS$ETH-WAN$
mtu 1480
ip address 222.x.x.66 255.255.255.252
ip flow ingress
ip flow egress
service-policy output SDM-QoS-Policy-1
ip route-cache flow
duplex auto
speed auto
media-type rj45
fair-queue 64 256 256
no cdp enable
interface FastEthernet0/2/0
switchport access vlan 2
no cdp enable
interface FastEthernet0/2/3
description ToTBToverFPT
switchport access vlan 5
no cdp enable
interface Vlan2
description CONNECT TO MPLS_VDC
ip address 192.168.201.9 255.255.248.0
interface Vlan5
description Connect to HoChiMinhCity
ip address 172.16.1.5 255.255.255.252
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 172.16.244.0 255.255.255.0 222.255.33.65
ip route 192.168.0.0 255.255.248.0 222.255.33.65
ip route 192.168.24.0 255.255.254.0 222.255.33.65
ip route 192.168.30.0 255.255.254.0 222.255.33.65
ip route 192.168.32.0 255.255.254.0 222.255.33.65
ip route 222.x.x.68 255.255.255.252 222.255.33.65
ip route 222.255.33.72 255.255.255.252 222.255.33.65
ip route 222.x.x.196 255.255.255.252 222.255.33.65
ip route 222.x.x.200 255.255.255.252 222.255.33.65
ip http server
ip http authentication local
no ip http secure-server
ip http max-connections 3
control-plane
line con 0
logging synchronous
stopbits 1
line aux 0
stopbits 1
line vty 0 4
password
login
transport input telnet
line vty 5 14
privilege level 15
password
login
transport input telnet
line vty 15
privilege level 15
password
login
transport input telnet
parser view SDM_Monitor
scheduler allocate 20000 1000
end

Hi Mr jianqu,
Because of our customer now has 2 main central offices, and all other sub branches are now connected to each of these main central office via one primary full-meshed MPLS VPN of 1st Service Provider, so If I use the float static routes, and when there is a failure at one link at a CENTRAL CE Router to primary link to primary MPLS VPN Service Provider, but still there is no failure at the other site from a router CE sub branch with the the PE of the primary full-meshed MPLS VPN Layer 3 Service Provider,so It cannot cause a failover to a second redundant link of the 2nd Service Provider?
So with our system, do we only have one solution like this:
-Configure BGP as the routing protocol between the CE and the PE routers.
-Use local preference and Multi Exit Discriminator (MED) when running BGP inside a our customer VPN to select the primary and backup links.
-Use AS-override feature to support overlapping AS numbers between customer sites

OSPF between Multiple MPLS Service Providers

Hi,
One of my customer currently connects to three different MPLS providers. All the SP's PEs are already configured with the customer's subnets, but the CE is configured to point only to one of the PE as the default route. If the link to this SP is down, the customer need to manually change the default route to point to another SP.
How can I enable dynamic routing, e.g. OSPF, to all the of service providers? What is required from the service providers to enable this?
Thanks for all the advice.
rgds,
Arief

A better understanding of the full topology, such as all the branches that this CE is talking to, and via which of the SPs they are reachable via would help.
I do not see much problem, more especiall, if you take the pains to configure the routing protocol on the CE to only advertise the local subnet and not other subnets learnt by it.

SLA monitoring of MPLS service

Hi Guys..we have MPLS links to about 5 offices around the globe, Bandwidth is around 2 mb across all links, managed by a single ISP. Now we have had various outages recently and we do not have transparency of the average bandwidth. The ISP has his own portal but it doesn't work when needed the most. They have an option where we can pay for getting SNMP feeds but there is no provisioning for capturing Netflow. I guess thay use that for their own portal purposes.
The routers at the CPE side (our side), are managed by the ISP.
What tools/applications I can use on my side to maintain visibility over the MPLS links provided to us?

Hi,
You can make use of the "IP SLA" features between your CPE devices. Though CPE's are connected via MPLS VPN network the enterprise network (your network)is actually unaware of MPLS technology and all you need for IP SLA to work is the ip reachability between devices. CPE to CPE "IP SLA" can be configured which will give you lot of informations that can be gathered. It also has MIB and OID values associated with it. So you can use a free network monitoring tool with OID values so that you can even view the pictorial presentation of your network uptime and lot of performance parameters (jitter, packet loss, latency, etc.)
You can get some insight to "IP SLA":
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6602/prod_presentation0900aecd8047bab5.pdf
HTH.. Pls rate if useful..
cheers
Arun Kumar

100 Mbps MPLS but service provider handing of gig fiber?

Our service provider is providing 100 Mbps MPLS service to one of our remote sites that will accept the handoff via a gig fiber connection into our 3845 router using a GLC-SX-MM SMF tranciever. I'm assuming that I will have to shape the ingress traffic to 100 Mbps. Can anybody send me a link on CCO that explains how to do this? And am I correct that I will have to shape the ingress traffic? Thanks, John

Hi,
Even though you have a fiber coming into your remote location your service provider would have rate limited it appropriately in and out from his perspective to 100MB as per the BW sold to you.
So from your question there should be no need to implement any policing in or out on your router towards the service provider.
HTH-Cheers,
Swaroop

FR-MPLS load balancing

Hi All,
i hv 3 Fr circuits and 1 mpls circuits from india to Usa. is it possible that i will go fro load balancing? pls give me the solution
Thanks

Yes it possible depending on your routing protocol being used,
1) With BGP,Static being used on your PE-CE and as well as other FR links you can control the routing, and install four paths towards your other end destinations.
2) If you have OSPF then you will need help form your MPLS service provider to give you intra-area routes of the other side, as over MPLS VPN you will see the other side routes as Inter-Area routes and hence only your FR links would be preferred for load balancing exlcuding the MPLS VPN circuit.
HTH-Cheers,
Swaroop

Integrating IGX with MPLS...

Hi,
We have a network of 10 IGXs running on Leased Lines serving the Voice & Dataconnectivity needs.. Now our Service Provider is offering Managed MPLS services.. Managed in the sense, he provides the Edge Router & asking us to just connect the Ethernet from our Switch to him.. This finds okay for Data.. However we have most of our BW only on Voice, Is there any Option someone can think of Integrating IGX traffic to go via the MPLS network... The Need is how to connect IGXs using ATM Trunks (UXMs) thru the MPLS network. ... Any suggestions Pls.
regards,
KCS Balaji

Balaji,
The URM is essentially an IP blade in the IGX platform. The URM has an atm OC3 interface that would connect to the IGX backplane . For details on using the IGX and URM for MPLS services, please check the following url .
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/igx8400/9_3_30/pg/igxpgrtr.htm
Regards
Shajith

7600 as Backbone router for MPLS core

I have 7600's and 7500's in my backbone and 7200's on the edge. My question is that when I look at the feature navigator the 7600 with Sup 720 is missing a lot of basic features required to be a core router of an MPLS Backbone. Features like Traffic engineering fast reroute, MPLS enabled Netflow are missing on this platform, is this platform not a good candidate to be a Backbone router for a service provider offering MPLS services??? 7500 on the other hand it seems 7500 seems to have support for the MPLS related features.

Not sure what version you where looking at but...
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Sat 10-Sep-05 01:18 by ccai
Image text-base: 0x40101040, data-base: 0x42D60000
ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF, RELEASE SOFTWARE (fc1)
CASAN_Core1 uptime is 1 week, 4 hours, 9 minutes
Time since CASAN_Core1 switched to active is 1 week, 4 hours, 8 minutes
System returned to ROM by power cycle (SP by power on)
System image file is "disk0:s72033-advipservicesk9_wan-mz.122-18.SXF.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco CISCO7609 (R7000) processor (revision 1.1) with 983008K/65536K bytes of memory.
Processor board ID FOX092307Q5
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
1 SIP-200 controller .
1 Virtual Ethernet/IEEE 802.3 interface
74 Gigabit Ethernet/IEEE 802.3 interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
CASAN_Core1#
CASAN_Core1(config)#mpls traffic-eng ?
auto-bw auto-bw parameters
fast-reroute fast-reroute parameters
link-management Link Management configuration
logging Trap logging configuration
path-selection Path Selection Configuration
reoptimize Reoptimization parameters
signalling Traffic Engineering Signalling Parameters
topology Topology Database Configuration
tunnels Traffic Engineering tunnels

Can i access internet, if I am connected to MPLS Network in my Data Center

I am planning a connectivity to MPLS network of a Service Provider. Do I need a separate internet connectivity or the MPLS connection it self will provide me the access to internet.
The main idea is to provide access to applications hosted in Data center to all the remote users who are working using their laptops and wireless broadband.
Kindl suggest.
Thanks for the support, in advance.

I am planning a connectivity to
MPLS network of a Service Provider. Do I need a separate internet
connectivity or the MPLS connection it self will provide me the access
to internet.
The
main idea is to provide access to applications hosted in Data center to
all the remote users who are working using their laptops and wireless
broadband.
Kindl suggest.
Thanks for the support, in advance.
Hi,
MPLS service provider can do the same check out the below link for more information
https://www.cisco.com/en/US/tech/tk436/tk428/technologies_white_paper09186a00801281f1.shtml
Hope to Help !!
Ganesh.H
If helpful do rate the post

MPLS Network for an Enterprise

Hi,
I am desiging an MPLS network for an enterprise customer. He would like to have both L2 and L3 VPNs (EoMPLS and VPLS). Initially I thought of positioning ASR1000 but later I ruled it out as it does not support VPLS. So it comes down to 7600. Then I have seen that we have 67XX, ES20 and SIP400 line cards. So what should be my choice for CE facing and Core facing line cards to run all the MPLS services (including MVPN). The customer needs only 3 ports to the access and 1 port as uplink.
Regards,
Prakash

Hi Prakash,
Definately go for the 7600 ES Line Cards:
http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-570730.html
They look like more than enough to do the job for your requirements.
HTH.
Regards,
Joe.

L3 MPLS-VPN with ATM Interfaces

Hi
I tacked a L3 MPLS-VPN from a MPLS service provider.My VPN have three points.
In first point, I have a PA-A3-OC3 over cisco router 7206. how can I config to place PVC1/2 into VPN?

You need that pvc to be under a separate sub-interface and then you can configure "ip vrf for " under that sub-interface.
Hope this helps,

MPLS backbone to support ipv6

Folks,
We currently have MPLS backbone comprised of about 12 routers in the core. We could like to implement support for IPV6. Has anyone implemented this in their MPLS network yet. I know very few providers have deployed ipv6 support on their MPLS network. Could someone point out areas I should be focussing on to make this happen?
Thanks,
Parwal

I appreciate your response to my questions. I had another question for you. I will surely rate this post.
I have 7600's and 7500's in my backbone and 7200's on the edge. My question is that when look at the feature navigator the 7600 with Sup 720 is missing a of basic features required to be a core router of an MPLS Backbone. Features like Traffic engineering fast reroute, MPLS enabled Netflow and missing for this platform, is this platform not a good candidate to be a Backbone router of a service provider offering MPLS services??? 7500 on the other hand seems to have support for the MPLS related features. Please give me your advice, i would highly appreciate it.

MPLS VPN L2 & L3

Hi guys !!!
How is a MPLS L2 VPN different from a MPLS L3 VPN and in what different scenarios do each of these find application?

Hi,
You can search several things in Google.
The most important part is that in L2 MPLS solution it is like overlay MPLS. The Service Provider need not to to participate in customer routing.
However in the L3 MPLS solution is peer-to-peer VPN. The MPLS Service Provider will participate for CE-PE routing.
L2 MPLS is ideal for Point to Point link required where as L3 is in general any-to-any connectiviy - best for Hub and spoke.
Cheers!
Prince

MPLS Per VRF QOS

Our WAN cloud will be a mesh between 3 campuses. Our provider will provide Layer 2 transport services, 1Gbps, FIFO. At each campus I will be running 2821 for WAN edge.
All services will be converged onto this WAN, Voice, Video, Data.
At each campus runs 3750 or 6513 as Campus Core peering 2821's. Each campus will be running VRF-Lite. My goal is to become the MPLS service provider for the college. The 2821's are the PE devices and the Campus Core's are the CE devices. Example, Voice will have it's own VRF at each respective site, each vrf will learn routes from other voice vrf's from the 2821's. Currently the 2821's peer each other iBGP. I want to be able to allocate portions of bandwidth (1Gb) for each VRF on the WAN and queue the traffic within each VRF.

Hi,
You need to configure normal QoS, remark the triple play traffic (data voice video) in ingress interface on the switch and implement queuing and bandwidth reservation out the egress interface of the router.
Regards,
W.Amer

MPLS Customer router physical interface

My provider wants to sell me MPLS services but I can't seem to get a straight answer regarding what the physical interface on my customer router needs to be. Some personnel tell me it will be a normal ethernet connection, other say it'll be a DS3 or T1 connection depending on the speed.
Please give me some advice on what to expect regarding an MPLS circuit? Or point me to some good documentation to maybe I can communicate better with the service provider.
Thank you.

Hi Tod
Few points from my side for your query
Access Link should be considered based on whether we are going for MPLS L3 VPN or MPLS L2 VPN Soilution
MPLS L3 VPN from my understanding is independent of Access Media but the Access Media will definitely put different hardware requirements for your Customer Edge Router
The Access Link Type and Bandwidth would vary depending upon the BW requirements for the network. The T1/T3 or a Subrate T3 Access Links would be a choice when we have BW requirements in that range(<45 Megs)
Using FE as an Acces link would require SP to provide Colocation Services or rather go for spanning a Fiber out from their Colo and deploying Optical Mux at Customer Premises and again suitable for BW requirements more than 45 Megs
MPLS L2 VPN
Ethernet is the choice for taking MPLS L2 VPN Services to connect your different branches in a point-to-multipoint fashion using VPLS at SP end.
You can go through the Cisco Doc - "Layer 3 MPLS VPN Enterprise Consumer Guide" which should help you gain more insight for choosing the PE-CE Routing Protocol and other points to consider for an MPLS L3 VPN Service.
Thats from my understanding. Hope you will get more good advises on this.
Regards
Vaibhava Varma

MPLS Service

Similar Messages

Maybe you are looking for