Errata
59
Release 10.0.3
The erroneous information appears in the following guides in the JUNOSe
documentation set:
JUNOSe Release 8.0.0—
Reverting After a Failover
section in
JUNOSe
Physical Layer Configuration Guide
,
Chapter 6
,
Configuring Ethernet
Interfaces
JUNOSe Releases 8.1.0, 8.2.0, and 9.0.0—
Reverting After a Failover
section
in
JUNOSe Physical Layer Configuration Guide
,
Chapter 5
,
Configuring
Ethernet Interfaces
JUNOSe Releases 9.1.0, 9.2.0, 9.3.0, and 10.0.0—
Reverting After a Failover
section in
JUNOSe Link Layer Configuration Guide
,
Chapter 6
,
Configuring
802.3ad Link Aggregation and Link Redundancy
The
redundant-port auto-revert
command was also erroneously omitted from
the procedure in the
Configuring Ethernet Link Redundancy
section of these
chapters.
In
the Configuring PIM SSM section of
Chapter 3, Configuring PIM for IPv4
Multicast
of the
JUNOSe Multicast Routing Configuration Guide,
the SSM group
multicast address limit is incorrect. For JUNOSe Release 8.2 and
higher-numbered releases, the correct SSM group multicast address limit is
IPv4 address range 232.0.0.0/8 and not 232.0.0.0/6.
In the
Configuring Data MDTs
section in
Chapter 3, Configuring PIM for IPv4
Multicast
of the
JUNOSe Multicast Routing Configuration Guide
, the procedures
for configuring the pe13DataMdtSend access-list are incorrect. For correct
procedures to configure the default Multicast Distribution Trees (MDT) and the
data MDTs for configuring the access list, see
Appendix C, Configuring the
Default and Data MDTs
in the
JUNOSe 10.0.2 Release Notes
.
In the
Configuring Group Outgoing Interface Mappin
g section in
Chapter 2,
Configuring IGMP
of the
JUNOSe Multicast Routing Configuration Guide,
the term
"multicast-date-forwarding" in the first paragraph is misspelled. The correct
spelling is "multicast-data-forwarding”.
In the
Graceful Restarts
section in
JUNOSe BGP and MPLS Configuration Guide,
Chapter 1, Configuring BGP Routing
, the following corrections and additions
apply to the working of the BGP graceful restart feature:
The
bgp graceful-restart
and
neighbor graceful-restart
command
sections incorrectly state that advertisement of the graceful restart
capability is enabled by default. The correct default behavior of these
commands is that BGP graceful restart is disabled, and advertisement of
the graceful restart capability is also disabled, both globally and for
specified peers or peer groups.
The
bgp graceful-restart
command section incorrectly mentions that you
can use the
default
keyword to restore the default condition, which causes
the sending of advertisements of the graceful restart capability to be sent.
However, the correct command behavior is that if you use the
default
keyword with the
bgp graceful-restart
command, advertisements of the
graceful restart capability are not sent.