User manual JUNIPER NETWORKS JUNOSE 10.0.3 RELEASE NOTES 4-30-2010

[. . . ] JUNOSeTM Software for E SeriesTM Broadband Services Routers Release Notes Release 10. 0. 3 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-04-30 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. [. . . ] [Defect ID 175356] Work-around: Use a mirror rule that triggers on account session ID rather than on username. ANCP On an E320 router that has established 3000 ANCP adjacencies with a client and traffic is initiated, the following behavior occurs sporadically: All existing Telnet sessions are disconnected and no new Telnet sessions can be established for several minutes. [Defect ID 83872] ARP The ES2 4G LM can reset during a unified in-service software upgrade after you issue the issu start command on a router configured with 8000 dynamic VCs and 8000 packet-triggered dynamic subscriber interfaces. [Defect ID 86761] ATM 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] When 16, 000 PPPoA interfaces are configured on an OCx/STMx ATM line module paired with an OC3-4 I/O module in an ERX-14xx model, ERX-7xx model, or ERX-310 router, PING traffic passing through the line module on the restarting router experiences an outage of 103 seconds, which is beyond the maximum limit, after a unified ISSU from JUNOSe Release 9. 2. 0p1-0 to 9. 3. 0b0-12. This outage does not occur when the same configuration is applied on a Gigabit Ethernet interface. [Defect ID 179794] 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] Unified ISSU is not supported when ILMI is configured on ATM interfaces. [Defect ID 176007/177122 ] The line module resets when you issue the show nbma arp command after you have configured NBMA interfaces on an ATM line module. [Defect ID 88491] 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] Known Problems and Limitations 35 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. 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. [. . . ] The capability to receive line rate data, when it changes on the access node, is disabled by default on the SRC client. Configuring the SRC Client to Retrieve DSL Information from Access Nodes 109 JUNOSe 10. 0. 3 Release Notes The access node passes the DSL line rate parameters, whenever they change, to the SRC client. The SRC client appends updated parameters to the COPS messages that it sends to the COPS server or SRC server. A COPS server processes the following topology parameters that it receives from the SRC client in the updated COPS messages: junoseIpInterfaceMode junoseIpInterfaceUpstreamRate junoseIpInterfaceDownstreamRate junoseIpInterfaceMinimumDataRateUpstream junoseIpInterfaceMinimumDataRateDownstream junoseIpInterfaceAttainableDataRateUpstream junoseIpInterfaceAttainableDataRateDownstream junoseIpInterfaceMaximumDataRateUpstream junoseIpInterfaceMaximumDataRateDownstream junoseIpInterfaceMinimumLowPowerDataRateUpstream junoseIpInterfaceMinimumLowPowerDataRateDownstream junoseIpInterfaceMaximumInterleavingDelayUpstream junoseIpInterfaceActualInterleavingDelayUpstream junoseIpInterfaceMaximumInterleavingDelayDownstream junoseIpInterfaceActualInterleavingDelayDownstream junoseIpInterfaceDSLlinestate A COPS server that runs an SRC software release earlier than Release 3. 0. 0 does not support and process the preceding topology parameters that are appended to the COPS messages. Such COPS servers analyze the information, other than the parameters that describe updated DSL line rate details, that they receive in the COPS messages for policy management. [. . . ]