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. 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. [. . . ] In this case, the standby is currently providing services. 34 Known Behavior Release 11. 0. 1 E120 routers and E320 routers report a module as inactive when either: The primary line module has no IOAs. The standby line module has taken over for the primary line module, and has control of the IOAs. Because E120 and E320 routers can accommodate up to two IOAs per slot, at least one IOA must be online. If the second IOA fails, the line module is still online, but does not use both IOAs. You can ensure that every module is up and active in the system and not in a failed state by issuing the show version all command. In a router with a redundancy group that does not span quadrants (for example, a three-slot redundancy group that spans slots 0, 1, and 2 in an ERX1410 chassis), the potential bandwidth of the redundant module is erroneously included in the quadrant bandwidth calculation. The show utilization command might indicate that the bandwidth is exceeded for modules in that group. [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. 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. 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. Known Behavior 35 JUNOSe 11. 0. 1 Release Notes 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 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 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 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 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. [. . . ]