Errata and Changes in Documentation for JUNOS Software Release
9.3 for M-series, MX-series, and T-series Routing Platforms
Changes to the JUNOS Documentation Set
The new JUNOS MX-series Layer 2 Configuration Guide provides an overview of the Layer 2 functions of the MX-series routers,
including configuring bridging domains, MAC address and VLAN learning
and forwarding, and spanning-tree protocols. It also details the routing
instance types used by Layer 2 applications. All of this material
was formerly covered in the JUNOS Routing Protocols Configuration Guide.
Errata
This section lists outstanding issues with the documentation.
User Interface and Configuration
The show system statistics bridge command displays
system statistics on MX-series routers. [System Basics Command
Reference]
Interfaces and Chassis
The version of the JUNOS Network Interfaces Configuration Guide accessible
at the JUNOS documentation home page (http://www.juniper.net/techpubs/software/junos/) corrects some errors in the version included on the JUNOS 9.3 Documentation
DVD. We recommend always accessing the online version to obtain the
most current information. [Network Interfaces]
In the JUNOS Network Interfaces Configuration Guide, Chapter 44 "Configuring
IEEE 802.1ag OAM Connectivity-Fault Management", "Configuring a CFM
Interface Down Action Profile Action" section states the following:
“NOTE: The action profile is supported only on the physical
interface level, and not on the logical interface level.” This
is incorrect, and has been revised in the 9.6R1 release of the same
document. The note has been replaced with the following text: “The
action profile is supported on the physical interface level and the
logical interface level.” [Network Interfaces]
Services Applications
The sample output and description of output fields for the show services pgcp statistics gateway command in the JUNOS System Basics and Services Command Reference do
not reflect the changes made to the command’s output in JUNOS
Release 9.3R2. [System Basics Command Reference]
Subscriber Access Management
Some links in the HTML output for the JUNOS
Subscriber Access Configuration Guide do not work correctly.
If you encounter any broken links, the workaround is to locate the
information by browsing the HTML expanded table of contents or the
HTML index.
Routing Policy and Firewall Filters
In the JUNOS 9.3 Configuration and Diagnostic
Automation Guide, the hyperlinks to the jcs:parse-ip function in the Table of Contents and in the second section titled
“Extension functions in the junos.xml File” (https://www.juniper.net/techpubs/software/junos/junos93/swconfig-automation/extension-functions-in-the-junosxsl-file_1.html) link
to the wrong target (the jcs:break-lines function). To access
the reference page for the jcs:parse-ip function, navigate
to the preceding or subsequent page and use the [Next] or [Prev] hyperlink. [Automation]
For MX-series routers only, you can configure a firewall
filter to provide matching on packet loss priority (PLP) level carried
in the frame for any protocol family. The match condition can specify
a single value or a range of values. [Layer 2, Policy ]
VPNs
When you issue a ping vpls instance command,
a chassis MAC address is drawn from the ingress PE router's pool of
MAC addresses and used to create the VPLS ping packet. The ping packet
is then forwarded to the egress PE router. When the egress PE router
receives the ping packet, it learns the MAC address from the VPLS
ping packet. The MAC address is added to the egress PE router's MAC
table. [System Basics Command Reference]
The LDP BGP VPLS interworking feature is currently supported
only on MX-series and M320 routers. [VPNs]
The ability to terminate multiple Layer 2 circuit pseudowires
at a single VPLS mesh group is not supported. Do not configure the local-switching statement at the [edit routing-instances routing-instance-name protocols vpls mesh-group group-name] hierarchy level. You must instead configure
a mesh group for each Layer 2 circuit pseudowire terminating at the
router. [VPNs]
High Availability
The section titled “Nonstop Active Routing Layer 2
Circuit and LDP-Based VPLN Support” in the JUNOS High Availability Configuration Guide uses
the term VPLN instead of the intended term VPLS. [High Availability]
The ability to terminate multiple Layer 2 circuit pseudowires
at a single VPLS mesh group is not supported. Do not include the local-switching statement at the [edit routing-instances routing-instance-name protocols vpls mesh-group group-name] hierarchy level. You must instead configure
a mesh group for each Layer 2 circuit pseudowire terminating at the
router. [VPNs]
Class of Service
The JUNOS Class of Service Configuration Guide incorrectly states that high-priority
queues on IQ2 PICs and EQ DPCs can starve lower priority queues if
the high-priority queues are not rate limited. In fact, if a queue
of any priority level is not rate limited, it can starve a queue with
lower priority (for example, a medium-priority queue can starve a
low-priority one). [CoS]
Mulitcast Applications
The JUNOS Class of Service Configuration Guide incorrectly states that high-priority
queues on IQ2 PICs and EQ DPCs can starve lower-priority queues if
the high-priority queues are not rate limited. In fact, if a queue
of any priority level is not rate limited, it can starve a queue with
lower priority (for example, a medium-priority queue can starve a
low-priority one). [CoS]
In the JUNOS Multicast Configuration Guide, under the section titled, “Configuring PIM Join Load Balancing”,
the following has been updated: “When PIM join load balancing
is enabled in a multicast VPN scenario with point-to-multipoint (P2MP)
tunnels, the load balancing is achieved based on the join counts for
the far-end provider edge (PE) routers, not for any intermediate P
routers” to correctly state “ When PIM join load balancing
is enabled in a draft-rosen Layer 3 VPN scenario, the load balancing
is achieved based on the join counts for the far-end provider edge
(PE) routers, not for any intermediate P routers.” In addition,
the following note has been added to this section to make the support
clear: “NOTE: PIM join load balancing is supported on Draft
Rosen multicast VPNs (also referred to as Dual PIM Multicast VPNs).
PIM join load balancing is not supported on multiprotocol BGP-based
multicast VPNs (also referred to as next-generation Layer 3 VPN multicast).”
[Multicast]
System Logging
The destination-address field is
no longer valid in the system log message text for the following tags: RPD_IGMP_JOIN, RPD_IGMP_LEAVE, RPD_MLD_JOIN, and RPD_MLD_LEAVE. In JUNOS Release 9.3 and later, the
character string “(null)” appears in the field instead
of an actual address, as in this example: “RPD_IGMP_JOIN: Listener ip-address sent a join to (null) for group multicast-address source * on interface interface-name at timestamp.” [System Log]
When an interface configured for IGMP or MLD goes down,
an RPD_IGMP_LEAVE or RPD_MLD_LEAVE message is no
longer generated for each group and host pairing that is associated
with the interface. Instead, a single message is generated, such as
the following: “RPD_IGMP_ALL_SUBSCRIBERS_DELETED: All IGMP subscribers
on interface interface-name deleted at timestamp because the interface is down.”
The RPD_IGMP_LEAVE and RPD_MLD_LEAVE messages
are still generated when a subscriber session ends or times out. [System Log]
