Routing

Hello commuinities.

I am trying to leak some desired prefixes from inet.0 to specific instance (let's say instance_A), so I can announce those prefixes to the peers who lives under instance A, here's the configuration.

First of all, I've configured the instance-export on the global routing-options:

show configuration routing-options instance-export 
instance-export Leaking_From_inet.0_to_instance_A.inet.0;

Also, I've applied the instance-import under the instance_A (the target instance):

show configuration routing-instances instance_A routing-options instance-import 
instance-import Leaking_From_inet.0_to_Instance_A.inet.0;

And here is what exactly the policy-statement is:

show configuration policy-options policy-statement Leaking_From_inet.0_to_Instance_A.inet.0

term BGP_Leaking {
    from {
        route-filter 10.0.0.0/24 exact;
        route-filter 10.0.1.0/24 exact;
    }
    then accept;
}
term Default_Reject {
    then reject;
}

I have confirmed both 10.0.0.0/24 and 10.0.1.0/24 are BGP route and remains active in the inet.0, but neither 10.0.0.0/24 or 10.0.1.0/24 are seen in the instance_A.inet.0.


Any help is appreciated. 

Update: I solved this issue by simply adding the "from instance master" in the policy-statement, and I found I don't even need the instance-export to make it. work. Here's what I currently have:

Configuration for pulling the route from inet.0:

show configuration routing-instances instance_A routing-options instance-import 
instance-import Leaking_From_inet.0_to_Instance_A.inet.0;

The policy itself:

show configuration policy-options policy-statement Leaking_From_inet.0_to_Instance_A.inet.0

term BGP_Leaking {
    from {

        from instance master; /* <---- what I have added*/
        route-filter 10.0.0.0/24 exact;
        route-filter 10.0.1.0/24 exact;
    }
    then accept;
}
term Default_Reject {
    then reject;
}

I am not sure that why a change of condition can make such massive different but I am happy with that.