Routing Protocols
■
BGP support for MDT-SAFI updates without a route target
—By default, the
JUNOS Software requires MDT-SAFI updates to have a route target attached.
Some vendors do not support attaching route targets to the MDT-SAFI updates.
For interoperability with these vendors, the JUNOS Software allows importing
MDT-SAFI updates without a route target being attached. The MDT-SAFI is
imported if the MDT default address in the MDT-SAFI prefix matches the MDT
default address configured within the routing instance.
To configure the MDT default address, include the
group-address
group-address
statement at the
[edit routing-instances
routing-instance-name
provider-tunnel
pim-ssm]
hierarchy level.
[
Multicast
,
Policy Framework
]
■
Distributed periodic packet management support for aggregate
interfaces
—Extends support for the Bidirectional Forwarding Detection (BFD)
protocol to use the periodic packet management daemon (PPMD) to distribute
IPv4 sessions over aggregate interfaces. PPMD automatically runs on the Routing
Engine and the Packet Forwarding Engine. To disable PPMD on the Packet
Forwarding Engine only, include the
no-delegate-processing
statement at the
[edit
routing-options ppm]
hierarchy level. Only IPv4 BFD sessions over aggregate
interfaces are supported. PPMD does not support IPv6 BFD sessions over an
aggregate interface or MPLS BFD sessions over an aggregate interface.
[
Routing Protocols
]
■
PIM join suppression support
—Enables a router to defer sending join messages
to an upstream router when identical join messages are sent on the same
multiaccess network. This improves scalability and efficiency by reducing the
number of identical messages sent to the same router.
This feature is useful when there are a large number of routers on a multiaccess
network that will be receiving traffic for a particular multicast group. Suppressing
joins at each router saves bandwidth and reduces heavy processing at upstream
routers.
PIM join suppression can be implemented per multiaccess interface and per
multicast group. It is only needed on downstream routers, and does not need to
be implemented on upstream routers in order for it to work.
A tracking bit field on the LAN prune delay hello option is used in the CLI to
enable join suppression for downstream routers. By default, the tracking bit is
set to 1 and PIM join suppression is disabled. This is the default behavior for
JUNOS Release 10.0 and earlier for Juniper Networks routers. With join
suppression disabled (T-bit=1), a downstream receiving router will send join
messages even if it receives identical joins for the same upstream router, as long
as no other router in the network has join suppression enabled. When the tracking
bit is set to 0 for at least one neighbor on this interface, join suppression is
enabled, and the receiving router will defer sending identical joins. Use
reset-tracking-bit in the CLI to enable join suppression.
When an upstream router receives a join message, its behavior is independent
of the value of the T-bit in the hello option. When join suppression is triggered,
a timer is activated and all sending of joins is deferred for the length of time
24
■
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes