User manual JUNIPER NETWORKS JUNOSE 11.0.2 RELEASE NOTES

[. . . ] JunosETM Software for E SeriesTM Broadband Services Routers Release Notes Release 11. 0. 2 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www. juniper. net Published: 2010-11-09 Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. The Juniper Networks Logo, the Junos logo, and JunosE are 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. [. . . ] [Defect ID 80378] Work-around: To ensure low strict-priority latency, shape the port rate to no more than 148. 5 Mbps. 32 Known Behavior Release 11. 0. 2 An error message regarding the qos-parameter instance QosParameterDefinition is erroneously generated on an ERX1440 router when it is configured for L2C and QoS RAM and receives TLV 144 (DSL Type). [Defect ID 80620] On the E120 and E320 routers, you cannot attach QoS profiles to L2TP tunnels by means of the CLI because the CLI does not pass the router ID to QoS. [Defect ID 81516] PPP sessions may be dropped if you change the shaping rate in a QoS profile that affects thousands of circuits while QoS traffic affected by the profile is being forwarded. [Defect ID 82950] Work-around: Do not change the shaping rate in a QoS profile that affects thousands of circuits while QoS traffic is using the profile. Egress traffic may be dropped on OC12/STM4 ATM interfaces if you have shaped the port rate to more than 542 Mbps. [Defect ID 83785] Work-around: Do not exceed a shaped port rate of 542 Mbps. Incorrect output is sent to the CLI the first time you enter Global Configuration mode or issue the show subscribers command after viewing the VLAN subinterface over which a subscriber is connected. [Defect ID 84507] RADIUS JunosE Software provides extended commands for configuring the formats of the RADIUS NAS-Port attribute (attribute 5) and the RADIUS Calling-Station-ID attribute (attribute 31) when the physical port value is greater than 7. When the physical port value is greater than 7: An incorrectly configured NAS-Port attribute format results if you use either the radius nas-port-format 0ssssppp or radius nas-port-format ssss0ppp command. An incorrectly configured Calling-Station-ID attribute results if you use either the radius calling-station-format fixed-format command or the radius calling-station-format fixed-format-adapter-embedded command. Work-around: Use the following commands on routers that have line modules with more than 7 physical ports: To configure the NAS-Port attribute format, use the radius nas-port-format extended [ atm | ethernet ] command. To configure the Calling-Station-ID attribute format, use the radius calling-station-format fixed-format-adapter-new-field command. Known Behavior 33 JunosE 11. 0. 2 Release Notes SNMP SNMP MIBs Information about all the SNMP MIBs (both standard and proprietary) that the router supports in this release is available in the MIB directory in the SW_Image_CD-2 folder of the JunosE Software image bundle, which you downloaded from the Juniper Networks website, that contains the release file for E120 and E320 routers. Some Juniper Networks SNMPv1-formatted traps contain an incorrect object identifier (OID) in the SNMPv1-Trap-PDU enterprise field. An SNMPv2 trap is typically identified by an OID that ends in the form . . . x. y. z. 0. n. This OID appears, in full, as the value of the snmpTrapOID. 0 object in the varbind list of an SNMPv2-formatted trap. In the corresponding SNMPv1-formatted trap, this OID is broken down into subcomponents that fill the SNMPv1-Trap-PDU enterprise field (. . . x. y. z) and specific trap number field (n); the zero is unused. The SNMPv1-formatted versions of the following Juniper Networks traps incorrectly contain . . . x. y. z. 0 in the SNMPv1-Trap-PDU enterprise field. That is, a zero is mistakenly appended to the correct enterprise OID value. Trap Name junidApsEventSwitchover junidApsEventModeMismatch junidApsEventChannelMismatch junidApsEventPSBF junidApsEventFEPLF juniAddressPoolHighAddrUtil juniAddressPoolAbatedAddrUtil juniAddressPoolNoAddresses juniDhcpLocalServerPoolHighAddrUtil juniDhcpLocalServerPoolAbatedAddrUtil juniDhcpLocalServerPoolNoAddresses pimNeighborLoss Expected Enterprise OID . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3 . 1. 3. 6. 1. 3. 61. 1 Enterprise OID Sent by SNMP Agent . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 3. 2. 2. 1. 2. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 21. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 4. 1. 4874. 2. 2. 22. 3. 0 . 1. 3. 6. 1. 3. 61. 1. 0 Work-around: Use the OIDs that the SNMP agent sends. When you configure the router with an address pool that has two IP address ranges, only the range that you configured first is available via the MIB. [Defect ID 61232] 34 Known Behavior Release 11. 0. 2 SRC Software and SDX Software The SRC client does not prevent you from changing the name of the router while the client is connected to the SAE, resulting in SAE issues such as lost IP addresses and stale users. [Defect ID 77102] Work-around: To change the router name while the SRC client is connected to the SAE, shut down the SRC client, change the name, then re-enable the SRC client. SSH If the SRP module restarts when SSH is configured in a VR other than default, SSH can sometimes become disabled. This happens if SSH attempts to bind with a VR before the VR comes back up after the restart. [. . . ] These values are subject to limitations on available SRP module memory, which varies according to your router configuration. Depending on your configuration, the router may support more routing table entries or fewer routing table entries than this value. In any case, you can choose to limit the number of routes that can be added to the routing table on a per-VR or per-VRF basis by means of the maximum routes command. The maximum number of ANCP adjacencies can be scaled over a maximum of 100 virtual routers. [. . . ]