Juniper JUNOSE 11.0.2 - RELEASE NOTES Release Note page 73

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.
NOTE: The BFD Admin Down state is used to bring down a BFD session
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.
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.
The IP Hinting section in JunosE Broadband Access Configuration Guide, Chapter
1, Configuring Remote Access inadvertently omits the following information
about AAA domain map support for IPv4 that enables you to configure
additional virtual router assignment capabilities for IPv4 subscribers:
AAA domain map support for IPv4 enables you to provide additional virtual
router assignment capabilities for IPv4 subscribers. If you assign a value other
than default to a layer 2 virtual router, then the access, IPv4, and IPv6 virtual
routers are all assigned the same value, which cannot be changed. If you use
RADIUS redirect to assign virtual routers, you can assign access, IPv4, and IPv6
to the redirection target.
Use the auth-router-name command in Domain Map Configuration mode to
assign an access virtual router. The no version restores the default router. An
example of the auth-router-name command is as follows:
host1(config)#aaa domain-map xyz.com
host1(config-domain-map)#auth-router-name accessvr
NOTE: The auth-router-name command replaces the router-name command,
which has been deprecated and may be removed completely in a future release.
Release 11.0.2
65
Errata