Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note page 44

JUNOSe 10.0.3 Release Notes
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 issue the no atm atm1483 auto-configure upperInterfaceType
lockout-time command in Profile configuration mode, the lockout time range
does not revert to the default values. [Defect ID 66544]
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.
The inPacketOctetDiscards counter in the output of the show atm vc atm
interface vcd command includes both inBytesDropped and
inBytesUnknownProtocol statistics. The inBytesUnknownProtocol statistics
should be displayed by a separate counter.
At the major interface level, the inPacketDiscards counter includes both
inPacketsDropped and inPacketUnknownProtocol statistics. The
inPacketUnknownProtocol statistics should be displayed by a separate counter.
[Defect ID 44286]
The baseline interface atm command fails for a VCD assigned by the router to
F4 OAM circuits. [Defect ID 174482]
For PPPoE, the AAL5 inPacket Discards counter might increment erroneously
during call setup when a packet is passed directly to PPPoE for negotiation
rather than being discarded. [Defect ID 51757]
Work-around: Incremental InPacketDiscards during call setup do not
necessarily indicate a problem. However, we recommend you investigate an
excessive count because that might indicate a connection that cannot be
successfully brought up for some reason, such as RADIUS denials or improper
configuration.
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.
36
Known Problems and Limitations