Hi Dan. The default action depends on whether it's an import or export policy, and on what protocol is being used. For all import policies, the default is to 'accept', so the 'then accept' isn't really needed, but personally I like to see it for my own sanity. See the following link for a list of protocols and their defaults if you're interested in a particular combination:
http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-policy/id-10157558.html#id-10157558 David On 04/01/2008, Dan Farrell <[EMAIL PROTECTED]> wrote: > As a newcomer to JUNOS I'm stumbling a little on the policy > configurations (in particular for prepending.) This really seems to > spell it out better than the Juniper reference. > > One question- The 'then accept;' statement after term 2 ... is it > necessary? If so, what is it doing that wouldn't happen if it was gone? > > > Thanks, > > danno > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Umar Ahmed > Sent: Thursday, January 03, 2008 10:06 AM > To: Erol KAHRAMAN; juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] bgp path > > An example : > > policy-statement prepend { > term 1 { > from protocol aggregate; > then { > as-path-prepend "1234 1234 1234"; > accept; > } > } > term 2 { > then reject; > } > then accept; > } > > In this case im matching an aggregate route, then apply this policy > outbound on your peer : > > bgp { > log-updown; > group Peer-1 { > type external; > export prepend; > neighbor x.x.x.x > peer-as 123456; > } > } > > > Any questions, give me a shout. > > regards, > > > > Umar Ahmed > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Erol KAHRAMAN > Sent: 03 January 2008 13:41 > To: juniper-nsp@puck.nether.net > Subject: [j-nsp] bgp path > > Hi guys, > > How can i show one path more far with bgp. I need to repead my AS in my > advertisement for this. > > > -- > Erol KAHRAMAN > System Network Administrator > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > ********************************************************************** > Any opinions expressed in the e-mail are those of the individual and not > necessarily the company. This e-mail and any files transmitted with it > are confidential and solely for the use of the intended recipient. If > you are not the intended recipient or the person responsible for > delivering it to the intended recipient, be advised that you have > received this e-mail in error and that any dissemination, distribution, > copying or use is strictly prohibited. > > If you have received this e-mail in error, or if you are concerned with > the content of this e-mail please e-mail to: > [EMAIL PROTECTED] > > The contents of an attachment to this e-mail may contain software > viruses which could damage your own computer system. Whilst the sender > has taken every reasonable precaution to minimise this risk, we can not > accept liability for any damage which you sustain as a result of > software viruses. You should carry out your own virus checks before > opening this e-mail or any attachments to this e-mail. > > This e-mail was sent from Vanco UK Limited a company registered in > England under number 2296733 and whose registered office is Units 1&2, > Great West Plaza, Riverbank Way, Brentford, TW8 9RE, UK > > Please consider the environment before printing this e-mail. > ********************************************************************** > > _______________________________________________ > 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
