Dell Powerconnect J Ex4200 Software Manual Guide For JUNOS Version 11.1 Volume 1
Dell-Powerconnect-J-Ex4500-Quick-Reference-Guide-114549 dell-powerconnect-j-ex4500-quick-reference-guide-114549
2015-01-05
: Dell Dell-Powerconnect-J-Ex4200-Software-Manual-136613 dell-powerconnect-j-ex4200-software-manual-136613 dell pdf
Open the PDF directly: View PDF .
Page Count: 1308
Download | |
Open PDF In Browser | View PDF |
Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Published: 2011-05-25 Revision 3 Dell 501 Dell Way Round Rock , Texas 78682 United States www.dell.com This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright © 1986-1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public domain. This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto. This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright © 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved. GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by Cornell University and its collaborators. GateD is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing protocol. Development of GateD has been supported in part by the National Science Foundation. Portions of the GateD software copyright © 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright © 1991, D. L. S. Associates. This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc. Information in this document is subject to change without notice. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell, Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, and PowerConnect are trademarks of Dell Inc. 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 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. Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 © Copyright Dell, Inc. , 2011. All rights reserved. Revision History 30 April 2011—Revision 3 15 November 2010—Revision 2 4 June 2010—Revision 1 The information in this document is current as of the date listed in the revision history. ii 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 iii 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 agreement. TO THE 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. Termination. 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. iv 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 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)). v vi Table of Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiii Downloading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxiv Documentation Symbols Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxv Repair and Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxvi Part 1 Junos OS for J-EX Series Switches Product Overview Chapter 1 Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Layer 3 Protocols Supported on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . 17 Layer 3 Protocols Not Supported on J-EX Series Switches . . . . . . . . . . . . . . . . . . . 18 Security Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . . 20 High Availability Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . . 22 VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Graceful Protocol Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Redundant Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Nonstop Active Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Nonstop Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . . . . 25 Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . . 25 Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Chapter 2 Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 J-EX4200 Switches Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 J-EX4200 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Uplink Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Power over Ethernet (PoE) Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 J-EX4200 Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 J-EX4500 Switches Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 J-EX4500 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Virtual Chassis Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Uplink Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 J-EX4500 Switch Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 vii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 J-EX8208 Switch Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Chassis Physical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Routing Engines and Switch Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 J-EX8216 Switch Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Chassis Physical Specifications, LCD Panel, and Midplane . . . . . . . . . . . . . . 38 Routing Engines and Switch Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Cooling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Part 2 Complete Software Configuration Statement Hierarchy Chapter 3 Complete Software Configuration Statement Hierarchy . . . . . . . . . . . . . . . 45 [edit access] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 45 [edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 46 [edit class-of-service] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 47 [edit ethernet-switching-options] Configuration Statement Hierarchy . . . . . . . . 48 [edit firewall] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 51 [edit forwarding-options] Configuration Statement Hierarchy . . . . . . . . . . . . . . . 51 [edit interfaces] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 52 [edit poe] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 [edit protocols] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 57 [edit routing-instances] Configuration Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 63 [edit snmp] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . 64 [edit virtual-chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . 64 [edit vlans] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Part 3 Software Installation Chapter 4 Software Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Understanding Software Installation on J-EX Series Switches . . . . . . . . . . . 69 Overview of the Software Installation Process . . . . . . . . . . . . . . . . . . . . 69 Software Package Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Installing Software on a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Installing Software on J-EX8200 Switches with Redundant Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Installing Software Using Automatic Software Download . . . . . . . . . . . . 71 Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Junos OS Package Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Understanding System Snapshot on J-EX Series Switches . . . . . . . . . . . . . . 72 viii Table of Contents Understanding Resilient Dual-Root Partitions on Switches . . . . . . . . . . . . . . 74 Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and Later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) . . . . . . 74 Understanding Upgrading or Downgrading Between Resilient Dual-Root Partition Releases and Earlier Releases . . . . . . . . . . . . . . . . . . . . . . . 75 Licenses Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Understanding Software Licenses for J-EX Series Switches . . . . . . . . . . . . . . 76 Features Requiring a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 License Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 License Key Components for the J-EX Series Switch . . . . . . . . . . . . . . . . . . . . 77 Chapter 5 Installing Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Downloading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Preparing the Switch for the Software Installation . . . . . . . . . . . . . . . . . . . . . 82 Installing Software on the Backup Routing Engine . . . . . . . . . . . . . . . . . . . . . 83 Installing Software on the Default Master Routing Engine . . . . . . . . . . . . . . . 84 Returning Routing Control to the Default Master Routing Engine (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Installing Software on J-EX Series Switches (J-Web Procedure) . . . . . . . . . . . . . 86 Installing Software Upgrades from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Installing Software Upgrades by Uploading Files . . . . . . . . . . . . . . . . . . . . . . 88 Rebooting or Halting the J-EX Series Switch (J-Web Procedure) . . . . . . . . . . . . . 88 Chapter 6 Booting the Switch, Upgrading Software, and Managing Licenses . . . . . . . 91 Registering the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Booting the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Booting a J-EX Series Switch Using a Software Package Stored on a USB Flash Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Creating a Snapshot and Using It to Boot a J-EX Series Switch . . . . . . . . . . . 92 Creating a Snapshot on a USB Flash Drive and Using It to Boot the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Creating a Snapshot on an Internal Flash Drive and Using it to Boot the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Upgrading Software Using Automatic Software Download on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Managing Licenses for the J-EX Series Switch (CLI Procedure) . . . . . . . . . . . 95 Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Saving License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Managing Licenses for the J-EX Series Switch (J-Web Procedure) . . . . . . . . 96 Adding New Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Deleting Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Displaying License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 ix Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Downloading Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Chapter 7 Verifying Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Verifying That Automatic Software Download Is Working Correctly . . . . . . . 99 Verifying That a System Snapshot Was Created on a J-EX Series Switch . . 100 Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Verifying the Number of Partitions and File System Mountings . . . . . . . 101 Verifying the Loader Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Verifying Which Root Partition Is Active . . . . . . . . . . . . . . . . . . . . . . . . . 102 Verifying the Junos OS Version in Each Root Partition . . . . . . . . . . . . . . 103 Monitoring Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Monitoring Licenses for the J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . 104 Displaying Installed Licenses and License Usage Details . . . . . . . . . . . . 104 Displaying Installed License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Chapter 8 Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Troubleshooting Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Recovering from a Failed Software Upgrade on a J-EX Series Switch . . . . . 107 Rebooting from the Inactive Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Freeing Disk Space for Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . 109 Installation from the Boot Loader Generates ’cannot open package’ Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Troubleshooting a Switch That Has Booted from the Backup Junos OS Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Resilient Dual-Root Partitions Frequently Asked Questions . . . . . . . . . . . . . . . . . 111 How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from Normal Upgrades? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 What Happens If I Do Not Upgrade Both the Loader Software and Junos OS at the Same Time? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Can I Downgrade Junos OS Without Downgrading the Loader Software? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Can I Upgrade to a Resilient Dual-Root Partition Release by Using the CLI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Will I Lose My Configuration During an Upgrade? . . . . . . . . . . . . . . . . . . . . . . 113 How Long Will the Upgrade Process Take? . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 What Happens to My Files If the System Detects a File System Corruption? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 How Will I Be Informed If My Switch Boots from the Alternate Slice Due to Corruption in the Root File System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Can I Use Automatic Software Update and Download to Upgrade to a Resilient Dual-Root Partition Release? . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Why Is the Message "At least one package installed on this device has limited support" Displayed When Users Log In to the Switch? . . . . . . . . 114 Chapter 9 Configuration Statements for Software Installation . . . . . . . . . . . . . . . . . . . 117 [edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 117 auto-image-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 x Table of Contents Chapter 10 Operational Commands for Software Installation . . . . . . . . . . . . . . . . . . . . 119 request system license add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 request system license delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 request system license save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 request system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 request system software add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 request system software delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 request system software rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 request system software validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 show system autoinstallation status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 show system boot-messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 show system license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 show system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 show system storage partitions (J-EX Series Switches Only) . . . . . . . . . . . . . . . 146 Part 4 User Interfaces Chapter 11 User Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 User Interfaces—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 CLI User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 CLI Help and Command Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 CLI Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 J-Web User Interface for J-EX Series Switches Overview . . . . . . . . . . . . . . . 153 Understanding J-Web Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Understanding J-Web User Interface Sessions . . . . . . . . . . . . . . . . . . . . . . . . 157 Chapter 12 Using the Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Using the CLI Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Starting the J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Chapter 13 Operational Commands for User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 161 set cli complete-on-space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 set cli directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 set cli idle-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 set cli prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 set cli restart-on-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 set cli screen-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 set cli screen-width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 set cli terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 set cli timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 show cli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 show cli authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 show cli directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 show cli history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 start shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 xi Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Part 5 Junos OS for J-EX Series Switches System Setup Chapter 14 System Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Junos OS—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . 181 Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . 182 Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . 182 Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Chapter 15 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Connecting and Configuring a J-EX Series Switch (CLI Procedure) . . . . . . . . . . . 185 Connecting and Configuring a J-EX Series Switch (J-Web Procedure) . . . . . . . . 187 Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) . . . . . . . . . 190 Disabling or Enabling Menus and Menu Options on the LCD Panel . . . . . . . 190 Configuring a Custom Display Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) . . . . . 192 Configuring System Identity for a J-EX Series Switch (J-Web Procedure) . . . . . . 193 Chapter 16 Configuration Statements for System Setup . . . . . . . . . . . . . . . . . . . . . . . . . 195 arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 auxiliary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 boot-server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 broadcast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 console (Physical Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 default-address-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 domain-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 gre-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 host-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 icmpv4-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 icmpv6-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 inet6-backup-router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 internet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 ipip-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 ipv6-duplicate-addr-detection-transmits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 ipv6-path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 ipv6-path-mtu-discovery-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 ipv6-reject-zero-hop-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 lcd-menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 menu-item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 multicast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 no-multicast-echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 no-ping-record-route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 no-ping-time-stamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 no-redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 no-tcp-rfc1323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 no-tcp-rfc1323-paws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 xii Table of Contents path-mtu-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 tcp-drop-synfin-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 traceoptions (SBC Configuration Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 trusted-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Chapter 17 Operational Commands for System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 227 clear chassis display message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 clear system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 request chassis pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 request chassis routing-engine master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 request system halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 request system logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 request system power-off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 request system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 request system scripts convert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 request system storage cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 set chassis display message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 set date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 show chassis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 show chassis lcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 show configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 show host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 show ntp associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 show ntp status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 show system firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 show system reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 show system snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 show system software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 show system storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 show system switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 show system uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 show system users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 show system virtual-memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 show task replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 xiii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Part 6 Junos OS for J-EX Series Switches Configuration Management Chapter 18 Configuration Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Configuration Files—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Understanding Configuration Files for J-EX Series Switches . . . . . . . . . . . . . 327 Configuration Files Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Understanding Automatic Refreshing of Scripts on J-EX Series Switches . . 329 Understanding Autoinstallation of Configuration Files on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Typical Uses for Autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Autoinstallation Configuration Files and IP Addresses . . . . . . . . . . . . . 330 Typical Autoinstallation Process on a New Switch . . . . . . . . . . . . . . . . 330 J-EX Series Switches Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 J-EX4200 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 J-EX4500 Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 J-EX8200 Switch Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 Chapter 19 Managing Junos OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Using the Configuration Tools in J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Using the CLI Viewer in the J-Web Interface to View Configuration Text . . . 343 Using the CLI Editor in the J-Web Interface to Edit Configuration Text . . . . . 343 Using the Point and Click CLI Tool in the J-Web Interface to Edit Configuration Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Using the Commit Options to Commit Configuration Changes (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Managing Junos OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Uploading a Configuration File (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 348 Uploading a Configuration File (J-Web Procedure) . . . . . . . . . . . . . . . . . . . 349 Managing Configuration Files Through the Configuration History (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Displaying Configuration History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Displaying Users Editing the Configuration . . . . . . . . . . . . . . . . . . . . . . . 351 Comparing Configuration Files with the J-Web Interface . . . . . . . . . . . . 351 Downloading a Configuration File with the J-Web Interface . . . . . . . . . 352 Loading a Previous Configuration File with the J-Web Interface . . . . . . 352 Loading a Previous Configuration File (CLI Procedure) . . . . . . . . . . . . . . . . . 352 Reverting to the Default Factory Configuration for the J-EX Series Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Reverting to the Default Factory Configuration by Using the LCD Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Reverting to the Default Factory Configuration by Using the load factory-default Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Reverting to the Rescue Configuration for the J-EX Series Switch . . . . . . . . 355 Setting or Deleting the Rescue Configuration (CLI Procedure) . . . . . . . . . . 356 Setting or Deleting the Rescue Configuration (J-Web Procedure) . . . . . . . . 357 Configuring Autoinstallation of Configuration Files (CLI Procedure) . . . . . . 357 Chapter 20 Verifying Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Verifying Autoinstallation Status on a J-EX Series Switch . . . . . . . . . . . . . . . . . . 361 xiv Table of Contents Chapter 21 Configuration Statements for Configuration File Management . . . . . . . . 363 archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 archive-sites (Configuration File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 commit synchronize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 configuration-servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 transfer-interval (Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 transfer-on-commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Chapter 22 Operational Commands for Configuration File Management . . . . . . . . . . 373 clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 clear system commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 file archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 file checksum md5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 file checksum sha1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 file checksum sha-256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 file compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 file copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 file delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 file list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 file rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 file show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 request system configuration rescue delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 request system configuration rescue save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 show system commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 show system configuration archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 show system configuration rescue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 show system rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 test configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Part 7 User and Access Management on J-EX Series Switches Chapter 23 User and Access Management on J-EX Series Switches Overview . . . . . . 403 J-EX Series Switch Software Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . 403 Understanding Software Infrastructure and Processes . . . . . . . . . . . . . . . . . . . . 404 Routing Engine and Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . 404 Junos OS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Chapter 24 User and Access Management Configuration . . . . . . . . . . . . . . . . . . . . . . . . 407 Configuring Management Access for the J-EX Series Switch (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Generating SSL Certificates to Be Used for Secure Web Access . . . . . . . . . . . . . 410 Configuring MS-CHAPv2 to Provide Password-Change Support (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Managing Users (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 xv Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Chapter 25 Troubleshooting User and Access Management . . . . . . . . . . . . . . . . . . . . . . 415 Troubleshooting Loss of the Root Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Chapter 26 Configuration Statements for User and Access Management . . . . . . . . . . 419 allow-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 allow-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 announcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 authentication (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 authentication-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 change-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 class (Assigning a Class to an Individual User) . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 class (Defining Login Classes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 deny-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 deny-configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 full-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 idle-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 login-alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 login-tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 maximum-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 minimum-changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 minimum-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 password (Login) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 radius-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 retry-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 root-authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 root-login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 tacplus-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 tacplus-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 traceoptions (Address-Assignment Pool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 uid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 user (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Chapter 27 Operational Commands for User and Access Management . . . . . . . . . . . 445 request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 show subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 Part 8 Junos OS for J-EX Series Switches System Services Chapter 28 System Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 DHCP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 DHCP Services for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . 457 DHCP/BOOTP Relay for J-EX Series Switches Overview . . . . . . . . . . . . . . . 458 Understanding Public Key Cryptography on Switches . . . . . . . . . . . . . . . . . . . . . 459 Public Key Infrastructure (PKI) and Digital Certificates . . . . . . . . . . . . . . . . 459 Understanding Self-Signed Certificates on J-EX Series Switches . . . . . . . . . . . 460 xvi Table of Contents Chapter 29 System Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Configuring DHCP Services (J-Web Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Configuring a DHCP SIP Server (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 466 Manually Generating Self-Signed Certificates on Switches (CLI Procedure) . . . 466 Generating a Public-Private Key Pair on Switches . . . . . . . . . . . . . . . . . . . . 467 Generating Self-Signed Certificates on Switches . . . . . . . . . . . . . . . . . . . . . 467 Enabling HTTPS and XNM-SSL Services on Switches Using Self-Signed Certificates (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Deleting Self-Signed Certificates (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . 468 Chapter 30 Monitoring System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Monitoring DHCP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Chapter 31 Configuration Statements for System Services . . . . . . . . . . . . . . . . . . . . . . 473 boot-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 boot-server (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 bootp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 ca-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 cache-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 cache-timeout-negative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 certification-authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 client-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 connection-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480 crl (Encryption Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 default-lease-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483 domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 domain-name (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 domain-search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 enrollment-retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 enrollment-url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 ftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 helpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 http . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 https . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 interface (BOOTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 interface (DNS and TFTP Packet Forwarding or Relay Agent) . . . . . . . . . . . . . . 494 ldap-url . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494 load-key-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 local-certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 maximum-certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 maximum-hop-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 maximum-lease-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 minimum-wait-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 xvii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 name-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 no-listen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 outbound-ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 path-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 port (HTTP/HTTPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 port (SRC Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 protocol-version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 server (DHCP and BOOTP Relay Agent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 server (DNS and TFTP Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 server-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 service-deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 sip-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 source-address (SRC Software) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 source-address-giaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 static-binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 system-generated-certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 tftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 traceoptions (DHCP Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 traceoptions (DNS and TFTP Packet Forwarding) . . . . . . . . . . . . . . . . . . . . . . . . 524 web-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 wins-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Chapter 32 Operational Commands for System Services . . . . . . . . . . . . . . . . . . . . . . . . 529 clear security pki local-certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 clear system services dhcp binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 clear system services dhcp conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 clear system services dhcp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 request ipsec switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 request security certificate (signed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 request security certificate (unsigned) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 request security key-pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537 request security pki generate-key-pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 request security pki local-certificate generate-self-signed . . . . . . . . . . . . . . . . . 539 show security pki local-certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 show system services dhcp binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 show system services dhcp conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 show system services dhcp global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 show system services dhcp pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548 show system services dhcp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 show system services service-deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 xviii Table of Contents telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555 Part 9 Junos OS for J-EX Series Switches System Monitoring Chapter 33 System Monitoring Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Understanding Alarm Types and Severity Levels on J-EX Series Switches . . . . . 559 Dashboard for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 System Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Health Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 Capacity Utilization Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 Alarms Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Chassis Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Chapter 34 Administering and Monitoring System Functions . . . . . . . . . . . . . . . . . . . . 569 Monitoring System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569 Checking Active Alarms with the J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . 572 Monitoring Chassis Alarms for a J-EX8200 Switch . . . . . . . . . . . . . . . . . . . . . . . 573 Monitoring Switch Control Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576 Monitoring System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 Monitoring Chassis Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 Monitoring System Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) . . 583 Cleaning Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Downloading Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Chapter 35 Configuration Statements for System Monitoring . . . . . . . . . . . . . . . . . . . . 587 facility-override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 file (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590 interface (Accounting or Sampling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 log-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591 match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592 structured-data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 time-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 time-zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 user (System Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 world-readable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599 Chapter 36 Operational Commands for System Monitoring . . . . . . . . . . . . . . . . . . . . . . 601 clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 file archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603 file checksum md5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 file checksum sha1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 file checksum sha-256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607 file compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 file copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611 xix Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 file delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612 file list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613 file rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 file show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615 monitor list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616 monitor start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617 monitor stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618 request chassis cb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619 request chassis fabric plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620 request chassis fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621 request system configuration rescue delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622 request system configuration rescue save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623 request system scripts refresh-from commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624 request system scripts refresh-from event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625 request system scripts refresh-from op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 show chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627 show chassis environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629 show chassis environment cb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631 show chassis environment fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 show chassis environment routing-engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 show chassis ethernet-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639 show chassis fabric fpcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644 show chassis fabric map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646 show chassis fabric plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649 show chassis fabric plane-location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651 show chassis fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 show chassis hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 show chassis led . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 show chassis location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 show chassis pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665 show chassis routing-engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668 show chassis temperature-thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671 show log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673 show pfe next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675 show pfe route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677 show pfe statistics ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679 show pfe statistics ip6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682 show pfe terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685 show system alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686 show system audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687 show system buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689 show system connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 show system core-dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696 show system directory-usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698 show system processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700 xx Table of Contents Part 10 J-EX4200 and J-EX4500 Virtual Chassis Chapter 37 J-EX4200 and J-EX4500 Virtual Chassis—Overview, Components, and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 J-EX4200 and J-EX4500 Virtual Chassis Overview . . . . . . . . . . . . . . . . . . . . . . . 709 Basic Configuration of a Virtual Chassis with Master and Backup Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Expanding Configurations—Within a Single Wiring Closet and Across Wiring Closets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Global Management of Member Switches in a Virtual Chassis . . . . . . . . . . . 711 High Availability Through Redundant Routing Engines . . . . . . . . . . . . . . . . . . 711 Adaptability as an Access Switch or Distribution Switch . . . . . . . . . . . . . . . . 712 Understanding J-EX4200 and J-EX4500 Virtual Chassis Components . . . . . . . . 712 Virtual Chassis Ports (VCPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 Master Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Backup Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 Linecard Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Member Switch and Member ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Mastership Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Virtual Chassis Identifier (VCID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 Understanding How the Master in a J-EX4200 or J-EX4500 Virtual Chassis Is Elected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Understanding Software Upgrade in a J-EX4200 or J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Understanding Global Management of a J-EX4200 or J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Understanding Nonvolatile Storage in a J-EX4200 or J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Nonvolatile Memory Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Understanding the High-Speed Interconnection of the J-EX4200 and J-EX4500 Virtual Chassis Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 Understanding J-EX4200 and J-EX4500 Virtual Chassis Link Aggregation . . . . . 721 Understanding J-EX4200 and J-EX4500 Virtual Chassis Configuration . . . . . . . 723 Understanding J-EX4200 and J-EX4500 Virtual Chassis Switch Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724 Understanding Fast Failover in a J-EX4200 Virtual Chassis . . . . . . . . . . . . . . . . . 725 Supported Topologies for Fast Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 How Fast Failover Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725 Fast Failover in a Ring Topology Using Dedicated VCPs . . . . . . . . . . . . . 725 Fast Failover in a Ring Topology Using Uplink Module VCPs . . . . . . . . . 727 Fast Failover in a Virtual Chassis Configuration Using Multiple Ring Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729 Effects of Topology Changes on a Fast Failover Configuration . . . . . . . . . . . 730 Understanding Split and Merge in a J-EX4200 or J-EX4500 Virtual Chassis . . . . 731 What Happens When a Virtual Chassis Configuration Splits . . . . . . . . . . . . . 731 Merging Virtual Chassis Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732 Understanding Automatic Software Update on J-EX4200 and J-EX4500 Virtual Chassis Member Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734 xxi Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Chapter 38 J-EX4200 and J-EX4500 Virtual Chassis—Configuration Examples . . . . 735 Example: Configuring a J-EX4200 Virtual Chassis with a Master and Backup in a Single Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736 Example: Configuring a J-EX4500 Virtual Chassis with a Master and Backup in a Single Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740 Example: Expanding a J-EX4200 Virtual Chassis in a Single Wiring Closet . . . . 745 Example: Adding a J-EX4500 Switch to a Nonprovisioned Virtual Chassis . . . . 750 Example: Adding J-EX4500 Switches to a Preprovisioned Virtual Chassis . . . . . 754 Example: Setting Up a Multimember J-EX4200 Virtual Chassis Access Switch with a Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 Example: Configuring a J-EX4200 Virtual Chassis Interconnected Across Multiple Wiring Closets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762 Example: Connecting J-EX4500 Member Switches in a Virtual Chassis Across Wiring Closets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770 Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a J-EX4200 Virtual Chassis Access Switch and a J-EX4200 Virtual Chassis Distribution Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777 Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a J-EX4200 Virtual Chassis Access Switch and a J-EX4200 Virtual Chassis Distribution Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 Example: Configuring a J-EX4200 Virtual Chassis Using a Preprovisioned Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788 Example: Configuring a Preprovisioned Mixed J-EX4200 and J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799 Example: Configuring Fast Failover on Uplink Module VCPs to Reroute Traffic When a J-EX4200 Virtual Chassis Switch or Intermember Link Fails . . . . . 804 Example: Assigning the Virtual Chassis ID to Determine Precedence During a J-EX4200 Virtual Chassis Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807 Example: Configuring Link Aggregation Groups Using J-EX4200 Uplink Virtual Chassis Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809 Example: Configuring Automatic Software Update on J-EX4200 Virtual Chassis Member Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818 Chapter 39 Configuring J-EX4200 and J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . 821 Configuring a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . 822 Configuring a J-EX4200 or J-EX4500 Virtual Chassis with a Preprovisioned Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823 Configuring a J-EX4200 or J-EX4500 Virtual Chassis with a Nonprovisioned Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824 Configuring a J-EX4200 Virtual Chassis (J-Web Procedure) . . . . . . . . . . . . . . . . 826 Configuring a Mixed J-EX4200 and J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828 xxii Table of Contents Installing Software on a Mixed J-EX4200 and J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831 Adding a New Switch to an Existing J-EX4200 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 Adding a New Switch to an Existing Virtual Chassis Within the Same Wiring Closet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832 Adding a New Switch from a Different Wiring Closet to an Existing Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833 Adding a New Switch to an Existing Preprovisioned Virtual Chassis Using Autoprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835 Adding a J-EX4200 Switch to a Preprovisioned J-EX4500 Virtual Chassis or a Preprovisioned Mixed J-EX4200 and J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837 Adding a J-EX4500 Switch to a Preprovisioned J-EX4200 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838 Adding a J-EX4500 Switch to a Nonprovisioned J-EX4200 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840 Replacing a Member Switch of a J-EX4200 or J-EX4500 Virtual Chassis Configuration (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841 Remove, Repair, and Reinstall the Same Switch . . . . . . . . . . . . . . . . . . . . . . 841 Remove a Member Switch, Replace It with a Different Switch, and Reapply the Old Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842 Remove a Member Switch and Make Its Member ID Available for Reassignment to a Different Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842 Removing a J-EX4200 or J-EX4500 Switch From a Mixed J-EX4200 and J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . 843 Configuring Mastership of the J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844 Configuring Mastership Using a Preprovisioned Configuration File . . . . . . . 844 Configuring Mastership Using a Configuration File That Is Not Preprovisioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845 Setting an Uplink Module Port on a J-EX4200 Switch as a Virtual Chassis Port (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846 Setting an Uplink VCP Between Two J-EX4200 Member Switches . . . . . . 848 Setting an Uplink VCP on a Standalone Switch . . . . . . . . . . . . . . . . . . . . . . 848 Setting an SFP+ Port as a Virtual Chassis Port on a J-EX4500 Switch (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 Setting a J-EX4200 Uplink Module Port as a Virtual Chassis Port Using the LCD Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850 Configuring the Virtual Management Ethernet Interface for Global Management of a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . 852 Configuring the Timer for the Backup Member to Start Using Its Own MAC Address, as Master of the J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852 Configuring Fast Failover in a J-EX4200 Virtual Chassis . . . . . . . . . . . . . . . . . . . 853 Disabling Fast Failover in a J-EX4200 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . 854 Disabling Split and Merge in a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854 xxiii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Assigning the Virtual Chassis ID to Determine Precedence During a J-EX4200 or J-EX4500 Virtual Chassis Merge (CLI Procedure) . . . . . . . . . . . . . . . . . . 855 Configuring Automatic Software Update on J-EX4200 or J-EX4500 Virtual Chassis Member Switches (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . 855 Configuring Graceful Routing Engine Switchover in a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856 Chapter 40 Verifying J-EX4200 and J-EX4500 Virtual Chassis Configuration . . . . . . 857 Command Forwarding Usage with a J-EX4200 or J-EX4500 Virtual Chassis . . 857 Verifying the Member ID, Role, and Neighbor Member Connections of a J-EX4200 or J-EX4500 Virtual Chassis Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860 Verifying That Virtual Chassis Ports on a J-EX4200 or J-EX4500 Switch Are Operational . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862 Monitoring J-EX4200 and J-EX4500 Virtual Chassis Status and Statistics . . . . 863 Verifying the Setting for the Virtual Chassis Mode on J-EX4200 and J-EX4500 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Verifying the Setting for the PIC Mode on a J-EX4500 Switch in a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Verifying That Graceful Routing Engine Switchover Is Working in the J-EX4200 or J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Chapter 41 Troubleshooting J-EX4200 and J-EX4500 Virtual Chassis . . . . . . . . . . . . 869 Troubleshooting a J-EX4200 or J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . 869 A Disconnected Member Switch's ID Is Not Available for Reassignment . . 869 Load Factory Default Does Not Commit on a Multimember Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869 The Member ID Persists When a Member Switch Is Disconnected From a Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870 Chapter 42 Configuration Statements for J-EX4200 and J-EX4500 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871 [edit virtual-chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . 871 auto-sw-update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872 fast-failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873 graceful-switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874 id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874 location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875 mac-persistence-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876 mastership-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877 member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878 no-management-vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879 no-split-detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880 package-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881 preprovisioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882 redundancy (Graceful Switchover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883 role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884 serial-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886 traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887 virtual-chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889 xxiv Table of Contents Chapter 43 Operational Commands for J-EX4200 and J-EX4500 Virtual Chassis . . 891 clear virtual-chassis vc-port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892 request chassis pic-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893 request session member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895 request virtual-chassis mode mixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896 request virtual-chassis recycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898 request virtual-chassis renumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899 request virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900 request virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901 show chassis pic-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902 show system uptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903 show virtual-chassis active-topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905 show virtual-chassis fast-failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907 show virtual-chassis mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908 show virtual-chassis status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910 show virtual-chassis vc-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912 show virtual-chassis vc-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914 show virtual-chassis vc-port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917 Part 11 High Availability Chapter 44 High Availability—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925 High Availability Features for J-EX Series Switches Overview . . . . . . . . . . . . . . . 925 VRRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925 Graceful Protocol Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926 Redundant Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926 Graceful Routing Engine Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927 Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927 Nonstop Active Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927 Nonstop Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928 Understanding VRRP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 928 Overview of VRRP on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . 928 Examples of VRRP Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929 Understanding Nonstop Active Routing on J-EX Series Switches . . . . . . . . . . . . 931 Understanding Nonstop Software Upgrade on J-EX Series Switches . . . . . . . . . 932 How an NSSU Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932 Standalone Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933 Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934 NSSU and Junos OS Release Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935 Overview of NSSU Configuration and Operation . . . . . . . . . . . . . . . . . . . . . 935 Understanding Power Management on J-EX Series Switches . . . . . . . . . . . . . . . 935 Power Priority of Line Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936 Power Supply Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938 Chapter 45 Examples of High Availability Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 941 Example: Configuring Nonstop Active Routing on J-EX Series Switches . . . . . . . 941 Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on J-EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944 xxv Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Chapter 46 Configuring High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947 Configuring VRRP for IPv6 (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947 Configuring Nonstop Active Routing on J-EX Series Switches (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948 Tracing Nonstop Active Routing Synchronization Events . . . . . . . . . . . . . . . . . . 949 Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951 Configuring Power Supply Redundancy (CLI Procedure) . . . . . . . . . . . . . . . . . . . 952 Configuring the Power Priority of Line Cards (CLI Procedure) . . . . . . . . . . . . . . . 953 Chapter 47 Administering High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955 Upgrading Software on a J-EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955 Preparing the Switch for Software Installation . . . . . . . . . . . . . . . . . . . . . . . 955 Upgrading Both Routing Engines Using NSSU . . . . . . . . . . . . . . . . . . . . . . . 957 Upgrading One Routing Engine Using NSSU . . . . . . . . . . . . . . . . . . . . . . . . . 959 Upgrading the Original Master Routing Engine . . . . . . . . . . . . . . . . . . . . . . . 961 Verifying Power Configuration and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962 Chapter 48 Configuration Statements for High Availability . . . . . . . . . . . . . . . . . . . . . . 965 commit synchronize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965 fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966 fpcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967 graceful-switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968 inet6-advertise-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968 n-plus-n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 nonstop-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969 nssu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970 power-budget-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 preempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971 priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972 psu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972 redundancy (Graceful Switchover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973 redundancy (Power Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973 traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974 upgrade-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976 virtual-inet6-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 virtual-link-local-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977 vrrp-inet6-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978 Chapter 49 Operational Commands for High Availability . . . . . . . . . . . . . . . . . . . . . . . . 979 request system software nonstop-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980 show chassis nonstop-upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985 show chassis power-budget-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986 show vrrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 xxvi Table of Contents Part 12 Interfaces on J-EX Series Switches Chapter 50 Interfaces—Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 J-EX Series Switches Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999 Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000 Understanding Interface Naming Conventions on J-EX Series Switches . . . . . . 1001 Physical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 Logical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003 Wildcard Characters in Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003 Understanding Aggregated Ethernet Interfaces and LACP . . . . . . . . . . . . . . . . 1003 Link Aggregation Group (LAG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004 Link Aggregation Control Protocol (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . 1005 Understanding Interface Ranges on J-EX Series Switches . . . . . . . . . . . . . . . . . 1005 Understanding Layer 3 Subinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007 Understanding Unicast RPF for J-EX Series Switches . . . . . . . . . . . . . . . . . . . . 1008 Unicast RPF for J-EX Series Switches Overview . . . . . . . . . . . . . . . . . . . . . 1008 Unicast RPF Implementation for J-EX Series Switches . . . . . . . . . . . . . . . 1009 Unicast RPF Packet Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009 Bootstrap Protocol (BOOTP) and DHCP Requests . . . . . . . . . . . . . . . 1009 Default Route Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009 When to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009 When Not to Enable Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010 Limitations of the Unicast RPF Implementation on J-EX4200 Switches . . . 1011 Understanding IP Directed Broadcast for J-EX Series Switches . . . . . . . . . . . . . 1012 IP Directed Broadcast for J-EX Series Switches Overview . . . . . . . . . . . . . . 1012 IP Directed Broadcast Implementation for J-EX Series Switches . . . . . . . . 1013 When to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013 When Not to Enable IP Directed Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . 1013 802.1Q VLANs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013 Chapter 51 Examples of Interfaces Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015 Example: Configuring Aggregated Ethernet High-Speed Uplinks Between a J-EX4200 Virtual Chassis Access Switch and a J-EX4200 Virtual Chassis Distribution Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015 Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between a J-EX4200 Virtual Chassis Access Switch and a J-EX4200 Virtual Chassis Distribution Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021 Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026 Example: Configuring Unicast RPF on a J-EX Series Switch . . . . . . . . . . . . . . . . 1033 Example: Configuring IP Directed Broadcast on a J-EX Series Switch . . . . . . . . 1037 Chapter 52 Configuring Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041 Configuring Gigabit Ethernet Interfaces (CLI Procedure) . . . . . . . . . . . . . . . . . . 1042 Configuring VLAN Options and Port Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 1042 Configuring the Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043 xxvii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Configuring the IP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044 Configuring Gigabit Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . . . . 1045 Port Role Configuration with the J-Web Interface (with CLI References) . . . . . . 1051 Adding an Interface Description to the Configuration . . . . . . . . . . . . . . . . . . . . . 1055 Example: Adding an Interface Description to the Configuration . . . . . . . . . 1055 Adding a Logical Unit Description to the Configuration . . . . . . . . . . . . . . . . . . . 1056 Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 Example: Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057 Disabling a Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058 Configuring Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058 Configuring the Interface Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059 Configuring Interface IPv4 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060 Configuring Interface IPv6 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061 Configuring the Interface Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061 Configuring the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062 Setting the Protocol MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065 Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066 Configuring Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066 Expanding Interface Range Member and Member Range Statements . . . 1069 Configuration Inheritance for Member Interfaces . . . . . . . . . . . . . . . . . . . . 1070 Member Interfaces Inheriting Configuration from Configuration Groups . . . 1071 Interfaces Inheriting Common Configuration . . . . . . . . . . . . . . . . . . . . . . . . 1073 Configuring Inheritance Range Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073 Configuration Expansion Where Interface Range Is Used . . . . . . . . . . . . . . 1073 Configuring Accounting for the Physical Interface . . . . . . . . . . . . . . . . . . . . . . . 1074 Applying an Accounting Profile to the Physical Interface . . . . . . . . . . . . . . 1075 Example: Applying an Accounting Profile to the Physical Interface . . . 1075 Configuring Accounting for the Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . 1076 Applying an Accounting Profile to the Logical Interface . . . . . . . . . . . . . . . 1076 Example: Applying an Accounting Profile to the Logical Interface . . . . 1076 Configuring Ethernet Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077 Configuring Gratuitous ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078 Configuring Static ARP Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078 Example: Configuring Static ARP Table Entries . . . . . . . . . . . . . . . . . . . . . . 1079 Disabling the Transmission of Redirect Messages on an Interface . . . . . . . . . . . 1079 Configuring Unrestricted Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080 Enabling or Disabling SNMP Notifications on Logical Interfaces . . . . . . . . . . . . 1080 Enabling or Disabling SNMP Notifications on Physical Interfaces . . . . . . . . . . . 1080 Configuring Aggregated Ethernet Interfaces (CLI Procedure) . . . . . . . . . . . . . . . 1081 Configuring Aggregated Ethernet Interfaces (J-Web Procedure) . . . . . . . . . . . . 1082 Configuring Aggregated Ethernet LACP (CLI Procedure) . . . . . . . . . . . . . . . . . . 1085 Configuring Aggregated Ethernet Link Protection . . . . . . . . . . . . . . . . . . . . . . . 1086 Configuring Link Protection for Aggregated Ethernet Interfaces . . . . . . . . 1086 Configuring Primary and Backup Links for Link Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086 Reverting Traffic to a Primary Link When Traffic is Passing Through a Backup Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087 Disabling Link Protection for Aggregated Ethernet Interfaces . . . . . . . . . . . 1087 Configuring Aggregated Ethernet Link Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087 xxviii Table of Contents Configuring Aggregated Ethernet Minimum Links . . . . . . . . . . . . . . . . . . . . . . . 1088 Configuring Tagged Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . 1088 Configuring a Layer 3 Subinterface (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . 1089 Configuring Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089 Disabling Unicast RPF (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091 Configuring IP Directed Broadcast (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . 1091 Tracing Operations of an Individual Router or Switch Interface . . . . . . . . . . . . . 1092 Tracing Operations of the Interface Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093 Setting the Mode on an SFP+ Uplink Module (CLI Procedure) . . . . . . . . . . . . . 1093 Chapter 53 Verifying Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095 Monitoring Interface Status and Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095 Verifying the Status of a LAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096 Verifying That LACP Is Configured Correctly and Bundle Members Are Exchanging LACP Protocol Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097 Verifying the LACP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097 Verifying That LACP Packets Are Being Exchanged . . . . . . . . . . . . . . . . . . . 1097 Verifying That Layer 3 Subinterfaces Are Working . . . . . . . . . . . . . . . . . . . . . . . 1098 Verifying Unicast RPF Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099 Verifying IP Directed Broadcast Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101 Chapter 54 Troubleshooting Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103 Troubleshooting Network Interfaces on J-EX4200 Switches . . . . . . . . . . . . . . . 1103 The interface on the port in which an SFP or SFP+ transceiver is installed in an SFP+ uplink module is down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103 Troubleshooting an Aggregated Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . 1104 Troubleshooting Interface Configuration and Cable Faults . . . . . . . . . . . . . . . . . 1104 Interface Configuration or Connectivity Is Not Working . . . . . . . . . . . . . . . . 1104 Troubleshooting Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105 Legitimate Packets Are Discarded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105 Troubleshooting Virtual Chassis Port Connectivity on a J-EX4200 Switch . . . . 1106 Virtual Chassis port (VCP) connection does not work . . . . . . . . . . . . . . . . . 1106 Diagnosing a Faulty Twisted-Pair Cable (CLI Procedure) . . . . . . . . . . . . . . . . . . 1106 Chapter 55 Configuration Statements for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111 [edit chassis] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . 1111 [edit interfaces] Configuration Statement Hierarchy . . . . . . . . . . . . . . . . . . . . . . 1112 802.3ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117 accounting-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119 aggregated-devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120 aggregated-ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121 arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122 auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123 bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124 broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125 chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127 device-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128 disable (Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1129 xxix Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130 ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131 eui-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131 family (for J-EX Series switches) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132 filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136 flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 force-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137 gratuitous-arp-reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138 interface-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139 interfaces (for J-EX Series switches) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141 lacp (802.3ad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148 lacp (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149 link-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150 link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151 link-speed (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152 loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) . . . . . . . 1153 member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153 members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154 member-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155 minimum-links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156 mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157 native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158 no-redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159 periodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160 pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161 pic-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161 port-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162 preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163 primary (Address on Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164 proxy-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165 rpf-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166 sfpplus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167 speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168 targeted-broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1169 traceoptions (Individual Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170 traceoptions (Interface Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172 traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173 unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174 vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175 vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176 vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177 Chapter 56 Operational Commands for Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1179 clear ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180 monitor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181 request diagnostics tdr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188 show diagnostics tdr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1190 show ethernet-switching interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195 show interfaces diagnostics optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1199 xxx Table of Contents show interfaces ge- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204 show interfaces me0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215 show interfaces queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1222 show interfaces xe- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228 show ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241 show lacp interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243 test interface restart-auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247 Part 13 Index Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251 xxxi Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 xxxii About This Guide • How to Use This Guide on page xxxiii • Downloading Software on page xxxiv • Documentation Symbols Key on page xxxv • Repair and Warranty on page xxxvi • Requesting Technical Support on page xxxvi How to Use This Guide This guide, the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 1, provides the following information about the Junos Operating System (Junos OS) for J-EX Series switches: product overview, complete software configuration statement hierarchy, software installation, user interfaces, system setup, configuration file management, user access management, system services, system monitoring, Virtual Chassis, high availability, and interfaces. For additional J-EX Series software information, see Volume 2. To download the Dell PowerConnect J-EX Series documentation listed in Table 1 on page xxxiii, see the following Dell support website: http://www.support.dell.com/manuals Table 1: List of J-EX Series Guides Title Description Dell PowerConnect J-Series J-EX4500 Ethernet Switch Hardware Guide Component descriptions, site preparation, installation, replacement, and safety and compliance information for J-EX4500 switches Dell PowerConnect J-Series J-EX4200 Ethernet Switch Hardware Guide Component descriptions, site preparation, installation, replacement, and safety and compliance information for J-EX4200 switches Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide Component descriptions, site preparation, installation, replacement, and safety and compliance information for J-EX8208 switches Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide Component descriptions, site preparation, installation, replacement, and safety and compliance information for J-EX8216 switches xxxiii Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 1: List of J-EX Series Guides (continued) Title Description Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 1 Junos OS for J-EX Series switches product overviews and complete software configuration statement hierarchy—plus feature descriptions, configuration examples, instructions, and reference pages for software installation, user interfaces, system setup, configuration file management, user access management, system services, system monitoring, Virtual Chassis, high availability, and interfaces Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 Junos OS for J-EX Series switches feature descriptions, configuration examples, instructions, and reference pages for Layer 2 bridging and Virtual LANs (VLANs), spanning-tree protocols, Layer 3 protocols, IGMP snooping and multicast, access control, rate limiting, port security, routing policy and packet filtering (firewall filters), class of service (CoS), fibre channel over Ethernet (FCoE), MPLS, and network management and monitoring To download additional Junos OS documentation for J-EX Series and all other PowerConnect J-Series products, see the following Juniper Networks support website: http://www.juniper.net/support/partners/dell. If the information in the latest release notes differs from the information in the documentation, follow the release notes. Downloading Software You can download Junos OS for J-EX Series switches from the Download Software area at juniper.net/support/csc/swdist-domestic/. To download the software, you must have a Juniper Networks user account. For information about obtaining an account, see http://www.support.dell.com. xxxiv About This Guide Documentation Symbols Key Notice Icons Icon Meaning Description Informational note Indicates important features or instructions. Caution Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser. Text and Syntax Conventions Convention Description Examples Bold text like this Represents text that you type. To enter configuration mode, type the configure command: user@host> configure Fixed-width text like this Italic text like this Represents output that appears on the terminal screen. user@host> show chassis alarms • Introduces important new terms. • • Identifies book names. A policy term is a named structure that defines match conditions and actions. • Identifies RFC and Internet draft titles. • Junos System Basics Configuration Guide • RFC 1997, BGP Communities Attribute No alarms currently active Represents variables (options for which you substitute a value) in commands or configuration statements. Configure the machine’s domain name: Represents names of configuration statements, commands, files, and directories; IP addresses; configuration hierarchy levels; or labels on routing platform components. • To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level. • The console port is labeled CONSOLE. < > (angle brackets) Enclose optional keywords or variables. stub; | (pipe symbol) Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity. broadcast | multicast Italic text like this Plain text like this [edit] root@# set system domain-name domain-name (string1 | string2 | string3) xxxv Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Text and Syntax Conventions Convention Description Examples # (pound sign) Indicates a comment specified on the same line as the configuration statement to which it applies. rsvp { # Required for dynamic MPLS only [ ] (square brackets) Enclose a variable for which you can substitute one or more values. community name members [ community-ids ] Indention and braces ( { } ) Identify a level in the configuration hierarchy. ; (semicolon) Identifies a leaf statement at a configuration hierarchy level. [edit] routing-options { static { route default { nexthop address; retain; } } } J-Web GUI Conventions Bold text like this Represents J-Web graphical user interface (GUI) items you click or select. > (bold right angle bracket) Separates levels in a hierarchy of J-Web selections. • In the Logical Interfaces box, select All Interfaces. • To cancel the configuration, click Cancel. In the configuration editor hierarchy, select Protocols>Ospf. Repair and Warranty CAUTION: Many repairs may only be done by a certified service technician. You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your warranty. Read and follow the safety instructions that came with the product. For more information, see “Getting Help” in the hardware guide for your Dell PowerConnect J-EX Series Ethernet Switch. Requesting Technical Support For technical support, see http://www.support.dell.com. For more information, see “Getting Help” in the hardware guide for your Dell PowerConnect J-EX Series Ethernet Switch. xxxvi PART 1 Junos OS for J-EX Series Switches Product Overview • Software Overview on page 3 • Supported Hardware on page 29 1 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 2 CHAPTER 1 Software Overview • J-EX Series Switch Software Features Overview on page 3 • Layer 3 Protocols Supported on J-EX Series Switches on page 17 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 18 • Security Features for J-EX Series Switches Overview on page 20 • High Availability Features for J-EX Series Switches Overview on page 22 • Understanding Software Infrastructure and Processes on page 25 J-EX Series Switch Software Features Overview The following tables list the J-EX Series Switches software features, the Junos operating system (Junos OS) release in which they were introduced, and the first Junos OS release for each switch: • Table 2 on page 4—First Junos OS Release for Each J-EX Series Switch • Table 3 on page 4—Access Control Features • Table 4 on page 5—Administration Features • Table 5 on page 5—Class-of-Service (CoS) Features • Table 6 on page 6—Device Security Features • Table 7 on page 6—Fibre Channel over Ethernet Features • Table 8 on page 7—High Availability and Resiliency Features • Table 9 on page 8—Interfaces Features • Table 10 on page 9—IP Address Management Features • Table 11 on page 9—IPv6 Features • Table 12 on page 10—Layer 2 Network Protocols Features • Table 13 on page 10—Layer 3 Protocols Features • Table 14 on page 12—MPLS Features • Table 15 on page 12—Multicast Features • Table 16 on page 13—Network Management and Monitoring Features 3 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Table 17 on page 14—Port Security Features • Table 18 on page 15—Routing Policy and Packet Filtering Features • Table 19 on page 15—Spanning-Tree Protocols Features • Table 20 on page 16—System Management Features The Junos OS release for software features on a switch cannot be earlier than the first Junos OS release for that switch. Table 2: First Junos OS Release for Each J-EX Series Switch Switch Junos OS Release J-EX4200 switches Junos OS Release 10.2R1 J-EX4200 Virtual Chassis Junos OS Release 10.2R1 J-EX4500 switches Junos OS Release 11.1R2 J-EX4500 Virtual Chassis and mixed J-EX4200 and J-EX4500 Virtual Chassis Junos OS Release 11.1R2 NOTE: A mixed J-EX4200 and J-EX4500 Virtual Chassis supports the same features as a J-EX4500 Virtual Chassis. J-EX8208 switches Junos OS Release 10.2R1 J-EX8216 switches Junos OS Release 10.2R1 NOTE: In the features tables, software features that run on J-EX4200 Virtual Chassis are indicated in the column headed "J-EX4200 Switches.” If the feature is only for a J-EX4200 Virtual Chassis and not for a standalone switch, the column entry includes "(J-EX4200 Virtual Chassis only)". Table 3: Access Control Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches 802.1X authentication (port-based, multiple supplicant) 10.2R1 Not supported Not supported 10.2R1 802.1X authentication with VLAN assignment, VoIP VLAN support 10.2R1 Not supported Not supported 10.3R1 802.1X user-based dynamic firewall filters 10.2R1 Not supported Not supported 10.3R1 802.1X user-based dynamic firewall filters on multiple-supplicant ports 10.2R1 Not supported Not supported 10.3R1 Feature 4 Chapter 1: Software Overview Table 3: Access Control Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Authentication fallback 10.3R1 Not supported Not supported Not supported Captive portal authentication for Layer 3 interfaces 10.2R1 Not supported Not supported Not supported Captive portal authentication for Layer 2 interfaces 10.3R1 Not supported Not supported Not supported MAC RADIUS authentication 10.2R1 10.2R1 11.1R2 10.3R1 NetBIOS snooping 11.1R2 Not supported Not supported 11.1R2 Server fail fallback 10.2R1 11.1R2 11.1R2 10.2R1 TACACS+ 10.2R1 11.1R2 11.1R2 10.2R1 Table 4: Administration Features by Junos OS Release Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches System logging (syslog) over IPv4 10.2R1 11.1R2 11.1R2 10.2R1 System logging (syslog) over IPv6 10.2R1 11.1R2 Not supported 10.2R1 System snapshot 10.2R1 11.1R2 Not supported 10.2R1 Table 5: Class-of-Service (CoS) Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Class of service (CoS)—Class-based queuing with prioritization, Layer 2 and Layer 3 classification, rewrite, and queueing; strict priority queuing on egress 10.2R1 11.1R2 11.1R2 10.2R1 CoS—DSCP, IEEE 802.1p, and IP precedence packet rewrites on routed VLAN interfaces (RVIs) 10.2R1 11.1R2 11.1R2 10.2R1 CoS—Interface-specific classifiers on routed VLAN interfaces (RVIs) 10.2R1 Not supported Not supported 10.2R1 CoS—multidestination Not applicable Not applicable Not applicable 10.2R1 CoS—per-interface classification 10.2R1 11.1R2 11.1R2 10.2R1 Feature 5 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 5: Class-of-Service (CoS) Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches CoS support on LAGs 10.2R1 11.1R2 Not supported 10.2R1 CoS support on routed VLAN interfaces (RVIs) 10.2R1 11.1R2 Not supported 10.2R1 Interface-specific CoS rewrite rules 10.2R1 Not supported Not supported 10.2R1 Junos EZQoS for CoS 10.2R1 11.1R2 11.1R2 10.2R1 Port shaping and queue shaping 10.2R1 11.1R2 11.1R2 10.1R1 Remarking of bridged packets 10.2R1 11.1R2 11.1R2 10.2R1 Scheduled deficit weighted round robin (SDWRR) 10.2R1 11.1R2 11.1R2 10.2R1 Single-rate two-color marking 10.2R1 11.1R2 11.1R2 10.2R1 Table 6: Device Security Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Automatic recovery for port error disable conditions 10.2R1 11.1R2 11.1R2 10.0R1 Storm control (broadcast and unicast) 10.2R1 11.1R2 11.1R2 10.2R1 Storm control (multicast) 10.3R2 11.1R2 Not supported 10.3R2 Unknown Layer 2 unicast forwarding 10.2R1 11.1R2 Not supported 10.2R1 Feature Table 7: Fibre Channel over Ethernet Features by Junos OS Release 6 Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches FIP snooping Not supported 11.1R2 Not supported Not supported Priority-based flow control (PFC) Not supported 11.1R2 Not supported Not supported Chapter 1: Software Overview Table 8: High Availability and Resiliency Features by Junos OS Release Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Graceful protocol restart for BGP 10.2R1 Not applicable 11.1R2 9.4R1 Graceful protocol restart for IS-IS 10.2R1 Not applicable 11.1R2 9.4R1 Graceful protocol restart for OSPF 10.2R1 Not applicable 11.1R2 9.4R1 Graceful Routing Engine switchover (GRES) for Virtual Chassis 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable Not supported Not applicable GRES for ARP entries, forwarding database, and Layer 3 Protocols 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 10.2R1 GRES for port security (DHCP snooping, DAI, and IP source guard) 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable Not supported 10.2R1 LACP support for dual-homing applications in data centers 10.2R1 11.1R2 11.1R2 10.2R1 Link Aggregation Control Protocol (LACP) 10.2R1 11.1R2 11.1R2 10.2R1 Link aggregation groups (LAGs) 10.2R1 11.1R2 11.1R2 10.2R1 Link aggregation groups (LAGs) over Virtual Chassis ports (VCPs) 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable Not supported Not applicable Nonstop active routing (NSR) for OSPFv2 11.1R2 Not applicable Not applicable 10.4R1 Nonstop active routing (NSR) for BGP, IS-IS, IGMP with BFD, and RIP 11.1R2 (J-EX4200 Virtual Chassis) Not applicable 11.1R2 11.1R2 Nonstop active routing (NSR) for IPv4 and IPv6 Not supported Not supported Not supported Not supported Nonstop software upgrade (NSSU) Not applicable Not applicable Not supported 10.4R1 Power budget management Not applicable Not applicable Not supported 10.2R1 Redundant trunk groups 10.2R1 Not supported Not supported 10.2R1 Virtual Chassis fast failover 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable Not supported Not applicable 7 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 8: High Availability and Resiliency Features by Junos OS Release (continued) J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Virtual Chassis split and merge 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 Not applicable Virtual Chassis 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 Not applicable Virtual Chassis—Autoprovisioning of Virtual Chassis ports (VCPs) 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 Not applicable Virtual Chassis—SFP uplink module port interconnection of member switches 10.2R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 Not applicable Virtual Router Redundancy Protocol (VRRP) 10.2R1 11.1R2 11.1R2 10.2R1 Virtual Router Redundancy Protocol (VRRP) for IPv6 (except authentication type and authentication key) 10.2R1 Not supported Not supported 10.2R1 Feature • Automatic software update on prospective member switches • Front-panel configuration of uplink module ports as Virtual Chassis ports (VCPs) Table 9: Interfaces Features by Junos OS Release 8 Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Digital optical monitoring (DOM) 10.2R1 Not supported Not supported 10.2R1 Interface ranges 10.2R1 11.1R2 Not supported 10.2R1 Power over Ethernet (PoE) 10.2R1 Not applicable Not applicable Not applicable Power over Ethernet Plus (PoE+) Not supported Not applicable Not applicable Not applicable Power over Ethernet (PoE) power management mode 10.2R1 Not applicable Not applicable Not applicable Reflective relay Not supported 11.1R2 Not supported Not supported Time domain reflectometry (TDR) 10.2R1 11.1R2 11.1R2 10.2R1 Chapter 1: Software Overview Table 9: Interfaces Features by Junos OS Release (continued) J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Unicast reverse-path forwarding (RPF) 10.2R1 Not supported Not supported 10.2R1 VLAN-tagged Layer 3 subinterfaces 10.2R1 Not supported Not supported 10.2R1 Feature Table 10: IP Address Management Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches DHCP server and relay with option 82 for Layer 2 VLANs 10.2R1 11.1R2 11.1R2 10.2R1 DHCP server and relay with option 82 for Layer 3 interfaces 10.2R1 11.1R2 11.1R2 10.2R1 DNS for IPv6 10.2R1 Not supported Not supported Not supported Local DHCP server 9.3R2 Not supported Not supported 10.2R1 Static addresses 10.2R1 11.1R2 Not supported 10.2R1 J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Feature Table 11: IPv6 Features by Junos OS Release Feature J-EX4200 Switches NOTE: A separate software license is required for IPv6. See “Understanding Software Licenses for J-EX Series Switches” on page 76. IPv6 CoS (multifield classification and rewrite) 10.2R1 11.1R2 Not supported 10.4R1 IPv6 management and services 10.2R1 11.1R2 Not supported 10.2R1 IPv6 multicast protocols (PIM, MLDv1/v2) 10.2R1 11.1R2 Not supported 10.2R1 IPv6 path MTU discovery 10.2R1 11.1R2 Not supported 10.2R1 IS-IS for IPv6 10.2R1 Not supported Not supported 10.2R1 RIPng 10.2R1 11.1R2 Not supported 10.2R1 OSPFv3 10.2R1 11.1R2 Not supported 10.2R1 9 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 12: Layer 2 Network Protocols Features by Junos OS Release Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches 802.1Q VLAN tagging 10.2R1 11.1R2 11.1R2 10.2R1 Layer 2 protocol tunneling (L2PT) 10.2R1 Not supported Not supported Not supported Link Layer Discovery Protocol (LLDP) 10.2R1 11.1R2 11.1R2 10.2R1 Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) with voice over IP (VoIP) integration 10.2R1 Not supported Not supported Not supported MAC-based VLANs 10.2R1 11.1R2 11.1R2 9.4R1 Multiple VLAN Registration Protocol (MVRP) 10.2R1 Not supported Not supported 10.2R1 Private VLANs (PVLANs) 10.2R1 Not supported 11.1R2 10.2R1 Private VLANs (PVLANs) support across switches 10.4R1 Not supported 11.1R2 Not supported Proxy ARP—restricted 10.2R1 11.1R2 Not supported 10.2R1 Proxy ARP—unrestricted 10.2R1 11.1R2 11.1R2 10.2R1 Proxy ARP per VLAN 10.2R1 11.1R2 Not supported 10.2R1 Q-in-Q tunneling 10.2R1 Not supported Not supported 11.1R2 Q-in-Q VLAN extended support for multiple S-VLANs per access interface, firewall-filter-based VLAN assignment, and routed VLAN interfaces (RVIs) 10.2R1 Not supported Not supported 11.1R2 VLAN ID translation 10.2R1 Not supported Not supported Not supported VLAN ranges 10.2R1 11.1R2 Not supported 10.2R1 Table 13: Layer 3 Protocols Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Bidirectional Forwarding Detection (BFD) 10.2R1 11.1R2 11.1R2 10.2R1 Border Gateway Protocol (BGP) 10.2R1 11.1R2 11.1R2 10.2R1 Feature 10 Chapter 1: Software Overview Table 13: Layer 3 Protocols Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches A separate software license is required for BGP and MBGP. See “Understanding Software Licenses for J-EX Series Switches” on page 76. Distributed periodic packet management (PPM) with BFD 10.4R1 Not supported Not supported 10.4R1 Distributed periodic packet management (PPM) with LACP 10.2R1 11.1R2 11.1R2 10.2R1 Filter-based forwarding 10.2R1 Not supported Not supported 10.2R1 Filter-based forwarding over IPv6 10.2R1 Not supported Not supported 10.3R1 Intermediate System-to-Intermediate System (IS-IS) 10.2R1 11.1R2 Not supported 10.2R1 A separate software license is required for IS-IS. See “Understanding Software Licenses for J-EX Series Switches” on page 76. IPv6 Layer 3 multicast protocols 10.2R1 Not supported Not supported 10.2R1 Jumbo frames on routed VLAN interfaces (RVIs) 10.2R1 11.1R2 Not supported 10.2R1 OSPF Multitopology Routing (MT-OSPF) 10.2R1 Not supported Not supported 10.2R1 See the Junos OS Routing Protocols Configuration Guide. OSPFv2 10.2R1 11.1R2 11.1R2 10.2R1 OSPFv3 IPSec support 10.3R1 Not supported Not supported Not supported Routed VLAN interfaces (RVIs) 10.2R1 11.1R2 11.1R2 10.2R1 Routing Information Protocol version 1 (RIPv1) and RIPv2 10.2R1 11.1R2 11.1R2 10.2R1 Static routes 10.2R1 11.1R2 11.1R2 10.2R1 Virtual routing and forwarding (VRF) with IPv4—virtual routing instances 10.2R1 11.1R2 11.1R2 10.2R1 VRF with IPv4—virtual routing instances for multicast traffic 10.2R1 11.1R2 11.1R2 10.2R1 VRF with IPv6—virtual routing instances for multicast traffic 10.2R1 Not supported Not supported 10.2R1 11 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 13: Layer 3 Protocols Features by Junos OS Release (continued) Feature VRF with IPv6—virtual routing instances for unicast traffic J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches 10.2R1 Not supported Not supported 10.2R1 J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Table 14: MPLS Features by Junos OS Release Feature J-EX4200 Switches A separate software license is required for MPLS. See “Understanding Software Licenses for J-EX Series Switches” on page 76. Aggregated Ethernet interfaces (LAGs) on circuit cross-connects (CCCs) Not supported Not supported Not supported 11.1R2 CCC with a beginning and ending on the same switch Not supported Not supported Not supported 11.1R2 IP over MPLS 10.2R1 Not supported Not supported 11.1R2 LDP-based MPLS Not supported Not supported Not supported 11.1R2 MPLS-based circuit cross-connects (CCC) 10.2R1 Not supported Not supported 11.1R2 MPLS with class of service (CoS) 10.2R1 Not supported Not supported Not supported MPLS with Layer 2 VPNs on Ethernet-encapsulated interfaces (VLAN encapsulated interfaces are not supported) Not supported Not supported Not supported 11.1R2 MPLS with Layer 3 VPNs—including support for RVIs on customer edge (CE) interfaces Not supported Not supported Not supported 11.1R2 MPLS with RSVP-based label-switched paths (LSPs) 10.2R1 Not supported Not supported 11.1R2 Table 15: Multicast Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches IGMP (Internet Group Management Protocol) version 1 (IGMPv1) and IGMPv2 10.2R1 11.1R2 11.1R2 10.2R1 IGMP snooping with routed VLAN interfaces (RVIs) 10.2R1 11.1R2 Not supported 10.2R1 Feature 12 Chapter 1: Software Overview Table 15: Multicast Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches IGMPv3 10.2R1 11.1R2 11.1R2 10.2R1 IGMPv1/v2 snooping 10.2R1 11.1R2 11.1R2 10.2R1 IGMPv3 snooping 10.2R1 11.1R2 11.1R2 10.2R1 Multicast Source Discovery Protocol (MSDP) 10.2R1 11.1R2 11.1R2 10.2R1 See the Junos OS Multicast Protocols Configuration Guide. Multicast VLAN registration (MVR) 10.2R1 Not supported Not supported Not supported Protocol Independent Multicast dense mode (PIM DM) 10.2R1 Not supported Not supported 10.2R1 11.1R2 11.1R2 10.2R1 11.1R2 11.1R2 10.2R1 Not supported Not supported 10.2R1 See the Junos OS Multicast Protocols Configuration Guide. Protocol Independent Multicast sparse mode (PIM SM) 10.2R1 See the Junos OS Multicast Protocols Configuration Guide. Protocol Independent Multicast source-specific multicast (PIM SSM) 10.2R1 See the Junos OS Multicast Protocols Configuration Guide. Single-source multicast 10.2R1 Table 16: Network Management and Monitoring Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches 802.1ag Ethernet OAM connectivity fault management (CFM) 10.2R1 Not supported Not supported Not supported Ethernet OAM link fault management (LFM) 10.2R1 Not supported Not supported 10.2R1 Port mirroring 10.2R1 11.1R2 11.1R2 10.2R1 Port mirroring enhancements 10.2R1 Not supported Not supported 10.2R1 Feature • Layer 3 interface support • Multiple VLAN support 13 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 16: Network Management and Monitoring Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Port mirroring enhancements 10.2R1 Not supported Not supported Not supported Real-time performance monitoring (RPM) 10.2R1 11.1R2 11.1R2 10.2R1 Real-time performance monitoring (RPM)—hardware timestamps with routed VLAN interfaces (RVIs) 10.3R1 11.1R2 11.1R2 10.3R1 RMON 10.2R1 11.1R2 11.1R2 10.2R1 sFlow monitoring technology 10.2R1 Not supported Not supported 10.2R1 sFlow technology—egress sampling 10.4R1 Not supported Not supported 10.4R1 sFlow technology— persistent IP addresses for agent IDs and use in datagrams 10.2R1 Not supported Not supported 10.2R1 Simple Network Management Protocol version 1 (SNMPv1), SNMPv2, and SNMPv3 10.2R1 11.1R2 11.1R2 10.2R1 Uplink failure detection 11.1R2 11.1R2 Not supported Not supported • Ingress-only and egress-only attributes on VLAN members to avoid flooding mirrored traffic to VLAN member interfaces VLAN on the intermediate switch Table 17: Port Security Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Automatic recovery for port error disable conditions 10.2R1 11.1R2 11.1R2 10.2R1 DHCP option 82 10.2R1 11.1R2 Not supported 10.2R1 DHCP snooping 10.2R1 Not supported Not supported 10.3R1 Dynamic ARP inspection (DAI) 10.2R1 Not supported Not supported 10.3R1 IP source guard 10.2R1 Not supported Not supported 10.3R1 MAC limiting 10.2R1 11.1R2 11.1R2 10.2R1 Feature 14 Chapter 1: Software Overview Table 17: Port Security Features by Junos OS Release (continued) Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches MAC address limit per port 10.2R1 11.1R2 11.1R2 10.3R1 MAC move limiting 10.2R1 Not supported Not supported Not supported Persistent storage for DHCP snooping 10.2R1 Not supported Not supported 10.3R1 Self-signed digital certificates for enabling SSL services 11.1R2 11.1R2 11.1R2 11.1R2 Static ARP support 10.2R1 11.1R2 11.1R2 10.2R1 Table 18: Routing Policy and Packet Filtering Features by Junos OS Release J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Dynamic allocation of TCAM memory to firewall filters 10.0R1 11.1R2 11.1R2 10.3R1 Firewall filters and rate limiting 9.0R2 11.1R2 11.1R2 9.4R1 Feature For a list of supported firewall filter match conditions and actions, see Firewall Filter Match Conditions and Actions for J-EX Series Switches in the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. Firewall filters on LAGs 10.2R1 11.1R2 11.1R2 10.0R1 Firewall filters on loopback interface 10.2R1 11.1R2 11.1R2 10.2R1 Firewall filters on management interface 10.4R1 11.1R2 Not supported 10.4R1 Firewall filters on virtual management interface 10.4R1 (J-EX4200 Virtual Chassis only) Not applicable 11.1R2 Not applicable Firewall filters with IPv6 10.2R1 Not supported Not supported 10.3R1 Policing 10.2R1 11.1R2 11.1R2 10.2R1 Table 19: Spanning-Tree Protocols Features by Junos OS Release Feature BPDU protection for spanning-tree protocols J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches 10.2R1 11.1R2 11.1R2 10.2R1 15 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 19: Spanning-Tree Protocols Features by Junos OS Release (continued) J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Loop protection for spanning-tree protocols 10.2R1 11.1R2 11.1R2 10.2R1 Root protection for spanning-tree protocols 10.2R1 11.1R2 11.1R2 10.2R1 Spanning tree: 10.2R1 11.1R2 11.1R2 10.2R1 10.2R1 11.1R2 11.1R2 10.2R1 10.2R1 11.1R2 11.1R2 10.2R1 Feature • RSTP and VSTP concurrent configuration Spanning tree: • Spanning Tree Protocol (STP) • Rapid Spanning Tree Protocol (RSTP) • Multiple Spanning Tree Protocol (MSTP) Spanning tree: • VLAN Spanning Tree Protocol (VSTP) Table 20: System Management Features by Junos OS Release Feature J-EX4200 Switches J-EX4500 Switches J-EX4500 Virtual Chassis J-EX8200 Switches Autoinstallation of configuration files 10.2R1 11.1R2 Not supported Not supported Automatic software download 10.2R1 11.1R2 Not supported 10.2R1 Configuration rollback 10.2R1 11.1R2 11.1R2 10.2R1 IP directed broadcast 10.2R1 11.1R2 11.1R2 10.2R1 J-Web interface, for switch configuration and management 10.2R1 11.1R2 Not supported 10.2R1 Online insertion and removal (OIR) of uplink modules 10.2R1 11.1R2 11.1R2 Not applicable Related Documentation 16 • J-EX4200 Switches Hardware Overview on page 29 • J-EX4500 Switches Hardware Overview on page 31 • J-EX8208 Switch Hardware Overview on page 35 • J-EX8216 Switch Hardware Overview on page 38 Chapter 1: Software Overview • Layer 3 Protocols Supported on J-EX Series Switches on page 17 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 18 Layer 3 Protocols Supported on J-EX Series Switches J-EX Series switches support the Junos OS Layer 3 features and configuration statements listed in Table 21 on page 17: Table 21: Supported Junos OS Layer 3 Protocol Statements and Features Protocol Notes For More Information BGP Fully supported. Junos OS Routing Protocols Configuration Guide BFD Fully supported. Junos OS Routing Protocols Configuration Guide ICMP Fully supported. Junos OS Routing Protocols Configuration Guide IGMPv1, v2 and v3 Fully supported. Junos OS Multicast Protocols Configuration Guide IS-IS Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 18. Junos OS Routing Protocols Configuration Guide MLD Supported on J-EX4200 and J-EX8200 switches (MLD versions 1 and 2). Junos OS Multicast Protocols Configuration Guide MPLS Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 18. Junos OS MPLS Applications Configuration Guide OSPFv1, v2 and v3 Supported, with the exceptions noted in “Layer 3 Protocols Not Supported on J-EX Series Switches” on page 18. Junos OS Routing Protocols Configuration Guide PIM Fully supported on J-EX4200 and J-EX8200 switches. Junos OS Multicast Protocols Configuration Guide RIP Fully supported. Junos OS Routing Protocols Configuration Guide RIPng Fully supported. Junos OS Routing Protocols Configuration Guide SNMP Fully supported. Junos OS Network Management Configuration Guide VRRP Fully supported. See “Understanding VRRP on J-EX Series Switches” on page 928 in the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. See also Junos OS High Availability Guide. 17 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • Layer 3 Protocols Not Supported on J-EX Series Switches on page 18 • J-EX Series Switch Software Features Overview on page 3 Layer 3 Protocols Not Supported on J-EX Series Switches J-EX Series switches do not support the Junos OS Layer 3 protocols and features listed in Table 22 on page 18: Table 22: Junos OS Layer 3 Protocol Statements and Features That Are Not Supported Feature Configuration Statements Not Supported on J-EX Series Switches DVMRP • dvmrp and subordinate statements Flow aggregation (cflowd) • cflow and subordinate statements GRE • Not supported IPSec • [edit services] statements related to IPSec IS-IS: • clns-routing statement • ipv6-multicast statement • lsp-interval statement • label-switched-path statement • lsp-lifetime statement • te-metric statement Logical routers • logical-routers and subordinate statements MLD • mld and all subordinate statements (J-EX4500 switches) MPLS: • ldp and all subordinate statements (except on J-EX8200 switches) • ES-IS • IPv6 in multicast routing protocols • Fast Reroute (FRR) • Label Distribution Protocol (LDP) (except on J-EX8200 switches) • Layer 3 VPNs (except on J-EX8200 switches) • Multiprotocol BGP (MP-BGP) for VPN-IPv4 family • Pseudowire emulation (PWE3) • Routing policy statements related to Layer 3 VPNs and MPLS (except on J-EX8200 switches) • Virtual Private LAN Service (VPLS) 18 Chapter 1: Software Overview Table 22: Junos OS Layer 3 Protocol Statements and Features That Are Not Supported (continued) Feature Configuration Statements Not Supported on J-EX Series Switches Network Address Translation (NAT) • nat and subordinate statements • Policy statements related to NAT OSPF • demand-circuit statement • label-switched-path and subordinate statements • neighbor statement within an OSPF area • peer-interface and subordinate statements within an OSPF area • sham-link statement • te-metric statement PIM DM • Not supported on J-EX4500 switches PIM: • inet6 family (J-EX4500 switches) • IPv6 Routed VLAN interfaces (RVIs) family mpls statement Routing instances: • l2vpn and subordinate statements (except on J-EX8200 switches) • ldp and subordinate statements (except on J-EX8200 switches) • vpls and subordinate statements SAP and SDP • sap and all subordinate statements General routing options in the routing-options hierarchy: • auto-export and subordinate statements • dynamic-tunnels and subordinate statements • • lsp-next-hop and subordinate statements • multicast and subordinate statements • p2mp-lsp-next-hop and subordinate statements • route-distinguisher-id statement (except on J-EX8200 switches) • accounting and subordinate statements • family mpls and family multiservice under hash-key hierarchy • Under monitoring group-name family inet output hierarchy: • Routing instance forwarding MPLS and label-switched-paths Traffic sampling and fowarding in the forwarding-options hierarchy • cflowd statement • export-format-cflowd-version-5 statement • flow-active-timeout statement • flow-export-destination statement • flow-inactive-timeout statement • interface statement • port-mirroring statement (On J-EX Series switches, port mirroring is implemented using the analyzer statement.) • sampling and subordinate statements 19 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • Layer 3 Protocols Supported on J-EX Series Switches on page 17 • J-EX Series Switch Software Features Overview on page 3 Security Features for J-EX Series Switches Overview The Junos operating system (Junos OS) is a network operating system that has been hardened through the separation of control forwarding and services planes, with each function running in protected memory. The control-plane CPU is protected by rate limiting, routing policy, and firewall filters to ensure switch uptime even under severe attack. In addition, the switches fully integrate with the Juniper Networks Unified Access Control (UAC) product to provide both standards-based 802.1X port-level access and Layer 2 through Layer 4 policy enforcement based on user identity. Access port security features such as dynamic Address Resolution Protocol (ARP) inspection, DHCP snooping, and MAC limiting are controlled through a single Junos OS CLI command. J-EX Series Switches provide the following hardware and software security features: Console Port—Allows use of the console port to connect to the Routing Engine through an RJ-45 cable. You then use the command-line interface (CLI) to configure the switch. Out-of-Band Management—A dedicated management Ethernet port on the rear panel allows out-of-band management. Software Images—All Junos OS images are signed by Juniper Networks certificate authority (CA) with public key infrastructure (PKI). User Authentication, Authorization, and Accounting (AAA)—Features include: • User and group accounts with password encryption and authentication. • Access privilege levels configurable for login classes and user templates. • RADIUS authentication, TACACS+ authentication, or both, for authenticating users who attempt to access the switch. • Auditing of configuration changes through system logging or RADIUS/TACACS+. 802.1X Authentication—Provides network access control. Supplicants (hosts) are authenticated when they initially connect to a LAN. Authenticating supplicants before they receive an IP address from a DHCP server prevents unauthorized supplicants from gaining access to the LAN. J-EX Series switches support Extensible Authentication Protocol (EAP) methods, including EAP-MD5, EAP-TLS, EAP-TTLS, and EAP-PEAP. Port Security—Access port security features include: 20 • DHCP snooping—Filters and blocks ingress DHCP server messages on untrusted ports; builds and maintains an IP-address/MAC-address binding database (called the DHCP snooping database). • Dynamic ARP inspection (DAI)—Prevents ARP spoofing attacks. ARP requests and replies are compared against entries in the DHCP snooping database, and filtering decisions are made based on the results of those comparisons. Chapter 1: Software Overview • MAC limiting—Protects against flooding of the Ethernet switching table. • MAC move limiting—Detects MAC movement and MAC spoofing on access ports. • Trusted DHCP server—With a DHCP server on a trusted port, protects against rogue DHCP servers sending leases. • IP source guard—Mitigates the effects of IP address spoofing attacks on the Ethernet LAN. The source IP address in the packet sent from an untrusted access interface is validated against the source MAC address in the DHCP snooping database. The packet is allowed for further processing if the source IP address to source MAC address binding is valid; if the binding is not valid, the packet is discarded. • DHCP option 82—Also known as the DHCP relay agent information option. Helps protect the J-EX Series switch against attacks such as spoofing (forging) of IP addresses and MAC addresses and DHCP IP address starvation. Option 82 provides information about the network location of a DHCP client, and the DHCP server uses this information to implement IP addresses or other parameters for the client. • Unrestricted proxy ARP—The switch responds to all ARP messages with its own MAC address. Hosts that are connected to the switch’s interfaces cannot communicate directly with other hosts. Instead, all communications between hosts go through the switch. • Restricted proxy ARP—The switch does not respond to an ARP request if the physical networks of the source and target of the ARP request are the same. It does not matter whether the destination host has the same IP address as the incoming interface or a different (remote) IP address. An ARP request for a broadcast address elicits no reply. Device Security—Storm control permits the switch to monitor unknown unicast and broadcast traffic and drop packets, or shut down, or temporarily disable the interface when a specified traffic level is exceeded, thus preventing packets from proliferating and degrading the LAN. You can enable storm control on access interfaces or trunk interfaces. Firewall Filters—Allow auditing of various types of security violations, including attempts to access the switch from unauthorized locations. Firewall filters can detect such attempts and create audit log entries when they occur. The filters can also restrict access by limiting traffic to source and destination MAC addresses, specific protocols, or, in combination with policers, to specified data rates to prevent denial of service (DoS) attacks. Policers—Provide rate-limiting capability to control the amount of traffic that enters an interface, which acts to counter DoS attacks. Encryption Standards—Supported standards include: Related Documentation • 128-, 192-, and 256-bit Advanced Encryption Standard (AES) • 56-bit Data Encryption Standard (DES) and 168-bit 3DES See the following information in the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals: • 802.1X for J-EX Series Switches Overview 21 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Firewall Filters for J-EX Series Switches Overview • Port Security for J-EX Series Switches Overview • Understanding Proxy ARP on J-EX Series Switches • Understanding Storm Control on J-EX Series Switches • Understanding the Use of Policers in Firewall Filters High Availability Features for J-EX Series Switches Overview High availability refers to the hardware and software components that provide redundancy and reliability for packet-based communications. This topic covers the following high availability features of J-EX Series Switches: • VRRP on page 22 • Graceful Protocol Restart on page 22 • Redundant Routing Engines on page 23 • Virtual Chassis on page 23 • Graceful Routing Engine Switchover on page 24 • Link Aggregation on page 24 • Nonstop Active Routing on page 24 • Nonstop Software Upgrade on page 24 VRRP You can configure the Virtual Router Redundancy Protocol (VRRP) or VRRP for IPv6 on Gigabit Ethernet interfaces, 10-Gigabit Ethernet interfaces, and logical interfaces on the switches. When VRRP is configured, the switches act as virtual routing platforms. VRRP enables hosts on a LAN to make use of redundant routing platforms on that LAN without requiring more than the static configuration of a single default route on the hosts. The VRRP routing platforms share the IP address corresponding to the default route configured on the hosts. At any time, one of the VRRP routing platforms is the master (active) and the others are backups. If the master routing platform fails, one of the backup routing platforms becomes the new master, providing a virtual default routing platform and enabling traffic on the LAN to be routed without relying on a single routing platform. Using VRRP, a backup switch can take over a failed default switch within a few seconds. This is done with minimum loss of VRRP traffic and without any interaction with the hosts. Graceful Protocol Restart With standard implementations of routing protocols, any service interruption requires an affected switch to recalculate adjacencies with neighboring switches, restore routing table entries, and update other protocol-specific information. An unprotected restart of a switch can result in forwarding delays, route flapping, wait times stemming from protocol reconvergence, and even dropped packets. Graceful protocol restart allows a restarting switch and its neighbors to continue forwarding packets without disrupting network 22 Chapter 1: Software Overview performance. Because neighboring switches assist in the restart (these neighbors are called helper switches), the restarting switch can quickly resume full operation without recalculating algorithms from scratch. On the switches, graceful protocol restart can be applied to aggregate and static routes and for routing protocols (BGP, IS-IS, OSPF, and RIP). Graceful protocol restart works similarly for the different routing protocols. The main benefits of graceful protocol restart are uninterrupted packet forwarding and temporary suppression of all routing protocol updates. Graceful protocol restart thus allows a switch to pass through intermediate convergence states that are hidden from the rest of the network. Most graceful restart implementations define two types of switches—the restarting switch and the helper switch. The restarting switch requires rapid restoration of forwarding state information so that it can resume the forwarding of network traffic. The helper switch assists the restarting switch in this process. Individual graceful restart configuration statements typically apply to either the restarting switch or the helper switch. Redundant Routing Engines Redundant Routing Engines are two Routing Engines that are installed in a switch. When a switch has two Routing Engines, one functions as the master, while the other stands by as a backup should the master Routing Engine fail. Redundant Routing Engines are supported on Dell PowerConnect J-EX Series J-EX8200 Ethernet Switches. The master Routing Engine receives and transmits routing information, builds and maintains routing tables, communicates with interfaces and Packet Forwarding Engine components of the switch, and has full control over the control plane of the switch. The backup Routing Engine stays in sync with the master Routing Engine in terms of protocol states, forwarding tables, and so forth. If the master becomes unavailable, the backup Routing Engine takes over the functions that the master Routing Engine performs. Network reconvergence takes place more quickly on switches with redundant Routing Engines than on switches with a single Routing Engine. Virtual Chassis A Virtual Chassis is multiple switches connected together that operate as a single network entity. The advantages of connecting multiple switches into a Virtual Chassis include better-managed bandwidth at a network layer, simplified configuration and maintenance because multiple devices can be managed as a single device, and a simplified Layer 2 network topology that minimizes or eliminates the need for loop prevention protocols such as Spanning Tree Protocol (STP). A Virtual Chassis improves high availability by introducing a variety of failover mechanisms; if a member switch, a line card, or an interface fails on a switch that is a member of a Virtual Chassis, for instance, traffic to that switch, line card, or interface can be rerouted within the Virtual Chassis. Dell PowerConnect J-EX Series J-EX4200 Ethernet Switches and Dell PowerConnect J-EX Series J-EX4500 Ethernet Switches can form a Virtual Chassis. 23 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Graceful Routing Engine Switchover You can configure graceful Routing Engine switchover (GRES) on a switch with redundant Routing Engines or on a Virtual Chassis, allowing control to switch from the master Routing Engine to the backup Routing Engine with minimal interruption to network communications. When you configure graceful Routing Engine switchover, the backup Routing Engine automatically synchronizes with the master Routing Engine to preserve kernel state information and forwarding state. Any updates to the master Routing Engine are replicated to the backup Routing Engine as soon as they occur. If the kernel on the master Routing Engine stops operating, the master Routing Engine experiences a hardware failure, or the administrator initiates a manual switchover, mastership switches to the backup Routing Engine. When the backup Routing Engine assumes mastership in a redundant failover configuration (that is, when graceful Routing Engine switchover is not enabled), the Packet Forwarding Engines initialize their state to the boot state before they connect to the new master Routing Engine. In contrast, in a graceful switchover configuration, the Packet Forwarding Engines do not reinitialize their state, but resynchronize their state to that of the new master Routing Engine. The interruption to traffic is minimal. Link Aggregation You can combine multiple physical Ethernet ports to form a logical point-to-point link, known as a link aggregation group (LAG) or bundle. A LAG provides more bandwidth than a single Ethernet link can provide. Additionally, link aggregation provides network redundancy by load-balancing traffic across all available links. If one of the links should fail, the system automatically load-balances traffic across all remaining links. In a Virtual Chassis, LAGs can be used to load-balance network traffic between member switches. The number of Ethernet interfaces you can include in a LAG and the number of LAGs you can configure on a switch depend on the switch model. Nonstop Active Routing Nonstop active routing (NSR) provides high availability in a switch with redundant Routing Engines by enabling transparent switchover of the Routing Engines without requiring restart of supported routing protocols. Both Routing Engines are fully active in processing protocol sessions, and so each can take over for the other. The switchover is transparent to neighbor routing devices, which do not detect that a change has occurred. To use nonstop active routing, you must also configure graceful Routing Engine switchover. Nonstop Software Upgrade Nonstop software upgrade (NSSU) is available on J-EX8200 switches with redundant Routing Engines. NSSU takes advantage of graceful Routing Engine switchover and nonstop active routing to enable upgrading the Junos OS version running on a switch or Virtual Chassis with no disruption to the control plane. In addition, NSSU upgrades line cards one at a time, permitting traffic to continue to flow through the line cards that are not being upgraded. By configuring LAGs such that the member links reside on different line cards, you can achieve minimal traffic disruption when performing an NSSU. 24 Chapter 1: Software Overview Related Documentation For details on high availability features, see the following information in the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals For more information, see the Junos OS High Availability Configuration Guide. • J-EX4200 Virtual Chassis Overview on page 709 • Understanding VRRP on J-EX Series Switches on page 928 • Understanding Aggregated Ethernet Interfaces and LACP on page 1003 • Understanding Nonstop Active Routing on J-EX Series Switches on page 931 • Understanding Nonstop Software Upgrade on J-EX Series Switches on page 932 • For more information, see the Junos OS High Availability Configuration Guide. Understanding Software Infrastructure and Processes Each switch runs the Junos operating system (Junos OS) for J-EX Series Switches on its general-purpose processors. Junos OS includes processes for Internet Protocol (IP) routing and for managing interfaces, networks, and the chassis. The Junos OS runs on the Routing Engine. The Routing Engine kernel coordinates communication among the Junos OS processes and provides a link to the Packet Forwarding Engine. With the J-Web interface and the command-line interface (CLI) to the Junos OS, you configure switching features and routing protocols and set the properties of network interfaces on your switch. After activating a software configuration, use either the J-Web or CLI user interface to monitor the switch, manage operations, and diagnose protocol and network connectivity problems. • Routing Engine and Packet Forwarding Engine on page 25 • Junos OS Processes on page 26 Routing Engine and Packet Forwarding Engine A switch has two primary software processing components: • Packet Forwarding Engine—Processes packets; applies filters, routing policies, and other features; and forwards packets to the next hop along the route to their final destination. • Routing Engine—Provides three main functions: • Creates the packet forwarding switch fabric for the switch, providing route lookup, filtering, and switching on incoming data packets, then directing outbound packets to the appropriate interface for transmission to the network • Maintains the routing tables used by the switch and controls the routing protocols that run on the switch. 25 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Provides control and monitoring functions for the switch, including controlling power and monitoring system status. Junos OS Processes The Junos OS running on the Routing Engine and Packet Forwarding Engine consists of multiple processes that are responsible for individual functions. The separation of functions provides operational stability, because each process accesses its own protected memory space. In addition, because each process is a separate software package, you can selectively upgrade all or part of the Junos OS, for added flexibility. Table 23 on page 26 describes the primary Junos OS processes. Table 23: Junos OS Processes Process Name Description Chassis process chassisd Detects hardware on the system that is used to configure network interfaces. Monitors the physical status of hardware components and field-replaceable units (FRUs), detecting when environment sensors such as temperature sensors are triggered. Relays signals and interrupts—for example, when devices are taken offline, so that the system can close sessions and shut down gracefully. Ethernet switching process eswd Handles Layer 2 switching functionality such as MAC address learning, Spanning Tree protocol and access port security. The process is also responsible for managing Ethernet switching interfaces, VLANs, and VLAN interfaces. Manages Ethernet switching interfaces, VLANs, and VLAN interfaces. Forwarding process pfem Defines how routing protocols operate on the switch. The overall performance of the switch is largely determined by the effectiveness of the forwarding process. Interface process dcd Configures and monitors network interfaces by defining physical characteristics such as link encapsulation, hold times, and keepalive timers. Management process mgd Provides communication between the other processes and an interface to the configuration database. Populates the configuration database with configuration information and retrieves the information when queried by other processes to ensure that the system operates as configured. Interacts with the other processes when commands are issued through one of the user interfaces on the switch. If a process terminates or fails to start when called, the management process attempts to restart it a limited number of times to prevent thrashing and logs any failure information for further investigation. Routing protocol process 26 rpd Defines how routing protocols such as RIP, OSPF, and BGP operate on the device, including selecting routes and maintaining forwarding tables. Chapter 1: Software Overview Related Documentation • For more information about processes, see the Junos OS Network Operations Guide • For more information about basic system parameters, supported protocols, and software processes, see the Junos OS System Basics Configuration Guide 27 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 28 CHAPTER 2 Supported Hardware • J-EX4200 Switches Hardware Overview on page 29 • J-EX4200 Switch Models on page 31 • J-EX4500 Switches Hardware Overview on page 31 • J-EX4500 Switch Models on page 34 • J-EX8208 Switch Hardware Overview on page 35 • J-EX8216 Switch Hardware Overview on page 38 J-EX4200 Switches Hardware Overview J-EX Series Switches provide scalable connectivity for the enterprise market, including branch offices, campus locations, and data centers. The switches run the Junos operating system (Junos OS), which provides Layer 2 and Layer 3 switching, routing, and security services. The same Junos OS code base that runs on J-EX Series switches also runs on all Dell PowerConnect J-SRX-Series Services Gateways. • J-EX4200 Switches on page 29 • Uplink Modules on page 30 • Power over Ethernet (PoE) Ports on page 30 J-EX4200 Switches Dell PowerConnect J-EX Series J-EX4200 Ethernet Switches provide connectivity for medium- and high-density environments and scalability for growing networks. These switches can be deployed wherever you need high density of Gigabit Ethernet ports (24 to 480 ports) or redundancy. Typically, J-EX4200 switches are used in large branch offices, campus wiring closets, and data centers where they can be positioned as the top device in a rack to provide connectivity for all the devices in the rack. You can connect individual J-EX4200 switches together to form one unit and manage the unit as a single chassis, called a Virtual Chassis. You can add more member switches to the Virtual Chassis as needed, up to a total of 10 members. J-EX4200 switches are available in models with 24 or 48 ports and with 8 ports equipped for Power over Ethernet (PoE). All models provide ports that have 10/100/1000Base-T Gigabit Ethernet connectors and optional 1-gigabit small form-factor pluggable (SFP) 29 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 transceivers, 10-gigabit small form-factor pluggable (SFP+) transceivers for use with fiber connections. Additionally, a 24-port model provides 100Base-FX/1000Base-X SFP ports. This model is typically used as a small distribution switch. All J-EX4200 switches have dedicated 64-Gbps Virtual Chassis ports that allow you to connect the switches to each other. You can also use optional uplink module ports to connect members of a Virtual Chassis across multiple wiring closets. To provide carrier-class reliability, J-EX4200 switches include: • Dual redundant power supplies that are field-replaceable and hot-swappable. An optional additional connection to an external power source is also available. • A field-replaceable fan tray with three fans. The switch remains operational if a single fan fails. • Redundant Routing Engines in a Virtual Chassis configuration. This redundancy enables graceful Routing Engine switchover (GRES) and nonstop active routing (NSR). • Junos OS with its modular design that enables failed system processes to gracefully restart. J-EX4200 switches have these features: • Run under Junos OS for J-EX Series switches • Have options of 24-port and 48-port models • Have options of partial (8 ports) Power over Ethernet (PoE) capability • Have optional uplink modules that provide connection to distribution switches Uplink Modules Optional uplink modules are available for all J-EX4200 switches. Uplink modules provide four 1-gigabit small form-factor pluggable (SFP) transceivers or two 10-gigabit small form-factor pluggable (SFP+) transceivers. You can use SFP or SFP+ ports to connect an access switch to a distribution switch or to interconnect member switches of a Virtual Chassis across multiple wiring closets. Power over Ethernet (PoE) Ports PoE ports provide electrical current to devices through the network cables so that separate power cords for devices such as IP phones, wireless access points, and security cameras are unnecessary. Two J-EX4200 switch models provide partial (8 ports) PoE capability. Partial PoE models are used in environments where, for example, only a few ports for wireless access points or security cameras are required. Related Documentation 30 • J-EX4200 Switch Models on page 31 • For information about switch FRUs and site preparation, see the Dell PowerConnect J-Series J-EX4200 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Chapter 2: Supported Hardware J-EX4200 Switch Models The J-EX4200 switch is available with 24 or 48 ports and with partial Power over Ethernet (PoE) capability. Table 24 on page 31 lists the J-EX4200 switch models. Table 24: J-EX4200 Switch Models Model Ports Number of PoE-enabled Ports Power Supply (Minimum) J-EX4200-24T 24 Gigabit Ethernet First 8 ports 320 W J-EX4200-48T 48 Gigabit Ethernet First 8 ports 320 W J-EX4200-24F 24 small form-factor pluggable (SFP) transceivers – 320 W Related Documentation • For front and rear panel illustrations and details, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. • J-EX4200 Switches Hardware Overview on page 29 J-EX4500 Switches Hardware Overview Dell PowerConnect J-EX Series J-EX4500 Ethernet Switches provide high performance, scalable connectivity, and carrier-class reliability for high-density environments such as campus-aggregation and data-center networks. You can manage J-EX4500 switches using the same interfaces that you use for managing other devices running the Junos operating system (Junos OS)—the command-line interface (CLI) and the J-Web graphical interface. The J-EX Series Switches run Junos OS, which provides Layer 2 and Layer 3 switching, routing, and security services. The same Junos OS code base that runs on J-EX Series switches also runs on all Dell PowerConnect J-SRX Series Services Gateways. • J-EX4500 Switches on page 31 • Virtual Chassis Module on page 33 • Uplink Modules on page 33 • Power Supplies on page 33 J-EX4500 Switches J-EX4500 switches provide connectivity for high-density 10-Gigabit Ethernet data center top-of-rack and aggregation deployments. Typically, J-EX4500 switches are used in data centers where they can be positioned as the top device in a rack to provide connectivity for all devices in the rack. 31 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 The J-EX4500 switch is 2 rack units (2 U) in size. Each J-EX4500 switch is designed to optimize rack space utilization and cabling. See Figure 1 on page 32 and Figure 2 on page 32. Figure 1: J-EX4500 Switch Front 0 1 2 3 ST 1 2 3 ST g020845 0 Figure 2: J-EX4500 Switch Rear with Virtual Chassis Module Installed AC power supply Virtual Chassis module g021062 Fan tray Fan tray handle J-EX4500 switches are available in models with either front-to back airflow or back-to-front airflow and hardware that is Converged Enhanced Ethernet (CEE) capable or not. All models provide 40 wire-speed 10-gigabit small form-factor pluggable (SFP+) network ports that can house either 1-Gigabit Ethernet connectors or 10-Gigabit Ethernet connectors. All models support two optional high-speed uplink modules. See “J-EX4500 Switch Models” on page 34. NOTE: The network ports are located on the front of the switch. To provide carrier-class reliability, J-EX4500 switches include: 32 • Dual redundant, load-sharing power supplies that are field-replaceable, hot-removable, and hot-insertable. • A field-replaceable fan tray with five fans. The switch remains operational if a single fan fails. Chapter 2: Supported Hardware • Redundant Routing Engines in a Virtual Chassis configuration. This redundancy enables graceful Routing Engine switchover (GRES). • Junos OS with its modular design that enables failed system processes to gracefully restart. Virtual Chassis Module J-EX4500 switches ship with the Virtual Chassis module preinstalled horizontally on the rear of the switch chassis. The Virtual Chassis module is an offline field-replaceable unit (FRU). The Virtual Chassis module has two dedicated Virtual Chassis ports (VCPs) that can be used to interconnect the J-EX4500 switch with J-EX4200 switches or another J-EX4500 switch to form a Virtual Chassis. The Virtual Chassis module must be installed in a J-EX4500 switch to form a Virtual Chassis. Only two J-EX4500 switches can be interconnected into a Virtual Chassis composed exclusively of J-EX4500 switches. J-EX4200 and J-EX4500 switches can be connected together into the same Virtual Chassis to form a mixed J-EX4200 and J-EX4500 Virtual Chassis. A mixed J-EX4200 and J-EX4500 Virtual Chassis supports up to two J-EX4500 switches and up to eight J-EX4200 switches. You can interconnect J-EX4200 and J-EX4500 switches through the dedicated Virtual Chassis ports (VCPs) to form a mixed Virtual Chassis. You can also interconnect J-EX4500 switches through SFP+ uplink module ports or SFP+ network ports configured as VCPs to form a Virtual Chassis. NOTE: Operating a J-EX4500 switch without the Virtual Chassis module is not supported. J-EX4500 switches will not boot if the Virtual Chassis module is not installed in the switch chassis. Uplink Modules Optional uplink modules are available for J-EX4500 switches. Two uplink modules can be installed in a J-EX4500 switch. Each uplink module provides four SFP+ ports for connecting to core devices in a data center. You can install SFP or SFP+ transceivers in these ports. You can also configure the uplink module ports as VCPs to form a Virtual Chassis. Power Supplies J-EX4500 switches support AC power supplies. J-EX4500 switches ship with one AC power supply installed. You can install a second AC power supply in your J-EX4500 switch. For slot numbering and line-card details, see the Dell PowerConnect J-Series J-EX4500 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. 33 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 CAUTION: Mixing power supplies with front-to-back and back-to-front airflow in the same chassis is not supported. Related Documentation • J-EX4500 Switch Models on page 34 • J-EX4200 and J-EX4500 Virtual Chassis Overview on page 709 J-EX4500 Switch Models The J-EX4500 switch is available in two models. Table 25 on page 34 lists the models for a J-EX4500 switch and the components included in each model. NOTE: The network ports are located on the front of the switch. Table 25: J-EX4500 Switch Models and Their Components Model GYTPN TX9CD Access Port Configuration Direction of Airflow Switch Components 40-port GbE/10GbE SFP/SFP+ Front-to-back • Chassis • One fan tray—displaying an EXHAUST label and arrow icons pointing towards you • One AC power supply—displaying an EXHAUST label and an arrow icon pointing towards you • One jumper cable • One power supply cover panel • Two uplink module cover panels • One Virtual Chassis module • Chassis • One fan tray—displaying an INTAKE label and arrow icons pointing away from you • One AC power supply—displaying an INTAKE label and an arrow icon pointing away from you) • One jumper cable • One power supply cover panel • Two uplink module cover panels • One Virtual Chassis module 40-port GbE/10GbE SFP/SFP+ Back-to-front NOTE: Uplink modules, transceivers, Virtual Chassis cables, and Virtual Chassis cable connector retainers are not part of the J-EX4500 switch’s shipping configuration. If you want to purchase any of these, or additional power supplies for your switch, you must order them separately. 34 Chapter 2: Supported Hardware CAUTION: Mixing power supplies with front-to-back and back-to-front airflow in the same chassis is not supported. Related Documentation • For chassis specifications and front and rear panel details, see the Dell PowerConnect J-Series J-EX4500 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. • J-EX4500 Switches Hardware Overview on page 31 J-EX8208 Switch Hardware Overview Dell PowerConnect J-EX Series J-EX8208 Ethernet Switches provide high performance, scalable connectivity, and carrier-class reliability for high-density environments such as campus-aggregation and data-center networks. The J-EX8208 switch is a modular system that provides high availability and redundancy for all major hardware components, including Routing Engines, switch fabric, fan tray, and power supplies. You can manage J-EX8208 switches using the same interfaces that you use for managing other devices running the Junos operating system (Junos OS)—the command-line interface (CLI) and , the J-Web graphical interface. • Software on page 35 • Chassis Physical Specifications on page 35 • Routing Engines and Switch Fabric on page 36 • Line Cards on page 37 • Cooling System on page 37 • Power Supplies on page 37 Software The J-EX Series Switches run the Juniper Networks Junos OS, which provides Layer 2 and Layer 3 switching, routing, and security services. The same Junos OS code base that runs on J-EX Series switches also runs on all Dell PowerConnect J-SRX Series Services Gateways. Chassis Physical Specifications The J-EX8208 switch is 14 rack units (14 U) in size (1/3 rack); three J-EX8208 switches can fit in a standard 42 U rack. Each J-EX8208 switch is designed to optimize rack space and cabling. See Figure 3 on page 36. 35 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Figure 3: J-EX8208 Switch The J-EX8208 switch has a chassis-level LCD panel that displays Routing Engine and switch fabric status as well as chassis components’ alarm information for rapid problem identification. The LCD panel provides a user-friendly interface for performing initial switch configuration, rolling back a configuration, or restoring the switch to its default settings. The J-EX8208 chassis backplane distributes the data, control, and management signals to various system components along with distributing power throughout the system. For LCD panel and chassis backplane details, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Routing Engines and Switch Fabric Switching functionality, system management, and system control functions of a J-EX8208 switch are performed by a Switch Fabric and Routing Engine (SRE) module. An SRE module contains a Routing Engine and switch fabric. The SRE modules are installed in the front of the chassis in the slots labeled SRE0 and SRE1. A redundant configuration J-EX8208 switch has a second SRE module. 36 Chapter 2: Supported Hardware The Switch Fabric (SF) module, working with the SRE module, provides the necessary switching functionality to a J-EX8208 switch. The SF module is installed in the front of the chassis in the slot labeled SF. In a redundant configuration the SF module provides a redundant switch fabric. The additional switch fabric provides full 2+1 switch fabric redundancy to the switch. For details about the SRE module, SF module, and slot numbering, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Line Cards The J-EX8208 switch features eight horizontal line card slots and supports the line rate for each line card. The line cards in J-EX8200 switches combine a Packet Forwarding Engine and Ethernet interfaces on a single assembly. Line cards are field-replaceable units (FRUs) that can be installed in the line card slots labeled 0 through 7 on the front of the switch chassis. For slot numbering and line-card details, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. The following line cards are available for J-EX8208 switches: • 8-port 10-Gigabit Ethernet SFP+ line card: This line card has eight 10-gigabit SFP+ ports on its faceplate in which you can install SFP+ transceivers. • 40-port 10-Gigabit Ethernet SFP+ line card: This line card has 40 10-gigabit SFP+ ports on its faceplate in which you can install either SFP+ or SFP transceivers. • 48-port 100/1000 SFP line card: This line card has 48 1-gigabit SFP ports on its faceplate in which you can install SFP transceivers. • 48-port 10/100/1000 RJ-45 line card: This line card has 48 10/100/1000 Gigabit Ethernet ports with RJ-45 connectors on its faceplate. Cooling System The cooling system in a J-EX8208 switch consists of a hot-removable and hot-insertable fan tray. The fan tray contains 12 fans. The fan tray installs vertically on the left front of the chassis and provides side-to-side chassis cooling. For details, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Power Supplies Power supplies for the J-EX8208 switch are fully redundant, load-sharing, and hot-removable and hot-insertable field-replaceable units (FRUs). Each J-EX8208 switch chassis can hold up to six 2000 W AC power supplies. The 2000 W AC power supplies support both low-voltage line (100–120 VAC) and high-voltage line (200–240 VAC) AC power configurations on a J-EX8208 switch. Each 2000 W AC power supply delivers 2000 W of power at high-voltage line (200–240 VAC) or 1200 W at low-voltage line (100–120 VAC) to the J-EX8208 chassis. 37 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Only two AC power supplies are required for the base AC configuration and switch powerup. The redundant AC configuration ships with six AC power supplies to provide the capacity to power the system using N+1 or N+N power redundancy. CAUTION: Mixing different types of power supplies in the same chassis is not supported. Related Documentation • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 185 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • For details about switch FRUs and line cards, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. J-EX8216 Switch Hardware Overview The Dell PowerConnect J-EX Series J-EX8216 Ethernet Switch is a half-rack, midplane architecture, modular Ethernet switch that is designed for ultra high-density environments such as campus aggregation, data center, or high performance core switching environments. J-EX8216 switches provide high-availability and redundancy for all major hardware components, including Routing Engine (RE) modules, Switch Fabric (SF) modules, fan trays (with redundant fans), and load-sharing 2000 W AC and 3000 W AC power supplies. Like other Dell PowerConnect J-EX Series J-EX8200 Ethernet Switches, J-EX8216 switches provide high performance, scalable connectivity, and carrier-class reliability. You can manage J-EX8216 switches using the same interfaces that you use for managing other devices running the Junos operating system (Junos OS)—the command-line interface (CLI) and the J-Web graphical interface. • Software on page 38 • Chassis Physical Specifications, LCD Panel, and Midplane on page 38 • Routing Engines and Switch Fabric on page 40 • Line Cards on page 41 • Cooling System on page 41 • Power Supplies on page 42 Software The J-EX Series Switches run Junos OS, which provides Layer 2 and Layer 3 switching, routing, and security services. The same Junos OS code base that runs on J-EX Series switches also runs on all Dell PowerConnect J-SRX Series Services Gateways. Chassis Physical Specifications, LCD Panel, and Midplane J-EX8216 switches are designed to optimize rack space and cabling. The J-EX8216 switch is 21 rack units (21 U) in size (1/2 rack); two J-EX8216 switches can fit in a standard 42 U rack. See Figure 4 on page 39 and Figure 5 on page 40. For chassis physical specification 38 Chapter 2: Supported Hardware details, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Figure 4: J-EX8216 Switch Front 39 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Figure 5: J-EX8216 Switch Rear The J-EX8216 switch has a chassis-level LCD panel that displays Routing Engine and switch fabric status as well as chassis components’ alarm information for rapid problem identification. The LCD panel provides a user-friendly interface for performing initial switch configuration, rolling back a configuration, or restoring the switch to the factory default configuration. The J-EX8216 chassis midplane distributes the data, control, and management signals to system components and distributes power throughout the system. For details about the LCD panel and midplane, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Routing Engines and Switch Fabric System management and system control functions of a J-EX8216 switch are performed by the Routing Engine (RE) module. An RE module contains a Routing Engine. The RE 40 Chapter 2: Supported Hardware modules are hot-insertable and hot-removable field-replaceable units (FRUs) that are installed in the front of the chassis in the slots labeled RE0 and RE1. A redundant configuration J-EX8216 switch has a second RE module for redundancy. The Switch Fabric (SF) modules provide the switching functionality to a J-EX8216 switch. The SF modules are hot-insertable and hot-removable field-replaceable units (FRUs). All eight SF modules are installed in the rear of the chassis in the slots labeled SF7 through SF0. In a J-EX8216 switch, all eight SF modules are active and must be installed in the switch for normal operation. If a single SF module fails, the input/output traffic for that module is load-balanced among the remaining SF modules, providing graceful degradation in midplane performance. The impact of an SF module failure on the performance of a J-EX8216 switch varies based on the type of line cards installed in the switch and the traffic mix flowing through them. In a J-EX8216 switch configuration that is fully loaded with 8-port 10-Gigabit Ethernet SFP+ line cards, if one SF module fails, the remaining seven SF modules still have sufficient switching capacity to maintain continuous switch operation at full wire-rate performance. For details about the RE and SF modules, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Line Cards The J-EX8216 switch features 16 horizontal line card slots and supports wire-rate performance for all packet sizes for the installed line cards. The line cards in J-EX8200 switches combine a Packet Forwarding Engine and Ethernet interfaces on a single assembly. They are field-replaceable units (FRUs), and you can install them in the slots labeled 0 through 15 on the front of the switch chassis. All line cards are hot-insertable and hot-removable. For line-card details, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. The following line cards are available for J-EX8216 switches: • 8-port 10-Gigabit Ethernet SFP+ line card: This line card has eight 10-gigabit SFP+ ports on its faceplate in which you can install SFP+ transceivers. • 40-port 10-Gigabit Ethernet SFP+ line card: This line card has 40 10-gigabit SFP+ ports on its faceplate in which you can install either SFP+ or SFP transceivers. • 48-port 100/1000 SFP line card: This line card has 48 1-gigabit SFP ports on its faceplate in which you can install SFP transceivers. • 48-port 10/100/1000 RJ-45 line card: This line card has 48 10/100/1000 Gigabit Ethernet ports with RJ-45 connectors on its faceplate. Cooling System The cooling system in a J-EX8216 switch consists of two hot-insertable and hot-removable, field-replaceable unit (FRU) fan trays. Each fan tray contains nine fans. Both fan trays install vertically on the left front of the chassis and provide side-to-side chassis cooling and front-to-side cooling. The top and bottom fan trays are identical and interchangeable. However, only the top fan tray cools the SF modules installed in the 41 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 rear of the chassis. For details, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Power Supplies Power supplies for the J-EX8216 switch are fully redundant, load-sharing, and hot-insertable and hot-removable field-replaceable units (FRUs). Each J-EX8216 switch chassis can hold up to six 2000 W AC or six 3000 W AC power supplies. The 2000 W AC power supplies support both low-voltage line (100–120 VAC) and high-voltage line (200–240 VAC) AC power configurations on a J-EX8216 switch. Each 3000 W AC power supply delivers 3000 W of power at high-voltage line (200–240 VAC) to the J-EX8216 chassis. Low-voltage line input is not supported for the 3000 W AC power supplies on the J-EX8216 switch. The redundant AC configuration ships with six AC power supplies to provide the capacity to power the system using N+1 or N+N power redundancy. For details about the power supplies, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. CAUTION: Mixing different types of power supplies in the same chassis is not a supported configuration. Related Documentation 42 • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 185 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • For details about switch FRUs, slot numbering, and line cards, see the Dell PowerConnect J-Series J-EX8216 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. PART 2 Complete Software Configuration Statement Hierarchy • Complete Software Configuration Statement Hierarchy on page 45 43 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 44 CHAPTER 3 Complete Software Configuration Statement Hierarchy • [edit access] Configuration Statement Hierarchy on page 45 • [edit chassis] Configuration Statement Hierarchy on page 46 • [edit class-of-service] Configuration Statement Hierarchy on page 47 • [edit ethernet-switching-options] Configuration Statement Hierarchy on page 48 • [edit firewall] Configuration Statement Hierarchy on page 51 • [edit forwarding-options] Configuration Statement Hierarchy on page 51 • [edit interfaces] Configuration Statement Hierarchy on page 52 • [edit poe] Configuration Statement Hierarchy on page 57 • [edit protocols] Configuration Statement Hierarchy on page 57 • [edit routing-instances] Configuration Hierarchy on page 63 • [edit snmp] Configuration Statement Hierarchy on page 64 • [edit virtual-chassis] Configuration Statement Hierarchy on page 64 • [edit vlans] Configuration Statement Hierarchy on page 65 [edit access] Configuration Statement Hierarchy access { profile profile-name { accounting { order [ radius | none ]; accounting-stop-on-access-deny; accounting-stop-on-failure; } authentication-order [ authentication-method ]; radius { accounting-server [ server-address ]; authentication-server [ server-address ]; } } } 45 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • For information about connecting a RADIUS servier to a switch and configuring 802.1 RADIUS accounting, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit chassis] Configuration Statement Hierarchy chassis { aggregated-devices { ethernet { device-count number; } } auto-image-upgrade; fpc slot { pic pic-number { sfpplus { pic-modemode; } } power-budget-priority priority; } lcd-menu fpc slot-number { menu-item (menu-name | menu-option); } nssu { upgrade-group group-name { fpcs (slot-number | [list-of-slot-numbers]); member member-id { fpcs (slot-number | [list-of-slot-numbers]); } } } psu { redundancy { n-plus-n; } } redundancy { graceful-switchover; } } Related Documentation 46 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 1081 • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 94 • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • Configuring Graceful Routing Engine Switchover in a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) on page 856 • Configuring Power Supply Redundancy (CLI Procedure) on page 952 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 953 Chapter 3: Complete Software Configuration Statement Hierarchy • Configuring Line-card Upgrade Groups for Nonstop Software Upgrade (CLI Procedure) on page 951 [edit class-of-service] Configuration Statement Hierarchy class-of-service { classifiers { (dscp | ieee-802.1 | inet-precedence) classifier-name { import (classifier-name | default); forwarding-class class-name { loss-priority loss-priority { code-points [ aliases ] [ 6 bit-patterns ]; } } } } code-point-aliases { (dscp | ieee-802.1 | inet-precedence) { alias-name bits; } } congestion-notification-profile profile-name { input{ ieee-802.1 { code-point up-bits pfc; } } forwarding-classes { class class-name queue-num queue-number priority ( high | low ); } interfaces { interface-name { congestion-notification-profile profile-name { input { ieee-802.1 { code-point up-bits pfc; } } } } scheduler-map map-name; unit logical-unit-number { forwarding-class class-name; classifiers { (dscp | ieee-802.1 | inet-precedence) (classifier-name | default); } } } } multi-destination { family { ethernet { broadcast forwarding-class-name; } 47 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 inet { classifiers { (dscp | inet-precedence) classifier-name; } } } scheduler-map map-name; } rewrite-rules { (dscp | ieee-802.1 | inet-precedence) rewrite-name { import (rewrite-name | default); forwarding-class class-name { loss-priority loss-priority code-point (alias | bits); } } } scheduler-maps { map-name { forwarding-class class-name scheduler scheduler-name; } } schedulers { scheduler-name { buffer-size (percent percentage | remainder); drop-profile-map loss-priority loss-priority protocol protocol drop-profile profile-name; priority priority; shaping-rate (rate | percent percentage); transmit-rate (rate | percent percentage | remainder); } } } Related Documentation • For CoS configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit ethernet-switching-options] Configuration Statement Hierarchy ethernet-switching-options { analyzer { name { loss-priority priority; ratio number; input { ingress { interface (all | interface-name); vlan (vlan-id | vlan-name); } egress { interface (all | interface-name); } } output { interface interface-name; 48 Chapter 3: Complete Software Configuration Statement Hierarchy vlan (vlan-id | vlan-name); } } } bpdu-block { disable-timeout timeout; interface (all | [interface-name]); } dot1q-tunneling { ether-type (0x8100 | 0x88a8 | 0x9100); } interfaces interface-name { no-mac-learning; } mac-notification { notification-interval seconds; } mac-table-aging-time seconds; port-error-disable { disable-timeout timeout; } redundant-trunk-group { group name { preempt-cutover-timer seconds; interface primary; } interface } } secure-access-port { static{ vlanvlan-id { macmac-address next-hopinterface-name; } } dhcp-snooping-file { location local_pathname | remote_URL; timeout seconds; write-interval seconds; } interface (all | interface-name) { allowed-mac { mac-address-list; } (dhcp-trusted | no-dhcp-trusted ); fcoe-trusted; mac-limit limit action action; no-allowed-mac-log; static-ip ip-address { vlan vlan-name; mac mac-address; } } vlan (all | vlan-name) { (arp-inspection | no-arp-inspection ); 49 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 dhcp-option82 { circuit-id { prefix hostname; use-interface-description; use-vlan-id; } remote-id { prefix hostname | mac | none; use-interface-description; use-string string; } vendor-id [string]; } (examine-dhcp | no-examine-dhcp ); examine-fip { fc-map fc-map-value; } (ip-source-guard | no-ip-source-guard); mac-move-limit limit action action; } } storm-control { action-shutdown; interface (all | interface-name) { bandwidth bandwidth; no-broadcast; no-multicast; no-registered-multicast; no-unknown-unicast; no-unregistered-multicast; } } traceoptions { file filename ; flag flag ; } unknown-unicast-forwarding { vlan (all | vlan-name) { interface interface-name; } } voip { interface (all | [interface-name | access-ports]) { vlan vlan-name ; forwarding-class (assured-forwarding | best-effort | expedited-forwarding | network-control); } } } Related Documentation 50 • For configuration examples, instructions, and concepts for port mirroring, port security, BPDU protection for spanning-tree protocols, redundant trunk links, storm control, 802.1X and VoIP, Q-in-Q tunneling, unicast forwarding, MAC notification, and FIP Chapter 3: Complete Software Configuration Statement Hierarchy snooping, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. • DHCP Services for J-EX Series Switches Overview on page 457 [edit firewall] Configuration Statement Hierarchy firewall { family family-name { filter filter-name { interface-specific; term term-name { from { match-conditions; } then { action; action-modifiers; } } } } policer policer-name { filter-specific; if-exceeding { bandwidth-limit bps; burst-size-limit bytes; } then { policer-action; } } } Related Documentation • For firewall filters (packet filtering) configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit forwarding-options] Configuration Statement Hierarchy helpers { bootp { dhcp-option82 { circuit-id { prefix hostname; use-interface-description; use-vlan-id; } remote-id { prefix hostname | mac | none; use-interface-description; use-string string; 51 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 } vendor-id ; } interface interface-name { dhcp-option82 { circuit-id { prefix hostname; use-interface-description; use-vlan-id; } remote-id { prefix hostname | mac | none; use-interface-description; use-string string; } vendor-id ; } source-address-giaddr; } source-address-giaddr; } } Related Documentation • DHCP Services for J-EX Series Switches Overview on page 457 • For DHCP and port security configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. • For more information about the [edit forwarding-options] hierarchy and its options, see the Junos OS Policy Framework Configuration Guide. [edit interfaces] Configuration Statement Hierarchy interfaces { aex { accounting-profile name; aggregated-ether-options { (flow-control | no-flow-control); lacp { (active | passive); admin-key key; periodic interval; system-id mac-address; } (link-protection | no-link-protection); link-speed speed; (loopback | no-loopback); minimum-links number; } description text; disable; (gratuitous-arp-reply | no-gratuitous-arp-reply); mtu bytes; no-gratuitous-arp-request; 52 Chapter 3: Complete Software Configuration Statement Hierarchy traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } ge-fpc/pic/port { accounting-profile name; description text; disable; ether-options { 802.3ad { aex; (backup | primary); lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; (loopback | no-loopback); speed (auto-negotiation | speed); } (gratuitous-arp-reply | no-gratuitous-arp-reply); mtu bytes; no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } interface-range name { accounting-profile name; description text; 53 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 disable; ether-options { 802.3ad { aex; (backup | primary); lacp { force-up; } } (auto-negotiation | no-auto-negotiation); (flow-control | no-flow-control); link-mode mode; (loopback | no-loopback); speed (auto-negotiation | speed); } (gratuitous-arp-reply | no-gratuitous-arp-reply); member interface-name; member-range starting-interface name to ending-interface name; mtu bytes; no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } lo0 { accounting-profile name; description text; disable; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} (traps | no-traps); } } me0 { accounting-profile name; description text; 54 Chapter 3: Complete Software Configuration Statement Hierarchy disable; (gratuitous-arp-reply | no-gratuitous-arp-reply); no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } vlan { accounting-profile name; description text; disable; (gratuitous-arp-reply | no-gratuitous-arp-reply); mtu bytes; no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); } } traceoptions { file ; flag flag ; no-remote-trace; } vme { accounting-profile name; description text; disable; (gratuitous-arp-reply | no-gratuitous-arp-reply); mtu bytes; no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); 55 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } xe-fpc/pic/port { accounting-profile name; description text; disable; ether-options { 802.3ad { aex; (backup | primary); lacp { force-up; } } (flow-control | no-flow-control); link-mode mode; (loopback | no-loopback); } (gratuitous-arp-reply | no-gratuitous-arp-reply); mtu bytes; no-gratuitous-arp-request; traceoptions { flag flag; } (traps | no-traps); unit logical-unit-number { accounting-profile name; bandwidth rate; description text; disable; family family-name {...} proxy-arp (restricted | unrestricted); (traps | no-traps); vlan-id vlan-id-number; } vlan-tagging; } } Related Documentation 56 • Configuring Gigabit Ethernet Interfaces (CLI Procedure) on page 1042 • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 1081 • Configuring a Layer 3 Subinterface (CLI Procedure) on page 1089 • Configuring Routed VLAN Interfaces (CLI Procedure) Chapter 3: Complete Software Configuration Statement Hierarchy • Configuring the Virtual Management Ethernet Interface for Global Management of a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) on page 852 • J-EX Series Switches Interfaces Overview on page 999 • Junos OS Network Interfaces Configuration Guide [edit poe] Configuration Statement Hierarchy poe { guard-band watts; interface (all | interface-name) { disable; maximum-power watts; priority (high | low); telemetries { disable; duration hours; interval minutes; } } management (class | static); notification-control { fpc slot-number { disable; } } } Related Documentation • For Power over Ethernet (PoE) configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit protocols] Configuration Statement Hierarchy protocols { connections { remote-interface-switch connection-name { interface interface-name.unit-number; transmit-lsp label-switched-path; receive-lsp label-switched-path; } } dot1x { authenticator { authentication-profile-name profile-name; interface (all | [ interface-names ]) { disable; guest-vlan ( vlan-id | vlan-name); mac-radius ; maximum-requests number; no-reauthentication; quiet-period seconds; 57 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 reauthentication { interval seconds; } retries number; server-fail (deny | permit | use-cache | vlan-id | vlan-name); server-reject-vlan (vlan-id | vlan-name); server-timeout seconds; supplicant (multiple | single | single-secure); supplicant-timeout seconds; transmit-period seconds; } static mac-address { interface interface-name; vlan-assignment (vlan-id |vlan-name); } } igmp-snooping { traceoptions { file filename ; flag flag (detail | disable | receive | send); } vlan (vlan-id | vlan-number) { data-forwarding { source { groups group-prefix; } receiver { source-vlans vlan-list; install ; } } disable { interface interface-name } immediate-leave; interface interface-name { group-limit limit; multicast-router-interface; static (IGMP Snooping) { group ip-address; } } proxy ; query-interval seconds; query-last-member-interval seconds; query-response-interval seconds; robust-count number; } } lldp { disable; advertisement-interval seconds; hold-multiplier number; interface (all | interface-name) { disable; 58 Chapter 3: Complete Software Configuration Statement Hierarchy } lldp-configuration-notification-interval seconds; management-address ip-management-address; netbios-snooping; ptopo-configuration-maximum-hold-time seconds; ptopo-configuration-trap-interval seconds; traceoptions { file filename ; flag flag ; } transmit-delay seconds; } lldp-med { disable; fast-start number; interface (all | interface-name) { disable; location { elin number; civic-based { what number; country-code code; ca-type { number { ca-value value; } } } } } } mpls { interface ( all | interface-name ); label-switched-path lsp-name to remote-provider-edge-switch; path destination { } mstp { disable; bpdu-block-on-edge; bridge-priority priority; configuration-name name; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; log; } cost cost; edge; mode mode; no-root-port; priority priority; 59 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 } max-age seconds; max-hops hops; msti msti-id { vlan (vlan-id | vlan-name); interface interface-name { disable; cost cost; edge; mode mode; priority priority; } } revision-level revision-level; traceoptions { file filename ; flag flag; } } mvrp { disable interface (all | interface-name) { disable; join-timer milliseconds; leave-timer milliseconds; leaveall-timer milliseconds; registration (forbidden | normal); } no-dynamic-vlan; traceoptions { file filename ; flag flag; } } oam { ethernet{ connectivity-fault-management { action-profile profile-name { default-actions { interface-down; } } linktrace { age (30m | 10m | 1m | 30s | 10s); path-database-size path-database-size; } maintenance-domain domain-name { level number; mip-half-function (none | default |explicit); name-format (character-string | none | dns | mac+2oct); maintenance-association ma-name { continuity-check { hold-interval minutes; interval (10m | 10s | 1m | 1s| 100ms); 60 Chapter 3: Complete Software Configuration Statement Hierarchy loss-threshold number; } mep mep-id { auto-discovery; direction down; interface interface-name; remote-mep mep-id { action-profile profile-name; } } } } } link-fault-management { action-profile profile-name; action { syslog; link-down; } event { link-adjacency-loss; link-event-rate; frame-error count; frame-period count; frame-period-summary count; symbol-period count; } interface interface-name { link-discovery (active | passive); pdu-interval interval; event-thresholds threshold-value; remote-loopback; event-thresholds { frame-errorcount; frame-period count; frame-period-summary count; symbol-period count; } } negotiation-options { allow-remote-loopback; no-allow-link-events; } } } } rstp { disable; bpdu-block-on-edge; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; 61 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 log; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; } traceoptions { file filename ; flag flag; } } sflow { agent-id; collector { ip-address; udp-port port-number; } disable; interfaces interface-name { disable; polling-interval seconds; sample-rate { egress number; ingress number; } } polling-interval seconds; sample-rate { egress number; ingress number; } source-ip; } stp { disable; bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { disable; bpdu-timeout-action { block; log; } cost cost; edge; mode mode; no-root-port; priority priority; } max-age seconds; 62 Chapter 3: Complete Software Configuration Statement Hierarchy } traceoptions { file filename ; flag flag; } uplink-failure-detection { group group-name { link-to-monitor interface-name; link-to-disable interface-name; } } vstp { bpdu-block-on-edge; disable; force-version stp; vlan (all | vlan-id | vlan-name) { bridge-priority priority; forward-delay seconds; hello-time seconds; interface (all | interface-name) { bpdu-timeout-action { log; block; } cost cost; disable; edge; mode mode; no-root-port; priority priority; } max-age seconds; traceoptions { file filename ; flag flag; } } } } Related Documentation • For protocol configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit routing-instances] Configuration Hierarchy routing-instances routing-instance-name { instance-type virtual-router interface interface-name } 63 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • For routing configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. [edit snmp] Configuration Statement Hierarchy snmp { rmon { history index { bucket-size number; interface interface-name; interval seconds; owner owner-name; } } } Related Documentation • For SNMP configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. • Junos OS Network Management Configuration Guide [edit virtual-chassis] Configuration Statement Hierarchy virtual-chassis { auto-sw-update { package-name package-name; } fast-failover (ge | vcp disable | xe); id id; mac-persistence-timer seconds; member member-id { location location mastership-priority number; no-management-vlan; serial-number; role; } no-split-detection; preprovisioned; traceoptions { file filename ; flag flag ; } } Related Documentation 64 • Example: Configuring a J-EX4200 Virtual Chassis with a Master and Backup in a Single Wiring Closet on page 736 Chapter 3: Complete Software Configuration Statement Hierarchy • Example: Configuring a J-EX4200 Virtual Chassis Interconnected Across Multiple Wiring Closets on page 762 • Example: Configuring a J-EX4200 Virtual Chassis Using a Preprovisioned Configuration File on page 788 • Configuring a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) on page 822 • J-EX4200 and J-EX4500 Virtual Chassis Overview on page 709 [edit vlans] Configuration Statement Hierarchy vlans { vlan-name { description text-description; dot1q-tunneling { customer-vlans (id | native | range); layer2-protocol-tunneling all | protocol-name { drop-threshold number; shutdown-threshold number; } } filter input filter-name; filter output filter-name; interface interface-name { mapping (native (push | swap) | policy | tag (push | swap)); pvlan-trunk; } isolation-id id-number; l3-interface vlan.logical-interface-number; mac-limit number; mac-table-aging-time seconds; no-local-switching; no-mac-learning; primary-vlan vlan-name; vlan-id number; vlan-range vlan-id-low-vlan-id-high; } } Related Documentation • For VLAN configuration examples, instructions, and concepts, see the Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS: Volume 2 at http://www.support.dell.com/manuals. 65 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 66 PART 3 Software Installation • Software Installation Overview on page 69 • Installing Junos OS on page 79 • Booting the Switch, Upgrading Software, and Managing Licenses on page 91 • Verifying Software Installation on page 99 • Troubleshooting Software Installation on page 107 • Configuration Statements for Software Installation on page 117 • Operational Commands for Software Installation on page 119 67 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 68 CHAPTER 4 Software Installation Overview • Installation Overview on page 69 • Licenses Overview on page 75 Installation Overview • Understanding Software Installation on J-EX Series Switches on page 69 • Junos OS Package Names on page 72 • Understanding System Snapshot on J-EX Series Switches on page 72 • Understanding Resilient Dual-Root Partitions on Switches on page 74 Understanding Software Installation on J-EX Series Switches A J-EX Series Switch is delivered with the Junos operating system (Junos OS) preinstalled. As new features and software fixes become available, you must upgrade your software to use them. You can also downgrade Junos OS to a previous release. This topic covers: • Overview of the Software Installation Process on page 69 • Software Package Security on page 70 • Installing Software on a Virtual Chassis on page 70 • Installing Software on J-EX8200 Switches with Redundant Routing Engines on page 71 • Installing Software Using Automatic Software Download on page 71 • Troubleshooting Software Installation on page 71 Overview of the Software Installation Process A J-EX Series switch is delivered with Junos OS preinstalled. When you connect power to the switch, it starts (boots) up from the installed software. You upgrade Junos OS on a J-EX Series switch by copying a software package to your switch or another system on your local network, then use either the J-Web interface or the CLI to install the new software package on the switch. Finally, you reboot the switch; it boots from the upgraded software. After a successful upgrade, you should back up the new current configuration to a secondary device. 69 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 NOTE: To access the J-Web interface, your management device must have the following software installed: • Operating system: Microsoft Windows XP Service Pack 3 • Browser version: One of the following. Other browsers might work but are not supported by J-Series platforms. • • Microsoft Internet Explorer version 7.0 • Mozilla Firefox version 3.0 Additional requirements: • Only English-language browsers are supported. • The browser and the network must be able to receive and process HTTP/1.1 gzip compressed data. During a successful upgrade, the upgrade package removes all files from /var/tmp and completely reinstalls the existing software. It retains configuration files, and similar information, such as secure shell and host keys, from the previous version. If the software installation fails for any reason, such as loss of power during the installation process, the system returns to the originally active installation when you reboot. At the completion of a successful software upgrade, we recommend that you use the request system snapshot command to copy the contents of the primary root partition to the alternate root partition. Software Package Security All Junos OS releases are delivered in signed packages that contain digital signatures to ensure official Juniper Networks software. For more information about signed software packages, see the Junos OS Installation and Upgrade Guide. Installing Software on a Virtual Chassis You can connect individual J-EX Series switches together to form one unit and manage the unit as a single device, called a Virtual Chassis. The Virtual Chassis operates as a single network entity composed of members. Each member of a Virtual Chassis runs a Junos OS package. Supported Virtual Chassis include J-EX4200 Virtual Chassis, J-EX4500 Virtual Chassis, and mixed J-EX4200 and J-EX4500 Virtual Chassis. For ease of management, a Virtual Chassis provides flexible methods to upgrade software releases. You can deploy a new software release to all members of a Virtual Chassis or to only a particular member. 70 Chapter 4: Software Installation Overview Installing Software on J-EX8200 Switches with Redundant Routing Engines You can install software on a J-EX8200 switch with redundant Routing Engines in one of two ways: • Perform a nonstop software upgrade (NSSU)—An NSSU upgrades both Routing Engines with a single command and with a minimum of network disruption. An NSSU takes advantage of graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) to ensure no disruption to the control plane. You can minimize disruption to network traffic by defining link aggregation groups (LAGs) such that the member links of each LAG reside on different line cards. The line cards are upgraded one at a time, so that traffic continues to flow through the other line cards while a line card is being upgraded. You cannot use NSSU to downgrade the software running on a switch. For more information about NSSU, see “Understanding Nonstop Software Upgrade on J-EX Series Switches” on page 932. • Upgrade each Routing Engine manually—You can perform a Junos OS installation on each Routing Engine separately, starting with the backup Routing Engine. You can use this procedure to downgrade the software running on a switch. See “Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure)” on page 81. Installing Software Using Automatic Software Download The automatic software download feature uses the DHCP message exchange process to download and install software packages. Users can define a path to a software package on the DHCP server, and then the DHCP server communicates this path to J-EX Series switches acting as DHCP clients as part of the DHCP message exchange process. The DHCP clients that have been configured for automatic software download receive these messages and, when the software package name in the DHCP server message is different from that of the software package that booted the DHCP client switch, download and install the software package. See “Upgrading Software Using Automatic Software Download on J-EX Series Switches” on page 94. Troubleshooting Software Installation If the Junos OS loads but the CLI is not working for any reason, or if the switch has no software installed, you can use the recovery installation procedure to install the software on the switch. See “Troubleshooting Software Installation” on page 107. NOTE: You can also use this procedure to load two versions of Junos OS in separate partitions on the switch. Related Documentation • Downloading Software Packages from Juniper Networks on page 79 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 71 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 81 • Understanding Nonstop Software Upgrade on J-EX Series Switches on page 932 • Understanding Resilient Dual-Root Partitions on Switches on page 74 Junos OS Package Names You upgrade Junos OS on a J-EX Series Switch by copying a software package to your switch or another system on your local network, then install the new software package on the switch. A software package name is in the following format: package-name-m.nZx.y-domestic-signed.tgz where: • package-name is the name of the package—for example, jinstall-ex-4200. • m.n is the software release, with m representing the major release number and n representing the minor release number—for example, 10.2. • Z indicates the type of software release, where R indicates released software and B indicates beta-level software. • x.y represents the version of the major software release (x) and an internal tracking number (y)—for example, 1.6. • domestic-signed is appended to all J-EX Series package names. For most Junos OS packages, domestic is used for the United States and Canada and export for worldwide distribution. However, for J-EX Series software, domestic is used for worldwide distribution as well. A sample J-EX Series software package name is: jinstall-ex-4200-10.2R1.6-domestic-signed.tgz Related Documentation • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 81 • Downloading Software Packages from Juniper Networks on page 79 • Understanding Software Installation on J-EX Series Switches on page 69 Understanding System Snapshot on J-EX Series Switches You can create copies of the software running a J-EX Series Switch using the system snapshot feature. The system snapshot feature takes a “snapshot” of the files currently used to run the switch—the complete contents of the /config and /var directories, which 72 Chapter 4: Software Installation Overview include the running Junos OS, the active configuration, and the rescue configuration—and copies all these files into an alternate (internal, meaning internal flash, or an external, meaning USB flash) memory source. You can then use this snapshot to boot the switch at the next bootup or as a backup boot option. You can only use snapshots to move files to external memory if the switch was booted from internal memory, or to move files to internal memory if the switch was booted from external memory. You cannot create a snapshot in the memory source that booted the switch even if the snapshot is being created on a different partition in the same memory source. Snapshots are particularly useful for moving files onto USB flash drives. You cannot use the copy command or any other file-moving technique to move files from an internal memory source to USB memory on the switch. System snapshots on J-EX Series switches have the following limitations: Related Documentation • You cannot use snapshots to move files to any destination outside of the switch other than an installed external USB flash drive or to move files between switches that are members of the same Virtual Chassis. • Snapshot commands, like other Virtual Chassis commands, are always executed on a local switch. In cases where a different member switches of the same Virtual Chassis requests the snapshot, the snapshot command is pushed to the Virtual Chassis member creating the snapshot and then executed. The output is then returned to the switch that initiated the process. For instance, if the command to create an external snapshot on Virtual Chassis member 3 is entered from Virtual Chassis member 1, the snapshot of internal memory on Virtual Chassis member 3 is taken on external memory on Virtual Chassis member 3. The output of the process is seen from Virtual Chassis member 1. No files move between the switches. • Understanding Software Installation on J-EX Series Switches on page 69 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 92 73 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Understanding Resilient Dual-Root Partitions on Switches Resilient dual-root partitioning, introduced on J-EX Series Ethernet Switches in Junos operating system (Junos OS) Release 10.4R3, provides additional resiliency to switches in the following ways: • Allows the switch to boot transparently from the second root partition if the system fails to boot from the primary root partition. • Provides separation of the root Junos OS file system from the /var file system. If corruption occurs in the /var file system (a higher probability than in the root file system due to the greater frequency in /var of reads and writes), the root file system is insulated from the corruption. This topic covers: • Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and Later) on page 74 • Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) on page 74 • Understanding Upgrading or Downgrading Between Resilient Dual-Root Partition Releases and Earlier Releases on page 75 Resilient Dual-Root Partition Scheme (Junos OS Release 10.4R3 and Later) J-EX Series switches that ship with Junos OS Release 10.4R3 or later are configured with a root partition scheme that is optimized for resiliency, as shown in Table 26 on page 74. Table 26: Resilient Dual-Root Partition Scheme Slice 1 Slice 2 Slice 3 s1a s2a s3e s3d s4d / / /var /var/tmp /config (root Junos OS ) (root Junos OS ) Slice 4 In the resilient dual-root partition scheme, the /var file system is contained in a separate slice from the root file systems, the /config directory is contained in its own slice, and switches ship from the factory with identical Junos OS images in slice 1 and slice 2. The /var file system, which has a greater frequency of reads and writes than the root file systems and is therefore more likely to have corruption issues, is isolated from the root directories and the /config directory. If the switch fails to boot, the system automatically boots from the alternate root partition. (If the switch fails to boot from the active root partition and instead boots from the alternate root partition, an alarm is triggered.) Earlier Partition Scheme (Junos OS Release 10.4R2 and Earlier) The earlier partition scheme is shown in Table 27 on page 75. 74 Chapter 4: Software Installation Overview Table 27: Earlier Partition Scheme Slice 2 Slice 1 Slice 3 s1a s1f s2a s2f s3d s3e / /var (empty until initial software upgrade) (empty until initial software upgrade) /var/tmp /config (root Junos OS) This is the partitioning scheme for a switch shipped with Release 10.4R2 or earlier (or after you reformat the disk during a downgrade from Release 10.4R3 or later to Release 10.4R2 or earlier). In this partitioning scheme, the switch comes from the factory with only one Junos OS image installed in the root Junos OS partition of slice 1. The first time that you perform a software upgrade, the new Junos OS image is installed in slice 2. If the switch fails to boot, you must manually trigger it to boot from the alternate partition (rebooting from the alternate partition does not occur automatically). Understanding Upgrading or Downgrading Between Resilient Dual-Root Partition Releases and Earlier Releases Upgrading from Release 10.4R2 or earlier to Release 10.4R3 or later differs from other upgrades in two important ways: • You must install a new loader software package in addition to installing the new Junos OS image. • Rebooting after the upgrade reformats the disk from three partitions to four partitions. You can perform all operations for this special software upgrade from the CLI. CAUTION: Back up any important log files because the /var/log files are not saved or restored during an upgrade from a nonresilient dual-root partitions release to a release that supports resilient dual-root partitions. We recommend that you also save your /config files and any important log files to an external medium because if there is a power interruption during the upgrade process, they could be lost. Related Documentation • Resilient Dual-Root Partitions Frequently Asked Questions on page 111 • Upgrading EX Series Switches to Support Resilient Dual-Root Partitions • Understanding Software Licenses for J-EX Series Switches on page 76 • License Key Components for the J-EX Series Switch on page 77 Licenses Overview 75 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Understanding Software Licenses for J-EX Series Switches To enable and use some Junos OS features, you must purchase, install, and manage separate software licenses. If the switch has the appropriate software license, you can configure and use these features. NOTE: The advanced feature license (AFL) software license is not currently available for J-EX4500 switches. The Junos OS feature license (the purchased authorization code) is universal. However, to conform to Junos OS feature licensing requirements, you must install a unique license key (a combination of the authorization code and the switch’s serial number) on each switch. For a Virtual Chassis deployment, two license keys are recommended for redundancy: one for the master switch and the other for the backup switch. You do not need additional license keys for the other member switches that you include within a Virtual Chassis. This topic describes: • Features Requiring a License on page 76 • License Warning Messages on page 76 Features Requiring a License The following Junos OS features require an Advanced Feature License (AFL): • Border Gateway Protocol (BGP) and multiprotocol BGP (MBGP) • Intermediate System-to-Intermediate System (IS-IS) • IPv6 protocols: OSPFv3, RIPng, IS-IS for IPv6, IPv6 BGP • MPLS with RSVP-based label-switched paths (LSPs) and MPLS-based circuit cross-connects (CCCs) You can purchase a license for your J-EX Series switch model. The license allows you to run all the advanced software features on your switch. For information about how to purchase a software license, contact Dell. NOTE: The AFL software license is not currently available for J-EX4500 switches. License Warning Messages For using features that require a license, you must install and configure a license key. To obtain a license key, use the contact information provided in your certificate. If you have not purchased the AFL and installed the license key, you receive warnings when you try to commit the configuration: 76 Chapter 4: Software Installation Overview [edit protocols] user@switch# bgp warning: requires ’bgp’ license error: commit failed: (statements constraint check failed) The system generates system log (syslog) alarm messages notifying you that the feature requires a license—for example: Sep 3 05:59:11 craftd[806]: Minor alarm set, BGP Routing Protocol usage requires a license Sep 3 05:59:11 alarmd[805]: Alarm set: License color=YELLOW, class=CHASSIS, reason=BGP Routing Protocol usage requires a license Sep 3 05:59:11 alarmd[805]: LICENSE_EXPIRED: License for feature bgp(47) expired Output of the show system alarms command displays the active alarms: user@switch> show system alarms 1 alarm currently active Alarm time Class 2009-09-03 06:00:11 UTC Minor Related Documentation Description BGP Routing Protocol usage requires a license • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 95 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 96 • Monitoring Licenses for the J-EX Series Switch on page 104 • License Key Components for the J-EX Series Switch on page 77 • J-EX Series Switch Software Features Overview on page 3 License Key Components for the J-EX Series Switch When you purchase a license for a Junos OS feature that requires a separate license, you receive a license key. A license key consists of two parts: • License ID—Alphanumeric string that uniquely identifies the license key. When a license is generated, it is given a license ID. • License data—Block of binary data that defines and stores all license key objects. For example, in the following typical license key, the string Junos204558 is the license ID, and the trailing block of data is the license data: Junos204558 aeaqea qmijhd amrqha ztfmbu gqzama uqceds ra32zr lsevik ftvjed o4jy5u fynzzj mgviyl kgioyf ardb5g sj7wnt rsfked wbjf5a sg The license data defines the device ID for which the license is valid and the version of the license. Related Documentation • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 95 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 96 • Software Licenses for the J-EX Series Switch Overview on page 76 77 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 78 CHAPTER 5 Installing Junos OS • Downloading Software Packages on page 79 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) on page 81 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Rebooting or Halting the J-EX Series Switch (J-Web Procedure) on page 88 Downloading Software Packages To upgrade Junos OS on your Dell PowerConnect J-EX Series switch, you can download software packages from the Dell PowerConnect J-Series—Juniper Networks partner website. Before you can begin to download software upgrades, ensure that you have registered your J-EX Series switch and obtained an account. To register for an account: 1. Locate the chassis serial number (not the Dell Service Tag) on your J-EX Series switch. 2. Go to http://www.juniper.net/partners/dell/ and click Register for an Account. 3. Fill out the registration information required. When your user registration is approved, you receive login information and credentials at the e-mail address you used for registration. If your registration is delayed or additional information is required, you receive a message with further instructions. 4. Save the login information and credentials you receive to use for software download. To download software upgrades from the Dell PowerConnect J-Series—Juniper Networks partner website: 1. Go to http://www.juniper.net/partners/dell/. 2. Select J-EX. 3. Select the appropriate software package for your application. See “Junos OS Package Names” on page 72. 4. Download the software to a local host or to an internal software distribution site. 79 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 If you have questions, contact Dell Customer Support at http://www.support.dell.com. Related Documentation • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Understanding Software Installation on J-EX Series Switches on page 69 Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) You can use this procedure to upgrade Junos OS on a J-EX Series switch with a single Routing Engine, including an individual member of a J-EX4200 Virtual Chassis or all members of a J-EX4200 Virtual Chassis, or a J-EX8200 switch using a single Routing Engine. To upgrade software on a J-EX8200 switch running two Routing Engines, see “Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure)” on page 81. NOTE: Upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later requires that you also upgrade the loader software. See the release notes for instructions on how to upgrade from Release 10.4R2 or earlier to Release 10.4R3 or later. To install software upgrades on a switch with a single Routing Engine: 1. Download the software package as described in “Downloading Software Packages” on page 79. 2. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide for instructions on performing this task. 3. (Optional) Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory. This step is optional because Junos OS can also be upgraded when the software image is stored at a remote location. These instructions describe the software upgrade process for both scenarios. 4. Install the new package on the switch: user@switch> request system software addpackage Replace package with one of the following paths: • For a software package in a local directory on the switch—/var/tmp/package.tgz. • For a software package on a remote server: • ftp://hostname/pathname/package.tgz • http://hostname/pathname/package.tgz where package.tgz is, for example, jinstall-ex-4200-10.2R1.8-domestic-signed.tgz. 80 Chapter 5: Installing Junos OS Include the optional member option to install the software package on only one member of a Virtual Chassis: user@switch> request system software add source member member-id reboot Other members of the Virtual Chassis are not affected. To install the software on all members of the Virtual Chassis, do not include the member option. NOTE: To abort the installation, do not reboot your device; instead, finish the installation and then issue the request system software delete package.tgz command, where package.tgz is, for example, jinstall-ex-4200-10.2R1.8-domestic-signed.tgz. This is your last chance to stop the installation. 5. Reboot to start the new software: user@switch> request system reboot 6. After the reboot has completed, log in and verify that the new version of the software is properly installed: user@switch> show version Related Documentation • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Troubleshooting Software Installation on page 107 • Junos OS Package Names on page 72 • Understanding Software Installation on J-EX Series Switches on page 69 Installing Software on a J-EX8200 Switch with Redundant Routing Engines (CLI Procedure) For a J-EX8200 switch with redundant Routing Engines, you can minimize disruption to network operation during a Junos OS upgrade by upgrading the Routing Engines separately, starting with the backup Routing Engine. NOTE: Upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later requires that you also upgrade the loader software. See the release notes for instructions on how to upgrade from Release 10.4R2 or earlier to Release 10.4R3 or later. NOTE: If your switch is running Junos OS Release 10.4 or later, you can upgrade the software packages on both Routing Engines with a single command and with minimal network disruption by using nonstop software upgrade (NSSU) instead of this procedure. See “Upgrading Software on a J-EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure)” on page 955. 81 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 WARNING: If graceful routing engine switchover (GRES) or nonstop active routing (NSR) is enabled when you initiate a software installation, the software does not install properly. Make sure you issue the CLI command delete chassis redundancy when prompted. If GRES is enabled, it will be removed with the redundancy command. By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit routing-options] hierarchy level to disable it. To upgrade the software package on a J-EX8200 switch with one installed Routing Engine, see “Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure)” on page 80. To upgrade redundant Routing Engines, you first install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine. After making sure that the new software version is running correctly on the backup Routing Engine, you switch device control to the backup Routing Engine. Finally, you install the new software on the new backup Routing Engine. To upgrade Junos OS on the switch, perform the following tasks: 1. Preparing the Switch for the Software Installation on page 82 2. Installing Software on the Backup Routing Engine on page 83 3. Installing Software on the Default Master Routing Engine on page 84 4. Returning Routing Control to the Default Master Routing Engine (Optional) on page 85 Preparing the Switch for the Software Installation Perform the following steps before installing the software: 1. Log in to the master Routing Engine’s console. For information on logging in to the Routing Engine through the console port, see “Connecting and Configuring a J-EX Series Switch (CLI Procedure)” on page 185. 2. Enter the Junos OS CLI configuration mode: a. Start the CLI from the shell prompt: user@switch:RE% cli You will see: {master} user@switch> b. Enter configuration mode: user@switch> configure You will see: {master}[edit] 82 Chapter 5: Installing Junos OS user@switch# 3. Disable nonstop active routing (NSR) (supported on switches running Junos OS Release 10.4 or later): {master}[edit] user@switch# delete routing-options nonstop-routing 4. Disable graceful Routing Engine switchover (GRES): {master}[edit] user@switch# deactivate chassis redundancy graceful-switchover 5. Save the configuration change on both Routing Engines: {master}[edit] user@switch# commit synchronize NOTE: To ensure the most recent configuration changes are committed before the software upgrade, perform this step even if nonstop active routing and graceful Routing Engine switchover (GRES) were previously disabled. 6. Exit the CLI configuration mode: [edit] user@switch# exit 7. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide for instructions on performing this task. Installing Software on the Backup Routing Engine After you have prepared the switch for software installation, install the software on the backup Routing Engine. During the installation, the master Routing Engine continues operations, minimizing the disruption to network traffic. 1. Download the software by following the procedures in “Downloading Software Packages from Juniper Networks” on page 79. 2. Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory. 3. Log in to the console of the backup Routing Engine. 4. Install the new software package: user@switch> request system software add /var/tmp/package.tgz where package.tgz is, for example, jinstall-ex-8200–10.2R1.5–domestic-signed.tgz. 83 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 NOTE: To abort the installation, do not reboot your device; instead, finish the installation and then issue the request system software delete package.tgz command, where package.tgz is, for example, jinstall-ex-8200–10.2R1.8–domestic-signed.tgz. This is your last chance to stop the installation. 5. Reboot to start the new software: user@switch> request system reboot Reboot the system? [yes, no] (no) yes NOTE: You must reboot the switch to load the new installation of the Junos OS. 6. After the reboot has completed, log in and verify the new version of the software is properly installed: user@switch> show version Installing Software on the Default Master Routing Engine To transfer control to the backup Routing Engine and then upgrade or downgrade the master Routing Engine software: 1. Log in to the master Routing Engine console port. 2. Transfer control to the backup Routing Engine: CAUTION: Because graceful Routing Engine switchover is disabled, this switchover causes all line cards in the switch to reload. All network traffic passing through these line cards is lost during the line card reloads. user@switch> request chassis routing-engine master switch 3. Verify that the default backup Routing Engine (shown as slot 1 in the command output) is now the master Routing Engine: user@switch> show chassis routing-engine You will see: Routing Engine status: Slot 0: Current state Election priority Routing Engine status: Slot 1: Current state Election priority Backup Master (default) Master Backup (default) 4. Install the new software package: 84 Chapter 5: Installing Junos OS user@switch> request system software add package.tgz 5. Reboot the Routing Engine: user@switch> request system reboot Reboot the system? [yes, no] (no) yes When the reboot completes, the prompt will reappear. Wait for this prompt to reappear before proceeding to the next step. 6. Log in to the default backup Routing Engine (slot 1) through the console port. 7. Re-enable graceful Routing Engine switchover: [edit] user@switch# activate chassis redundancy graceful-switchover Re-enabling graceful Routing Engine switchover allows any future Routing Engine switchovers to occur without loss of any network traffic. 8. Re-enable nonstop active routing: [edit] user@switch# set routing-options nonstop-routing NOTE: Automatic commit synchronization is a requirement for nonstop active routing. If you have not yet enabled it, do so with the set system commit synchronize command. 9. Save the configuration change: [edit] user@switch# commit synchronize 10. Log in and verify the version of the software installed. If you want to return routing control to the Routing Engine that was the master Routing Engine at the beginning of the procedure (the default master Routing Engine), perform the next task. Returning Routing Control to the Default Master Routing Engine (Optional) The switch can maintain normal operations with the Routing Engine in slot 1 acting as the master Routing Engine after the software upgrade, so only perform this task if you want to return routing control to the default master Routing Engine in slot 0. 1. Transfer routing control back to the default master Routing Engine: user@switch> request chassis routing-engine master switch 2. Verify that the default master Routing Engine (slot 0) is indeed the master Routing Engine: user@switch> show chassis routing-engine You will see: Routing Engine status: Slot 0: 85 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Current state Election priority Routing Engine status: Slot 1: Current state Election priority Related Documentation Master Master (default) Backup Backup (default) • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Upgrading Software on a J-EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure) on page 955 • Troubleshooting Software Installation on page 107 • Junos OS Package Names on page 72 • Understanding Software Installation on J-EX Series Switches on page 69 • For more information about J-EX8208 switch component and functionality redundancy, see the Dell PowerConnect J-Series J-EX8208 Ethernet Switch Hardware Guide at http://www.support.dell.com/manuals. Installing Software on J-EX Series Switches (J-Web Procedure) You can upgrade software packages on a single fixed-configuration switch, on an individual member of a Virtual Chassis, or for all members of a Virtual Chassis. You can use the J-Web interface to install software upgrades from a server using FTP or HTTP, or by copying the file to the J-EX Series switch. 86 Chapter 5: Installing Junos OS NOTE: To access the J-Web interface, your management device must have the following software installed: • Operating system: Microsoft Windows XP Service Pack 3 • Browser version: One of the following. Other browsers might work but are not supported by J-Series platforms. • • Microsoft Internet Explorer version 7.0 • Mozilla Firefox version 3.0 Additional requirements: • Only English-language browsers are supported. • The browser and the network must be able to receive and process HTTP/1.1 gzip compressed data. This topic describes: 1. Installing Software Upgrades from a Server on page 87 2. Installing Software Upgrades by Uploading Files on page 88 Installing Software Upgrades from a Server To install software upgrades from a remote server by using FTP or HTTP: 1. Download the software package as described in “Downloading Software Packages from Juniper Networks” on page 79. 2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives. 3. In the J-Web interface, select Maintain > Software > Install Package. 4. On the Install Remote page, enter information into the fields described in Table 28 on page 87. 5. Click Fetch and Install Package. The software is activated after the switch has rebooted. Table 28: Install Remote Summary Field Function Your Action Package Location (required) Specifies the FTP or HTTP server, file path, and software package name. Type the full address of the software package location on the FTP or HTTP server—one of the following: ftp://hostname/pathname/package-name http://hostname/pathname/package-name 87 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 28: Install Remote Summary (continued) Field Function Your Action User Specifies the username, if the server requires one. Type the username. Password Specifies the password, if the server requires one. Type the password. Reboot If Required If this box is checked, the switching platform is automatically rebooted when the upgrade is complete. Check the box if you want the switching platform to reboot automatically when the upgrade is complete. Installing Software Upgrades by Uploading Files To install software upgrades by uploading files: 1. Download the software package. 2. In the J-Web interface, select Maintain>Software>Upload Package. 3. On the Upload Package page, enter information into the fields described in Table 29 on page 88. 4. Click Upload and Install Package. The software is activated after the switching platform has rebooted. Table 29: Upload Package Summary Field Function Your Action File to Upload (required) Specifies the location of the software package. Type the location of the software package, or click Browse to navigate to the location. Reboot If Required Specifies that the switching platform is automatically rebooted when the upgrade is complete. Select the check box if you want the switching platform to reboot automatically when the upgrade is complete. Related Documentation • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Understanding Software Installation on J-EX Series Switches on page 69 • Troubleshooting Software Installation on page 107 Rebooting or Halting the J-EX Series Switch (J-Web Procedure) You can use the J-Web interface to schedule a reboot or to halt the switching platform. To reboot or halt the switching platform by using the J-Web interface: 88 Chapter 5: Installing Junos OS 1. In the J-Web interface, select Maintain > Reboot. 2. Select one: • Reboot Immediately—Reboots the switching platform immediately. • Reboot in number of minutes—Reboots the switch in the number of minutes from now that you specify. • Reboot when the system time is hour:minute —Reboots the switch at the absolute time that you specify, on the current day. You must select a 2-digit hour in 24-hour format and a 2-digit minute. • Halt Immediately— Stops the switching platform software immediately. After the switching platform software has stopped, you can access the switching platform through the console port only. 3. (Optional) In the Message box, type a message to be displayed to any users on the switching platform before the reboot occurs. 4. Click Schedule. The J-Web interface requests confirmation to perform the reboot or halt. 5. Click OK to confirm the operation. Related Documentation • • If the reboot is scheduled to occur immediately, the switch reboots. You cannot access the J-Web interface until the switch has restarted and the boot sequence is complete. After the reboot is complete, refresh the browser window to display the J-Web interface login page. • If the reboot is scheduled to occur in the future, the Reboot page displays the time until reboot. You have the option to cancel the request by clicking Cancel Reboot on the J-Web interface Reboot page. • If the switch is halted, all software processes stop and you can access the switching platform through the console port only. Reboot the switch by pressing any key on the keyboard. Starting the J-Web Interface on page 160 89 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 90 CHAPTER 6 Booting the Switch, Upgrading Software, and Managing Licenses • Registering the Switch on page 91 • Booting the Switch on page 91 • Upgrading Software on page 94 • Managing Licenses on page 95 Registering the Switch Booting the Switch • Booting a J-EX Series Switch Using a Software Package Stored on a USB Flash Drive on page 91 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 92 Booting a J-EX Series Switch Using a Software Package Stored on a USB Flash Drive There are two methods of getting Junos OS onto a USB flash drive before using the software to boot the switch. You can pre-install the software onto the USB flash drive before inserting the USB flash drive into the USB port, or you can use the system snapshot feature to copy files from internal switch memory to the USB flash drive. To move files into USB flash memory using a system snapshot and use those files to boot the switch, see “Creating a Snapshot and Using It to Boot a J-EX Series Switch” on page 92. We recommend that you use this method to boot the switch from a USB flash drive if your switch is running properly. If you need to pre-install the software onto the USB flash drive, you can use the method described in this topic. Pre-installing the Junos OS onto a USB flash drive to boot the switch can be done at any time and is particularly useful when the switch boots to the loader prompt because the switch cannot locate the Junos OS in internal flash memory. Ensure that you have the following tools and parts available to boot the switch from a USB flash drive: 91 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • A USB flash drive that meets the J-EX Series switch USB port specifications. For information, see the Dell PowerConnect J-Series Ethernet Switch hardware guides at http://www.support.dell.com/manuals. • A computer or other device that you can use to download the software package from the Internet and copy it to the USB flash drive. To download a Junos OS package onto a USB flash drive before inserting the USB flash drive: 1. Download the Junos OS package that you would like to place onto the J-EX Series switch from the Internet onto the USB flash drive using your computer or other device. See “Downloading Software Packages from Juniper Networks” on page 79. 2. Remove the USB flash drive from the computer or other device. 3. Insert the USB flash drive into the USB port on the switch. 4. This step can only be performed when the prompt for the loader script (loader>) is displayed. The loader script starts when the Junos OS loads but the CLI is not working for any reason or if the switch has no software installed. Install the software package onto the switch: loader> install source where source represents the name and location of the Junos OS package on the USB flash drive. The Junos OS package on a flash drive is commonly stored in the root drive as the only file—for example, file:///jinstall-ex-4200-10.2R1.5-domestic-signed.tgz. Related Documentation • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • For the location of the USB port on your switch, see the Dell PowerConnect J-Series Ethernet Switch hardware guides at http://www.support.dell.com/manuals. • Understanding Software Installation on J-EX Series Switches on page 69 Creating a Snapshot and Using It to Boot a J-EX Series Switch The system snapshot feature takes a “snapshot” of the files currently used to run the J-EX Series switch—the complete contents of the /config and /var directories, which include the running Junos OS, the active configuration, and the rescue configuration—and copies all of these files into an alternate (internal, meaning internal flash, or an external, meaning USB flash) memory source. You can then use these snapshots to boot the switch at the next bootup or as a backup boot option. This topic includes the following tasks: 1. Creating a Snapshot on a USB Flash Drive and Using It to Boot the Switch on page 93 2. Creating a Snapshot on an Internal Flash Drive and Using it to Boot the Switch on page 93 92 Chapter 6: Booting the Switch, Upgrading Software, and Managing Licenses Creating a Snapshot on a USB Flash Drive and Using It to Boot the Switch A snapshot can be created on USB flash memory after a switch is booted using files stored in internal memory. Ensure that you have the following tools and parts available before creating a snapshot on a USB flash drive: • A USB flash drive that meets the J-EX Series switch USB port specifications. For information, see the Dell PowerConnect J-Series Ethernet Switch hardware guides at http://www.support.dell.com/manuals. To create a snapshot on USB flash memory and use it to boot the switch: 1. Place the snapshot into USB flash memory: user@switch> request system snapshot partition media external slice 1 NOTE: This example uses the partition option. If you have already created a partition for the snapshot, you don’t need to use the partition option. 2. (Optional) Perform this step if you want to boot the switch now using the snapshot stored on the USB flash drive. If you created the snapshot as a backup, do not perform this step. • To reboot the switch using the most recently created snapshot: user@switch> request system reboot media external • To reboot the switch using a snapshot in a specific partition on the USB flash drive: user@switch> request system reboot media external slice 1 Creating a Snapshot on an Internal Flash Drive and Using it to Boot the Switch A snapshot can be created on internal memory after a switch is booted using files stored in external memory. To create a snapshot in internal memory and use it to boot the switch: 1. Place the snapshot files in internal memory: user@switch> request system snapshot parition media internal slice 1 NOTE: This example uses the partition option. If you have already created a partition for the snapshot, you don’t need to use the partition option. 2. (Optional) Perform this step if you want to boot the switch now using the newly created snapshot. If you created the snapshot as a backup, do not perform this step. • To reboot the switch using the most recently created snapshot: user@switch> request system reboot media internal 93 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • To reboot the switch using a snapshot in a specific partition in internal memory: user@switch> request system reboot media internal slice 1 Related Documentation • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 100 • Understanding System Snapshot on J-EX Series Switches on page 72 Upgrading Software • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 94 Upgrading Software Using Automatic Software Download on J-EX Series Switches The automatic software download feature uses the DHCP message exchange process to download and install software packages. You configure the automatic software download feature on J-EX Series switches acting as DHCP clients. You must enable automatic software download on the J-EX Series switch before the software upgrade can occur. NOTE: Upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later is a special upgrade. Automatic software update and automatic software download are supported for this special upgrade. However, after an automatic installation you must take the extra step of upgrading the loader software. See the release notes for instructions on how to upgrade the loader software. You configure a path to a software package file on the DHCP server. The server communicates the path to the software package file through DHCP server messages. If you enable automatic software download, the DHCP client J-EX Series switch compares the software package name in the DHCP server message to the name of the software package that booted the switch. If the software packages are different, the DHCP client J-EX Series switch downloads and installs the software package specified in the DHCP server message. Before you upgrade software using automatic software download, ensure that you have configured DHCP services for the switch, including configuring a path to a boot server and a boot file. See the Junos OS System Basics Configuration Guide for information about using the CLI to configure DHCP services and settings. See “Configuring DHCP Services (J-Web Procedure)” on page 463 for information about using the J-Web interface to configure DHCP services and settings. To enable automatic software download on a J-EX Series switch acting as a DHCP client: [edit chassis] user@switch# set auto-image-upgrade 94 Chapter 6: Booting the Switch, Upgrading Software, and Managing Licenses Once automatic software download is enabled on your DHCP client J-EX Series switch and once DHCP services are enabled on your network, an automatic software download can occur at any time as part of the DHCP message exchange process. If an automatic software download occurs, you see the following message on the switch: Auto-image upgrade started On successful installation system will reboot automatically The switch reboots automatically to complete the upgrade. Related Documentation • Verifying That Automatic Software Download Is Working Correctly on page 99 • Understanding Software Installation on J-EX Series Switches on page 69 • DHCP Services for J-EX Series Switches Overview on page 457 • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 95 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 96 Managing Licenses Managing Licenses for the J-EX Series Switch (CLI Procedure) To enable and use some Junos OS features on a J-EX Series switch, you must purchase, install, and manage separate software licenses. Each switch requires one license. For a Virtual Chassis deployment, two licenses are recommended for redundancy. After you have configured the features, you see a warning message if the switch does not have a license for the feature. The AFL software license is not currently available for J-EX4500 switches. Before you begin managing licenses, be sure that you have: • Obtained the needed licenses. For information about how to purchase software licenses, contact Dell. • Understand what makes up a license key. For more information, see “License Key Components for the J-EX Series Switch” on page 77. This topic includes the following tasks: • Adding New Licenses on page 95 • Deleting Licenses on page 96 • Saving License Keys on page 96 Adding New Licenses To add one or more new license keys on the switch, with the CLI: 1. Add the license key or keys: • To add one or more license keys from a file or URL, specify the filename of the file or the URL where the key is located: 95 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 user@switch> request system license add filename | url • To add a license key from the terminal: user@switch> request system license add terminal 2. When prompted, enter the license key, separating multiple license keys with a blank line. If the license key you enter is invalid, an error appears in the CLI output when you press Ctrl+d to exit the license entry mode. Deleting Licenses To delete one or more license keys from the switch with the CLI, specify the license ID: user@switch> request system license delete license-id You can delete only one license at a time. Saving License Keys To save the installed license keys to a file (which can be a URL) or to the terminal: user@switch> request system license save filename | url For example, the following command saves the installed license keys to a file named license.conf: user@switch> request system license save ftp://user@switch/license.conf Related Documentation • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 96 • Monitoring Licenses for the J-EX Series Switch on page 104 • Understanding Software Licenses J-EX Series Switches on page 76 Managing Licenses for the J-EX Series Switch (J-Web Procedure) To enable and use some Junos OS features on a J-EX Series switch, you must purchase, install, and manage separate software licenses. Each switch requires one license. For a Virtual Chassis deployment, two licenses are recommended for redundancy. After you have configured the features, you see a warning message if the switch does not have a license for the feature. The AFL software license is not currently available for J-EX4500 switches. Before you begin managing licenses, be sure that you have: 96 • Obtained the needed licenses. For information about how to purchase software licenses, contact Dell. • Understand what makes up a license key. For more information, see “License Key Components for the J-EX Series Switch” on page 77. Chapter 6: Booting the Switch, Upgrading Software, and Managing Licenses NOTE: To access the J-Web interface, your management device must have the following software installed: • Operating system: Microsoft Windows XP Service Pack 3 • Browser version: One of the following. Other browsers might work but are not supported by J-Series platforms. • • Microsoft Internet Explorer version 7.0 • Mozilla Firefox version 3.0 Additional requirements: • Only English-language browsers are supported. • The browser and the network must be able to receive and process HTTP/1.1 gzip compressed data. This topic includes the following tasks: • Adding New Licenses on page 97 • Deleting Licenses on page 97 • Displaying License Keys on page 98 • Downloading Licenses on page 98 Adding New Licenses To add one or more new license keys on the switch, with the J-Web license manager: 1. In the J-Web interface, select Maintain > Licenses. 2. Under Installed Licenses, click Add to add a new license key or keys. 3. Do one of the following, using a blank line to separate multiple license keys: • In the License File URL box, type the full URL to the destination file containing the license key or keys to be added. • In the License Key Text box, paste the license key text, in plain-text format, for the license to be added. 4. Click OK to add the license key or keys. A list of features that use the license key is displayed. The table also lists the ID, state, and version of the license key. Deleting Licenses To delete one or more license keys from a switch with the J-Web license manager: 1. In the J-Web interface, select Maintain > Licenses. 2. Select the check box of the license or licenses you want to delete. 97 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 3. Click Delete. Displaying License Keys To display the license keys installed on a switch with the J-Web license manager: 1. In the J-Web interface, select Maintain > Licenses. 2. Under Installed Licenses, click Display Keys to display all the license keys installed on the switch. A screen displaying the license keys in text format appears. Multiple licenses are separated by a blank line. Downloading Licenses To download the license keys installed on the switch with the J-Web license manager: 1. In the J-Web interface, select Maintain > Licenses. 2. Under Installed Licenses, click Download Keys to download all the license keys installed on the switch to a single file. 3. Select Save it to disk and specify the file to which the license keys are to be written. You can also download the license file to your system. Related Documentation 98 • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 95 • Monitoring Licenses for the J-EX Series Switch on page 104 • Understanding Software Licenses for J-EX Series Switches on page 76 CHAPTER 7 Verifying Software Installation • Routine Monitoring on page 99 • Monitoring Licenses on page 104 • Verifying That Automatic Software Download Is Working Correctly on page 99 • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 100 • Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch on page 100 Routine Monitoring Verifying That Automatic Software Download Is Working Correctly Purpose Action Verify that the automatic software download feature is working correctly. Use the show system services dhcp client interface-name command to verify that the automatic software download feature has been used to install a software package. user@switch> show system services dhcp client ge-0/0/1.0 Logical Interface Name ge-0/0/1.0 Hardware address 00:0a:12:00:12:12 Client Status bound Vendor Identifier ether Server Address 10.1.1.1 Address obtained 10.1.1.89 Lease Obtained at 2009-08-20 18:13:04 PST Lease Expires at 2009-08-22 18:13:04 PST DHCP Options : Name: name-server, Value: [ 10.209.194.131, 2.2.2.2, 3.3.3.3 ] Name: server-identifier, Value: 10.1.1.1 Name: router, Value: [ 10.1.1.80 ] Name: boot-image, Value: jinstall-ex-4200-10.2R1.5-domestic-signed.tgz Name: boot-image-location, Value: 10.1.1.25:/bootfiles/ Meaning The output from this command shows the name and location of the software package under DHCP options when automatic software download was last used to install a software package. The sample output in DHCP options shows that the last DHCP server message to arrive on the DHCP client had a boot server address of 192.168.1.165 and a 99 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 boot file named jinstall-ex-4200-10.2R1.5-domestic-signed.tgz. If automatic software download was enabled on this client switch during the last DHCP message exchange, these values were used by the switch to upgrade the software. Related Documentation • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 94 • DHCP Services for J-EX Series Switches Overview on page 457 Verifying That a System Snapshot Was Created on a J-EX Series Switch Purpose Action Verify that a system snapshot was created with the proper files on a J-EX Series switch. View the snapshot: user@switch> show system snapshot media external Information for snapshot on external (da1s1) Creation date: Oct 1320:23:23 2009 Junos version on snapshot: jbase : 10.0I20090726_0011_user jcrypto-ex: 10.0I20090726_0011_user jdocs-ex: 10.0I20090726_0011_user jkernel-ex: 10.0I20090726_0011_user jroute-ex: 10.0I20090726_0011_user jswitch-ex: 10.0I20090726_0011_user jweb-ex: 10.0I20090726_0011_user jpfe-ex42x: 10.0I20090726_0011_user Meaning The output shows the date and time when the snapshot was created and the packages that are part of the snapshot. The date and time match the time when you created the snapshot. You can compare the output of this command to the output of the show system software command to ensure that the snapshot contains the same packages as the software currently running the switch. Related Documentation • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 92 Verifying Junos OS and Boot Loader Software Versions on an EX Series Switch Before or after upgrading or downgrading Junos OS, you might need to verify the Junos OS version. You might also need to verify the boot loader software version if you are upgrading to or downgrading from a release that supports resilient dual-root partitions (Junos OS Release 10.4R3 and later). This topic includes: 100 • Verifying the Number of Partitions and File System Mountings on page 101 • Verifying the Loader Software Version on page 102 Chapter 7: Verifying Software Installation • Verifying Which Root Partition Is Active on page 102 • Verifying the Junos OS Version in Each Root Partition on page 103 Verifying the Number of Partitions and File System Mountings Purpose Action Between Junos OS Release 10.4R2 and Release 10.4R3, upgrades were made to further increase resiliency of root partitions, which required reformatting the disk from three partitions to four partitions. Generally, if your switch is running Release 10.4R2 or earlier, it has three partitions, and if it is running Release 10.4R3 or later, it has four partitions. Verify how many partitions the disk has, as well as where each file system is mounted, by using the following command: user@switch> show system storage fpc0: ----------------------------------------------------------------------Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 184M 124M 45M 73% / devfs 1.0K 1.0K 0B 100% /dev /dev/md0 37M 37M 0B 100% /packages/mnt/jbase /dev/md1 18M 18M 0B 100% /packages/mnt/jcrypto-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md2 6.1M 6.1M 0B 100% /packages/mnt/jdocs-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md3 154M 154M 0B 100% /packages/mnt/jkernel-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md4 23M 23M 0B 100% /packages/mnt/jpfe-ex42x-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md5 46M 46M 0B 100% /packages/mnt/jroute-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md6 28M 28M 0B 100% /packages/mnt/jswitch-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md7 22M 22M 0B 100% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081 /dev/md8 126M 10.0K 116M 0% /tmp /dev/da0s3e /dev/da0s3d /dev/da0s4d 123M 369M 62M 632K 20K 62K 112M 1% /var 339M 0% /var/tmp 57M 0% /config /dev/md9 118M 12M 96M 11% /var/rundb procfs 4.0K 4.0K 0B 100% /proc /var/jail/etc 123M 632K 112M 1% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/etc /var/jail/run 123M 632K 112M 1% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/run /var/jail/tmp 123M 632K 112M 1% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/tmp /var/tmp 369M 20K 339M 0% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/var/tmp/uploads devfs 1.0K 1.0K 0B 100% /packages/mnt/jweb-ex-10.4I20110121_0509_hbRPSRLI15184421081/jail/dev Meaning The presence of the partition name containing s4d indicates the fourth slice. If this were a three-slice partition scheme, in place of s1a, s3e, s3d, and s4d, you would see s1a, s1f, s2a, s2f, s3d, and s3e and you would not see s4d. 101 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Verifying the Loader Software Version Purpose Action For the special case of upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later, you must upgrade the loader software. For J-EX switches, except J-EX8200 switches: user@switch> show chassis firmware Part Type FPC 0 uboot loader Version U-Boot 1.1.6 (Jan 3 2011 - 16:14:58) 1.0.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.4 For J-EX8200 switches: user@switch> show chassis firmware Part Type FPC 0 uboot loader Meaning Version U-Boot 1.1.6 (Jan 3 2011 - 16:14:58) 3.5.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.4 For J-EX switches other than J-EX8200 switches, if there is version information following the timestamp for U-Boot (1.0.0 in the example above), then the loader software does not require upgrading. If there is no version information following the timestamp for U-boot, then the loader software requires upgrading. For J-EX8200 switches, the version number following the timestamp for U-Boot that is lower than 3.5.0. Verifying Which Root Partition Is Active Purpose Switches running Release 10.4R3 or later have resilient dual-root partition functionality, which includes the ability to boot transparently from the inactive partition if the system fails to boot from the primary root partition. You can verify which root partition is active using the following command: Action user@switch> show system storage partitions fpc0: -------------------------------------------------------------------------Boot Media: internal (da0) Active Partition: da0s1a Backup Partition: da0s2a Currently booted from: active (da0s1a) Partitions information: Partition Size Mountpoint s1a 184M / s2a 184M altroot s3d 369M /var/tmp s3e 123M /var s4d 62M /config s4e unused (backup config) 102 Chapter 7: Verifying Software Installation Verifying the Junos OS Version in Each Root Partition Purpose Action Each switch contains two root partitions. We recommend that you copy the same Junos OS version in each partition when you upgrade. In Junos OS Release 10.4R2 and earlier, you might choose to have different Junos OS release versions in each partition. You might have different versions during a software upgrade and before you have finished verifying the new software installation. To enable a smooth reboot if corruption is found in the primary root file system, ensure that the identical Junos OS images are in each root partition. For Release 10.4R2 and earlier, you must manually reboot the switch from the backup root partition. However, for Release 10.4R3 and later, the switch reboots automatically from the backup root partition if it fails to reboot from the active partition. Verify whether both root partitions contain the same image by using the following commands: user@switch> show system snapshot media internal slice 1 Information for snapshot on internal (da0s1) Creation date: Jan 21 05:48:34 2011 JUNOS version on snapshot: jbase : 10.4I20110121_0509_hbRPSRLI15184421081 jcrypto-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jdocs-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jkernel-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jroute-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jswitch-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jweb-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jpfe-ex42x: 10.4I20110121_0509_hbRPSRLI15184421081 user@switch# run show system snapshot media internal slice 2 Information for snapshot on internal (da0s2) Creation date: Jan 21 05:47:54 2011 JUNOS version on snapshot: jbase : 10.4I20110121_0509_hbRPSRLI15184421081 jcrypto-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jdocs-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jkernel-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jroute-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jswitch-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jweb-ex: 10.4I20110121_0509_hbRPSRLI15184421081 jpfe-ex42x: 10.4I20110121_0509_hbRPSRLI15184421081 Related Documentation • Upgrading J-EX Series Switches to Support Resilient Dual-Root Partitions • Verifying Junos OS and Boot Loader Software Versions on a J-EX Series Switch on page 100 • Troubleshooting Software Installation on page 107 • Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on page 110 • Understanding Resilient Dual-Root Partitions on Switches on page 74 • Resilient Dual-Root Partitions Frequently Asked Questions on page 111 • show system storage partitions (J-EX Series Switches Only) on page 146 103 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Monitoring Licenses • Monitoring Licenses for the J-EX Series Switch on page 104 Monitoring Licenses for the J-EX Series Switch To enable and use some Junos OS features on the J-EX Series switch, you must purchase, install, and manage the appropriate software licenses. Each switch requires one license. For a Virtual Chassis deployment, two licenses are recommended for redundancy. To monitor your installed licenses, perform the following tasks: • Displaying Installed Licenses and License Usage Details on page 104 • Displaying Installed License Keys on page 105 Displaying Installed Licenses and License Usage Details Purpose Verify that the expected license is installed and active on the switch and fully covers the switch configuration. Action From the CLI, enter the show system license command. (To display only the License usage list, enter the show system license usage command. To display only the Licenses installed output, enter show system license installed.) user@switch> show system license License usage: Licenses Licenses Licenses used installed needed bgp 1 1 0 permanent isis 0 1 0 permanent ospf3 0 1 0 permanent ripng 0 1 0 permanent mpls 0 1 0 permanent Feature name Licenses installed: License identifier: JUNOS204558 License version: 2 Valid for device: BN0208380000 Features: 104 Expiry Chapter 7: Verifying Software Installation ex—series - Licensed routing protocols in ex-series permanent Meaning The output shows the license or licenses (for Virtual Chassis deployments) installed on the switch and license usage. Verify the following information: • If a feature that requires a license is configured (used), a license is installed on the switch. The Licenses needed column must show that no licenses are required. • The appropriate number of licenses is installed. Each switch requires one license. For a Virtual Chassis deployment, two licenses are recommended for redundancy. • The expected license is installed. Displaying Installed License Keys Purpose Action Verify that the expected license keys are installed on the switch. From the CLI, enter the show system license keys command. user@switch> show system license keys JUNOS204558 aeaqea qmijhd amrqha ztfmbu gqzama uqceds ra32zr lsevik ftvjed o4jy5u fynzzj mgviyl kgioyf ardb5g sj7wnf rsdked wbjf5a sg Meaning Related Documentation The output shows the license key or keys (for Virtual Chassis deployments) installed on the switch. Verify that each expected license key is present. • Managing Licenses for the J-EX Series Switch (CLI Procedure) on page 95 • Managing Licenses for the J-EX Series Switch (J-Web Procedure) on page 96 • Understanding Software Licenses for J-EX Series Switches on page 76 105 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 106 CHAPTER 8 Troubleshooting Software Installation • Troubleshooting Software Installation on page 107 • Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on page 110 • Resilient Dual-Root Partitions Frequently Asked Questions on page 111 Troubleshooting Software Installation • Recovering from a Failed Software Upgrade on a J-EX Series Switch on page 107 • Rebooting from the Inactive Partition on page 108 • Freeing Disk Space for Software Installation on page 109 • Installation from the Boot Loader Generates ’cannot open package’ Error on page 109 Recovering from a Failed Software Upgrade on a J-EX Series Switch Problem If Junos OS loads but the CLI is not working for any reason, or if the switch has no software installed, you can use this recovery installation procedure to install Junos OS. Solution If there is already a Junos OS image on the system, you can either install the new Junos OS package in a separate partition and have both Junos OS images remain on the system, or you can wipe the disk clean before the new installation proceeds. If there is no Junos OS image on the system, follow the instructions in “Booting a J-EX Series Switch Using a Software Package Stored on a USB Flash Drive” on page 91 to get an image on the system and boot the switch. To perform a recovery installation: 1. Power on the switch. The loader script starts. After the message Loading /boot/defaults/loader.conf appears, you are prompted with: Hit [Enter] to boot immediately, or space bar for command prompt. 2. Press the space bar to enter the manual loader. The loader> prompt appears. 3. Enter the following command: loader> install [– –format] [– –external] source 107 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 where: • format—Use this option to wipe the installation media before installing the software package. If you do not include this option, the system installs the new Junos OS package in a different partition from the partition used by the most recently installed Junos OS package. • external—Use this option to install the software package on an external medium. • source—Represents the name and location of the Junos OS package either on a server on the network or as a file on the USB flash drive: • Network address of the server and the path on the server; for example, tftp://192.17.1.28/junos/jinstall-ex-4200-10.2R1.5-domestic-signed.tgz • The Junos OS package on a USB device is commonly stored in the root drive as the only file; for example, file:///jinstall-ex-4200-10.2R1.5-domestic-signed.tgz The boot process proceeds normally and ends with a login prompt. Rebooting from the Inactive Partition Problem J-EX Series switches shipped with Junos OS Release 10.4R2 or earlier have Junos OS loaded on the system disk in partition 1. The first time you upgrade, the new software package is installed in partition 2. When you finish the installation and reboot, partition 2 becomes the active partition. Similarly, subsequent software packages are installed in the inactive partition, which becomes the active partition when you reboot at the end of the installation process. On switches shipped with Release 10.4R3 and later, the same Junos OS image is loaded in each of the two root partitions, and you should copy the new software image to the alternate partition each time you upgrade. If you performed an upgrade and rebooted, the system resets the active partition. You can use this procedure to manually boot from the inactive partition. NOTE: If you have completed the installation of the software image but have not yet rebooted, you can issue the request system software rollback command to return to the original software installation package. Solution Reboot from the inactive partition: user@switch> request system reboot partition alternate 108 Chapter 8: Troubleshooting Software Installation NOTE: If you cannot access the CLI, you can reboot from the inactive partition using the following procedure from the loader script prompt: 1. Unload and clear the interrupted boot from the active partition: loader> unload loader> unset vfs.root.mountfrom 2. Select the new (inactive) partition to boot from: loader> set currdev=disk[0|1]s[1|2]: where the first value is either 0 (internal) or 1 (external) and the second value indicates the number of the inactive partition, either 1 or 2. You must include the colon (:) at the end of this command. 3. Boot Junos OS from the inactive partition: loader> boot Freeing Disk Space for Software Installation Problem The software installation process requires a certain amount of unused disk space. If there is not enough space, you might receive an error message such as: fetch: /var/tmp/incoming-package.tgz: No space left on device Solution Identify and delete unnecessary files by using the request system storage cleanup command. Installation from the Boot Loader Generates ’cannot open package’ Error Problem When you are installing a Junos OS software image from the loader prompt, a “cannot open package error” is generated: loader> install - -format tftp://10.204.33.248/images/Flash_corr/official/jinstall-ex-4200-10.4I2011012-domestic-signed.tgz Speed: 1000, full duplex bootp: no reply No response for RARP request net_open: RARP failed cannot open package (error 5) Solution This problem might result from the IP address, gateway IP address, netmask address, or server IP address not being properly set. You can set these values either from the shell or from the u-boot prompt. To set these values from the shell: % % % % nvram setenv ipaddr 10.204.35.235 nvram setenv netmask 255.255.240.0 nvram setenv gatewayip 10.204.47.254 nvram setenv serverip 10.204.33.248 To set these values from the u-boot prompt, log in to a console connection, reboot, and stop at the u-boot prompt (Cntrl-C): 109 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 => setenv ipaddr 10.204.35.235 => setenv gatewayip 10.204.47.254 => setenv serverip 10.204.33.248 => setenv netmask 255.255.240.0 => saveenv => printenv Verify whether variables are set properly or not => boot Related Documentation • Upgrading EX Series Switches to Support Resilient Dual-Root Partitions • Installing Software on a J-EX Series Switch with a Single Routing Engine (CLI Procedure) on page 80 • Upgrading Software Using Nonstop Software Upgrade (CLI Procedure) on page 955 • Installing Software on J-EX Series Switches (J-Web Procedure) on page 86 • Understanding Software Installation on J-EX Series Switches on page 69 • show system storage partitions (J-EX Series Switches Only) on page 146 Troubleshooting a Switch That Has Booted from the Backup Junos OS Image Problem The switch boots from the backup root file partition. This event is flagged in two ways: • Upon login through the console or management port, the following warning message is displayed: WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE It is possible that the primary copy of JUNOS failed to boot up properly, and so this device has booted from the backup copy. Please re-install JUNOS to recover the primary copy in case it has been corrupted. • The following alarm message is generated: user@switch> show chassis alarms 1 alarms currently active Alarm time Class 2011-02-17 05:48:49 PST Minor Solution Description Host 0 Boot from backup root Install a new Junos OS image on the partition that had the corruption, or take a snapshot of the currently active partition and use it to replace the image in the backup partition: user@switch# request system snapshot media internal slice alternate Copying '/dev/da0s2a' to '/dev/da0s1a' .. (this may take a few minutes) The following filesystems were archived: / Related Documentation 110 • Verifying Junos OS and Boot Loader Software Versions on a J-EX Series Switch on page 100 • Troubleshooting Software Installation on page 107 • show system storage partitions (J-EX Series Switches Only) on page 146 Chapter 8: Troubleshooting Software Installation Resilient Dual-Root Partitions Frequently Asked Questions This FAQ addresses questions regarding resilient dual-root partitions on J-EX Series switches and upgrading to resilient dual-root partition releases. This feature was introduced on J-EX Series switches at Junos OS Release 10.4R3. It provides additional resiliency for J-EX Series switches. This FAQ covers the following questions: • How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from Normal Upgrades? on page 111 • What Happens If I Do Not Upgrade Both the Loader Software and Junos OS at the Same Time? on page 111 • Can I Downgrade Junos OS Without Downgrading the Loader Software? on page 112 • Can I Upgrade to a Resilient Dual-Root Partition Release by Using the CLI? on page 113 • Will I Lose My Configuration During an Upgrade? on page 113 • How Long Will the Upgrade Process Take? on page 113 • What Happens to My Files If the System Detects a File System Corruption? on page 113 • How Will I Be Informed If My Switch Boots from the Alternate Slice Due to Corruption in the Root File System? on page 114 • Can I Use Automatic Software Update and Download to Upgrade to a Resilient Dual-Root Partition Release? on page 114 • Why Is the Message "At least one package installed on this device has limited support" Displayed When Users Log In to the Switch? on page 114 How Does Upgrading to Junos OS Release 10.4R3 and Later Differ from Normal Upgrades? Upgrading from Junos OS Release 10.4R2 or earlier to Release 10.4R3 or later differs from other upgrades in these ways: • You must upgrade the loader software in addition to installing the new Junos OS image. • Rebooting after the upgrade reformats the disk from three partitions to four partitions. • The upgrade process and the reboot take longer due to the additional time required to upgrade the loader software and additional time for the first reboot after the Junos OS installation (longer than normal because it reformats the disk from three partitions to four). Also, J-EX8200 switches require an additional reboot per Routing Engine as part of the loader software upgrade. What Happens If I Do Not Upgrade Both the Loader Software and Junos OS at the Same Time? You must install a new loader software package if you are upgrading to a release that supports resilient dual-root partitions (Release 10.4R3 and later) from an earlier release (Release 10.4R2 and earlier). Table 30 on page 112 describes the combinations of Junos OS and loader software versions. 111 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 30: Combinations of Junos OS Versions and Loader Software Versions Junos OS Release Loader Software Notes Release 10.4R3 and later New loader software Recommended For all J-EX Series switches except EX8200 switches: U-Boot 1.1.6 (Mar 11 2011 - 04:39:06) 1.0.0 (Contains version 1.0.0 after the timestamp.) For J-EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 3.5.0 (Contains version 3.5.0.) Release 10.4R2 and earlier Old loader software Recommended For all J-EX Series switches except EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) (Does not contain a version number after the timestamp.) For J-EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 2.3.0 (Contains a version earlier than 3.5.0.) Release 10.4R3 and later Old loader software For all J-EX Series switches except EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) The switch will come up and function normally. However, if the switch cannot boot from the active root partition, it cannot transparently boot up from the alternate root partition. (Does not contain a version number after the timestamp.) For J-EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 2.3.0 (Contains a version earlier than 3.5.0.) Release 10.4R2 and earlier New loader software For all J-EX Series switches except EX8200 switches: U-Boot 1.1.6 (Mar 11 2011 - 04:39:06) 1.0.0 (Contains version 1.0.0 after the timestamp.) For J-EX8200 switches: U-Boot 1.1.6 (Jan 11 2008 - 05:24:35) 3.5.0 The switch will come up and function normally. However, on each reboot the switch boots from the alternate root partition. This might cause your switch to unexpectedly boot with a previous Junos OS version (if a different version is installed in the alternate partition). See “Can I Downgrade Junos OS Without Downgrading the Loader Software?” on page 112. (Contains version 3.5.0.) Can I Downgrade Junos OS Without Downgrading the Loader Software? To downgrade to Release 10.4R2 or earlier without downgrading the loader software, you must disable the boot-sequencing function. Because earlier Junos OS releases do not contain the newer settings, the switch will boot on each subsequent reboot from the alternate root partition rather than from the active partition. If you disable the boot-sequencing function, you can run Release 10.4R2 or earlier with the new loader software and have no adverse effects. 112 Chapter 8: Troubleshooting Software Installation Disable the boot-sequencing function in one of two ways: • From the shell as user root: % nvram setenv boot.btsq.disable 1 • From a console connection, reboot and stop at the u-boot prompt (Ctrl-C): => setenv boot.btsq.disable 1 => savenv Can I Upgrade to a Resilient Dual-Root Partition Release by Using the CLI? Yes, you can perform the entire upgrade to resilient dual-root partitions from the CLI. You download both the new loader software and Junos OS packages and install them from the CLI. During the final reboot, the disk is automatically reformatted from three partitions to four partitions. Will I Lose My Configuration During an Upgrade? Configuration files are preserved and restored during the reformatting of the disk. We recommend that you save your configuration before upgrading because if there is a power interruption during the installation process, files might be lost. How Long Will the Upgrade Process Take? The process of upgrading to a resilient dual-root partitions release takes longer than other upgrades due to the additional step of upgrading the loader software and a longer reboot time while the disk is reformatted to four partitions during the reboot of the switch that completes the Junos OS upgrade. The reformat increases the reboot time for J-EX4200, and J-EX4500 switches by 5 to 10 minutes. For J-EX8200 switches, the reboot time increases by 10 to 25 minutes per Routing Engine, and additional reboots are required. What Happens to My Files If the System Detects a File System Corruption? During a reboot, the system checks each file system partition for corruption. Table 31 on page 113 shows the action the system takes if corruption is detected and the corrective action that you can take. Table 31: Actions If Corrupt Files Are Found Slice 1 Slice 2 Slice 3 s1a s2a s3e s3d s4d / / /var /var/tmp /config (root Junos OS) (root Junos OS) If a root directory (/) is corrupted, the corrupted file system is not mounted and the switch boots from the alternate slice. Slice 4 During early boot, the integrity of /var, /var/tmp, and /config files are verified. If they are corrupted, the corrupted slice is reformatted and the file directory in that slice is lost. 113 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 31: Actions If Corrupt Files Are Found (continued) Slice 1 Slice 2 Slice 3 s1a s2a s3e Corrective action: Issue a request system snapshot command from the good root directory to the corrupted slice. Slice 4 s3d s4d Corrective action: Restore the /var or /config files from the external backup. How Will I Be Informed If My Switch Boots from the Alternate Slice Due to Corruption in the Root File System? If the switch detects corruption in the primary root file system, it boots from the alternate root partition. When this occurs, you are notified in two ways: • If you are logged in through the console port or the management port: WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE It is possible that the primary copy of JUNOS failed to boot up properly, and so this device has booted from the backup copy. Please re-install JUNOS to recover the primary copy in case it has been corrupted. • The following alarm message is generated: user@switch> show chassis alarms 1 alarms currently active Alarm time Class 2011-02-17 05:48:49 PST Minor Description Host 0 Boot from backup root Can I Use Automatic Software Update and Download to Upgrade to a Resilient Dual-Root Partition Release? Automatic software update and automatic software download are both supported with upgrading to resilient dual-root partition releases. However, after an automatic installation, you must take the extra step of upgrading the loader software. Automatic software update is for new members added to a Virtual Chassis that do not have the same software as the master. Once this feature is configured on the Virtual Chassis, any new member added with a different software version will be upgraded automatically. Automatic software download uses the DHCP message exchange process to download and install software packages. Why Is the Message "At least one package installed on this device has limited support" Displayed When Users Log In to the Switch? The following message might be displayed when you log in to a J-EX8200 switch: 114 Chapter 8: Troubleshooting Software Installation Logging to master ..Password: --- JUNOS 10.4R3.4 built 2011-03-19 22:06:32 UTC At least one package installed on this device has limited support. Run 'file show /etc/notices/unsupported.txt' for details. This message can be safely ignored or you can permanently remove it. It appears because of the jloader package file detected on system, and only appears when the Junos OS software is installed before upgrading the loader software. You can permanently remove this message by removing the jloader package and rebooting the system: request system software delete jloader-ex-8200 request system reboot Related Documentation • Upgrading J-EX Series Switches to Support Resilient Dual-Root Partitions • Verifying Junos OS and Boot Loader Software Versions on a J-EX Series Switch on page 100 • Troubleshooting Software Installation on page 107 • Troubleshooting a Switch That Has Booted from the Backup Junos OS Image on page 110 • Verifying Junos OS and Boot Loader Software Versions on a J-EX Series Switch on page 100 115 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 116 CHAPTER 9 Configuration Statements for Software Installation • [edit chassis] Configuration Statement Hierarchy on page 117 [edit chassis] Configuration Statement Hierarchy chassis { aggregated-devices { ethernet { device-count number; } } auto-image-upgrade; fpc slot { pic pic-number { sfpplus { pic-modemode; } } power-budget-priority priority; } lcd-menu fpc slot-number { menu-item (menu-name | menu-option); } nssu { upgrade-group group-name { fpcs (slot-number | [list-of-slot-numbers]); member member-id { fpcs (slot-number | [list-of-slot-numbers]); } } } psu { redundancy { n-plus-n; } } redundancy { graceful-switchover; } } 117 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • Configuring Aggregated Ethernet Interfaces (CLI Procedure) on page 1081 • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 94 • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • Configuring Graceful Routing Engine Switchover in a J-EX4200 or J-EX4500 Virtual Chassis (CLI Procedure) on page 856 • Configuring Power Supply Redundancy (CLI Procedure) on page 952 • Configuring the Power Priority of Line Cards (CLI Procedure) on page 953 • Configuring Line-card Upgrade Groups for Nonstop Software Upgrade (CLI Procedure) on page 951 auto-image-upgrade Syntax Hierarchy Level Release Information Description auto-image-upgrade; [edit chassis] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable automatic software download on a J-EX Series switch acting as a DHCP client. The DHCP client J-EX Series switch compares the software package name in the DHCP server message to the name of the software package that booted the switch. If the software packages are different, the DHCP client J-EX Series switch downloads and installs the software package specified in the DHCP server message. Before you upgrade software using automatic software download, ensure that you have configured DHCP services for the switch, including configuring a path to a boot server and a boot file. See the Junos OS System Basics Configuration Guide for information about using the CLI to configure DHCP services and settings. See “Configuring DHCP Services (J-Web Procedure)” on page 463 for information about using the J-Web interface to configure DHCP services and settings. Default Required Privilege Level Related Documentation 118 Automatic software download is disabled. interface—To view this statement in the configuration. interface-control—To add this statement to the configuration. • Upgrading Software Using Automatic Software Download on J-EX Series Switches on page 94 • Understanding Software Installation on J-EX Series Switches on page 69 • DHCP Services for J-EX Series Switches Overview on page 457 CHAPTER 10 Operational Commands for Software Installation 119 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request system license add Syntax Release Information Description Options request system license add (filename | terminal) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Add a license key. filename—License key from a file or URL. Specify the filename or the URL where the key is located. terminal—License key from the terminal. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • Adding New Licenses request system license add on page 120 When you enter this command, you are provided feedback on the status of your request. Sample Output request system license add 120 user@host> request system license add terminal Chapter 10: Operational Commands for Software Installation request system license delete Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields request system license delete license-id Command introduced before Junos OS Release 10.2 for J-EX Series switches. Delete a license key. You can delete only one license at a time. license-id—License ID that uniquely identifies a license key. maintenance • Deleting a License request system license delete on page 121 When you enter this command, you are provided feedback on the status of your request. Sample Output request system license delete user@host> request system license delete G03000002223 121 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request system license save Syntax Release Information Description Options request system license save (filename | terminal) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Save installed license keys to a file or URL. filename—License key from a file or URL. Specify the filename or the URL where the key is located. terminal—License key from the terminal. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • Saving License Keys request system license save on page 122 When you enter this command, you are provided feedback on the status of your request. Sample Output request system license save 122 user@host> request system license save ftp://user@host/license.conf Chapter 10: Operational Commands for Software Installation request system reboot Syntax Release Information Description request system reboot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reboot the Junos OS. Reboot requests are recorded in the system log files, which you can view with the show log command. You can view the process names with the show system processes command. Options none—Reboots the software immediately. all-members | local | member member-id—(J-EX4200 switch only) (Optional) Specify which member of the Virtual Chassis to reboot: • all-members—Reboots each switch that is a member of the Virtual Chassis. • local—Reboots the local switch, meaning the switch you are logged into, only. • member member-id—Reboots the specified member switch of the Virtual Chassis. at time—(Optional) Time at which to reboot the software, specified in one of the following ways: • +minutes—Number of minutes from now to reboot the software. • hh:mm—Absolute time on the current day at which to reboot the software, specified in 24-hour time. • now—Stop or reboot the software immediately. This is the default. • yymmddhhmm—Absolute time at which to reboot the software, specified as year, month, day, hour, and minute. in minutes—(Optional) Number of minutes from now to reboot the software. This option is an alias for the at +minutes option. media (external | internal)—(Optional) Boot medium for the next boot. The external option reboots the switch using a software package stored on an external boot source, such as a USB flash drive. The internal option reboots the switch using a software package stored in an internal memory source. message “text”—(Optional) Message to display to all system users before rebooting the software. 123 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 other-routing-engine—(Optional) Reboot the other Routing Engine from which the command is issued. For example, if you issue the command from the master Routing Engine, the backup Routing Engine is rebooted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is rebooted. slice (1 | 2 | alternate)—(Optional) Reboot using the specified partition on the boot media. This option has the following suboptions: • 1—Reboot from partition 1. • 2—Reboot from partition 2. • alternate—Reboot from the alternate partition, which is the partition that did not boot the switch at the last bootup. Required Privilege Level Related Documentation Output Fields maintenance • clear system reboot on page 230 • request system halt on page 239 When you enter this command, you are provided feedback on the status of your request. Sample Output request system reboot user@host> request system reboot Reboot the system ? [yes,no] (no) request system reboot (at 2300) user@host> request system reboot at 2300 message ?Maintenance time!? Reboot the system ? [yes,no] (no) yes shutdown: [pid 186] *** System shutdown message from root@berry.network.net *** System going down at 23:00 request system reboot (in 2 Hours) The following example, which assumes that the time is 5 PM (17:00), illustrates three different ways to request the system to reboot in two hours: user@host> request system reboot at +120 user@host> request system reboot in 120 user@host> request system reboot at 19:00 request system reboot (Immediately) user@host> request system reboot at now request system reboot (at 1:20 AM) To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM is the next day, you must specify the absolute time. user@host> request system reboot at 06060120 request system reboot at 120 Reboot the system at 120? [yes,no] (no) yes 124 Chapter 10: Operational Commands for Software Installation request system snapshot Syntax Release Information Description Options request system snapshot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Take a snapshot of the files currently used to run the switch—the complete contents of the /config and /var directories, which include the running Juniper Networks Junos OS, the active configuration, and the rescue configuration—and copy all of these files into an alternate (internal, meaning internal flash, or an external, meaning USB flash) memory source. none—Create a snapshot on the alternate media, meaning the external media if you booted the switch using software stored on internal media or internal media if you booted the switch using software stored on external media. all-members | local | member member-id—(J-EX4200 switch only) (Optional) Specify where to place the snapshot in Virtual Chassis configurations: • all-members—Create a snapshot for each switch that is a member of the Virtual Chassis. • local—Create a snapshot on the local switch only. • member member-id—Create a snapshot for the specified member or member switches of the Virtual Chassis. as-primary—(Optional) Create a bootable snapshot. NOTE: The snapshot is always bootable on J-EX Series switches. The as-primary option has no effect on snapshots on J-EX Series switches. media (external | internal)—(Optional) Specify the destination media location for the snapshot. The external option copies the snapshot to an external mass storage device, such as a USB flash drive. The internal option copies the snapshot to an internal memory source, such as internal flash memory. partition—(Optional) Partition the destination media before copying over the snapshot. re0 | re1 | routing-engine routing-engine-id—(J-EX8200 switch only) Specify where to place the snapshot in dual Routing Engine configurations. • re0—Create a snapshot on Routing Engine 0. • re1—Create a snapshot on Routing Engine 1. 125 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • routing-enginerouting-engine-id—Create a snapshot on the specified Routing Engine. slice ( 1 | 2 | alternate)—(Optional) Specify the destination partition for the snapshot: • 1—Copy the snapshot to partition 1. • 2—Copy the snapshot to partition 2. • alternate—Copy the snapshot to the alternate partition, which is the partition that did not boot the switch at the last bootup. Required Privilege Level Related Documentation Output Fields view • show system snapshot on page 144 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 92 When you enter this command, you are provided feedback on the status of your request. Sample Output request system snapshot media external slice 1 126 user@switch> request system snapshot media external slice 1 Chapter 10: Operational Commands for Software Installation request system software add Syntax request system software add package-name Syntax (J-EX Series Switches) request system software add package-name Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. The set [package-name package-name] option added in Junos OS Release 11.1 for J-EX Series switches. Install a software package or bundle on the router or switch. package-name—Location from which the software package or bundle is to be installed. For example: • /var/tmp/package-name—For a software package or bundle that is being installed from a local directory on the router or switch. • protocol://hostname/pathname/package-name—For a software package or bundle that is to be downloaded and installed from a remote location. Replace protocol with one of the following: • ftp—File Transfer Protocol. Use ftp://hostname/pathname/package-name. To specify authentication credentials, use ftp:// : @hostname/pathname/package-name. To have the system prompt you for the password, specify prompt in place of the password. If a password is required, and you do not specify the password or prompt, an error message is displayed. • http—Hypertext Transfer Protocol. Use http://hostname/pathname/package-name. To specify authentication credentials, use 127 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 http:// : @hostname/pathname/package-name. If a password is required and you omit it, you are prompted for it. • scp—Secure copy (available only for Canada and U.S. version). Use scp://hostname/pathname/package-name. To specify authentication credentials, use scp:// : @hostname/pathname/package-name. NOTE: • The pathname in the protocol is the relative path to the user’s home directory on the remote system and not the root directory. • Do not use the scp protocol in the request system software add command to download and install a software package or bundle from a remote location. The software upgrade is handled by the MGD process which does not support scp. Use the file copy command to copy the software package or bundle from the remote location to the /var/tmp directory on the hard disk: file copy scp://source/package-name /var/tmp Then install the software package or bundle using the request system software add command: request system software add /var/tmp/package-name best-effort-load—(Optional) Activate a partial load and treat parsing errors as warnings instead of errors. delay-restart—(Optional) Install software package or bundle, but do not restart software processes. force—(Optional) Force the addition of the software package or bundle (ignore warnings). no-copy—(Optional) Install a software package or bundle, but do not save copies of package or bundle files. no-validate—(Optional) When loading a software package or bundle with a different release, suppress the default behavior of the validate option. re0 | re1—(Optional) On routers that support dual or redundant Routing Engines, load a software package or bundle on the Routing Engine in slot 0 (re0) or Routing Engine in slot 1 (re1). reboot—(Optional) After adding the software package or bundle, reboot the system. set [package-name package-name]—(Mixed J-EX4200 and J-EX4500 Virtual Chassis only) (Optional) Install two software packages-a package for a J-EX4200 switch and the same release of the package for a J-EX4500 switch-to upgrade all member switches in a mixed J-EX4200 and J-EX4500 Virtual Chassis. 128 Chapter 10: Operational Commands for Software Installation validate—(Optional) Validate the software package or bundle against the current configuration as a prerequisite to adding the software package or bundle. This is the default behavior when the software package or bundle being added is a different release. Additional Information Before upgrading the software on the router or switch, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /altroot and /altconfig file systems. After you have upgraded the software on the router or switch and are satisfied that the new package or bundle is successfully installed and running, issue the request system snapshot command again to back up the new software to the /altroot and /altconfig file systems. After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical. If you are upgrading more than one package at the same time, delete the operating system package, jkernel, last. Add the operating system package, jkernel, first and the routing software package, jroute, last. If you are upgrading all packages at once, delete and add them in the following order: user@host> request system software add /var/tmp/jbase user@host> request system software add /var/tmp/jkernel user@host> request system software add /var/tmp/jpfe user@host> request system software add /var/tmp/jdocs user@host> request system software add /var/tmp/jroute user@host> request system software add /var/tmp/jcrypto Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • request system software delete on page 131 • request system software rollback on page 133 • request system storage cleanup on page 251 • Upgrading Software request system software add validate on page 129 request system software add (Mixed J-EX4200 and J-EX4500 Virtual Chassis) on page 130 When you enter this command, you are provided feedback on the status of your request. Sample Output request system software add validate user@host> request system software add validate /var/tmp/ jinstall-7.2R1.7-domestic-signed.tgz Checking compatibility with configuration Initializing... Using jbase-7.1R2.2 Using /var/tmp/jinstall-7.2R1.7-domestic-signed.tgz Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0 Using /var/validate/tmp/jinstall-signed/jinstall-7.2R1.7-domestic.tgz 129 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Using /var/validate/tmp/jinstall/jbundle-7.2R1.7-domestic.tgz Checking jbundle requirements on / Using /var/validate/tmp/jbundle/jbase-7.2R1.7.tgz Using /var/validate/tmp/jbundle/jkernel-7.2R1.7.tgz Using /var/validate/tmp/jbundle/jcrypto-7.2R1.7.tgz Using /var/validate/tmp/jbundle/jpfe-7.2R1.7.tgz Using /var/validate/tmp/jbundle/jdocs-7.2R1.7.tgz Using /var/validate/tmp/jbundle/jroute-7.2R1.7.tgz Validating against /config/juniper.conf.gz mgd: commit complete Validation succeeded Validating against /config/rescue.conf.gz mgd: commit complete Validation succeeded Installing package '/var/tmp/jinstall-7.2R1.7-domestic-signed.tgz' ... Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0 Adding jinstall... WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: This package will load JUNOS 7.2R1.7 software. It will save JUNOS configuration files, and SSH keys (if configured), but erase all other files and information stored on this machine. It will attempt to preserve dumps and log files, but this can not be guaranteed. This is the pre-installation stage and all the software is loaded when you reboot the system. Saving the config files ... Installing the bootstrap installer ... WARNING: WARNING: WARNING: WARNING: WARNING: A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the 'request system reboot' command when software installation is complete. To abort the installation, do not reboot your system, instead use the 'request system software delete jinstall' command as soon as this operation completes. Saving package file in /var/sw/pkg/jinstall-7.2R1.7-domestic-signed.tgz ... Saving state for rollback ... Sample Output request system software add (Mixed J-EX4200 and J-EX4500 Virtual Chassis) 130 user@switch> request system software add set [/var/tmp/jinstall-ex4200-11.1R2.1-domestic-signed.tgz /var/tmp/jinstall-ex-4500-11.1R2.1-domestic-signed.tgz] ... Chapter 10: Operational Commands for Software Installation request system software delete Syntax Release Information Description request system software delete software-package Command introduced before Junos OS Release 10.2 for J-EX Series switches. Remove a software package or bundle from the router or switch. CAUTION: Before removing a software package or bundle, make sure that you have already placed the new software package or bundle that you intend to load onto the router or switch. Options software-package—Software package or bundle name. You can delete any or all of the following software bundles or packages: • jbase—(Optional) Junos base software suite • jcrypto—(Optional, in domestic version only) Junos security software • jdocs—(Optional) Junos online documentation file • jkernel—(Optional) Junos kernel software suite • jpfe—(Optional) Junos Packet Forwarding Engine support • jroute—(Optional) Junos routing software suite • junos—(Optional) Junos base software force—(Optional) Ignore warnings and force removal of the software. Additional Information Required Privilege Level Related Documentation List of Sample Output Before upgrading the software on the router or switch, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /altroot and /altconfig file systems. After you have upgraded the software on the router or switch and are satisfied that the new packages are successfully installed and running, issue the request system snapshot command again to back up the new software to the /altroot and /altconfig file systems. After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical. maintenance • request system software add on page 127 • request system software rollback on page 133 • request system software validate on page 135 request system software delete jdocs on page 132 131 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Output Fields When you enter this command, you are provided feedback on the status of your request. Sample Output request system software delete jdocs The following example displays the system software packages before and after the jdocs package is deleted through the request system software delete command: user@host> show system software Information for jbase: Comment: JUNOS Base OS Software Suite [7.2R1.7] Information for jcrypto: Comment: JUNOS Crypto Software Suite [7.2R1.7] Information for jdocs: Comment: JUNOS Online Documentation [7.2R1.7] Information for jkernel: Comment: JUNOS Kernel Software Suite [7.2R1.7] ... user@host> request system software delete jdocs Removing package 'jdocs' ... user@host> show system software Information for jbase: Comment: JUNOS Base OS Software Suite [7.2R1.7] Information for jcrypto: Comment: JUNOS Crypto Software Suite [7.2R1.7] Information for jkernel: Comment: JUNOS Kernel Software Suite [7.2R1.7] ... 132 Chapter 10: Operational Commands for Software Installation request system software rollback Syntax request system software rollback Syntax (J-EX Series Switch) request system software rollback Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Revert to the software that was loaded at the last successful request system software add command. none—Revert to the set of software as of the last successful request system software add. all-members—(J-EX4200 switches only) (Optional) Attempt to roll back to the previous set of packages on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Attempt to roll back to the previous set of packages on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Attempt to roll back to the previous set of packages on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields A software rollback fails if any required package (or a jbundle package containing the required package) cannot be found in /var/sw/pkg. maintenance • request system software abort • request system software add on page 127 • request system software delete on page 131 • request system software validate on page 135 • request system configuration rescue delete on page 388 • request system configuration rescue save on page 389 request system software rollback on page 134 When you enter this command, you are provided feedback on the status of your request. 133 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Sample Output request system software rollback user@host> request system software rollback Verified SHA1 checksum of ./jbase-7.2R1.7.tgz Verified SHA1 checksum of ./jdocs-7.2R1.7.tgz Verified SHA1 checksum of ./jroute-7.2R1.7.tgz Installing package './jbase-7.2R1.7.tgz' ... Available space: 35495 require: 7335 Installing package './jdocs-7.2R1.7.tgz' ... Available space: 35339 require: 3497 Installing package './jroute-7.2R1.7.tgz' ... Available space: 35238 require: 6976 NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install Reloading /config/juniper.conf.gz ... Activating /config/juniper.conf.gz ... mgd: commit complete Restarting mgd ... Restarting aprobed ... Restarting apsd ... Restarting cosd ... Restarting fsad ... Restarting fud ... Restarting gcdrd ... Restarting ilmid ... Restarting irsd ... Restarting l2tpd ... Restarting mib2d ... Restarting nasd ... Restarting pppoed ... Restarting rdd ... Restarting rmopd ... Restarting rtspd ... Restarting sampled ... Restarting serviced ... Restarting snmpd ... Restarting spd ... Restarting vrrpd ... WARNING: cli has been replaced by an updated version: CLI release 7.2R1.7 built by builder on 2005-04-22 02:03:44 UTC Restart cli using the new version ? [yes,no] (yes) yes Restarting cli ... user@host 134 Chapter 10: Operational Commands for Software Installation request system software validate Syntax Syntax (J-EX Series Switch) Release Information Description Options request system software validate package-name request system software validate Command introduced before Junos OS Release 10.2 for J-EX Series switches. Validate candidate software against the current configuration of the router or switch. member member-id—(J-EX4200 switches only) (Optional) Validate the software bundle or package on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. package-name—Name of the software bundle or package to test. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • request system software abort • request system software add on page 127 • request system software delete on page 131 • request system software rollback on page 133 request system software validate (Successful Case) on page 136 request system software validate (Failure Case) on page 136 When you enter this command, you are provided feedback on the status of your request. 135 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Sample Output request system software validate (Successful Case) user@host> request system software validate /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz Checking compatibility with configuration Initializing... Using /packages/jbase-5.3I20020122_1901_sjg Using /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jbase-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jkernel-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jcrypto-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jpfe-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jdocs-5.3I20020124_0520_sjg.tgz Using /var/chroot/var/tmp/jbundle/jroute-5.3I20020124_0520_sjg.tgz Validating against /config/juniper.conf.gz mgd: commit complete WARNING: cli has been replaced by an updated version: CLI release 5.3I0 built by sjg on 2002-01-24 05:23:53 UTC Restart cli using the new version ? [yes,no] (yes) request system software validate (Failure Case) user@host> request system software validate 6.3/ Pushing bundle to lcc0-re0 error: Failed to transfer package to lcc0-re0 user@host> request system software validate test Pushing bundle to lcc0-re0 Pushing bundle to lcc2-re0 lcc0-re0: gzip: stdin: not in gzip format tar: child returned status 1 ERROR: Not a valid package: /var/tmp/test 136 Chapter 10: Operational Commands for Software Installation show system autoinstallation status Syntax show system autoinstallation status Release Information Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description (J-EX Series switches) Display autoinstallation status information. Options This command has no options. Required Privilege Level view List of Sample Output show system autoinstallation status on page 137 Output Fields Table 32 on page 137 describes the output fields for the show system autoinstallation status command. Output fields are listed in the approximate order in which they appear. Table 32: show system autoinstallation status Output Fields Field Name Field Description Autoinstallation status Display autoinstallation status information: • Last committed file—File last committed for autoinstallation configuration. • Configuration server of last committed file—IP address or URL of server configured to retrieve configuration information for the last committed configuration file. • • Interface—Interface configured for autoinstallation. • Name—Name of interface. • State—Interface state. Address acquisition—Display IP address acquired and protocol used for acquisition upon bootup. • Protocol—Protocol used for acquisition: BOOTP/DHCP or RARP. • Acquired address—IP address acquired from the DHCPserver. Sample Output show system autoinstallation status user@host> show system autoinstallation status Autoinstallation status: Master state: Active Last committed file: None Configuration server of last committed file: 0.0.0.0 Interface: Name: fe-0/0/1 State: None Address acquisition: Protocol: DHCP Client Acquired address: None Protocol: RARP Client Acquired address: None 137 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show system boot-messages Syntax show system boot-messages Syntax (J-EX Series Switch) show system boot-messages Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display initial messages generated by the system kernel upon startup. These messages are the contents of /var/run/dmesg.boot. none—Display all boot time messages. all-members—(J-EX4200 switches only) (Optional) Display boot time messages on all members of the Virtual Chassis configuration. local—(J-EX4200 switches only) (Optional) Display boot time messages on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Display boot time messages on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. Required Privilege Level List of Sample Output view show system boot-messages (QFX Series) on page 138 Sample Output show system boot-messages (QFX Series) user@switch> show sytem boot-messages getmemsize: msgbufp[size=32768] = 0x81d07fe4 System physical memory distribution: ------------------------------------------------------------------------------Total physical memory: 4160749568 (3968 MB) Physical memory used: 3472883712 (3312 MB) Physical memory allocated to kernel: 2130706432 (2032 MB) Physical memory allocated to user BTLB: 1342177280 (1280 MB) ------------------------------------------------------------------------------Copyright (c) 1996-2010, Juniper Networks, Inc. All rights reserved. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. JUNOS 11.1I #0: 2010-09-17 19:18:07 UTC ssiano@svl-junos-pool125.juniper.net:/c/ssiano/DEV_QFX_SI_BRANCH/03/20100917.399988/ obj-xlr/bsd/sys/compile/JUNIPER-DCTOR WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant JUNOS 11.1I #0: 2010-09-17 19:18:07 UTC 138 Chapter 10: Operational Commands for Software Installation ssiano@svl-junos-pool125.juniper.net:/c/ssiano/DEV_QFX_SI_BRANCH/03/20100917.399988/ obj-xlr/bsd/sys/compile/JUNIPER-DCTOR real memory = 3472883712 (3312MB) avail memory = 1708171264 (1629MB) cpuid: 0, btlb_cpumap:0xfffffff8 FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs ETHERNET SOCKET BRIDGE initialising Initializing QFX platform properties .. cpu0 on motherboard : RMI's XLR CPU Rev. 0.3 with no FPU implemented L1 Cache: I size 32kb(32 line), D size 32kb(32 line), eight way. L2 Cache: Size 1024kb, eight way pic_lbus0: pic_lbus0: on motherboard Enter qfx control ethernet probe addr:0xc5eeec00 gmac4: on pic_lbus0 me0: Ethernet address 00:1d:b5:f7:68:40 Enter qfx control ethernet probe addr:0xc5eeeb40 gmac5: on pic_lbus0 me1: Ethernet address 00:1d:b5:f7:68:41 Enter qfx control ethernet probe addr:0xc5eeea80 gmac6: on pic_lbus0 me1: Ethernet address 00:1d:b5:f7:68:42 sio0 on pic_lbus0 Entering sioattach sio0: type 16550A, console xls_setup_intr: skip irq 3, xlr regs are set up somewhere else. gblmem0 on pic_lbus0 ehci0: on pic_lbus0 ehci_bus_attach: allocated resource. tag=1, base=bef24000 xls_ehci_init: endian hardware swapping NOT enabled. usb0: EHCI version 1.0 usb0 on ehci0 usb0: USB revision 2.0 uhub0: vendor 0x0000 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered umass0: USB USBFlashDrive, rev 2.00/11.00, addr 2 pcib0: PCIe link 0 up pcib0: PCIe link 2 up pcib0: PCIe link 3 up pcib0: on pic_lbus0 pci0: on pcib0 pcib1: at device 0.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 1.0 on pci0 pcib3: at device 2.0 on pci0 pci2: on pcib3 pci2: at device 0.0 (no driver attached) pcib4: at device 3.0 on pci0 pci3: on pcib4 pci3: at device 0.0 (no driver attached) cfi device address space at 0xbc000000 cfi0: on pic_lbus0 cfi device address space at 0xbc000000 i2c0: on pic_lbus0 i2c1: on pic_lbus0 qfx_fmn0 on pic_lbus0 pool offset 1503776768 xlr_lbus0: on motherboard 139 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 qfx_bcpld_probe[124] qfx_bcpld_probe[138]: dev_type=0x0 qfx_bcpld_probe[124] qfx_bcpld0: QFX BCPLD probe success qfx_bcpld0qfx_bcpld_attach[174] qfx_bcpld_attach[207] : bus_space_tag=0x0, bus_space_handle=0xbd900000 qfx_bcpld_probe[124] qfx_bcpld1: QFX BCPLD probe success qfx_bcpld1qfx_bcpld_attach[174] tor_bcpld_slave_attach[1245] : bus_space_tag=0x0, bus_space_handle=0xbda00000 Initializing product: 96 .. bmeb: bmeb_lib_init done 0xc60a5000, addr 0x809c99a0 bme0:Virtual BME driver initializing Timecounter "mips" frequency 1200000000 Hz quality 0 Timecounter "xlr_pic_timer" frequency 66666666 Hz quality 1 Timecounters tick every 1.000 msec Loading the NETPFE fc module IPsec: Initialized Security Association Processing. SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #8 Launched! da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 3920MB (8028160 512 byte sectors: 255H 63S/T 499C) Trying to mount root from ufs:/dev/da0s1a 140 Chapter 10: Operational Commands for Software Installation show system license Syntax Release Information Description Options show system license Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display licenses and information about how they are used. none—Display all license information. installed—(Optional) Display installed licenses only. keys—(Optional) Display a list of license keys. Use this information to verify that each expected license key is present. usage—(Optional) Display the state of licensed features. Required Privilege Level List of Sample Output Output Fields maintenance show system license on page 142 show system license installed on page 142 show system license keys on page 143 show system license usage on page 143 Table 33 on page 141 lists the output fields for the show system license command. Output fields are listed in the approximate order in which they appear. Table 33: show system license Output Fields Field Name Field Description Feature name Name assigned to the configured feature. You use this information to verify that all the features for which you installed licenses are present. Licenses used Number of licenses used by a router or switch. You use this information to verify that the number of licenses used matches the number configured. If a licensed feature is configured, the feature is considered used. NOTE: In Junos OS Release 10.1 and later, the Licenses used column displays the actual usage count based on the number of active sessions or connections as reported by the corresponding feature daemons. This is applicable for scalable license-based features such as Subscriber Access (scale-subscriber), L2TP (scale-l2tp), Mobile IP (scale-mobile-ip), and so on. 141 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 33: show system license Output Fields (continued) Field Name Field Description Licenses installed Information about the installed license key: • License identifier—Identifier associated with a license key. • State—State of the license key:valid or invalid. An invalid state indicates that the key was entered incorrectly or is not valid for the specific device. • License version—Version of a license. The version indicates how the license is validated, the type of signature, and the signer of the license key. • Valid for device—Device that can use a license key. • Group defined—Group membership of a device. • Features—Feature associated with a license, such as data link switching (DLSw). Licenses needed Number of licenses required for features being used but not yet properly licensed. Expiry Amount of time left within the grace period before a license is required for a feature being used. Sample Output show system license user@host> show system license License usage: Feature name subscriber-accounting subscriber-authentication subscriber-address-assignment subscriber-vlan subscriber-ip scale-subscriber scale-l2tp scale-mobile-ip Licenses used 2 1 2 2 0 2 4 1 Licenses installed 2 2 2 2 2 3 5 2 Licenses needed 0 0 0 0 0 0 0 0 Expiry Licenses installed: License identifier: XXXXXXXXXX License version: 2 Features: subscriber-accounting - Per Subscriber Radius Accounting permanent subscriber-authentication - Per Subscriber Radius Authentication permanent subscriber-address-assignment - Radius/SRC Address Pool Assignment permanent subscriber-vlan - Dynamic Auto-sensed Vlan permanent subscriber-ip - Dynamic and Static IP permanent permanent permanent permanent permanent permanent permanent permanent permanent show system license installed 142 user@host> show system license installed License identifier: XXXXXXXXXX License version: 2 Features: subscriber-accounting - Per Subscriber Radius Accounting permanent subscriber-authentication - Per Subscriber Radius Authentication Chapter 10: Operational Commands for Software Installation permanent subscriber-address-assignment - Radius/SRC Address Pool Assignment permanent subscriber-vlan - Dynamic Auto-sensed Vlan permanent subscriber-ip - Dynamic and Static IP permanent show system license keys user@host> show system license keys XXXXXXXXXX xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxxxxx xxx show system license usage user@host> show system license usage License usage: Licenses Feature name used subscriber-accounting 2 subscriber-authentication 1 subscriber-address-assignment 2 subscriber-vlan 2 subscriber-ip 0 scale-subscriber 2 scale-l2tp 4 scale-mobile-ip 1 Licenses installed 2 2 2 2 2 3 5 2 Licenses needed 0 0 0 0 0 0 0 0 Expiry permanent permanent permanent permanent permanent permanent permanent permanent 143 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show system snapshot Syntax Release Information Description Options show system snapshot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the complete collection of files in a snapshot. none—Display the system snapshot on the alternate media, which is the media that does not have the software packages that last booted the switch. all-members | local | member member-id—(J-EX4200 switch only) Display the snapshot in a Virtual Chassis configuration: • all-members—Display the snapshot for each switch that is a member of the Virtual Chassis. • local—Display the snapshot on the switch that you are currently logged into. • member member-id—Display the snapshot for the specified member switch of the Virtual Chassis. media (external | internal)—(Optional) Display the destination media location for the snapshot. The external option specifies the snapshot on an external mass storage device, such as a USB flash drive. The internal option specifies the snapshot on an internal memory source, such as internal flash memory. slice (1 | 2 | alternate)—Display the snapshot in a partition: • 1—Display the snapshot in partition 1. • 2—Display the snapshot in partition 2. • alternate—Display the snapshot in the alternate partition, which is the partition that did not boot the switch at the last bootup. Required Privilege Level Related Documentation view • request system snapshot on page 125 • Creating a Snapshot and Using It to Boot a J-EX Series Switch on page 92 • Verifying That a System Snapshot Was Created on a J-EX Series Switch on page 100 show system snapshot media external user@switch> show system snapshot media external Information for snapshot on external (da1s1) Creation date: Oct 13 20:23:23 2009 JUNOS version on snapshot: 144 Chapter 10: Operational Commands for Software Installation jbase : 10.0I20090726_0011_user jcrypto-ex: 10.0I20090726_0011_user jdocs-ex: 10.0I20090726_0011_user jkernel-ex: 10.0I20090726_0011_user jroute-ex: 10.0I20090726_0011_user jswitch-ex: 10.0I20090726_0011_user jweb-ex: 10.0I20090726_0011_user jpfe-ex42x: 10.0I20090726_0011_user 145 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show system storage partitions (J-EX Series Switches Only) Syntax Release Information Description Options show system storage partitions Command introduced in Junos OS Release 11.1 for J-EX Series switches. Display information about the disk partitions on J-EX Series switches. none—Display partition information. all-members—(Optional) Display partition information for all members of the Virtual Chassis. local—(Optional) Display partition information for the local Virtual Chassis member. member member-id—(Optional) Display partition information for the specified member of the Virtual Chassis configuration. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Verifying Junos OS and Boot Loader Software Versions on a J-EX Series Switch on page 100 show system storage partitions on page 147 Table 34 on page 146 describes the output fields for the show system storage partitions command. Output fields are listed in the approximate order in which they appear. Table 34: show system storage partitions Output Fields Field Name Field Description Boot Media Media (internal or external) from which the switch was booted. Active Partition Name of the active root partition. Backup Partition Name of the backup (alternative) root partition. Currently booted from Partition from which the switch was last booted. Partitions information Information about partitions on the boot media: 146 • Partition—Partition identifier. • Size—Size of partition. • Mountpoint—Directory on which the partition is mounted. Chapter 10: Operational Commands for Software Installation Sample Output show system storage partitions user@switch> show system storage partitions fpc0: -------------------------------------------------------------------------Boot Media: internal (da0) Active Partition: da0s1a Backup Partition: da0s2a Currently booted from: active (da0s1a) Partitions information: Partition Size Mountpoint s1a 184M / s2a 184M altroot s3d 369M /var/tmp s3e 123M /var s4d 62M /config s4e unused (backup config) 147 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 148 PART 4 User Interfaces • User Interfaces Overview on page 151 • Using the Configuration Tools on page 159 • Operational Commands for User Interfaces on page 161 149 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 150 CHAPTER 11 User Interfaces Overview • User Interfaces—Overview on page 151 User Interfaces—Overview • CLI User Interface Overview on page 151 • J-Web User Interface for J-EX Series Switches Overview on page 153 • Understanding J-Web Configuration Tools on page 155 • Understanding J-Web User Interface Sessions on page 157 CLI User Interface Overview You can use two interfaces to monitor, configure, troubleshoot, and manage a J-EX Series Switch: the J-Web graphical user interface and the Junos operating system (Junos OS) command-line interface (CLI). Both of these user interfaces are shipped with the switch. This topic describes the CLI. For information about the J-Web user interface, see “J-Web User Interface for J-EX Series Switches Overview” on page 153. • CLI Overview on page 151 • CLI Help and Command Completion on page 151 • CLI Command Modes on page 152 CLI Overview The Junos OS CLI is a command shell that runs on top of a UNIX-based operating system kernel. The CLI provides command help and command completion. The CLI also provides a variety of UNIX utilities, such as Emacs-style keyboard sequences that allow you to move around on a command line and scroll through recently executed commands, regular expression matching to locate and replace values and identifiers in a configuration, filter command output, or log file entries, store and archive router files on a UNIX-based file system, and exit from the CLI environment and create a UNIX C shell or Bourne shell to navigate the file system, manage switch processes, and so on. CLI Help and Command Completion To access CLI Help, type a question mark (?) at any level of the hierarchy. The system displays a list of the available commands or statements and a short description of each. 151 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 To complete a command, statement, or option that you have partially typed, press the Tab key or the Spacebar. If the partially typed letters uniquely identify a command, the complete command name appears. Otherwise, a beep indicates that you have entered an ambiguous command and the possible completions are displayed. This completion feature also applies to other strings, such as filenames, interface names, usernames, and configuration statements. CLI Command Modes The CLI has two modes, operational mode and configuration mode. In operational mode, you enter commands to monitor and troubleshoot switch hardware and software and network connectivity. Operational mode is indicated by the > prompt—for example, user@switch>. In configuration mode, you can define all properties of the Junos operating system (Junos OS), including interfaces, VLANs, Virtual Chassis information, routing protocols, user access, and several system hardware properties. To enter configuration mode, enter the configure command: user@switch> configure Configuration mode is indicated by the # prompt, and includes the current location in the configuration hierarchy—for example: [edit interfaces ge-0/0/12] user@switch# In configuration mode, you are actually viewing and changing the candidate configuration file. The candidate configuration allows you to make configuration changes without causing operational changes to the current operating configuration, called the active configuration. When you commit the changes you added to the candidate configuration, the system updates the active configuration. Candidate configurations enable you to alter your configuration without causing potential damage to your current network operations. To activate your configuration changes, enter the commit command. To return to operational mode, go to the top of the configuration hierarchy and then quit—for example: [edit interfaces ge-0/0/12] user@switch# top [edit] user@switch# exit You can also activate your configuration changes and exit configuration mode with a single command, commit and-quit. This command succeeds only if there are no mistakes or syntax errors in the configuration. TIP: When you commit the candidate configuration, you can require an explicit confirmation for the commit to become permanent by using the commit 152 Chapter 11: User Interfaces Overview confirmed command. This is useful for verifying that a configuration change works correctly and does not prevent management access to the switch. After you issue the commit confirmed command, you must issue another commit command within the defined period of time (10 minutes by default) or the system reverts to the previous configuration. Related Documentation • J-EX Series Switch Software Features Overview on page 3 • Junos OS CLI User Guide J-Web User Interface for J-EX Series Switches Overview You can use two interfaces to monitor, configure, troubleshoot, and manage a J-EX Series Switch: the J-Web graphical user interface and the Junos OS command-line interface (CLI). Both user interfaces are shipped with the switch. This topic describes the J-Web interface. You can navigate the J-Web interface, scroll pages, and expand and collapse elements as you do in a typical Web browser interface. For information about the CLI user interface, see “CLI User Interface Overview” on page 151. NOTE: To access the J-Web interface, your management device must have the following software installed: • Operating system: Microsoft Windows XP Service Pack 3 • Browser version: One of the following. Other browsers might work but are not supported by J-Series platforms. • • Microsoft Internet Explorer version 7.0 • Mozilla Firefox version 3.0 Additional requirements: • Only English-language browsers are supported. • The browser and the network must be able to receive and process HTTP/1.1 gzip compressed data. Each page of the J-Web interface is divided into panes. • Top pane—Displays system identity information and links. • Main pane—Location where you monitor, configure, diagnose (troubleshoot), and manage (maintain) the switch by entering information in text boxes, making selections, and clicking buttons. • Side pane—Displays suboptions of the Monitor, Configure, Troubleshoot, or Maintain task currently displayed in the main pane. Click a suboption to access it in the main pane. 153 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 The layout of the panes allows you to quickly navigate through the interface. Table 35 on page 154 summarizes the elements of the J-Web interface. The J-Web interface provides CLI tools that allow you to perform all of the tasks that you can perform from the Junos OS command-line interface (CLI), including a CLI Viewer to view the current configuration, a CLI Editor for viewing and modifying the configuration, and a Point & Click CLI editor that allows you to click through all of the available CLI statements. Table 35: J-Web Interface J-Web Interface Element Description Top Pane Host The hostname of the switch. Logged in as: username The username you used to log in to the switch. Commit Options A set of options using which you can configure committing multiple changes with a single commit. • Commit—Commits the candidate configuration of the current user session, along with changes from other user sessions. • Compare—Displays the XML log of pending configurations on the device. • Discard—Discards the candidate configuration of the current user session, along with changes from other user sessions. • Preference—Indicates your choice of committing all configurations changes together or committing each configuration change immediately. The two commit options are: • Commit changes immediately—Sets the system to force an immediate commit on every page after every configuration change. • Validate changes until explicit commit—Loads all configuration changes for an accumulated single commit. If there are errors in loading the configuration, the errors are logged. This is the default mode. NOTE: There are some pages on which configuration changes must be committed immediately. For such pages, if you configure the commit options for a single commit, the system displays warning notifications that remind you to commit your changes immediately. An example for such a page is Switching. Help Logout 154 Displays links to information on help and the J-Web interface. • Help Contents—View context-sensitive help topics. • About—Displays information about the J-Web interface, such as the version number. Ends your current login session with the switch and returns you to the login page. Chapter 11: User Interfaces Overview Table 35: J-Web Interface (continued) J-Web Interface Element Description Taskbar Menu of J-Web main options. Click the tab to access an option. • Dashboard—Displays a high-level, graphical view of the chassis and status of the switch. It displays system health information, alarms, and system status. • Configure—Configure the switch, and view configuration history. • Monitor—View information about configuration and hardware on the switch. • Maintain—Manage files and licenses, upgrade software, and reboot the switch. • Troubleshoot—Run diagnostic tools to troubleshoot network issues. Main Pane Help (?) icon Displays useful information—such as the definition, format, and valid range of an option—when you move the cursor over the question mark. Red asterisk (*) Indicates a required field. Icon legend (Applies to the Point & Click CLI editor only) Explains icons that appear in the user interface to provide information about configuration statements: • C—Comment. Move your cursor over the icon to view a comment about the configuration statement. • I—Inactive. The configuration statement does not apply for the switch. • M—Modified. The configuration statement has been added or modified. • *—Mandatory. The configuration statement must have a value. Task Pane Configuration hierarchy Related Documentation (Applies to the Junos OS CLI configuration editor only) Displays the hierarchy of committed statements in the switch configuration. • Click Expand all to display the entire hierarchy. • Click Hide all to display only the statements at the top level. • Click plus signs (+) to expand individual items. • Click minus signs (-) to hide individual items. • Using the Commit Options to Commit Configuration Changes (J-Web Procedure) on page 346 • J-EX Series Switch Software Features Overview on page 3 • J-EX4200 Switches Hardware Overview on page 29 • J-EX Series Switch Software Features Overview on page 3 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • CLI User Interface Overview on page 151 Understanding J-Web Configuration Tools The J-Web graphical user interface (GUI) allows you to monitor, configure, troubleshoot, and manage the switching platform by means of a Web browser with Hypertext Transfer 155 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Protocol (HTTP) or HTTP over Secure Sockets Layer (HTTPS) enabled. The J-Web interface provides access to all the configuration statements supported by the switch. The J-Web interface provides three methods of configuring the switch: • Configure menu • Point & Click CLI Editor • CLI Editor Table 36 on page 156 gives a comparison of the three methods of configuration. Table 36: Switching Platform Configuration Interfaces Tool Description Function Use Configure menu Web browser pages for setting up the switch quickly and easily without configuring each statement individually. Configure basic switch platform services: Use for basic configuration. • Interfaces • Switching • Virtual Chassis • Security NOTE: You can configure and manage a standalone J-EX4500 switch with the J-Web interface, but the J-Web interface does not support configuration and management of a J-EX4500 Virtual Chassis. • Services • System Properties • Routing Web browser pages divided into panes in which you can do any of the following: Configure all switching platform services: • • System parameters • User Accounting and Access • Interfaces • VLAN properties • Virtual Chassis properties For example, use the Virtual Chassis Configuration page to configure the Virtual Chassis parameters on a J-EX4200 switch. Point & Click CLI editor • CLI editor Paste a complete configuration hierarchy into a scrollable text box, or edit individual lines. • Upload or download a complete configuration. • Secure Access • Roll back to a previous configuration. • Services • Create or delete a rescue configuration. • Routing protocols Interface in which you do any of the following: Configure all switching platform services: • Type commands on a line and press Enter to create a hierarchy of configuration statements. • System parameters • Create an ASCII text file that contains the statement hierarchy. • User Accounting and Access • Interfaces • Upload a complete configuration, or roll back to a previous configuration. • VLAN properties • Virtual Chassis properties • Secure Access • Services • Routing protocols • 156 Expand the entire configuration hierarchy and click a configuration statement to view or edit. The main pane displays all the options for the statement, with a text box for each option. Create or delete a rescue configuration. Use for complete configuration if you are not familiar with the Junos OS CLI or prefer a graphical interface. Use for complete configuration if you know the Junos OS CLI or prefer a command interface. Chapter 11: User Interfaces Overview Related Documentation • Understanding J-Web User Interface Sessions on page 157 • J-Web User Interface for J-EX Series Switches Overview on page 153 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • Configuration Files Terms on page 328 Understanding J-Web User Interface Sessions You establish a J-Web session with the switch through an HTTP-enabled or HTTPS-enabled Web browser. The HTTPS protocol, which uses 128-bit encryption, is available only in domestic versions of the Junos operating system (Junos OS). To use HTTPS, you must have installed a certificate on the switch and enabled HTTPS. See “Generating SSL Certificates to Be Used for Secure Web Access” on page 410. When you attempt to log in through the J-Web interface, the switch authenticates your username with the same methods used for Telnet and SSH. If the switch does not detect any activity through the J-Web interface for 15 minutes, the session times out and is terminated. You must log in again to begin a new session. To explicitly terminate a J-Web session at any time, click Logout in the top pane. Related Documentation • J-Web User Interface for J-EX Series Switches Overview on page 153 • Configuring Management Access for the J-EX Series Switch (J-Web Procedure) on page 407 157 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 158 CHAPTER 12 Using the Configuration Tools • Using the CLI Terminal on page 159 • Starting the J-Web Interface on page 160 Using the CLI Terminal The J-Web CLI terminal provides access to the Junos OS command-line interface (CLI) through the J-Web interface. The functionality and behavior of the CLI available through the CLI terminal page is the same as that of the Junos OS CLI available through the switch console. The CLI terminal supports all CLI commands and other features such as CLI help and autocompletion. Using the CLI terminal page you can fully configure, monitor, and manage the switch. • Before you can use the CLI terminal, you must configure the domain name and hostname of the switch. See “Configuring System Identity for the J-EX Series Switch (J-Web Procedure)” on page 193 for more information. • To access the CLI through the J-Web interface, your management device requires the following features: • SSH access—Enable Secure shell (SSH) on your system. SSH provides a secured method of logging in to the switch, to encrypt traffic so that it is not intercepted. If SSH is not enabled on the system, the CLI terminal page displays an error. • Java applet support—Make sure that your Web browser supports Java applets. • JRE installed on the client—Install Java Runtime Environment (JRE) version 1.4 or later on your system. JRE is a software package that must be installed on a system to run Java applications. Download the latest JRE version from the Java Software website http://www.java.com/. Installing JRE installs Java plug-ins, which once installed, load automatically and transparently to render Java applets. NOTE: The CLI terminal is supported on JRE version 1.4 and later only. To access the CLI terminal, select Troubleshoot >CLI Terminal. Related Documentation • CLI User Interface Overview on page 151 159 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Understanding J-Web Configuration Tools on page 155 Starting the J-Web Interface You can use the J-Web graphical interface to configure and manage the J-EX Series switch. To start the J-Web interface: 1. Launch your HTTP-enabled or HTTPS-enabled Web browser. To use HTTPS, you must have installed a certificate on the switch and enabled HTTPS. 2. After http:// or https:// in your Web browser, type the hostname or IP address of the switch and press Enter. The J-Web login page appears. 3. On the login page, type your username and password, and click Log In. To correct or change the username or password you typed, click Reset, type the new entry or entries, and click Log In. NOTE: The default username is root with no password. You must change this during initial configuration or the system does not accept the configuration. The Chassis Dashboard information page appears. To explicitly terminate a J-Web session at any time, click Logout in the top pane. Related Documentation 160 • J-Web User Interface for J-EX Series Switches Overview on page 153 • Understanding How to Use the J-Web Interface to View System Information CHAPTER 13 Operational Commands for User Interfaces 161 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 set cli complete-on-space Syntax Release Information Description Options set cli complete-on-space (off | on) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the command-line interface (CLI) to complete a partial command entry when you type a space or a tab. This is the default behavior of the CLI. off—Turn off command completion. on—Allow either a space or a tab to be used for command completion. Required Privilege Level Related Documentation List of Sample Output Output Fields view • CLI User Interface Overview • show cli on page 171 set cli complete-on-space on page 162 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli complete-on-space In the following example, pressing the Spacebar changes the partial command entry from com to complete-on-space. The example shows how adding the keyword off at the end of the command disables command completion. user@host> set cli com user@host>set cli complete-on-space off Disabling complete-on-space 162 Chapter 13: Operational Commands for User Interfaces set cli directory Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields set cli directory directory Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the current working directory. directory—Pathname of the working directory. view • CLI User Interface Overview • show cli directory on page 176 set cli directory on page 163 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli directory user@host> set cli directory /var/home/regress Current directory: /var/home/regress 163 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 set cli idle-timeout Syntax Release Information set cli idle-timeout Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Set the maximum time that an individual session can be idle before the user is logged off the router or switch. Options minutes—(Optional) Maximum idle time. The range of values, in minutes, is 0 through 100,000. If you do not issue this command, and the user’s login class does not specify this value, the user is never forced off the system after extended idle times. Setting the value to 0 disables the timeout. Required Privilege Level Related Documentation List of Sample Output Output Fields view • CLI User Interface Overview • show cli on page 171 set cli idle-timeout on page 164 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli idle-timeout 164 user@host> set cli idle-timeout 60 Idle timeout set to 60 minutes Chapter 13: Operational Commands for User Interfaces set cli prompt Syntax Release Information Description Options set cli prompt string Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the prompt so that it is displayed within the CLI. string—CLI prompt string. To include spaces in the prompt, enclose the string in quotation marks. By default, the string is username@hostname. Required Privilege Level Related Documentation List of Sample Output Output Fields view • CLI User Interface Overview • show cli on page 171 set cli prompt on page 165 When you enter this command, the new CLI prompt is displayed. Sample Output set cli prompt user@host> set cli prompt lab1-router> lab1-router> 165 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 set cli restart-on-upgrade Syntax Release Information Description Options set cli restart-on-upgrade string (off | on) Command introduced before Junos OS Release 10.2 for J-EX Series switches. For an individual session, set the CLI to prompt you to restart the router or switch after upgrading the software. off—Disables the prompt. on—Enables the prompt. Required Privilege Level Related Documentation List of Sample Output Output Fields view • CLI User Interface Overview • show cli on page 171 set cli restart-on-upgrade on page 166 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli restart-on-upgrade 166 user@host> set cli restart-on-upgrade on Enabling restart-on-upgrade Chapter 13: Operational Commands for User Interfaces set cli screen-length Syntax Release Information Description Options set cli screen-length length Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set terminal screen length. length—Number of lines of text that the terminal screen displays (0 through 10,000). The default is 24. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields The point at which the ---(more)--- prompt appears on the screen is a function of this setting and the settings for the set cli screen-width and set cli terminal commands. view • CLI User Interface Overview • set cli screen-width on page 168 • set cli terminal on page 169 • show cli on page 171 set cli screen-length on page 167 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli screen-length user@host> set cli screen-length 75 Screen length set to 75 167 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 set cli screen-width Syntax Release Information Description Options Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields set cli screen-width width Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the terminal screen width. width—Number of characters (0 through 1024) in a line. The default is 80. The point at which the ---(more)--- prompt appears on the screen is a function of this setting and the settings for the set cli screen-length and set cli terminal commands. view • CLI User Interface Overview • set cli screen-length on page 167 • set cli terminal on page 169 • show cli on page 171 set cli screen-width on page 168 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli screen-width 168 user@host> set cli screen-width Screen width set to 132 Chapter 13: Operational Commands for User Interfaces set cli terminal Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields set cli terminal terminal-type Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the terminal type. terminal-type—Type of terminal that is connected to the Ethernet management port: • ansi—ANSI-compatible terminal (80 characters by 24 lines) • small-xterm—Small xterm window (80 characters by 24 lines) • vt100—VT100-compatible terminal (80 characters by 24 lines) • xterm—Large xterm window (80 characters by 65 lines) view • CLI User Interface Overview • set cli screen-length on page 167 • set cli screen-width on page 168 • show cli on page 171 set cli terminal on page 169 This command provides no output. Sample Output set cli terminal user@host> set cli terminal xterm 169 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 set cli timestamp Syntax Release Information Description Options set cli timestamp (format timestamp-format | disable) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set a timestamp for CLI output. format timestamp-format—Set the date and time format for the timestamp. The timestamp format you specify can include the following placeholders in any order: • %m—Two-digit month • %d—Two-digit date • %T—Six-digit hour, minute, and seconds disable—Remove the timestamp from the CLI. Required Privilege Level Related Documentation List of Sample Output Output Fields view • CLI User Interface Overview • show cli on page 171 set cli timestamp on page 170 When you enter this command, you are provided feedback on the status of your request. Sample Output set cli timestamp 170 user@host> set cli timestamp format '%m-%d-%T' '04-21-17:39:13' CLI timestamp set to: '%m-%d-%T' Chapter 13: Operational Commands for User Interfaces show cli Syntax Release Information show cli Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Display configured CLI settings. Options This command has no options. Required Privilege Level List of Sample Output Output Fields view show cli on page 171 Table 37 on page 171 lists the output fields for the show cli command. Output fields are listed in the approximate order in which they appear. Table 37: show cli Output Fields Field Name Field Description CLI complete-on-space Capability to complete a partial command entry when you type a space or a tab: on or off. CLI idle-timeout Maximum time that an individual session can be idle before the user is logged off the router or switch. When this feature is enabled, the number of minutes is displayed. Otherwise, the state is disabled. CLI restart-on-upgrade CLI is set to prompt you to restart the router or switch after upgrading the software: on or off. CLI screen-length Number of lines of text that the terminal screen displays. CLI screen-width Number of characters in a line on the terminal screen. CLI terminal Terminal type. CLI is operating in Mode: enhanced. CLI timestamp Date and time format for the timestamp. If the timestamp is not set, the state is disabled. CLI working directory Pathname of the working directory. Sample Output show cli user@host> show cli CLI complete-on-space set to on CLI idle-timeout disabled CLI restart-on-upgrade set to on CLI screen-length set to 47 CLI screen-width set to 132 CLI terminal is 'vt100' CLI is operating in enhanced mode 171 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 CLI timestamp disabled CLI working directory is '/var/home/regress' 172 Chapter 13: Operational Commands for User Interfaces show cli authorization Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show cli authorization Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the permissions for the current user. This command has no options. view show cli authorization on page 175 Table 38 on page 173 lists the output fields for the show cli authorization command. In the table, all possible permissions are displayed and output fields are listed in alphabetical order. Table 38: show cli authorization Output Fields Field Name Field Description access Can view access configuration information. access-control Can modify access configuration. admin Can view user account information. admin-control Can modify user account information. clear Can clear learned network information. configure Can enter configuration mode. control Can modify any configuration. edit Can edit configuration files. field Reserved for field (debugging) support. firewall Can view firewall configuration information. firewall-control Can modify firewall configuration information. floppy Can read from and write to removable media. flow-tap Can view flow-tap configuration information. flow-tap-control Can configure flow-tap configuration information. 173 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Table 38: show cli authorization Output Fields (continued) 174 Field Name Field Description idp-profiler-operation Can configure Profiler data. interface Can view interface configuration information. interface-control Can modify interface configuration information. maintenance Can perform system maintenance. network Can access the network by entering the ping, ssh, telnet, and traceroute commands. pgcp-session-mirroring Can view Packet Gateway Control Protocol (PGCP) session mirroring configuration. pgcp-session-mirroring-control Can modify PGCP session mirroring configuration all-control. reset Can reset or restart interfaces and system processes. rollback Can roll back to previous configurations. routing Can view routing configuration information. routing-control Can modify routing configuration information. secret Can view passwords and authentication keys in the configuration. secret-control Can modify passwords and authentication keys in the configuration. security Can view security configuration information. security-control Can modify security configuration information. shell Can start a local shell. snmp Can view SNMP configuration information. snmp-control Can modify SNMP configuration information. system Can view system configuration information. system-control Can modify system configuration information. trace Can view trace file settings information. trace-control Can modify trace file settings information. view Can view current values and statistics. Chapter 13: Operational Commands for User Interfaces Table 38: show cli authorization Output Fields (continued) Field Name Field Description view-configuration Can view all configuration information (not including secrets). Sample Output show cli authorization user@host> show cli authorization Current user: 'remote' login: 'user' class '' Permissions: admin -- Can view user accounts admin-control-- Can modify user accounts clear -- Can clear learned network information configure -- Can enter configuration mode control -- Can modify any configuration edit -- Can edit full files field -- Special for field (debug) support floppy -- Can read and write from the floppy interface -- Can view interface configuration interface-control-- Can modify interface configuration network -- Can access the network reset -- Can reset/restart interfaces and daemons routing -- Can view routing configuration routing-control-- Can modify routing configuration shell -- Can start a local shell snmp -- Can view SNMP configuration snmp-control-- Can modify SNMP configuration system -- Can view system configuration system-control-- Can modify system configuration trace -- Can view trace file settings trace-control-- Can modify trace file settings view -- Can view current values and statistics maintenance -- Can become the super-user firewall -- Can view firewall configuration firewall-control-- Can modify firewall configuration secret -- Can view secret configuration secret-control-- Can modify secret configuration rollback -- Can rollback to previous configurations security -- Can view security configuration security-control-- Can modify security configuration access -- Can view access configuration access-control-- Can modify access configuration view-configuration-- Can view all configuration (not including secrets) flow-tap -- Can view flow-tap configuration flow-tap-control-- Can configure flow-tap service Individual command authorization: Allow regular expression: none Deny regular expression: none Allow configuration regular expression: none Deny configuration regular expression: none 175 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show cli directory Syntax Release Information Description Options Required Privilege Level List of Sample Output Output Fields show cli directory Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display the current working directory. This command has no options. view show cli directory on page 176 Table 39 on page 176 lists the output fields for the show cli directory command. Output fields are listed in the approximate order in which they appear. Table 39: show cli directory Output Fields Field Name Field Description Current directory Pathname of the current working directory. Sample Output show cli directory 176 user@host> show cli directory Current directory: /var/home/regress Chapter 13: Operational Commands for User Interfaces show cli history Syntax Release Information Description Options show cli history Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display a list of previous CLI commands. none—Display all previous CLI commands. count—(Optional) Maximum number of commands to display. Required Privilege Level List of Sample Output Output Fields view show cli history on page 177 Table 40 on page 177 lists the output fields for the show cli history command. Output fields are listed in the approximate order in which they appear. Table 40: show cli history Output Fields Field Name Field Description timestamp Time at which the command was entered. command-syntax Command that was entered. Sample Output show cli history user@host> 11:14:14 11:22:10 11:27:12 show cli history -- show arp -- show cli authorization -- show cli history 177 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 start shell Syntax Release Information Description start shell (csh | sh) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Exit from the CLI environment and create a UNIX-level shell. To return to the CLI, type exit from the shell. NOTE: To issue this command, the user must have the required login access privileges configured by including the permissions statement at the [edit system login class class-name] hierarchy level. UNIX wheel group membership or permissions are no longer required to issue this command. Options csh—Create a UNIX C shell. sh—Create a UNIX Bourne shell. user username—(Optional) Start the shell as another user. Additional Information When you are in the shell, the shell prompt has the following format: username@hostname% An example of the prompt is: root@host% Required Privilege Level List of Sample Output Output Fields shell and maintenance start shell csh on page 178 When you enter this command, you are provided feedback on the status of your request. Sample Output start shell csh user@host> start shell csh % exit % username@hostname% start shell sh % exit user@host> 178 PART 5 Junos OS for J-EX Series Switches System Setup • System Setup Overview on page 181 • Initial Configuration on page 185 • Configuration Statements for System Setup on page 195 • Operational Commands for System Setup on page 227 179 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 180 CHAPTER 14 System Setup Overview • Junos OS—Overview on page 181 Junos OS—Overview • J-EX Series Switch Software Features Overview on page 181 • Understanding Software Infrastructure and Processes on page 182 J-EX Series Switch Software Features Overview The following tables list the J-EX Series Switches software features, the Junos OS release in which they were introduced, and the first Junos OS release for each switch: • Table 2 on page 4—First Junos OS Release for Each J-EX Series Switch • Table 3 on page 4—Access Control Features • Table 4 on page 5—Administration Features • Table 5 on page 5—Class-of-Service (CoS) Features • Table 6 on page 6—Device Security Features • Table 7 on page 6—Fibre Channel over Ethernet Features • Table 8 on page 7—High Availability and Resiliency Features • Table 9 on page 8—Interfaces Features • Table 10 on page 9—IP Address Management Features • Table 11 on page 9—IPv6 Features • Table 12 on page 10—Layer 2 Network Protocols Features • Table 13 on page 10—Layer 3 Protocols Features • Table 14 on page 12—MPLS Features • Table 15 on page 12—Multicast Features • Table 16 on page 13—Network Management and Monitoring Features • Table 17 on page 14—Port Security Features • Table 18 on page 15—Routing Policy and Packet Filtering Features 181 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Table 19 on page 15—Spanning-Tree Protocols Features • Table 20 on page 16—System Management Features The Junos OS release for software features on a switch cannot be earlier than the first Junos OS release for that switch. Related Documentation • J-EX4200 Switches Hardware Overview on page 29 • J-EX4500 Switches Hardware Overview on page 31 • J-EX8208 Switch Hardware Overview on page 35 • J-EX8216 Switch Hardware Overview on page 38 • Layer 3 Protocols Supported on J-EX Series Switches on page 17 • Layer 3 Protocols Not Supported on J-EX Series Switches on page 18 Understanding Software Infrastructure and Processes Each switch runs the Junos operating system (Junos OS) for J-EX Series Switches on its general-purpose processors. Junos OS includes processes for Internet Protocol (IP) routing and for managing interfaces, networks, and the chassis. The Junos OS runs on the Routing Engine. The Routing Engine kernel coordinates communication among the Junos OS processes and provides a link to the Packet Forwarding Engine. With the J-Web interface and the command-line interface (CLI) to the Junos OS, you configure switching features and routing protocols and set the properties of network interfaces on your switch. After activating a software configuration, use either the J-Web or CLI user interface to monitor the switch, manage operations, and diagnose protocol and network connectivity problems. • Routing Engine and Packet Forwarding Engine on page 182 • Junos OS Processes on page 183 Routing Engine and Packet Forwarding Engine A switch has two primary software processing components: 182 • Packet Forwarding Engine—Processes packets; applies filters, routing policies, and other features; and forwards packets to the next hop along the route to their final destination. • Routing Engine—Provides three main functions: • Creates the packet forwarding switch fabric for the switch, providing route lookup, filtering, and switching on incoming data packets, then directing outbound packets to the appropriate interface for transmission to the network • Maintains the routing tables used by the switch and controls the routing protocols that run on the switch. Chapter 14: System Setup Overview • Provides control and monitoring functions for the switch, including controlling power and monitoring system status. Junos OS Processes The Junos OS running on the Routing Engine and Packet Forwarding Engine consists of multiple processes that are responsible for individual functions. The separation of functions provides operational stability, because each process accesses its own protected memory space. In addition, because each process is a separate software package, you can selectively upgrade all or part of the Junos OS, for added flexibility. Table 23 on page 26 describes the primary Junos OS processes. Table 41: Junos OS Processes Process Name Description Chassis process chassisd Detects hardware on the system that is used to configure network interfaces. Monitors the physical status of hardware components and field-replaceable units (FRUs), detecting when environment sensors such as temperature sensors are triggered. Relays signals and interrupts—for example, when devices are taken offline, so that the system can close sessions and shut down gracefully. Ethernet switching process eswd Handles Layer 2 switching functionality such as MAC address learning, Spanning Tree protocol and access port security. The process is also responsible for managing Ethernet switching interfaces, VLANs, and VLAN interfaces. Manages Ethernet switching interfaces, VLANs, and VLAN interfaces. Forwarding process pfem Defines how routing protocols operate on the switch. The overall performance of the switch is largely determined by the effectiveness of the forwarding process. Interface process dcd Configures and monitors network interfaces by defining physical characteristics such as link encapsulation, hold times, and keepalive timers. Management process mgd Provides communication between the other processes and an interface to the configuration database. Populates the configuration database with configuration information and retrieves the information when queried by other processes to ensure that the system operates as configured. Interacts with the other processes when commands are issued through one of the user interfaces on the switch. If a process terminates or fails to start when called, the management process attempts to restart it a limited number of times to prevent thrashing and logs any failure information for further investigation. Routing protocol process rpd Defines how routing protocols such as RIP, OSPF, and BGP operate on the device, including selecting routes and maintaining forwarding tables. 183 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation 184 • For more information about processes, see the Junos OS Network Operations Guide • For more information about basic system parameters, supported protocols, and software processes, see the Junos OS System Basics Configuration Guide CHAPTER 15 Initial Configuration • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 185 • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) on page 192 • Configuring System Identity for a J-EX Series Switch (J-Web Procedure) on page 193 Connecting and Configuring a J-EX Series Switch (CLI Procedure) There are two ways to connect and configure a J-EX Series switch: one method is through the console using the command-line interface (CLI) and the other is using the J-Web interface. This topic describes the CLI procedure. NOTE: To run the ezsetup script, the switch must have the factory default configuration as the active configuration. If you have configured anything on the switch and want to run ezsetup, revert to the factory default configuration. See “Reverting to the Default Factory Configuration for the J-EX Series Switch” on page 353. Before you begin connecting and configuring a J-EX Series switch through the console using the CLI: • Set the following parameter values in the console server or PC: • Baud Rate—9600 • Flow Control—None • Data—8 • Parity—None 185 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • Stop Bits—1 • DCD State—Disregard To connect and configure the switch from the console using the CLI: 1. Connect the console port to a laptop or PC using the RJ-45 to DB-9 serial port adapter. The RJ-45 cable and RJ-45 to DB-9 serial port adapter are supplied with the switch. • J-EX4500 switch—The console port is located on the front panel of the switch. • J-EX8200 switch—The console port is located on the Switch Fabric and Routing Engine (SRE) module in slot SRE0 in a J-EX8208 switch or on the Routing Engine (RE) module in slot RE0 in a J-EX8216 switch. 2. At the Junos OS shell prompt root%, type ezsetup. 3. Enter the hostname. This is optional. 4. Enter the root password you plan to use for this device. You are prompted to re-enter the root password. 5. Enter yes to enable services like Telnet and SSH. By default, Telnet is not enabled and SSH is enabled. NOTE: When Telnet is enabled, you will not be able to log in to a J-EX Series switch through Telnet using root credentials. Root login is allowed only for SSH access. 6. Use the Management Options page to select the management scenario: NOTE: On J-EX4500 and J-EX8200 switches, only the out-of-band management option is available. • • Configure in-band management. In this scenario you have the following two options: • Use the default VLAN. • Create a new VLAN—If you select this option, you are prompted to specify the VLAN name, VLAN ID, management IP address, and default gateway. Select the ports that must be part of this VLAN. Configure out-of-band management. Specify the IP address and gateway of the management interface. Use this IP address to connect to the switch. 7. Specify the SNMP Read Community, Location, and Contact to configure SNMP parameters. These parameters are optional. 8. Specify the system date and time. Select the time zone from the list. These options are optional. 186 Chapter 15: Initial Configuration 9. The configured parameters are displayed. Enter yes to commit the configuration. The configuration is committed as the active configuration for the switch. 10. (For J-EX4500 switches only) Enter the request chassis pic-mode intraconnect operational mode command to set the PIC mode to intraconnect. You can now log in with the CLI or the J-Web interface to continue configuring the switch. If you use the J-Web interface to continue configuring the switch, the Web session is redirected to the new management IP address. If the connection cannot be made, the J-Web interface displays instructions for starting a J-Web session. Related Documentation • Connecting and Configuring a J-EX Series Switch (J-Web Procedure) on page 187 • Installing and Connecting a J-EX4200 Switch • Installing and Connecting a J-EX4500 Switch • Installing and Connecting a J-EX8208 Switch • Installing and Connecting a J-EX8216 Switch Connecting and Configuring a J-EX Series Switch (J-Web Procedure) There are two ways to connect and configure a J-EX Series switch: one method is through the console using the command-line interface (CLI) and the other is using the J-Web interface. This topic describes the J-Web procedure. NOTE: Before you begin the configuration, enable a DHCP client on the management PC you will connect to the switch so that the PC can obtain an IP address dynamically. 187 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 NOTE: Read the following steps before you begin the configuration. You must complete the initial configuration using EZSetup within 10 minutes. The switch exits EZSetup after 10 minutes and reverts to the factory default configuration, and the PC loses connectivity to the switch. • J-EX4200, J-EX4500, or J-EX8200 switch—The LCD panel displays a count-down timer when the switch is in initial setup mode. To connect and configure the switch using the J-Web interface: 1. Transition the switch into initial setup mode: • J-EX4200, J-EX4500, or J-EX8200 switch—Use the Menu and Enter buttons located to the right of the LCD panel (see Figure 6 on page 188): Figure 6: LCD Panel in a J-EX4200, J-EX4500, or J-EX8200 Switch 1. Press the Menu button until you see MAINTENANCE MENU. Then press the Enter button. 2. Press Menu until you see ENTER EZSetup. Then press Enter. If EZSetup does not appear as an option in the menu, select Factory Default to return the switch to the factory default configuration. EZSetup is displayed in the menu of standalone switches only when a switch is set to the factory default configuration. 3. Press Enter to confirm setup and continue with EZSetup. 2. Connect the Ethernet cable from the Ethernet port on the PC to the switch. • J-EX4200 switch—Connect the cable to port 0 (ge-0/0/0) on the front panel of the switch. • J-EX4500 switch—Connect the cable to the port labeled MGMT on the front panel of the switch. • J-EX8200 switch—Connect the cable to the port labeled MGMT on the Switch Fabric and Routing Engine (SRE) module in slot SRE0 in a J-EX8208 switch or on the Routing Engine (RE) module in slot RE0 in a J-EX8216 switch. These ports are configured as the DHCP server with the default IP address, 192.168.1.1. The switch can assign an IP address to the management PC in the IP address range 192.168.1.2 through 192.168.1.253. 3. From the PC, open a Web browser, type http://192.168.1.1 in the address field, and press Enter. 188 Chapter 15: Initial Configuration 4. On the J-Web login page, type root as the username, leave the password field blank, and click Login. 5. On the Introduction page, click Next. 6. On the Basic Settings page, modify the hostname, the root password, and date and time settings: • Enter the hostname. This is optional. • Enter a password and reenter the password. • Specify the time zone. • Synchronize the date and time settings of the switch with the management PC or set them manually by selecting the appropriate option button. This is optional. Click Next. 7. Use the Management Options page to select the management scenario: NOTE: On J-EX4500 and J-EX8200 switches, only the out-of-band management option is available. • In-band Management—Use VLAN 'default' for management. Select this option to configure all data interfaces as members of the default VLAN. Click Next. Specify the management IP address and the default gateway for the default VLAN. • In-band Management—Create new VLAN for management. Select this option to create a management VLAN. Click Next. Specify the VLAN name, VLAN ID, member interfaces, management IP address, and default gateway for the new VLAN. • Out-of-band Management—Configure management port. Select this option to configure only the management interface. Click Next. Specify the IP address and default gateway for the management interface. 8. Click Next. 9. On the Manage Access page, you may select options to enable Telnet, SSH, and SNMP services. For SNMP, you can configure the read community, location, and contact. 10. Click Next. The Summary screen displays the configured settings. 11. Click Finish. The configuration is committed as the active switch configuration. 189 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 NOTE: After the configuration is committed, the connectivity between the PC and the switch might be lost. To renew the connection, release and renew the IP address by executing the appropriate commands on the management PC or by removing and reinserting the Ethernet cable. 12. (For J-EX4500 switches only) In the CLI, enter the request chassis pic-mode intraconnect operational mode command to set the PIC mode to intraconnect. You can now log in using the CLI or the J-Web interface to continue configuring the switch. If you use the J-Web interface to continue configuring the switch, the Web session is redirected to the new management IP address. If the connection cannot be made, the J-Web interface displays instructions for starting a J-Web session. Related Documentation • Connecting and Configuring a J-EX Series Switch (CLI Procedure) on page 185 • Installing and Connecting a J-EX4200 Switch • Installing and Connecting a J-EX4500 Switch • Installing and Connecting a J-EX8208 Switch • Installing and Connecting a J-EX8216 Switch Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) The LCD panel on the front panel of J-EX Series switches displays a variety of information about the switch in the Status menu and provides the Maintenance menu to allow you to perform basic operations such as initial setup and reboot. You can disable these menus or individual menu options if you do not want switch users to use them. You can also set a custom message that will be displayed on the panel. This topic describes: • Disabling or Enabling Menus and Menu Options on the LCD Panel on page 190 • Configuring a Custom Display Message on page 191 Disabling or Enabling Menus and Menu Options on the LCD Panel By default, the Maintenance menu, the Status menu, and the options in those menus in the LCD panel are enabled. Users can configure and troubleshoot the switch using the Maintenance menu and view certain details about the switch using the Status menu. If you do not want users to be able to use those menus or use some of the menu options, you can disable the menus or individual menu options. You can re-enable the menus or menu options. Issue the show chassis lcd operational mode command to see which menus and menu options are currently enabled. 190 Chapter 15: Initial Configuration NOTE: On some platforms you must specify an FPC slot number in these commands. See the lcd-menu statement for details. To disable a menu: [edit] user@switch# set chassis lcd-menu menu-item menu-name disable To enable a menu: [edit] user@switch# delete chassis lcd-menu menu-item menu-name disable To disable a menu option: [edit] user@switch# set chassis lcd-menu menu-item menu-option disable To enable a menu option: [edit] user@switch# delete chassis lcd-menu menu-item menu-option disable Configuring a Custom Display Message You can configure the second line of the LCD to display a custom message temporarily for 5 minutes or permanently. To display a custom message temporarily: • On a standalone J-EX4200 switch or a J-EX8200 switch: user@switch> set chassis display message message • On a switch in a Virtual Chassis configuration: user@switch> set chassis display message message fpc-slot slot-number To display a custom message permanently: • On a standalone J-EX4200 or J-EX4500 switch or a J-EX8200 switch: user@switch> set chassis display message message permanent • On a switch in a Virtual Chassis configuration: user@switch> set chassis display message message fpc-slot slot-number permanent NOTE: The Menu button and the Enter button are disabled if the LCD is configured to display a custom message. To disable the display of the custom message: user@switch> clear chassis display message You can view the custom message by issuing the command show chassis lcd. 191 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 Related Documentation • LCD Panel in J-EX4200 Switches • LCD Panel in J-EX4500 Switches • LCD Panel in a J-EX8200 Switch Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) To configure date and time on a J-EX Series switch: 1. Select Configure > System Properties > Date & Time. 2. To modify the information, click Edit. Enter information into the Edit Date & Time page as described in Table 42 on page 192. 3. Click one: • To apply the configuration, click OK. • To cancel your entries and return to the System Properties page, click Cancel. NOTE: After you make changes to the configuration in this page, you must commit the changes for them to take effect. To commit all changes to the active configuration, select Commit Options > Commit. See “Using the Commit Options to Commit Configuration Changes (J-Web Procedure)” on page 346 for details about all commit options. Table 42: Date and Time Settings Time Function Your Action Time Zone Identifies the timezone that the switching platform is located in. Select the appropriate time zone from the list. Set Time Synchronizes the system time with that of the NTP server. You can also manually set the system time and date. To immediately set the time, click one: Related Documentation 192 • • Synchronize with PC time—The switch synchronizes the time with that of the PC. • NTP Servers—The switch sends a request to the NTP server and synchronizes the system time. • Manual—A pop-up window allows you to select the current date and time from a list. J-Web User Interface for J-EX Series Switches Overview on page 153 Chapter 15: Initial Configuration Configuring System Identity for a J-EX Series Switch (J-Web Procedure) To configure identification details for a J-EX Series switch: 1. Select Configure > System Properties > System Identity. The System Identity page displays configuration details. 2. To modify the configuration, click Edit. Enter information into the System Identity page as described in Table 43 on page 193. NOTE: After you make changes to the configuration in this page, you must commit the changes for them to take effect. To commit all changes to the active configuration, select Commit Options > Commit. See “Using the Commit Options to Commit Configuration Changes (J-Web Procedure)” on page 346 for details about all commit options. Table 43: Set Up Configuration Summary Field Function Your Action Host Name Defines the hostname of the switching platform. Type the hostname. Domain Name Defines the network or subnetwork that the machine belongs to. Type the domain name. Root Password Sets the root password that user root can use to log in to the switching platform. Type a plain-text password. The system encrypts the password. NOTE: After a root password has been defined, it is required when you log in to the J-Web user interface or the CLI. Confirm Root Password Verifies that the root password has been typed correctly. Retype the password. DNS Name Servers Specifies a DNS server for the switching platform to use to resolve hostnames into addresses. To add an IP address, click Add. To edit an IP address, click Edit. To delete an IP address, click Delete. Domain Search Specifies the domains to be searched. To add a domain, click Add. To edit a domain click Edit. To delete a domain, click Delete. Related Documentation • Configuring Date and Time for the J-EX Series Switch (J-Web Procedure) on page 192 193 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 194 CHAPTER 16 Configuration Statements for System Setup 195 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 arp Syntax Hierarchy Level Release Information arp { aging-timer minutes; gratuitous-arp-delayseconds; gratuitous-arp-on-ifup; interfaces { interface-name { aging-timer minutes; } } passive-learning; purging; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Specify ARP options. You can enable backup VRRP routers to learn ARP requests for VRRP-IP to VRRP-MAC address translation. You can also set the time interval between ARP updates. Options aging-timer—Time interval in minutes between ARP updates. In environments where the number of ARP entries to update is high (for example, on routers only, metro Ethernet environments), increasing the time between updates can improve system performance. Default: 20 minutes Range: 5 to 240 minutes The remaining statements are explained separately. Required Privilege Level Related Documentation 196 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS ARP Learning and Aging Options for Mapping IPv4 Network Addresses to MAC Addresses • Junos OS Network Interfaces Configuration Guide Chapter 16: Configuration Statements for System Setup authentication-key Syntax Hierarchy Level Release Information Description authentication-key key-number type type value password; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure Network Time Protocol (NTP) authentication keys so that the router or switch can send authenticated packets. If you configure the router or switch to operate in authenticated mode, you must configure a key. Both the keys and the authentication scheme (MD5) must be identical between a set of peers sharing the same key number. Options key-number—Positive integer that identifies the key. type type—Authentication type. It can only be md5. value password—The key itself, which can be from 1 through 8 ASCII characters. If the key contains spaces, enclose it in quotation marks. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring NTP Authentication Keys • broadcast on page 200 • peer on page 220 • server on page 223 • trusted-key on page 226 197 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 auxiliary Syntax Hierarchy Level Release Information Description Default Options auxiliary { disable; insecure; type terminal-type; } [edit system ports] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the characteristics of the auxiliary port. The auxiliary port is disabled. disable—Disable the port. insecure—Disable super user access or root logins to establish terminal connection. type terminal-type—Type of terminal that is connected to the port. Range: ansi, vt100, small-xterm, xterm Default: The terminal type is unknown, and the user is prompted for the terminal type. Required Privilege Level Related Documentation 198 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Set Console and Auxiliary Port Properties Chapter 16: Configuration Statements for System Setup boot-server (NTP) Syntax Hierarchy Level Release Information Description boot-server (address | hostname); [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the server that NTP queries when the router or switch boots to determine the local date and time. When you boot the router or switch, it issues an ntpdate request, which polls a network server to determine the local date and time. You need to configure a server that the router or switch uses to determine the time when the router or switch boots. Otherwise, NTP will not be able to synchronize to a time server if the server’s time appears to be very far off of the local router’s or switch’s time. You can either configure an IP address or a hostname for the boot server. If you configure a hostname instead of an IP address, the ntpdate request resolves the hostname to an IP address when the router or switch boots up. Options Required Privilege Level Related Documentation • address—The IP address of an NTP boot server. • hostname—The hostname of an NTP boot server. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Synchronizing and Coordinating Time Distribution Using NTP 199 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 broadcast Syntax Hierarchy Level Release Information Description Options broadcast address ; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the local router or switch to operate in broadcast mode with the remote system at the specified address. In this mode, the local router or switch sends periodic broadcast messages to a client population at the specified broadcast or multicast address. Normally, you include this statement only when the local router or switch is operating as a transmitter. address—The broadcast address on one of the local networks or a multicast address assigned to NTP. You must specify an address, not a hostname. If the multicast address is used, it must be 224.0.1.1. key key-number—(Optional) All packets sent to the address include authentication fields that are encrypted using the specified key number. Range: Any unsigned 32-bit integer ttl value—(Optional) Time-to-live (TTL) value to use. Range: 1 through 255 Default: 1 version value—(Optional) Specify the version number to be used in outgoing NTP packets. Range: 1 through 4 Default: 4 Required Privilege Level Related Documentation 200 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the NTP Time Server and Time Services Chapter 16: Configuration Statements for System Setup broadcast-client Syntax broadcast-client; Hierarchy Level [edit system ntp] Release Information Description Required Privilege Level Related Documentation Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the local router or switch to listen for broadcast messages on the local network to discover other servers on the same subnet. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Router or Switch to Listen for Broadcast Messages Using NTP 201 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 console (Physical Port) Syntax Hierarchy Level Release Information Description Default Options console { disable; insecure; log-out-on-disconnect; type terminal-type; } [edit system ports] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the characteristics of the console port. The console port is enabled and its speed is 9600 baud. disable—Disable console login connections. insecure—Disable root login connections to the console and auxiliary ports. Configuring the console port as insecure also prevents superusers and anyone with a user identifier (UID) of 0 from establishing terminal connections in multiuser mode. log-out-on-disconnect—Log out the session when the data carrier on the console port is lost. type terminal-type—Type of terminal that is connected to the port. Range: ansi, vt100, small-xterm, xterm Default: The terminal type is unknown, and the user is prompted for the terminal type. Required Privilege Level Related Documentation 202 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Set Console and Auxiliary Port Properties Chapter 16: Configuration Statements for System Setup default-address-selection Syntax Hierarchy Level Release Information default-address-selection; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Use the loopback interface, lo0, as the source address for all locally generated IP packets when the packet is sent through a routed interface, but not when the packet is sent through a local interface such as fxp0. The lo0 interface is the interface to the router’s or switch’s Routing Engine. Default The default address is used as the source address for all locally generated IP packets on outgoing interfaces that are unnumbered. If an outgoing interface is numbered, the default address is chosen using the following sequence: • The primary address on the loopback interface lo0 that is not 127.0.0.1 is used. • The primary address for the primary interface or the preferred address (if configured) for the primary interface is used. By default, the primary address on an interface is selected as the numerically lowest local address configured on the interface. An interface’s primary address is used by default as the local address for broadcast and multicast packets sourced locally and sent out through the interface. An interface’s preferred address is the default local address used for packets sourced by the local router or switch to destinations on the subnet. By default, the numerically lowest local address configured for the interface is chosen as the preferred address on the subnet. To configure a different primary address or preferred address, include the primary or preferred statement at the [edit interfaces interface-name unit logical-unit-number family family address address or [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family address address hierarchy levels. For more information about default, primary, and preferred addresses for an interface, see “Configuring Default, Primary, and Preferred Addresses and Interfaces” in the Junos OS Network Interfaces Configuration Guide. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Select a Fixed Source Address for Locally Generated TCP/IP Packets • Junos OS Network Interfaces Configuration Guide 203 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 domain-name Syntax Hierarchy Level Release Information Description Options Required Privilege Level Related Documentation domain-name domain-name; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the name of the domain in which the router or switch is located. This is the default domain name that is appended to hostnames that are not fully qualified. domain-name—Name of the domain. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Domain Name for the Router or Switch gre-path-mtu-discovery Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation 204 (gre-path-mtu-discovery | no-gre-path-mtu-discovery); [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure path MTU discovery for outgoing GRE tunnel connections: • gre-path-mtu-discovery—Path MTU discovery is enabled. • no-gre-path-mtu-discovery—Path MTU discovery is disabled. Path MTU discovery is enabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for Path MTU Discovery on Outgoing GRE Tunnel Connections Chapter 16: Configuration Statements for System Setup host-name Syntax Hierarchy Level Release Information host-name hostname; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Set the hostname of the router or switch. Options hostname—Name of the router or switch. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Hostname of the Router or Switch icmpv4-rate-limit Syntax Hierarchy Level Release Information Description Options icmpv4-rate-limit { bucket-size seconds; packet-rate pps; } [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure rate-limiting parameters for ICMPv4 messages sent. bucket-size seconds—Number of seconds in the rate-limiting bucket. Range: 0 through 4294967295 seconds Default: 5 packet-rate pps—Rate-limiting packets earned per second. Range: 0 through 4294967295 pps Default: 1000 Required Privilege Level Related Documentation admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Junos OS ICMPv4 Rate Limit for ICMPv4 Routing Engine Messages 205 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 icmpv6-rate-limit Syntax Hierarchy Level Release Information Description Options icmpv6-rate-limit { bucket-size seconds; packet-rate packet-rate; } [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure rate-limiting parameters for ICMPv6 messages sent. bucket-size seconds—Number of seconds in the rate-limiting bucket. Range: 0 through 4294967295 seconds Default: 5 packet-rate pps—Rate-limiting packets earned per second. Range: 0 through 4294967295 pps Default: 1000 Required Privilege Level Related Documentation 206 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Junos OS ICMPv6 Rate Limit for ICMPv6 Routing Engine Messages Chapter 16: Configuration Statements for System Setup inet6-backup-router Syntax Hierarchy Level Release Information Description Options inet6-backup-router address ; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set a default router (running IP version 6 [IPv6]) to use while the local router or switch (running IPv6) is booting and if the routing protocol processes fail to start. The Junos OS removes the route to this router or switch as soon as the software starts. address—Address of the default router. destination destination-address—(Optional) Destination address that is reachable through the backup router. Include this option to achieve network reachability while loading, configuring, and recovering the router or switch, but without the risk of installing a default route in the forwarding table. Default: All hosts (default route) are reachable through the backup router. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring a Backup Router 207 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 internet-options Syntax Hierarchy Level Release Information Description internet-options { (gre-path-mtu-discovery | no-gre-path-mtu-discovery); icmpv4-rate-limit bucket-size bucket-size packet-rate packet-rate; icmpv6-rate-limit bucket-size bucket-size packet-rate packet-rate; (ipip-path-mtu-discovery | no-ipip-path-mtu-discovery); ipv6-duplicate-addr-detection-transmits; (ipv6-reject-zero-hop-limit | no-ipv6-reject-zero-hop-limit); (ipv6-path-mtu-discovery | no-ipv6-path-mtu-discovery); ipv6-path-mtu-discovery-timeout; no-tcp-rfc1323; no-tcp-rfc1323-paws; (path-mtu-discovery | no-path-mtu-discovery); source-port upper-limit ; (source-quench | no-source-quench); tcp-drop-synfin-set; tcp-mss mss-value; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure system IP options to protect against certain types of denial-of-service (DoS) attacks. The remaining statements are explained separately. Required Privilege Level Related Documentation 208 admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Junos OS ICMPv4 Rate Limit for ICMPv4 Routing Engine Messages • Configuring the Junos OS ICMPv6 Rate Limit for ICMPv6 Routing Engine Messages • Configuring the Junos OS for IP-IP Path MTU Discovery on IP-IP Tunnel Connections • Configuring the Junos OS for Path MTU Discovery on Outgoing GRE Tunnel Connections • Configuring the Junos OS for Path MTU Discovery on Outgoing TCP Connections • Configuring the Junos OS for IPv6 Duplicate Address Detection Attempts • Configuring the Junos OS for Acceptance of IPv6 Packets with a Zero Hop Limit • Configuring the Junos OS to Ignore ICMP Source Quench Messages • Configuring the Junos OS to Enable the Router or Switch to Drop Packets with the SYN and FIN Bits Set • Configuring the Junos OS to Disable TCP RFC 1323 Extensions • Configuring the Junos OS to Disable the TCP RFC 1323 PAWS Extension • Configuring the Junos OS to Extend the Default Port Address Range Chapter 16: Configuration Statements for System Setup • Configuring TCP MSS for Session Negotiation ipip-path-mtu-discovery Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation (ipip-path-mtu-discovery | no-ipip-path-mtu-discovery); [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure path MTU discovery for outgoing IP-IP tunnel connections: • ipip-path-mtu-discovery—Path MTU discovery is enabled. • no-ipip-path-mtu-discovery—Path MTU discovery is disabled. Path MTU discovery is enabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for IP-IP Path MTU Discovery on IP-IP Tunnel Connections • internet-options on page 208 ipv6-duplicate-addr-detection-transmits Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation ipv6-duplicate-addr-detection-transmits; [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Control the number of attempts for IPv6 duplicate address detection. The default value is 3. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for IPv6 Duplicate Address Detection Attempts 209 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 ipv6-path-mtu-discovery Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation (ipv6-path-mtu-discovery | no-ipv6-path-mtu-discovery); [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure path MTU discovery for IPv6 packets: • ipv6-path-mtu-discovery—IPv6 path MTU discovery is enabled. • no-ipv6-path-mtu-discovery—IPv6 path MTU discovery is disabled. IPv6 path MTU discovery is enabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for IPv6 Path MTU Discovery ipv6-path-mtu-discovery-timeout Syntax Hierarchy Level Release Information Description Options ipv6-path-mtu-discovery-timeout minutes; [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Set the IPv6 path MTU discovery timeout interval. minutes—IPv6 path MTU discovery timeout. Default: 10 minutes Required Privilege Level Related Documentation 210 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for IPv6 Path MTU Discovery Chapter 16: Configuration Statements for System Setup ipv6-reject-zero-hop-limit Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation (ipv6-reject-zero-hop-limit | no-ipv6-reject-zero-hop-limit); [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Enable and disable rejecting incoming IPv6 packets with a zero hop limit value in their header. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for Acceptance of IPv6 Packets with a Zero Hop Limit 211 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 lcd-menu Syntax J-EX4200, or J-EX4500 switch: lcd-menu fpc slot-number { menu-item (menu-name | menu-option); } J-EX8200 switch: lcd-menu { menu-item (menu-name | menu-option); } Hierarchy Level Release Information Description Options [edit chassis] Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Disable or enable the Maintenance menu or the Status menu in the LCD panel. none—(J-EX8200 switches only) Disable or enable the specified menu or menu options. fpc slot-number—(J-EX4200 and J-EX4500 switches only) Disable or enable the specified menu or menu options, where slot-number is: • 0—On a standalone J-EX4200 switch or a J-EX4500 switch • 0–9—On a J-EX4200 switch in a Virtual Chassis. The value is the member ID of the switch. The remaining statement is explained separately. Required Privilege Level Related Documentation 212 interface—To view this statement in the configuration. interface-level—To add this statement to the configuration. • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • LCD Panel in J-EX4200 Switches • LCD Panel in J-EX4500 Switches • LCD Panel in a J-EX8200 Switch Chapter 16: Configuration Statements for System Setup location Syntax Hierarchy Level Release Information Description Options location { altitude feet; building name; country-code code; floor number; hcoord horizontal-coordinate; lata service-area; latitude degrees; longitude degrees; npa-nxx number; postal-code postal-code; rack number; vcoord vertical-coordinate; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the system location in various formats. altitude feet—Number of feet above sea level. building name—Name of building. The name of the building can be 1 to 28 characters in length. If the string contains spaces, enclose it in quotation marks (" "). country-code code—Two-letter country code. floor number—Floor in the building. hcoord horizontal-coordinate—Bellcore Horizontal Coordinate. lata service-area—Long-distance service area. latitude degrees—Latitude in degree format. longitude degrees—Longitude in degree format. npa-nxx number—First six digits of the phone number (area code and exchange). postal-code postal-code—Postal code. rack number—Rack number. vcoord vertical-coordinate—Bellcore Vertical Coordinate. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Physical Location of the Router or Switch 213 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 menu-item Syntax menu-item (menu-name | menu-option); Hierarchy Level [edit chassis lcd-menu fpc slot-number] Release Information Description Options Statement introduced in Junos OS Release 10.2 for J-EX Series switches. Disable or enable the Maintenance menu, the Status menu, or an individual option in one of those menus in the LCD panel. menu-name—Name of the LCD menu: • maintenance-menu • status-menu menu-option—Specific option on one of the LCD menus. You must include the quotation marks when you type the option. • ''maintenance-menu halt-menu''—System halt option • ''maintenance-menu system-reboot''—System reboot option • ''maintenance-menu rescue-config''—Load rescue option • ''maintenance-menu vc-uplink-config''—(J-EX4200 switches only) Request VC port option for a J-EX4200 switch in a Virtual Chassis configuration • ''maintenance-menu factory-default''—Factory default option • ''status-menu vcp-status''—(J-EX4200 switches only) Virtual Chassis port (VCP) status for a J-EX4200 switch in a Virtual Chassis configuration • ''status-menu sf-status1-menu''—(J-EX8200 switches only) Status of the switch fabric on the Switch Fabric and Routing Engine (SRE) module in slot SRE0 on J-EX8208 switches. Status of the switch fabric on the Switch Fabric (SF) modules in slots SF0 and SF1 on J-EX8216 switches. • ''status-menu sf-status2-menu''—(J-EX8200 switches only) Status of the switch fabric on the SRE module in slot SRE1 on J-EX8208 switches. Status of the switch fabric on the SF modules in slots SF2–SF5 on J-EX8216 switches. • ''status-menu sf-status3-menu''—(J-EX8216 switches only) Status of the switch fabric on the SF modules in slots SF6 and SF7 • ''status-menu power-status''—(J-EX4200 and J-EX4500 switches only) Status of the power supply • ''status-menu psu-status1-menu''—(J-EX8200 switches only) Status of the power supplies in slots P0 and P1 • ''status-menu psu-status2-menu''—(J-EX8200 switches only) Status of the power supplies in slots P2–P5 • 214 ''status-menu environ-status''—Status of the fan and the temperature Chapter 16: Configuration Statements for System Setup • ''status-menu show-version''—The version of Junos OS for J-EX Series switches loaded on the switch Required Privilege Level Related Documentation view-level—To view this statement in the configuration. control-level—To add this statement to the configuration. • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • LCD Panel in J-EX4200 Switches • LCD Panel in J-EX4500 Switches • LCD Panel in a J-EX8200 Switch multicast-client Syntax Hierarchy Level Release Information Description Options multicast-client ; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For NTP, configure the local router or switch to listen for multicast messages on the local network to discover other servers on the same subnet. address—(Optional) One or more IP addresses. If you specify addresses, the router or switch joins those multicast groups. Default: 224.0.1.1. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Router or Switch to Listen for Multicast Messages Using NTP 215 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 no-multicast-echo Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation no-multicast-echo; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the Routing Engine from responding to ICMP echo requests sent to multicast group addresses. The Routing Engine responds to ICMP echo requests sent to multicast group addresses. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Disable the Routing Engine Response to Multicast Ping Packets no-ping-record-route Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 216 no-ping-record-route; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Junos OS to disable the reporting of the IP address in ping responses. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Disable the Reporting of IP Address and Timestamps in Ping Responses Chapter 16: Configuration Statements for System Setup no-ping-time-stamp Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation no-ping-time-stamp; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Junos OS to disable the recording of timestamps in ping responses. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Disable the Reporting of IP Address and Timestamps in Ping Responses no-redirects Syntax Hierarchy Level Release Information Description no-redirects; [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Disable the sending of protocol redirect messages by the router or switch. To disable the sending of redirect messages on a per-interface basis, include the no-redirects statement at the [edit interfaces interface-name unit logical-unit-number family family] hierarchy level. Default Required Privilege Level Related Documentation The router or switch sends redirect messages. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Disable Protocol Redirect Messages on the Router or Switch • Junos OS Network Interfaces Configuration Guide 217 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 no-tcp-rfc1323 Syntax Hierarchy Level Release Information no-tcp-rfc1323; [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Description Configure the Junos OS to disable RFC 1323 TCP extensions. Required Privilege Level system—To view this statement in the configuration. system-control—To add this statement to the configuration. Related Documentation • Configuring the Junos OS to Disable TCP RFC 1323 Extensions no-tcp-rfc1323-paws Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation 218 no-tcp-rfc1323-paws; [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the Junos OS to disable the RFC 1323 Protection Against Wrapped Sequence (PAWS) number extension. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Disable the TCP RFC 1323 PAWS Extension Chapter 16: Configuration Statements for System Setup ntp Syntax Hierarchy Level Release Information Description ntp { authentication-key number type type value password; boot-server address; broadcast ; broadcast-client; multicast-client ; peer address ; server address ; source-address source-address; trusted-key [ key-numbers ]; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure NTP on the router or switch. The remaining statements are explained separately. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Synchronizing and Coordinating Time Distribution Using NTP path-mtu-discovery Syntax Hierarchy Level Release Information Description Default Required Privilege Level Related Documentation (path-mtu-discovery | no-path-mtu-discovery); [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure path MTU discovery for outgoing Transmission Control Protocol (TCP) connections: • path-mtu-discovery—Path MTU discovery is enabled. • no-path-mtu-discovery—Path MTU discovery is disabled. Path MTU discovery is enabled. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS for Path MTU Discovery on Outgoing TCP Connections 219 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 peer Syntax Hierarchy Level Release Information Description Options peer address ; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For NTP, configure the local router or switch to operate in symmetric active mode with the remote system at the specified address. In this mode, the local router or switch and the remote system can synchronize with each other. This configuration is useful in a network in which either the local router or switch or the remote system might be a better source of time. address—Address of the remote system. You must specify an address, not a hostname. key key-number—(Optional) All packets sent to the address include authentication fields that are encrypted using the specified key number. Range: Any unsigned 32-bit integer prefer—(Optional) Mark the remote system as the preferred host, which means that if all other factors are equal, this remote system is chosen for synchronization among a set of correctly operating systems. version value—(Optional) Specify the NTP version number to be used in outgoing NTP packets. Range: 1 through 4 Default: 4 Required Privilege Level Related Documentation 220 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the NTP Time Server and Time Services Chapter 16: Configuration Statements for System Setup ports Syntax Hierarchy Level Release Information Description ports { auxiliary { disable; insecure; type terminal-type; } console { disable; insecure; log-out-on-disconnect; type terminal-type; } } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the properties of the console and auxiliary ports. The ports are located on the router’s craft interface. See the switch’s hardware documentation for port locations. The remaining statements are explained separately. Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the Junos OS to Set Console and Auxiliary Port Properties 221 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 processes Syntax Hierarchy Level Release Information Description processes { process-name (enable | disable) failover (alternate-media | other-routing-engine); timeout seconds; } [edit system] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure which Junos OS processes are running on the router or switch. CAUTION: Never disable any of the software processes unless instructed to do so by a customer support engineer. Default Options All processes are enabled by default. (enable | disable)—(Optional) Enable or disable a specified process. failover (alternate-media | other-routing-engine)—(Optional) For routers or switches with redundant Routing Engines only, switch to backup media if a process fails repeatedly. If a process fails four times within 30 seconds, the router or switch reboots from the alternate media or the other Routing Engine. process-name—One of the valid process names. You can obtain a complete list of process names by using the CLI command completion feature. After specifying a process name, command completion also indicates any additional options for that process. timeout seconds—(Optional) How often the system checks the watchdog timer, in seconds. If the watchdog timer has not been checked in the specified number of seconds, the system reloads. If you set the time value too low, it is possible for the system to reboot immediately after it loads. Values: 15, 60, or 180 Default: 180 seconds (rounded up to 291 seconds by the Junos kernel) Required Privilege Level Related Documentation 222 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Disabling Junos OS Processes Chapter 16: Configuration Statements for System Setup server (NTP) Syntax Hierarchy Level Release Information Description Options server address ; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For NTP, configure the local router or switch to operate in client mode with the remote system at the specified address. In this mode, the local router or switch can be synchronized with the remote system, but the remote system can never be synchronized with the local router or switch. address—Address of the remote system. You must specify an address, not a hostname. key key-number—(Optional) Use the specified key number to encrypt authentication fields in all packets sent to the specified address. Range: Any unsigned 32-bit integer prefer—(Optional) Mark the remote system as preferred host, which means that if all other things are equal, this remote system is chosen for synchronization among a set of correctly operating systems. version value—(Optional) Specify the version number to be used in outgoing NTP packets. Range: 1 through 4 Default: 4 Required Privilege Level Related Documentation system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring the NTP Time Server and Time Services tcp-drop-synfin-set Syntax Hierarchy Level Release Information Description Required Privilege Level Related Documentation tcp-drop-synfin-set; [edit system internet-options] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure the router or switch to drop packets that have both the SYN and FIN bits set. admin—To view this statement in the configuration. admin-control—To add this statement to the configuration. • Configuring the Junos OS to Enable the Router or Switch to Drop Packets with the SYN and FIN Bits Set 223 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 traceoptions (SBC Configuration Process) Syntax Hierarchy Level Release Information Description Options traceoptions { file filename ; flag flag; } [edit system processes sbc-configuration-process] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. Configure trace options for the session border controller (SBC) process of the border signaling gateway (BSG). file filename—Name of the file that receives the output of the tracing operation. Enclose the name in quotation marks. All files are placed in the directory /var/log. You can include the following file options: • files number—(Optional) Maximum number of trace files. When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten. If you specify a maximum number of files, you must also specify a maximum file size with the size option and a filename. Range: 2 through 1000 Default: 3 files • match regex—(Optional) Refine the output to include lines that contain the regular expression. • no-world-readable—(Optional) Disable unrestricted file access. • size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues until the maximum number of trace files is reached. Then the oldest trace file is overwritten. If you specify a maximum file size, you also must specify a maximum number of trace files with the files option and filename. Syntax: xk to specify KB, xm to specify MB, or xg to specify GB. Range: 10 KB through 1 GB Default: 128 KB • world-readable—(Optional) Enable unrestricted file access. flag flag—Tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags: 224 Chapter 16: Configuration Statements for System Setup • all trace-level—Trace all SBC process operations. • common trace-level—Trace common events. • configuration trace-level—Trace configuration events. • device-monitor trace-level—Trace device monitor events. • ipc trace-level—Trace IPC events. • memory—pool trace-level—Trace memory pool events. • trace-level—Trace level options are related to the severity of the event being traced. When you choose a trace level, messages at that level and higher levels are captured. Enter one of the following trace levels as the trace-level: • debug—Log all code flow of control. • error—Log failures with a short-term effect. • info—Log summary for normal operations, such as the policy decisions made for a call. • Required Privilege Level Related Documentation • trace—Log program trace START and EXIT macros. • warning—Log failure recovery events or failure of an external entity. ui trace-level—Trace user interface operations. system—To view this statement in the configuration. system-control—To add this statement to the configuration. • See “Troubleshooting the IMSG” in the Junos OS Multiplay Solutions Guide • System Management Configuration Statements 225 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 trusted-key Syntax Hierarchy Level Release Information Description Options trusted-key [ key-numbers ]; [edit system ntp] Statement introduced before Junos OS Release 10.2 for J-EX Series switches. For NTP, configure the keys you are allowed to use when you configure the local router or switch to synchronize its time with other systems on the network. key-numbers—One or more key numbers. Each key can be any 32-bit unsigned integer except 0. Required Privilege Level Related Documentation 226 system—To view this statement in the configuration. system-control—To add this statement to the configuration. • Configuring NTP Authentication Keys • authentication-key on page 197 • broadcast on page 200 • peer on page 220 • server on page 223 CHAPTER 17 Operational Commands for System Setup 227 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 clear chassis display message Syntax Release Information Description Options Required Privilege Level Related Documentation List of Sample Output Output Fields clear chassis display message Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear or stop a text message on the craft interface display, which is on the front of the router or switch or on the LCD panel display on the router or switch. The craft interface alternates the display of text messages with standard craft interface messages, switching between messages every 2 seconds. By default, on both the router and the switch, the text message is displayed for 5 minutes. The craft interface display has four 20-character lines. The LCD panel display has two 16-character lines, and text messages appear only on the second line. none—Clear or stop a text message on the craft interface display. clear • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • set chassis display message on page 257 • show chassis craft-interface clear chassis display message on page 228 See show chassis craft-interface for an explanation of output fields. Sample Output clear chassis display message The following example displays and then clears the text message on the craft interface display: user@host> show chassis craft-interface Red alarm: LED off, relay off Yellow alarm: LED off, relay off Host OK LED: On Host fail LED: Off FPCs 0 1 2 3 4 5 6 7 ------------------------------Green .. *.. * *. Red ........ LCD screen: +--------------------+ |NOC contact Dusty | |(888) 526-1234 | +--------------------+ user@host> clear chassis display message user@host> show chassis craft-interface Red alarm: LED off, relay off Yellow alarm: LED off, relay off Host OK LED: On 228 Chapter 17: Operational Commands for System Setup Host fail LED: Off FPCs 0 1 2 3 4 5 6 7 ------------------------------Green .. *.. * *. Red ........ LCD screen: +--------------------+ |host | |Up: 0+17:05:47 | | | |Temperature OK | +--------------------+ 229 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 clear system reboot Syntax clear system reboot Syntax (J-EX Series Switch) clear system reboot Release Information Description Options Command introduced before Junos OS Release 10.2 for J-EX Series switches. Clear any pending system software reboots or halts. none—Clear all pending system software reboots or halts. all-members—(J-EX4200 switches only) (Optional) Clear all halt or reboot requests on all members of the Virtual Chassis configuration. both-routing-engines—(Systems with multiple Routing Engines) (Optional) Clear all halt or reboot requests on both Routing Engines. local—(J-EX4200 switches only) (Optional) Clear all halt or reboot requests on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Clear all halt or reboot requests on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. Required Privilege Level Related Documentation List of Sample Output Output Fields 230 maintenance • request system reboot • request system reboot clear system reboot on page 231 When you enter this command, you are provided feedback on the status of your request. Chapter 17: Operational Commands for System Setup Sample Output clear system reboot user@host> clear system reboot reboot requested by root at Sat Dec 12 19:37:34 1998 [process id 17855] Terminating... 231 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 configure Syntax Release Information Description Options configure Command introduced before Junos OS Release 10.2 for J-EX Series switches. Enter configuration mode. When this command is entered without any optional keywords, everyone can make configuration changes and commit all changes made to the configuration. none—Enter configuration mode. dynamic—(Optional) Configure routing policies and certain routing policy objects in a dynamic database that is not subject to the same verification required in the standard configuration database. As a result, the time it takes to commit changes to the dynamic database is much shorter than for the standard configuration database. You can then reference these policies and policy objects in routing policies you configure in the standard database. exclusive—(Optional) Lock the candidate configuration for as long as you remain in configuration mode, allowing you to make changes without interference from other users. Other users can enter and exit configuration mode, but they cannot change the configuration. private—(Optional) Allow multiple users to edit different parts of the configuration at the same time and to commit only their own changes, or to roll back without interfering with one another's changes. You cannot commit changes in configure private mode when another user is in configure exclusive mode. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields For more information about the different methods of entering configuration mode and the restrictions that apply, see the Junos OS System Basics Configuration Guide. configure • show configuration on page 269 configure on page 232 When you enter this command, you are placed in configuration mode and the system prompt changes from hostname> to hostname#. Sample Output configure 232 user@host> configure Chapter 17: Operational Commands for System Setup Entering configuration mode [edit] user@host# 233 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 op Syntax Release Information Description Options op filename Command introduced before Junos OS Release 10.2 for J-EX Series switches. Execute an op script stored in one of the following locations: • On the router or switch in the /var/db/scripts/op directory • At a remote URL detail—(Optional) Display detailed output. argument-name argument-value—(Optional) Specify one or more arguments to the script. For each argument you include on the command line, you must specify a corresponding value for the argument. key (md5 | sha-256 | sha1) key-value—(Optional) With the option, specify a checksum hash to verify the integrity of the script. You can include the option if the checksum statement is included at the [edit system scripts op file filename] hierarchy level. url url—(Optional) Specify a URL where the script is located. Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields 234 For more information about Junos op scripts, see the Junos OS Configuration and Operations Automation Guide. maintenance • Executing an Op Script in the Junos OS Configuration and Operations Automation Guide • Executing an Op Script from a Remote Site in the Junos OS Configuration and Operations Automation Guide • checksum • file checksum md5 on page 378 • file checksum sha-256 on page 380 • file checksum sha1 on page 379 op on page 235 op url on page 235 When you enter this command, you are provided feedback on the status of your request. Chapter 17: Operational Commands for System Setup Sample Output op op url user@host> op script1 interface ge-0/2/0.0 protocol inet user@host> op url https://www.juniper.net/fa/2009-04-01.01.slax key md5 8de24d09e1d90b2581bb937d2a5ad590 interface ge-0/2/0.0 protocol inet 235 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request chassis pic Syntax Release Information Description request chassis pic (offline | online) fpc-slot slot-number pic-slot slot-number Command introduced before Junos OS Release 10.2 for J-EX Series switches. Control the operation of the PIC. NOTE: To view a list of built-in PICs on the router or switch chassis, use the show chassis hardware command. Options offline—Take the PIC offline. online—Bring the PIC online. fpc-slot slot-number—Flexible PIC Concentrator (FPC) slot number. Replace slot-number with a value appropriate for your router or switch: • J-EX Series switches: • J-EX4200 standalone switches—0. • J-EX4200 switches in a Virtual Chassis configuration—0 through 9 (switch’s member ID). • J-EX8208 switches—0 through 7 (line card). • J-EX8216 switches—0 through 15 (line card). pic-slot slot-number—PIC slot number. For J-EX4200 switches, it is 0 for built-in network interfaces and 1 for interfaces on uplink modules. For J-EX8208 and J-EX8216 switches, it is 0. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • show chassis hardware on page 656 • show chassis pic on page 665 request chassis pic on page 236 When you enter this command, you are provided feedback on the status of your request. Sample Output request chassis pic 236 user@host> request chassis pic pic-slot 0 online fpc-slot 0 FPC 0, PIC 0 is already online Chapter 17: Operational Commands for System Setup request chassis routing-engine master Syntax Release Information Description request chassis routing-engine master (acquire | release | switch) Command introduced before Junos OS Release 10.2 for J-EX Series switches. For routers or switches with multiple Routing Engines, control which Routing Engine is the master. NOTE: Successive graceful Routing Engine switchover events must be a minimum of 240 seconds (4 minutes) apart after both Routing Engines have come up. If the router or switch displays a warning message similar to “Standby Routing Engine is not ready for graceful switchover. Packet Forwarding Engines that are not ready for graceful switchover might be reset,” do not attempt switchover. If you choose to proceed with switchover, only the Packet Forwarding Engines that were not ready for graceful switchover are reset. None of the Flexible PIC concentrators (FPCs) should spontaneously restart. We recommend that you wait until the warning no longer appears and then proceed with the switchover. Options acquire—Attempt to become the master Routing Engine. release—Request that the other Routing Engine become the master. switch—Toggle mastership between Routing Engines. The acquire, release, and switch options have the following suboptions: no-confirm—(Optional) Do not request confirmation for the switch. force—(Optional) Available only with the acquire option. Force the change to a new master Routing Engine. Additional Information Because both Routing Engines are always running, the transition from one to the other as the master Routing Engine is immediate. However, the changeover interrupts communication to the System and Switch Board (SSB). The SSB takes several seconds to reinitialize the Flexible PIC Concentrators (FPCs) and restart the PICs. Interior gateway protocol (IGP) and BGP convergence times depend on the specific network environment. By default, the Routing Engine in slot 0 (RE0) is the master and the Routing Engine in slot 1 (RE1) is the backup. To change the default master Routing Engine, include the routing-engine statement at the [edit chassis redundancy] hierarchy level in the configuration. For more information, see the Junos OS System Basics Configuration Guide 237 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 To have the backup Routing Engine become the master Routing Engine, use the request chassis routing-engine master switch command. If you use this command to change the master and then restart the chassis software for any reason, the master reverts to the default setting. NOTE: Although the configurations on the two Routing Engines do not have to be the same and are not automatically synchronized, we recommend making both configurations the same. Required Privilege Level Related Documentation List of Sample Output Output Fields maintenance • show chassis routing-engine on page 668 request chassis routing-engine master acquire on page 238 request chassis routing-engine master switch on page 238 When you enter this command, you are provided feedback on the status of your request. Sample Output request chassis routing-engine master acquire user@host> request chassis routing-engine master acquire warning: Traffic will be interrupted while the PFE is re-initialized warning: The other routing engine's file system could be corrupted Reset other routing engine and become master ? [yes,no] (no) request chassis routing-engine master switch user@host> request chassis routing-engine master switch warning: Traffic will be interrupted while the PFE is re-initialized Toggle mastership between Routing Engines ? [yes,no] (no) yes Resolving mastership... Complete. The other Routing Engine becomes the master. Switch mastership back to the local Routing Engine: user@host> request chassis routing-engine master switch warning: Traffic will be interrupted while the PFE is re-initialized Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The local routing engine becomes the master. 238 Chapter 17: Operational Commands for System Setup request system halt Syntax Syntax (J-EX Series Switch) Release Information Description Options request system halt request system halt Command introduced before Junos OS Release 10.2 for J-EX Series switches. Stop the router or switch software. none—Stop the router or switch software immediately. all-members—(J-EX4200 switches only) (Optional) Halt all members of the Virtual Chassis configuration. at time —(Optional) Time at which to stop the software, specified in one of the following ways: • now—Stop the software immediately. This is the default. • +minutes—Number of minutes from now to stop the software. • yymmddhhmm—Absolute time at which to stop the software, specified as year, month, day, hour, and minute. • hh:mm—Absolute time on the current day at which to stop the software. both-routing-engines—(Optional) Halt both Routing Engines at the same time. local—(J-EX4200 switches only) (Optional) Halt the local Virtual Chassis member. in minutes—(Optional) Number of minutes from now to stop the software. This option is an alias for the at +minutes option. media (compact-flash | disk | removable-compact-flash | usb)—(Optional) Boot medium for next boot. media (external | internal)—(J-EX Series switches) (Optional) Halt the boot media: 239 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 • external—Halt the external mass storage device. • internal—Halt the internal flash device. member member-id—(J-EX4200 switches only) (Optional) Halt the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. message "text"—(Optional) Message to display to all system users before stopping the software. other-routing-engine—(Optional) Halt the other Routing Engine from which the command is issued. For example, if you issue the command from the master Routing Engine, the backup Routing Engine is halted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is halted. slice slice—(J-EX Series switches) (Optional) Halt a partition on the boot media. This option has the following suboptions: Additional Information Required Privilege Level Related Documentation List of Sample Output Output Fields 240 • 1—Halt partition 1. • 2—Halt partition 2. • alternate—Reboot from the alternate partition. NOTE: If you have a router or switch with two Routing Engines and you want to shut the power off to the router or switch or remove a Routing Engine, you must first halt the backup Routing Engine (if it has been upgraded), then halt the master Routing Engine. To halt a Routing Engine, issue the request system halt command. You can also halt both Routing Engines at the same time by issuing the request system halt both-routing-engines command. maintenance • clear system reboot on page 230 request system halt on page 241 request system halt (in 2 Hours) on page 241 request system halt (Immediately) on page 241 request system halt (at 1:20 AM) on page 241 request system halt (in 2 Hours) on page 241 request system halt (Immediately) on page 241 request system halt (at 1:20 AM) on page 241 When you enter this command, you are provided feedback on the status of your request. Chapter 17: Operational Commands for System Setup Sample Output request system halt user@host> request system halt Halt the system ? [yes,no] (no) yes *** FINAL System shutdown message from root@section2 *** System going down IMMEDIATELY Terminated ... syncing disks... 11 8 done The operating system has halted. Please press any key to reboot. request system halt (in 2 Hours) The following example, which assumes that the time is 5 PM (1700), illustrates three different ways to request that the system stop 2 hours from now: user@host> request system halt at +120 user@host> request system halt in 120 user@host> request system halt at 19:00 request system halt (Immediately) user@host> request system halt at now request system halt (at 1:20 AM) To stop the system at 1:20 AM, enter the following command. Because 1:20 AM is the next day, you must specify the absolute time. user@host> request system halt at yymmdd120 request system halt at 120 Halt the system at 120? [yes,no] (no) yes Sample Output request system halt (in 2 Hours) The following example, which assumes that the time is 5 PM (1700), illustrates three different ways to request that the system stop 2 hours from now: user@switch> request system halt at +120 user@switch> request system halt in 120 user@switch> request system halt at 19:00 request system halt (Immediately) user@switch> request system halt at now request system halt (at 1:20 AM) To stop the system at 1:20 AM, enter the following command. Because 1:20 AM is the next day, you must specify the absolute time. user@switch> request system halt at yymmdd120 request system halt at 120 Halt the system at 120? [yes,no] (no) yes 241 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request system logout Syntax Release Information request system logout (pid pid | terminal terminal | user username) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Description Log out users from the router or switch and the configuration database. If a user held the configure exclusive lock, this command clears the exclusive lock. Options all—(Optional) Log out all sessions owned by a particular PID, terminal session, or user. pid pid—Log out the user session using the specified management process identifier (PID). The PID type must be management process. terminal terminal—Log out the user for the specified terminal session. user username—Log out the specified user. Required Privilege Level Related Documentation List of Sample Output Output Fields configure • Junos OS System Basics Configuration Guide request system logout on page 242 When you enter this command, you are provided feedback on the status of your request. Sample Output request system logout 242 user@host> request system logout user tammy all Connection closed by foreign host. Chapter 17: Operational Commands for System Setup request system power-off Syntax Syntax (J-EX Series Switch) Release Information Description Options request system power-off request system power-off Command introduced before Junos OS Release 10.2 for J-EX Series switches. Power off the software. none—Power off the router or switch software immediately. all-members—(J-EX4200 switches only) (Optional) Power off all members of the Virtual Chassis configuration. at time—(Optional) Time at which to power off the software, specified in one of the following ways: • now—Power off the software immediately. This is the default. • +minutes—Number of minutes from now to power off the software. • yymmddhhmm—Absolute time at which to power off the software, specified as year, month, day, hour, and minute. • hh:mm—Absolute time on the current day at which to power off the software. both-routing-engines—(Optional) Power off both Routing Engines at the same time. in minutes—(Optional) Number of minutes from now to power off the software. This option is an alias for the at +minutes option. local—(J-EX4200 switches only) (Optional) Power off the local Virtual Chassis member. media (compact-flash | disk | removable-compact-flash | usb)—(Optional) Boot medium for next boot. (The options removable-compact-flash and usb pertain to the J Series routers only.) 243 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 media (external | internal)—(J-EX Series switches) (Optional) Power off the boot media: • external—Power off the external mass storage device. • internal—Power off the internal flash device. member member-id—(J-EX4200 switches only) (Optional) Power off the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. message "text"—(Optional) Message to display to all system users before powering off the software. other-routing-engine—(Optional) Power off the other Routing Engine from which the command is issued. For example, if you issue the command from the master Routing Engine, the backup Routing Engine is halted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is halted. slice slice—(J-EX Series switches) (Optional) Power off a partition on the boot media. This option has the following suboptions: Required Privilege Level List of Sample Output Output Fields • 1—Power off partition 1. • 2—Power off partition 2. • alternate—Reboot from the alternate partition. maintenance request system power-off on page 244 When you enter this command, you are provided feedback on the status of your request. Sample Output request system power-off user@host> request system power-off message “This router will be powered off in 30 minutes. Please save your data and log out immediately.” warning: This command will not halt the other routing-engine. If planning to switch off power, use the both-routing-engines option. Power Off the system ? [yes,no] (no) yes *** FINAL System shutdown message from remote@nutmeg *** System going down IMMEDIATELY This router will be powered off in 30 minutes. Please save your data and log out immediately. Shutdown NOW! [pid 5177] 244 Chapter 17: Operational Commands for System Setup request system reboot Syntax Release Information Description request system reboot Command introduced before Junos OS Release 10.2 for J-EX Series switches. Reboot the Junos OS. Reboot requests are recorded in the system log files, which you can view with the show log command. You can view the process names with the show system processes command. Options none—Reboots the software immediately. all-members | local | member member-id—(J-EX4200 switch only) (Optional) Specify which member of the Virtual Chassis to reboot: • all-members—Reboots each switch that is a member of the Virtual Chassis. • local—Reboots the local switch, meaning the switch you are logged into, only. • member member-id—Reboots the specified member switch of the Virtual Chassis. at time—(Optional) Time at which to reboot the software, specified in one of the following ways: • +minutes—Number of minutes from now to reboot the software. • hh:mm—Absolute time on the current day at which to reboot the software, specified in 24-hour time. • now—Stop or reboot the software immediately. This is the default. • yymmddhhmm—Absolute time at which to reboot the software, specified as year, month, day, hour, and minute. in minutes—(Optional) Number of minutes from now to reboot the software. This option is an alias for the at +minutes option. media (external | internal)—(Optional) Boot medium for the next boot. The external option reboots the switch using a software package stored on an external boot source, such as a USB flash drive. The internal option reboots the switch using a software package stored in an internal memory source. message “text”—(Optional) Message to display to all system users before rebooting the software. 245 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 other-routing-engine—(Optional) Reboot the other Routing Engine from which the command is issued. For example, if you issue the command from the master Routing Engine, the backup Routing Engine is rebooted. Similarly, if you issue the command from the backup Routing Engine, the master Routing Engine is rebooted. slice (1 | 2 | alternate)—(Optional) Reboot using the specified partition on the boot media. This option has the following suboptions: • 1—Reboot from partition 1. • 2—Reboot from partition 2. • alternate—Reboot from the alternate partition, which is the partition that did not boot the switch at the last bootup. Required Privilege Level Related Documentation Output Fields maintenance • clear system reboot on page 230 • request system halt on page 239 When you enter this command, you are provided feedback on the status of your request. Sample Output request system reboot user@host> request system reboot Reboot the system ? [yes,no] (no) request system reboot (at 2300) user@host> request system reboot at 2300 message ?Maintenance time!? Reboot the system ? [yes,no] (no) yes shutdown: [pid 186] *** System shutdown message from root@berry.network.net *** System going down at 23:00 request system reboot (in 2 Hours) The following example, which assumes that the time is 5 PM (17:00), illustrates three different ways to request the system to reboot in two hours: user@host> request system reboot at +120 user@host> request system reboot in 120 user@host> request system reboot at 19:00 request system reboot (Immediately) user@host> request system reboot at now request system reboot (at 1:20 AM) To reboot the system at 1:20 AM, enter the following command. Because 1:20 AM is the next day, you must specify the absolute time. user@host> request system reboot at 06060120 request system reboot at 120 Reboot the system at 120? [yes,no] (no) yes 246 Chapter 17: Operational Commands for System Setup request system scripts convert Syntax Release Information Description Options request system scripts convert (slax-to-xslt | xslt-to-slax) source source/filename destination destination/ Command introduced before Junos OS Release 10.2 for J-EX Series switches. Convert an Extensible Stylesheet Language Transformations (XSLT) script to Stylesheet Language, Alternative syntaX (SLAX), or convert a SLAX script to XSLT. destination destination/ —Specify a destination for the converted file. Optionally, you can specify a filename for the converted file. If you do not specify a filename, the software assigns one automatically. The default destination filename is the same as the source filename, except the file extension is altered. For example, the software converts a source file called test.xsl to test.slax. The software converts a source file called test1.slax to test1.xsl. slax-to-xslt—Convert a SLAX script to XSLT. source source/filename—Specify a source file that you want to convert. xslt-to-slax—Convert an XSLT script to SLAX. Required Privilege Level List of Sample Output Output Fields maintenance request system scripts convert slax-to-xslt on page 247 request system scripts convert xslt-to-slax on page 247 When you enter this command, you are provided feedback on the status of your request. Sample Output request system scripts convert slax-to-xslt user@host> request system scripts convert slax-to-xslt source /var/db/scripts/op/script1.slax destination /var/db/scripts/op conversion complete request system scripts convert xslt-to-slax user@host> request system scripts convert xslt-to-slax source /var/db/scripts/commit/script1.xsl destination /var/db/scripts/commit conversion complete 247 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request system scripts refresh-from commit Syntax Release Information Description request system scripts refresh-from commit file file-name url url-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Automatically download the initial Junos OS configuration and a set of standard commit scripts during a Junos XML management protocol/NETCONF session when a switch is brought up for the first time. The Junos XML management protocol equivalent for this operational mode command is: Options file file-name—Name of the file to be downloaded. url url-path—URL of the file to be downloaded. Required Privilege Level Related Documentation List of Sample Output maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 329 • Junos OS Junos XML Management Protocol Guide • Junos OS NETCONF XML Management Protocol Guide request system scripts refresh-from commit file config.txt url http://host1.juniper.net on page 248 Sample Output request system scripts refresh-from commit file config.txt url http://host1.juniper.net 248 user@switch> request system scripts refresh-from commit file config.txt url http://host1.juniper.net user@switch> Chapter 17: Operational Commands for System Setup request system scripts refresh-from event Syntax Release Information Description request system scripts refresh-from event file file-name url url-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Automatically download the initial Junos OS configuration and a set of standard event scripts during a Junos XML management protocol/NETCONF session when a switch is brought up for the first time. The Junos XML management protocol equivalent for this operational mode command is: commit file-name> URL Options file file-name—Name of the file to be downloaded. url url-path—URL of the file to be downloaded. Required Privilege Level Related Documentation List of Sample Output maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 329 • Junos OS Junos XML Management Protocol Guide • Junos OS NETCONF XML Management Protocol Guide request system scripts refresh-from event file config.txt url http://host1.juniper.net on page 249 Sample Output request system scripts refresh-from event file config.txt url http://host1.juniper.net user@switch> request system scripts refresh-from event file config.txt url http://host1.juniper.net user@switch> 249 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 request system scripts refresh-from op Syntax Release Information Description request system scripts refresh-from op file file-name url url-path Command introduced before Junos OS Release 10.2 for J-EX Series switches. Automatically download the initial Junos OS configuration and a set of standard op scripts during a Junos XML management protocol/NETCONF session when a switch is brought up for the first time. The Junos XML management protocol equivalent for this operational mode command is: event file-name> URL Options file file-name—Name of the file to be downloaded. url url-path—URL of the file to be downloaded. Required Privilege Level Related Documentation List of Sample Output maintenance • Understanding Automatic Refreshing of Scripts on J-EX Series Switches on page 329 • Junos OS Junos XML Management Protocol Guide • Junos OS NETCONF XML Management Protocol Guide request system scripts refresh-from op file config.txt url http://host1.juniper.net on page 250 Sample Output request system scripts refresh-from op file config.txt url http://host1.juniper.net 250 user@switch> request system scripts refresh-from op file config.txt url http://host1.juniper.net user@switch> Chapter 17: Operational Commands for System Setup request system storage cleanup Syntax Syntax (J-EX Series Switch) Release Information Description Options request system storage cleanup op file-name> URL request system storage cleanup Command introduced before Junos OS Release 10.2 for J-EX Series switches. Free storage space on the router or switch by rotating log files and proposing a list of files for deletion. User input is required for file deletion. all-members—(J-EX4200 switches only) (Optional) Delete files on all members of the Virtual Chassis configuration. dry-run—(Optional) List files proposed for deletion (without deleting them). local—(J-EX4200 switches only) (Optional) Delete files on the local Virtual Chassis member. member member-id—(J-EX4200 switches only) (Optional) Delete files on the specified member of the Virtual Chassis configuration. Replace member-id with a value from 0 through 9. Additional Information Required Privilege Level List of Sample Output Output Fields If logging is configured and being used, the dry-run option will rotate the log files. In that case, the output displays the message “Currently rotating log files, please wait.” If no logging is currently underway, the output displays only a list of files to delete. maintenance request system storage cleanup dry-run on page 251 request system storage cleanup on page 252 When you enter this command, you are provided feedback on the status of your request. Sample Output request system storage cleanup dry-run user@host> request system storage cleanup dry-run Currently rotating log files, please wait. This operation can take up to a minute. List of files to delete: 11.4K 7245B 11.8K 3926B 3962B Size Date Mar 8 15:00 Feb 5 15:00 Feb 22 13:00 Mar 16 13:57 Feb 22 12:47 Name /var/log/messages.1.gz /var/log/messages.3.gz /var/log/messages.2.gz /var/log/messages.0.gz /var/log/sampled.1.gz 251 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 4146B 4708B 7068B 13.7K 890B 65.8M 63.1M request system storage cleanup Mar Dec Jan Dec Feb Oct Oct 8 21 16 27 22 26 26 12:20 11:39 18:00 22:00 17:22 09:10 09:13 /var/log/sampled.0.gz /var/log/sampled.2.gz /var/log/messages.4.gz /var/log/messages.5.gz /var/tmp/sampled.pkts /var/sw/pkg/jinstall-7.4R1.7-export-signed.tgz /var/sw/pkg/jbundle-7.4R1.7.tgz user@host> request system storage cleanup Currently rotating log files, please wait. This operation can take up to a minute. List of files to delete: 11.4K 7245B 11.8K 3926B 11.6K 7254B 12.9K 3726B 3962B 4146B 4708B 7068B 13.7K 890B 65.8M 63.1M Size Date Mar 8 15:00 Feb 5 15:00 Feb 22 13:00 Mar 16 13:57 Mar 8 15:00 Feb 5 15:00 Feb 22 13:00 Mar 16 13:57 Feb 22 12:47 Mar 8 12:20 Dec 21 11:39 Jan 16 18:00 Dec 27 22:00 Feb 22 17:22 Oct 26 09:10 Oct 26 09:13 Name /var/log/messages.1.gz /var/log/messages.3.gz /var/log/messages.2.gz /var/log/messages.0.gz /var/log/messages.5.gz /var/log/messages.6.gz /var/log/messages.8.gz /var/log/messages.7.gz /var/log/sampled.1.gz /var/log/sampled.0.gz /var/log/sampled.2.gz /var/log/messages.4.gz /var/log/messages.5.gz /var/tmp/sampled.pkts /var/sw/pkg/jinstall-7.4R1.7-export-signed.tgz /var/sw/pkg/jbundle-7.4R1.7.tgz Delete these files ? [yes,no] (yes) 252 Chapter 17: Operational Commands for System Setup restart Syntax restart | sampling | service-deployment | services pgcp gateway gateway-name |sbc-configuration-process | snmp | usb-control| web-management> Syntax (J-EX Series Switch) restart Release Information Description Command introduced before Junos OS Release 10.2 for J-EX Series switches. Restart a Junos OS process. CAUTION: Never restart a software process unless instructed to do so by a customer support engineer. A restart might cause the router or switch to drop calls and interrupt transmission, resulting in possible loss of data. Options none—Same as gracefully. adaptive-services—(Optional) Restart the configuration management process that manages the configuration for stateful firewall, Network Address Translation (NAT), intrusion detection services (IDS), and IP Security (IPsec) services on the Adaptive Services PIC. audit-process—(Optional) Restart the RADIUS accounting process. autoinstallation—(J-EX Series switch only) (Optional) Restart the autoinstallation process. chassis-control—(Optional) Restart the chassis management process. class-of-service—(Optional) Restart the class-of-service (CoS) process, which controls the router's or switch’s CoS configuration. database-replication—(J-EX Series switch only) (Optional) Restart the database replication process. 253 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 dhcp—(J-EX Series switch only) (Optional) Restart the software process for a Dynamic Host Configuration Protocol (DHCP) server. A DHCP server allocates network IP addresses and delivers configuration settings to client hosts without user intervention. dhcp-service—(J-EX Series switch only) (Optional) Restart the Dynamic Host Configuration Protocol process. diameter-service—(Optional) Restart the diameter process. disk-monitoring—(Optional) Restart disk monitoring, which checks the health of the hard disk drive on the Routing Engine. dot1x-protocol—(J-EX Series switch only) (Optional) Restart the port-based network access control process. dynamic-flow-capture—(Optional) Restart the dynamic flow capture (DFC) process, which controls DFC configurations on Monitoring Services III PICs. ecc-error-logging—(Optional) Restart the error checking and correcting (ECC) process, which logs ECC parity errors in memory on the Routing Engine. ethernet-link-fault-management—(J-EX Series switch only) (Optional) Restart the Ethernet OAM link fault management process. ethernet-switching—(J-EX Series switch only) (Optional) Restart the Ethernet switching process. event-processing—(Optional) Restart the event process (eventd). firewall—(Optional) Restart the firewall management process, which manages firewall configuration. general-authentication-service—(J-EX Series switch only) (Optional) Restart the general authentication process. gracefully—(Optional) Restart the software process. immediately—(Optional) Immediately restart the software process. interface-control—(Optional) Restart the interface process, which controls the router's or switch’s physical interface devices and logical interfaces. ipsec-key-management—(Optional) Restart the IPsec key management process. kernel-replication—(Optional) Restart the kernel replication process, which replicates the state of the backup Routing Engine when graceful Routing Engine switchover is configured. l2-learning—(Optional) Restart the Layer 2 address flooding and learning process. lacp—(Optional) Restart the Link Aggregation Control Protocol process. license-service—(J-EX Series switch only) (Optional) Restart the feature license management process. 254 Chapter 17: Operational Commands for System Setup lldpd-service—(J-EX Series switch only) (Optional) Restart the Link Layer Discovery Protocol process. mib-process—(Optional) Restart the Management Information Base (MIB) II process, which provides the router's MIB II agent. mountd-service—(J-EX Series switch only) (Optional) Restart the service for NFS mounts requests. multicast-snooping—(J-EX Series switch only) (Optional) Restart the multicast snooping process. pgcp-service—(Optional) Restart the pgcpd service process running on the Routing Engine. This option does not restart pgcpd processes running on mobile station PICs. To restart pgcpd processes running on mobile station PICs, use the services pgcp gateway option. pgm—(Optional) Restart the process that implements the Pragmatic General Multicast (PGM) protocol for assisting in the reliable delivery of multicast packets. pic-services-logging—(Optional) Restart the logging process for some PICs. With this process, also known as fsad (the file system access daemon), PICs send special logging information to the Routing Engine for archiving on the hard disk. ppp—(Optional) Restart the Point-to-Point Protocol (PPP) process. pppoe—(Optional) Restart the Point-to-Point Protocol over Ethernet (PPPoE) process. protected-system-domain-service—(Optional) Restart the Protected System Domain (PSD) process. redundancy-interface-process—(Optional) Restart the ASP redundancy process. remote-operations—(Optional) Restart the remote operations process, which provides the ping and traceroute MIBs. root-system-domain-service—(Optional) Restart the Root System Domain (RSD) service. routing—(J-EX Series switch only) (Optional) Restart the routing protocol process. routing —(Optional) Restart the routing protocol process, which controls the routing protocols that run on the router or switch and maintains the routing tables. Optionally, restart the routing protocol process for the specified logical system only. sampling—(Optional) Restart the sampling process, which performs packet sampling and cflowd export. secure-neighbor-discovery—(J-EX Series switch only) (Optional) Restart the secure Neighbor Discovery Protocol process. service-deployment—(Optional) Restart the service deployment service process. 255 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 services pgcp gateway gateway-name—(Optional) Restart the pgcpd process for a specific BGF running on an MS-PIC. This option does not restart the pgcpd process running on the Routing Engine. To restart the pgcpd process on the Routing Engine, use the pgcp-service option. sflow-service—(J-EX Series switch only) (Optional) Restart the flow sampling (sFlow technology) process. snmp—(Optional) Restart the SNMP process, which provides the router's or switch’s SNMP master agent. soft—(Optional) Reread and reactivate the configuration without completely restarting the software processes. For example, BGP peers stay up and the routing table stays constant. Omitting this option results in a graceful restart of the software process. vrrp—(J-EX Series switch only) (Optional) Restart the Virtual Router Redundancy Protocol process. web-management—(J-EX Series switch only) (Optional) Restart the Web management process. Required Privilege Level Related Documentation List of Sample Output Output Fields reset • Overview of Junos OS CLI Operational Mode Commands restart interfaces on page 256 When you enter this command, you are provided feedback on the status of your request. Sample Output restart interfaces 256 user@host> restart interfaces interfaces process terminated interfaces process restarted Chapter 17: Operational Commands for System Setup set chassis display message Syntax Release Information Description Options set chassis display message "message" Command introduced before Junos OS Release 10.2 for J-EX Series switches. Display or stop a text message on the craft interface display, which is on the front of the router, or on the LCD panel display on the switch. The craft interface alternates the display of text messages with standard craft interface messages, switching between messages every 2 seconds. By default, on both the router and the switch, the text message is displayed for 5 minutes. The craft interface display has four 20-character lines. The LCD panel display has two 16-character lines, and text messages appear only on the second line. "message"—Message to display. On the craft interface display, if the message is longer than 20 characters, it wraps onto the next line. If a word does not fit on one line, the entire word moves down to the next line. Any portion of the message that does not fit on the display is truncated. An empty pair of quotation marks (“ ”) deletes the text message from the craft interface display. On the LCD panel display, the message is limited to 16 characters. fpc-slot slot-number—(J-EX4200 only) On the router or switch, display the text message on the craft interface for a specific Flexible PIC Concentrator (FPC). Replace slot-number with a value from 0 through 31. On the switch, display the text message for a specific member of a Virtual Chassis, where fpc-slot slot-number corresponds to the member ID. Replace slot-number with a value from 0 through 9. permanent—(Optional) Display a text message on the craft interface display or LCD panel display permanently. Required Privilege Level Related Documentation List of Sample Output Output Fields clear • Configuring the LCD Panel on J-EX Series Switches (CLI Procedure) on page 190 • clear chassis display message on page 228 • show chassis craft-interface set chassis display message (Creating) on page 257 set chassis display message (Deleting) on page 258 See show chassis craft-interface for an explanation of output fields. Sample Output set chassis display message (Creating) The following example shows how to set the display message and verify the result: user@host> set chassis display message "NOC contact Dusty (888) 555-1234" 257 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 message sent user@host> show chassis craft-interface Red alarm: LED off, relay off Yellow alarm: LED off, relay off Host OK LED: On Host fail LED: Off FPCs 0 1 2 3 4 5 6 7 ------------------------------Green .. *.. * *. Red ........ LCD screen: +--------------------+ |NOC contact Dusty | |(888) 555-1234 | +--------------------+ set chassis display message (Deleting) The following example shows how to delete the display message and verify that the message is removed: user@host> set chassis display message "" message sent user@host> show chassis craft-interface Red alarm: LED off, relay off Yellow alarm: LED off, relay off Host OK LED: On Host fail LED: Off FPCs 0 1 2 3 4 5 6 7 ------------------------------Green .. *.. * *. Red ........ LCD screen: +--------------------+ |host | |Up: 0+17:05:47 | | | |Temperature OK | +--------------------+ 258 Chapter 17: Operational Commands for System Setup set date Syntax Release Information Description Options set date (date-time ntp ) Command introduced before Junos OS Release 10.2 for J-EX Series switches. Set the date and time. date-time—Date and time. Enter this string inside quotation marks. ntp—Use a Network Time Protocol (NTP) server to synchronize the current date and time setting on the router or switch. servers—(Optional) Specify the IP address of one or more NTP servers. source-address source-address—Specify the source address that the router or switch uses to contact the remote NTP server. Required Privilege Level Related Documentation List of Sample Output Output Fields view • Setting the Date and Time set date on page 259 When you enter this command, you are provided feedback on the status of your request. Sample Output set date user@host> set date ntp 21 Apr 17:22:02 ntpdate[3867]: step time server 172.17.27.46 offset 8.759252 sec 259 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show chassis firmware Syntax Release Information Description show chassis firmware Command introduced before Junos OS Release 10.2 for J-EX Series switches. Command introduced for J-EX8200 switches in Junos OS Release 10.2 for J-EX Series switches. On the routers and switches, display the version levels of the firmware running on the System Control Board (SCB), Switching and Forwarding Module (SFM), System and Switch Board (SSB), Forwarding Engine Board (FEB), Flexible PIC Concentrators (FPCs), and Routing Engines. On J-EX4200 switches, display the version levels of the firmware running on the switch. On a J-EX8208 switch, display the version levels of the firmware running on the Switch Fabric and Routing Engine (SRE) modules and on the line cards (shown as FPCs). On a J-EX8216 switch, display the version levels of the firmware running on the Routing Engine (RE) modules and on the line cards (shown as FPCs). Options none—Display the version levels of the firmware running. For a J-EX4200 switch that is a member of a Virtual Chassis, display version levels for all members. Required Privilege Level List of Sample Output Output Fields view show chassis firmware (J-EX4200 Switch) on page 260 show chassis firmware (J-EX8200 Switch) on page 261 Table 44 on page 260 lists the output fields for the show chassis firmware command. Output fields are listed in the approximate order in which they appear. Table 44: show chassis firmware Output Fields Field Name Field Description Part Chassis part name. Type Type of firmware: On routers: ROM or O/S. On switches: uboot or loader. Version Version of firmware running on the chassis part. Sample Output show chassis firmware (J-EX4200 Switch) user@host> show chassis firmware Part FPC 0 FPC 1 260 Type uboot loader uboot loader Version U-Boot 1.1.6 (Feb 6 2008 - 11:27:42) FreeBSD/PowerPC U-Boot bootstrap loader 2.1 U-Boot 1.1.6 (Feb 6 2008 - 11:27:42) FreeBSD/PowerPC U-Boot bootstrap loader 2.1 Chapter 17: Operational Commands for System Setup FPC 2 show chassis firmware (J-EX8200 Switch) uboot loader U-Boot 1.1.6 (Feb 6 2008 - 11:27:42) FreeBSD/PowerPC U-Boot bootstrap loader 2.1 user@host> show chassis firmware Part FPC 0 FPC 3 FPC 5 FPC 7 Routing Engine 0 Routing Engine 1 Type U-Boot loader U-Boot loader U-Boot loader U-Boot loader U-Boot loader U-Boot loader Version U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 U-Boot 1.1.6 (Dec 4 2009 - 13:17:34) 3.1.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 U-Boot 1.1.6 (Feb 6 2009 - 05:31:46) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0 FreeBSD/PowerPC U-Boot bootstrap loader 2.2 261 Dell PowerConnect J-Series Ethernet Switch Complete Software Guide for Junos OS, Release 11.1: Volume 1 show chassis lcd Syntax Release Information show chassis lcd >