Multiplay
■
Border gateway function (BGF) improved efficiency and scalability through
use of service interface pools
—You can now use service interface pools to
improve the maintainability and scalability of your service set configurations.
When your service sets handle VPN traffic, you
must
specify a service interface
pool for the next next-hop-service for the service sets. The interfaces that are
members of the pool can serve as either inside or outside interfaces.
You should also specify service interface pools as the next-hop service for service
sets that do not currently handle VPN traffic. You gain the immediate benefit of
more efficient resource utilization
and
you can add VPNs to the service set in
the future without reconfiguring your service sets.
[
Multiplay Solutions
]
Routing Policy and Firewall Filters
■
The
ipsec-sa
sa-name
firewall filter action is no longer supported on the MX Series
routers. To configure one or more actions for a firewall filter, include the
actions
statement at the
[edit firewall family
family-name
filter
filter-name
term
term-name
then]
hierarchy level.
[
Policy
]
■
Enhanced match-conditions support for VPLS and bridge firewall filters (MX
Series routers and routers with Enhanced IQ2 [IQ2E] PICs only)
—The protocol
families
vpls
and
bridge
now support the
interface-set
match condition for firewall
filters. To configure, include the
interface-set
interface-set-name
statement at the
[edit firewall family bridge filter
filter-name
term
term-name
from]
or the
[edit firewall
family vpls filter
filter-name
term
term-name
from]
hierarchy level. The protocol
family
bridge
is supported only on MX Series routers.
An interface set is a set of logical interfaces used to configure hierarchical class-of-
service schedulers. Previously only the following protocol families supported the
interface-set
match condition:
ipv4
,
ipv6
,
any
, and
mpls
.
[
Policy
]
Routing Protocols
■
OSPF sham link
—An OSPF sham link is now installed in the routing table as a
hidden route. Previously, an OSPF sham link was not installed in the routing
table. In addition, a BGP route is no longer exported to OSPF if a corresponding
OSPF sham link is available. To configure a sham link, include the
sham-link local
ip-address
statement at the
[edit routing-instances
routing-instance-name
protocols
ospf]
hierarchy level.
[
Routing Protocols
]
■
Removal of BGP warning message
—If a BGP group is created without any
defined peers, the warning message no longer appears when the configuration
is committed.
[
Routing Protocols
]
Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
47
Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers