Specifications

| address ipv6-address) statement at the [edit services rpm probe owner test test-name]
hierarchy level. You can also define the RPM client or the source that sents RPM probes
to contain an IPv6 address. To specify the IPv6 protocol-related settings and the source
IPv6 address of the client from which the RPM probes are sent, include the inet6-options
source-address ipv6-address statement at the [edit services rpm probe owner test
test-name] hierarchy level.
Software Installation and Upgrade
•
Support for autoinstallation of satellite devices in a JNU group—In a Junos Node
Unifier (JNU) topology that contains an MX Series router as a controller that manages
satellite devices, such as EX Series Ethernet Switches, QFX Series devices, and ACX
Series Universal Access Routers, the autoinstallation functionality is supported for the
satellite devices. Starting in Junos OS Release 13.3, JNU has an autoinstallation
mechanism that enables a satellite device to configure itself out-of-the-box with no
manual intervention, using the configuration available either on the network or locally
through a removable media, or using a combination of both. This autoinstallation
method is also called the zero-touch facility.
A JNU factory default file, jnu-factory.conf, is present in the /etc/config/ directory and
contains the configuration to perform autoinstallation on satellite devices. The
zero-touch configuration can be disabled by including the delete-after-commit
statement at the [edit system autoinstallation] hierarchy level and committing the
configuration.
[See Autoinstallation of Satellite Devices in a Junos Node Unifier Group and Configuring
Autoinstallation on JNU Satellite Devices.]
Subscriber Management and Services (MX Series)
•
Pseudowire subscriber logical interfaces MPC support—Starting in Junos OS Release
13.3, pseudowire subscriber logical interfaces are supported on MPCs with Ethernet
MICs only.
•
Service packet counting (MX Series)—Starting in Junos OS Release 13.3, you can
configure the counters that subscriber management uses when capturing volume
statistics for subscribers on a per-service session basis.
•
Inline counters are captured when the event occurs, and do not include any additional
packet processing events that occur after the event.
•
Deferred counters are not incremented until the packet is queued for transmission,
and therefore include the entire packet processing. Deferred counters provide a more
accurate packet count than inline counters, and are more useful for subscriber
accounting and billing.
NOTE: Fast update filters do not support deferred counters.
[See Configuring Service Packet Counting.]
47Copyright © 2015, Juniper Networks, Inc.
New and Changed Features