Specifications

and if the RPM server is Packet Forwarding Engine-based, the RPM client must also
be Packet Forwarding Engine-based.
•
The show chassis fabric unreachable-destinations command is incorrectly mentioned
as supported on MX240, MX480, and MX960 routers from Junos OS Release 11.4R2
and Junos OS Release 12.1. The Supported Platforms section of this topic also incorrectly
state MX240, MX480, and MX960 routers as supported routers for this command.
This command is not available on the MX240, MX480, and MX960 routers. Instead,
the correct command is the show chassis fabric destinations command, which you can
use to view the state of fabric destinations for all FPCs.
•
The following additional information regarding the processing of TWAMP traffic applies
to the "Configuring TWAMP Servers" section in the "Configuring TWAMP" topic:
The preceding configuration settings that are described define a TWAMP server on the
router that enables a TWAMP client to connect to the server using any media interface
IP address such as a ge- interface. In such a scenario, the router functions as a TWAMP
server and timestamping is performed in the ukernel of the media-facing FPC.
To configure an inline TWAMP server, which causes timestamping to be performed as
part of the inline services (si-) interface processing, configure the amount of bandwidth
reserved on each Packet Forwarding Engine for tunnel traffic using inline services by
including the bandwidth (1g | 10g) statement at the [edit chassis fpc slot-number pic
number inline-services] hierarchy level and specify the service PIC logical interface that
provides the TWAMP service by including the twamp-server statement at the [edit
interfaces sp-fpc/pic/port unit logical-unit- number family inet] hierarchy level.
•
The description of the check option available with the request chassis routing-engine
master command topic fails to state that this option is supported on MX104 routers
and PTX5000 routers, in addition to the list of device models mentioned in that topic.
Also, this option is incorrectly stated as supported on MX240 routers, whereas this
option is not supported on those routers.
•
The network-services configuration statement topic inadvertently fails to state that
the enhanced network services mode settings, such as the enhanced-ethernet and the
enhanced-ip option, are supported on MS-MPCs on MX Series routers.
•
The "Configuring Redundancy Fabric Mode for Active Control Boards on MX Series
Routers" topic incorrectly states that on MX routers that contain the enhanced SCB
with Trio chips and the MPC3E, redundancy mode is enabled by default. The correct
default behavior is that on MX routers that contain the enhanced SCB, regardless of
the type of DPC or MPC installed on it, the default mode is the redundancy mode.
139Copyright © 2015, Juniper Networks, Inc.
Documentation Updates