JUNOSe 10.3.1 Release Notes
12
Known Behavior
Known Behavior
This section briefly describes E Series router behavior and related issues. In some
cases the behavior differs from non–E Series implementations; in others the
behavior is included to emphasize how the router works.
AAA
Although you can use the
max-sessions
command to configure a maximum of
32,000 outstanding authentication/authorization requests to a RADIUS server,
AAA internal limits prevent the actual number of outstanding
authentication/authorization requests from exceeding 9600. These internal
AAA limits apply only to authentication/authorization requests and not to
accounting requests.
The JUNOSe Software does not support accounting for ATM 1483 subscribers.
The
atm1483
keyword for the
aaa accounting default
command is present in
the CLI, but it is not supported.
ATM
You cannot configure connection admission control (CAC) on an ATM interface
on which you have created a bulk-configured virtual circuit (VC) range for use
by a dynamic ATM 1483 subinterface. Conversely, you cannot create a
bulk-configured VC range on an ATM interface on which you have configured
CAC. The router rejects these configurations, which causes them to fail.
Configuring CAC and bulk-configured VCs on the same ATM interface was
supported in previous JUNOSe Software releases. As a result, If you are
upgrading to the current JUNOSe release from a lower-numbered release,
configurations that use CAC and bulk configuration on the same ATM interface
continue to work. However, we recommend that you disable CAC on these
ATM interfaces to ensure continued compatibility with future JUNOSe releases.
BGP
The E Series router does not include the link-local IPv6 address in the next-hop
field of an MP-BGP update message carrying IPv6 routing information over
IPv4 transport. This behavior is compliant with RFC 2545 but might have
interoperability issues with other implementations that depend on a link-local
IPv6 address in the next-hop field on a directly connected external BGP
peering.
Work-around:
Enable EBGP multihop configuration on the remote
(non–Juniper Networks) peer.
The following message might be displayed under certain conditions:
bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting
inbound TCP connection
The message is generated when an unconfigured peer attempts to establish a
TCP session with an E Series router and a valid route to the source address of
the peer is absent from the router’s routing table.