[j-nsp] question regarding l3vpn

[Nabarun Baks]

 Hi Robert,

Thanks very much !

Also can you say whether I need to order the BGP Attributes. Currently
I am sending Extended Community attribute placed after MP_REACH_NLRI
attribute (as per BGP rule), the router accepts the route but ethereal
fails to show the extended community attribute and gives a hex dump.

Also when examining packets from the router I saw that extended
community attribute is placed before the MP_REACH_NLRI attribute.

Is there any requirement to place Extended Community attribute before
MP_REACH_NLRI?

Any suggestions will be grateful !

Regards
Naba

On 10/18/05, Robert Raszuk <raszuk at cisco.com> wrote:
>
> Nabarun,
>
> Nope unless you have some use for std communities.
>
> Cheers,
> R.
>
> > hi All,
> >
> > Can anybody tell me whether we need to send community attribute
> > containing route targets in the bgp update message when BGP/MPLS VPN is
> > used.
> >
> > We can send extended community attribute and put the route target
> > extended community. But do we also need to send the community attribute.
> >
> > Any help will be grateful
> >
> > Regards
> > naba
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>