Juniper JUNOSE SOFTWARE 10.3.2 - RELEASE NOTES 9-29-2010, JUNOSe 10.3.2 Release Note
JunosE™ Software
for E Series
™
Broadband Services Routers
Release Notes
Release 10.3.2
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Published: 2010-09-29
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other
countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered
trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. 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 10.3.2
Writing: Subash Babu Asokan, Krupa Chandrashekar, Megha Shaseendran, Pallavi Madhusudhan, Namrata Mehta, Diane Florio, Brian Wesley Simmons,
Fran Singer, Sairam V
Editing: Ben Mann, Alana Calapai
Cover Design: Edmonds Design
Revision History
September 2010—FRS JunosE 10.3.2
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 10.3.2 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........................................................4
Opening a Case with JTAC ......................................................................... 4
Release Overview............................................................................................. 5
Before You Start ........................................................................................ 5
Release Highlights............................................................................................7
IPv6...........................................................................................................7
Early Field Trial Features.................................................................................. 7
DHCP ........................................................................................................8
Unified ISSU .............................................................................................. 9
Unsupported Features ...................................................................................... 9
E120 Router and E320 Router ................................................................... 9
Multicast....................................................................................................9
Policy Management ...................................................................................9
Stateful SRP Switchover (High Availability) .............................................. 10
Release Software Protocols ............................................................................ 10
Core Routing Stack ..................................................................................10
Layer 2 Protocols..................................................................................... 10
Multiprotocol Label Switching (MPLS) ......................................................11
Network Management Protocols..............................................................11
Routing Protocols .................................................................................... 11
Security Protocols....................................................................................11
SRC Software and SDX Software Compatibility Matrix................................... 12
Known Behavior ............................................................................................12
AAA......................................................................................................... 12
ATM.........................................................................................................12
BGP ......................................................................................................... 13
BGP/MPLS VPNs ......................................................................................13
B-RAS ......................................................................................................13
CLI........................................................................................................... 14
DHCP ......................................................................................................17
DHCP External Server.............................................................................. 17
Dynamic Interfaces .................................................................................19
Ethernet .................................................................................................. 19
Flash........................................................................................................20
Forwarding ..............................................................................................20
Table of Contents v
JunosE 10.3.2 Release Notes
GRE ......................................................................................................... 21
Hardware ................................................................................................21
HDLC....................................................................................................... 22
IP.............................................................................................................22
IPSec .......................................................................................................24
IS-IS.........................................................................................................24
L2TP........................................................................................................25
Line Module Redundancy ........................................................................25
MLPPP.....................................................................................................26
MPLS ....................................................................................................... 26
Multicast..................................................................................................26
Packet Mirroring...................................................................................... 27
Policy Management .................................................................................27
PPP..........................................................................................................29
PPPoE......................................................................................................29
QoS .........................................................................................................29
RADIUS ...................................................................................................30
SNMP ...................................................................................................... 31
SSH ......................................................................................................... 31
Stateful SRP Switchover (High Availability) .............................................. 32
Subscriber Interfaces ...............................................................................33
System ....................................................................................................33
System Logging ....................................................................................... 34
Tunneling ................................................................................................ 34
Known Problems and Limitations ..................................................................35
ANCP....................................................................................................... 35
ATM.........................................................................................................35
BFD ......................................................................................................... 37
Bridged Ethernet .....................................................................................37
CLI........................................................................................................... 37
DHCP ......................................................................................................37
DHCP External Server.............................................................................. 38
DoS Protection ........................................................................................ 38
Ethernet .................................................................................................. 38
File System..............................................................................................38
Forwarding ..............................................................................................39
ICR ..........................................................................................................40
IGMP ....................................................................................................... 41
IP.............................................................................................................41
IPSec .......................................................................................................42
IS-IS.........................................................................................................43
L2TP........................................................................................................43
MLD ........................................................................................................ 43
MLPPP.....................................................................................................43
Mobile IP ................................................................................................. 44
MPLS ....................................................................................................... 44
Multicast..................................................................................................45
Netflow.................................................................................................... 45
Policy Management .................................................................................45
PPPoE......................................................................................................47
QoS .........................................................................................................47
RSVP-TE .................................................................................................. 49
Service Manager ......................................................................................49
SNMP ...................................................................................................... 49
vi Table of Contents
Table of Contents
SONET..................................................................................................... 49
SRC Software and SDX Software ............................................................. 50
Stateful SRP Switchover (High Availability) and IP Tunnels......................50
Subscriber Management .......................................................................... 51
System ....................................................................................................52
System Logging ....................................................................................... 52
TCP ......................................................................................................... 52
Unified ISSU ............................................................................................ 52
Resolved Known Problems ............................................................................ 54
ATM.........................................................................................................54
BGP ......................................................................................................... 54
Bridged Ethernet .....................................................................................54
DHCP ......................................................................................................54
DHCPv6 Server........................................................................................55
DoS Protection ........................................................................................ 55
Ethernet .................................................................................................. 55
Forwarding ..............................................................................................55
HTTP Server ............................................................................................ 55
IGMP ....................................................................................................... 55
IP.............................................................................................................56
IPv6.........................................................................................................56
L2TP........................................................................................................56
Line Module Redundancy ........................................................................56
MPLS ....................................................................................................... 56
OSPF ....................................................................................................... 56
Policy Management .................................................................................56
QoS .........................................................................................................56
RSVP-TE .................................................................................................. 57
SRC Software and SDX Software ............................................................. 57
SRP..........................................................................................................57
Errata.............................................................................................................58
Appendix A
System Maximums 69
ERX310, ERX7xx, and ERX14xx System Maximums.....................................70
General System Maximums ..................................................................... 70
Physical and Logical Density Maximums ................................................. 71
Link Layer Maximums ............................................................................. 74
Routing Protocol Maximums ................................................................... 79
Policy and QoS Maximums......................................................................83
Tunneling Maximums.............................................................................. 86
Subscriber Management Maximums........................................................88
E120 and E320 System Maximums ............................................................... 91
General System Maximums ..................................................................... 91
Physical and Logical Density Maximums ................................................. 92
Link Layer Maximums ............................................................................. 94
Routing Protocol Maximums ................................................................. 100
Policy and QoS Maximums....................................................................103
Tunneling Maximums............................................................................ 107
Subscriber Management Maximums......................................................109
Table of Contents
vii
JunosE 10.3.2 Release Notes
viii Table of Contents
Release 10.3.2
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 10.3.2 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. Your software upgrades or application images may be available remotely
through Telnet or FTP, or may be delivered on a new NVS card. If you upgrade the
JunosE Software using a new NVS card, we recommend you perform the upgrade in
two stages: first to an intermediate release and then to the higher-numbered release
you want to run. This restriction is not applicable if you upgrade your software
remotely through Telnet or FTP.
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, if you are upgrading the software using a new NVS card, 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
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.
Highest Release Able
to 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
Cannot Load
6.x.x or
higher-numbered
release
Maximum
Application Image
~172 MB
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 10.3.2
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.
Requesting Technical Support 3
JunosE 10.3.2 Release Notes
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:
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.
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
4 Requesting Technical Support
Release Overview
Release 10.3.2
These Release Notes cover Release 10.3.2 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 7
Unsupported Features on page 9
Release Software Protocols on page 10
SRC Software and SDX Software Compatibility Matrix on page 12
Known Behavior on page 12
Known Problems and Limitations on page 35
Before You Start
Resolved Known Problems on page 54
Errata on page 58
Appendix A, System Maximums, on page 69
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
10.3.1 and 10.3.2. 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
10.3.2:
These 10.3.2 Release Notes, which describe changes between Release 10.3.1
and Release 10.3.2
The 10.3.1 Release Notes, which describe the features available in Release
10.3.1
The 10.3.x documentation set, which provides detailed information about
features available in Release 10.3.0
Release Overview 5
JunosE 10.3.2 Release Notes
The 10.3.x documentation set consists of several manuals and is available only in
electronic format. You can print your own documentation using the PDF and HTML
formats available at the Juniper Networks Technical Documentation Web site at
www.juniper.net/techpubs. Refer to the following table to help you decide which
document to use.
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
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
IPv6
Release 10.3.2
Release 10.3.2 is a maintenance release and includes the feature described in this
section.
Category Feature
IPv6 Support for IPv6 Neighbor Discovery Router
Advertisements with Service Modules on ERX Routers
Support for IPv6 Neighbor Discovery Router Advertisements with Service
Modules on ERX Routers
Service line modules and IPSec service modules (collectively referred to as
Service Modules) on ERX14xx models, ERX7xx models, and the ERX310 router
now support IPv6 Neighbor Discovery router advertisements for dynamically
configured interfaces. When a router is configured for IPv6, it uses router
advertisements to announce its presence to other nodes connected to it. Hosts
discover the addresses of their neighboring routers by listening for these
advertisements.
In addition to configuring Neighbor Discovery through the CLI, you can also use
IPv6 profiles and RADIUS to configure Neighbor Discovery route
advertisements for dynamically configured interfaces. If both an IPv6 profile
and RADIUS are configured for Neighbor Discovery router advertisement, the
prefix value returned in RADIUS VSA 26-129 takes precedence over the prefix
specified in the IPv6 profile configuration.
Change in existing behavior: Existing feature extended as described here. In
lower-numbered releases, IPv6 Neighbor Discovery was supported only on Fast
Ethernet, Gigabit Ethernet, OCx/STMx GE/FE, and OCx/STMx ATM line modules
on ERX routers. In this release, ERX routers that contain SMs support IPv6
Neighbor Discovery router advertisements on dynamic interfaces.
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.
Release Highlights 7
JunosE 10.3.2 Release Notes
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).
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
*****************************************
DHCP Local Server Address Limits
ATM Limit - 48000
VLAN Limit - 48000
POS Limit - 1000
Ethernet Limit - 48000
8 Early Field Trial Features
Unified ISSU
Service Manager Support for Unified ISSU
Unsupported Features
The JunosE Release 10.3.x documentation set describes some features that are
present in the code but that have not yet been fully qualified by Juniper Networks. If
you use any of these features before they have been fully qualified, it is your
responsibility to ensure that the feature operates correctly in your targeted
configuration.
The following features are present but unsupported in this release.
Release 10.3.2
Service Manager support for unified ISSU is limited in this release to early field
trial purposes only.
E120 Router and E320 Router
The ES2 10G LM and ES2 10G Uplink LM do not support layer 2 statistics for
VLANs.
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.
Multicast
Unsupported IPv6 Data MDT Commands in CLI
The ipv6 pim data-mdt command and the show ipv6 pim data-mdt
command 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.
Unsupported Features 9
JunosE 10.3.2 Release Notes
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
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
Layer 2 Protocols
Internet Protocol (IP) version 4 and version 6
Transmission Control Protocol (TCP) for IPv4
User Datagram Protocol (UDP) for IPv4 and IPv6
Asynchronous Transfer Mode (ATM)
Bridged Ethernet
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
10 Release Software Protocols
Multiprotocol Label Switching (MPLS)
Border Gateway Protocol (BGP-4)
Label Distribution Protocol (LDP)
Resource ReSerVation Protocol – Traffic Engineering Extensions (RSVP-TE)
Network Management Protocols
Simple Network Management Protocol (SNMP) versions 1, 2c, and 3
Routing Protocols
Border Gateway Protocol (BGP-4)
Distance Vector Multicast Routing Protocol (DVMRP)
Release 10.3.2
Security Protocols
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)
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)
Release Software Protocols 11
JunosE 10.3.2 Release Notes
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
3.2.0 Not applicable 10.1.0, 10.2.0, 10.3.0
Known Behavior
AAA
ATM
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.
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.
12 SRC Software and SDX Software Compatibility Matrix
BGP
Release 10.3.2
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.
BGP/MPLS VPNs
B-RAS
The following message might be displayed under certain conditions:
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.
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.
Known Behavior 13
JunosE 10.3.2 Release Notes
CLI
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
interval and
aaa user accounting interval
cablelength short Controller Configuration
channel-group description Controller Configuration
channel-group shutdown Controller Configuration
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 Interface Configuration
Still available in Controller
Configuration and VRF
Configuration modes
fdl Controller Configuration
fdl carrier Controller Configuration
fdl string Controller Configuration
fdl transmit Controller Configuration
filter Policy List Configuration filter in Classifier Group
forward next-hop Policy List Configuration forward next-hop in
forward next-interface Policy List Configuration forward interface in
ip description
Configuration mode
Classifier Group
Configuration mode
Classifier Group
Configuration mode
14 Known Behavior
Release 10.3.2
Deprecated Command Command Mode Preferred Command
hostname Domain Map Tunnel
client-name
Configuration
Still available in Global
Configuration mode
hssi description Interface Configuration
hssi force dte acknowledge Interface Configuration
hssi internal-clock Interface Configuration
ignore dcd Interface Configuration
ignore link-state-signals Interface Configuration
[ no ] ike cr
l Global Configuration [ no ] ipsec crl
interface hssi Global Configuration
invert tx clock Global Configuration
ip dhcp-local cable-modem Global Configuration set dhcp-relay with the
strings docsis and pktc in
the server-string mapping
specification
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.
ip policy local-input Interface Configuration,
None
Profile Configuration
[ no ] ipsec isakmp-policy rule Global Configuration [ no ] ipsec ike-policy-rule
ipv6 policy local-input Interface Configuration,
None
Profile Configuration
j1 Controller Configuration
license l2tp-session Global Configuration None
lineCoding Controller Configuration
log Policy List Configuration log in Classifier Group
Configuration mode
log severity debug
dhcpLocalProtocolDecode
loopback Domain Map Configuration
Global Configuration log severity debug
dhcpCapture
local-interface
Still available in Controller
Configuration and Interface
Configuration modes
loopback remote { remote line fdl
Controller Configuration
ansi | remote line fdl bellcore |
remote line inband remote payload
[ fdl ] [ ansi ] }
mark Policy List Configuration mark in Classifier Group
Configuration mode
Known Behavior 15
JunosE 10.3.2 Release Notes
Deprecated Command Command Mode Preferred Command
mark-de Policy List Configuration mark-de in Classifier Group
Configuration mode
mark-exp Policy List Configuration mark-exp in Classifier Group
Configuration mode
mark-user-priority Policy List Configuration mark-user-priority in
Classifier Group
Configuration mode
mpls ldp discovery
transport-address
mpls topology-driven-lsp
ip-interfaces
[ no ] next-hop Policy List Configuration forward next-hop in
[ no ] next-interface Policy List Configuration forward interface in
nrzi-encoding Interface Configuration
no ospf enable Router Configuration ospf shutdown
policy-list Global Configuration ip policy-list
radius disconnect client Global Configuration
rate-limit-profile Policy List Configuration rate-limit-profile in Classifier
remote-loopback Controller Configuration
show controllers t1/e1 User Exec, Privileged Exec
show controllers t1 remote User Exec, Privileged Exec
show ike certificates User Exec, Privileged Exec show ipsec certificates
show ike configuration User Exec, Privileged Exec show ipsec ike-configuration
show ike identity User Exec, Privileged Exec show ipsec identity
show ike policy-rule User Exec, Privileged Exec show ipsec ike-policy-rule
show ike sa User Exec, Privileged Exec show ipsec ike-sa
show ip dhcp-external binding Privileged Exec show dhcp binding
show ip dhcp-external binding-id Privileged Exec show dhcp binding
show ip dhcp-local binding Privileged Exec show dhcp binding
show ip dynamic-interface-prefix Privileged Exec, User Exec None
show ip mirror interface Privileged Exec show secure policy-list
show license l2tp-session User Exec, Privileged Exec None
t1 lineCoding Controller Configuration None. This command never
Interface Configuration This command has no effect
in Interface Configuration
mode. Now available in
Global Configuration mode.
Global Configuration ldp ip-forwarding
Classifier Group
Configuration mode
Classifier Group
Configuration mode
subscriber disconnect
The RADIUS Disconnect
Configuration mode has
been removed from the CLI.
Group Configuration mode
had any effect.
16 Known Behavior
Release 10.3.2
Deprecated Command Command Mode Preferred Command
traffic-class Policy List Configuration traffic-class in Classifier
Group Configuration mode
tunnel mpls autoroute announce
bgp
tunnel mpls label-dist Interface Configuration,
unframed Controller Configuration
user-packet-class Policy List Configuration user-packet-class in
virtual-router Domain Map Configuration
yellow Controller Configuration
Interface Configuration,
Tunnel Profile Configuration
Tunnel Profile Configuration
Still available in Privileged
Exec and Global
Configuration modes
None
None
Classifier Group
Configuration mode
router-name
DHCP
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.
The show configuration command normally takes a long time to finish for
extremely large configurations. If you specify a search string (with the begin,
exclude, or include options) with the command for a string that is not present
in the configuration, then the CLI session appears to be busy for a prolonged
period. The CLI filtering feature for show commands does not speed up
execution of the command.
Configuring authentication on the DHCP local server requires that you first
disable the DHCP local server for standalone mode. Doing so removes your
entire DHCP local server configuration. Therefore, if you want to configure
authentication, do so before you have otherwise configured the DHCP local
server.
When you upgrade from a release numbered lower than Release 7.1.0, all
DHCP host routes previously stored in NVS are deleted. After the upgrade,
DHCP clients must reacquire their IP addresses, which results in the new host
routes being correctly stored in NVS.
DHCP External Server
If you are using DHCP external server and a burst of client releases occurs
during a unified ISSU, some of the client releases might not be processed.
[Defect ID 180178]
Known Behavior 17
JunosE 10.3.2 Release Notes
When the DHCP relay agent application and the DHCP external server
application are configured in the same virtual router, using the ip
dhcp-external server-sync command on an unnumbered IP interface does not
function as expected. When you issue the ip dhcp-external server-sync
command in this configuration to create subscriber state information based on
lease renewals when the external DHCP server and the router are
unsynchronized, the router does not forward the ACK request from the DHCP
server to the client because there is no route. [Defect ID 88562]
When a bound DHCP client on a dynamic subscriber interface extends its IP
address lease by restarting the DHCP discovery process on its primary IP
interface instead of by initiating the DHCP renewal process on its dynamic
subscriber interface, the default behavior of the DHCP external server
application to preserve the client’s dynamic subscriber interface was changed
in the following JunosE releases to delete and re-create the client’s dynamic
subscriber interface:
Release 7.2.4p0-4 and all higher-numbered 7.2.x releases and patch
releases
Release 7.3.4 and all higher-numbered 7.3.x releases and patch releases
Release 8.0.4 and all higher-numbered 8.0.x releases and patch releases
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
delete and re-create the DHCP client’s dynamic subscriber interface.
NOTE: The DHCP external server application is unsupported in JunosE Release
8.2.1 and JunosE Release 8.2.2.
DHCP external server may not be able to bind all DHCP clients when all of the
following conditions exist:
DHCP external server and either DHCP relay or relay proxy are configured
The client-facing and server-facing interfaces for DHCP external server and
DHCP external server is configured to create dynamic subscriber interfaces.
18 Known Behavior
in separate virtual routers on an E320 router.
either DHCP relay or relay proxy are configured on the same ES2 4G LM.
Release 10.3.2
When these three conditions exist simultaneously, the ES2 4G LM may not be
able to successfully process all DHCP packets. Although all clients may get
bounded in DHCP relay or relay proxy, some clients may not get bounded in
DHCP external server. (In a production environment it is highly unlikely for
conditions 1 and 2 to exist because stand-alone DHCP external server is
normally configured for a DHCP relay in a different chassis.)
Work-aro u n d: You can eliminate this issue by modifying any one of these
conditions. For example, this issue does not exist with any of the following
configuration modifications:
Configure DHCP external server and either DHCP relay or relay proxy in
the same virtual router.
Configure the client-facing and server-facing interfaces for DHCP external
server and either DHCP relay or relay proxy on the same ES2 10G LM
instead of the same ES2 4G LM.
Dynamic Interfaces
Ethernet
Configure the client-facing and server-facing interfaces for DHCP external
server and either DHCP relay or relay proxy on separate ES2 4G LMs.
Dynamic IPv6 interfaces over static PPP interfaces are not supported.
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. When the link
goes down and then comes back up, the traffic flow is automatically
redistributed.
When counting bits per second on a Fast Ethernet or Gigabit Ethernet interface,
an E Series router includes 12 bytes for interpacket gap, 7 bytes for preamble,
and 1 byte for start frame delimiter, for a total of 20 bytes (160 bits) per packet
more than some non–E Series routers. This value therefore shows the total
bandwidth utilization on the interface, including both data and overhead.
To bridge unicast known-DA packets at line rate on both 2-Gbps ports of the
GE-2 line module or the GE-HDE module when paired with the GE-2 SFP I/O
module, the minimum packet size must be at least 144 bytes.
When installed in the ERX1440 router, the GE-2 module delivers full bandwidth
of 4 GB per line module (2 GB at the ingress and 2 GB at the egress) only when
installed in slot 2 or slot 4, and when the SRP-40G+ module is used in the
router. When installed in any other ERX1440 slot, the GE-2 module delivers a
maximum bandwidth of 2 GB per line module (1 GB maximum at the ingress
and 1 GB maximum at the egress). Therefore, of the maximum 24 possible
ports for the module in an ERX1440 chassis (that is, two ports in each of 12
slots), full bandwidth is delivered only on a maximum of four ports (those in
slots 2 and 4).
Known Behavior 19
JunosE 10.3.2 Release Notes
When installed in the ERX1440 router, the GE-HDE line module delivers full
bandwidth of 4 GB per line module (2 GB at the ingress and 2 GB at the egress)
only when installed in slot 2 or slot 4, and when the SRP-40G+ module is used
in the router. When installed in any other ERX1440 slot, the GE-HDE module
delivers a maximum bandwidth of 2 GB per line module (1 GB maximum at the
ingress and 1 GB maximum at the egress). Therefore, of the maximum 96
possible ports for the module in an ERX1440 chassis (that is, 8 ports in each of
12 slots), full bandwidth is delivered only on a maximum of 16 ports (those in
slots 2 and 4).
When the GE-2 line module or the GE-HDE line module is installed in either the
ERX1440 router or the ERX310 router and both ports are active, line rate
performance is achieved only with packets that are 174 bytes or larger. The line
module might not achieve line rate with packets that are smaller than
174 bytes.
Support for the 0x9200 S-VLAN Ethertype has been removed. You can no
longer specify the 9200 option with the svlan ethertype command.
Flash
Forwarding
When you upgrade to Release 7.1.0 or higher-numbered release, the software
automatically transfers existing configurations that use the 0x9200 Ethertype to
the 0x88a8 Ethertype.
The show interface gigabitEthernet command output does not display the
following line of output for Gigabit Ethernet modules that do not support SFPs,
such as the GE Single Mode I/O module and GE I/O Multi Mode I/O modules:
Primary/Secondary link signal detected
Primary/Secondary link signal not detected
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. This
integrity check is an expected side effect of the enhanced firmware available in
this release. The integrity check does not indicate a problem with the flash card
or its contents.
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. When the link
goes down and then comes back up, the traffic flow is automatically
redistributed. [Defect ID 180570]
20 Known Behavior
GRE
Hardware
Release 10.3.2
When you shut down the only outgoing IP interface to the IP destinations of
GRE/IP tunnels, the tunnels remain in the up state rather than transitioning to
down. As a consequence, all IP routes that use these tunnels as next hops also
remain in the routing table.
SRP modules with only 1 GB of memory do not work reliably in ERX7xx and
ERX14xx routers running JunosE Release 8.1.0 or higher, and may experience
system resets due to an out of memory condition. However, the ERX310 router
still supports 1 GB of memory in the SRP-SE10 module.
Work-aro u n d: Upgrade your SRP module memory to 2 GB for all ERX7xx and
ERX14xx routers running JunosE Release 8.1.0 or higher.
Do not include a not protocol clause in any classifier control list for policies
attached to an interface on an ES2 10G Uplink LM. The not protocol
functionality is not available for this module.
The ES2 10G LM and the ES2 10G Uplink LM do not support VLAN statistics in
the current release.
PCMCIA NVS Card Caution
CAUTION: Before you insert or remove PCMCIA NVS (flash) cards from a running
router, we strongly recommend that you halt the SRP module or shut down the
router. Failure to do this can result in file corruption in one or both cards.
The 4XOC3 APS MULTIMODE and 4XOC3 APS SINGLE MODE I/O modules are
incompatible with the following versions of the OCx/STMx ATM and OCx/STMx
POS line modules:
OCx/STMx ATM line modules with assembly numbers 350-00039-xx,
350-80039-xx, and 350-90039-xx
OCx/STMx POS line modules with assembly number 350-10039-xx
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.
There is a very small chance that some line modules can have an improperly
modified keying block that prevents the module from proper seating in the top
slot of an older ERX7xx chassis or a preproduction ERX310 chassis. For
example, this problem has been observed for an OCx/STMx module in slot 2 of
an early-test ERX310 chassis.
Work-aro u n d: Remove the keying block to insert the module into the top slot,
or insert the module into a different slot.
Known Behavior 21
JunosE 10.3.2 Release Notes
HDLC
IP
By design, on the cOC12/STM4 module you cannot delete a serial interface
while data for the interface is still enqueued. The enqueued data can drain only
when the interface is operationally up. Therefore you must ensure that the
interface is operationally up before you delete it. For example, if you have
issued the shutdown command for the interface before you try to delete the
interface, issue the no shutdown command, then delete the interface.
When you upgrade from certain releases to JunosE Release 9.2.0p1-0 or
higher-numbered releases, descriptions configured for IP interfaces or IP
subinterfaces are not retained across the upgrade when the descriptions are
shorter than 9 characters in length. Additionally, VRF descriptions are not
retained across the upgrade when the combined length of the VRF description
and the VRF name is shorter than 9 characters. This behavior is seen during
upgrades using a reload, stateful SRP switchover, or unified ISSU. Upgrades
from the following releases are affected by this behavior:
7.x.x
8.0.x
8.1.x, 8.2.x, and 9.x.x builds created before July 23, 2008
Examples of descriptions that are not retained across the upgrade:
host1(config-if)#ip description 12345678
host1(config)#ip vrf 123
host1(config-vrf)#description 45678
Examples of descriptions that are retained across the upgrade:
host1(config-if)#ip description longdescription
host1(config)#ip vrf longername
host1(config-vrf)#description 45678
host1(config)#ip vrf 123
host1(config-vrf)#description longdescription
Work-aro u n d: 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
The ip tcp adjust-mss command, which modifies the maximum segment size
for TCP SYN packets traveling through the interface, is not supported on the
ES2 10G LM or ES2 10G Uplink LM.
22 Known Behavior
associated VRF names and descriptions consists of 9 or more characters.
Loading...