I wouldn't agree that Cisco would recommend RIP as best practice for a PE-CE
routing protocol. Every IGP - RIP, OSPF, EIGRP and ISIS (12.0S is limited)
is VRF aware and is supported as a PE-CE routing protocol in IOS. I don't
know where the original quote was pulled from, but each IGP above can be
used. It's also the reason there are extensions made to BGP to carry the
attributes (via extended communities) from these IGP's across an MPLS cloud
(metrics, route-types, etc.) The decision on which IGP to use will always
vary according to design requirements - like anything else.....
- AB
CCIE #21901
On Wed, Mar 9, 2011 at 10:40 AM, Jeferson Guardia <jefersonf_at_gmail.com>wrote:
> Those are best practices, cisco thinks: the ce side is really simple and
> small, then RIP does the job, it is simple to setup and troubleshoot but at
> the end of the day any igp would accomplish it, is really up to you to
> decide.
>
> Sent using my Iphone
>
> Em 09/03/2011, C s 12:28, "Aaron" <aaron1_at_gvtc.com> escreveu:
>
> > " A service provider edge (PE) router can learn an IP prefix from a
> customer
> > edge (CE) router by static configuration, through a BGP session with the
> CE
> > router, or through the routing information protocol (RIP) exchange with
> the
> > CE router. "
> >
> >
> >
> > Is it just me or have y'all also read statements like this before? It
> seems
> > that I see RIP mentioned a lot when speaking of an IGP route prot that
> can
> > be used from CE to PE...does this mean I can't use eigrp, ospf ?
> >
> >
> >
> > Aaron
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Wed Mar 09 2011 - 10:55:56 ART
This archive was generated by hypermail 2.2.0 : Fri Apr 01 2011 - 06:35:41 ART