User manual JUNIPER NETWORKS JUNOSE 10.3.1 RELEASE NOTES 3-19-2010

[. . . ] JUNOSeTM Software for E SeriesTM Broadband Services Routers Release Notes Release 10. 3. 1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-03-19 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 31034] When you copy the running configuration to NVS, the E Series router verifies whether it has available space equal to at least twice the size of the . cnf file. [Defect ID 40655] Work-around: Make sufficient space on the NVS by deleting . rel or . cnf files. 32 Known Behavior Release 10. 3. 1 You cannot delete the ipInterface log after you delete the corresponding IP interface. This does not prevent you from adding filters to other interfaces, nor does it prevent you from adding a filter to the same interface if you re-create it after deletion. [Defect ID 34842/45063] Work-around: Remove the filter before you remove the interface. Alternatively, if you remove the interface first, then you must remove all filters associated with all IP interfaces. System Logging If you enable engineering logs and set the control network logs to a level of notice or lower (down from the default of error), you might see erroneous controlNetwork log messages like the following that are generated because SNMP polling on line modules (correctly) detects no fabric: [Defect ID 43168] NOTICE 09/01/2002 18:47:52 CEST controlNetwork (slot 11): Control Bus Master slave error 0x5 while accessing slot Tunneling When you configure the GE-2 line module, the GE-HDE line module, or the ES2-S1 GE-4 IOA to operate as a shared tunnel-server module, the available bandwidth for tunnel services is limited to 0. 5 Gbps per module. In releases numbered lower than Release 7. 3. 0, a dynamic tunnel-server port was located on port 8 of the GE-HDE line module and GE-8 I/O module. In Release 7. 3. 0 and higher-numbered releases, the dynamic tunnel-server port is located on port 9. When you upgrade to Release 7. 3. 0, any existing tunnel-server port configurations move from port 8 to port 9. Known Behavior 33 JUNOSe 10. 3. 1 Release Notes Known Problems and Limitations This section identifies the known problems and limitations in this release. For more information about known problems that were discovered at customer sites, you can log in to the JUNOSe Knowledge Base at https://www2. juniper. net/kb/, enter the defect ID number in the Search by Keyword field, and click Search. 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] ATM When 16, 000 PPPoA interfaces are configured on an OCx/STMx ATM line module paired with an OC3-4 I/O module in an ERX14xx model, ERX7xx model, or ERX310 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] 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] 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] 34 Known Problems and Limitations Release 10. 3. 1 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. [. . . ] 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. 3. 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. [. . . ]