Known Problems and Limitations
35
Release 10.2.2
When a mirror rule that triggers on username is employed for packet mirroring
of dynamic IP subscribers over ATM, removal of the rule does not disable
packet mirroring. [Defect ID 175356]
Work-around:
Use a mirror rule that triggers on account session ID rather than
on username.
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. Edited [Defect ID 60933]
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]
When one or more ATM1483 attributes appears in a profile, the
show
configuration include-defaults
command fails to display the default values for
all possible ATM1483 attributes. [Defect ID 67157]
The output of the
show atm arp
command displays only 4096 entries when the
line module is configured with more than 4096 NBMA ARP entries. [Defect ID
68849]
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]
The
baseline interface atm
command fails for a VCD assigned by the router to
F4 OAM circuits. [Defect ID 174482]
Unified ISSU is not supported when ILMI is configured on ATM interfaces.
[Defect ID 176007/177297/177122]
ATM line modules reset after unified ISSU completes at the LAC when an
MLPPP bundle with three links are tunneled to the LNS. [Defect ID 178821]
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.
