JUNOSe 10.0.3 Release Notes
60
Errata
The
neighbor graceful-restart
command section fails to state that using
the
no
version of this command disables advertisement of the graceful
restart capability for specified peers or peer groups only. The
no
form of
this command does not affect global advertisement of the graceful restart
capability.
The Note in the
timeout
command section in
JUNOSe Broadband Access
Configuration Guide, Chapter 1, Configuring Remote Access
fails to mention that
the router uses the backoff algorithm only for subscriber AAA accounting
messages except Acct-On messages.
In the JUNOSe documentation for Release 9.3.x, 10.x.x, and 11.0.x, the
descriptions about support for DSL line rate information retrieval from access
nodes for transmission to the SRC software, and the
sscc
update-policy-request enable
command introduced by this feature are
erroneously omitted. This feature was introduced in JUNOSe Release 9.3.0.
The information on this functionality and associated command is missing from
the following guides in the JUNOSe documentation set:
JUNOSe Broadband Access Configuration Guide—Configuring the SRC Client
section in
Chapter 1, Configuring Remote Access,
and
Monitoring SRC Client
Conection Status
section in
Chapter 2, Monitoring and Troubleshooting
Remote Access
JUNOSe Command Reference Guide N to Z
See
Appendix C, Transferring DSL Line Rate Information from an Access Node to
SRC Software
, in these
Release Notes
for detailed information.
The section
Qualifications for Change of Authorization in JUNOSe Broadband
Access Configuration Guide, Chapter 4, Configuring RADIUS Dynamic-Request
Server
, fails to mention that the Calling-station-id attribute is valid only for the
tunneled subscribers and on the LNS. Also, the Calling-station-id and
NAS-Port-Id attributes are valid only if there is no RADIUS override setting.
The following row was not added to the Local Pool Selection in Equal-Access
Mode table in
JUNOSe Broadband Access Configuration Guide, Chapter 18, DHCP
Local Server Overview
.
Received interface
IP address
The router uses the IP address of the interface on which the DHCP packet is being processed and
attempts to match it with the network address of a DHCP local pool. If the interface address matches with
the IP address configured in the DHCP local address pool on the router, that pool is used to delegate the
address to the client.