Specifications

interface-name] hierarchy level. There is no new configuration option available if the

firewall filter term action is set to next-ip, meaning that if the next-ip is down, traffic is

still dropped.

The action configured at this level only becomes active if the next-interface is down

and the ARP on the interface is cleared. If not configured, the default action is to drop

the packet.

Routing Protocols

•

Support for BMP version 3—Starting in Junos OS Release 13.3, BGP monitoring protocol

(BMP) version 3 is supported. BMP allows a remote device (the BMP station) to monitor

BGP as it is running on a router or group of routers. BMP version 3 includes substantial

additional functionality versus version 1. The BMP version 3 configuration is incompatible

with the old version. If you are running BMP version 1 on your Juniper Networks devices,

be sure to update your BMP configuration when you upgrade to Junos OS Release 13.3.

[See Configuring BGP Monitoring Protocol Version 3.]

•

Support for consistent load balancing for ECMP groups (MX Series routers with

MPCs)—Effective in Junos OS Release 13.3R3, on MX Series 3D Universal Edge Routers

with modular port concentrators (MPCs) only, you can prevent the reordering of flows

to active paths in an ECMP group when one or more paths fail. Only flows that are

inactive are redirected. This feature applies only to Layer 3 adjacencies learned through

external BGP connections. It overrides the default behavior of disrupting all existing,

including active, TCP connections when an active path fails. Include the consistent-hash

statement at the [edit policy-options policy-statement policy-statement-name then

load-balance] hierarchy level. You must also configure a global per-packet

load-balancing policy.

[See Actions in Routing Policy Terms. ]

•

Recursive DNS server ICMPv6 router advertisement option support (M Series, MX

Series, and T Series)—Beginning with Junos OS Release 13.3R4, you can configure a

maximum of three recursive DNS server addresses and their respective lifetimes via

static configuration at interface level for IPv6 hosts. Previously, rpd supported only

link-local address information, prefix information, and the link MTU. The router

advertisement-based DNS configuration is useful in networks where an IPv6 host’s

address is auto-configured through an IPv6 stateless address and where there is no

DHCPv6 infrastructure available.

To configure the recursive DNS server address, include the dns-server-address statement

at the [edit protocols router-advertisement interface interface-name] hierarchy level.

[See Example: Configuring Recursive DNS Address.]

New and Changed Features