The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: Fwd: IP VPN over MPLS backbone
Roger Reg static routing as an option for CE-PE , AFAIK this will not be applicable in this setup as dynamic routing is needed to find out when to initiate the ISDN backup to a specific remote site(s) . Aleksander AFAIK For the CE-PE : For L2 : U could use whatever available from the provider (PPP, FR .etc) . If U will be using FR , U will notice that U will have a single DLCI (and may be 2nd one for mang) . this in comparison of the current setup where it exist a DLCI per remote site . (PIPE mode versus Hose Mode ) For L3 : U need to use a L3 between the CE-PE . Depend on the provider it could be : RIP , eBGP or OSPF . So the CE config and it's complexity depend on the L3 routing protocol used . Personaly i believe that eBGP is the simple one to use and it provide clean demarcation point between the customer (CE) and the provider (PE) . In this case the CE will be geting all the remote sites routes (Say Net1 to Netn) from the PE through eBGP , U need to config the ISDN to be initiated to a remote Site "n" if NETn is not present in the routing table . U could config the static route pointing to the ISDN interface as floating (distance higher than eBGP) so it is only used if their is no eBGP route (this has the advantage to test ISDN -bring it up-without disturbing the traffic ie: traffic will still continue to flow through the PE ) . The above assume that U are handling the CE config , if it is the resp of the provider so nothing need to be done from the customer side . Brgds >From: Roger Clark Williams <rogerw@nordlink.com> >To: MPLS-ops Mailing List <mpls-ops@mplsrc.com> >Subject: Fwd: [MPLS-OPS]: IP VPN over MPLS backbone >Date: Wed, 19 Nov 2003 14:08:24 -0500 > >Aleksander, one reason you may not find much written about the CE >configuration is that in an MPLS VPN there is none, beyond what is required >in normal routing. The PEs holds all the configurations required to host >your VPNs. The PEs holds route tables (VRFs) that are particular to your >service. The role of the MPLS VPN is, in effect, to forward the traffic >coming into the PE over a certain interface across the network to the >outgoing interface on another PE (or PEs). The CEs knows nothing of all >this and are set up approximately like any other router. The only >differences may be the PE-CE routing protocols; the provider may insist on >a limited choice, but certainly static routing should be one. > >It is probable that your present FR link will stay in place as the >connecting link to the PE, but there are other options. > >Things get a bit more complicated if you want access to the internet as >well as VPN service, but again, this is a configuration issue at the >provider PE end, not normally at the CE end. Even when multi-homed, nothing >much changes on the CE. > >The ISDN could stay in place as a backup/failover system if necessary. At >least in the US ISDN is a time-dependant service; if not used, the charges >are lower. > >Roger Williams > >>X-MindSpring-Loop: rogerw@nordlink.com >>Resent-Date: Wed, 19 Nov 2003 05:04:59 -0500 >>X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to >>mpls-ops-request@mplsrc.com using -f >>From: "Aleksandar Dzambaski" <dzambo@mt.net.mk> >>To: <mpls-ops@mplsrc.com> >>Date: Wed, 19 Nov 2003 10:51:11 +0100 >>X-Mailer: Microsoft Outlook Express 6.00.2800.1158 >>X-OriginalArrivalTime: 19 Nov 2003 09:51:11.0606 (UTC) >>FILETIME=[A9E84960:01C3AE82] >>Subject: [MPLS-OPS]: IP VPN over MPLS backbone >>Resent-From: mpls-ops@mplsrc.com >>X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/6503 >>X-Loop: mpls-ops@mplsrc.com >>Resent-Sender: mpls-ops-request@mplsrc.com >>Resent-Bcc: >> >>Hi, >> >>I currently have a Frame Relay network with central site and 22 remote >>locations, coupled with ISDN backup. The system works fine, but now our >>telecom provider has new service. >> >> >> >>They have MPLS backbone, and they are offering IP VPN connections as a >>replacement for our current network. >> >> >> >>I spent several days in research for this new opportunity and I see that >>obviously this is a better offer. We will start a test period in which we >>are supposed to connect several locations just to compare with the Frame >>Relay. >> >> >> >>Now here are the questions: >> >>1. I have problem with understanding the configuration of the customer >>(mine) router. I have read many papers about configuring the PE and P >>routers in the MPLS backbone, and the PE interface to the CE router, but I >>haven't found a paper describing the configuration of the CE interface to >>the PE router, nor I have found an example of it. Can someone point me or >>explain the configuration of the IP VPN interface. Are there any examples >>of >>it or comparison with the Frame Relay configuration? >> >> >> >>2. The current situation is with ISDN backup lines which are configured >>with >>static routes and Frame Relay end-to-end keepalive parameters. This >>eliminates using dynamic routing protocols (ex. RIP, OSPF...). Regarding >>the >>previous question and this statement, are there any possibilities of >>keeping >>the static routing or should we definitely turn to a dynamic routing >>protocol. >> >> >> >>Best regards, >> >>Aleksandar >> >> >> >>------- >>The MPLS-OPS Mailing List >>Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > >------- >The MPLS-OPS Mailing List >Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml |
|