[j-nsp] 4 byte as mixed with 2 byte recieving problem

[moki]

Thanks Jeff
Actually it make sense , 
I will apply the policy at my export policy to the world /

Cheers   

-----Original Message-----
From: Jeff Wheeler [mailto:jsw at inconcepts.biz] 
Sent: Tuesday, December 11, 2012 1:42 PM
To: moki
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] 4 byte as mixed with 2 byte recieving problem

On Tue, Dec 11, 2012 at 6:04 AM, moki <vomoki at gmail.com> wrote:
>         The customer have 4byte as and requested we add prepend (with our
> as) to

Loop detection is preventing your RR from accepting the path.  Do you
actually need the prepend behavior to influence best-path selection
inside of your network, or does the customer really want you to
prepend your AS when you EXPORT the route to your EBGP NEIGHBORS?

I think what you need is a mechanism for prepending upon export.
Normally this is implemented by assigning a BGP community and doing
the prepend in your export policy.

-- 
Jeff S Wheeler <jsw at inconcepts.biz>
Sr Network Operator  /  Innovative Network Concepts