Change the date to 2004, and do not use NTP.
set date 200403311010.10
-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
Mircho Mirchev
Sent: Saturday, March 29, 2014 11:32 PM
To: Tom Storey
Cc: Juniper Maillist
Subject: Re: [j-nsp]
Hi -
Let's say I want to reject everything except the following communities:
Either 100:100
OR 101:101
OR both 100:100 101:100
Tried to setup something:
[edit policy-options]
policy-statement TEST {
term TEST1 {
from community [ TEST1 TEST2 ]; ///Is not it logical OR, and
Hello all,
I had about 3 weeks ago a Main Board PFE Temp Too Hot alarm on a EX Switch.
Currently everything seems normal, temp is in the 30C area. But the alarm is
still present with show chassis alarm. What can I do to clear this?
Thanks!Frank
---
Alle Postfächer an einem Ort. Jetzt wechseln
A match 100:100
B match 101:101
Your TEST1 term match on !A OR !B = !(A AND B), so it effectively rejects
every route that has NO communities 100:100 AND 101:101 (at the same time)
Your target is to accept A OR B, so you can first match and accept on these
communities (TEST1 OR TEST2 defined
Hello Krasi,
Thanks for the reply, appreciated. Sorry I did not mention in my first email
that I'm trying to find a workaround while using invert-match. Any idea on
achieving the same results when using invert-match.
Kind regards,
Date: Mon, 31 Mar 2014 13:41:40 +0300
Subject: Re: [j-nsp]
In addition to my last question, what I don't understand is that !A OR !B =
!(A AND B) /// how come it became AND operation rather than logical OR///
From Juniper documentation:
You can include the names of multiple communities in the community match
condition. If you do this, only one
The logic of !A OR !B makes my head hurt, so its simple to write out a
truth table to work out exactly what it does.
A | B | !A OR !B
---
T | T | F
T | F | T
F | T | T
F | F | T
This makes it clear that !A OR !B is identical to !(A AND B)
I don't think there is any way to do
Le 31/03/2014 13:47, Andrew Khan a écrit :
In addition to my last question, what I don't understand is that !A OR !B =
!(A AND B) /// how come it became AND operation rather than logical OR///
Think of them in terms of boolean truth tables.
From Juniper documentation:
You can include the
Thanks, Dave! Your table is awesome and clarified my doubts and clicked into my
mind :) On your query, It may be possible to add the two communities into one
community statement. I'm unsure how exactly that will behave though
let's say something like
community A members [ 100:100 101:101 ];
Yes, that's what that documentation is saying. You probably don't want a
single community statement then.
Regards,
Dave
On 31 March 2014 13:13, Andrew Khan good1...@outlook.com wrote:
Thanks, Dave! Your table is awesome and clarified my doubts and clicked
into my mind :) On your query, It
I managed to find an hour or so today to look at this further.
A commit script is the result. My very first!
match configuration {
var $comment = $junos-context/commit-context/commit-comment;
if( jcs:empty ($comment)) {
xnm:error {
message
With the requirement to use only invert-match community definitions let
say:
TEST1 = everything except 100:100
TEST2 = everything except 101:101
we have !TEST1 OR !TEST2 ( these are target routes you want to accept) =
!(!!TEST1 !!TEST2) = !(TEST1 TEST2)
So define policies:
policy-statement
Hello.
I need to change CF in RE-850. How big capacity of CF is supported ?
It is difficult to find a 1-2Gb CF now. Have anybody experience
installing 8Gb CF ?
--
Regards,
Sergey
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
Do anyone have in-sight on this?
More over, I guess my quest is to find a device that support
1) per flow hashing with as many as ECMP route as possible. (not sure how
many ECMP route is supported)
2) consistent hashing (existing flow don't break if route is added or
removed) (juniper doc
14 matches
Mail list logo
