User manual JUNIPER NETWORKS JUNOSE SOFTWARE 11.0.1 RELEASE NOTES 7-14-2010

[. . . ] JUNOSeTM Software for E SeriesTM Broadband Services Routers Release Notes Release 11. 0. 1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-07-14 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. [. . . ] This outage does not occur when the same configuration is applied on a Gigabit Ethernet interface. [Defect ID 179794] 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. 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. [Defect ID 60933] 36 Known Problems and Limitations Release 11. 0. 1 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/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. The inPacketOctetDiscards counter in the output of the show atm vc atm interface vcd command includes both inBytesDropped and inBytesUnknownProtocol statistics. The inBytesUnknownProtocol stxatistics 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. [. . . ] 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 111 JUNOSe 11. 0. 1 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. [. . . ]