Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010 Release Note page 72

JunosE 10.3.2 Release Notes
64
Errata
In the Detecting Peer Reachability with BFD section in JunosE BGP and MPLS
Configuration Guide, Chapter 1, Configuring BGP Routing, the
neighbor-bfd-liveness-detection command subsection incorrectly states the
following:
If you remove the BFD configuration while the BGP sessions and the BFD
protocol session are up, then the BGP session may flap because the remote BGP
speaker cannot detect why the BFD session went down.
The correct behavior of BGP sessions, when you remove the BFD configuration
for the last client tied to a BFD session, is as follows:
If you remove the BFD configuration while the BGP sessions and the BFD
protocol session are up, BFD moves to the Admin Down state and
communicates the change to the peer to enable the client protocols to handle
this transition in a seamless manner without going down. For the Admin Down
state to work, the peer, which receives the Admin Down state notification, must
have the capability to distinguish between administratively down state and real
link down.
The BFD Admin Down state is used to bring down a BFD session
NOTE:
administratively, to protect client applications from BFD configuration removal,
license issues, and clearing of BFD sessions.
The Number of CAM Entries Per Allocation and Free Entries section in Chapter 8,
Policy Resources of the JunosE Policy Management Configuration Guide
inadvertently omitted the following paragraph:
The block that is common to the variable-sized entries is not available for
144-bit CAM entries when you configure any 288-bit or 576-bit entries, even
though you remove them later. It is also not available for any 288-bit or 576-bit
entries when the 144-bit entries spill into this block, even though you remove
the 144-bit entries later.
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 the JunosE 10.3.1 Release Notes for detailed information.