in which case route-policies use AND or OR logic?
Am I correct, that route policies use OR logic if the "from" statement is the same(for example only "from route-filter") and use AND logic if different from statements are present(for example "from route-filter" and "from community")? In other words, in this case:
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.10.10.0/19 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.11.11.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 192.168.1.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate then community delete 12345
set groups TEST policy-options policy-statement TEST1 term aggregate then accept
..all 10.10.10.0/19, 10.11.11.0/24 and 192.168.1.0/24 would be accepted? And in this example:
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.10.10.0/19 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.11.11.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 192.168.1.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from community 777
set groups TEST policy-options policy-statement TEST1 term aggregate then community delete 12345
set groups TEST policy-options policy-statement TEST1 term aggregate then accept
..the 10.10.10.0/19, 10.11.11.0/24 and 192.168.1.0/24 will be accepted only if the community for a prefix is 777?
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.10.10.0/19 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.11.11.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 192.168.1.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate then community delete 12345
set groups TEST policy-options policy-statement TEST1 term aggregate then accept
..all 10.10.10.0/19, 10.11.11.0/24 and 192.168.1.0/24 would be accepted? And in this example:
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.10.10.0/19 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 10.11.11.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from route-filter 192.168.1.0/24 exact
set groups TEST policy-options policy-statement TEST1 term aggregate from community 777
set groups TEST policy-options policy-statement TEST1 term aggregate then community delete 12345
set groups TEST policy-options policy-statement TEST1 term aggregate then accept
..the 10.10.10.0/19, 10.11.11.0/24 and 192.168.1.0/24 will be accepted only if the community for a prefix is 777?