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. 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. [. . . ] 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. 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. 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. 36 Known Problems and Limitations Release 10. 0. 3 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] BFD After you have shut down the interface to the next hop (for the route that is used to establish the BFD session), output for the show bfd session command erroneously indicates the shutdown interface as Management Interface (FastEthernet 6/0). [Defect ID 174271] Bridged Ethernet The CLI erroneously permits you to configure bridge1483 encapsulation over AAL5MUX IP even though that configuration is not supported. [Defect ID 35013] CLI When you issue a run show ppp command, the CLI changes the configuration level of the command line to Global Configuration mode rather than remaining at the level from which you issued the command. [Defect ID 52165] Work-around: Reissue the commands necessary to reenter the desired mode. The logout subscribers all command may not log out all of the DHCP subscribers. Although the bindings and DHCP addresses are cleared, the show subscribers summary command may display some of the DHCP subscribers. [Defect ID 180176] Work-around: Try using the dhcp delete-binding all command. If this does not clear the subscribers, you may want to reload the line module to avoid further issues. You cannot paste a load-rebalance command string that uses the percent option into a console or Telnet session from show configuration output because the output displays the % sign rather than the percent keyword that was submitted with the command and the percent sign is not recognized by the CLI. [Defect ID 81705] DHCP DHCP NAK packets are sent from a different VLAN than the one on which the renew request is received on a router that is configured with dynamic VLANs, DHCP local server, and automatically created dynamic subscriber interfaces. This behavior occurs only after a link flap has taken place. [Defect ID 87062] DHCP packets are not forwarded to the DHCP server over dynamically created interfaces when all of the following are true: [Defect ID 180343] DHCP relay or DHCP relay proxy is configured on the router. [. . . ] 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. [. . . ]