FW: [c-nsp] One BGP-L2VPN question

[Gautam]

Yes it will be present in the NLRI Prefix field and not in MP NLRI as there
is no MP Extensions in L2VPN (assuming it is AToM).


-----Original Message-----
From: Arnab Bakshi [mailto:arnab.bakshi at gmail.com]
Sent: Friday, August 05, 2005 2:12 PM
To: Gautam; cisco-nsp at puck.nether.net
Subject: Re: FW: [c-nsp] One BGP-L2VPN question


   How should the Update message look like,I mean, will the label be
present with the NLRI prefix field in Update Msg rather than sending
it using MP_REACH_NLRI attribute.

On 8/5/05, Gautam <gautam_attravanam at sifycorp.com> wrote:
>
> Dont send label through MP-BGP. It should be under ipv4 address-family.
> -----Original Message-----
> From: Arnab Bakshi [mailto:arnab.bakshi at gmail.com]
> Sent: Friday, August 05, 2005 12:33 PM
> To: Gautam
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: FW: [c-nsp] One BGP-L2VPN question
>
>
> Hi,
>
>   I tried by sending label in MP_REACH_NLRI in BGP but the problem
> still exists and the mpls forwarding  table is still not updated with
> the prefix.
>  the following is the AFI/SAFI value is used :
>
>   AFI = 1 (IPv4 Address)
>   SAFI = 4 (Labelled Unicast).
>
> The ip routing table is updated successfully. The labels sent are proper.
> Is this the correct way or there should be more changes.
>
> Thanks
> Arnab
>
>
> On 8/4/05, Gautam <gautam_attravanam at sifycorp.com> wrote:
> > NO Normal BGP will do as you dont transport any extended communities
(RTs
> > etc). ensure that you use send-label in the BGP and ensure the neighbors
> are
> > reachable through an IGP. This should work.
> >
> > -----Original Message-----
> > From: Arnab Bakshi [mailto:arnab.bakshi at gmail.com]
> > Sent: Thursday, August 04, 2005 9:53 AM
> > To: Gautam; cisco-nsp at puck.nether.net
> > Subject: Re: FW: [c-nsp] One BGP-L2VPN question
> >
> >
> > Hi,
> >
> >    So BGP can be used as the routing protocol between PE-PE ?
> >
> >   Shall I have to use MP-BGP in this case.
> >
> >   One of my PE is Cisco 7206. When I am using core BGP the ip routing
> > table is updated
> > with the route but the mpls forwarding table is not updated and thus
> > the PW is not coming
> > up.
> >
> >   Do I have to perform any configuration on the CISCO or shall I have
> > to use MP-BGP?
> >
> > Thanks
> > Arnab
> >
> > On 8/4/05, Gautam <gautam_attravanam at sifycorp.com> wrote:
> > > Hi
> > >
> > > If you are talking of the protocol between PE-PE, you can use any
> protocol
> > > as long as the PE label is reachable and the end-to-end LSP is up.
There
> > is
> > > no question of PE-CE Routing protocol as the link is a L2 Link. CE-CE
> > > routing protocol can be anything as the L2VPN is a pseudowire. ANy
> issues
> > > Pls let me know
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: cisco-nsp-bounces at puck.nether.net
> > > [mailto:cisco-nsp-bounces at puck.nether.net]On Behalf Of Bruce Pinsky
> > > Sent: Thursday, August 04, 2005 12:28 AM
> > > To: Arnab Bakshi
> > > Cc: cisco-nsp at puck.nether.net
> > > Subject: Re: [c-nsp] One BGP-L2VPN question
> > >
> > >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Arnab Bakshi wrote:
> > > | Hi,
> > > |
> > > |   I have a question regarding the routing protocol to be used in
case
> of
> > > L2VPN.
> > > |
> > > |   Can IP routes be advertised using BGP so that the LFIB is updated
in
> > > | the PE router and thus pseudowire can be established ? Currently I
am
> > > | using OSPF as the routing protocol, but I also want to use BGP as a
> > > | routing protocol.
> > > |
> > > |   If BGP can be used then shall we have to use MP-BGP ? What shall
be
> > > | the AFI/SAFI values in this case?
> > > |
> > >
> > > The routing protocol for what in the L2VPN?
> > >
> > > Where are you using OSPF now?  PE->PE routing, PE->CE routing, ????
> > >
> > > BGP is often used as the PE->CE routing protocol.  In that case, it is
> not
> > > MP-BGP, but simply a regular eBGP session.
> > >
> > > - --
> > > =========
> > > bep
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.0 (MingW32)
> > >
> > > iD8DBQFC8RPSE1XcgMgrtyYRArE/AKDJBibUDpVUGxpLSphoJy6F5F48GwCg/lll
> > > uPLSiMjuT/KjmTgJNFHmbmw=
> > > =rS8D
> > > -----END PGP SIGNATURE-----
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >
> > > ********** DISCLAIMER **********
> > > Information contained and transmitted by this E-MAIL is proprietary to
> > > Sify Limited and is intended for use only by the individual or entity
to
> > > which it is addressed, and may contain information that is privileged,
> > > confidential or exempt from disclosure under applicable law. If this
is
> a
> > > forwarded message, the content of this E-MAIL may not have been sent
> with
> > > the authority of the Company. If you are not the intended recipient,
an
> > > agent of the intended recipient or a  person responsible for
delivering
> > the
> > > information to the named recipient,  you are notified that any use,
> > > distribution, transmission, printing, copying or dissemination of this
> > > information in any way or in any manner is strictly prohibited. If you
> > have
> > > received this communication in error, please delete this mail & notify
> us
> > > immediately at admin at sifycorp.com
> > >
> >
> >
>
>
> --
> Arnab Bakshi
> Software Engineer
> Conformance-ANVL
> CalaKol-IXIA.
> (M) 09830660593
> www.ixiacom.com
>
>


--
Arnab Bakshi
Software Engineer
Conformance-ANVL
CalaKol-IXIA.
(M) 09830660593
www.ixiacom.com