User manual JUNIPER NETWORKS LN1000 RELEASE NOTES 8-27-2010

[. . . ] LN1000 Mobile Secure Router Release Notes Junos OS 10. 3R1 27 August 2010 These release notes contain information for the LN1000 Mobile Secure Router family of routers running Junos OS Release 10. 3 on the LN1000-V Vita chassis hardware platform. Contents LN1000 Mobile Secure Router Overview . 2 Known Limitations for the LN1000 Router Running Junos OS Release 10. 3 . [. . . ] When you delete and add PPPoE interfaces, syslog reports the following benign error message: PPPoE config - KERN-2: if_pfe: Error 5 (invalid) on IF command 10 (IFD ioctl) · In addition, the following MIB variables are not currently supported on the LN1000: · · · · · · · · · · · · · dot3StatsDuplexMode dot3StatsFramesTooLongs dot3StatasAlignmentErrors dot3StatsInternalMacTransmit dot3StatsInternalMacReceiveErrors dot3StatsCarrierSenseErrors dot3StatsSQETestErrors dot3StatsSingleCollisionFrames dot3StatsMultipleCollisionFrames dot3StatsDeferredTransmissions dot3StatsLateCollisions dot3StatsExcessiveCollisions dot3StatsSymbolErrors 2 Copyright © 2010, Juniper Networks, Inc. Outstanding Issues for the LN1000 Router Running Junos OS Release 10. 3 Outstanding Issues for the LN1000 Router Running Junos OS Release 10. 3 The LN1000 Mobile Secure Router running Junos OS Release 10. 3 has the following outstanding issues: · · PPPoE multicast CoS shaping does not work. [PR/500076] When the router is configured as a PPPoE server, all logical PPP and PPPoE subinterfaces (such as pp0. 1 and pp0. 2) that share the same underlying interface (such as ge-0/0/0. 1) must be configured with the same PPP authentication (for example, PAP, CHAP, RADIUS, or none. ) When a PPP or PPPoE client initiates PPPoE discovery with an underlying interface on the router, the PPPoE server can allocate any of the available logical subinterfaces above that underlying interface for the client. For PPP authentication to succeed following PPPoE discovery, the allocated subinterface on the router must have an authentication configuration that is compatible with the client. Because any subinterface above an underlying interface can be allocated for a client, all such subinterfaces must have the same PPP authentication configuration. [PR/503758] The CoS parameters for an R2CP session are not displayed in the show r2cp session command output until a session update is received from the radio. [PR/508865] Syslog reports the following message [PR/431799]: PPPoE LICENSE_SOCKET_FAILURE: `envConnect' messages on authd, rtlogd · · Workaround: Run the following command from the UNIX shell: sh /etc/rc. license · The output from the CLI show interface statistics command does not show input errors. [PR/434067] The CLI show chassis command does not receive environment information from the IPMC. [PR/446547] The activity and link LEDs on the RTM front panel are always green. [PR/450667] · · Resolved Issues for the LN1000 Router Running Junos OS Release 10. 3 The following issues have been fixed on the LN1000 Mobile Secure Router running Junos OS Release 10. 3: · · VRRP is now supported. When sending traffic at a high rate over PPPoE sessions, the PPPoE sessions no longer flap. [PR/487017] Under some circumstances, the Gigabit Ethernet copper interface may not come up. [PR/471983] · Copyright © 2010, Juniper Networks, Inc. 3 LN1000 Mobile Secure Router Release Notes Documentation and Release Notes For a list of related Junos OS documentation, see http://www. juniper. net/techpubs/software/junos/. If the information in the latest release notes differs from the information in the documentation, follow the LN1000 Release Notes. [. . . ] Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U. S. 5, 473, 599, 5, 905, 725, 5, 909, 440, 6, 192, 051, 6, 333, 650, 6, 359, 479, 6, 406, 312, 6, 429, 706, 6, 459, 579, 6, 493, 347, 6, 538, 518, 6, 538, 899, 6, 552, 918, 6, 567, 902, 6, 578, 186, and 6, 590, 785. 4 Copyright © 2010, Juniper Networks, Inc. [. . . ]