We use some same kinds of things here, that is subpolicies expressions (or
subpolicies chains at other places):
policy-statement Blah {
term MyTerm {
from {
policy ( ! (( ! A ) && B && ( C || D )));
}
then next policy;
}
policy-statement A {
term
Hi, in Harry Reynolds JNCIP Book, page 202 of 708 is the ospf multi-area
picture. page 217 of 708 mentions summarization using area-range.
Is there a reason why the lsa-id in area 0 is 10.0.8.0 but is 10.0.9.255 in
area 10 ? It's interesting that the subnet-id of the /23 is used as the
FYI I made a Juniper SE submit an ER to implement this kind of
functionality (plus some more community stuff). What I asked for
related to this case was to be able to add this `logical-operation
or|and|xor|not` to the end of a policy match community statement. I'll
see if I can find the ER info if
IMHO whether you add a community to a policy term match statement or add a
community to a community members list, you still have to add the community
somewhere. I don't see how you get from 2x10 to 100 Maybe I don't
understand the ask.
The only way I know how to get the AND logic to work in a
Hello Serge,
this works, but that is exactly the config I would like to avoid.
In case of 2 communities this adds a third one, but in case of 2x 10
communities that can be combined this adds 100 additional communities.
kind regards
Rolf
> Hello,
>
> Have you tried this?
>
> set policy-options
Hello,
Have you tried this?
set policy-options community MATCH2 members [ 123:1 123:2 ]
I believe this will result in a logical AND.
Serge
On Thu, Apr 6, 2017 at 8:47 AM, "Rolf Hanßen" wrote:
> Hello,
>
> please show me an example, maybe I understood wrong.
> If I just
Hello,
please show me an example, maybe I understood wrong.
If I just create multiple policies and add them to the import/export
statement, they are processed indiviually one after another.
This would result in the same OR-behaviour.
If this match was the whole policy I could combine 2 terms
Hello. You need to Creat 2 policy and make AND in export import protokół
statement.
W dniu czw., 6.04.2017 o 13:04 "Rolf Hanßen" napisał(a):
> Hello,
>
> I wanted to match 2 named communities in a policy and I am interested how
> you solve such things.
>
> policy-options {
>
Hello,
I wanted to match 2 named communities in a policy and I am interested how
you solve such things.
policy-options {
policy-statement xy {
from {
community [a b];
}
}
community a members 123:1;
community
Actually, if the L2 switch supports E-OAM, it can be done as well.
Basically, on router side use 1 subinterface/VLAN per endpoint with CFM
running between the router and switchport connected to that endpoint.
When the endpoint goes down, switchport will go down too, CFM will
signal RDI to
10 matches
Mail list logo