Expand all | Collapse all

routing policy

Jump to Best Answer
  • 1.  routing policy

    Posted 07-01-2018 13:06


    I am looking at this policy hierarchy and wondering why the community attribute is not added to the eBGP routes when I do a show advertising routes detail. 

    If there is no bgp match in p1 then why is p0 not evaluated, is this because the default export policy is to re-advertise all active BGP routes to all BGP speakers and therefore p0 is never evaluated ? or am i misunderstanding routing policy evaluation a the fact there is a neighbor policy negates totaly the global policy?


    instance-type vrf;
    vrf-export p0;
    protocol bgp {
     group external-peers {
      type external;  
        export p1;
    #export policy evaluation order: p1->p0

    policy-statement p1 {
        term redistribute-ospf {
            from protocol [ ospf direct ];
            then accept;
    policy-statement p0
    term EXPORT {
        from protocol [ ospf direct bgp ];
        then {
            community add CORE_RT;
    term REJECT_ALL {
        then reject;

  • 2.  RE: routing policy

    Posted 07-01-2018 18:15
    Policy applied to neighbor override the policy applied at global. So in your case after P1, the default export policy will be evaluated by BGP.

  • 3.  RE: routing policy
    Best Answer

    Posted 07-02-2018 22:54



    the vrf-export policy is processed while sending routing updates towards your core network (RR or remote PE router), i.e. those BGP neighbors that are defined in the global routing instance with family inet-vpn unicast, while the standard export policy is evaluated for updates towards your CE router. So, there is no processing order in this case, just two different directions.




  • 4.  RE: routing policy

    Posted 07-15-2018 13:42

    Hi Carsten,

    Sorry for late thank you, as been on holiday..

    I understand thank you for taking time to explain this