Juniper JUNOSE 11.1.0 - REV 4-29-2010, JUNOSe 11.1.0 User Manual
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
Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or
registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or
otherwise revise this publication without notice.
Products made or sold by Juniper Networks (including the ERX310, ERX705, ERX710, ERX1410, ERX1440, M5, M7i, M10, M10i, M20, M40, M40e, M160,
M320, and T320 routers, T640 routing node, and the JUNOS, JUNOSe, and SDX-300 software) or components thereof might be covered by one or more of
the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650,
6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Copyright © 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.
JUNOSe™ Software for E Series™ Broadband Services Routers Release Notes, Release 11.1.0
Writing: Subash Babu Asokan, Krupa Chandrashekar, Megha Shaseendran, Pallavi Madhusudhan, Namrata Mehta, Diane Florio, Brian Wesley Simmons,
Fran Singer, Sairam V
Editing: Ben Mann, Krishnaveni Venkatesan
Cover Design: Edmonds Design
Revision History
April 2010—FRS JUNOSe 11.1.0
The information in this document is current as of the date listed in the revision history.
Software License
The terms and conditions for using this software are described in the software license contained in the acknowledgment to your purchase order or, to the
extent applicable, to any reseller agreement or end-user purchase agreement executed between you and Juniper Networks. By using this software, you
indicate that you understand and agree to be bound by those terms and conditions.
Generally speaking, the software license restricts the manner in which you are permitted to use the software and may contain prohibitions against certain
uses. The software license may state conditions under which the license is automatically terminated. You should consult the license for further details.
For complete product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.
END USER LICENSE AGREEMENT
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING,
INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER OR
IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS
AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE
SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1. 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
of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for which
Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment
which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such
software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades,
additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a
non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use
restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer
from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units for which
Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software
only, Customer shall use such Software on a single computer containing a single physical random access memory space and containing any
number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones)
requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits
to Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users,
sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate
licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput, performance,
configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use of the Software to
managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software. Customer’s use of the
Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software.
Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or
create an additional trial period by re-installing the Software after the 30-day trial period.
e. 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. No license is granted herein to any user who did not originally purchase the
applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall
not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as
necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d)
remove any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute
any copy of the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ‘locked’
or key-restricted feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid
key from Juniper, even if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the
Software provided by Juniper to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer
from Juniper or an authorized Juniper reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available
for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of
testing or benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other
than as expressly provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall
furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such,
Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum
includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customer’s internal business
purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software,
associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or
interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement
that accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support the Software.
Support services may be purchased separately. Any such support shall be governed by a separate, written support services agree
MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE
SOFTWARE, OR ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM
UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY
STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER
EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK
RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR
ATTACK. In no event shall Juniper’s or its suppliers’ or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of
warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the Software is embedded in another
Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered
into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of
risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.
9. Termi natio n. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license
granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in
Customer’s possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase
of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to
Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer
shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by
promptly: providing Juniper with valid tax receipts and other required documentation showing Customer’s payment of any withholding taxes;
completing appropriate applications that would reduce the amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or
tax proceeding related to transactions hereunder. Customer shall comply with all applicable tax laws and regulations, and Customer will promptly pay
or reimburse Juniper for all costs and damages related to any liability incurred by Juniper as a result of Customer’s non-compliance or delay with its
responsibilities herein. Customer’s obligations under this Section shall survive termination or expiration of this Agreement.
11 . Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign
agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations,
or without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain
encryption or other capabilities restricting Customer’s ability to export the Software without an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or
disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through
227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface
information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if
any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with
any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology
are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or
vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided
with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are
distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU
General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (including Juniper
ment. TO THE
modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. 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.
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The
provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this
Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara
County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and
supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written (including any inconsistent terms contained in
a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern
to the extent such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement nor any waiver of any rights
hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any portion of this Agreement is held invalid, the
Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and associated documentation has
been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur
volonté que cette convention de même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation:
The parties confirm that this Agreement and all related documentation is and will be in the English language)).
Table of Contents
Release 11.1.0 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 ..........................................................3
Hardware and Software Compatibility.......................................................3
Requesting Technical Support .........................................................................3
Self-Help Online Tools and Resources........................................................3
Opening a Case with JTAC ......................................................................... 4
Release Overview............................................................................................. 4
Before You Start ........................................................................................ 5
Release Highlights............................................................................................7
Ethernet .................................................................................................... 8
ICR ............................................................................................................9
IP.............................................................................................................10
L2TP over MPLS ......................................................................................10
MLPPP.....................................................................................................10
MPLS ....................................................................................................... 10
Multiclass MLPPP.....................................................................................12
Packet Mirroring...................................................................................... 12
Policy Management .................................................................................13
SDX Software and SRC Software .............................................................13
SNMP ...................................................................................................... 14
System ....................................................................................................15
System Maximums .................................................................................. 15
Early Field Trial Features................................................................................ 16
DHCP ......................................................................................................16
Policy Management .................................................................................17
Unsupported Features .................................................................................... 17
E120 Router and E320 Router ................................................................. 17
Multicast..................................................................................................18
Policy Management .................................................................................18
Stateful SRP Switchover (High Availability) .............................................. 18
Release Software Protocols ............................................................................ 19
Core Routing Stack ..................................................................................19
Network Management Protocols..............................................................19
Routing Protocols .................................................................................... 19
Multiprotocol Label Switching (MPLS) ......................................................19
Layer 2 Protocols..................................................................................... 19
Security Protocols....................................................................................20
SRC Software and SDX Software Compatibility Matrix................................... 20
Known Behavior ............................................................................................21
Table of Contents v
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....................................................................................................... 30
IP.............................................................................................................30
IPSec .......................................................................................................32
IS-IS.........................................................................................................32
L2TP........................................................................................................33
Line Module Redundancy ........................................................................33
MLPPP.....................................................................................................34
MPLS ....................................................................................................... 34
Multicast..................................................................................................34
Packet Mirroring...................................................................................... 35
Policy Management .................................................................................35
PPP..........................................................................................................37
PPPoE......................................................................................................37
QoS .........................................................................................................38
RADIUS ...................................................................................................38
SNMP ...................................................................................................... 39
SSH ......................................................................................................... 40
Stateful SRP Switchover (High Availability) .............................................. 40
Subscriber Interfaces ...............................................................................41
System ....................................................................................................41
System Logging ....................................................................................... 42
Tunneling ................................................................................................ 42
Known Problems and Limitations ..................................................................43
ANCP....................................................................................................... 43
ATM.........................................................................................................43
BFD ......................................................................................................... 45
Bridged Ethernet .....................................................................................45
CLI........................................................................................................... 45
DHCP ......................................................................................................45
DHCP External Server.............................................................................. 46
DoS Protection ........................................................................................ 46
Ethernet .................................................................................................. 47
File System..............................................................................................47
Forwarding ..............................................................................................47
ICR ..........................................................................................................48
IGMP ....................................................................................................... 49
IP.............................................................................................................50
IPSec .......................................................................................................51
IS-IS.........................................................................................................51
L2TP........................................................................................................51
MLD ........................................................................................................ 51
vi Table of Contents
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......................59
Subscriber Management .......................................................................... 59
System ....................................................................................................60
System Logging ....................................................................................... 61
TCP ......................................................................................................... 61
Unified ISSU ............................................................................................ 61
Resolved Known Problems ............................................................................ 63
IP.............................................................................................................63
Errata.............................................................................................................64
Appendix A
System Maximums 65
ERX310, ERX7xx, and ERX14xx System Maximums.....................................66
General System Maximums ..................................................................... 66
Physical and Logical Density Maximums ................................................. 67
Link Layer Maximums ............................................................................. 70
Routing Protocol Maximums ................................................................... 75
Policy and QoS Maximums......................................................................79
Tunneling Maximums.............................................................................. 82
Subscriber Management Maximums........................................................84
E120 and E320 System Maximums ............................................................... 87
General System Maximums ..................................................................... 87
Physical and Logical Density Maximums ................................................. 88
Link Layer Maximums ............................................................................. 90
Routing Protocol Maximums ................................................................... 96
Policy and QoS Maximums......................................................................99
Tunneling Maximums............................................................................ 103
Subscriber Management Maximums......................................................105
Table of Contents
vii
JUNOSe 11.1.0 Release Notes
viii Table of Contents
Release 11.1.0
Release Installation
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.
Before upgrading to a new version of software, save your router’s running
configuration to a .cnf file or .scr file. If you subsequently need to downgrade for
any reason, you can restore the earlier software version.
NOTE: When you upgrade the software on a router that has a large number of
interfaces configured, the router might appear to be unresponsive for several
minutes. This condition is normal; allow the process to continue uninterrupted.
Upgrading to Release 5.3.0 or a Higher-Numbered Release
When you upgrade from a lower-numbered release to Release 5.3.0 or a
higher-numbered release, the higher release might not load if you issue the boot
system command from Boot mode while the lower-numbered software is running
on the router or if you insert a flash card running a higher-numbered release into a
system running a lower numbered release. However, if you issue the boot system
command from Global Configuration mode, the new software loads properly.
Release Installation 1
JUNOSe 11.1.0 Release Notes
Upgrading from Release 5.1.1 or Lower-Numbered Releases to
Release 6.x.x or Higher-Numbered Releases
Release 5.1.1 or lower-numbered releases support application images only up to
172 MB. To install larger application images for Release 6.0.0 and higher-numbered
releases, you must first install Release 5.1.2 (or a higher-numbered 5.x.x release).
This enables the system to support application images greater than 172 MB. For
example, you cannot go from Release 5.1.1 to Release 7.2.0 without first upgrading
to Release 5.1.2. See the following table for compatibility of releases.
JUNOSe Release
5.1.1 or lower-numbered
release
5.1.2 or
higher-numbered release
7.2.0 or
higher-numbered release
Highest Release Able
to Load Cannot Load
5.3.5p0-2 or the
highest-numbered 5.x.x
release
No limitation Not applicable ~234 MB
No limitation Not applicable ~256 MB
6.x.x or
higher-numbered
release
Maximum
Application Image
~172 MB
Your software upgrades may be available remotely through Telnet or FTP, or may
be delivered on a new NVS card. Depending on how you access the software
updates, there are two different procedures to follow. For more detailed
information on installing software, and about NVS cards and SRP modules, see the
following documents:
JUNOSe System Basics Configuration Guide, Chapter 6, Managing Modules
Upgrading NVS Cards on SRP Modules in ERX Hardware Guide, Chapter 8,
Maintaining ERX Routers
Upgrading NVS Cards on SRP Modules in E120 and E320 Hardware Guide, Chapter
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
release onto the current router, and then reboot the router to load the release onto
the line modules. If you then move any of those line modules to an ERX1440
router, that router is able to recognize the line module.
If you move a compatible line module from an ERX1440 router to an ERX705,
ERX710, or ERX1410 router, the module loads properly in the new router
regardless of the release.
2 Release Installation
SRP Module Memory Requirements
For Release 5.3.0 and higher-numbered software releases on ERX14xx models,
ERX7xx models, and the Juniper Networks ERX310 Broadband Services Router, see
ERX Module Guide, Table 1, ERX Module Combinations, for detailed information
about memory requirements.
For Release 8.2.0 and higher-numbered software releases on Juniper Networks
E120 and E320 Broadband Services Routers, see E120 and E320 Module Guide, Table
1, Modules and IOAs, for detailed information about memory requirements.
Hardware and Software Compatibility
For important information about hardware and software, see the document set as
follows:
Combinations of line modules to achieve line rate performance are in JUNOSe
System Basics Configuration Guide, Chapter 6, Managing Modules.
Release 11.1.0
Compatibility of ERX router modules with software releases is in ERX Module
Guide, Table 1, ERX Module Combinations.
Layer 2 and layer 3 protocols and applications supported by ERX router
modules are in ERX Module Guide, Appendix A, Module Protocol Support.
Compatibility of E120 router and E320 router modules with software releases
is in E120 and E320 Module Guide, Table 1, Modules and IOAs.
Layer 2 and layer 3 protocols and applications supported by IOAs on the E120
router and the E320 router are in E120 and E320 Module Guide, Appendix A, IOA
Protocol Support.
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical
Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC
support contract, or are covered under warranty, and need post-sales technical
support, you can access our tools and resources online or open a case with JTAC.
JTAC Policies—For a complete understanding of our JTAC procedures and
policies, review the JTAC User Guide located at
http://www.juniper.net/customers/support/downloads/710059.pdf
Product Warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/
JTAC Hours of Operation—The JTAC centers have resources available 24 hours
a day, 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:
Requesting Technical Support 3
JUNOSe 11.1.0 Release Notes
Find CSC offerings:
http://www.juniper.net/customers/support/
Search for known bugs:
http://www2.juniper.net/kb/
Find product documentation:
http://www.juniper.net/techpubs/
Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/
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/
To verify service entitlement by product serial number, use our Serial Number
Entitlement (SNE) Tool located at
https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
Use the Case Manager tool in the CSC at
http://www.juniper.net/cm/
Call 1-888-314-JTAC
(1-888-314-5822 – toll free in the USA, Canada, and Mexico)
For international or direct-dial options in countries without toll-free numbers, visit
http://www.juniper.net/support/requesting-support.html
Release Overview
These Release Notes cover Release 11.1.0 of the system software for the Juniper
Networks E Series Broadband Services Routers and contain the following sections:
Release Highlights on page 7
Early Field Trial Features on page 16
Unsupported Features on page 17
Release Software Protocols on page 19
4 Release Overview
Before You Start
Release 11.1.0
SRC Software and SDX Software Compatibility Matrix on page 20
Known Behavior on page 21
Known Problems and Limitations on page 43
Resolved Known Problems on page 63
Errata on page 64
Appendix A, System Maximums on page 65
If the information in these Release Notes differs from the information found in the
published documentation set, follow these Release Notes.
These Release Notes include information about the changes between Releases
11.0.0 and 11.1.0. Before you use your new software, read these Release Notes in
their entirety, especially the section Known Problems and Limitations. You need the
following documentation to fully understand all the features available in Release
11.1.0:
These 11.1.0 Release Notes, which describe changes between Release 11.0.0
and Release 11.1.0
The 11.0.0 Release Notes, which describe features available in Release 11.0.0
The 11.1.x documentation set, which provides detailed information about
features available in Release 11.1.0
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.
Task Document
Install the router ERX Hardware Guide
E120 and E320 Hardware Guide
Learn about modules ERX Module Guide
ERX End-of-Life Module Guide
E120 and E320 Module Guide
Get up and running quickly E Series Installation Quick Start poster or ERX Quick Start
Guide
E120 and E320 Quick Start Guide
Configure the router JUNOSe System Basics Configuration Guide
Configure physical layer interfaces JUNOSe Physical Layer Configuration Guide
Configure link layer interfaces JUNOSe Link Layer Configuration Guide
Release Overview 5
JUNOSe 11.1.0 Release Notes
Task Document
Configure line module redundancy,
stateful SRP switchover, unified ISSU,
VRRP, and interchassis redundancy
(ICR)
Configure IP, IPv6 and Neighbor
Discovery, and interior gateway
protocols (RIP, OSPF, and IS-IS)
Configure IP routing services,
including routing policies, NAT, J-Flow
statistics, BFD, IPSec, digital
certificates, and IP tunnels
Configure IP multicast routing and
IPv6 multicast routing
Configure BGP, MPLS, Layer 2
service, and related applications
Configure policy management JUNOSe Policy Management Configuration Guide
Configure quality of service (QoS) JUNOSe Quality of Service Configuration Guide
Configure remote access JUNOSe Broadband Access Configuration Guide
Get specific information about
commands
Monitor system events JUNOSe System Event Logging Reference Guide
Look up definitions of terms used in
JUNOSe technical documentation
JUNOSe Service Availability Configuration Guide
JUNOSe IP, IPv6, and IGP Configuration Guide
JUNOSe IP Services Configuration Guide
JUNOSe Multicast Routing Configuration Guide
JUNOSe BGP and MPLS Configuration Guide
JUNOSe Command Reference Guide A to M
JUNOSe Command Reference Guide N to Z
JUNOSe Glossary
6 Release Overview
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
ICR
IP
L2TP over MPLS
MLPPP
MPLS
Multiclass MLPPP
Packet Mirroring
Policy Management
SDX Software and SRC
Software
SNMP
System
System Maximums
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
GE-20 IOA on page 10
Support for L2TP over MPLS with ES2 10G ADV LM as
Access Module on page 10
MLPPP Fragmentation and Reassembly Support on
OCx/STMx ATM IOAs on page 10
Support for Verifying Connectivity of Point-to-Multipoint
LSPs at Egress Nodes on page 10
Support for Troubleshooting MTU Failures in
Point-to-Point MPLS LSPs on page 11
Multiclass MLPPP Support on page 12
Support for Packet Mirroring Trigger on page 12
Support for HTTP Redirect on ES2 10G ADV LM on
page 13
Support for IPv6 HTTP Redirect on ES2 10G LM on
page 13
Support for CAM Classifier Size of 144-Bit on page 13
Transfer of Calling Station ID to PDP on page 13
Bulk Statistics Support for QoS Schema on page 14
Automatic Update of MAC Address Without SRP
Switchover After SRP IOA Hot-Swap on page 15
Increased Number of Active Service Sessions and Active
Subscriber Sessions on E120 and E320 Routers on
page 15
Increased Number of L2TP Tunnels per Chassis on E120
and E320 Routers with SRP-320 and ES2 4G LM on
page 16
Release 11.1.0
Release Highlights 7
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.
JUNOSe Software supports the following OAM functionalities:
Discovery—Detects the devices in the network and their OAM capabilities.
This process is triggered automatically when you enable OAM on the
interface.
Link monitoring—Detects and signifies link faults under various conditions
using the Event Notification OAM protocol data unit (PDU), and sends
events to the remote OAM entity when problems are detected on the link.
Remote fault detection—Detects failure conditions that occur in the receive
path of the link and influences the state of the link based on the Event
Notification OAM PDU received from the remote peer.
Remote loopback—Causes the interface of a local entity to receive and
respond to loopback requests from remote peers. Remote loopback mode
ensures link quality between the router and a remote peer.
NOTE: Because the hysteresis mechanism is not available in JUNOSe Software
Release 11.1.0, an OAM session can terminate unexpectedly.
The following line module combinations on E Series routers support the
802.3ah OAM link-fault management feature:
ES2 4G line module combinations on the E120 router and the E320 router:
ES2 4G line modules with ES2-S1 GE-8 IOA
ES2 4G line modules with ES2-S1 GE-4 IOA
ES2 4G line modules with ES2-S1 10GE IOA
GE-2 and GE-HDE line module combinations on ERX14xx models, ERX7xx
In addition, the following log event categories have been added to support the
OAM link-fault management feature:
8 Release Highlights
models, and the ERX310 router:
GE-2 and GE-HDE line modules with GE-2 SFP I/O module
GE-HDE line modules with GE-8 I/O module
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
link-fault management:
ICR
show ethernet oam lfm discovery show ethernet oam lfm status
show ethernet oam lfm statistics show ethernet oam lfm summary
Change in existing behavior: New feature added as described here.
Support for Interchassis Redundancy (ICR) on ES2 10G LM and the ES2 10G
ADV LM
On E120 and E320 routers, the ES2 10G LM and ES2 10G ADV LM now support
interchassis redundancy (ICR). ICR enables you to recover from router failure
and minimize subscriber downtime, when the router or access interface on the
edge router fails, by re-creating subscriber sessions on the backup router that
were originally terminated on the failed router. ICR currently supports only
PPPoE subscribers.
NOTE: The ES2 10G LM and ES2 10G ADV LM do not support fast reconnection of
PPPoE subscribers.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, ICR was not supported on the ES2 10G LM and ES2
10G ADV LM.
Support for Fast Reconnection of PPPoE Subscribers
JUNOSe Software now supports the fast reconnection of PPPoE subscribers
after an ICR failover, except when an administrator intentionally forces a
failover.
After an ICR failover, when the new master router becomes active, the
aggregation network forwards PPPoE data to the new master router. In
lower-numbered releases, the new master router dropped these packets
because a session did not exist for the PPPoE subscribers on the new master
router.
Release Highlights 9
JUNOSe 11.1.0 Release Notes
IP
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. Then, the new master router creates sessions for the PPPoE subscribers..
NOTE: The ES2 10G LM and ES2 10G ADV LM do not support fast reconnection of
PPPoE subscribers.
Change in existing behavior: New feature added as described here. In
lower-numbered releases, the router drops the PPPoE packets because a
session did not exist for the PPPoE subscribers. This is no longer the case.
Support for Hardware Multicast Replication on ES2-S3 GE-20 IOA
Logical port 20 on the ES2-S3 GE-20 IOA is reserved for the hardware multicast
packet replication feature. You can now configure logical port 20 for hardware
multicast replication on the ES2-S3 GE-20 IOA.
L2TP over MPLS
MLPPP
Change in existing behavior: Existing feature extended as described here. In
lowered-numbered releases, logical port 20 could not be configured for
hardware multicast replication on the ES2-S3 GE-20 IOA. This is no longer the
case.
Support for L2TP over MPLS with ES2 10G ADV LM as Access Module
JUNOSe Software now supports configuration of L2TP over MPLS with an ES2
4G LM, ES2 10G LM, or ES2 10G ADV LM as the access module and an ES2 10G
ADV LM as the uplink line module.
Change in existing behavior: Existing feature extended as described here.
MLPPP Fragmentation and Reassembly Support on OCx/STMx ATM IOAs
You can now configure MLPPP fragmentation and reassembly on the following
module combinations on E120 routers and E320 routers:
ES2 4G LM with ES2-S1 OC3-8 STM1 ATM IOA
ES2 4G LM with ES2-S1 OC12-2 STM4 ATM IOA
Change in existing behavior: Existing feature extended as described here.
MPLS
Support for Verifying Connectivity of Point-to-Multipoint LSPs at Egress Nodes
You can now use the MPLS ping and trace features, available in routers other
than E Series routers, to detect data plane failures at E Series routers that
function as egress nodes of point-to-multipoint LSPs.
10 Release Highlights
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.
As part of this feature, the mplsTraffic event log category has been enhanced to
display point-to-multipoint MPLS ping and trace packets received at egress
LSRs of point-to-multipoint LSPs.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, E Series routers that were egress nodes of
point-to-multipoint RSVP-TE MPLS LSPs could not respond to
point-to-multipoint MPLS ping messages (echo requests) and, therefore, could
not participate in verification of data-plane of point-to-multipoint RSVP-TE
MPLS LSPs.
Support for Troubleshooting MTU Failures in Point-to-Point MPLS LSPs
You can now determine the label-switched router (LSR) in a point-to-point LSP
at which packets are dropped from further transmission, when the size of the
packet exceeds the maximum transmission (MTU) size, and troubleshoot MTU
failures.
Release 11.1.0
You can use the data-size keyword with the trace mpls command for
point-to-point LSPs in Privileged Exec and User Exec modes to specify the size
of the MPLS ping messages (echo requests) in point-to-point LSPs associated
with an IP or IPv6 address, a Martini circuit, an L3VPN IP or IPv6 prefix, an
RSVP-TE tunnel, or a VPLS instance. You can specify a size in the range 0–6400
bytes; the default size is 100 bytes.
You can use the data-size keyword to determine whether MPLS packets with a
particular size can be forwarded over an MPLS point-to-point LSP, when the
size of the packet exceeds the MTU size at any of the LSRs that are nodes on
the LSP. If you specify the packet size for MPLS echo requests, you can
determine the exact LSR where the MTU size is exceeded and the MPLS
packets are discarded. You can use this keyword to enable the pad TLV to be
added to the MPLS LSP ping message (echo request), which results in future
MPLS LSP ping echo requests to be of the same specified number of bytes.
The following commands have been enhanced to support specification of size
of the MPLS ping message (echo request packet) to troubleshoot MTU problems
in point-to-point MPLS LSPs:
trace mpls ip trace mpls rsvp tunnel
trace mpls l2transport trace mpls vpls
trace mpls l3vpn
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, you could not use the trace function of the MPLS
ping feature to troubleshoot MTU problems in point-to-point MPLS LSPs.
Release Highlights 11
JUNOSe 11.1.0 Release Notes
Multiclass MLPPP
Multiclass MLPPP Support
Multiclass multilink PPP (MLPPP) enables you to fragment data packets of
different priorities into multiple classes and to send high-priority packets
between fragments of larger packets. When the MLPPP bundle consists of
more than one multilink interface, multilink classes ensure that high-priority
data packets are received in the sequence they were transmitted.
With multiclass MLPPP each traffic class is mapped to a separate multilink
class. Multiclass MLPPP supports mapping of up to eight traffic classes. The
default traffic class is the best-effort class. The multiclass MLPPP feature also
supports fragmentation and reassembly on the multilink classes.
As part of this feature, the following SNMP MIB objects have been added to the
Juniper Networks PPP MIB:
juniPppMlPppLinkConfigMultilinkMulticlass
Packet Mirroring
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
MLPPP configuration and monitoring:
ppp multilink multiclass show ppp interface mlppp config
ppp multilink multiclass
fragmentation
ppp multilink multiclass reassembly show ppp interface mlppp statistics
ppp multilink multiclass traffic-class
show ppp interface mlppp full
Change in existing behavior: New feature added as described here.
Support for Packet Mirroring Trigger
You can now trigger packet mirroring for PPP and DHCP subscribers through
the following new subscriber identification methods:
Agent Circuit ID
Agent Remote ID
DHCP Option 82
12 Release Highlights
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.
Change in existing behavior: New feature added as described here.
Support for HTTP Redirect on ES2 10G ADV LM
You can now create an exception rule within an IP policy classifier group for
the ES2 10G ADV LM. The exception rule enables an application such as HTTP
redirect to perform application-dependent action on the content of the packet.
To create the exception rule, use the exception http-redirect command.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, an IP policy with exception http-redirect as the
action was not supported on the ES2 10G ADV LM.
Support for IPv6 HTTP Redirect on ES2 10G LM
You can now create an exception rule within an IPv6 policy classifier group for
the ES2 10G LM. The exception rule enables an application such as HTTP
redirect to perform application-dependent action on the content of the packet.
To create the exception rule, use the exception http-redirect command.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, the ES2 10G LM did not support an IPv6 policy with
exception http-redirect.
Support for CAM Classifier Size of 144-Bit
You can now configure content-addressable memory (CAM) hardware classifier
entries to be 144 bits for IPv6 policies on the ES2 10G LM or the ES2 10G
Uplink LM. The number of 144-bit classifiers supported on the ES2 10G LM is
256K and on the ES2 10G Uplink LM is 128K.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, the number of 144-bit classifiers supported on the
ES2 10G LM was 128K and the number of 144-bit classifiers supported on the
ES2 10G Uplink LM was 64K.
SDX Software and SRC Software
Transfer of Calling Station ID to PDP
JUNOSe Software now supports sending of the calling station ID to the Policy
Decision Point (PDP) for a virtual router. To enable this, use the sscc option
send-calling-station-id command in Global Configuration mode.
The following command has been modified in this release:
sscc option
Release Highlights 13
JUNOSe 11.1.0 Release Notes
SNMP
The output of the following command has been modified in this release:
show sscc option
Change in existing behavior: New feature added as described here.
Bulk Statistics Support for QoS Schema
The bulk statistics feature now supports the QoS schema, which enables
service providers to receive QoS statistics on egress queues for various
interface types. Service providers can use this feature to keep track of network
congestion and oversubscription by monitoring the QoS statistics and
configuration information for the egress interface queues on the router.
To enable bulk statistics to export egress queue-level statistics for subscriber
interfaces, you can now use the bulkstats schema subtree qos command in
Global Configuration mode. To enable the export of aggregate forwarded and
dropped rates of traffic over each S-VLAN or ATM VP (virtual path), include the
export-summarized-stats keyword.
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
rsAcctngAssuredRate rsAcctngQueueProfile
rsAcctngBurst rsAcctngRedDropBytes
rsAcctngByteAdjBytes rsAcctngRedDropPackets
rsAcctngByteAdjType rsAcctngRedEnabled
rsAcctngDropProfile rsAcctngSchedulerProfile
rsAcctngForwardedBytes rsAcctngShapingMode
rsAcctngForwardedPackets rsAcctngShapingRate
rsAcctngForwardedRate rsAcctngSharedShapingMode
rsAcctngGreenDropBytes rsAcctngSharedShapingRate
rsAcctngGreenDropPackets rsAcctngStatisticsProfile
rsAcctngParentChildWeight rsAcctngWeight
rsAcctngParentShapingRate rsAcctngYellowDropBytes
rsAcctngParentSharedShapRate rsAcctngYellowDropPackets
The following commands have been added or modified as part of this feature
bulkstats schema subtree qos show bulkstats
14 Release Highlights
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.
Automatic Update of MAC Address Without SRP Switchover After SRP IOA
Hot-Swap
On E120 and E320 routers, when you complete hot-swapping an SRP IOA, its
MAC address in the subnet is now automatically refreshed without rebooting
the SRP or the chassis. Also, you can re-insert an SRP IOA that you had taken
out previously to the same network without refreshing the MAC address of the
SRP IOA.
If you have configured RADIUS server on an SRP IOA that you want to replace,
you can perform either of the following actions to prevent loss of accounting or
logout information:
System Maximums
Disable accounting and, when there is no subscriber login or logout
activity, hot-swap the SRP IOA.
Increase the timeout value of the RADIUS server configured depending on
the time used for IOA replacement. The maximum timeout value is 1000
seconds.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, after you completed the hot-swap, you used the srp
switch command to refresh the MAC address of the SRP IOA. Failure to refresh
the MAC address resulted in MAC address conflict, which could cause
disruption of applications or sessions running over the management port. This
is no longer the case.
Increased Number of Active Service Sessions and Active Subscriber Sessions on
E120 and E320 Routers
Beginning with JUNOSe Release 11.1.0, the number of active service sessions
and the number of active subscriber sessions on E120 and E320 routers have
increased as follows:
For E120 routers, the number of active service sessions increased from
131,072 to 196,608 and the number of active subscriber sessions
increased from 49,152 to 64,000.
For E320 routers, the number of active service sessions increased from
Change in existing behavior: Existing feature extended as described here.
131,072 to 262,144 and the number of active subscriber sessions
increased from 49,152 to 96,000.
Release Highlights 15
JUNOSe 11.1.0 Release Notes
Early Field Trial Features
Increased Number of L2TP Tunnels per Chassis on E120 and E320 Routers
with SRP-320 and ES2 4G LM
The number of L2TP tunnels per chassis on E120 and E320 routers with an
SRP-320 module and an ES2 4G LM has increased from 16,000 to 32,000
CAUTION: On E120 and E320 routers with an SRP-320 module, scaling the L2TP
tunnel to more than 16,000 is not supported if the chassis has an ES2 10G LM.
The ES2 10G LM may reset if the L2TP tunnel is scaled to more than 16,000.
Change in existing behavior: New system maximums as described here.
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.
DHCP
Support for DHCP External Server, DHCP Local Server, DHCP Relay, and DHCP
Relay Proxy on POS Access Interfaces
The following packet over SONET (POS) module combinations on E Series
routers now support configuration of the DHCP external server, DHCP local
server, DHCP relay, and DHCP relay proxy applications, alone or in
combination, when the POS module is the access interface:
POS module combinations on the E120 router and the E320 router:
ES2 4G LM with ES2-S1 OC12-2 STM4 POS IOA
ES2 4G LM with ES2-S1 OC48 STM16 POS IOA
POS module combinations on ERX14xx models, ERX7xx models, and the
ERX310 router:
OCx/STMx POS line module with OC3-4 I/O module
OCx/STMx POS line modules with OC12/STM4 I/O module
OC48 line module with OC48 FRAME APS I/O module
In the current release, this feature is available for early field test purposes only.
You can configure DHCP external server, DHCP local server, DHCP relay, and
DHCP relay proxy on these POS modules in either a virtual router (VR) or a VPN
routing and forwarding instance (VRF).
16 Early Field Trial Features
Release 11.1.0
As part of this feature, the pos keyword has been added to the existing ip
dhcp-local limit command. To specify the maximum number of IP addresses
that the DHCP local server application can supply to all POS access interfaces
or to a specific POS access interface, in the range 0–96000, use the ip
dhcp-local limit command with the new pos keyword. For example:
! Set the IP address limit for all POS access interfaces to 1000
host1(config)#ip dhcp-local limit pos 1000
! Set the IP address limit for the specified POS access interface to 2000
host1(config)#ip dhcp-local limit interface pos 5/0/0 2000
! Restore the IP address limit for all POS access interfaces to the default value,
! 48000
host1(config)#no ip dhcp-local limit pos
To display the maximum number of IP address leases available for POS access
interfaces, use the existing show ip dhcp-local limits command. For example:
host1#show ip dhcp-local limits
Policy Management
Support for CAM Classifier Size of Larger Than 144 Bits
Unsupported Features
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.
*****************************************
DHCP Local Server Address Limits
ATM Limit - 48000
VLAN Limit - 48000
POS Limit - 1000
Ethernet Limit - 48000
You can now configure content-addressable memory (CAM) hardware classifier
entries to be greater than 144 bits for IPv6 policies on the ES2 10G LM or the
ES2 10G Uplink LM. All different sizes of CAM classification entries like 144,
288, and 576 bits are supported. This feature is limited in this release to early
field trial purposes only.
The following features are present but unsupported in this release.
E120 Router and E320 Router
The ES2 10G LM and ES2 10G Uplink LM do not support layer 2 statistics for
VLANs.
Unsupported Features 17
JUNOSe 11.1.0 Release Notes
Multicast
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.
Unsupported IPv6 Data MDT Commands in CLI
The ipv6 pim data-mdt command and the show ipv6 pim data-mdt
commands are unsupported in the current release.
The IPv6 PIM Data MDT Configuration mode is unsupported in this release. The
following commands appear in IPv6 PIM Data MDT Configuration mode but are
unsupported in the current release:
ipv6 pim join-filter mdt-data-timeout
ipv6 pim query-interval route map
mdt-data-delay tunnel group-address-pool
mdt-data-holdown tunnel source
Policy Management
External Parent Groups Unsupported on ES2 10G, ES2 10G Uplink, and ES2
10G ADV LMs
External parent groups are not supported on the ES2 10G, ES2 10G Uplink, and
ES2 10G ADV LMs. If you create a policy that references an external parent
group on these LMs, the system prevents you from attaching it to the LM
interface and you receive an error message.
Stateful SRP Switchover (High Availability)
Stateful SRP Switchover for Certain Applications
The stateful SRP switchover feature has not been qualified for the following
applications:
Remote Access
DHCP proxy client
L2TP dialout
18 Unsupported Features
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
Release 11.1.0
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
Open Shortest Path First (OSPF) version 2 and version 3
Protocol Independent Multicast Protocol (PIM), including PIM dense mode, PIM
sparse mode, PIM dense-sparse mode, and PIM source-specific multicast
Routing Information Protocol (RIP) version 2
Virtual Private LAN Service (VPLS)
Virtual Router Redundancy Protocol (VRRP)
Multiprotocol Label Switching (MPLS)
Border Gateway Protocol (BGP-4)
Label Distribution Protocol (LDP)
Resource ReSerVation Protocol – Traffic Engineering Extensions (RSVP-TE)
Layer 2 Protocols
Asynchronous Transfer Mode (ATM)
Bridged Ethernet
Release Software Protocols 19
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
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)
SRC Software and SDX Software Compatibility Matrix
The SRC software offers the features of the SDX software on the C Series
Controllers, a range of hardware platforms that use the Linux operating system. In
contrast, the SDX software runs on Solaris workstations. The SRC software contains
the features found in the associated SDX release plus additional features described
in the SRC Release Notes.
The following table shows which versions of the SRC software and SDX software
are compatible with specified versions of the JUNOSe Software.
SRC Software Release SDX Software Release Tested with JUNOSe Release
2.0.0 7.1.0 8.1.2, 8.2.2
2.1.0 Not applicable 9.1.0p0-1
3.0.0 Not applicable 9.0.0, 9.0.1, 9.1.1
3.1.0 Not applicable 9.2.0, 9.3.0, 10.0.0
20 SRC Software and SDX Software Compatibility Matrix
Known Behavior
AAA
Release 11.1.0
SRC Software Release SDX Software Release Tested with JUNOSe Release
3.2.0 Not applicable 10.1.0, 10.2.0, 10.3.0
For more detailed information about SRC software and SDX software compatibility
with JUNOSe releases, see the SRC Release Notes.
This section briefly describes E Series router behavior and related issues. In some
cases the behavior differs from non–E Series implementations; in others the
behavior is included to emphasize how the router works.
Although you can use the max-sessions command to configure a maximum of
32,000 outstanding authentication/authorization requests to a RADIUS server,
AAA internal limits prevent the actual number of outstanding
authentication/authorization requests from exceeding 9600. These internal
AAA limits apply only to authentication/authorization requests and not to
accounting requests.
ATM
BGP
The JUNOSe Software does not support accounting for ATM 1483 subscribers.
The atm1483 keyword for the aaa accounting default command is present in
the CLI, but it is not supported.
You cannot configure connection admission control (CAC) on an ATM interface
on which you have created a bulk-configured virtual circuit (VC) range for use
by a dynamic ATM 1483 subinterface. Conversely, you cannot create a
bulk-configured VC range on an ATM interface on which you have configured
CAC. The router rejects these configurations, which causes them to fail.
Configuring CAC and bulk-configured VCs on the same ATM interface was
supported in previous JUNOSe Software releases. As a result, If you are
upgrading to the current JUNOSe release from a lower-numbered release,
configurations that use CAC and bulk configuration on the same ATM interface
continue to work. However, we recommend that you disable CAC on these
ATM interfaces to ensure continued compatibility with future JUNOSe releases.
The E Series router does not include the link-local IPv6 address in the next-hop
field of an MP-BGP update message carrying IPv6 routing information over
IPv4 transport. This behavior is compliant with RFC 2545 but might have
interoperability issues with other implementations that depend on a link-local
IPv6 address in the next-hop field on a directly connected external BGP
peering.
Work-aro u n d: Enable EBGP multihop configuration on the remote
(non–Juniper Networks) peer.
The following message might be displayed under certain conditions:
Known Behavior 21
JUNOSe 11.1.0 Release Notes
BGP/MPLS VPNs
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.
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
NAT does not function properly with secondary routing table lookup (fallback
global) or global export mapping on the VRF.
B-RAS
CLI
Pool groups are not supported; although the ip local pool group command
appears in the CLI, it is not supported.
If the router is under a heavy load, the show profile command might take
longer than usual to execute.
Work-aro u n d: You can either delay examination of profiles until the router is
less busy, or save a copy of the profile to a text file off the router.
In Interface Configuration mode for a major interface, the CLI displays options
for protocols that are not supported by that interface type.
When you issue the reload command on an ERX310 router, the command
might display a warning message that erroneously indicates that a
synchronizing operation will be performed. Any references to synchronization
that appear in command output or system messages do not apply to the
ERX310 router, which does not support SRP module redundancy.
The following commands have been deprecated in the JUNOSe Software and
might be removed completely in a future release. If a command has been
deprecated for only a particular command mode, the table specifies any modes
for which it is still available.
Deprecated Command Command Mode Preferred Command
aaa accounting interval Global Configuration aaa service accounting
cablelength short Controller Configuration
channel-group description Controller Configuration
channel-group shutdown Controller Configuration
22 Known Behavior
interval and
aaa user accounting interval
Loading...