Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6 Release Note page 48

JUNOS OS 10.4 Release Notes
48
statement and include the
from
match condition statement at the following hierarchy levels:
[edit policy-options policy-statement policy-name term term-name]
[edit logical-systems logical-system-name policy-options policy-statement policy-name
term term-name]
If you configure multiple
community-count
is effectively a logical AND operation. The following example accepts BGP routes with
two, three, or four communities. If a route contains three communities, it is considered
a match and is accepted. If a route contains one community, it is not considered a
match and is rejected.
[edit]
policy-options {
policy-statement import-bgp {
term community {
from {
community-count 2 orhigher;
community-count 4 orlower;
}
then {
accept;
}
}
}
}
[Routing Policy]
Enhancement to the PIM system log messages—The RPD_PIM_NBRDOWN and the
RPD_PIM_NBRUP system log messages have been updated to include the name of
the routing instance. This enhancement is also applicable to Junos OS Release 10.0R4,
10.1R4, 10.2R2, and 10.3R1. The following sample shows the enhanced PIM system log
messages (depending on your network configuration, the type of messages you see
might be different):
Jun 15 21:54:43.831533 RPD_PIM_NBRDOWN: Instance PIM.master: PIM neighbor 11.1.1.2
(so-0/1/3.0) removed due to: the interface is purged
Jun 15 21:53:28.941198 RPD_PIM_NBRUP: Instance PIM.master: PIM new neighbor 11.1.1.2
interface so-0/1/3.0
[System Log Messages Reference]
community-count value (equal | orhigher | orlower)
match condition statements, the matching
Copyright © 2011, Juniper Networks, Inc.