JUNOSe 10.0.3 Release Notes
58
Errata
DHCP external server began supporting unified ISSU in JUNOSe Release 10.0.0.
Therefore, you can perform unified ISSU even when the DHCP external server
is configured on the virtual router for JUNOSe Release 10.0.0 and
higher-numbered releases.
The
Monitoring Suspicious Control Flow
section in
JUNOSe System Basics
Configuration Guide, Chapter 9, Passwords and Security
, incorrectly contains a
section titled
show snmp interfaces
. The discussion in this section is only about
commands to monitor suspicious control flows, while the
show snmp
interfaces
command is used to view SNMP status.
The
show snmp interfaces
command is described in detail in the
Monitoring
Interface Tables
section in
Chapter 4, Configuring SNMP
. However, the heading
of the subtopic in that section incorrectly reads
show snmp group
, while the
description is about the usage of the
show snmp interfaces
command.
JUNOSe System Basics Configuration Guide, Appendix B References,
and
JUNOSe
IP Services Configuration Guide, Chapter 7, Configuring ANCP,
fails to state the
correct version of the GSMPv3 Base Specification.
The correct version of the IETF draft is draft-ietf-gsmp-v3-base-spec-06.txt and
not draft-ietf-gsmp-v3-base-spec-07.txt.
In the
Monitoring the Current Configuration
section of
JUNOSe System Basics
Configuration Guide, Chapter 5, Managing the System
, the example for the
service check-config
command is incorrect. The correct example is
host1(config)#
service check-config auto
and not host1(config)#
service
config-check auto.
The
ES2 10G Uplink LM Combination
and
ES2 10G LM Combination
, sections in
JUNOSe Physical Layer Configuration Guide, Chapter 5, Configuring Ethernet
Interfaces
incorrectly indicates that the IOAs on these LMs can also support 9.6
Kbps jumbo packets at both the ingress and egress.
The correct unit specification for the maximum receive unit (MRU), which is
referenced in this line, is bytes and not Kbps. Therefore, the correct size of
jumbo packets that these IOAs can support at both the ingress and egress is
9600 bytes. This value refers to the maximum allowable size in bytes of the
MRU for the jumbo Ethernet frames and not the maximum allowable size in
bytes of the MTU (frames transmitted from the egress interface).
In the JUNOSe documentation for Release 8.0.0 and higher-numbered releases,
the
auto-revert
keyword, which is used with the
redundant-port
command to
configure Ethernet link redundancy for an IEEE 802.3ad link aggregation group
(LAG), was incorrectly documented as requiring the keywords
auto-revert on
to enable auto-reversion and
auto-revert off
to disable auto-reversion. In fact,
the keywords
on
and
off
are not valid for
auto-revert
. An example of the
correct command for enabling auto-reversion is as follows, where
gigabitEthernet 1/1 is the redundant link for an 802.3ad LAG interface:
host1(config-if)#
redundant-port gigabitEthernet 1/1 auto-revert
