On 3/13/2012 4:15 PM, Stefan Fouant wrote: > Yes this is correct and is indeed the default Junos behavior. If you wanted > to receive a looped BGP update, you can define the amount of loops allowed > (.i.e. number of times your own AS appears in the AS Path attribute) by > configuring the 'set routing-options autonomous system <as-num> loops <num>' > command. > > HTHs. > > Stefan Fouant > JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI > Technical Trainer, Juniper Networks > > Follow us on Twitter @JuniperEducate > > Sent from my iPad
You can also allow loops on a per BGP neighbor basis with: neighbor 10.0.0.1 { family inet { unicast { loops 1; } } } -DMM > On Mar 13, 2012, at 4:10 PM, "Mohammad" <masal...@gmail.com> wrote: > >> Hi john; >> >> >> >> As far as I know when an eBGP router receives a route contains its own AS >> in the AS path it consider it as a loop, so for your case the juniper router >> is seeing its own AS (XXXX) in the route's ASPATH received from its eBGP >> neighbor (XXXXX YYYYY I), so the solution I would suggest is to remove AS >> XXXX on the other router before sending it to the juniper router, if XXXX is >> a private AS you can use remove private on the other router; or you can use >> AS override. >> >> Hope it is helpful; >> Mohammad Salbad >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp