1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE 10.3.1 - S 3-19-2010
  6. Release note

Juniper JUNOSE 10.3.1 - RELEASE NOTES 3-19-2010 Release Note

For e series broadband services routers
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
JUNOSe
Software
™
for E Series
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

Advertisement

Table of Contents
loading

Related Manuals for Juniper JUNOSE 10.3.1 - RELEASE NOTES 3-19-2010

Summary of Contents for Juniper JUNOSE 10.3.1 - RELEASE NOTES 3-19-2010

  • Page 1: Release Notes

    JUNOSe Software ™ for E Series Broadband Services Routers ™ Release Notes Release 10.3.1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-03-19...
  • Page 2 SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use...
  • Page 3 The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any commercial network access services. The foregoing license is not transferable or assignable by Customer.
  • Page 4 Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html.

  • Page 5: Table Of Contents

    Table of Contents Release 10.3.1 Release Installation ..................1 Upgrading to Release 5.3.0 or a Higher-Numbered Release ....... 1 Upgrading from Release 5.1.1 or Lower-Numbered Releases to Release 6.x.x or Higher-Numbered Releases ........2 Moving Line Modules Between Releases ............ 2 SRP Module Memory Requirements ............
  • Page 6 JUNOSe 10.3.1 Release Notes Hardware ....................20 HDLC....................... 21 IP......................21 IPSec ....................... 23 IS-IS ......................23 L2TP ......................24 Line Module Redundancy ................ 24 MLPPP..................... 25 MPLS ....................... 25 Multicast....................25 Packet Mirroring ..................26 Policy Management ................. 26 PPP......................
  • Page 7 Table of Contents Subscriber Management ................49 System ....................50 System Logging ..................50 TCP ......................50 Unified ISSU .................... 50 Resolved Known Problems ................52 AAA ......................52 ARP ......................52 ATM......................52 BFD ......................52 CLI......................53 DHCP ...................... 53 DHCP External Server................
  • Page 8 JUNOSe 10.3.1 Release Notes Tunneling Maximums................105 Subscriber Management Maximums............107 Appendix B Transferring DSL Line Rate Information from an Access Node to SRC Software Configuring the SRC Client to Retrieve DSL Information from Access Nodes..................109 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the COPS Server ..................112 JUNOSe Command Reference Guide Update ..........113 sscc update-policy-request enable ..............113...

  • Page 9: Release 10.3.1

    Complete procedures for installing the system software are available in JUNOSe System Basics Configuration Guide, Chapter 3, Installing JUNOSe Software. New software releases are available for download from the Juniper Networks website at http://www.juniper.net/customers/support. You can use the downloaded image bundle to create your own software CDs.

  • Page 10: Upgrading From Release 5.1.1 Or Lower-Numbered Releases To Release 6.X.x Or Higher-Numbered Releases

    8, Maintaining the Router Moving Line Modules Between Releases The Juniper Networks ERX1440 Broadband Services Router employs a 40-Gbps SRP module and a new midplane. Release 3.3.2 was the first software release to support the 40-Gbps SRP module and midplane. Before you can transfer a compatible line module from a Juniper Networks ERX705, ERX710, or ERX1410 Broadband Services Router to an ERX1440 router, you must first load Release 3.3.2 or a higher...

  • Page 11: Srp Module Memory Requirements

    7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:...

  • Page 12: Opening A Case With Jtac

    Download the latest versions of software and review release notes: http://www.juniper.net/customers/csc/software/ Search technical bulletins for relevant hardware and software notifications: https://www.juniper.net/alerts/ Join and participate in the Juniper Networks Community Forum: http://www.juniper.net/company/communities/ Open a case online in the CSC Case Manager: http://www.juniper.net/cm/...

  • Page 13: Before You Start

    The 10.3.x documentation set consists of several manuals and is available only in electronic format. You can print your own documentation using the PDF and HTML formats available at the Juniper Networks Technical Documentation Web site at www.juniper.net/techpubs. Refer to the following table to help you decide which document to use.
  • Page 14 JUNOSe 10.3.1 Release Notes Task Document Configure line module redundancy, JUNOSe Service Availability Configuration Guide stateful SRP switchover, unified ISSU, VRRP, and interchassis redundancy (ICR) Configure IP, IPv6 and Neighbor JUNOSe IP, IPv6, and IGP Configuration Guide Discovery, and interior gateway protocols (RIP, OSPF, and IS-IS) Configure IP routing services, JUNOSe IP Services Configuration Guide...

  • Page 15: Release Highlights

    The features described in this section are present in the code but have not yet been fully qualified by Juniper Networks. These features are available only for field test purposes in this release. If you use any of these features before they have been fully qualified, it is your responsibility to ensure that the feature operates correctly in your targeted configuration.

  • Page 16: Sdx Software And Src Software

    The JUNOSe Release 10.3.x documentation set describes some features that are present in the code but that have not yet been fully qualified by Juniper Networks. If you use any of these features before they have been fully qualified, it is your responsibility to ensure that the feature operates correctly in your targeted configuration.

  • Page 17: Multicast

    Release 10.3.1 Subscriber Interfaces on the ES2 10G Uplink LM You can configure dynamic subscriber interfaces and static subscriber interfaces on the ES2 10G Uplink LM using the CLI. However, configuring subscriber interfaces on the ES2 10G Uplink LM provides no benefit because access features such as per-subscriber QoS are unavailable on the module.

  • Page 18: Network Management Protocols

    JUNOSe 10.3.1 Release Notes User Datagram Protocol (UDP) for IPv4 and IPv6 Network Management Protocols Simple Network Management Protocol (SNMP) versions 1, 2c, and 3 Routing Protocols Border Gateway Protocol (BGP-4) Distance Vector Multicast Routing Protocol (DVMRP) Internet Group Membership Protocol (IGMP) Intermediate System–to–Intermediate System (IS-IS) Layer 2 Virtual Private Networks (L2VPNs) Mobile IP...

  • Page 19: Security Protocols

    Release 10.3.1 Layer 2 Tunneling Protocol (L2TP) Multilink Frame Relay (MLFR) Multilink Point-to-Point Protocol (MLPPP) Packet over SONET (POS) Point-to-Point Protocol (PPP) PPP over Ethernet (PPPoE) Transparent bridging Security Protocols Internet Key Exchange (IKE) Internet Security Association and Key Management Protocol (ISAKMP) IP Authentication Header (AH) IP Encapsulating Security Payload (ESP) Network Address Translation (NAT)

  • Page 20: Known Behavior

    IPv6 address in the next-hop field on a directly connected external BGP peering. Work-around: Enable EBGP multihop configuration on the remote (non–Juniper Networks) peer. The following message might be displayed under certain conditions: bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting...

  • Page 21: Bgp/Mpls Vpns

    Release 10.3.1 If a valid route exists in the routing table, the following message is displayed when an unconfigured peer attempts to establish a TCP session with an E Series router; X.X.X.X is the source address of the unconfigured peer: NOTICE 08/29/2001 16:50:11 bgpConnections (default,X.X.X.X): Inbound connection refused - no peer X.X.X.X configured in core BGP/MPLS VPNs...
  • Page 22 JUNOSe 10.3.1 Release Notes Deprecated Command Command Mode Preferred Command color Policy List Configuration color in Classifier Group Configuration mode controller e1 Global Configuration controller t1 Global Configuration description Interface Configuration ip description Still available in Controller Configuration and VRF Configuration modes Controller Configuration fdl carrier...
  • Page 23 Release 10.3.1 Deprecated Command Command Mode Preferred Command [ no ] ipsec isakmp-policy rule Global Configuration [ no ] ipsec ike-policy-rule ipv6 policy local-input Interface Configuration, None Profile Configuration Controller Configuration license l2tp-session Global Configuration None lineCoding Controller Configuration Policy List Configuration log in Classifier Group Configuration mode log severity debug...
  • Page 24 JUNOSe 10.3.1 Release Notes Deprecated Command Command Mode Preferred Command rate-limit-profile Policy List Configuration rate-limit-profile in Classifier Group Configuration mode remote-loopback Controller Configuration show controllers t1/e1 User Exec, Privileged Exec show controllers t1 remote User Exec, Privileged Exec show ike certificates User Exec, Privileged Exec show ipsec certificates show ike configuration...

  • Page 25: Dhcp

    Release 10.3.1 The show configuration command normally takes a long time to finish for extremely large configurations. If you specify a search string (with the begin, exclude, or include options) with the command for a string that is not present in the configuration, then the CLI session appears to be busy for a prolonged period.

  • Page 26: Dynamic Interfaces

    JUNOSe 10.3.1 Release Notes Release 9.0.1 and all 9.0.1 patch releases Release 9.1.0 and all 9.1.0 patch releases If you are upgrading the JUNOSe Software on the router from any of these releases, you must explicitly issue the ip dhcp-external recreate-subscriber-interface command to configure the router to continue to delete and re-create the DHCP client’s dynamic subscriber interface.

  • Page 27: Ethernet

    Release 10.3.1 Ethernet The hashing algorithm that selects the LAG member link is associated with the IP address of the subscriber client to support QoS. Consequently, a particular flow is always hashed to the same link. When a member link is removed from a LAG bundle, traffic rate is disrupted and traffic flow is reduced.

  • Page 28: Flash

    JUNOSe 10.3.1 Release Notes Primary/Secondary link signal detected Primary/Secondary link signal not detected Flash Flash cards manufactured by Wintec are present on some currently deployed routers. When you upgrade the JUNOSe Software on such routers, the firmware on the flash card controller is automatically updated during diagnostics. During this reboot, the software runs an integrity check on the file system to verify that the firmware update did not corrupt the contents of the flash card.

  • Page 29: Hdlc

    Release 10.3.1 When you configure 1:5 line module redundancy by using either the 4XOC3 APS MULTIMODE or 4XOC3 APS SINGLE MODE I/O module, the spare R-Mid OCX I/O module you install must have assembly number 350-00094-01 Rev. A01 or later. Spare R-Mid OCX I/O modules with an earlier assembly number are not supported for 1:5 redundancy configurations that use either the 4XOC3 APS MULTIMODE or 4XOC3 APS SINGLE MODE I/O module.
  • Page 30 JUNOSe 10.3.1 Release Notes host1(config)#ip vrf 123 host1(config-vrf)#description longdescription Work-around: Before you upgrade from an affected release to JUNOSe Release 9.2.0p1-0 or higher-numbered releases, ensure that you do the following: Change IP interface and subinterface descriptions to 9 or more characters. Change VRF descriptions, VRF names, or both so that the combination of associated VRF names and descriptions consists of 9 or more characters.

  • Page 31: Ipsec

    Release 10.3.1 host1(config-if)#ip share-interface FastEthernet 3/0.2 % No such interface Unnumbered interfaces that refer to nonloopback interfaces (for example, ip unnumbered fastEthernet 3/0.2) and that appear in the show configuration output before the interface referred to might generate similar no such interface errors. Work-around: Run the script twice.

  • Page 32: L2Tp

    JUNOSe 10.3.1 Release Notes Work-around: To ensure proper election of the DIS when you configure IS-IS over bridged Ethernet for back-to-back VRs, we recommend that you use the isis network point-to-point command in Interface Configuration mode to configure IS-IS to operate using point-to-point (P2P) connections on a broadcast circuit when only two routers (or, in this case, two VRs) are on the circuit.

  • Page 33: Mlppp

    User Exec and Privileged Exec modes respectively. These commands are intended to be used in a Juniper Networks internal lab environment for testing without a traffic generator. Do not configure a multicast group with more than 10,219 outgoing interfaces (OIFS) on the same ES2 10G LM.

  • Page 34: Packet Mirroring

    JUNOSe 10.3.1 Release Notes Packet Mirroring The ES2 10G LM supports the packet mirroring feature when the module is paired with the ES2-S2 10GE PR IOA, the ES2-S1 GE-8 IOA, or the ES2-S3 GE-20 IOA. When you use the ES2 10G LM with these IOAs, CLI-based interface-specific mirroring is not supported.
  • Page 35 Release 10.3.1 If multiple forward or filter rules were configured to reference the same classifier list in a single policy, then all rules except the first rule configured were marked as eclipsed in the show policy command display. Next-interface and next-hop rules were treated in the same manner.

  • Page 36: Ppp

    JUNOSe 10.3.1 Release Notes NOTE: When you upgrade the nonvolatile memory to Release 5.2.0 or later, the upgrade removes eclipsed rules and rules whose behavior was not applied in the previous release. This removal ensures that the postupgrade forwarding behavior is the same as the preupgrade behavior.

  • Page 37: Radius

    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. .

  • Page 38: Ssh

    JUNOSe 10.3.1 Release Notes 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.
  • Page 39 Release 10.3.1 We have ongoing development activities to characterize and improve call setup rates in future releases. Stateful SRP switchover remains inactive for 20 minutes after an initial cold-start or cold-restart of the router. This delay enables the system to reach a stable configuration before starting stateful SRP switchover.

  • Page 40: Subscriber Interfaces

    JUNOSe 10.3.1 Release Notes Subscriber Interfaces MAC address validation is not supported on either of the following: Packet-triggered subscriber interfaces that are created dynamically Packet-triggered subscriber interfaces that are managed on the primary IP interface A packet-triggered subscriber interface is created when the router receives a packet with an IP source address that does not match any entries in the demultiplexer table.

  • Page 41: System Logging

    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.

  • Page 42: Known Problems And Limitations

    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.

  • Page 43: Bfd

    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.

  • Page 44: Bridged Ethernet

    JUNOSe 10.3.1 Release Notes Bridged Ethernet The CLI erroneously permits you to configure bridge1483 encapsulation over AAL5MUX IP even though that configuration is not supported. [Defect ID 35013] 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.

  • Page 45: Dos Protection

    Release 10.3.1 The DHCP renew counter and release counter (displayed with the show ip dhcp-external statistics command) are doubled rather than incremented for each renew and release sent. [Defect ID 78802] When DHCP clients on an S-VLAN over bridged Ethernet stack configuration send a decline message to a router that has DHCP relay and DHCP external server configured in the same VR, the clients bindings are not removed from the DHCP external server.
  • Page 46 JUNOSe 10.3.1 Release Notes When performing MAC validation to match subscriber demux entries with ARP host entries, the ES2 10G LM does an exact match, rather than a longest prefix match. The subscriber demux entry source address must be a /32 value matching the IP address of an ARP entry in order to validate the MAC address against that ARP entry.

  • Page 47: Icr

    Release 10.3.1 Ethernet statistics are incorrectly displayed for virtual port 8 of the ES2-S1 GE-8 IOA when that module is paired with the ES2 10G LM or the ES2 10G Uplink LM. [Defect ID 174784] The ES2 10G LM does not support framed routes configured for dynamic subscriber interfaces.
  • Page 48 JUNOSe 10.3.1 Release Notes When more than about 100,000 mapped OIF entries are configured on a virtual router, issuing the no virtual router command for this and other virtual routers does not delete all the virtual routers within the deletion timeout interval (3 minutes).

  • Page 49: Ipsec

    Release 10.3.1 When you change the demultiplexer type on a primary interface that has 1024 demultiplexer table entries, the ICC ping threshold times out due to the removal of the old entries and the addition of the new ones. [Defect ID 182218] After an SRP stateful switchover completes on an ERX1410 router configured with a single VPN routing and forwarding instance (VRF) and Network Address...

  • Page 50: Mld

    JUNOSe 10.3.1 Release Notes MLDv2 proxy is not supported. [Defect ID 46038] The E Series router MLDv2 proxy does not operate correctly in the presence of MLDv1 queriers. [Defect ID 46039/46045] Work-around: If an MLDv1 router is present on the network, configure version 1 with the ipv6 mld-proxy version command on that network interface.

  • Page 51: Mpls

    Release 10.3.1 When mobility bindings are present and you delete the Mobile IP home agent with the no virtual router command, Mobile IP sends a RADIUS Acct-Stop message with no accounting statistics for the subscribers. [Defect ID 179081] Work-around: Issue the clear ip mobile binding all command before you issue the no virtual router command.

  • Page 52: Netflow

    JUNOSe 10.3.1 Release Notes Netflow Flow sampling stops after a cold switchover on a router that is configured with 16 VRs and 32 interfaces per VR, when all flows are passing through the configuration (32 flows per VR). [Defect ID 74477] Work-around: After the cold switchover is completed, reissue the ip flow-sampling-mode packet-interval 10 command on each VR, even though the command is present in the configuration.

  • Page 53: Pppoe

    Release 10.3.1 On E320 line modules that support secure policies, the SRP module enables you to configure more than 1022 secure policies per module. [Defect ID 175756/180360] Work-around: To avoid potential performance issues, we recommend that you do not configure more than 1022 secure policies per module. Unified in-service software upgrade (unified ISSU) is not supported on an E120 or E320 router if a hierarchical policy is attached to an external parent group.
  • Page 54 JUNOSe 10.3.1 Release Notes The compound shared shaping feature does not work properly on egress forwarding ASIC 2 (EFA2)-based ATM line modules when the shared shaper is queue-controlled as opposed to node-controlled. In a node-controlled configuration, in which you configure the shared-shaping rate on the best-effort scheduler node for the logical interface, integration of the EFA2 and ATM segmentation and reassembly (SAR) schedulers functions properly.

  • Page 55: Service Manager

    Release 10.3.1 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] When QoS resources such as failure nodes and statistics bins are exhausted because of insufficient memory available on the line module, the failures are properly logged, but additional log messages are generated every 10 minutes that report zero failures.

  • Page 56: Sonet

    JUNOSe 10.3.1 Release Notes SONET You cannot use the highest sensitivity bit-error rate setting (a value of 9) associated with APS/MSP alarm when you issue the threshold sd-ber command to configure a cOCx/STMx line module with cOC12-APS-capable IOAs. [Defect ID 72861] Work-around: Use only a value in the range 5–8 when you issue the threshold sd-ber command for this module combination, as in the following example: host1(config)#controller sonet 2/1...

  • Page 57: Subscriber Management

    Release 10.3.1 When you use the ping command with the IPv6 address of the helper router in the broadcast network as the destination address and no source address when stateful SRP switchover is performed the first time, an identical packet loss occurs. In this case too, no packet loss occurs during subsequent switchovers.

  • Page 58: System

    JUNOSe 10.3.1 Release Notes Work-around: Use the no interface ip ipAddress command to remove the dynamic subscriber interfaces. Although you can use the dhcp delete-binding command to remove the DHCP binding and the dynamic subscriber interfaces, the DHCP client does not detect the binding removal and retains the lease. System You cannot use a configuration script to boot the E320 router.
  • Page 59 Release 10.3.1 When any of the subsystems is excluded for a JUNOSe release, a unified ISSU to that release fails to apply conversion code to all of the line modules. As a result, the line modules reset when they come up with that release. [Defect ID 179595] Work-around: To prevent the exclusion of a subsystem file from the release, do the following before you upgrade to a new JUNOSe release that supports...

  • Page 60: Resolved Known Problems

    JUNOSe 10.3.1 Release Notes Resolved Known Problems The following problems were reported open in Release 10.3.0 and have been resolved in this release. For more information about particular resolved problems, 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.

  • Page 61: Cli

    Release 10.3.1 SIT_11.0.0b0-6: SRP Crash: reset type: panic arg (0x6) file: osPool.cc line: 1290 task: IpSubscriberMana [Defect ID 184506] When you attempt to access the router through telnet or the CLI, the router is unavailable. However, the router responds to SNMP messages. [Defect ID 82970] SRP crash: reset type: exception 0x300 (data access: protection violation (write attempt))task: telC42083 [Defect ID 73380]...

  • Page 62: Dhcp Relay

    JUNOSe 10.3.1 Release Notes DHCP Relay SRP crash - reset type: panic task: dhcpRelay_dhcpRe file: dhcpRelay.cc line: 11249 [Defect ID 90123] DoS-protection-group configuration for IpLocalLspPing is not working as expected. [Defect ID 88877] Ethernet When you remove the IP address of a LAG bundle on an ES2 10G LM or an ES2 10G ADV LM, which is configured with a Gigabit Ethernet physical interface as the member interface and assigned an IP address and subnet mask, the line module resets during the time of deletion of the IP address.

  • Page 63: Hardware

    Release 10.3.1 After the LAG member link flaps VLAN subinterfaces are not created on ES2 10G LM LAG in the svlan-range in the bulk configuration. [Defect ID 89708] Create a mechanism to detect invalid op-code for SRAM errors and log it. [Defect ID 89878] Few COA-ACK packets sent from the ERX router are missing under control-plane load.

  • Page 64: Http Server

    JUNOSe 10.3.1 Release Notes The ERX router did not respond to ingress L2TP control packets during warm-restart. [Defect ID 89751] Implement credit based mechansim for Global recirculation SRA panic. [Defect ID 89877] SN for fan in show hard not updated when fan is swapped. [Defect ID 90008] LM10A experiencing memory leak in memory pool LuCodeBranch on LM10.

  • Page 65: Ipv6

    Release 10.3.1 IPv6 When an IPv6 client that is connected to the requesting router using a PPP link is delegated a prefix by the DHCPv6 server, the client binding is not removed when the PPP session terminates and is retained until the lease time expires. As a result, when the same PPP client logs in again and sends a DHCPv6 SOLICIT request to the DHCPv6 server, the SOLICIT request is ignored if the prefix or the local address pool returned by the RADIUS server is different from...

  • Page 66: Pppoe

    JUNOSe 10.3.1 Release Notes PPPoE Old PPPoE subinterfaces cause subscriber connectivity problem. [Defect ID 89681] When you connect a PPPoE subscriber and then shutdown the interface from the CLI, PPPoE lockout is not activated on the server. Instead if you first log out the subscriber from the server using the logout subscriber command, PPPoE lockout is activated.

  • Page 67: Rsvp-Te

    Release 10.3.1 ‘bad if’ logs reported when QoS Agent checks for L2TP client interface type [Defect ID 89711] Unable to display scheduler hierarchy or egress-queue rate for LM4 tunnel server ports. [Defect ID 89692] ES2 10G LM in slot 0 crashed - reset type: panic arg (0xda) file: templateRam.cc line: 305 [Defect ID 90093] QoS has a limit of 4 Gbps on tenGigabitEthernet interface for maximum rate.

  • Page 68: System Logging

    JUNOSe 10.3.1 Release Notes SRP Reset: exception 0x300 task: sssClient_Data_1 pc: SssClient::ReportStateMessage::append(...) [Defect ID 90043] SRP reset type: processor exception 0x300; task: sssClient_Data_2 [Defect ID 90218] System Logging After stateful SRP switchover, the source of the syslog messages stored on the syslog server erroneously displays the IP address of the uplink interface instead of the IP address of the configured loopback interface.

  • Page 69: Errata

    Release 10.3.1 Errata This section identifies errors found in the JUNOSe documentation. These errors are corrected in subsequent releases of the affected documentation. The Link Layer Maximums table (for the E120 and E320 routers) in Appendix A, System Maximums, of the JUNOSe Release Notes, for the following releases incorrectly stated that the maximum number of Ethernet S-VLANs per ES2-S2 10GE PR IOA with an ES2 10G LM or ES2 10G Uplink LM was 32,768: Releases 10.2.0 and 10.2.1...
  • Page 70 JUNOSe 10.3.1 Release Notes The General System Maximums table (for the ERX310, ERX7xx, and ERX14xx routers) in Appendix A, System Maximums, of the JUNOSe Release Notes, for the following releases incorrectly mentioned that the maximum number of SRC interfaces supported on all the ERX routers was 48,000: Releases 9.0.0, 9.0.1, and 9.0.2 Releases 9.1.0, 9.1.1, and 9.1.2 Releases 9.2.0 and 9.2.1...
  • Page 71 Release 10.3.1 The subscriber broadcasts a PPPoE Active Discovery Initiation (PADI) packet to both the master and backup router. Only the master router processes the packet and creates the subscriber session. When the master router fails, VRRP switchover occurs and the backup router becomes the new master router. PPPoE data that now shows up on the new master is dropped because a session was not created for the subscriber on the new master.
  • Page 72 JUNOSe 10.3.1 Release Notes The DHCP Affected Behaviors section in JUNOSe Service Availability Configuration Guide, Chapter 4, Configuring a Unified In-Service Software Upgrade, incorrectly contains the DHCP Relay and DHCP Relay Proxy Prevent Unified ISSU subsection, which indicates that the DHCP relay and DHCP relay proxy applications do not support unified ISSU.
  • Page 73 Release 10.3.1 master—Displays the total number of master ICR partitions configured on the router summary—Displays a summary of all ICR partitions configured on the router filer—Displays a filtered output using a combination of | (the UNIX pipe symbol), defined keywords, and a text string or regular expression The tables in the Interface Types and Specifiers section of Chapter 1, Command Refrence Topics, in the JUNOSe Command Reference Guide erroneously state that the maximum number of PPPoE subinterfaces per Ethernet (GE/FE) line...
  • Page 74 JUNOSe 10.3.1 Release Notes Errata...

  • Page 75: Appendix A System Maximums

    For some entries, early field trial (EFT) values are presented in addition to supported values. These values have not been fully qualified by Juniper Networks and are mentioned only for field test purposes in this release. EFT values are enclosed within parentheses with an EFT designation;...

  • Page 76: Erx310, Erx7Xx, And Erx14Xx System Maximums

    JUNOSe 10.3.1 Release Notes ERX310, ERX7xx, and ERX14xx System Maximums The following tables provide system maximums for the ERX310, ERX7xx, and ERX14xx routers. General System Maximums Table 1 lists some general system maximums for the ERX routers. Table 1: General System Maximums ERX705 and Feature ERX310...

  • Page 77: Physical And Logical Density Maximums

    Appendix A: System Maximums Physical and Logical Density Maximums Table 2 lists physical and logical density maximums for the ERX routers. The following notes are referred to in Table 2: 1. Wire rate indicates the port density that supports maximum (wire-rate) performance.
  • Page 78 JUNOSe 10.3.1 Release Notes Table 2: Physical and Logical Density Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Fast Ethernet (10/100) ports per chassis 32/40 32/96 (FE-8 I/O and FE-8 SFP I/O modules) Gigabit Ethernet ports per chassis 4/12 (GE I/O modules) Gigabit Ethernet ports per chassis –...
  • Page 79 Appendix A: System Maximums Table 2: Physical and Logical Density Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Logical density per chassis Logical E1s per chassis 1260 3024 3024 Logical E3s per chassis Logical fractional E1s (DS0) per chassis 4000 10,000 24,000...

  • Page 80: Link Layer Maximums

    JUNOSe 10.3.1 Release Notes Link Layer Maximums Table 3 lists link layer maximums for the ERX routers. The following notes are referred to in Table 3: 1. The ERX1440 router supports a maximum of 48,000 interface columns of all types combined. You can use either all dynamic interfaces or a combination of dynamic and static interfaces to achieve this maximum.
  • Page 81 Appendix A: System Maximums Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 ATM bulk configuration overriding profile assignments per chassis ATM VCs per chassis (active/configured) 16,000/32,000 32,000/64,000 32,000/64,000 48,000/96,000 ATM VCs per line module OCx/STMx/DS3-ATM (active/configured) 8000/16,000 8000/16,000 8000/16,000...
  • Page 82 JUNOSe 10.3.1 Release Notes Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Ethernet S-VLANs per I/O module FE-8 I/O and FE-8 SFP I/O 16,384 16,384 16,384 16,384 GE I/O 16,384 16,384 16,384 16,384 GE-2 SFP I/O 16,384 –...
  • Page 83 Appendix A: System Maximums Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 HDLC interfaces per chassis 4000 10,000 24,000 24,000 HDLC interfaces per line module COCX-F3 cOCx/STMx F0 2000 2000 2000 2000 CT3/T3 F0 1992 1992 1992 1992...
  • Page 84 JUNOSe 10.3.1 Release Notes Table 3: Link Layer Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 PPP packet logging Aggregate dynamic and static PPP interfaces for which you can log PPP packets per chassis PPPoE service name tables PPPoE service name tables per chassis Service name tags per PPPoE service name table (including one empty service name tag) PPPoE subinterfaces...

  • Page 85: Routing Protocol Maximums

    Appendix A: System Maximums Routing Protocol Maximums Table 4 lists routing protocol maximums for the ERX routers. The following notes are referred to in Table 4: 1. The total set of FTEs can be shared by interfaces, next hops, ECMP sets, VRs, and VRFs.
  • Page 86 JUNOSe 10.3.1 Release Notes 10. Dynamic values represent typical limits that vary depending on configuration details and actual dynamic behavior. For dynamic values only, multiple server modules (SMs) in a chassis can improve the values as long as the multiple server modules are online and the number of virtual routers configured with NAT is greater than or equal to the number of server modules.
  • Page 87 Appendix A: System Maximums Table 4: Routing Protocol Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 IS-IS adjacencies IS-IS routes 20,000 20,000 20,000 20,000 MPLS LDP LSPs 10,000 10,000 10,000 10,000 MPLS RSVP-TE LSPs 10,000 10,000 10,000 10,000 OSPF adjacencies 1000 1000 1000...
  • Page 88 JUNOSe 10.3.1 Release Notes Table 4: Routing Protocol Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Response Time Reporter simultaneous operations per VR VRRP VRIDs per line module ASIC See Ethernet VRRP VRIDs per line module ASIC on page 74. ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 89: Policy And Qos Maximums

    Appendix A: System Maximums Policy and QoS Maximums Table 5 lists policy and QoS maximums for the ERX routers. The following notes are referred to in Table 5: 1. The OC48 line module supports only 131,071 entries. The GE-2 and GE-HDE line modules support only 65,535 entries.
  • Page 90 JUNOSe 10.3.1 Release Notes Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 CAM entries (See Note 3 on page 81.) GE-2 64,000 – – 64,000 GE-HDE 64,000 – – 64,000 OC48/STM16 – – – 128,000 Policy egress interface attachments per ASIC line module...
  • Page 91 Appendix A: System Maximums Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Secure policies (for packet mirroring) Per ASIC line module 1022 1022 1022 1022 Per chassis 2400 2400 2400 2400 ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 92: Tunneling Maximums

    JUNOSe 10.3.1 Release Notes Tunneling Maximums Table 6 lists tunneling maximums for the ERX routers. The following notes are referred to in Table 6: 1. The SM supports any combination of DVMRP, GRE, and L2TP tunnels up to a maximum of 8000 tunnels; however, no more than 4000 tunnels can be DVMRP or GRE tunnels in any combination.
  • Page 93 Appendix A: System Maximums Table 6: Tunneling Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 IPSec tunnels per IPSec Service Module 5000 5000 5000 5000 L2TP sessions per chassis 16,000 16,000 16,000 32,000 (See Notes 2 and 3 on page 84.) L2TP sessions per line module (See Notes 1 and 3 on page 84.) GE-2 with shared tunnel-server ports provisioned...

  • Page 94: Subscriber Management Maximums

    JUNOSe 10.3.1 Release Notes Subscriber Management Maximums Table 7 lists subscriber management maximums for the ERX routers. The following notes are referred to in Table 7: 1. DHCP relay proxy maintains a list of active DHCP clients up to a maximum of 100,000 clients per chassis for all virtual routers.
  • Page 95 Appendix A: System Maximums Table 7: Subscriber Management Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 DHCPv6 local server Clients 32,000 32,000 32,000 32,000 (See Note 3 on page 86.) DHCP relay and relay proxy client (See Notes 1 and 2 on page 86.) DHCP client host routes for DHCP relay and DHCP relay 100,000 100,000...
  • Page 96 JUNOSe 10.3.1 Release Notes Table 7: Subscriber Management Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Subscriber interfaces (See Note 2 on page 86.) Dynamic subscriber interfaces per chassis 16,000 32,000 32,000 48,000 Dynamic subscriber interfaces per line module 8000 8000 8000...

  • Page 97: E120 And E320 System Maximums

    Appendix A: System Maximums E120 and E320 System Maximums The following tables provide system maximums for the E120 router and the E320 router. General System Maximums Table 8 lists some general system maximums for the E120 router and the E320 router.

  • Page 98: Physical And Logical Density Maximums

    JUNOSe 10.3.1 Release Notes Physical and Logical Density Maximums Table 9 lists physical and logical density maximums for the E120 router and the E320 router. The following notes are referred to in Table 9: 1. Wire rate indicates the port density that supports maximum (wire-rate) performance.
  • Page 99 Appendix A: System Maximums Table 9: Physical and Logical Density Maximums (continued) Feature E120 E320 OC12/STM-4 POS ports per chassis (ES2-S1 OC12-2 STM4 POS IOAs) OC48/STM16 ports per chassis (ES2-S1 OC48 STM16 POS IOAs) Logical density per chassis Logical OC3/STM1 per chassis Logical OC12/STM4 per chassis Logical OC48/STM16 per chassis E120 and E320 System Maximums...

  • Page 100: Link Layer Maximums

    JUNOSe 10.3.1 Release Notes Link Layer Maximums Table 10 lists link layer maximums for the E120 router and the E320 router. The following notes are referred to in Table 10: 1. On the ES2 10G LM, ES2 10G ADV LM, or ES2 10 G Uplink LM, you can have configurations with up to 100,000 static entries that support 100,000 DHCP relay proxy clients.
  • Page 101 Appendix A: System Maximums Table 10: Link Layer Maximums Feature E120 E320 ARP entries per line module Dynamic entries per LM 32,768 32,768 Static entries per ES2 4G LM 32,768 32,768 Static entries per ES2 10G LM, ES2 10G ADV LM, or ES2 128,000 128,000 10G Uplink LM...
  • Page 102 JUNOSe 10.3.1 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 ATM VP tunnels per port, all supported modules Bridged Ethernet interfaces per chassis 64,000 96,000 (See Notes 2 and 3 on page 92.) Bridged Ethernet interfaces per line module 16,000 16,000 (OCx/STMx ATM)
  • Page 103 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLANs per chassis 64,000 96,000 (See Notes 2, 4, and 5 on page 92.) Ethernet VLANs per IOA (See Note 7 on page 92.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM)
  • Page 104 JUNOSe 10.3.1 Release Notes Table 10: Link Layer Maximums (continued) Feature E120 E320 Ethernet VLAN overriding profile assignments per chassis Ethernet VRRP VRIDs per line module HDLC interfaces per chassis 24,000 24,000 HDLC interfaces per line module 8000 8000 MLPPP bundles per chassis 12,000 12,000 MLPPP bundles per line module...
  • Page 105 Appendix A: System Maximums Table 10: Link Layer Maximums (continued) Feature E120 E320 PPPoE service name tables PPPoE service name tables per chassis Service name tags per PPPoE service name table (including one empty service name tag) PPPoE subinterfaces per chassis 64,000 96,000 (See Notes 2 and 3 on page 92.)

  • Page 106: Routing Protocol Maximums

    JUNOSe 10.3.1 Release Notes Routing Protocol Maximums Table 11 lists routing protocol maximums for the E120 router and the E320 router. The following notes are referred to in Table 11: 1. The total set of FTEs can be shared by interfaces, next hops, ECMP sets, VRs, and VRFs.
  • Page 107 Appendix A: System Maximums Table 11: Routing Protocol Maximums (continued) Feature E120 E320 ECMP maximum paths to a destination BGP, IS-IS, MPLS, OSPF, RIP IPv4 forwarding table entries per chassis 1,048,576 1,048,576 (See Note 1 on page 98.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 108 JUNOSe 10.3.1 Release Notes Table 11: Routing Protocol Maximums (continued) Feature E120 E320 IPv6 routing table entries 100,000 100,000 (See Note 3 on page 98.) J-Flow statistics J-Flow–enabled VRs and VRFs, in any combination Sampled interfaces per VR or VRF Total sampled Interfaces per chassis Martini circuits for layer 2 services over MPLS Total Martini circuits per line module...

  • Page 109: Policy And Qos Maximums

    Appendix A: System Maximums Policy and QoS Maximums Table 12 lists policy and QoS maximums for the E120 router and the E320 router. The following notes are referred to in Table 12: 1. For more information about system resource requirements for nodes, queues, and shadow nodes, see JUNOSe Quality of Service Configuration Guide, Chapter 15, QoS Profile Overview.
  • Page 110 JUNOSe 10.3.1 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Policy classification (CLACL) entries per line module ES2 4G LM 256,000 256,000 ES2 10G LM 131, 071 131, 071 ES2 10G ADV LM 131, 071 131, 071 ES2 10G Uplink LM 65,535 65,535...
  • Page 111 Appendix A: System Maximums Table 12: Policy and QoS Maximums (continued) Feature E120 E320 ES2 10G Uplink LM 8191 8191 VLAN interface attachments Rate limiters (egress) per line module ES2 4G LM 64,000 64,000 ES2 10G LM 64,000 64,000 ES2 10G ADV LM 64,000 64,000 ES2 10G Uplink LM...
  • Page 112 JUNOSe 10.3.1 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Parent groups (ingress) per line module ES2 4G LM 49,151 49,151 ES2 10G LM 8191 8191 (internal parent groups only) ES2 10G ADV LM 8191 8191 (internal parent groups only ES2 10G Uplink LM 8191...

  • Page 113: Tunneling Maximums

    Appendix A: System Maximums Tunneling Maximums Table 13 lists tunneling maximums for the E120 router and the E320 router. The following notes are referred to in Table 13: 1. The ES2-S1 Service IOA supports any combination of DVMRP, GRE, and L2TP tunnels up to a maximum of 8000 tunnels;...
  • Page 114 JUNOSe 10.3.1 Release Notes Table 13: Tunneling Maximums (continued) Feature E120 E320 L2TP tunnels per line module with shared 8000 8000 tunnel-server ports provisioned (See Note 2 on page 105.) L2TP tunnels per ES2-S1 Service IOA 16,000 16,000 (See Note 1 and Note 2 on page 105.) E120 and E320 System Maximums...

  • Page 115: Subscriber Management Maximums

    Appendix A: System Maximums Subscriber Management Maximums Table 14 lists subscriber management maximums for the E120 router and the E320 router. The following notes are referred to in Table 14: 1. DHCP relay proxy maintains a list of active DHCP clients up to a maximum of 100,000 clients per chassis for all virtual routers.
  • Page 116 JUNOSe 10.3.1 Release Notes Table 14: Subscriber Management Maximums (continued) Feature E120 E320 DHCP relay and relay proxy client (See Notes 1 and 2 on page 107.) DHCP client host routes for DHCP relay and DHCP relay 100,000 100,000 proxy combined (per chassis for all virtual routers; and per virtual router) DHCP relay proxy clients (per chassis for all virtual 100,000...

  • Page 117: Appendix B Transferring Dsl Line Rate Information From An Access Node To Src Software

    Appendix B Transferring DSL Line Rate Information from an Access Node to SRC Software This appendix describes support for collection of updated DSL line rate parameters from an access node and transfer of this information from the Common Open Policy Service (COPS) or SRC client to the COPS server with other COPS messages. Configuring the SRC Client to Retrieve DSL Information from Access Nodes on page 109 Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the...
  • Page 118 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...
  • Page 119 Appendix B: Transferring DSL Line Rate Information from an Access Node to SRC Software Even if you confirm the prompt to enable the SRC client to forcibly send updated DSL line rate parameters to the COPS server, the COPS server that is running a release of SRC software earlier than Release 3.0.0 ignores the updated line rate details that it receives and processes only the other information in the COPS messages.

  • Page 120: Cops Server

    JUNOSe 10.3.1 Release Notes Monitoring the Status of Transfer of Updated DSL Line Rate Parameters to the COPS Server Display whether the SRC client is enabled to retrieve updated DSL line rate details Purpose from ANCP and send them to the SRC client with corresponding COPS messages. The command output refers to the SRC client by its former name, SSC client.

  • Page 121: Junose Command Reference Guide Update

    Appendix B: Transferring DSL Line Rate Information from an Access Node to SRC Software Only the field that has been newly added by this feature in the output of the NOTE: show sscc info command is described here. For a complete version of the descriptions of all the other fields that are displayed in the output of this command, see JUNOSe Broadband Access Configuration Guide, Chapter 2, Monitoring and Troubleshooting Remote Access.
  • Page 122 JUNOSe 10.3.1 Release Notes sscc update-policy-request enable...

This manual is also suitable for:

Junose 10.3.1

Table of Contents