5.0: Granular Routing policy. "match-all" tag behaves the same with or without selection
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Committed
|
High
|
Manoj | |||
Trunk |
Fix Committed
|
High
|
Manoj |
Bug Description
For 5.0, I have 2 similar routing policies with the only difference being "Match all" tag when I create the policy.
Currently, both of the routing policies seem to have the same affect and both seem to be doing a logical "and" of all terms provided.
Need the usecase for "Match all" tag or we need to remove this config option if its redundant or not supported.
With "Match all" selected:
<iq>
<routing-
<term>
<term-
<protocol>
<community>
<community-
<community-
</term-
<term-
<update>
<as-path>
<expand />
</as-path>
<community>
<add>
</add>
<remove />
<set />
</community>
<local-
<med>0</med>
</update>
<action>
</term-
</term>
</routing-
</iq>
With tag removed:
<iq>
<routing-
<term>
<term-
<protocol>
<community>
<community-
<community-
</term-
<term-
<update>
<as-path>
<expand />
</as-path>
<community>
<add>
</add>
<remove />
<set />
</community>
<local-
<med>0</med>
</update>
<action>
</term-
</term>
</routing-
</iq>
looks like there was some confusion regarding the UI.
It turns out we can enter multiple communities (using ',' after each) and this box "match all" applies only to communities.
Additionally multiple protocols can be specified in the same way. I am assuming its a logical OR always for protocol, the backend code also does an OR.
The UI already explicitly allows multiple prefixes ( obviously a logical OR).
Please retry and let me know if there are still issues.