Re: MPLS L3 VPN query

Hi Paul

I cant get ur point regarding Passive Interface in the main process. What
do u mean exactly?

On Thu, Jan 19, 2012 at 10:58 PM, Paul Negron <negron.paul_at_gmail.com> wrote:

>
>
> The thing under the main process that can kill you is the
> "passive-interface" command. This was unfortunately inherited under the
> address-family.
> --
> Paul Negron
> CCIE# 14856 CCSI# 22752
> Senior Technical Instructor
>
>
>
> > From: Aaron <aaron1_at_gvtc.com>
> > Date: Thu, 19 Jan 2012 11:18:03 -0600
> > To: 'Paul Negron' <negron.paul_at_gmail.com>, 'Routing Freak'
> > <routingfreak_at_gmail.com>, 'Cisco certification' <ccielab_at_groupstudy.com>
> > Subject: RE: MPLS L3 VPN query
> >
> > I also recall something about the autonomous-system command under the
> eigrp
> > process under the vrf specific af having some significance too with vrf
> > eigrp via mpls core
> >
> > Aaron
> >
> >
> > -----Original Message-----
> > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Paul
> > Negron
> > Sent: Thursday, January 19, 2012 10:55 AM
> > To: Routing Freak; Cisco certification
> > Subject: Re: MPLS L3 VPN query
> >
> > BGP also uses a similar method of keeping track of the OSPF info
> (Domain-ID,
> > Cost using the MED attribute, type of route). Look at the extended
> > information for OSPF like you did EIGRP.
> >
> > ISIS should not be used to the edge and I know it used to leak routes in
> an
> > efficient way in the VPN in times past. Very inconsistent and sloppy. I
> know
> > they have cleaned some things up in code but I have not implemented ISIS
> to
> > the edge in any real scenario to verify.
> >
> > Paul
> > --
> > Paul Negron
> > CCIE# 14856 CCSI# 22752
> > Senior Technical Instructor
> >
> >
> >
> >> From: Routing Freak <routingfreak_at_gmail.com>
> >> Reply-To: Routing Freak <routingfreak_at_gmail.com>
> >> Date: Thu, 19 Jan 2012 21:22:42 +0530
> >> To: Cisco certification <ccielab_at_groupstudy.com>
> >> Subject: MPLS L3 VPN query
> >>
> >> Hi all,
> >>
> >> I have a weird doubt when redistributing EIGRP or OSPF or ISIS into
> MPBGP
> >> update to another PE and again MPBGP is redistributed into EIGRP or OSPF
> > or
> >> ISIS.
> >> How does BGP carry EIGRP info or OSPF info or ISIS info such as ( Area
> for
> >> OSPF, internal route or external route what is the area type or lsa
> type)
> >> or for EIGRP ( AS number , Delay, BW). I know for EIGRP , there is
> > extended
> >> bgp communites attributes to carry for EIGRP .. ( which is
> >> 8801,8802,8803,8804,8805)
> >>
> >> But wat about OSPF or ISIS into BGP ( how does BGP carry OSPF or ISIS
> >> routes) ? Is there any extended community attributes for this?
> >>
> >> And also how does OSPF or ISIS carry BGP updates from one end to another
> >> end ? Is there any extended TLVS for it or else is there any other
> >> extended headers for OSPF or ISIS to carry BGP information.
> >>
> >>
> >> 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 Fri Jan 20 2012 - 00:14:14 ART