Juniper JUNOSE 11.1.0 - REV 4-29-2010 Manual
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOSE 11.1.0 - REV 4-29-2010
  6. Manual
Juniper JUNOSE 11.1.0 - REV 4-29-2010 Manual

Juniper JUNOSE 11.1.0 - REV 4-29-2010 Manual

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 11.1.0
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Published: 2010-04-29

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOSE 11.1.0 - REV 4-29-2010 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Juniper JUNOSE 11.1.0 - REV 4-29-2010

Summary of Contents for Juniper JUNOSE 11.1.0 - REV 4-29-2010

  • Page 1: Release Notes

    JUNOSe Software ™ for E Series Broadband Services Routers ™ Release Notes Release 11.1.0 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 408-745-2000 www.juniper.net Published: 2010-04-29...
  • 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 11.1.0 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 11.1.0 Release Notes AAA ......................21 ATM......................21 BGP ......................21 BGP/MPLS VPNs ..................22 B-RAS ...................... 22 CLI......................22 DHCP ...................... 26 DHCP External Server................26 Dynamic Interfaces ................. 27 Ethernet ....................28 Flash......................29 GRE ......................29 Hardware ....................29 HDLC.......................
  • Page 7 Table of Contents MLPPP..................... 52 Mobile IP ....................52 MPLS ....................... 52 Multicast....................53 Netflow....................53 Policy Management ................. 54 PPPoE...................... 55 QoS ......................55 RSVP-TE ....................57 Service Manager ..................58 SNMP ...................... 58 SONET..................... 58 SRC Software and SDX Software ............. 58 Stateful SRP Switchover (High Availability) and IP Tunnels ......
  • Page 8 JUNOSe 11.1.0 Release Notes viii Table of Contents...

  • Page 9: Release 11.1.0

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

    Release 11.1.0 Release Highlights Release 11.1.0 includes the features described in this section. Category Feature Ethernet Support for Configuring 802.3ah OAM Link-Fault Management on Ethernet Interfaces on page 8 Support for Interchassis Redundancy (ICR) on ES2 10G LM and the ES2 10G ADV LM on page 9 Support for Fast Reconnection of PPPoE Subscribers on page 9 Support for Hardware Multicast Replication on ES2-S3...

  • Page 16: Ethernet

    JUNOSe 11.1.0 Release Notes Ethernet Support for Configuring 802.3ah OAM Link-Fault Management on Ethernet Interfaces JUNOSe Software supports the IEEE 802.3ah standard for Operation, Administration, and Maintenance (OAM). You can configure IEEE 802.3ah OAM on Ethernet point-to-point direct links or emulated point-to-point links. You must enable link-fault management on an interface using the ethernet oam lfm command in Interface Configuration mode to be able to configure link detection settings.

  • Page 17: Icr

    Release 11.1.0 oam3ahAssociations oam3ahEvents oam3ahPdus The following commands have been added to support configuration of OAM link-fault management: ethernet oam lfm ethernet oam lfm pdu-lost-threshold ethernet oam lfm high-threshold ethernet oam lfm pdu-transmit-interval ethernet oam lfm link-monitor ethernet oam lfm remote-failure ethernet oam lfm mode ethernet oam lfm remote-loopback The following commands have been added to support monitoring of OAM...

  • Page 18: L2Tp Over Mpls

    JUNOSe 11.1.0 Release Notes Now, when receiving traffic for non-existent PPPoE sessions, the router sends early termination requests by sending PPPoE Active Discovery Termination (PADT) packets to the clients instead of waiting for the client to reconnect after the PPPoE session expires. The clients respond by sending requests to log in again.
  • Page 19 Release 11.1.0 The MPLS ping feature for egress nodes in point-to-multipoint LSPs is not supported on ES2 10G LM line modules, although these LMs support MPLS settings. This restriction occurs because ES2 10G LMs do not forward the received MPLS LSP ping packets to the SRP module on the router, which disables a response to be transmitted to the originator of the request.

  • Page 20: Multiclass Mlppp

    As part of this feature, the following SNMP MIB objects have been added to the Juniper Networks PPP MIB: juniPppMlPppLinkConfigMultilinkMulticlass juniPppMlPppLinkConfigMultilinkMaxClasses The following SNMP MIB objects have been added to the Juniper Networks PPP Profile MIB: juniPppProfileMultilinkMulticlass juniPppProfileMultilinkMaxClasses The following commands have been added or enhanced to support multiclass...

  • Page 21: Policy Management

    Release 11.1.0 You can use the mirror-enable command to configure this feature through the CLI. The DHCP Option 82 identification method is used to trigger mirroring only for DHCP subscribers. The Agent Circuit ID and Agent Remote ID identification methods are used to trigger mirroring for both PPP and DHCP subscribers.

  • Page 22: Snmp

    The output of the show bulkstats command has been updated to display information about the QoS schema. As part of this feature, the following new MIB objects have been added to the Juniper Networks Enterprise MIB to specify the attributes for the QoS schema: rsAcctngAggDropRate rsAcctngQueueLength...

  • Page 23: System

    Release 11.1.0 Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, you obtained queue level statistics and configuration information for all logical interfaces using the QoS MIB. This feature has been enhanced to support the export of egress queue QoS statistics for various interface types.

  • Page 24: Early Field Trial Features

    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 25: Policy Management

    The JUNOSe Release 11.1.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 26: Multicast

    JUNOSe 11.1.0 Release Notes 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 27: Release Software Protocols

    Release 11.1.0 Release Software Protocols The following list identifies the major software protocols supported in this release. For detailed information about any protocol, see the configuration guides. Core Routing Stack Internet Protocol (IP) version 4 and version 6 Transmission Control Protocol (TCP) for IPv4 User Datagram Protocol (UDP) for IPv4 and IPv6 Network Management Protocols Simple Network Management Protocol (SNMP) versions 1, 2c, and 3...

  • Page 28: Security Protocols

    JUNOSe 11.1.0 Release Notes Bridged IP Cisco High-Level Data Link Control (Cisco HDLC) Ethernet Extensible Authentication Protocol (EAP) Frame Relay 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...

  • Page 29: 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: Known Behavior...

  • Page 30: Bgp/Mpls Vpns

    JUNOSe 11.1.0 Release Notes bgpConnections (default,0.0.0.0): TCP error code xx (...) occurred while accepting inbound TCP connection The message is generated when an unconfigured peer attempts to establish a TCP session with an E Series router and a valid route to the source address of the peer is absent from the router’s routing table.
  • Page 31 Release 11.1.0 Deprecated Command Command Mode Preferred Command channel-group snmp trap link-status Controller Configuration channel-group timeslots Controller Configuration classifier-list Global Configuration ip classifier-list clock rate Interface Configuration color Policy List Configuration color in Classifier Group Configuration mode controller e1 Global Configuration controller t1 Global Configuration description...
  • Page 32 JUNOSe 11.1.0 Release Notes Deprecated Command Command Mode Preferred Command ip mirror Global Configuration ip policy secure-input and ip policy secure-output; for E120 and E320 routers, you must use these commands because the ip mirror command has been removed from the CLI for those routers.
  • Page 33 Release 11.1.0 Deprecated Command Command Mode Preferred Command nrzi-encoding Interface Configuration no ospf enable Router Configuration ospf shutdown policy-list Global Configuration ip policy-list radius disconnect client Global Configuration subscriber disconnect The RADIUS Disconnect Configuration mode has been removed from the CLI. rate-limit-profile Policy List Configuration rate-limit-profile in Classifier...

  • Page 34: Dhcp

    JUNOSe 11.1.0 Release Notes The router displays a notice when you issue the command manually. If the command is in a script, the router automatically maps the deprecated command to the preferred command. If the deprecated command no longer has a function, then that command has no effect when you run a script containing the command.

  • Page 35: Dynamic Interfaces

    Release 11.1.0 Release 8.1.2 and all higher-numbered 8.1.x releases and patch releases Release 8.2.3 and all 8.2.3 patch releases Release 9.0.0 and all 9.0.0 patch releases 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...

  • Page 36: Ethernet

    JUNOSe 11.1.0 Release Notes 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 37: Flash

    Release 11.1.0 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 38: Hdlc

    JUNOSe 11.1.0 Release Notes 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 39 Release 11.1.0 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 40: Ipsec

    JUNOSe 11.1.0 Release Notes 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.

  • Page 41: L2Tp

    Release 11.1.0 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 42: 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 43: Packet Mirroring

    Release 11.1.0 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 44 JUNOSe 11.1.0 Release Notes 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 45: Ppp

    Release 11.1.0 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. NOTE: If you upgrade to Release 5.2.0 or later and then configure your router using a script generated before Release 5.2.0, the postupgrade and preupgrade...

  • Page 46: Qos

    JUNOSe 11.1.0 Release Notes In JUNOSe Releases 7.1.x, 7.2.x, and 7.3.x, you can attach a QoS profile to Ethernet interfaces that are configured in a link aggregation group (LAG) interface. However, beginning with JUNOSe Release 8.0.1, you can attach a QoS profile directly to the LAG interface.

  • Page 47: Snmp

    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 48: Ssh

    JUNOSe 11.1.0 Release Notes 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. In this event, a warning message is generated to alert you to the fact that SSH is disabled in that VR.

  • Page 49: Subscriber Interfaces

    Release 11.1.0 For OSPF, use the ip ospf dead-interval command to set the hold time. We recommend that you use Bidirectional Forwarding Detection (BFD) with a longer OSPF dead interval to achieve fast failure detection. For IS-IS, use the isis hello-interval and isis hello-multiplier commands to set the hold time.

  • Page 50: System Logging

    JUNOSe 11.1.0 Release Notes 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.

  • Page 51: Known Problems And Limitations

    Release 11.1.0 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 52 JUNOSe 11.1.0 Release Notes 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] 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.

  • Page 53: Bfd

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

  • Page 54: Dhcp External Server

    JUNOSe 11.1.0 Release Notes Work-around: To avoid this defect, do all of the following: Do not use the ip auto-detect ip-subscriber command to enable packet triggering and to create dynamic subscriber interfaces Ensure that DHCP external server is configured in the virtual router. Ensure that the set dhcp relay inhibit-access-route-creation command is configured in the virtual router to prevent DHCP relay from installing host routes by default.

  • Page 55: Ethernet

    Release 11.1.0 Ethernet When autonegotiation is enabled on Gigabit Ethernet interfaces with the speed automatically negotiate command, issuing the link selection command logs out subscribers. [Defect ID 87185] Work-around: Use the following commands to enable auto link selection (GE port redundancy) and to switch from one port to the other port: (config-if)#no link selection (config-if)#link failover force File System...

  • Page 56: Icr

    JUNOSe 11.1.0 Release Notes Work-around: You can do either of the following to avoid this problem. Specify each S-VLAN within the partially overlapping range as individual S-VLANs, as in the following example: host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 22 22 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 23 23 401 426 host1(config-if)#vlan bulk-config BulkDHCPCnfg1 svlan-range 21 21 427 712...

  • Page 57: Igmp

    Release 11.1.0 Work-around: To correct this problem and enable ICR partitions to be created correctly, make sure that you add the ICR partition configuration before the subscriber interface configuration in the .scr file. You can perform this reordering by modifying the .scr file to place the commands that configure subinterfaces for ICR partitions before the commands used for VLAN-based or S-VLAN-based grouping of subscribers.
  • Page 58 JUNOSe 11.1.0 Release Notes The ES2 4G LM can reset during a unified ISSU after you issue the issu start command on a router configured with 8000 dynamic VCs and 8000 packet-triggered dynamic subscriber interfaces. [Defect ID 86761] If you have a large configuration on a hybrid module combination (OC3/STM-1 GE/FE line module with the OC3-2 GE APS I/O module), boot from NVS, and issue the slot erase command before booting has completed, the line module resets.

  • Page 59: Ipsec

    Release 11.1.0 IPSec When the LAC–to–LNS data path runs over an MPLS tunnel and the MPLS tunnel originates or terminates at the LAC on an ES2 10G LM or an ES2 10G Uplink LM, the L2TP data traffic that originated or terminated at the LAC is discarded.

  • Page 60: Mlppp

    JUNOSe 11.1.0 Release Notes The E Series router does not log a warning when it receives an MLDv1 query but is not configured to use MLDv1 on the interface. [Defect ID 46046] MLPPP Failure to meet all of the following conditions for fragmented packets can result in an incorrect operation during packet classification of the resulting reassembled packet: [Defect ID 50111] The initial fragment of a packet must either contain the entire MLPPP...

  • Page 61: Multicast

    Release 11.1.0 Work-around: Issue the no mpls command to disable MPLS, then delete the interface. You cannot use an underscore character (_) in an MPLS tunnel name. [Defect ID 31291] If LSPs are announced into IS-IS, then the IS-IS routes cannot be used for multicast RPF checks, because LSPs are unidirectional.

  • Page 62: Policy Management

    JUNOSe 11.1.0 Release Notes The OC3/STM1 GE/FE line module might reset after sending Ethernet traffic into a VPLS network in a test environment when Ethernet packets are flooded to remote VPLS bridges. [Defect ID 74540] Policy Management On the E320 router, redirecting a large configuration with thousands of interfaces to a script file can take a long time, perhaps exceeding a half-hour depending on the configuration.

  • Page 63: Pppoe

    Release 11.1.0 When you modify a rate-limit profile in Global Configuration mode after the system is in a scaled state, changes to the rate-limit profile fail owing to lack of adequate policy resources. However, the changed value of the rate-limit profile is displayed in the output of the show rate-limit profile command.
  • Page 64 JUNOSe 11.1.0 Release Notes Work-around: Use node-controlled compound shared shaping configured on the best-effort scheduler node with EFA2-based ATM line modules. Egress strict-priority packets may experience high latency on OC3/STM1 ATM interfaces associated with the LM if you have shaped the port rate to more than 148.5 Mbps.

  • Page 65: Rsvp-Te

    Release 11.1.0 The no qos-parameter-define definition command does not delete the specified QoS parameter definition. [Defect ID 176844] Work-around: Remove the interface and add the desired QoS parameters when you re-create the interface instead of deleting the definition. When 32,000 subscribers with 128,000 QoS queues are brought up on an ES2 10G or ES2 10G ADV LM, the LM resets if you modify the QoS profile that contains the best-effort IP or VLAN node rule, which references a scheduler profile configured with shared shaping rate, to a scheduler profile configured...

  • Page 66: Service Manager

    JUNOSe 11.1.0 Release Notes Service Manager After you activate an independent IPv6 service and issue either of the following commands on the default virtual router or any other virtual router, except the one on which the subscriber session is active, no output is displayed in the CLI interface: [Defect ID 181929] show service-management subscriber-session subscriberName interface interfaceType interfaceSpecifier...

  • Page 67: Stateful Srp Switchover (High Availability) And Ip Tunnels

    Release 11.1.0 Changing the SSCC status (enable/disable) while IPv6 interfaces are configured might cause the SRP to reset. [Defect ID 179537] Stateful SRP Switchover (High Availability) and IP Tunnels When you issue show commands as soon as the CLI is available after a stateful SRP switchover, the commands can hang until the warm restart is completed.

  • Page 68: System

    JUNOSe 11.1.0 Release Notes If you configured a dynamic interface column, such as a dynamic bridged Ethernet interface, dynamic VLAN interface, or an ATM interface, and when any one of the following conditions is satisfied: The major interface is bounced (shut down and reenabled) The major interface is shut down, which cause the dynamic VLAN interfaces to be removed The physical link goes down and comes back up...

  • Page 69: System Logging

    Release 11.1.0 System Logging The show configuration category management syslog virtual-router default command incorrectly displays logs for multiple syslog destinations when you add a log to only one syslog destination. The show log configuration command shows the correct configuration. [Defect ID 84082] The SRP module resets in any of the following circumstances on an E320 router that has a line module configured with 5000 ANCP adjacencies: [Defect ID 176916]...
  • Page 70 JUNOSe 11.1.0 Release Notes During the unified ISSU operation, if you modify the router configuration after the initialization phase of the process is completed and before you issue the issu start command to commence the upgrade phase of the unified ISSU process, the unified ISSU procedure completes successfully and the stateful SRP switchover process begins to synchronize between the active and standby SRP modules.

  • Page 71: Resolved Known Problems

    Release 11.1.0 Resolved Known Problems Release 11.1.0 is based on Release 11.0.0 and incorporates all problem resolutions found in that release. The following problems were reported open in Release 11.0.0 and have been resolved in this release, or have been resolved since the 11.0.0 release.

  • Page 72: Errata

    JUNOSe 11.1.0 Release Notes Errata This section identifies errors found in the JUNOSe documentation. These errors are corrected in subsequent releases of the affected documentation. The Policy and QoS Maximums (for E120 and E320 routers) table in JUNOSe Release Notes, Appendix A, System Maximums for Releases 9.x, 10.x, and 11.0.x incorrectly states that the maximum number of policy classification (CLACL) entries for the ES2 10G Uplink LM is 131,171.

  • Page 73: 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 74: Erx310, Erx7Xx, And Erx14Xx System Maximums

    JUNOSe 11.1.0 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 75: 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 76 JUNOSe 11.1.0 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 77 Appendix A: System Maximums Table 2: Physical and Logical Density Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Logical density per module combination (specified line module and all supported I/O modules) Logical E1s per cOCx/STMx F0 line module 63 per 63 per 63 per 63 per...

  • Page 78: Link Layer Maximums

    JUNOSe 11.1.0 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 79 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 80 JUNOSe 11.1.0 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 81 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 82 JUNOSe 11.1.0 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 83: 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 84 JUNOSe 11.1.0 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 85 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 86 JUNOSe 11.1.0 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 72. ERX310, ERX7xx, and ERX14xx System Maximums...

  • Page 87: 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 88 JUNOSe 11.1.0 Release Notes Table 5: Policy and QoS Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 CAM entries (See Note 3 on page 79.) 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 89 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 90: Tunneling Maximums

    JUNOSe 11.1.0 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 91 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 82.) L2TP sessions per line module (See Notes 1 and 3 on page 82.) GE-2 with shared tunnel-server ports provisioned...

  • Page 92: Subscriber Management Maximums

    JUNOSe 11.1.0 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 93 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 84.) DHCP relay and relay proxy client (See Notes 1 and 2 on page 84.) DHCP client host routes for DHCP relay and DHCP relay 100,000 100,000...
  • Page 94 JUNOSe 11.1.0 Release Notes Table 7: Subscriber Management Maximums (continued) ERX705 and Feature ERX310 ERX710 ERX1410 ERX1440 Subscriber interfaces (See Note 2 on page 84.) Dynamic subscriber interfaces per chassis 16,000 32,000 32,000 48,000 Dynamic subscriber interfaces per line module 8000 8000 8000...

  • Page 95: 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 96: Physical And Logical Density Maximums

    JUNOSe 11.1.0 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 97 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 98: Link Layer Maximums

    JUNOSe 11.1.0 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 99 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 100 JUNOSe 11.1.0 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 90.) Bridged Ethernet interfaces per line module 16,000 16,000 (OCx/STMx ATM)
  • Page 101 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 90.) Ethernet VLANs per IOA (See Note 7 on page 90.) ES2-S1 GE-4 IOA 16,384 16,384 (with ES2 4G LM)
  • Page 102 JUNOSe 11.1.0 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 103 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 90.)

  • Page 104: Routing Protocol Maximums

    JUNOSe 11.1.0 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 105 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 96.) IP network interfaces (IPv4 and IPv6) Per chassis 64,000 96,000...
  • Page 106 JUNOSe 11.1.0 Release Notes Table 11: Routing Protocol Maximums (continued) Feature E120 E320 IPv6 routing table entries 100,000 100,000 (See Note 3 on page 96.) 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 107: 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 108 JUNOSe 11.1.0 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 QoS profile attachments per line module ES2 4G LM 16,000 16,000 ES2 10G LM 16,000 16,000 ES2 10G ADV LM 32,000 32,000 QoS scheduler nodes per line module 64,000 64,000 QoS shapers per line module...
  • Page 109 Appendix A: System Maximums Table 12: Policy and QoS Maximums (continued) Feature E120 E320 ES2 4G LM 16,383 16,383 combined ATM, GRE, L2TP (LAC only), MPLS, and VLAN interface attachments ES2 10G LM 16,383 16,383 IP interface attachments ES2 10G LM 16,383 16,383 VLAN interface attachments...
  • Page 110 JUNOSe 11.1.0 Release Notes Table 12: Policy and QoS Maximums (continued) Feature E120 E320 Parent groups (egress) 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 111: 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 112 JUNOSe 11.1.0 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 103.) L2TP tunnels per ES2-S1 Service IOA 16,000 16,000 (See Note 1 and Note 2 on page 103.) E120 and E320 System Maximums...

  • Page 113: 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 114 JUNOSe 11.1.0 Release Notes Table 14: Subscriber Management Maximums (continued) Feature E120 E320 DHCP relay and relay proxy client (See Notes 1 and 2 on page 105.) 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...

This manual is also suitable for:

Junose 11.1.0

Table of Contents