Known Behavior
13
Release 11.0.2
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.
When you reload an ATM line module that is configured with NBMA circuits as
passive OSPF interfaces and that has established OSPF adjacencies and IBGP
peers (configured on Gigabit Ethernet interfaces), the transmission of OSPF
hello packets might be affected until all the NBMA interfaces have initialized.
[Defect ID 46157]
Work-around:
Either remove the passive OSPF interface statements on the
NBMA interfaces, or statically configure the OSPF cost on the NBMA interfaces.
The ATM peak cell rate (PCR) does not appear in the L2TP Calling Number AVP
for the first PPP session when the ATM shaping parameters were configured by
RADIUS return attributes. [Defect ID 60933]
When you configure an ATM PVC where PCR = SCR and maximum burst size
is zero, the CLI returns an error indicating the burst size is invalid and it does
not create the VC. [Defect ID 58357]
Work-around:
Configure a CBR or a UBR plus PCR to create the circuit with the
same parameters, depending on the desired priority for the traffic. CBR has a
high priority and UBR plus PCR has a medium priority.
When you use the
no-authenticate
keyword with the
subscriber
command to
prevent subscriber authentication so that the subscriber information can be
used for DHCP option 82, suboption 2, the SRP module can reset. This issue
does not occur when you use the
no-authenticate
keyword with the
subscriber
command as a way to perform a RADIUS configuration. [Defect ID
69865]
When you perform an snmpWalk on the juniAtmSubIfVccTable, a response is
received for only a few of the total configured ATM subinterfaces when both of
the following are true: the router has a line module that has some ATM-related
configuration and the line module is in the disabled state. [Defect ID 80020]
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.
